Hi Felix, I think the messages from osmconvert are correct. -324214 is less than -324213, so the nodes are not in the expected order.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Felix Herwegh <mlmm...@herwegh.de> Gesendet: Freitag, 22. November 2024 14:59 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] Dealing with JOSM exports Hi, for some special application I'm parsing gpx-files to osm-files, identical to importing the .gpx into JOSM, convert them to datalayers and finally export to .osm. These files are then processed by splitter to .o5m. I'd like to add a timestamp to the .o5m using "osmconvert --timestamp" next. While that normally works for split-files based on OSM data, for the above files osmconvert allways throws 6 warnings like osmconvert Warning: wrong sequence at node -324213 osmconvert Warning: next object is node -324214 osmconvert Warning: wrong sequence at node -324214 osmconvert Warning: next object is node -324215 osmconvert Warning: wrong sequence at node -324215 osmconvert Warning: next object is node -324216 I guess, osmconvert is expecting ordered increasing positive IDs only. Iirc the decreasing negative IDs are correct here nevertheless, implemented long ago to indicate dealing with non OSM objects. mkgmap seems to work perfectly fine on such split-files. Did I miss any means to avoid these warnings and have the timestamp added other than converting the IDs to positive? Thanks //Felix _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
