As the pre-eminent OpenSource raster GIS, I am interested in contributing
to GRASS when it is convenient to do so, primarily related to my data
In addition to the shape related work, I am also interested in making the
TIFF tools GeoTIFF aware, and perhaps work related to projections support
I have removed my v.in.shape code, because the copy checked into GRASS CVS
is much more up to date. Last I saw it was in grass/src/mapdev/v.in.shape.
This is a raster import program based on my
Geospatial Data Abstraction
Library (GDAL). It supports import of a wide variety of raster file
formats, including many variations on GeoTIFF.
The current implementation uses dynamic loading of libgdal.1.1.so using
dlopen(), so as to avoid depending on linking against GDAL explicitly. Integer
and floating point rasters are supported; as well as importing the
georeferenced bounds. The current source is now in CVS (in
src/raster/r.in.gdal), so fetch from there to get the most
recent. To make it work you will need a built libgdal.1.1.so, such as
one of those listed below.
When building GDAL for use with GRASS the following options are suggested.
They minimize dependencies on external shared libraries, and avoid some
stuff of no use to GDAL.
./configure --with-grass=no --with-png=internal --with-jpeg=internal
--with-geotiff=internal --with-libz=internal --without-ogr
Standalone GRASS Library
The libgrass package consists of the majority of the GRASS libgis, and
libdatetime library build as a standalone shared library suitable for use
by non-GRASS applications wishing to read and write GRASS databases. Some
additional functions have been added to simplify library initialization and
data access by non-GRASS applications.
While libgrass is currently only suitable for accessing GRASS raster cells,
and associated support files, it is hoped that future revisions will include
support for vector files, and other data elements stored within the GRASS
Sample GRASS Data In Different Projections
I generated locations in a bunch of different projections using r.in.gdal
from the "pci_eg" sample GeoTIFF files for testing my projections handling.
Each projection is it's own location. A location like proj_tm has a
single raster cell in the PERMANENT mapset called proj_tm as well. The
projection parameters are in the PROJ_INFO file, and the listgeo output
for the original file can be found in the tm.lgo file in the