I'm not sure if this is a bug or behavior to be expected based on how the program works.
After using JOSM to either update the spatial location of a way or create a new way in a .osm file and running osm2pgrouting to create the network, stray lines appear on the new or modified ways. I have recreated this behavior across several datasets.
When I look at the edits online and in JOSM, the added or modified ways show correctly.
screen shot1 - before edit
1) run osmconvert to get .osm file
2) run osm2pgrouting --clean using for_cars config
screen shot2 - after edit
1) run osmconvert to get .osm file
2) edit .osm file with JOSM (ways added, moved)
3) run osm2pgrouting --clean using for_cars config
System: Windows 7 x64
PostgreSQL: 10.5
PostGIS: 2.4.4 r16526
pgRouting: 2.5.2
osm2pgrouting: 2.3.4
note: possibly related to #244 & #183
Hi,
I'm not sure if this is a bug or behavior to be expected based on how the program works.
After using JOSM to either update the spatial location of a way or create a new way in a .osm file and running osm2pgrouting to create the network, stray lines appear on the new or modified ways. I have recreated this behavior across several datasets.
When I look at the edits online and in JOSM, the added or modified ways show correctly.
When I wait to download a new state file with the changes from https://download.geofabrik.de/north-america/us/georgia.html, they show correctly without any stray lines after running osm2pgrouting.
screen shot1 - before edit 1) run osmconvert to get .osm file 2) run osm2pgrouting --clean using for_cars config![greene_county_ga_before_edit](https://user-images.githubusercontent.com/24419571/45704036-2f887b80-bb33-11e8-9764-ce639f6f38c7.png)
screen shot2 - after edit 1) run osmconvert to get .osm file 2) edit .osm file with JOSM (ways added, moved) 3) run osm2pgrouting --clean using for_cars config![greene_county_ga_after_edit](https://user-images.githubusercontent.com/24419571/45704082-4a5af000-bb33-11e8-8fde-018eb80f49c7.png)
System: Windows 7 x64 PostgreSQL: 10.5 PostGIS: 2.4.4 r16526 pgRouting: 2.5.2 osm2pgrouting: 2.3.4 note: possibly related to #244 & #183