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

Automated way to generate config.toml #262

Open
MohammedAlsayed opened this issue Jan 14, 2018 · 3 comments
Open

Automated way to generate config.toml #262

MohammedAlsayed opened this issue Jan 14, 2018 · 3 comments

Comments

@MohammedAlsayed
Copy link

MohammedAlsayed commented Jan 14, 2018

Hi,

I'm looking for a config.toml where it's layer names matches with osm-liberity.json layer names
The osm-liberity style can be found here: https://maputnik.github.io/editor/#0.8/-0/0.

Also, is there a matching style with the config.toml in the tegola-osm (meaning (the layer names matches in both files) example ?

@ARolek
Copy link
Member

ARolek commented Jan 15, 2018

@MohammedAlsayed tegola does not currently have a way to generate a config file from a data source. We have considered this idea to help get up and running quicker but have not yet implemented it. Even if we did automate the config generation you would need to do subsequent refinement to match the properties the client side would be expecting.

This being said, the config should not be too difficult to implement. If you need some guidance I'm happy to help with any hurdles you encounter. If you do setup the config it would be great if you released it for others to use.

@PetersonGIS
Copy link
Contributor

An auto-generated config would help when the database has 20+ tables. It could get newbies started more easily as well. They can start with the auto-generated config and then refine it as necessary. I think this is a great idea if it is possible.

@erictheise
Copy link
Member

I've been working on and using a Python tool that creates providers and maps layers for the tegola config based on the imposm3 import. I'm also planning to implement a reconcile action that'll flag imports that don't appear in the tegola config and vice versa. Seems quite likely this could be modified to ingest a style and export a reasonable starting point for a tegola config.

@ARolek ARolek added this to the v0.7.0 milestone Feb 13, 2018
@ARolek ARolek modified the milestones: v0.7.0, v0.8.0 Aug 2, 2018
@ARolek ARolek modified the milestones: v0.8.0, v0.9.0 Oct 24, 2018
@ARolek ARolek removed this from the v0.9.0 milestone Apr 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants