News for hackers. Stuff that matters.
Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0 by tidwall on Friday December 30, 2016 @01:12PM (#13285966)
> For the GeoJSON, does it support properties?

Yes, Tile38 has full GeoJSON support including properties for Feature objects. Though there is one exception, the CRS key is ignored because WGS84 is assumed.

> Meaning can I store a a whole document in there?

Yes, as long as the document conforms to http://geojson.org/geojson-spec.html. Though JSON keys that are not defined in the spec will be stripped out of the document prior to storing in memory. For example, a "properties" key of a type that is not a "Feature" will be stripped, and requesting that object at later time will result in a JSON document that does not include the "properties".

Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0 by mynewtb on Friday December 30, 2016 @06:17PM (#13288363)
The RFC also limits GeoJSON to WGS84 by the way. https://tools.ietf.org/html/rfc7946
Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0 by tidwall on Friday December 30, 2016 @06:43PM (#13288485)
Thanks for sharing. The draft RFC at the beginning of the year included the CRS key so it must've be a recent decision.