Vector tiles contain much of the same information as the GeoJSON tiles from the soundscape-backend server. This issue is to investigate what would be required to use the vector tiles instead of the soundscape-backend server.
I think that although not totally straightforward, it's not impossible. It may require custom changes to tile generation tools to add intersections (and entrances?) to the max zoom tiles which by default don't always exist in vector mapping tiles.
The reason to do this would be to reduce the amount of infrastructure required to support the app which would reduce the monthly cost. This is discussed here https://scottish-tech-army.github.io/Soundscape-Android/mapping.html, and the cost of running a protomaps server which would provide both UI and tiles for audio has a cost calculator here. If we could make this work, then the ongoing server cost would be very small indeed.
Vector tiles contain much of the same information as the GeoJSON tiles from the soundscape-backend server. This issue is to investigate what would be required to use the vector tiles instead of the
soundscape-backendserver. I think that although not totally straightforward, it's not impossible. It may require custom changes to tile generation tools to add intersections (and entrances?) to the max zoom tiles which by default don't always exist in vector mapping tiles.The reason to do this would be to reduce the amount of infrastructure required to support the app which would reduce the monthly cost. This is discussed here https://scottish-tech-army.github.io/Soundscape-Android/mapping.html, and the cost of running a protomaps server which would provide both UI and tiles for audio has a cost calculator here. If we could make this work, then the ongoing server cost would be very small indeed.