Rounding issue in generated id for /points

[russor]

Describe the bug
For some values of latitude (and presumably, longitude), the returned id fields do not follow the rounding rules, leading to extra requests if the ID is saved for future use.

To Reproduce
I noticed this when fetching https://api.weather.gov/points/47.6553,-122.5354; see for example,

$ curl https://api.weather.gov/points/47.6553,-122.5354 -v 2>&1 | grep -E '/points/|correlation-id'
> GET /points/47.6553,-122.5354 HTTP/2
< x-correlation-id: ab13c615-d0c1-4880-bc81-fb57326179df
    "id": "https://api.weather.gov/points/47.6552999,-122.5354",

$ curl -I "https://api.weather.gov/points/47.6552999,-122.5354"
HTTP/2 301
server: nginx/1.16.1
content-type: application/problem+json
location: /points/47.6553,-122.5354
[...]

Expected behavior
I would expect the id returned to follow rounding rules, so requesting it in the future does not return a redirect.

Environment
shown in curl, also experienced in browser and PHP

Additional context
I would prioritize this pretty low, I don't know that this id is even useful to anyone, but it's there and I noticed it looked weird.