You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Waze and Trafficcast needing real, valid street and lat/long information, we should make these feeds conditional based on whether the installation has configured an appropriate Address Service.
The Address Service needs to be able to handle all the validation and information calls inRoads will make in order to check the info for the streets a user chooses.
Without the Address Service I'm not sure it even makes sense to designate each of the street segments individually, as required by Waze and Trafficcast.
The text was updated successfully, but these errors were encountered:
With Waze and Trafficcast needing real, valid street and lat/long information, we should make these feeds conditional based on whether the installation has configured an appropriate Address Service.
The Address Service needs to be able to handle all the validation and information calls inRoads will make in order to check the info for the streets a user chooses.
Without the Address Service I'm not sure it even makes sense to designate each of the street segments individually, as required by Waze and Trafficcast.
The text was updated successfully, but these errors were encountered: