[GRASS5] GRASS 6.0.1 release schedule

[Paul Kelly]

On Sat, 2 Jul 2005, Maciek Sieczka wrote:

>>> cs2cs doesn't see GRASS's NTv2 grid files. see:
>>>   http://bugzilla.remotesensing.org/show_bug.cgi?id=834
>> 
>> Fixed by Paul. I have lightly tested; don't know if it has been applied
>> to the 6.0.x release branch.

It hasn't. I hesitated to do it because it changes the output of
"g.proj -jf" to make it machine-specific (path to gridshift files 
hard-coded) and someone may be relying on the old behaviour so it may not 
be a good idea to change it. But when I think about it more, the old 
behaviour often didn't work so maybe it could be justified to merge the 
patch.

> r.proj works ONLY when source and target mapset names are identical
> http://intevation.de/rt/webrt?serial_num=3362&display=History

That has been fixed (revert change to lib/gis/asprintf.c using G_tempfile) 
I didn't resolve the bug report as there was a discussion about 
G_tempfile() usage ongoing.

> d.where -l is giving wrong results
> http://intevation.de/rt/webrt?serial_num=3172&display=History
> (Paul said it shouldn't be hard to fix yet the discussion stopped at some
> point. Quite important - GIS should handle any coordinates conversion 
> perfect.)

I've looked into this a bit more but still haven't been able to track it 
down. See comment to bug report CCed to grass5 list.

> zooming in v.digit changes resolution in region settings
> http://intevation.de/rt/webrt?serial_num=2962&display=History

Just a little comment that I think it is a nice feature that v.digit shares
the region with the location rather than the 5.x and earlier v.digit which 
by default used the region in the header of the vector map. But obviously 
more thought needs to go into how the location region and the map region 
interact and I don't use v.digit any more so am unable to contribute.

> r.info displays the '(zone 0)' message in any location
> http://intevation.de/rt/webrt?serial_num=3054&display=History
> (A lot mess there, sorry! Go to the bottom of the page, there is a fresh
> comment by me).

I suppose that dates back to when UTM was the only projection GRASS 
supported and thus zone was always relevant. I wouldn't like to try fixing 
it without risking breaking something else. It is a harmless "feature", is 
it not?