-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
PostGIS JSON field #380
Comments
@sacontreras currently the MVT spec has no treatment specifically for objects or lists, which is why the JSON is being encoded as a string. There's a discussion on the spec repo for this topic here. Near term I think you will need to use JSON.parse() on the client side to convert the string to a JSON object. Alternatively you could pull the important parameters out of the JSON object in your ProviderLayer SQL and encode the values as normal tags. |
@ARolek While I do find this topic interesting, I think you've confused me with the original poster (@sanfilippopablo). 👍 |
@ARolek yes, |
Hello! I have a JSON field in my PostGIS table that I want to put as an object in the properties of the feature. However, the json is being put as a string. Is it possible to parse it to an object?
The text was updated successfully, but these errors were encountered: