I created a gdal/ogr-plugin (as .deb) for the ogr-grass-driver which
loads perfect into ogr:
ogrinfo --formats
Loaded OGR Format Drivers:
-> "GRASS" (readonly)
-> "ESRI Shapefile" (read/write)
[...]
-> "Interlis 1" (read/write)
-> "Interlis 2" (read/write)
-> "PostgreSQL" (read/write)
When I try to use ogrinfo on a GRASS-vectordataset (outside GRASS), I
have some variable-related warnings... Inside GRASS everything works
great.
When building gdal/ogr not as a module, I did not discover this
problem.
Perhaps anybody can give me a hint how to solve this issue?
<warnings>
ogrinfo /home/gdf/grassdata/spearfish57/PERMANENT/vector/soils/head
Warning 1: GRASS warning: GISBASE enviroment variable was not set,
using: ogrinfo -al
-summary /home/gdf/grassdata/spearfish57/PERMANENT/vector/soils/head
Warning 1: GRASS warning: GISBASE enviroment variable was not set,
using:
Warning 1: GRASS warning: unable to open datum table
file: /etc/datum.table /etc/ellipse.table: Datei oder Verzeichnis nicht
gefunden Warning 1: GRASS warning: unable to open ellipsoid table
file: /etc/ellipse.table Warning 1: GRASS fatal error: invalid
ellipsoid clark66 in file Unable to initialise PROJ.4 with the
following parameter list: +proj=utm +zone=13 +a=-1.995876312255859
+rf=-1.998111724853517 +no_defs +nadgrids=conus The error message was
'squared eccentricity < 0' Warning 1: GRASS warning: Can't parse GRASS
PROJ_INFO file Datei oder Verzeichnis nicht gefunden: /driver/db/
Warning 1: GRASS warning: Cannot open driver 'dbf'
ERROR 1: Cannot open database dbf by
driver /home/gdf/grassdata/spearfish57/PERMANENT/dbf/, check if GISBASE
enviroment variable is set, the driver isavailable and the database is
accessible. Warning 1: GRASS warning: unable to open datum table
file: /etc/datum.table /etc/ellipse.table: Datei oder Verzeichnis nicht
gefunden Warning 1: GRASS warning: unable to open ellipsoid table
file: /etc/ellipse.table Warning 1: GRASS fatal error: invalid
ellipsoid clark66 in file Unable to initialise PROJ.4 with the
following parameter list: +proj=utm +zone=13 +a=-1.995876312255859
+rf=-1.998111724853517 +no_defs +nadgrids=conus The error message was
'squared eccentricity < 0' Warning 1: GRASS warning: Can't parse GRASS
PROJ_INFO file INFO: Open of
`/home/gdf/grassdata/spearfish57/PERMANENT/vector/soils/head' using
driver `GRASS' successful.
On 9/15/05, Stephan Holl <holl@gdf-hannover.de> wrote:
Dear GRASS/GDAL-users,
I created a gdal/ogr-plugin (as .deb) for the ogr-grass-driver which
loads perfect into ogr:
ogrinfo --formats
Loaded OGR Format Drivers:
-> "GRASS" (readonly)
-> "ESRI Shapefile" (read/write)
[...]
-> "Interlis 1" (read/write)
-> "Interlis 2" (read/write)
-> "PostgreSQL" (read/write)
When I try to use ogrinfo on a GRASS-vectordataset (outside GRASS), I
have some variable-related warnings... Inside GRASS everything works
great.
When building gdal/ogr not as a module, I did not discover this
problem.
Perhaps anybody can give me a hint how to solve this issue?
OGRGRASSDataSource is using char *gisbase = GRASS_GISBASE;
which is set in makefile:
CPPFLAGS := -DGRASS_GISBASE=\"$(GRASS_GISBASE)\"
and that is probably missing in your makefile for the module.
On 9/15/05, Stephan Holl <holl@gdf-hannover.de> wrote:
> Dear GRASS/GDAL-users,
>
> I created a gdal/ogr-plugin (as .deb) for the ogr-grass-driver which
> loads perfect into ogr:
> ogrinfo --formats
> Loaded OGR Format Drivers:
> -> "GRASS" (readonly)
> -> "ESRI Shapefile" (read/write)
> [...]
> -> "Interlis 1" (read/write)
> -> "Interlis 2" (read/write)
> -> "PostgreSQL" (read/write)
>
> When I try to use ogrinfo on a GRASS-vectordataset (outside GRASS),
> I have some variable-related warnings... Inside GRASS everything
> works great.
>
> When building gdal/ogr not as a module, I did not discover this
> problem.
> Perhaps anybody can give me a hint how to solve this issue?
OGRGRASSDataSource is using char *gisbase = GRASS_GISBASE;
which is set in makefile:
CPPFLAGS := -DGRASS_GISBASE=\"$(GRASS_GISBASE)\"
and that is probably missing in your makefile for the module.
Well, it is set in the makefile, but I do not know if it is used when
using debian dpkg-buildpackage. I had some trouble about overriding
variables by the debian packagebuild-system.