-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Many ways are missing after import #269
Comments
Hi @Doev , Could you specify what osm2pgrouting version you are using? Could you copy/paste here exact command you are running? What xml config are you using? Thanks, |
Hello, "This is osm2pgrouting Version 2.3.6" ... Ubuntu 20.04 Repo The OSM-File is complete, I do a test import with osm2psql. I use the default config.
|
~/osm$ osmconvert rheinland-pfalz-latest.osm.pbf > rheinland-pfalz-latest.osm |
|
Hi @Doev , I've downloaded raw OSM file using Overpass API and it seems all Ok in this area of Koblenz. See screenshot: Could you test with this file if it works for you? Or you can download using Overpass API. |
Thank you. I will take a look to the Overpass API, so far I haven't worked with it. BTW: How is your background map called? |
I imported the planet-osm file for germany with osmosis to postgresl. I deleted all nodes/ways that I don't need. I exported the data with osmosis and create a new osm-file. I imported the file with osm2pgrouting. Until now, I didn't find any missing ways. Everything seems ok. |
I am encountering the same issue. I also tried to use |
I have the same problem. |
I am still looking for the reason. way id="945765463" |
imho: |
The data was loaded without errors ERROR: relation "__ways********" does not exist. |
When I compare the result with original osm-data after a import, I can see that there are many ways are nissing.
The screenshot shows a random area of the map. Green are the osm ways with the tag "residential" and blue is what was imported by osm2pgrouting.
The text was updated successfully, but these errors were encountered: