Not really sure that’s the answer… I’d much rather see work on geodetic edges in GEOS
P > On Jan 21, 2019, at 1:20 PM, Darafei Komяpa Praliaskouski <m...@komzpa.net> > wrote: > > If someone is willing, there is an old Geography Overlays patch that needs > lots of love: https://github.com/postgis/postgis/pull/191 > <https://github.com/postgis/postgis/pull/191> > > On Tue, Jan 22, 2019 at 12:13 AM Paul Ramsey <pram...@cleverelephant.ca > <mailto:pram...@cleverelephant.ca>> wrote: > > > > On Jan 21, 2019, at 1:00 PM, Simon Greener <si...@spatialdbadvisor.com > > <mailto:si...@spatialdbadvisor.com>> wrote: > > > > When a geography is casted to geometry for use in the aggregate form of > > ST_Union (or other commands such as ST_Within) is the processing done > > assuming the data is projected even when geodetic? > > All processing of geometry make cartesian assumptions. Processing of > geography using geography native functions (no casting required) makes > spherical assumptions. When you case from geography::geometry you are telling > the database “please process this data using cartesian assumptions”. Do we > support spherical processing for all (or even many) kinds of operations? No > we do not. That’s hard. Could we in the future? Sure, it might happen. > > ATB, > P > _______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org <mailto:postgis-users@lists.osgeo.org> > https://lists.osgeo.org/mailman/listinfo/postgis-users > <https://lists.osgeo.org/mailman/listinfo/postgis-users> > > -- > Darafei Praliaskouski > Support me: http://patreon.com/komzpa > <http://patreon.com/komzpa>_______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/postgis-users
_______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/postgis-users
