-
Notifications
You must be signed in to change notification settings - Fork 51
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
Add BBox Option to Heatmap Poster #7
Comments
hi, i was looking for the same feature as well ;) (min_x, min_y, max_x, max_y) = utils.compute_bounds_xy(xy_polylines) |
Shall all the statistics on the poster's bottom be calculated based on all tracks or only on filtered tracks? @lefty01 I guess track_loader.py::__filter_tracks(self, tracks) is the right place and you might need something similar to utils.py::compute_bounds_xy(polylines) for lat/lng. |
hi I pushed my works I had so far to my fork and submitted a pull request ... you can review the changes and I would be glad to hear any feedback if that makes sense... so maybe I give your idea with filtering all tracks beforehand and see if they match the given boundaries. cheers |
@lefty01 Nope, my work on the background map does use all tracks. |
hi, now had some more time to look into this ... as discussed in the old pull-request comment: #11 (comment) |
add options |
Add bbox option (
--bbox COORDS1;COORDS2
) to restrict the extent of the heatmap poster.Rationale: if there are some tracks in your collection that are far away from the other tracks (e.g. runs during vacation), the heatmap poster becomes useless.
The text was updated successfully, but these errors were encountered: