You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 6, 2021. It is now read-only.
My suggestion : add a param to format datetime and use the RfC 3339 or the format used in wms/wfs. This could allow us to format it to what we want and by pass the error.
I have a timestamp field without timezones in the database and when feature server try to serialize it he is unable.
There is no standards in JSON nor in GeoJSON for datetime formats, but there should be a way to avoid this problem.
Here's a discussion about it :
http://stackoverflow.com/questions/455580/json-datetime-between-python-and-javascript
My suggestion : add a param to format datetime and use the RfC 3339 or the format used in wms/wfs. This could allow us to format it to what we want and by pass the error.
Thanks