Dear all
I’m seeking guidance on how to responsibly use the go.Choroplethmapbox figure. Can we hit it like crazy on a public dash website or is that abusing the free API? Please advise on whether this is open season or if there is an appropriate approach.
Background
I’ve been playing around with a dash webapp using the plotly.graph_objects.Choroplethmapbox figure which DOES NOT need an API token. I really only need simple tile based maps that come available without an API token requirement in the go.Choroplethmapbox figure (lovely). Presumably there are still mapbox API keys and they are managed behind the scenes by plotly in providing this service?
I don’t really understand how it all works and I don’t want to abuse this free service, so can you please advise:
-
Are there limits on using the Mapbox token-free-API go.Choroplethmapbox fig?? (i.e. for a public/enterprise website)
-
If so, please advise how best to manage this.
-
If not, assume I can hit go.Choroplethmapbox as hard as I want without any guilt!
Cheers all
Dan
https://plotly.com/python-api-reference/generated/plotly.graph_objects.Choroplethmapbox.html
Hi @dan_baker
I found this on the Mapbox website, under the Rate Limits section. Does that answer your question?
| API |
Default coordinates per request |
Default requests per minute |
| Vector Tiles API |
N/A |
100,000 requests per minute |
| Raster Tiles API |
N/A |
100,000 requests per minute |
| Static Images API |
N/A |
1,200 requests per minute |
| Static Tiles API |
N/A |
5,000 requests per minute |
| Styles API |
N/A |
2,000 requests per minute |
| Tilequery API |
N/A |
600 requests per minute |
| Uploads API |
N/A |
30 requests per minute |
|
Mapbox Tiling Service (Read) |
N/A |
100,000 requests per minute |
|
Mapbox Tiling Service (Write) |
N/A |
100 requests per minute |
|
Mapbox Tiling Service (Publish) |
N/A |
2 requests per minute |
| Datasets API |
|
|
| (Read) |
N/A |
480 requests per minute |
| Datasets API |
|
|
| (Write) |
N/A |
40 requests per minute |
| Directions API |
|
|
( driving , walking , and cycling profiles) |
25 coordinates per request |
300 requests per minute |
| Directions API |
|
|
( driving-traffic profile) |
3 coordinates per request |
300 requests per minute |
| Isochrone API |
1 coordinate per request |
300 requests per minute |
| Map Matching API |
100 coordinates per request |
300 requests per minute |
| Matrix API |
|
|
( driving , walking , and cycling profiles) |
25 coordinates per request |
60 requests per minute |
| Matrix API |
|
|
( driving-traffic profile) |
10 coordinates per request |
30 requests per minute |
| Optimization API |
12 coordinates per request |
300 requests per minute |
| Geocoding API |
N/A |
600 requests per minute |
| Tokens API |
N/A |
100 requests per minute |
Thanks Adam. Yes I guess that means it’s open season. I wonder which of these API’s the chororplethmapbox uses? Presumably it’s the static tiles API which is up to 5000 requests per minute which is probably fine for an enterprise site!
I wonder if any of the Plotly admin’s can clarify??
Dan
See https://plotly.com/python/mapbox-layers/
The layers that don’t use a mapbox token don’t use the mapbox tile sets, they use tile sets from other services with their own T&C’s and no api key requires.