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

Ignore a particular shp file #424

Open
hayatsingh-geospoc opened this issue Dec 22, 2022 · 2 comments
Open

Ignore a particular shp file #424

hayatsingh-geospoc opened this issue Dec 22, 2022 · 2 comments

Comments

@hayatsingh-geospoc
Copy link

hayatsingh-geospoc commented Dec 22, 2022

How can I ignore a particular shp file from my source directory in CLI while generating mbtiles so i can use my desired shp file ?Please repy

@phanecak-maptiler
Copy link
Contributor

AFAIK, I might be wrong):

In case of OpenMapTile schema it is not possible (yet) to skip certain shp files. But you can replace them with some "empty ones" and switch to them (via file name or URL) with configuration options, command line parameters or environment variables, see for example:

https://github.com/openmaptiles/planetiler-openmaptiles/blob/b3347b808326a666229287aa3ef735d4c1cc4ba9/src/main/java/org/openmaptiles/OpenMapTilesMain.java#L33-L35

If that is not enough, then following applies:

If you want to customize the OpenMapTiles schema or generate an mbtiles file with OpenMapTiles + extra layers, then fork ...

https://github.com/onthegomap/planetiler/blame/main/README.md#L143-L145

After that, I guess others might be interested too in such a change, hence PR would be welcome.

When using Planetiler in other ways (say custom map, etc.) then you are defining (among other things) all inputs, hence you can skip (un)desired ones.

@msbarry
Copy link
Contributor

msbarry commented Jan 2, 2023

@HayatSingh7409150572 how are you running planetiler?

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

3 participants