This will be really slow, if you are talking about doing a query for each point 
of each geometry you want to retrieve... I guess you could request several 
points in one query but probably not all point in on query as some geometries 
are likely to have too many points and the SQL will get too big. Doesn't the 
postgis code itself have stuff for dealing with WKT/WKB input/output? Shouldn't 
be too hard to use it to do what you want.

Chris


Quoting Seamus Thomas Carroll <carrolls@cpsc.ucalgary.ca>:

> I was thinking of using postgis functions NumPoints(geometry)
> and PointN(geometry,integer) to do the parsing on the database side.  Not
> as efficient but should do the job well enough under current time
> restrictions.
> 
> Seamus
> 
> On Wed, 18 Feb 2004, David Blasby wrote:
> 
> > Frank Warmerdam wrote:
> > > Seamus,
> > >
> > > It isn't really a lightweight solution, but the OGR library can be used
> > > for this purpose.  It will read PostGIS features and turn them into C++
> > > objects from which you can get geometry bits, attribute values and so
> > > forth.
> >
> >
> > You can also use WKB - its the standard method for easily getting data
> > from the database.  A WKB parser is fairly easy to write.
> >
> > dave
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users@postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> >
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
> 





