Hello, i have created a simple graphical model of the r.external work-flow, attached as PNG file. (for presentation purpose) If this is correct, i can add this to the help-pages or Wiki?
Soeren 2010/2/15 Glynn Clements <[email protected]>: > > Michael Barton wrote: > >> >> It is unclear how r.external.out works. Does it make a GDAL-compatible >> >> file appear as a GRASS raster in a mapset? If so, shouldn't this be >> >> r.external.in? (i.e., it makes an external raster usable by GRASS) >> > >> > r.external.out causes new raster maps to be created as files via GDAL. >> > >> > Whereas r.external turns a specific file into a GRASS raster map, >> > r.external.out enables a mode whereby all new rasters are created as >> > files via GDAL. >> > >> > It creates a key-value file named "GDAL" in the mapset directory >> > containing various parameters (output directory, file format, creation >> > parameters). If this file is present, Rast_open_*_new() and >> > Rast_put_*_row() go via GDAL. >> >> So the files can be opened and used subsequently as GRASS files even >> though they are created in a non-GRASS format (e.g., geotiff)? > > Yes. Files created this way are automatically linked as GRASS rasters > as if by r.external. > > -- > Glynn Clements <[email protected]> > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev >
<<attachment: Direct_raster_file_access_grass.png>>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
