Upgrading GRASS database: Difference between revisions
mNo edit summary |
|||
Line 33: | Line 33: | ||
=== Migrating from GRASS 6 to GRASS 7 === | === Migrating from GRASS 6 to GRASS 7 === | ||
'''Raster:''' No changes. | |||
''' | '''Raster3D:''' No changes. | ||
'''Vector:''' You need to rebuild the topology with {{cmd|v.build|version=70}} (for all maps automatically: {{cmd|v.build.all|version=70}}). | |||
=== Migrating from GRASS 7 to GRASS 8 === | |||
So far GRASS GIS 8 is not yet under development. | |||
See [https://trac.osgeo.org/grass/wiki/Grass8Planning GRASS 8 planning: ideas] | |||
== Troubleshooting == | == Troubleshooting == |
Revision as of 20:36, 26 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
Raster: No changes.
Raster3D: No changes.
Vector: You need to rebuild the topology with v.build (for all maps automatically: v.build.all).
Migrating from GRASS 7 to GRASS 8
So far GRASS GIS 8 is not yet under development.
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.