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. Or maybe there is a geojson to xml converter or something. The imports will be in chunks, so 2,000 features at a time or something. Is this not the case? Is there not an 'import' method using one of the desktop editors? If not then could you point me in the direction of the actual import process. All the other communication stuff I have no problem with.
Overall, considering I could probably map these in a few days directly into OSM, this while process seems a bit absurd. If we get another intern I may have them do just that, though it may take them a bit longer. The problem is we cannot use the direct OSM iD mapping as our only solution due to the license. All of the data we create must be in the public domain - so hence creating it ourselves outside OSM then doing the import. However I didnt realize the import process would be so complicated. But once I figure all this out, when I am ready to import another city's sidewalks, do I have to do all this stuff again, or can I just use this same wiki/communication/procedure, etc for the remainder of our cities once they are complete? Thanks Malcolm Meyer Transportation Planning Coordinator Ohio Valley Regional Development Commission (740) 947-2853 [email protected] On Fri, Aug 12, 2016 at 8:09 PM -0400, "Greg Troxel" <[email protected]<mailto:[email protected]>> wrote: Malcolm Meyer <[email protected]> writes: > Basically we will follow the sidewalk proposal outlined here - > http://wiki.openstreetmap.org/wiki/Proposed_features/sidewalk_schema > > For example - > > highway = footway, footway = sidewalk; > highway = crossing, crossing = uncontrolled > > We collected pedestrian signals so for those we would use "crossing = > traffic_signals". > We also collected curb ramp information, so for those we would use > "kerb = flush". How to extract those as points, then merge those > points back to the nodes of the crossings, that is something I will > have to look into. > > I am looking for specific guidance for this process, more than what is > outlined in the wiki. For anyone with prior experience on importing > please email me directly. I am basically pro-import, but my advice is that importing is almost certainly harder than you think. First, publish your raw data in the native form with a clear statement of PDness. By publish, I mean so that any random mapper can download and use it. Announce it on talk-us. PUt a link in your state's wiki page. Publish code to transform the raw datato OSM format. Comment that heavily to describe what you are doing for tags and why. Publish code to take that and the actual OSM database and generate .osc files or some other way to get exactly what an import would do. Note that at this point, you can render your own osm+your_data maps, without importing, and without needing permission. Find the mappers in your state. Meet them in person. Ask them for help. When doing the above, ask for help if anything isn't obvious. Then, return to thinking about the actual import. (Based on helping with a building import in Mass, where many of us have met each other in person, and some merely have been emailing for years.) _______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
