1r.in.gdal(1)                  Grass User's Manual                 r.in.gdal(1)
2
3
4

NAME

6       r.in.gdal   -  Imports  raster  data into a GRASS raster map using GDAL
7       library.
8

KEYWORDS

10       raster, import, create location
11

SYNOPSIS

13       r.in.gdal
14       r.in.gdal --help
15       r.in.gdal [-ojeflakcrp]  input=name  output=name   [band=integer[,inte‐
16       ger,...]]    [memory=integer]    [target=name]   [title=phrase]   [off‐
17       set=integer]    [num_digits=integer]    [map_names_file=name]    [loca‐
18       tion=name]    [table=file]    [gdal_config=string]    [gdal_doo=string]
19       [--overwrite]  [--help]  [--verbose]  [--quiet]  [--ui]
20
21   Flags:
22       -o
23           Override projection check (use current location’s projection)
24           Assume that the dataset has same projection as the current location
25
26       -j
27           Perform projection check only and exit
28
29       -e
30           Extend region extents based on new dataset
31           Also updates the default region if in the PERMANENT mapset
32
33       -f
34           List supported formats and exit
35
36       -l
37           Force Lat/Lon maps  to  fit  into  geographic  coordinates  (90N,S;
38           180E,W)
39
40       -a
41           Auto-adjustment for lat/lon
42           Attempt to fix small precision errors in resolution and extents
43
44       -k
45           Keep band numbers instead of using band color names
46
47       -c
48           Create the location specified by the "location" parameter and exit.
49           Do not import the raster file.
50
51       -r
52           Limit import to the current region
53
54       -p
55           Print number of bands and exit
56
57       --overwrite
58           Allow output files to overwrite existing files
59
60       --help
61           Print usage summary
62
63       --verbose
64           Verbose module output
65
66       --quiet
67           Quiet module output
68
69       --ui
70           Force launching GUI dialog
71
72   Parameters:
73       input=name [required]
74           Name of raster file to be imported
75
76       output=name [required]
77           Name for output raster map
78
79       band=integer[,integer,...]
80           Band(s) to select (default is all bands)
81
82       memory=integer
83           Maximum memory to be used (in MB)
84           Cache size for raster rows
85           Default: 300
86
87       target=name
88           Name of GCPs target location
89           Name of location to create or to  read  projection  from  for  GCPs
90           transformation
91
92       title=phrase
93           Title for resultant raster map
94
95       offset=integer
96           Offset to be added to band numbers
97           If 0, no offset is added and the first band is 1
98           Default: 0
99
100       num_digits=integer
101           Zero-padding  of  band  number  by filling with leading zeros up to
102           given number
103           If 0, length will be adjusted to ’offset’  number  without  leading
104           zeros
105           Default: 0
106
107       map_names_file=name
108           Name of the output file that contains the imported map names
109
110       location=name
111           Name for new location to create
112
113       table=file
114           File prefix for raster attribute tables
115           The band number and ".csv" will be appended to the file prefix
116
117       gdal_config=string
118           GDAL configuration options
119           Comma-separated list of key=value pairs
120
121       gdal_doo=string
122           GDAL dataset open options
123           Comma-separated list of key=value pairs
124

DESCRIPTION

