I make an edit on a place which can be see on the picture1, i create a test area called iD_test20170104.1 as show on the picture2, but a way occured which point to the place which i built before, then i delete the iD_test20170104.1, but the way still exist. And now i do not know how to restore the map to the original state. It is on my own rails port, and i use iD editor to make the edit, and use osmosis command to produce a changes.osc.gz file, then use osm2pgsql with -append and -e options to generate a expire.list file, finally, i use "cat /data/mod_map/expire.list | /root/src/mod_tile/render_expired -m osmcarto -z 10 -Z 18 -T=10" command to re-renderd the tile, but the error occurs. Is there a possibility that the changes.osc.gz files node id have conflict with the exist nodes causes the error? The changes.osc.gz file can be shown below.
asked 04 Jan '17, 06:05  yuyy edited 10 Jan '17, 10:13  SomeoneElse ♦ |
One Answer:
I think it was caused by the conflict id in the changes.osc.gz file and the tile server database. I installed my own rails port, and when i use the editor to make a changes file, the index id of the node and way are begin at 1, but there has be a node or a way which id is 1 in the tile server database, so when i use osm2pgsql with -append option to import the changes file into the database, the error occurs. And now, what confuses me is that the index id of the nodes and ways are automatically generated by the osmosis command, how can i set them to start at a large index number? answered 10 Jan '17, 11:19 yuyy |
Also is this on osm.org or on your own copy of the rails port (with data loaded)?
It is on my own rails port, and i use iD editor to make the edit, and use osmosis command to produce a changes.osc.gz file, then use osm2pgsql with -append and -e options to generate a expire.list file, finally, i use "cat /data/mod_map/expire.list | /root/src/mod_tile/render_expired -m osmcarto -z 10 -Z 18 -T=10" command to re-renderd the tile, but the error occurs.