ideas for new initial config parameters for colouring-core

[traveller195]

Hello,
I hope there is not already a similar discussion existing.
Here, we could collect ideas for further parameters, which could be configured in the beginning of setting up a new Colouring Cities platform from colouring-core.
@matkoniecz @mdsimpson42 @tomalrussell @polly64

I refer to this:
https://github.com/colouring-cities/colouring-core/blob/master/docs/configuring-colouring-cities.md

and the following config file:

app/src/cc-config.ts
app/src/cc-config.json

First idea for new initial parameter (to find it easier in the beginning):

extent/ bbox for tile renderer:
see
colouring-cities/colouring-dresden@9b73c3b

https://github.com/colouring-cities/colouring-core/blob/master/app/src/tiles/rendererDefinition.ts#L26

[matkoniecz]

It may make sense to simply create issues for each parameter. "extent/ bbox for tile renderer:" is definitely a good fit for a parameter.

[traveller195]

further idea for parameter: (and yes, I/ we can also create issues for that)

URL for city base map layer/ service:

https://github.com/colouring-cities/colouring-core/blob/master/app/src/frontend/map/layers/city-base-map-layer.tsx#L26

as default (for city not in the UK), OpenStreetMap tile service could fit better to start with:

const baseUrl = `http://a.tile.openstreetmap.org/{z}/{x}/{y}.png`;

problem for the usage as an initial parameter could be, that partly there is the need of an API KEY for OS service, which shoudl be then a second parameter? or maybe just provide a comment where to change the base service, without including it to the config file?