Upgrading GRASS database
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 LZW removal 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 LZW removal 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 addon).
(note: also available in GRASS GIS 7 as addons: v.convert (for all maps, use v.convert.all addon)).
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
Raster: No changes. However, it is recommended
Raster3D: No changes.
Vector: The DBF file default backend has been replaced to SQLite. While conversion is not mandatory it is highly recommended. See Convert all GRASS 6 vector maps to GRASS 7 for an automated conversion.
Migrating from GRASS 7 to GRASS 8
Raster: Semantic labels have been added. Due to added internal range files it is recommended to run r.support with -s flag on each raster map to update the internal statistic files. No incompatible format changes.
Raster3D: No changes.
Vector: No changes.
Temporal: Semantic labels have been added and are supported by temporal GRASS GIS modules. Users need to run t.upgrade in mapsets where they have space-time datasets and this tool will take care of the needed changes.
See also: GRASS 8 planning: ideas
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.