|
|
|
|
|
|
by bpicolo
3081 days ago
|
|
|
It's interesting - their use case requires consistent background refresh, which might make postGIS less optimal, but unsure what rate they were doing it at. Query-wise, PostGIS should be able to use geohashes which can do these lookups in O(1) time (S2 geometry would be similar). That said, indexing scales terrible with geohashing/S2 at high granularity levels, though they wouldn't need something particularly granular for this (seems fine to be off by tens or hundreds of meters) |
|
|