[GRASS5] raster map file format

[Mris Nartis]

What about detaching zoom/pan from region settings for digitising?
That could fix crashes (look for them in bug tracking system). Or
maybee just remove digitising from GRASS and make it yet tighter with
qgis?

Or maybee we need new roadmap? New vision for GRASS future. Target
audience, features etc.?

Just my 2c.

Maris Nartiss.

2005/11/3, Markus Neteler <neteler at itc.it>:
> Hamish wrote:
>
> >Any thoughts on finally rearranging the raster map storage format soon
> >after 6.2 is released? (into $MAPSET/raster/$MAPNAME/cell etc)
> >This will break a lot of modules but it needs to happen some time..
> >
> >Other queued raster format updates could be done at the same time.
> > - majorly rewrite the meta-data setup (see previous email)
> > - Put LZW compression back in?
> > - Start from scratch using netCDF, XML, or some other newfangled system?
> >    (Glynn, Frank, Andrea?, et al: How horrible or apt is GRASS's raster
> >     format anyway? for a format accessed row by row, is it fairly
> >nice?)
> >
> >This needs someone to do it too of course .. :) as well as necessitate
> >bumping us up to GRASS 7.0, FWTIW.
> >
> >But if we decide to do it, we can break it soon after a release and
> >force everyone to fix things as they want their pet module back ;)
> >
> >thoughts?
> >
> >
>
> Yes, let's do the raster layout modification and go for GRASS 7. Other
> things to do
> - the parameter/flags cleanup (more consistency)
> - virtual raster maps via GDAL
> - separation of raster lib (into Rast_*() functions) and G_*() libgis
>
> Markus
>
> _______________________________________________
> grass5 mailing list
> grass5 at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5
>