Skip to content
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

Segfault when trying to access .nodes of relation #51

Closed
osmuser63783 opened this issue Feb 25, 2024 · 3 comments
Closed

Segfault when trying to access .nodes of relation #51

osmuser63783 opened this issue Feb 25, 2024 · 3 comments

Comments

@osmuser63783
Copy link

... or at least that's what I think is going on.

traffic_sign_nodes_on_non_highways = set()
for h in planet_240219("aw[!highway]"):
    print(h)
    traffic_sign_nodes_on_non_highways.update(h.nodes("n[traffic_sign]"))
... 
way/120993860
way/120992621
way/120993742
way/986571987
way/120992739
way/120993191
relation/1655222
Segmentation fault (core dumped)

That's what I get for forgetting to do .ways.

It would be nice to fail more gracefully :-) (not sure if the method should return an empty set in case of an area, or all the nodes that define the multipolygon...)

@clarisma
Copy link
Owner

clarisma commented Feb 26, 2024

FYI -- your query aw[!highway] may also be effected by this bug: #52 ; fix coming soon.

However, unable to reproduce the segfault. Tried in both Ubunu 22.04 and Windows 10, with planet-wide GOLs built with GOL Tool pre and post v0.1.9.

Does the segfault appear consistently at relation/1655222? Does the query fail if applied to other relations?

@clarisma
Copy link
Owner

Regarding nodes of relations, please see #54

@osmuser63783
Copy link
Author

I have not been able to reproduce this recently so I am closing this issue. Sorry for the false positive!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants