Malcolm, On 08/13/2016 02:36 PM, Malcolm Meyer wrote: > Ok, that all sounds doable, but the thing that you said that makes me > pause is 'the code needed to transform the data'. I have been under > the assumtion that I can just import something like geojson into JOSM > or another editor, assuming all the feature properties match.
OSM generally assumes that the uploader takes responsiblity for what they're importing and how it relates to what is already in OSM. That's why we don't encourage any form of "just importing a GeoJSON" becuase this often makes people careless. If, for example, one of your imported sidewalks runs straight through a house in OSM or overlaps with a street, then the expectation is that the importer double-checks and either fixes their data or the street/house that already is in OSM. And if OSM already has sidewalks in an area, then the importer would be expected to make sure that there are no duplicates. While "GeoJSON import" and "diligent checking" don't exclude one another, we want to be very careful to avoid the misconception that you could "simply upload" data (without diligent checking). The JOSM editor can open shape files and upload them to OSM. Having said all that, there's been a discussion about the importing of sidewalks just last week on the tagging and talk-us lists. Mapping sidewalks as individual geometries is not a cure-all for pedestrian routing; it solves some problems and creates others. (For example, I'm from Europe so I don't know US regulations but I heard that in some places it is illegal for pedestrians to simply cross a road and in others it's ok. If it is illegal in your area then does your data contain all the legal crossings - or if it is legal then what is the concept for routing engines to allow crossing?) Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
