[OHM] OHM for Knight News Challenge?
Susanna Ånäs
susanna.anas at gmail.com
Mon Sep 14 09:32:05 UTC 2015
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.
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.
Unfortunately Weston Subedge does not have an item yet...
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.*
Supporting shapes has not been defined yet, but the structure would be
similar.
I would look into
- TopoTime <http://dh.stanford.edu/topotime/>
- SAPO <http://www.seco.tkk.fi/ontologies/sapo/>
- Albin's proposal
<http://abbe98.github.io/blog/2015/03/26/mapping-the-past-with-linked-data-in-openhistoricalmap/>
- Humphrey Southall's work for using Wikidata
<http://www.geos.ed.ac.uk/~gisteac/eeo_agi/2013-14/11_southall_11042014.pdf>
There are many other leads, and it would be great to bring together a
functional simple way of working. Time for the shared doc!
https://hackpad.com/OpenHistoricalMap-zqcHY8EVehs
Susanna
2015-09-14 10:20 GMT+03:00 Lester Caine <lester at lsces.co.uk>:
> On 14/09/15 01:37, Richard Welty wrote:
> >> The Knight News Challenge this year is "How might we make data work
> >> > for individuals and communities?"
> >> >
> >> > Proposals remain the same:
> >> >
> >> > The key feature I think we need is ways to better represent the data
> >> > - dynamic maps of any desired time range. Server side and client side
> >> > should be looked at.
> >> >
> > i think a key thing is a coherent plan for representing complex time
> > data. it
> > needs to be reasonable to enter, but also reasonable for data consumers
> to
> > use, and it needs to represent some sometimes quite complex situations as
> > well as some very ambiguous situations (where precise times are not
> known.)
> >
> > during the SOTM US hack day, i know that there was a pretty good
> > conversation
> > on the other side of the table about representation of time, but i was
> > too deep
> > in getting minutely updates of overpass going to pay anywhere near enough
> > attention.
>
> Having just spent far too much time on something else over the weekend I
> can appreciate the problem of keeping up with everything ...
>
> My own can of worms relates to the 'time' element of OSM data and why
> separate development of a mechanism to fix that is irritating. My can of
> worms has had several posts in both OSM lists and on wikipedia but the
> crux of the problem is that different people have different views of
> even the same data.
>
> To document a short example, one of the next villages over from here is
> 'Weston Subedge' or at least that is the name identified in the OS data,
> on the Royal Mail PAF file it's 'Weston-Subedge' while on the current
> road signs it's a combination of 'Weston Subedge', 'Weston Sub-Edge' and
> 'Weston-Sub-Edge'. The latter seems to be what was 'adopted' by the
> local railway when it was built with old pictures showing
> 'Weston-Sub-Edge' on the platform and timetables, while the OS maps
> continued to show 'Weston Subedge Station'. I am waiting on an answer to
> a couple of emails to official bodies as to their take on things, but
> even simply adding the data a name change arose would seem to be a
> pointless exercise when everybody is using a different name.
>
> ORIGINALLY I was looking to add start_date and end_date to the OSM data
> to map these changes over time, and we have accurate dates for such
> events as the opening and closure of the station and can identify the
> source of it's different names but just how do you handle even the
> current differences in the name?
>
> It's not the only example of name confusion just down the 30 odd miles
> of 'track' and of cause we have the argument on OSM on mapping
> 'abandoned' railway lines and pushing the old data to OHM. The
> Honeybourne line is a perfect example of such a line which physically
> exists today even if there are no tracks on some sections. The track is
> fast approaching Broadway and it would have been nice to document it's
> progress as each section was restored and 'appeared' again on the OSM
> data, but we just have the whole route of cleared track bed, and while
> the remaining section from Broadway to Honeybourne is shown as a track,
> it is owned by Sustrans with the intention of restoring the track in
> conjunction with a cycleway. The data is OSM has been 'adjusted' so that
> the information remains on the current map.
>
> We should be documenting current history today, but instead a lot of
> that material is being lost or buried in a way it can't easily be used.
> I feel that I have a fairly self contained section of data that could be
> used as an example of best practice when working with both current,
> historic and forthcoming data, but don't know what to do with it :(
>
> --
> 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/c77ac738/attachment-0001.html>
More information about the Historic
mailing list