[GRASS-dev] r.in.gdal problems

[Markus GRASS]

Laura Toma wrote:
> Markus,
>
>
> Here is what the cellhd contains (it seems correct).
>
> proj:       3
> zone:       0
> north:      61:00:01.5N
> south:      9:59:58.5N
> east:       179:59:58.5W
> west:       179:59:58.5E
That's the problem. g.region or some underlying function thinks that
this raster starts at 179:59:58.5E and extends towards east until
179:59:58.5W, giving a total extend of 0:00:03 degrees longitude instead
of 363 degrees longitude. Longitude values larger than 180E or smaller
than 180E are somewhere wrapped around. As Hamish said, the safest would
probably be "gdaltranslate -srcwin 1 0 431999 61201" to chop off the
first and last column. Not so sure if it is sufficient to chop off only
the first or only the last column. Then r.in.gdal again.

BTW, the current east and west bounds are perfectly legal in grass and
allow a raster to smoothly cross the 180E/W border. So you could create
another DEM with e.g. east=90:00:01.5W and west=90:00:01.5E going over
the 180E/W border.

Good luck with that DEM:-)

Markus M

> cols:       432001
> rows:       61201
> e-w resol:  0:00:03
> n-s resol:  0:00:03
> format:     3
> compressed: 1
>
>  but r.info gives:
>    Projection: Latitude-Longitude                                      |
>  |            N: 61:00:01.5N    S: 9:59:58.5N   Res:
> 0:00:03                  |
>  |            E: 179:59:58.5W    W: 179:59:58.5E   Res:
> 0:00:00.000007        |
>
>
> so for some reason the ewres is messed up.
>