Import/London/Greater London Authority/Charging Stations
overview
this audit is currently underway thanks to all those osm members who have contributed, once the validation run is complete, we will import the audited charging stations dataset to osm with josm and progress to more projects
background
at fosdem 2019 talks on linking wikidata and osm and using thousands of taxi gps traces to improve osm gave rise to the idea to consider osm as a platform for syndicating government open data more widely; the [Import/Catalogue import catalogue] also shows a series of works to publish government open data on osm
the gis team at london city hall are in the early stages of creating a re-usable procedure to release batches of open data, licensed via the open government licence and compatible with the open database licence
initial investigations
before starting work on batch platform imports, the first step was to become familiar with osm, overpass, tags, changesets, the london community and talk-gb-london groups, links with osm.wikidata.link wikidata, the community interest company
first trial, drinking fountains
we also had a go at using id and a maps.me note to handle a series of 18 newly installed drinking fountains individually, and received some feedback on the use of tags in changesets - a further ten drinking fountains were to be individually added as they were installed (this didn't take place, although there are now 28 fountains listed)
charging stations
background
the source data is licensed under the open government licence and contains lon/lat plus capacity and taxipublicuse fields, the latter of which indicates that a point is reserved for taxis, and use by others may incur a fine, for example see this photo of an e-taxi charging station on tower bridge road by vlivyur, licensed under CC-BY-SA
osm conflation tool
based on the guidance received, we're trialling OSM Conflator by Ilya Zyerev
the conflation tool now has a profile.py and has been run on the source dataset a dataset of electric vehicle rapid charging stations
osm conflation audit tool
osm conflation this has created a change file to be verified by using the audit tool
permanent ids
in addition to auditing the incoming data for duplications and modifications existing osm elements, it is also proposed to add a wikidata=* tag:key to each element, having previously added the data to wikidata, and then subsequently adding the osm relation identifier to the wikidata record to demonstrate reciprocal use. an example of this is the bundesautobahn 555 wikidata entry, which includes an identifiers section cross-referencing the osm way record this achieves a permanent identifier for the osm record, which gives the original data contributor an audit trail should the osm element become changed in some way, such as deleted/re-added or split.
there is a discussion about mutability in osm records, and wikidata is seen as one means of giving contributions a permanent reference, nonetheless, according to the "notability criterion" wikidata=* tags are generally added to osm relations only (not nodes or ways) and furthermore only to citable features that can be cross-referenced, e.g. locations of unique signifcance - this means that giving wikidata tags to commonplace features challenges the criteria for wikidata inclusion.
wikidata
ev charging station entry
a query of london boroughs shows no stations charted as yet
the proposal then is that once the audit has completed, to create the validated records on wikidata first, using QuickStatements, and then add the wikidata=* tag to each record as it is add to osm