TItidwall·Dec 30, 2016Submission
Tile38 – Realtime geofencing and geospatial index, v1.7.0
130 points · Open discussiontidwall
tile38
Go2016–2023
tidwall / tile38
tile38
Real-time Geospatial and Geofencing
10Distinct people
27Mentions
2Explicit recommenders
9.8KGitHub stars
What to know before exploring
What it is
Real-time Geospatial and Geofencing
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
On a side note, tidwall (Josh) is one of the primary reasons why I want to give Go a go. I love https://github.com/tidwall/tile38.
nevi-me used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- tidwall/buntdb · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:02:44 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year27 dated mentions
Observed mentions: 2016-03-04 23:55:51 UTC to 2023-09-23 12:08:29 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 5 | 2 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 8 | 5 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 5 | 4 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesTile38 – Geospatial DB and realtime geofence v1.6. 25% faster and Geofence groups
5 points · Open discussionTile38 – Geospatial database and realtime geofence. v1.5.0 – GRPC and 3d support
24 points · Open discussionTile38 – Geospatial index and realtime geofence. v1.4.1 adds BOUNDS command
3 points · Open discussionhttps://github.com/tidwall/tile38#geofencing
And the connection will be kept open. If any object enters or exits the 6 km radius around 33.462,-112.268 the server will respond in realtime with a message such as:
{"command":"set","detect":"enter","id":"truck02","object":{"type":"Point","coordinates":[-112.2695,33.4626]}}
In Show HN: Tile38 – A geolocation DB with spatial index and realtime geofencingThis is a really interesting project. I love the concept of a fast, in-memory geospatial database - kind of like Redis for Geo (interestingly Redis itself has grown some basic Geo features recently, but nowhere near as comprehensive as this - http://redis.io/commands/georadius ).
The way you can subscribe to geofenced areas is particularly clever, especially when combined with the WebSocket protocol option.
The docs don't cover how to communicate polygons/etc over the protocol just yet.
I hadn't realised you could use unicode characters for identifiers in Go - very aesthetically pleasing: https://github.com/tidwall/tile38/blob/master/geojson/geo/ge...
In Show HN: Tile38 – A geolocation DB with spatial index and realtime geofencingShow HN: Tile38 – A geolocation DB with spatial index and realtime geofencing
82 points · Open discussion