[postgis-devel] RE: [postgis-users] Problem with PostGIS 1.0.0 RC1

strk at refractions.net strk at refractions.net
Tue Jan 25 06:33:05 PST 2005


On Tue, Jan 25, 2005 at 03:23:18PM +0100, Markus Schaber wrote:
> Hi, strk,
> 
> strk at refractions.net schrieb:
> 
> > At this point, to finish with consistency, we might want to
> > change geoemtry::text cast to return EWKT instead of HEXWKB.
> 
> I'm okay with this, I think this does not hurt.
> 
> > So you could do:
> >
> > 	GeomFromWKB(geometry); <-- autocast to bytea
> > 	GeomFromText(geometry); <-- autocast to text (needs (E)WKT to work)
> 
> Strange, I cannot imagine any use-case for this, at least in my apps.

It came to mind to check OGC compliance of a given geometry, does not
sound as a clean way anyway...

> I think that both variants would issue parser warnings in GeomFrom*()
> when we have a 3D, M or 3D/M geometry?

Yes, with these massages:

WARNING:  OGC WKT expected, EWKT provided - use GeomFromEWKT() for this
WARNING:  OGC WKB expected, EWKB provided - use GeometryFromEWKB() for this

--strk;

> 
> 
> Happy coding,
> Markus
> --
> markus schaber | dipl. informatiker
> logi-track ag | rennweg 14-16 | ch 8001 z├╝rich
> phone +41-43-888 62 52 | fax +41-43-888 62 53
> mailto:schabios at logi-track.com | www.logi-track.com



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




More information about the postgis-devel mailing list