-
Notifications
You must be signed in to change notification settings - Fork 45
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
Question about rastering the osm #17
Comments
Thank you for reporting an issue, can you please provide a minimal code example that reproduces this? |
Thanks for your helping! I have found out the real problem is that when we query elements from the bounding box. It gerneates lines/points outisde of the boundingbox. Here is the minimal code to reproduce the error. (All hard code numbers and parameters are from avigon.osm and related json) from ..utils.geo import BoundaryBox, Projection osm = OSMData.from_file('./avigon.osm') It will get something like [-1395.64272195, -1090.34845149], |
This is working as intended. The map index uses an R-tree to efficiently retrieve elements based on their bounding box: OrienterNet/maploc/osm/tiling.py Line 25 in 71e89eb
It returns any lines and polygons whose bounding box intersect with the query. OpenCV drawing functions support elements that are partially outside the canvas: OrienterNet/maploc/osm/raster.py Lines 45 to 53 in 71e89eb
|
Thx for producing such great work!
I have met some questions about render raster mask function for osm data. During the render_raster_mask function, I find out multipoints(more than 10) in xy space are ploted as two or zero points after the cv2.polylines function.
The text was updated successfully, but these errors were encountered: