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

error feature ID is not a number if it is numeric but not an mvt_double is confusing and possibly incorrect #262

Open
dzfranklin opened this issue Sep 10, 2024 · 1 comment

Comments

@dzfranklin
Copy link

I got Warning: Attribute "id"="2568923" as feature ID is not a number. This error message initially made me think I was emitting string feature IDs.

From reading the source I believe this error occurs whenever the column type is not an mvt_double:

fprintf(stderr, "Warning: Attribute \"%s\"=\"%s\" as feature ID is not a number\n", sf.full_keys[i].c_str(), sf.full_values[i].s.c_str());

In my case this came from a flatgeobuf uint column: https://github.com/felt/tippecanoe/blob/51fcf142df1ba33e5d0a6ae6ebc57bae47d0fca3/flatgeobuf.cpp#L200C1-L200C56

Is the expected usage that I should be emitting floating point feature IDs? Instinctively that feels wrong because I have never seen non-integer feature IDs used.

@e-n-f
Copy link
Collaborator

e-n-f commented Sep 10, 2024

Thanks. I think this is a bug in the flatgeobuf code, since tippecanoe frontends should treat integer and floating point inputs as equivalent. I'll take a look.

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