Background
I'm working on a client-side tile merging approach that combines static geometry with geometry-less attribute tilesets: maplibre-merge-protocol
I already use tile-join to prepare the tiles, but currently need a custom step to strip geometry from the original tiles.
Would you accept a PR adding an option to tile-join to remove geometry from features while preserving IDs and attributes?
I understand this would technically produce invalid MVT, but it would be an explicit opt-in option for this advanced workflows where geometry is provided separately and merged client-side.
I'd be happy to try to contribute the PR if this is acceptable.
Background
I'm working on a client-side tile merging approach that combines static geometry with geometry-less attribute tilesets: maplibre-merge-protocol
I already use
tile-jointo prepare the tiles, but currently need a custom step to strip geometry from the original tiles.Would you accept a PR adding an option to
tile-jointo remove geometry from features while preserving IDs and attributes?I understand this would technically produce invalid MVT, but it would be an explicit opt-in option for this advanced workflows where geometry is provided separately and merged client-side.
I'd be happy to try to contribute the PR if this is acceptable.