126       r.in.gdal  allows  a  user  to  create a GRASS GIS raster map layer, or
127       imagery group, from any GDAL  supported  raster  map  format,  with  an
128       optional title. The imported file may also be optionally used to create
129       a new location.
130
131   GDAL supported raster formats
132       Full details on all GDAL supported formats are available at:
133
134       http://www.gdal.org/formats_list.html
135
136       Selected formats out of the more than 140 supported formats:
137       Long Format Name                              Code           Creation  Georeferencing Maximum file size
138       ---------------------------------------------+-------------+----------+--------------+-----------------
139       ADRG/ARC Digitilized Raster Graphics          ADRG              Yes      Yes          --
140       Arc/Info ASCII Grid                           AAIGrid           Yes      Yes          2GB
141       Arc/Info Binary Grid (.adf)                   AIG               No       Yes          --
142       Arc/Info Export E00 GRID                      E00GRID           No       Yes          --
143       ArcSDE Raster                                 SDE               No       Yes          --
144       ASCII Gridded XYZ                             XYZ               Yes      Yes          --
145       BSB Nautical Chart Format (.kap)              BSB               No       Yes          --
146       CEOS (Spot for instance)                      CEOS              No       No           --
147       DB2                                           DB2               Yes      Yes          No limits
148       DODS / OPeNDAP                                DODS              No       Yes          --
149       EarthWatch/DigitalGlobe .TIL                  TIL               No       No           --
150       ENVI .hdr Labelled Raster                     ENVI              Yes      Yes          No limits
151       Envisat Image Product (.n1)                   ESAT              No       No           --
152       EOSAT FAST Format                             FAST              No       Yes          --
153       Epsilon - Wavelet compressed images           EPSILON           Yes      No           --
154       Erdas 7.x .LAN and .GIS                       LAN               No       Yes          2GB
155       ERDAS Compressed Wavelets (.ecw)              ECW               Yes      Yes
156       Erdas Imagine (.img)                          HFA               Yes      Yes          No limits
157       Erdas Imagine Raw                             EIR               No       Yes          --
158       ERMapper (.ers)                               ERS               Yes      Yes
159       ESRI .hdr Labelled                            EHdr              Yes      Yes          No limits
160       EUMETSAT Archive native (.nat)                MSGN              No       Yes
161       FIT                                           FIT               Yes      No           --
162       FITS (.fits)                                  FITS              Yes      No           --
163       Fuji BAS Scanner Image                        FujiBAS           No       No           --
164       GDAL Virtual (.vrt)                           VRT               Yes      Yes          --
165       Generic Binary (.hdr Labelled)                GENBIN            No       No           --
166       GeoPackage                                    GPKG              Yes      Yes          No limits
167       Geospatial PDF                                PDF               Yes      Yes          --
168       GMT Compatible netCDF                         GMT               Yes      Yes          2GB
169       Golden Software Surfer 7 Binary Grid          GS7BG             Yes      Yes          4GiB
170       Graphics Interchange Format (.gif)            GIF               Yes      No           2GB
171       GRASS Raster Format                           GRASS             No       Yes          --
172       GSat File Format                              GFF               No       No           --
173       Hierarchical Data Format Release 4 (HDF4)     HDF4              Yes      Yes          2GiB
174       Hierarchical Data Format Release 5 (HDF5)     HDF5              No       Yes          2GiB
175       Idrisi Raster                                 RST               Yes      Yes          No limits
176       ILWIS Raster Map (.mpr,.mpl)                  ILWIS             Yes      Yes          --
177       Image Display and Analysis (WinDisp)          IDA               Yes      Yes          2GB
178       In Memory Raster                              MEM               Yes      Yes
179       Intergraph Raster                             INGR              Yes      Yes          2GiB
180       IRIS                                          IRIS              No       Yes          --
181       Japanese DEM (.mem)                           JDEM              No       Yes          --
182       JAXA PALSAR Product Reader (Level 1.1/1.5)    JAXAPALSAR        No       No           --
183       JPEG2000 (.jp2, .j2k)                         JP2OpenJPEG       Yes      Yes
184       JPEG JFIF (.jpg)                              JPEG              Yes      Yes          4GiB
185       KMLSUPEROVERLAY                               KMLSUPEROVERLAY   Yes      Yes
186       MBTiles                                       MBTiles           Yes      Yes          --
187       Meta Raster Format                            MRF               Yes      Yes          --
188       Meteosat Second Generation                    MSG               No       Yes
189       MG4 Encoded Lidar                             MG4Lidar          No       Yes          --
190       Microsoft Windows Device Independent Bitmap   BMP               Yes      Yes          4GiB
191       Military Elevation Data (.dt0, .dt1, .dt2)    DTED              Yes      Yes          --
192       Multi-resolution Seamless Image Database      MrSID             No       Yes          --
193       NASA Planetary Data System                    PDS               No       Yes          --
194       NetCDF                                        netCDF            Yes      Yes          2GB
195       Netpbm (.ppm,.pgm)                            PNM               Yes      No           No limits
196       NITF                                          NITF              Yes      Yes          10GB
197       NLAPS Data Format                             NDF               No       Yes          No limits
198       NOAA NGS Geoid Height Grids                   NGSGEOID          No       Yes
199       NOAA Polar Orbiter Level 1b Data Set (AVHRR)  L1B               No       Yes          --
200       OGC Web Coverage Service                      WCS               No       Yes          --
201       OGC Web Map Service, and TMS, WorldWind, On EaWMS               No       Yes          --
202       OGC Web Map Tile Service                      WMTS              No       Yes          --
203       OGDI Bridge                                   OGDI              No       Yes          --
204       Oracle Spatial GeoRaster                      GEORASTER         Yes      Yes          No limits
205       OziExplorer .MAP                              MAP               No       Yes          --
206       OZI OZF2/OZFX3                                OZI               No       Yes          --
207       PCI Geomatics Database File                   PCIDSK            Yes      Yes          No limits
208       PCRaster                                      PCRaster          Yes      Yes
209       Planet Labs Mosaics API                       PLMosaic          No       Yes          --
210       Portable Network Graphics (.png)              PNG               Yes      No
211       PostGIS Raster (previously WKTRaster)         PostGISRaster     No       Yes          --
212       RadarSat2 XML (product.xml)                   RS2               No       Yes          4GB
213       Rasdaman                                      RASDAMAN          No       No           No limits
214       Rasterlite - Rasters in SQLite DB             Rasterlite        Yes      Yes          --
215       Raster Product Format/RPF (CADRG, CIB)        RPFTOC            No       Yes          --
216       R Object Data Store                           R                 Yes      No           --
217       ROI_PAC Raster                                ROI_PAC           Yes      Yes          --
218       R Raster (.grd)                               RRASTER           No       Yes          --
219       SAGA GIS Binary format                        SAGA              Yes      Yes          --
220       SAR CEOS                                      SAR_CEOS          No       Yes          --
221       Sentinel 1 SAR SAFE (manifest.safe)           SAFE              No       Yes          No limits
222       Sentinel 2                                    SENTINEL2         No       Yes          No limits
223       SGI Image Format                              SGI               Yes      Yes          --
224       SRTM HGT Format                               SRTMHGT           Yes      Yes          --
225       TerraSAR-X Complex SAR Data Product           COSAR             No       No           --
226       TerraSAR-X Product                            TSX               Yes      No           --
227       TIFF / BigTIFF / GeoTIFF (.tif)               GTiff             Yes      Yes          4GiB/None for BigTIFF
228       USGS ASCII DEM / CDED (.dem)                  USGSDEM           Yes      Yes          --
229       USGS Astrogeology ISIS cube (Version 3)       ISIS3             No       Yes          --
230       USGS SDTS DEM (*CATD.DDF)                     SDTS              No       Yes          --
231       Vexcel MFF                                    MFF               Yes      Yes          No limits
232       VICAR                                         VICAR             No       Yes          --
233       VTP Binary Terrain Format (.bt)               BT                Yes      Yes          --
234       WEBP                                          WEBP              Yes      No           --
235       WMO GRIB1/GRIB2 (.grb)                        GRIB              No       Yes          2GB
236
237   Location Creation
238       r.in.gdal attempts to preserve projection  information  when  importing
239       datasets  if  the source format includes projection information, and if
240       the GDAL driver supports it.  If the projection of the  source  dataset
241       does  not  match  the projection of the current location r.in.gdal will
242       report an error message (Projection of dataset does not appear to match
243       current  location)  and  then  report  the  PROJ_INFO parameters of the
244       source dataset.
245
246       If the user wishes to ignore the difference between the apparent  coor‐
247       dinate  system  of  the  source data and the current location, they may
248       pass the -o flag to override the projection check.
249
250       If the user wishes to import the data with the full projection  defini‐
251       tion, it is possible to have r.in.gdal automatically create a new loca‐
252       tion based on the projection and extents of the file being read.   This
253       is accomplished by passing the name to be used for the new location via
254       the location parameter.  Upon completion of the command, a new location
255       will  have  been created (with only a PERMANENT mapset), and the raster
256       will have been imported with the indicated output name into the  PERMA‐
257       NENT mapset.
258
259   Support for Ground Control Points
260       In case the image contains Ground Control Points (GCP) they are written
261       to a POINTS file within an imagery group. They can directly be used for
262       i.rectify.
263
264       The  target option allows you to automatically re-project the GCPs from
265       their own projection into another projection read  from  the  PROJ_INFO
266       file of the location name target.
267
268       If  the  target location does not exist, a new location will be created
269       matching the projection definition of the GCPs. The target of the  out‐
270       put  group  will  be  set to the new location, and i.rectify can now be
271       used without any further preparation.
272
273       Some satellite images (e.g. NOAA/AVHRR, ENVISAT) can  contain  hundreds
274       or  thousands  of  GCPs.  In  these  cases thin plate spline coordinate
275       transformation is recommended, either before import with gdalwarp  -tps
276       or after import with i.rectify -t.
277
278   Map names: Management of offset and leading zeros
279       The offset parameter allows adding an offset to band number(s) which is
280       convenient in case of the import of e.g. a continuous time series split
281       across different input files.
282
283       The  num_digits  parameter allows defining the number of  leading zeros
284       (zero padding) in case of band  numbers  (e.g.,  to  turn  band.1  into
285       band.001).
286

NOTES

288       Import  of  large files can be significantly faster when setting memory
289       to the size of the input file.
290
291       The r.in.gdal command does support the following features, as  long  as
292       the underlying format driver supports it:
293
294        Color Table
295           Bands with associated colortables will have the color tables trans‐
296           ferred.  Note that if the source  has  no  colormap,  r.in.gdal  in
297           GRASS  5.0  will emit no colormap.  Use r.colors map=... color=grey
298           to assign a greyscale colormap.   In  a  future  version  of  GRASS
299           r.in.gdal  will  likely be upgraded to automatically emit greyscale
300           colormaps.
301
302        Data Types
303           Most GDAL data types are supported.  Float32 and Float64 type bands
304           are translated as GRASS floating point cells (but not double preci‐
305           sion ...  this could be added if needed), and most other types  are
306           translated  as  GRASS  integer  cells.  This includes 16bit integer
307           data sources.  Complex (some SAR signal data  formats)  data  bands
308           are  translated  to  two  floating  point  cell  layers (*.real and
309           *.imaginary).
310
311        Georeferencing
312           If the dataset has affine georeferencing information, this will  be
313           used  to  set  the  north,  south, east and west edges.  Rotational
314           coefficients will be ignored, resulting  in  incorrect  positioning
315           for rotated datasets.
316
317        Projection
318           The  datasets  projection  will  be  used to compare to the current
319           location or to define a new location.  Internally  GDAL  represents
320           projections  in  OpenGIS Well Known Text format.  A large subset of
321           the total set of GRASS projections are supported.
322
323        Null Values
324           Raster bands for which a null value is recognised by GDAL will have
325           the  null  pixels transformed into GRASS style nulls during import.
326           Many generic formats (and formats poorly supported by GDAL) do  not
327           have  a  way of recognising null pixels in which case r.null should
328           be used after the import.
329
330        GCPs
331           Datasets that have Ground Control Points will have them imported as
332           a  POINTS  file  associated  with the imagery group.  Datasets with
333           only one band that would otherwise have been translated as a simple
334           raster  map will also have an associated imagery group if there are
335           ground control points.  The coordinate system of the ground control
336           points is reported by r.in.gdal but not preserved.  It is up to the
337           user to ensure that the location established with  i.target  has  a
338           compatible  coordinate  system  before using the points with i.rec‐
339           tify.
340
341        Raster Attribute Tables
342           r.in.gdal can write out  raster  attribute  tables  as  CSV  files.
343           Moreover,  information  in raster attribute tables is automatically
344           imported as long as the field definitions contain information about
345           how to use a field, e.g. for color information or for labels.
346
347       Planned  improvements  to  r.in.gdal  in the future include support for
348       reporting everything known about a dataset if the output  parameter  is
349       not set.
350
351   Error Messages
352       "ERROR: Input map is rotated - cannot import."
353       In  this  case the image must be first externally rotated, applying the
354       rotation info stored in the metadata field of the  raster  image  file.
355       For example, the gdalwarp  software can be used to transform the map to
356       North-up (note, there are several gdalwarp  parameters  to  select  the
357       resampling algorithm):
358       gdalwarp rotated.tif northup.tif
359
360       "ERROR:  Projection  of  dataset  does  not appear to match the current
361       location."
362       You need to create a location whose projection  matches  the  data  you
363       wish  to  import. Try using location parameter to create a new location
364       based upon the projection information in the file. If desired, you  can
365       then  re-project it to another location with r.proj.  Alternatively you
366       can override this error by using the -o flag.
367
368       "WARNING: G_set_window(): Illegal latitude for North"
369       Latitude/Longitude locations in GRASS can not have regions which exceed
370       90°  North  or  South. Non-georeferenced imagery will have coordinates
371       based on the images’s  number  of  pixels:  0,0  in  the  bottom  left;
372       cols,rows in the top right. Typically imagery will be much more than 90
373       pixels tall and so the GIS refuses to import it. If you are  sure  that
374       the  data is appropriate for your Lat/Lon location and intentd to reset
375       the map’s bounds with the r.region module directly after import you may
376       use  the  -l  flag  to  constrain  the map coordinates to legal values.
377       While the resulting bounds and resolution will likely be wrong for your
378       map the map’s data will be unaltered and safe. After resetting to known
379       bounds with r.region you should double check them with  r.info,  paying
380       special attention to the map resolution. In most cases you will want to
381       import into the datafile’s native projection, or into a simple XY loca‐
382       tion  and  use the Georectifaction tools (i.rectify et al.) to properly
383       project into the target location.  The -l flag should only be  used  if
384       you  know the projection is correct but the internal georeferencing has
385       gotten lost, and you know the what  the  map’s  bounds  and  resolution
386       should be beforehand.
387

EXAMPLES

389   ECAD Data
390       The  European  Climate  Assessment  and Dataset (ECAD) project provides
391       climate data for Europe ranging from 1950 - 2015  or  later  (Terms  of
392       use).   To  import the different chunks of data provided by the project
393       as netCDF files, the offset parameter can be used  to  properly  assign
394       numbers  to  the series of daily raster maps from 1st Jan 1950 (in case
395       of importing the ECAD data split into multi-annual  chunks).  The  ECAD
396       data must be imported into a LatLong location.
397
398       By  using  the  num_digits parameter leading zeros are added to the map
399       name numbers, allowing for  chronological  numbering  of  the  imported
400       raster  map  layers,  so  that  g.list lists them in the correct order.
401       Here, use num_digits=5 to have a 5  digit  suffix  with  leading  zeros
402       (00001 - 99999).
403       # Import of ECAD data split into chunks
404       # Import precipitation data
405       r.in.gdal -o input=rr_0.25deg_reg_1950-1964_v12.0.nc output=precipitation num_digits=5 offset=0
406       r.in.gdal -o input=rr_0.25deg_reg_1965-1979_v12.0.nc output=precipitation num_digits=5 offset=5479
407       r.in.gdal -o input=rr_0.25deg_reg_1980-1994_v12.0.nc output=precipitation num_digits=5 offset=10957
408       r.in.gdal -o input=rr_0.25deg_reg_1995-2015_v12.0.nc output=precipitation num_digits=5 offset=16436
409       # Import air pressure data
410       r.in.gdal -o input=pp_0.25deg_reg_1950-1964_v12.0.nc output=air_pressure num_digits=5 offset=0
411       r.in.gdal -o input=pp_0.25deg_reg_1965-1979_v12.0.nc output=air_pressure num_digits=5 offset=5479
412       r.in.gdal -o input=pp_0.25deg_reg_1980-1994_v12.0.nc output=air_pressure num_digits=5 offset=10957
413       r.in.gdal -o input=pp_0.25deg_reg_1995-2015_v12.0.nc output=air_pressure num_digits=5 offset=16436
414       # Import min temperature data
415       r.in.gdal -o input=tn_0.25deg_reg_1950-1964_v12.0.nc output=temperatur_min num_digits=5 offset=0
416       r.in.gdal -o input=tn_0.25deg_reg_1965-1979_v12.0.nc output=temperatur_min num_digits=5 offset=5479
417       r.in.gdal -o input=tn_0.25deg_reg_1980-1994_v12.0.nc output=temperatur_min num_digits=5 offset=10957
418       r.in.gdal -o input=tn_0.25deg_reg_1995-2015_v12.0.nc output=temperatur_min num_digits=5 offset=16436
419       # Import max temperature data
420       r.in.gdal -o input=tx_0.25deg_reg_1950-1964_v12.0.nc output=temperatur_max num_digits=5 offset=0
421       r.in.gdal -o input=tx_0.25deg_reg_1965-1979_v12.0.nc output=temperatur_max num_digits=5 offset=5479
422       r.in.gdal -o input=tx_0.25deg_reg_1980-1994_v12.0.nc output=temperatur_max num_digits=5 offset=10957
423       r.in.gdal -o input=tx_0.25deg_reg_1995-2015_v12.0.nc output=temperatur_max num_digits=5 offset=16436
424       # Import mean temperature data
425       r.in.gdal -o input=tg_0.25deg_reg_1950-1964_v12.0.nc output=temperatur_mean num_digits=5 offset=0
426       r.in.gdal -o input=tg_0.25deg_reg_1965-1979_v12.0.nc output=temperatur_mean num_digits=5 offset=5479
427       r.in.gdal -o input=tg_0.25deg_reg_1980-1994_v12.0.nc output=temperatur_mean num_digits=5 offset=10957
428       r.in.gdal -o input=tg_0.25deg_reg_1995-2015_v12.0.nc output=temperatur_mean num_digits=5 offset=16436
429
430   GTOPO30 DEM
431       To  avoid that the GTOPO30 data are read incorrectly, you can add a new
432       line "PIXELTYPE SIGNEDINT" in the .HDR to force interpretation  of  the
433       file as signed rather than unsigned integers. Then the .DEM file can be
434       imported.  Finally, e.g. the ’terrain’ color table can be  assigned  to
435       the imported map with r.colors.
436
437   GLOBE DEM
438       To  import  GLOBE DEM tiles (approx 1km resolution, better than GTOPO30
439       DEM data), the user  has  to  download  additionally  the  related  HDR
440       file(s).   Finally,  e.g.  the ’terrain’ color table can be assigned to
441       the imported map with r.colors.  See also their DEM portal.
442
443   Raster file import over network
444       Since GDAL 2.x it is possible to import raster data over  network  (see
445       GDAL  Virtual  File  Systems)  including  Cloud Optimized GeoTIFF, i.e.
446       access uncompressed and compressed raster data via  a  http(s)  or  ftp
447       connection.   As an example the import of the global SRTMGL1 V003 tiles
448       at 1 arc second (about 30 meters) resolution, void-filled:
449       r.in.gdal /vsicurl/https://www.datenatlas.de/geodata/public/srtmgl1/srtmgl1.003.tif output=srtmgl1_v003_30m memory=2000
450       g.region raster=srtmgl1_v003_30m -p
451       r.colors srtmgl1_v003_30m color=srtm_plus
452
453   Worldclim.org data
454       To import the BIL data from Worldclim, the following  line  has  to  be
455       added to each .hdr file:
456       PIXELTYPE SIGNEDINT
457
458       To  import  the ESRI Grd data from Worldclim, the broken spatial extent
459       (exceeding the boundaries) needs to be fixed prior to import:
460       # example: tmean dataset
461       gdal_translate -a_ullr -180 90 180 -60 tmean_1 tmean_1_fixed.tif
462       r.in.gdal input=tmean_1_fixed.tif output=tmean_1
463
464   HDF
465       The import of HDF bands requires the specification  of  the  individual
466       bands as seen by GDAL:
467       # Example MODIS FPAR
468       gdalinfo MOD15A2.A2003153.h18v04.004.2003171141042.hdf
469       ...
470       Subdatasets:
471         SUBDATASET_1_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km
472         SUBDATASET_1_DESC=[1200x1200] Fpar_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
473         SUBDATASET_2_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Lai_1km
474         SUBDATASET_2_DESC=[1200x1200] Lai_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
475       ...
476       # import of first band, here FPAR 1km:
477       r.in.gdal HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km \
478                 out=fpar_1km_2003_06_02
479       # ... likewise for other HDF bands in the file.
480

SEE ALSO

482        r.colors, r.import, r.in.ascii, r.in.bin, r.null, t.register
483
484       GRASS GIS Wiki page: Import of Global datasets
485

REFERENCES

487       GDAL Pages: http://www.gdal.org/
488

AUTHOR

490       Frank Warmerdam (email).
491

SOURCE CODE

493       Available at: r.in.gdal source code (history)
494
495       Main  index  | Raster index | Topics index | Keywords index | Graphical
496       index | Full index
497
498       © 2003-2019 GRASS Development Team, GRASS GIS 7.8.2 Reference Manual
499
500
501
502GRASS 7.8.2                                                       r.in.gdal(1)
Impressum