3 ms·

Thanks for the response. I see what I was actually looking for was on http://tile38.com/topics/object-types/ http://tile38.com/topics/object-types/ Right there

Thanks for the response. I see what I was actually looking for was on http://tile38.com/topics/object-types/ http://tile38.com/topics/object-types/ Right there on the front page, and not in the docs tab where I was looking. For the GeoJSON, does it support properties? Meaning can I store a a whole document in there? Or would it be best to just store an ID and lookup the ID in a DB or something?

tidwall 10y ago
> 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 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".
- mynewtb 10y ago
  The RFC also limits GeoJSON to WGS84 by the way. https://tools.ietf.org/html/rfc7946 https://tools.ietf.org/html/rfc7946
  - tidwall 10y ago
    Thanks for sharing. The draft RFC at the beginning of the year included the CRS key so it must've be a recent decision.