You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2020. It is now read-only.
I have one problem which is that when I run the OsmBboxFilter as a script it sets the bounds of the new file to 0,0,0,0 which obviously is not correct.
BR
Henrik
The text was updated successfully, but these errors were encountered:
Hi, thanks for pointing this out. I remember that this is a blind spot in the library: I wasn't sure about the best way to handle the bounds for the output, especially in situations where the input file already specifies bounds and apparently just postponed to make a decision. The question is whether the specified filtering bounding box is just stored in the output as the bounds independent of the input file's bounds or whether the tool calculates the intersection of both bounding boxes and stores the result. I now implemented a fix (826008e) that does the latter.
I'm archiving this repository because this module has been merged into the osm4j master repository. Please re-open the issue there if you want to continue the discussion.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi
Thanks for a good set of tools and libraries!
I have one problem which is that when I run the OsmBboxFilter as a script it sets the bounds of the new file to 0,0,0,0 which obviously is not correct.
BR
Henrik
The text was updated successfully, but these errors were encountered: