|
Heyo, Software of my company is using osm.pbf as input to a tool to calculate a network analysis. The goal is to calculate difference in accessibility if network nodes/edges are removed or added from the openstreetmap network. Therefore we want to be able to locally edit .osm files and export it back to .osm.pbf files. Workflow: We downloaded .osm.pbf files from Geofabrik, selected highways only with FME, selected spatial region, converted to .osm and then we want to remove one node/edge. This previous question mentioned using JOSM to locally edit osm files. However JOSM only accepts .osm files with usernames and does not accept latest GDPR abiding osm files from Geofabrik. When giving JOSM files without user data, it throws error: Could not read file 'monaco.osm'. Error is: Illegal value for attribute 'changeset'. Got 0. (At line 4, column 114). What is the best way to locally edit OSM files whilst abiding by GDPR, keeping network relations intact and exporting to osm.pbf? Would aprreciate your help. We are kinda stuck :/ |
|
This was reported as a bug in JOSM on July 19, and fixed the next day. Any JOSM with a version number of at least 14038 should be able to open GDPR-abiding .OSM files successfully. You can either download the latest development version of JOSM now, or wait until the next "tested" version is released. ... the next "tested" version very likely will be released in a few days. The schedule is about each month beginning. However, the "latest" dev version usually also is fine to work with.
(27 Jul '18, 21:43)
aseerel4c26 ♦
Thanks for your answers. Could have found that maybe myself, but good to know there is a fix
(29 Jul '18, 22:10)
Davmatic
1
@Davmatic: the new "tested" version is released, you can update to it and try again.
(29 Jul '18, 22:34)
aseerel4c26 ♦
1
Downloaded latest JOSM version. Version 14066 works for me, I can open .osm files that are GDPR abiding
(30 Jul '18, 07:17)
Davmatic
Also you can 'fake' the user_id and other metadata using osmconvert.
(30 Jul '18, 09:45)
SK53 ♦
|
