You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After importing an .osm file I discovered that some road links are missing compared to the original OSM data. I found #114 and thought that might be the problem, but decided to try a simplified mapconfig.xml and the import completed as expected.
As far as I can tell, osm2pgrouting has trouble with features where multiple tags match the types defined in mapconfig.xml.
An example osm_id is 46226421. There are matching tags for highway and cycleway.
To test this, I imported once with the default mapconfig.xml file and once with a modified config file where I removed the "cycleway" class. When I import with the default config file there are no links for osm_id 46226421, when imported with the modified config file the road segments are present.
The text was updated successfully, but these errors were encountered:
Some fixes were done on develop branch some time ago by @PanlerAvide (see #130)
and he also added a map config for bycycles
maybe you can try out develop branch.
After importing an .osm file I discovered that some road links are missing compared to the original OSM data. I found #114 and thought that might be the problem, but decided to try a simplified mapconfig.xml and the import completed as expected.
As far as I can tell, osm2pgrouting has trouble with features where multiple tags match the types defined in mapconfig.xml.
An example osm_id is 46226421. There are matching tags for highway and cycleway.
To test this, I imported once with the default mapconfig.xml file and once with a modified config file where I removed the "cycleway" class. When I import with the default config file there are no links for osm_id 46226421, when imported with the modified config file the road segments are present.
The text was updated successfully, but these errors were encountered: