Centralize the pygeoapi configuration file

[jvanulde]

Right now it's living in the OpenDRR/pygeoapi repository as well as here. One approach to consider is to have the canonical version in OpenDRR/pygeoapi and generate one in this repository when the stack is built (e.g.: in add_data.sh).

Update (2021-06-04): PR #110 represents Joost's earlier work towards this goal. He remarked: "I am not convinced that this will be the way we generate the configuration in the future but let's at least bring it in so that we don't lose it in some obscure branch."

See also:

• 93

• 107

Ideas:

• start pygeoapi with a baseline configuration (e.g. no data), then add data as the stack build progresses via the generate configuration script (Joost)
• wait until ES is populated then run the configuration script and start the container (Anthony)

[jvanulde]

Now that we are deploying on Docker, we don't need to have any customizations that shouldn't be in the community version. So once we move the translations over to the community version we can probably remove the dependency on our own build.