[GRASS5] [bug #992] (grass) g.region Vask problem in lat/long

[Glynn Clements]

Markus Neteler wrote:

> I generated this location from GLOBE DEM30 (user defined window)
> automatically with r.in.gdal (it reads GLOBE DEM30 directly),
> therefore these strange west/east boundaries:
> 
> gdalinfo botswana.bil
> Driver: EHdr/ESRI .hdr Labelled
> Size is 2160, 1920
> Coordinate System is '
> Origin = (16.000000,-13.000000)
> Pixel Size = (0.008333,-0.008333)
> Corner Coordinates:
> Upper Left  (  16.0000000, -13.0000000)
> Lower Left  (  16.0000000, -28.9999936)
> Upper Right (  33.9999928, -13.0000000)
> Lower Right (  33.9999928, -28.9999936)
> Center      (  24.9999964, -20.9999968)
> Band 1 Block=2160x1 Type=Int16, ColorInterp=Undefined
>   NoData Value=-500

Well, that explains where the error is coming from. Perhaps you should
correspond with Frank on this aspect.

> > > Eventually yes. At least the overwriting (see RT followup) isn't nice.
> > 
> >     I slighly change the report:
> >     The field of default region in the g.region menu is too long and writing
> >     into the current region. If there are no objections we should limit the
> >     field length in
> >     src/libes/gis/edit_cellhd.c
> > 
> > What should it be changed to? To whatever space is currently
> > available?
> 
> I think so. Or we have to use two lines
> 
>        |       
>  default_west
>        | current_west
>        |
> In this case default_west may keep its original length. I am not
> sure if that is a good idea.

I'll look into rounding the data before passing it to the formatting
routines. I'll also truncate the string to prevent errors.

> If still needed, I can put the entire location somewhere. Let me know
> (46MB uncompressed).

Not necessary.

-- 
Glynn Clements <glynn.clements at virgin.net>