I'm setting up a server to replicate a small subset of the OSM database (amenities in the United Kingdom tagged as "place of worship") which will be stored on a cartoDB instance (PostGIS database) and updated on an hourly basis. From what I can tell current best practice for this is to use osmosis to filter out a subset of the planet.osm databse. This all seems straight-forward and well documented, and this brings me to my question. The current data in OSM is pretty messy and incomplete, and I have already generated a nearly complete set of data. So I'd like to merge in a bulk changeset on these POIs (around 25,000 points) to OSM and then continue to push smaller changesets as metadata is updated on the local server periodically as well. Can someone recommend the best practice for push rather than pull interaction with OSM?

asked 11 Jan '17, 18:08

kidwellj's gravatar image

kidwellj
26112
accept rate: 0%


JOSM has the option of reading shape files and converting them to OSM data, and there's also a number of shp2osm-style programs around, but none of these techniques actually allows updating existing objects. Doing so will require, among other things, conflict resolution for cases where the object has been edited in the mean time. You might want to check out the codebase of "POSM" here https://github.com/AmericanRedCross/posm which has the aim of allowing offline edits and loading them into OSM later; perhaps there's something you can re-use.

Having said that: You write that you have "generated" a nearly complete set of data. If this involves (a) the automatic conversion/use of third-party data sources and/or (b) the query-based or rule-based editing of OSM objects (e.g. search+replace operations on names, geometric operations like merging tags from nodes to ways or vice versa, removal of duplicates, etc.etc.), then you must follow the appropriate policies for imports and/or mechanical edits. The most important point of both these policies is that you must discuss your import/edit with the community before you act, and you must explain what rules you've applied to what data. If you simply stuff the results of some computation into OSM then your edits will be reverted. The same is true if you plan to continually apply automatic edits - seek community agreement before you act. The reason we have these policies is that a lot can go wrong, even if people think they know what they're doing.

permanent link

answered 11 Jan '17, 18:56

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
69.9k806321095
accept rate: 24%

Thanks for pointing this out. I've been reading the policy (http://wiki.openstreetmap.org/wiki/Import/Guidelines) in-depth and plan definitely to work through the human/consensus aspect before flipping the switch. I've already begun conversations regarding tagging etc. and plan to get input and consensus along the way, with a wiki page for the import process in draft. Just out of curiosity, have you worked with osmsync (http://wiki.openstreetmap.org/wiki/Osmsync)? And hadn't thought of POSM. I'll add that to my list!

(11 Jan '17, 19:20) kidwellj
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×216
×158
×120

question asked: 11 Jan '17, 18:08

question was seen: 1,082 times

last updated: 11 Jan '17, 19:23

powered by OSQA