[GRASS-user] Debugging a r.gdal import error

Rich Shepard rshepard at appl-ecosys.com
Mon Sep 23 15:34:00 PDT 2019

On Mon, 23 Sep 2019, Markus Neteler wrote:

> Well, without error message nor link to the data it is hard to say.
> In addition, it is usually worthwhile to check a dataset with gdalinfo.


I'm dealing with two separate issues: r.in.gdal/r.import unable to read
hdr.adf and maps that are supposed to fit tightly to the border of a topo
quad rectangle don't. I'll deal with the latter issue first.

I separated the orginal bare-earth dataset for one portion of the topo quad
and uploaded it to fileconvory.com
Even xz compressed it's 550MB large. It will be available at that URL for 5

The output of gdalinfo -proj4 on the w* file is the same as that in the
prj.adf file.

My workflow started with creating a new location using the prj.adf file to
set the projection. Then I applied r.in.gdal to the hdr.adf. Displaying the
imported file shows it is slightly rotated clockwise (see attached file
h5clatsop.png). The other two maps in this topo quad import and display
correctly (the three can be seen in the attached file, 45123a5_clatsop.png.

I'm at a loss to understand why the imported map is not square with the topo
boundary. The gdalinfo -proj4 results (attached) show different coordinates
for the northwest and southwest but the OLC data coordinator tells me the
map displays correctly for him and one of his colleagues.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: h5clatsop.png
Type: image/png
Size: 115547 bytes
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190923/835a063c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 45123h5-map.png
Type: image/png
Size: 179347 bytes
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190923/835a063c/attachment-0003.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gdalinfo-results.txt
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190923/835a063c/attachment-0001.txt>

More information about the grass-user mailing list