In OTHR's maps, there are places where multiple fixed route city buses run on the same portion of road. When these agencies don't submit their systems to Google Transit, I generally supply the GPS tracks for them.
Lets say that instead of a airplane, or interstate bus, they took a magic teleporter instead and it dropped them in some Canton neighborhood and it made them dizzy. After they regain their senses, they take out their GPS with my transit tracks already loaded in and, start walking and see that they're approaching a line.
But the road that it's on actually has 4 bus lines. On the map, the reader can't see it because they're stacked on top of each other (Google Maps Engine, what I wrote them with took the exact same path over the road). And even though the users "Track Manager" in their GPS is ordered nearest to farthest, they might not put 2 & 2 together and realize that they're all on the same stretch of the road that they're approaching because the distance numbers on the device are awfully small?
So, when I'm drawing these tracks now, I'm taking concurrent portions and I'm just drawing one track. It's pretty much block by block in these cases. But the title which will appear in normal font on their Track Manager will read every bus line that that's routed over it.
For those of you who use OTHR, converting the existing fixed route tracks to suit this is going to take a couple years.
No comments:
Post a Comment