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

Implement style.json resolution strategy a when handling the stable style url #439

Closed
1 task
achou11 opened this issue Jan 18, 2024 · 0 comments · Fixed by #459
Closed
1 task

Implement style.json resolution strategy a when handling the stable style url #439

achou11 opened this issue Jan 18, 2024 · 0 comments · Fixed by #459
Assignees
Labels
mvp Requirement for MVP

Comments

@achou11
Copy link
Member

achou11 commented Jan 18, 2024

Description

A frontend client is provided a single endpoint to use for retrieving a style.json definition (see #438). This endpoint should be handled by the backend, which performs the following resolution strategy to determine the style.json payload that's returned as the response:

  1. Check if there's a offline static map with the style id of default (or whatever name we decide on). In practice, this means that there's a file that exists on the filesystem at __ROOT__/default/style.json, where __ROOT__ is a provided directory where static custom maps are stored. If it exists, serve the style.json content as the response

  2. if internet access is available, proxy a default online style of our choosing (e.g. using a mapbox style that requires our account's public access token)

  3. if internet access is not available, serve an fallback map style that uses statically served local geojson files (e.g. https://github.com/digidem/mapeo-offline-map)

Tasks

@achou11 achou11 self-assigned this Jan 18, 2024
@achou11 achou11 changed the title Implement style.json resolution strategy a when handling the canonical style url Implement style.json resolution strategy a when handling the stable style url Jan 18, 2024
@EvanHahn EvanHahn assigned EvanHahn and unassigned EvanHahn Jan 29, 2024
@ximenabb ximenabb added the mvp Requirement for MVP label Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mvp Requirement for MVP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants