-
Notifications
You must be signed in to change notification settings - Fork 432
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
Using non-numeric feature ID #357
Comments
This is a limitation of the vector tile format specification: the feature ID is defined only as an optional integer. I think a future version of the spec could allow non-numeric IDs, but there is no way to represent them now. |
Is the vector tile format specification going to change soon to support non-numeric IDs? The last comment was in Jan 2017, over 2 years ago. i.e. tippecanoe will support non-numeric IDs soon? The map GL setFeatureState api seems to imply the feature id can be either number or string at the moment and it is not consistent with the current state of tippecanoe. |
String IDs are supported in the #611 development branch for version 3 of the vector tile spec. |
Hi, I am still getting a
when using Tippecanoe. Has this been fixed? Thanks! |
Hi,
I was trying to convert some geojson to mbtiles with zoom-level setups, noticed some of the geojson like this have string as their feature ID, which tippecanoe warns: Warning: Can't represent non-numeric feature ID "xx"
Wondering is there a way for tippecanoe to use string feature ID directly? before trying to manually cast them to numeric types.
Thanks :)
The text was updated successfully, but these errors were encountered: