[postgis-users] PostgreSQL geographical datatypes and PostGIS

Obe, Regina DND\MIS robe.dnd at ci.boston.ma.us
Thu Jun 26 05:58:25 PDT 2003

If the intent is to maintain old apps while developing new apps that use the
new postgis datatypes,  I would think that perhaps adding a postgis geometry
field to your existing tables would do the trick.

E.g. you still keep your point data for example as is, add another field
that is a postgis geometry and then update that new field with the postgis
geometry equivalent.

Your old scripts would still utilize the native postgresql (POINT, POLYGON,
PATH) columns and your new scripts or mapserver scripts would utilize the
new geometry fields.

I'm not sure if there is an easier way than that, but that's the first
thought that comes to mind.


-----Original Message-----
From: Hubert Fröhlich [mailto:hubert.froehlich at bvv.bayern.de]
Sent: Thursday, June 26, 2003 2:41 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] PostgreSQL geographical datatypes and PostGIS

Hi list,

I have been using PostgreSQL geographical datatypes (POINT, POLYGON, 
PATH etc. ) for GIS web applications, mainly accessed by self-developed 
CGI scripts.

Now, with UMN MapServer upcoming and OGC Simple Features,, SHAPE export 
etc., I'd like to use PostGIS geographical datatypes and operations for 
my existing PostgreSQL data.

Now my question. Is there a way to integrate old PostgreSQL datatypes 
into the PostGIS concept WITHOUT redesigning the database and tinkering 
around a lot with cast operations? How can I use PostgreSQL datatypes 
for PostGIS (and MapServer) in an un-sophisticated way?


Dr.-Ing. Hubert Fröhlich			
Bezirksfinanzdirektion München 			
Alexandrastr. 3, D-80538 München, GERMANY
Tel. :+49 (0)89 / 2190 - 2980
Fax  :+49 (0)89 / 2190 - 2459
hubert.froehlich at bvv.bayern.de

postgis-users mailing list
postgis-users at postgis.refractions.net

More information about the postgis-users mailing list