[postgis-devel] Geog/Geom Hack

[Paragon Corporation]

Paul,
I would rather you didn't for 2 reasons

1) I'm lazy and for each of these things we'd have to apply the text
additional function proto hack to prevent from it breaking geometry.  which
we will probably end up taking out anyway.

2) I don't like the hiddenness of it since it becomes especially annoying if
you have your native in geometry and you are converting to geography for a
special usecase, then you end up with a slower implementation

as you would really end up doing accidentally

geometry -> geography -> geometry ->operation (and why do I want my calcs
done in UTM?)

Instead of the more efficient

geometry -> operation

Thanks,
Regina

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
Ramsey
Sent: Friday, October 30, 2009 8:16 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] Geog/Geom Hack

I'm interested to know what the general opinion is of the trick I've used on
ST_Buffer(geography):

http://trac.osgeo.org/postgis/browser/trunk/postgis/geography.sql.in.c#L541

I ask because I could apply the same idea to the larger suite of OGC SFSQL
predicates before release. Is half-a-loaf better than no loaf in this case?
(Note that there will be failure cases for really large geometry, like a
polygon of "Asia" or "Russia" that have polygons over the dateline.)

P.
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel