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

Optimize route traces #8

Open
thekaveman opened this issue Feb 22, 2017 · 0 comments
Open

Optimize route traces #8

thekaveman opened this issue Feb 22, 2017 · 0 comments
Assignees

Comments

@thekaveman
Copy link
Contributor

Currently, when a particular route map is viewed on the BBB site, e.g. Route 14, a 1.4mb traces.geojson file is downloaded to draw the route trace. This file contains traces for all routes, each of which is loaded into Google Maps as a hidden layer, and selectively shown for the route in question.

This download can be problematic for mobile customers, especially on slower connections.

We should try to optimize the route trace download similar to how stops are handled, and only request the trace for the route in question.

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