[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: [postgis-users] Geometry representation (was: PostGIS Geometry
From: strk () refractions ! net
Date: 2006-02-20 9:52:23
Message-ID: 20060220095223.GC99983 () keybit ! net
[Download RAW message or body]
To make some light on the question:
PostGIS *NEVER* stored geometries in Text format.
Internal representation has always been in binary form.
The difference between 0.x and 1.x is the
*canonical text output representation*
The canonical text output representation is what you get
when fetching a Geometry object from a text cursor. This
is what you get with the 'psql' monitor application, for
example.
Most importantly, canonical text output representation is
the representation used when *dumping* a database. This
is the exact reason why it changed betseen 0.x and 1.x:
to allow lossless dump/restore operations.
I hope this clarify things.
--strk;
On Mon, Feb 20, 2006 at 10:20:38AM +0100, Oleg wrote:
> Dear All,
> 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. and included in the installer
> PostGIS.
> 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?
> Thanks a lot in advance
> Oleg
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic