Re:Tile38 – Realtime geofencing and geospatial index, v1.11.0
by larsvegas_ on Tuesday March 06, 2018 @05:42AM
(#16528042)
I had been following tidwall/tile38 for a while already, too without a clear use case for actually using it. When we refactored a main part of our code base the use case finally arose;-)
At this point we're about to release tile38 to our staging environment. We opted for it basically for its capability to cache and spatially query geojson directly. Plus this can be done without the serialisation/deserialisation overhead. Another advantage for us is the ability to use the python-redis bindings. This let's us execute commands like this to retrieve data for a tile x,y,z request:
res = client.execute_command(
"INTERSECTS", our_key, "WHERE", "minzval", 1, z,
"LIMIT", LIMIT, "TILE", x, y, z
)
At this point we're about to release tile38 to our staging environment. We opted for it basically for its capability to cache and spatially query geojson directly. Plus this can be done without the serialisation/deserialisation overhead. Another advantage for us is the ability to use the python-redis bindings. This let's us execute commands like this to retrieve data for a tile x,y,z request:
res = client.execute_command( "INTERSECTS", our_key, "WHERE", "minzval", 1, z, "LIMIT", LIMIT, "TILE", x, y, z )
Very straightforward and very fast.