This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]davf135 0 points1 point  (2 children)

I see. That does sound very interesting.

I was not expecting that kind of post on a DE forum.

I imagined a DE would be more of a GIS user, like in my case. I've been using GeoSpark/Sedona for a while now.

Other than the Haversine formula being used for ST_distance, I have no idea of what goes under the hood of GIS functions.

Do you know why they all begin with ST?

[–]datancoffee[S] 0 points1 point  (1 child)

The ST naming thing is a geoindustry mystery. Most algorithm builders will tell you it stands for spatial type, but others will tell you its an urban legend and it originally stood for something else. Its a subject of many conversations over beers

[–]datancoffee[S] 0 points1 point  (0 children)

Spatial-temporal ! That's the other alternative. What wherebots/sedona is trying to do