Hello, Let aside the technical aspect—this is a good question and I hope somebody will be able to give valuable advice—I believe that some datasets in government open data portals are poisoned with either incorrect or outdated data. Importing them into OSM could make some damage without extensive review by humans with local knowledge.
Here are two examples I am familiar with, and for which I believe bulk imports should be avoided. 1) Villo! stations: name tag is an odd upper-case string concatenating the name and the address, and capacity seems to be missing in the source data (but can be manually retrieved for the website by clicking each station one by one). 2) STIB/MIVB stops: not only the GTFS export replaces the name of the stop with a truncated and upper-case version of it—to cope with limitations of their real-time app on smaller devices—but the lat/lon values refer to the stop position… in OSM it must be a node that is part of the way used by the route (and they do not match). Incidently, STIB/MIVB does not maintain any database with the location of the stop *posts*; the only place in the world where this information exists is in OSM. Have a nice day. Yves On Tue, 3 Apr 2018 21:22:33 +0200 eMerzh <[email protected]> wrote: > Hi all :) > > I'm just discovering the data sets that are in > http://opendatastore.brussels/ (brussels region) > and some of them might be really interesting for osm. > Like : > - school list > - streets surfaces > - 3d buildings > - parkings > - transports stop poles > and much more > > , but I was wondering if there was an "easy" way to do the conflation... > automatically or semi-manually ... > for now the only way I see is to transform data, put them in a postgis > then doing all the work manually... but... > ** there must be a better way ** > no? _______________________________________________ Talk-be mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-be
