Inquiry
Hello
BeNomad is currently developing a mapping service (geocoding, routing, etc.) for the company DDS Wireless which includes support of NYCT DOT traffic data flow.
We have an issue with the decoding of the polyline geometries.
Below are 2 examples of truncated polylines in the NYCT Json traffic file. There are many other cases of truncated geometry.
Can this be solved one way or the other from our side (like a parameter in the request we do not know about)?
,{"id":"382","speed":"0.00","travel_time":"0","status":"-101","data_as_of":"2020-01-23T10:43:12.000","link_points":"40.63089,-74.14569 40.6298,-74.14569 40.62883,-74.14556 40.62805,-74.145451 40.6272105,-74.14546 40.62642,-74.1456 40.6255106,-74.14595 40.6247904,-74.14614 40.6241404,-74.146441 40.6234004,-74.146791 40.6226205,-74.14725 40.6217004,-74.147961 40.61916,-7","encoded_poly_line":"av~vFpqpcMxE?`EYzCUfD@\\\\|CZtDdAnCd@`Cz@rCdAzCzAvDlCzNlNfEfEbChBhD~AjJnBnVzDtA]\\\\|@cBD_Bq@qAaBD"}
,{"id":"259","speed":"13.04","travel_time":"310","status":"0","data_as_of":"2020-01-23T10:43:12.000","link_points":"40.6756,-74.841 40.67643,-74.001241 40.6772405,-74.001741 40.6783605,-74.002531 40.67925,-74.00331 40.6795705,-74.00341 40.68001,-74.00332 40.6805806,-74.003031 40.6814704,-74.0026 40.68522,-74.76 40.6872004,-73.999811 40.6892206,-73.99885 40.68972,-73.99","encoded_poly_line":"omgwFfhtbMeDnAaDbB_F\\\\|CqDzC_ARwAQqBy@qDuAmVoJkK}DsK_EcBc@yBAuBb@yBt@"}
Assigned Agencys Response
Hi,
Thank you for your inquiry. This has been forwarded to the appropriate department for further review and will provide a response.
For additional information on the Real Time Traffic Speed Data, please refer to the metadata_trafficspeeds.pdf document under the Attachments section.
DOT Traffic Speeds NBE: https://data.cityofnewyork.us/Transportation/DOT-Traffic-Speeds-NBE/i4gi-tjb9
Thank you,
- NYCDOT Open Data Team