I am encountering an issue with Tippecanoe while generating vector tiles from GeoJSON data. Specifically, the uprn property of the second feature is being replaced with the uprn of the first feature. This occurs when generating tiles with the following command:
When generating tiles, the second feature’s uprn (10022901830) gets replaced by the first feature's uprn (100062108583). The other properties are retained correctly, but this issue is causing a duplication of the uprn value across both features.
Expected Result:
The uprn of each feature should remain unique and retain its original value from the GeoJSON input.
Steps Taken:
I ensured the uprn property is included and set as a string using --include=uprn and --attribute-type=uprn:string.
I used the --no-feature-limit and --no-tile-size-limit options to avoid any potential feature limitations.
Tested with different zoom levels and tile generation configurations, but the issue persists.
Could you please provide guidance on how to fix this issue or whether there might be a bug affecting the handling of unique properties across features?
I am encountering an issue with Tippecanoe while generating vector tiles from GeoJSON data. Specifically, the
uprn
property of the second feature is being replaced with theuprn
of the first feature. This occurs when generating tiles with the following command:Command:
GeoJSON Sample:
Issue:
When generating tiles, the second feature’s
uprn
(10022901830
) gets replaced by the first feature'suprn
(100062108583
). The other properties are retained correctly, but this issue is causing a duplication of theuprn
value across both features.Expected Result:
The
uprn
of each feature should remain unique and retain its original value from the GeoJSON input.Steps Taken:
uprn
property is included and set as a string using--include=uprn
and--attribute-type=uprn:string
.--no-feature-limit
and--no-tile-size-limit
options to avoid any potential feature limitations.Could you please provide guidance on how to fix this issue or whether there might be a bug affecting the handling of unique properties across features?
Thank you for your assistance!