Closed kyooryoo closed 4 months ago
I would think that that should be documented in the traffic-api service you linked, not the in (generic) library that supports every possible precision?
Closing, as I mentioned this should be documented in the service that is using this format to expose same data.
I am Ling Jiang, the Platform Support Engineer in HERE. This feedback is from the support case CS0092990. The customer got confused as they cannot get the same encoded value from example: https://developer.here.com/documentation/traffic-api/dev_guide/topics/concepts/geospatial-filters.html Please update the README.md section by adding the precision=6 or at least remind it. As mentioned in the official document https://pypi.org/project/flexpolyline/
For your reference: