-
-
Notifications
You must be signed in to change notification settings - Fork 19
enable reading of pbfs with node location for ways #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
Comments
Do you know if they are used in any of the official pbf files? If that is the case, it is fine to add it, but I'm pretty sure that it will be necessary to add more code to read and manage it properly (ex. They are deltas, so it's necessary to calculate the real value). FYI: @angelcerveraroldan |
I don't think there are official pbfs that already have geometry, but with osmium you can add it. The lat/lon is present in the pbf format https://wiki.openstreetmap.org/wiki/PBF_Format. I do have more code on a branch, and will ask for a PR. |
Feel free to create the PR. Could you find a small pbf with this data as example and add it into the testing? |
I've added Monaco with geometry and added some test cases |
Forget what I said about Feroe Islands. Monaco is the one used for testing, so good. |
I just added way node location on the Monaco file from the repo. Should be exactly the same + lay/long |
@sergiupantiru Thanks for the PR. Give me few days to find free time to do the code review. |
Hello,
I've looked into adding lat/long support for Ways. I know that osmium can add location on ways and that some other tools can read it. This would allow you to create the WKT of the way without too much headache.
I've added the lat/lon, the same as the osmformat.proto
In the OsmSqlEtity I've added a new schema for way.nodes
Before I make a PR I wanted to know your opinion if this would be acceptable.
Thanks in advance
The text was updated successfully, but these errors were encountered: