Invalid JSON created when setting a field to a string value like '000296'. about tile38 HOT 4 CLOSED

I just pushed an update that will ensure that a numeric field value conforms to JSON.

from tile38.

So this is tied to this issue: #719
Turns out, that field is supposed to be "vehicle name". The vehicle just happens to be called '000296'...

So i'm not sure how to fix this besides moving the "vehicle name" property to under the "properties" object. But i'm not sure if i can do that as that object is currently inserted as a POINT and performance is critical.

Thoughts?

from tile38.

I'm just going to prepend the field value with vn:<name>. Its a hack, but it works.

from tile38.

Turns out _ is also a valid number character for Go but not for JSON....

Tile38Error: Unexpected token _ in JSON at position 11948

from tile38.