[GRASS5] WIND/WIND3

GRASS GIS GRASS GIS developer
1

I want to merge WIND3 into WIND but then GRASS < 5.7 cannot read WIND which was written in GRASS 5.7. Any idea?

Radim

2

On Thu, Dec 09, 2004 at 03:37:48PM +0100, Radim Blazek wrote:

I want to merge WIND3 into WIND but then GRASS < 5.7 cannot read WIND
which was written in GRASS 5.7. Any idea?

It seems that there are no objections.

In any case the user can simply modify the WIND file and eliminate
the additional lines if s/he wants to go back to an older GRASS release.

Markus

3

WIND was extended to keep also 3D values. Different resolutions are maintained for 2D and 3D.

g3.region, g3.setregion and g3.createwind are removed.

g.region has new oprions:
Flags:
   -3 Print also 3D
Parameters:
          t Value for the top edge
          b Value for the bottom edge
       res3 3D grid resolution (north-south, east-west and top-bottom)
      tbres Top-bottom grid resolution
   raster3d Set region to match this 3D raster map (both 2D and 3D
    values)

Please test, if you work with 3D rasters.

Radim

4

> I want to merge WIND3 into WIND but then GRASS < 5.7 cannot read
> WIND which was written in GRASS 5.7. Any idea?

It seems that there are no objections.

In any case the user can simply modify the WIND file and eliminate
the additional lines if s/he wants to go back to an older GRASS
release.

Shall we modify the 5.4 cvs tree so that it will ignore the new lines?
That way if there is ever a 5.4.1 etc things will be better....
I expect that we will find one bad bug which might necessitate a 5.4.1
some day.

Hamish

5

Hamish wrote:

I want to merge WIND3 into WIND but then GRASS < 5.7 cannot read
WIND which was written in GRASS 5.7. Any idea?

It seems that there are no objections.

In any case the user can simply modify the WIND file and eliminate
the additional lines if s/he wants to go back to an older GRASS
release.

Shall we modify the 5.4 cvs tree so that it will ignore the new lines?
That way if there is ever a 5.4.1 etc things will be better....
I expect that we will find one bad bug which might necessitate a 5.4.1
some day.

It is desirable to fix 5.4 branch. In fact, there is a bug somewhere in g.region or gis library - if the WIND file is corrupted or contains unknown items, DEFAULT_WIND is used without warning in both 5.4/5.7.

Radim