Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by tidwall on Monday March 04, 2019 @06:20PM
(#19306661)
I'm glad you like the product.
Today it's possible to assign a Z coordinate to an object, which allows for querying on Lat/Lon and filtering on Z.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by gravypod on Monday March 04, 2019 @06:38PM
(#19306786)
That's really cool! The only other optimization that I wanted to try and do was to use GPU acceleration to support huge numbers of shapes and entities. Something similar to what's described here [0]. I think it would really help for very very large numbers of entities or large complex geometry.
[0] - https://devblogs.nvidia.com/thinking-parallel-part-i-collisi...
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by ptrott2017 on Tuesday March 05, 2019 @02:09AM
(#19308683)
I think JB originally added Z for zoom level for map tile zoom level, but (having done exactly this for some internal demos) you can totally abuse it for what you want and it works well. Tile38 is a really excellent geospatial database and a lovely codebase.
As for integrating GPU - look at Gorgonia's CU package by Xuanyi Chew that will give you ahead start from using CUDA from Go. Good luck.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by tidwall on Tuesday March 05, 2019 @11:13AM
(#19311477)
The Z coord is a flexible field that can handle any numerical range. Zoom level, elevation, timestamp, etc.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by Ancient on Monday March 04, 2019 @06:15PM
(#19306628)
I'm curious to know where one gets such "heigh-support" data from?
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by joshvm on Monday March 04, 2019 @07:21PM
(#19307034)
GPS gives you a 3D fix (lat/lon/height). A common use case in aviation, particularly drones, is avoiding controlled airspace. The height of controlled airspace varies with location - for example a rural area might be 7500ft while near an airport traffic zone it might be only 1000ft or lower.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by gravypod on Monday March 04, 2019 @09:24PM
(#19307602)
GPS isn't too great in skyscrapers. In most current gen smartphones GPS can only really pin you to a 16ft resolution on a current gen smartphone in ideal conditions [0]. This gets worse indoors and if the target is moving.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by sbr464 on Monday March 04, 2019 @10:11PM
(#19307800)
It wouldn’t necessarily need to come from GPS. You could use beacons (ble) or similar to augment the raw dataset.
https://estimote.com (etc)
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by joshvm on Tuesday March 05, 2019 @03:55AM
(#19309180)
For airspace it doesn't matter too much. Allowable Mode-C accuracy is something more than 100 feet (I think) to allow for poor sensors, and controllers simply add a buffer.
Re:Show HN: Tile38 – Realtime geofencing and geospatial index
by gravypod on Monday March 04, 2019 @06:26PM
(#19306694)
If I worked in the advertisement space I'd probably install WiFi networks that could broadcast SSIDs at known mac addresses that are coded to a height. I could install apps on user phones that could read that and pull out height & building name data.
Do you plan on adding height-support? I'm sure some clients in the professional space would like to know "what room/floor in this building are you in?"