Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to update the README.md of this Python section #65

Closed
kyooryoo opened this issue Apr 25, 2023 · 2 comments
Closed

Request to update the README.md of this Python section #65

kyooryoo opened this issue Apr 25, 2023 · 2 comments

Comments

@kyooryoo
Copy link

kyooryoo commented Apr 25, 2023

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:

print(fp.encode(example)) # this might be what the customer got by default.
BF81zgKsl1xCoUs7DojBrU0RgxC3N--C

print(fp.encode(example, precision=6)) # this is what we provided in our example.
BG-6kmkDw1zwZqqG6xmBsgL5rGmwFgqZ_oEw1d

@VeaaC
Copy link
Contributor

VeaaC commented Apr 25, 2023

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?

@VeaaC
Copy link
Contributor

VeaaC commented Jun 6, 2024

Closing, as I mentioned this should be documented in the service that is using this format to expose same data.

@VeaaC VeaaC closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants