table of contents
other versions
- jessie 6.4.4-1
- stretch 7.2.0-2
- testing 7.6.0-1
- unstable 7.6.0-1
- experimental 7.6.1-1~exp1
r.in.gdal(1grass) | Grass User's Manual | r.in.gdal(1grass) |
NAME¶
r.in.gdal - Import GDAL supported raster file into a binary raster map layer.KEYWORDS¶
raster, importSYNOPSIS¶
r.in.gdalFlags:¶
- -o
-
- -e
-
- -f
-
- -l
-
- -k
-
- --overwrite
-
- --verbose
-
- --quiet
-
Parameters:¶
- input=name
-
- output=name
-
- band=integer
-
- memory=integer
-
- target=name
-
- title=
-
- location=name
-
DESCRIPTION¶
r.in.gdal allows a user to create a (binary) GRASS raster map layer, or imagery group, from any GDAL supported raster map format, with an optional title. The imported file may also be optionally used to create a new location.OPTIONS¶
Extended explanations:Flags:¶
- -e
-
GDAL supported raster formats¶
Full details on GDAL supported formats are available at: http://www.gdal.org/formats_list.html Selected formats of the more than 80 supported formats:Location Creation¶
r.in.gdal attempts to preserve projection information when importing datasets if the source format includes projection information, and if the GDAL driver supports it. If the projection of the source dataset does not match the projection of the current location r.in.gdal will report an error message (Projection of dataset does not appear to match current location) and then report the PROJ_INFO parameters of the source dataset. If the user wishes to ignore the difference between the apparent coordinate system of the source data and the current location, they may pass the -o flag to override the projection check. If the user wishes to import the data with the full projection definition, it is possible to have r.in.gdal automatically create a new location based on the projection and extents of the file being read. This is accomplished by passing the name to be used for the new location via the location parameter. Upon completion of the command, a new location will have been created (with only a PERMANENT mapset), and the raster will have been imported with the indicated output name into the PERMANENT mapset. Support for GCPs: In case the image contains GCPs they are written to a POINTS file within an imagery group. They can directly be used for i.rectify. The target option allows you to automatically re-project the GCPs from their own projection into another projection read from the PROJ_INFO file of the location name target.NOTES¶
Import of large files can be significantly faster when setting memory to the size of the input file. The r.in.gdal command does support the following features, as long as the underlying format driver supports it:- Color Table
-
Bands with associated colortables will have the color tables transferred. Note that if the source has no colormap, r.in.gdal in GRASS 5.0 will emit no colormap. Use r.colors map=... color=grey to assign a greyscale colormap. In a future version of GRASS r.in.gdal will likely be upgraded to automatically emit greyscale colormaps.
- Data Types
-
Most GDAL data types are supported. Float32 and Float64 type bands are translated as GRASS floating point cells (but not double precision ... this could be added if needed), and most other types are translated as GRASS integer cells. This includes 16bit integer data sources. Complex (some SAR signal data formats) data bands are translated to two floating point cell layers (*.real and *.imaginary).
- Georeferencing
-
If the dataset has affine georeferencing information, this will be used to set the north, south, east and west edges. Rotational coefficients will be ignored, resulting in incorrect positioning for rotated datasets.
- Projection
-
The datasets projection will be used to compare to the current location or to define a new location. Internally GDAL represents projections in OpenGIS Well Known Text format. A large subset of the total set of GRASS projections are supported.
- Null Values
-
Raster bands for which a null value is recognised by GDAL will have the null pixels transformed into GRASS style nulls during import. Many generic formats (and formats poorly supported by GDAL) do not have a way of recognising null pixels in which case r.null should be used after the import.
- GCPs
-
Datasets that have Ground Control Points will have them imported as a POINTS file associated with the imagery group. Datasets with only one band that would otherwise have been translated as a simple raster map will also have an associated imagery group if there are ground control points. The coordinate system of the ground control points is reported by r.in.gdal but not preserved. It is up to the user to ensure that the location established with i.target has a compatible coordinate system before using the points with i.rectify.
Error Messages¶
"ERROR: Input map is rotated - cannot import."EXAMPLES¶
GTOPO30 DEM¶
To avoid that the GTOPO30 data are read incorrectly, you can add a new line "PIXELTYPE SIGNEDINT" in the .HDR to force interpretation of the file as signed rather than unsigned integers. Then the .DEM file can be imported. Finally, e.g. the 'terrain' color table can be assigned to the imported map with r.colors.GLOBE DEM¶
To import GLOBE DEM tiles (approx 1km resolution, better than GTOPO30 DEM data), the user has to download additionally the related HDR file(s). Finally, e.g. the 'terrain' color table can be assigned to the imported map with r.colors.Worldclim.org¶
To import Worldclim data, the following line has to be added to each .hdr file:HDF¶
The import of HDF bands requires the specification of the individual bands as seen by GDAL:SUBDATASET_1_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km
SUBDATASET_1_DESC=[1200x1200] Fpar_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
SUBDATASET_2_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Lai_1km
SUBDATASET_2_DESC=[1200x1200] Lai_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
out=fpar_1km_2003_06_02
SEE ALSO¶
r.colors, r.in.ascii, r.in.arc, r.in.bin, r.nullREFERENCES¶
GDAL Pages: http://www.gdal.org/AUTHOR¶
Frank Warmerdam (email). Last changed: $Date: 2013-04-18 07:56:53 +0200 (Thu, 18 Apr 2013) $ Full index © 2003-2014 GRASS Development TeamGRASS 6.4.4 |