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

Need Assistance with Reducing PBF File Size in Tippecanoe #271

Open
mani-mworks opened this issue Sep 24, 2024 · 2 comments
Open

Need Assistance with Reducing PBF File Size in Tippecanoe #271

mani-mworks opened this issue Sep 24, 2024 · 2 comments

Comments

@mani-mworks
Copy link

I am using the following command to generate MVT vector tiles using Tippecanoe, but the output PBF files are too large (4+ MB each). My goal is to display all the geo data starting from the minimum zoom level. Below are the command details:

tippecanoe --force  --no-feature-limit --no-tile-size-limit --force-feature-limit --no-clipping --drop-rate=1 --minimum-zoom=5 --maximum-zoom=16 --layer=households --output-to-directory "output_dir" json_path

Requirement:

  • The PBF file sizes need to be reduced while still displaying the geo data starting from the minimum zoom level.

Attempts:

  • I've used settings like --no-feature-limit, --no-tile-size-limit, --force-feature-limit, and --no-clipping to ensure all data is retained.
  • Despite this, the file sizes are too large (4+ MB per tile).

Questions:

  1. What configuration can I adjust to reduce the size of the PBF files without losing the visibility of data at the minimum zoom level?
  2. Are there other optimizations I can apply to balance size and performance at lower zoom levels?

Thank you for your help!

@e-n-f
Copy link
Collaborator

e-n-f commented Sep 24, 2024

If you can't drop features, the other things that you can do to reduce tile size are to simplify geometry (probably through lower geometric detail with -D) and to drop attributes and feature IDs that you don't need. Integer attributes take less space than floating point and strings; duplicate attributes take less space than unique attributes.

Do not use --no-clipping unless you really need the complete geometry of each feature to appear in every tile that it intersects.

@mani-mworks
Copy link
Author

@e-n-f Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants