[GRASSLIST:6068] GRASS60: Warning This is not a valid mapset

Hi all,
  I installed GRASS54 and GRASS60beta2 on my DEBIAN box without any
problem, but when I tried to access to my old data, I obtained a Message
Box saying "Warning This is not a valid mapset" and I can't open my
data.
Is there any changes in the Mapset definitions... is there anyway to get
more details about the warning ?
  Thanks

     D

-----------------------------------------
Stay ahead of the information curve.
Receive GIS news and jobs on your desktop daily.
Subscribe today to the GIS CafeNews newsletter.
[ http://www10.giscafe.com/nl/newsletter_subscribe.php ]
It's informative and essential.

  I installed GRASS54 and GRASS60beta2 on my DEBIAN box without any
problem, but when I tried to access to my old data, I obtained a
Message Box saying "Warning This is not a valid mapset" and I can't
open my data.
Is there any changes in the Mapset definitions... is there anyway to
get more details about the warning ?

perhaps this is it:
??

GRASS 6 now includes support for 3D raster grids. see:
  http://grass.ibiblio.org/grid3d/index.html

To do this we need to have a min,max,res for the z coordinate as well as
x and y.

Running:

g.region -p3

in GRASS 6 will show all the new region settings (usually hidden for
everyday 2D use).

... things like 6.0's NVIZ now require the new region format so it
automatically updates it if needed. So if you go back to 5.4 after using
6.0, the region settings can be strange and new as far as 5.4 is concerned.
(If anybody ever does it, we should release a forward compatible GRASS 5.4.1)

Solution: in 5.4 run 'g.region -d' then go on your way. As long as the
mapset was created in 5.4 this should work ok.

or copy DEFAULT_WIND from the PERMANENT mapset to the WIND file in your
local mapset if outside of GRASS.

maybe just run d.zoom?

Hamish

It tests if $database/$location/PERMANENT/WIND exists.
WIND is probably the only file which can be used to indicate a mapset.
It is true that without WIND it is not a valid mapset.

Radim

DrakeGis wrote:

Hi all,
  I installed GRASS54 and GRASS60beta2 on my DEBIAN box without any
problem, but when I tried to access to my old data, I obtained a Message
Box saying "Warning This is not a valid mapset" and I can't open my
data.
Is there any changes in the Mapset definitions... is there anyway to get
more details about the warning ?
  Thanks

     D

-----------------------------------------
Stay ahead of the information curve.
Receive GIS news and jobs on your desktop daily.
Subscribe today to the GIS CafeNews newsletter.
[ http://www10.giscafe.com/nl/newsletter_subscribe.php ]
It's informative and essential.

  I installed GRASS54 and GRASS60beta2 on my DEBIAN box without any
problem, but when I tried to access to my old data, I obtained a
Message Box saying "Warning This is not a valid mapset" and I can't
open my data.
Is there any changes in the Mapset definitions... is there anyway to
get more details about the warning ?

perhaps this is it:
??

GRASS 6 now includes support for 3D raster grids. see:
  http://grass.ibiblio.org/grid3d/index.html

To do this we need to have a min,max,res for the z coordinate as well as
x and y.

Running:

g.region -p3

in GRASS 6 will show all the new region settings (usually hidden for
everyday 2D use).

... things like 6.0's NVIZ now require the new region format so it
automatically updates it if needed. So if you go back to 5.4 after using
6.0, the region settings can be strange and new as far as 5.4 is
concerned.
(If anybody ever does it, we should release a forward compatible GRASS
5.4.1)

Solution: in 5.4 run 'g.region -d' then go on your way. As long as the
mapset was created in 5.4 this should work ok.

or copy DEFAULT_WIND from the PERMANENT mapset to the WIND file in your
local mapset if outside of GRASS.

maybe just run d.zoom?

Hi,
   Still with the problem.
   First I can't run g.region -p3 in GRASS 6 because of I can't enter (I
don't have a valid mapset :frowning: ).
   I check the DEFAULT_WIND and the WIND files and they are the same, and
still have the problem. Also, in the local mapsets I found not only a
WIND file but also a wind file, Is that right ?
   I will try to create a new Mapset and see what happens....

  Thanks

    D.

-----------------------------------------
Stay ahead of the information curve.
Receive GIS news and jobs on your desktop daily.
Subscribe today to the GIS CafeNews newsletter.
[ http://www10.giscafe.com/nl/newsletter_subscribe.php ]
It's informative and essential.

>> I installed GRASS54 and GRASS60beta2 on my DEBIAN box without any
>> problem, but when I tried to access to my old data, I obtained a
>> Message Box saying "Warning This is not a valid mapset" and I can't
>> open my data.
>> Is there any changes in the Mapset definitions... is there anyway
>to > get more details about the warning ?

..

> GRASS 6 now includes support for 3D raster grids. see:
> http://grass.ibiblio.org/grid3d/index.html

..

> ... things like 6.0's NVIZ now require the new region format so it
> automatically updates it if needed. So if you go back to 5.4 after
> using 6.0, the region settings can be strange and new as far as 5.4
> is concerned.
> (If anybody ever does it, we should release a forward compatible
> GRASS 5.4.1)

..

   Still with the problem.
   First I can't run g.region -p3 in GRASS 6 because of I can't enter
   (I
don't have a valid mapset :frowning: ).

It fails in GRASS 6?? That ain't right. what happens when you do

g.region rast=some_map

or

g.region rast=some_map@other_mapset

?

I check the DEFAULT_WIND and the WIND files and they are the same,
and
still have the problem.

In that case 'g.region -d' will fail as DEFAULT_WIND is broken too?

can you post the file here?

Also, in the local mapsets I found not only a WIND file but also a
wind file, Is that right ?

yes.

   I will try to create a new Mapset and see what happens....

this starts out by copying the DEFAULT_WIND file to the mapset's WIND
file.. if your DEFAULT_WIND is bad, the new mapset will be bad as well.
(but do try)

I was switching between 6.0 and 5.4 yesterday.. the need for a forward
compatible 5.4.1 is fairly clear if people are going to continue to use
the 5.4 line.

Hamish