[OHM] OHM for Knight News Challenge?
Susanna Ånäs
susanna.anas at gmail.com
Mon Sep 14 10:35:19 UTC 2015
Sorry, false info: Weston-sub-Edge has an item
https://www.wikidata.org/wiki/Q20968424 and the railway station has another
one https://www.wikidata.org/wiki/Q7989380. Just did not find it because of
the spelling differences :)
Susanna
2015-09-14 13:07 GMT+03:00 Lester Caine <lester at lsces.co.uk>:
> On 14/09/15 10:32, Susanna Ånäs wrote:
> > I am opening my can as well, laying out some interests I have:
> >
> > I am a fan of the Wikidata data model, and I would like to challenge
> > this community to see if it can be applied to OHM.
> I have yet to be convince!
> But if there was a clean boilerplate for a place having all of the
> various data fields the current manual blocks and categories links
> currently include manually. I have raw data that is clear to use but
> inputing it looks like a nightmare.
>
> > The OHM data will not be able to be stored IN Wikidata. The granularity
> > of it is far too dense, and the application of notability thresholds
> > cannot go with geodata. The positive outcome would be to be able to map
> > to Wikidata elements and read/write data across.
> OSM includes a link for a place to wikipedia/wikidata
> This then uses the storage in wikidata to manage abstract data such as
> population figures and the like which vary over time. The problem part
> is managing the changes of layout of structures on the ground over time.
> New road layouts where the historic material is already mapped, while
> simple new additions such as the new housing developments around here
> just need a 'start_date' properly adding. Although the odd anoying
> roundabout on a once straight road is a small element of history that
> I'm going to need to map shortly ...
>
> > Unfortunately Weston Subedge does not have an item yet...
> The vast majority of the material in wikipedia needs importing into
> wikidata?
> Then the wikipedia information blocks can be upgraded to the wikidata
> content, and we get an easier update path.
>
> > The item (village) would have a title in all of the languages, and it
> > also has aliases for quick alternative names. Statements can be added to
> > *Weston Subedge (item)*.
> > - Label (English): /Weston Subedge/
> > - Aliases (English): /Weston Sub-Edge, Weston-Subedge/
> > - Statement: <official name
> > <https://www.wikidata.org/wiki/Property:P1448> (English)> /Weston
> Subedge/
> > - Statement: <native label
> > <https://www.wikidata.org/wiki/Property:P1705> (English)> /Weston
> > Sub-Edge/ with a qualifier(s): <startdate
> > <https://www.wikidata.org/wiki/Property:P580>> /date/, <end date
> > <https://www.wikidata.org/wiki/Property:P582>> /date/ and source:
> > <stated in <https://www.wikidata.org/wiki/Property:P248>> /some map URI
> > + possible other qualifiers./
> > /+ additional statements for alternative names./
> You see my book that is even worse than XML schema data :( I see the
> point but thousands of <Property:PXXX> entries to navigate?
>
> > Supporting shapes has not been defined yet, but the structure would be
> > similar.
> We have a vast amount of the geo material already contained in OSM. It
> is maintaining the historic changes to that which is the first problem.
> Changes to political boundaries over the last several years are buried
> in the OSM change log now and need recovering. Treating OHM in isolation
> is simply wrong!
>
> > I would look into
> Need to earn a crust so I'll have to digest this next weekend ... should
> be working now :)
>
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> _______________________________________________
> Historic mailing list
> Historic at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/historic
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/historic/attachments/20150914/f32af012/attachment.html>
More information about the Historic
mailing list