Jan. 28, 2015
8:31 p.m.
2015-01-28 17:17 GMT-03:00 stepharo <stepharo@free.fr>:
Why would you have to do that in SQL?
PostGIS is a little more than SQL, SQL enables you to query it, but it provides you with a lot of GIS functionality. I woudn't load a million rows into Pharo memory to search nearby locations to a coordinate, or group results based on whether they are inside of a certain boundary. Why you cannot import PGPoint and PGPolygon in Pharo?
Right now there is no PGPoint nor any of the PostGIS geometry objects in Pharo. Mainly because of that. If its worth, I might end up creating those abstractions. So I can also create the proper "converter" to map back and forth using GLORP. Regards, Esteban A. Maringolo