From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Oleg <evdakov(at)iwk(dot)uka(dot)de> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: PostGIS Geometry column in pg8.1.3 |
Date: | 2006-02-17 16:59:08 |
Message-ID: | 20060217165908.GA44873@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Fri, Feb 17, 2006 at 02:50:21PM +0100, Oleg wrote:
> While workin with PostgreSQL 7.4.6 Geometry was stored as String for
> example:
> SRID=-1;POINT(135.744865606022 304.591390378093)
> Now we have installed PostgreSQL 8.1.3.
> Geometries are stored in a different format for example:
> 01010000003E580C9953964A41F76AF257F9CD5441
> Is there a way to set up PostgreSQL8.1 or PostGIS to store geometries in
> String format as it was prviously?
PostGIS is a separate project from PostgreSQL so you'd be better off
asking questions about it on the postgis-users mailing list.
http://postgis.refractions.net/mailman/listinfo/postgis-users
The change you're seeing is due to a different version of PostGIS,
not a different version of PostgreSQL. Recent versions of PostGIS
(since 1.0, I think) display a different "canonical form" than older
versions did; search the postgis-users and postgis-devel archives
for discussion and rationale. You can use the AsText or AsEWKT
functions to get the Well-Known Text representation:
postgis=> SELECT geom, AsText(geom) FROM foo;
geom | astext
--------------------------------------------+------------------------
010100000077BE9F1A2FDD5E40AC1C5A643BDD8E40 | POINT(123.456 987.654)
(1 row)
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-02-17 17:09:57 | Re: Writing Python triggers and the TD dictionary value |
Previous Message | operationsengineer1 | 2006-02-17 16:40:04 | Re: Queries to Export |