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

Use a different hosting service for map tiles #10

Open
willf opened this issue Jan 27, 2025 · 2 comments
Open

Use a different hosting service for map tiles #10

willf opened this issue Jan 27, 2025 · 2 comments

Comments

@willf
Copy link
Collaborator

willf commented Jan 27, 2025

We might want to investigate the use of a third-party hosting service for map tiles in case the current provider stops hosting them, although as long as it continues to work, it makes sense to use them (and the Cloudflare cache).

@ericnost
Copy link
Member

Mapbox https://www.mapbox.com/pricing#tilesets and ArcGIS Online https://doc.arcgis.com/en/arcgis-online/manage-data/publish-vector-tiles.htm may be options though I've actually never used either for this purpose.

@titaniumbones
Copy link
Collaborator

there are actually two pieces to this, I believe:

  • base tile server. The version we are currently serving uses openstreetmaps tiles, whereas the old version used mapbox tiles (with an API key). It would be pretty straightforward to revert back to the mapbox method -- we'd just have to use the production build pipeline and provide a key. This might be necessary if the proejct is successful and starts to see heavy usage.
  • CEJST custom tile server. Currently we just use the department of the interior CDN. We could either copy those directories to our own AWS (or other) location, or alternatively I think both @willf and I have successfully built all the assets using the existing data pipeline. so we could copy the relevant folder (which is just a couple of gigs) to that new location instead. In either case, I think there's an env variable for the base URL for all assets.

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

3 participants