CrazyBug-11

I have added the following code to calculate the centroid of each feature after executing sliceIntoTiles(). However, after testing, I found that the results did not change, and the label...

test data: General Information Name: AR.parquet Size: 998.83 MB Last Modified: July 1, 2024, Monday, China Standard Time, 7:03:01 PM Provider: ogr Information Provided by the Program Storage Format: Parquet...

I've found that the Geometry obtained in this part of the code is empty during debugging. Is there any parameter that can be set to avoid this, ensuring at least...

> Planetiler doesn't include empty tiles in the output. It only includes tiles with data in them. Could that explain what you're seeing? I've found that the Geometry obtained in...

Yes, my apologies for not describing it clearly earlier. I have identified a few parameters: `arguments.getDouble("min_feature_size_at_max_zoom", "Default value for the minimum size in tile pixels of features to emit at...

> Yes, for this use-case that seems like it makes sense. There are a few other options as well: > > 1. You could call `setMinPixelSize(0)` on the features during...

hello，@msbarry Currently, I am testing some large datasets, and the generated tiles, especially at lower zoom levels, often result in large blank areas due to the small size of features....

Yes, I am currently using setMinPixelSize(0), but unfortunately, there are still some blank areas. According to my understanding, setMinPixelSize(0) should represent the raw data, so theoretically, there shouldn't be any...

In planetiler I can't find the logic that features smaller than a single pixel will be discarded. Can you tell me if this logic is in planetiler or in other...