Josh Baker

Hi Mona, Sorry for the slow response on this issue. I agree that there should be a way for Tile38 to automatically delete the hook that is watching on the...

Hi huangpeizhi, If I understand correctly, you are asking for fields that allow string values? For example: ``` SET fleet truck1 FIELD id abc123 POINT 33.423 -115.726 ```

I'm going to allow storing string fields in a future release.

I've done benchmarking but I haven't published any formal results. Geofencing performance can vary greatly due to the complexity and number of geofences and object updates per second. A database...

Hi @naveenchlsn, Tile38 is a single instance database that supports replication. There is one leader instance, but there can be many followers. The leader is the only instance that can...

I agree. I think this may be a good candidate for a topic page on http://tile38.com/documentation. I would very much appreciate your help. Right now the tile38.com content is being...

In the section about Bounding Boxes, the [GeoJSON spec](https://tools.ietf.org/html/rfc7946#section-3.1.9) does state: > Implementers MUST NOT use latitude values greater than 90 or less than -90 to imply an extent that...

I'm cool with that. Were you thinking to just validate the lat/lons for -/+180,90, and throw an error?

I agree. Perhaps the easiest approach is to add a `Valid` method to the GeoJSON `Object` type. https://github.com/tidwall/geojson/blob/master/object.go#L31-L45 Also having a parse option list 'RequireValid=true' https://github.com/tidwall/geojson/blob/master/object.go#L75-L90

Then from Tile38, maybe have a configuration option like `require-valid` ?