Traffic Volume API - known issues

Thank you to all who have provided feedback on the Traffic Volume API. Based on our investigations, the issue doesn’t stem from the API, rather the backend data that the API reads from.

What we’ve identified is that the counter configuration details (i.e. location / lat / long etc) have changed resulting with invalid results. As such, as part of the data refresh/validation process, they have been removed.

Unfortunately because of the COVID 19 situation, we haven’t been able to allocate the resources to resolve this issue. We hope to resolve this in the near future, and will update the community once it has been done.