Open e-n-f opened 6 years ago
Is geobuf expected to support numbers like this? It's at least 3 orders of magnitude bigger than Number.MAX_SAFE_INTEGER
.
I don't know. It works with the vector tile format, which supports 64-bit signed and unsigned integers, which is what I was trying to test here, but isn't going to be comfortable for anything like JavaScript that wants everything to be doubles. I would have expected it to get rounded to the nearest double instead of giving an error.
json2geobuf
exits with this error:when given this input (the
overflow
test from Tippecanoe):