3 ms·
You could have built most of the data side entirely static. First convert the user coordinates to simple mercator XY. Just divide or round that down to some pre
by iamleppert 10y ago
You could have built most of the data side entirely static. First convert the user coordinates to simple mercator XY. Just divide or round that down to some precision and put the resources in a namespaced S3 bucket/path. Then just do a directory listing on resources in that bucket. You could even name them the full precision xy coord so you could still sort by distance, within the bucket.
Let S3 be your database.
You don’t need the full precision of a geospatial query or database if you’re building a simple app that organizes content by location. Depending on your density you segment few 100 meters or few 1000 meters.
- tracker1 10y agoThank you... was my thought for channels as well, geohashes of varying precision for chat channels, and for more static resources using something like you suggest.