GeoStream: Custom Traffic Layer Link Attributes
1 to 3 of 3
-
- CommentAuthorDavid K
- CommentTimeFeb 19th 2012
I am using a custom traffic source and would like to be able for my custom traffic layer .cam file to be able to respond to an attribute on the link in addition to the speed. For example, a traffic link might represent historical information, real time information, or even predicted information. When GeoStream requests the speed it would be nice to be able to pass back an additional attribute that would provide further information on how to render the link. Historical information might be rendered with right hash fill, predicted information might be rendered with dot fill, and real time information rendered solid fill. Please let me know if this is possible in the latest version of GeoBase/GeoStream custom traffic rendering. -
- CommentAuthorAlex H
- CommentTimeFeb 19th 2012
Hi David,
Our Traffic Renderers, on both JS and .NET, work from TrafficInfo objects, which only hold Speed information. As such, they have no way to adjust rendering based on other properties/tags in your traffic source.
What would work is to split your traffic source into three separate sources; historical, real-time and predicted. You could then render each source separately on the map.
If you're using GeoStream, this would result in a lot of different layers to render, which may result in unacceptable network traffic. A workaround for this would be to create your own tile rendering class using GeoStreamRenderer. This could wrap three instances of the .NET TrafficRenderer and render all three at once, returning only one set of overlay tiles to your GeoStream client rather than three.
Some useful documentation links:
Rendering Your Own Tiles tutorial
TrafficRenderer Class (.NET)
If you require further help on this, drop us an e-mail and we'll see what we can do help: gbsupport@telogis.com
Thanks,
Alex -
- CommentAuthorDavid K
- CommentTimeFeb 21st 2012
Thanks. I'll take a look at the tile rendering resources you provided.
1 to 3 of 3
