[Gdal-dev] StarSpan Progress, and quick question on OGR data sources [update]

Dylan Beaudette debeaudette at ucdavis.edu
Thu Nov 2 15:06:21 EST 2006

Quick update, based on some quick analysis by Hobu:


reveals that starspan is only using the _first_ layer from an OGR data source. 
Hobu suggests that "starspan needs an option that does GetLayerByName and 
takes in a layer name".

Any ideas on who I can implement this Carlos ? 


> Hi guys,
> I was recently working on a project involving vector data stored in a
> PostGIS table, and raster data stored in GRASS - using starspan to perform
> the analysis. I noticed a (bug?) in starspan, where the --vector argument
> will only accept a single parameter. This becomes a problem when specifying
> an OGR PostGIS connection.
> For example:
> ogrinfo PG:"dbname=pinn  host=localhost" table_name
> would return all the gory details from the spatial table 'table_name'  from
> the database 'pinn' .
> note that there are two parameters on the command line: a DSN and the table
> (or in OGR terms, a layer).
> In starspan it is not possible to pass in 2 items to the --vector argument.
> I posted this question on the IRC channel yesterday, and was away from the
> computer when Frank responded.
> It sounds like there is no way to specify a 'table' in the PG datasource
> description line. Searching google, it sounds like there is some way to
> specify a 'schema' - but it is not clear how or if this would allow one to
> specify a specific table in a PostGIS data source.
> Therefore, I wonder if there is a simple modification to the starspan code
> which would allow for PG data sources to specify a table.
> Note that starspan can correctly extract PG vector data, when there is only
> 1 spatial table in the DB.
> Any thoughts?
> PS: I think that the abilities of starspan really shine here: extracting
> data from postgis and GRASS, two drastically different data sources -- all
> though the magic which is GDAL. Good work everyone!

Dylan Beaudette
Soils and Biogeochemistry Graduate Group
University of California at Davis

More information about the Gdal-dev mailing list