I use the VRM for monitoring of systems on a ship, as well as visualisation of the ship’s track. This all worked perfectly for a number of years.
A year ago, we encountered the CORS issue with the change in the response to the API call. I worked around this through the implementation of a web proxy. It would still be nice if the CORS response could be fixed.
However, at some point I started encountering a “too many requests” response to the “gps-download” API call. The “installations” API continues works perfectly fine. My web page is only requesting an update every 30s, so I would doubt that I should be triggering any rate control. By default I retrieve 24 hours of tracking points.
I see that other folk have reported similar issues. Is the new rate limiting a little too conservative? Or perhaps something specific in the configuration of the “gps-download” API call?
A GX updates once every 60seconds minimum.
You will definitely be triggering a rate control in any case. VRM is alot busier these days. There are variable limits on different types of data.
Thanks! I will definitely reduce the polling interval to 60s.
I had not found the thread you referenced…
“Might it be that the system is being asked to return a broad/large range of data with a query, which could trigger limiting, where a specific/single topic would not.”
That could explain why I hit it was 24 hours of gps-download data, but not with the installations endpoint.
I’ve switched the page to only request the historical track on demand (button press), rather than automatically on page load and every 60s. Hopefully that helps.
Would be open to a subscription fee to remove the CORS limitation and rate limiting…
