search

rl-institut / digiplan

StEmp ABW 2.0 - new version of StEmp ABW tool
https://digiplan.rl-institut.de
GNU Affero General Public License v3.0
1 stars 1 forks source link

Switch to custom base map? #23

Closed 4lm closed 1 year ago

4lm commented 1 year ago

This repo is piggybacking on Djagora's basemap.

Shall we switch to a custom basemap for this project? Or shall we declare the basemap as ours for this and (maybe) future projects?

Remember, we have 50.000 free map loads a month. Right now, we use ~100 map loads a day, ~3000 a month. So I think, our map apps must become much more popular, until we run into capacity problems here.

@henhuy, @nesnoj, what do you think?

nesnoj commented 1 year ago

Hey @4lm, for now keeping the basemap sounds good to me (It'd could need some custom styling which goes in line with the regional resolution though). But I'm also open for good alternatives.

Note: This repo will be released under open source licenses later, so consider not to push any tokens...

4lm commented 1 year ago

It'd could need some custom styling which goes in line with the regional resolution though

The same base map can have different styles: https://github.com/rl-institut-private/digiplan/blob/dev/.envs/.local/.django#L15

But I'm also open for good alternatives.

MapTiler has many offers comparable to MapBox, but also offers map data in different forms and qualities for self hosting (non-commercial is free, commercial costs money): https://data.maptiler.com/downloads/planet/. MapTIler is one of the driving forces behind the Mapbox GL JS fork (MapLibre GL JS) we use in our apps.

The tiles MapTiler offers are based on the OpenMapTIles project - link to org: https://github.com/openmaptiles. So we could even go one step further and create those tiles ourselves. Basically it's a bigger Makefile, wrapped around a postgres database and fed with a sql script for each layer: https://github.com/openmaptiles/openmaptiles. If we also adjust this to our needs (add our areas/layers, data from the oep, etc.) we could truly create something of value for us and others to work with for many projects to come.

Note: This repo will be released under open source licenses later, so consider not to push any tokens...

Too late, the "public" token was already pushed over a year ago: https://github.com/rl-institut-private/digiplan/blob/dev/.envs/.local/.django#L16

But this is no biggy, because we can easily devalue the given token and create a new one the moment we go public.

henhuy commented 1 year ago

The tiles MapTiler offers are based on the OpenMapTIles project - link to org: https://github.com/openmaptiles. So we could even go one step further and create those tiles ourselves. Basically it's a bigger Makefile, wrapped around a postgres database and fed with a sql script for each layer: https://github.com/openmaptiles/openmaptiles. If we also adjust this to our needs (add our areas/layers, data from the oep, etc.) we could truly create something of value for us and others to work with for many projects to come.

For this project I would not change the running tile server, as there is also some django-model-based-filtering in the backend, which is likely hard to adapt with this solution. For static tiles this could be an option (maybe replacing our old tileserver-gl)

4lm commented 1 year ago

Talked to @heyhu. In this project we use the given basemap and create a new styling. Closing.

nesnoj commented 1 year ago

Talked to @heyhu. In this project we use the given basemap and create a new styling. Closing.

Ok. BTW, I think you used the wrong nick to mention @henhuy ;)

4lm commented 1 year ago

BTW, I think you used the wrong nick to mention @henhuy ;)

Haha :laughing: you are right!