-
Notifications
You must be signed in to change notification settings - Fork 112
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
List way membership of points #39
Comments
Hmm. Wouldn't it be better to perform this kind of analysis on the OSM data before converting it to geojson? Then, you could simply have separate information like "door with id x belongs to building with id y" alongside the geojson geometries… |
Well, let's consider it reversed: if you consider that a node may have the list of ways it belongs to, the same way that a feature knows to which relations it belongs, would it be more interesting to implement ? The goal is to avoid two-time parsing for performance reasons. |
Ok, that does indeed sound like a useful information to have! |
Nice, thank you for this great library and your openness to new functionalities ;) |
Hello,
I think it could be interesting to keep track of the nodes identifiers in OSM way-based features, for example by adding an array of nodes ID in feature properties. This would allow some advanced processing (like finding a door direction along a wall). Do you think it can be implemented ?
The text was updated successfully, but these errors were encountered: