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

Best settings to optimize bathymetry data #269

Open
y3nd opened this issue Sep 20, 2024 · 1 comment
Open

Best settings to optimize bathymetry data #269

y3nd opened this issue Sep 20, 2024 · 1 comment

Comments

@y3nd
Copy link

y3nd commented Sep 20, 2024

Here are some produced tiles

The main issue is not the tile size but the extreme amount of polygons at low zoom levels.
I have tried many settings like polygon drops, coalesce etc.. without success in reducing the complexity without breaking the file completely. The source geojson is a 17 multipolygon file for each possible depth.

What would be the best tracks to reduce the complexity and display a lower amount of polygons at low zoom level ?

Thanks

@e-n-f
Copy link
Collaborator

e-n-f commented Sep 20, 2024

If your polygons were pancaked instead of adjacent, I would suggest setting a tippecanoe:minzoom for every other contour level to make it drop out at lower zooms, but it looks like you need continuous coverage. Do you have the option of setting a larger tile size limit?

What we do at Felt is:

  • set a 2.5 MB tile size limit with -M2500000
  • set a lower tile resolution at low zooms with -D10
  • use --no-simplification-of-shared-nodes to prevent introduction of shard gaps between adjacent rings
  • use --coalesce-densest-as-needed to collapse small rings into larger ones when necessary

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