[GRASS-user] workflow to import/georectify binary remote sensing data: POINTS file editing

["Peter Löwe"]

Hi Markus, all,

thanks for the feedback. The new temporary location option is a great feature.

However, I wonder whether having to manually create a POINTS file within the locations file structure is (still) the proper way to handle the rectification process in GRASS 7.x. This approach dates back to GRASS 4.x. There are no references to it in the recent documentation, so its kind of a (old-fashioned?) hack.
   
best
Peter

<peter.loewe at gmx.de>


> Gesendet: Donnerstag, 16. August 2018 um 17:17 Uhr
> Von: "Markus Neteler" <neteler at osgeo.org>
> An: "Peter Löwe" <peter.loewe at gmx.de>
> Cc: "GRASS user list" <grass-user at lists.osgeo.org>
> Betreff: Re: [GRASS-user] workflow to import/georectify binary remote sensing data
>
> Hi Peter,
> 
> On Wed, Aug 1, 2018 at 10:29 AM "Peter Löwe" <peter.loewe at gmx.de> wrote:
> > Hello list,
> >
> > here is a question about what's currently the most effective way to ingest binary raster data which need to be georectified.
> >
> > The data source are calibrated weather radar precipitation rasters (lots of them), which come in a well documented binary format (+ GCPs), which is not (yet) supported by gdal.
> >
> > A "classical" approach could be:
> >
> > 1) Create XY location as source
> > 2) Create LatLon location as target
> 
> (probably a metric projection would be better?)
> 
> > 3) Ingest data via r.in.bin (to skip over file header) into XY location
> > 4) Use GCP to set up i.rectify within XY location
> > 5) Apply i.rectify
> > 6) Discard XY-location and continue work in LatLon location
> >
> > In there a more effective way, probably without using a XY location ?
> 
> Perhaps the new:
> grass75 --tmp-location ...
> 
> See
> https://grass.osgeo.org/grass75/manuals/grass7.html#batch-jobs-with-the-exec-interface
> --> Using temporary location
> ?
> 
> It also supports XY locations and all could be done in a script.
> 
> Best
> Markus
>