Upgrading GRASS database: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
No edit summary
Line 33: Line 33:
=== Migrating from GRASS 6 to GRASS 7 ===
=== Migrating from GRASS 6 to GRASS 7 ===


''IMPORTANT: GRASS 7 is NOT recommended for production use as it is under heavy development.''
<--! ''IMPORTANT: GRASS 7 is NOT recommended for production use as it is under heavy development.'' # commenting as I don't think it applies any longer-->


'''Raster:''' No changes (yet) but format update planned.
'''Raster:''' No changes (yet) but format update planned.

Revision as of 09:47, 23 April 2015

Upgrading the GRASS database from older to recent GRASS versions

Migrating from GRASS 4 to GRASS 5

Raster: The LZW compression has been removed which requires a format conversion: see announcement from Jan. 2001.

Raster3D: No changes.

Sites: No changes.

Vector: You need to rebuild the topology with v.support.

Migrating from GRASS 4 to GRASS 6

Raster: The LZW compression has been removed which requires a format conversion: see announcement from Jan. 2001.

Raster3D: No changes.

Sites: Sites have been deprecated and are handled as vector points. Convert sites maps to vector maps with v.in.sites (for all maps, use v.in.sites.all).

Vector: You need to convert the format with v.convert (for all maps, use v.convert.all).

Migrating from GRASS 5 to GRASS 6

Raster: No relevant changes.

Raster3D: No changes.

Sites: Sites have been deprecated and are handled as vector points. Convert sites maps to vector maps with v.in.sites (for all maps, use v.in.sites.all).

Vector: You need to convert the format with v.convert (for all maps, use v.convert.all).

Migrating from GRASS 6 to GRASS 7

<--! IMPORTANT: GRASS 7 is NOT recommended for production use as it is under heavy development. # commenting as I don't think it applies any longer-->

Raster: No changes (yet) but format update planned.

Raster3D: No changes.

Vector: You need to rebuild the topology with v.build.

Troubleshooting

  • "XXX is not a valid mapset" error:
This normally indicates that the directory lacks a WIND file. Copying the DEFAULT_WIND file (if it exists) to WIND should suffice.