Open barbeau opened 7 years ago
Looks like it might be a race condition waiting for the route geometries to load from the server.. It also throws a javascript error at:
because the vehicles weren't defined - although they do eventually load it seems since those refresh every 5 seconds. But the geometries are only loaded on initialize: and so, somehow they don't seem to load or be assigned to the correct (this) context..
Thanks @jmfield2!
From @liquidsunshine, regarding priority of some of these related issues for using the app to show information in the CUTR lobby on a TV display:
Here’s how I would prioritize them, based on CUTR’s needs:
- https://github.com/CUTR-at-USF/usf-mobullity/issues/401 (a bug)
- https://github.com/CUTR-at-USF/usf-mobullity/issues/403 (allows us to automatically center on CUTR)
- https://github.com/CUTR-at-USF/usf-mobullity/issues/404 (allows us to automatically bypass popup)
- https://github.com/CUTR-at-USF/usf-mobullity/issues/405 (offers a better view of CUTR)
- https://github.com/CUTR-at-USF/usf-mobullity/issues/402 (possibly improves refresh performance)
Summary:
If you go to: https://maps.usf.edu/#layers/usf_A,usf_B,usf_C,usf_D,usf_E,usf_F
...you should see all USF buses and route polylines on the map.
For some reason, the polylines are currently missing:
It should look like:
Steps to reproduce:
Go to https://maps.usf.edu/#layers/usf_A,usf_B,usf_C,usf_D,usf_E,usf_F
Expected behavior:
You should see route polylines on the map
Observed behavior:
No route polylines are shown
Workaround - go to https://maps.usf.edu/#layers/ and manually check the layers
Platform:
Windows 7 Enterprise w/ Chrome Version 57.0.2987.133 (64-bit)