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
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 ?
best,
Peter
<peter.loewe@gmx.de>
Hi Peter,
On Wed, Aug 1, 2018 at 10:29 AM "Peter Löwe" <peter.loewe@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
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@gmx.de>
Gesendet: Donnerstag, 16. August 2018 um 17:17 Uhr
Von: "Markus Neteler" <neteler@osgeo.org>
An: "Peter Löwe" <peter.loewe@gmx.de>
Cc: "GRASS user list" <grass-user@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@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
On 17/08/18 10:11, "Peter Löwe" wrote:
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.
Do you mean how to georeference without definined ground control points ?
Normally, for creating GCPs, you would use https://grass.osgeo.org/grass74/manuals/wxGUI.gcp.html.
What do you see as a more "modern" approach ?
Moritz
best
Peter
<peter.loewe@gmx.de>
Gesendet: Donnerstag, 16. August 2018 um 17:17 Uhr
Von: "Markus Neteler" <neteler@osgeo.org>
An: "Peter Löwe" <peter.loewe@gmx.de>
Cc: "GRASS user list" <grass-user@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@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
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hi Moritz,
you are of course right, provided that the GRASS GUI can be used.
This case is a bit different, as a scripted workflow is needed, without user input through the GUI.
THe GCPs for all four corners of the image are known as WKT.
The rasters are not strictly north-south / east-west aligned, gdal_translate can't be used, as far as I understand.
Peter
<peter.loewe@gmx.de>
Gesendet: Freitag, 17. August 2018 um 12:57 Uhr
Von: "Moritz Lennert" <mlennert@club.worldonline.be>
An: "Peter Löwe" <peter.loewe@gmx.de>, "Markus Neteler" <neteler@osgeo.org>
Cc: "GRASS user list" <grass-user@lists.osgeo.org>
Betreff: Re: [GRASS-user] workflow to import/georectify binary remote sensing data: POINTS file editing
On 17/08/18 10:11, "Peter Löwe" wrote:
> 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.
Do you mean how to georeference without definined ground control points ?
Normally, for creating GCPs, you would use
https://grass.osgeo.org/grass74/manuals/wxGUI.gcp.html.
What do you see as a more "modern" approach ?
Moritz
>
On 17/08/18 13:07, "Peter Löwe" wrote:
Hi Moritz,
you are of course right, provided that the GRASS GUI can be used.
This case is a bit different, as a scripted workflow is needed, without user input through the GUI.
THe GCPs for all four corners of the image are known as WKT.
Check the i.gcp addon.
Moritz
Moritz,
thanks a bunch for pointing out i.gcp - that's exactly what is needed !
thx,
Peter
<peter.loewe@gmx.de>
Gesendet: Freitag, 17. August 2018 um 16:32 Uhr
Von: "Moritz Lennert" <mlennert@club.worldonline.be>
An: "Peter Löwe" <peter.loewe@gmx.de>
Cc: "Markus Neteler" <neteler@osgeo.org>, "GRASS user list" <grass-user@lists.osgeo.org>
Betreff: Re: Editing POINTS file vs wxGUI.gcp
On 17/08/18 13:07, "Peter Löwe" wrote:
> Hi Moritz,
>
> you are of course right, provided that the GRASS GUI can be used.
> This case is a bit different, as a scripted workflow is needed, without user input through the GUI.
> THe GCPs for all four corners of the image are known as WKT.
>
Check the i.gcp addon.
Moritz