File: README.md

package info (click to toggle)
gdal-grass 2.0.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,044 kB
  • sloc: python: 2,240; cpp: 1,954; makefile: 18
file content (115 lines) | stat: -rw-r--r-- 3,632 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
# Introduction

Description: GRASS GIS extension for the GDAL library

GDAL is a translator library for raster geospatial data formats.
As a library, it presents a single abstract data model to the
calling application for all supported formats. This extension
provides access to GRASS data via GDAL.

This package contains the two standalone GDAL-GRASS GIS drivers,
the [raster driver](docs/grass_raster.md) and the [vector driver](docs/grass_vector.md)
for [GRASS GIS](http://grass.osgeo.org/) raster and vector file support
in [GDAL](https://gdal.org/).

This approach avoids circular dependencies with GRASS depending on GDAL,
but GDAL with GRASS support depending on GRASS. With this driver package
you configure and install GDAL normally, then build and install GRASS normally
and finally build and install this driver in
[GDAL's "autoload" directory](https://gdal.org/user/configoptions.html#driver-management).

## Installation

To build this driver it is necessary for it to find GDAL and GRASS
support files.

**Building with CMake:**

```bash
cd gdal-grass
mkdir build && cd build
cmake ..
cmake --build .
cmake --install .
```

CMake usually works out the location of GDAL and GRASS, but at times you
may need/wish to set some configurations manually, e.g.:

```bash
cmake .. -DAUTOLOAD_DIR=/opt/local/lib/gdalplugins \
         -DGDAL_CONFIG_PREFER_PATH=/opt/local/bin \
         -DGRASS_BIN_PREFER_PATH=/opt/local/bin
```

## Usage

Set the driver path (e.g. in $HOME/.bashrc):

```bash
GDAL_DRIVER_PATH="/usr/lib/gdalplugins"
```

Access GRASS GIS raster data from GDAL:

```bash
gdalinfo $HOME/grassdata/nc_spm_08_grass7/PERMANENT/cellhd/elevation
```

Access GRASS GIS vector data from GDAL-OGR:

```bash
ogrinfo -so -al $HOME/grassdata/nc_spm_08_grass7/PERMANENT/vector/zipcodes/head
```

## Where is the gdal-grass driver available?

- Linux: <https://repology.org/project/gdal-grass/versions>
- Windows: <https://trac.osgeo.org/osgeo4w/>
- other operating systems: please add here

## Version number has been restarted

Note that during the transit of this driver out of core GDAL we have
decided to reset the version numbering back to 1.

So: older packages show 3.x which the new driver is 1.x (or later).

## Release management

List of [milestones](https://github.com/OSGeo/gdal-grass/milestones).

## Tracking upstream changes

The release policies of the GDAL-GRASS driver are (so far) fairly simple:

- we follow the GDAL development for their breaking changes:
  - as of 2022, any GDAL 2+ and GDAL 3+ version is compliant, with GDAL 3+ recommended.
- we follow the GRASS GIS development for their breaking changes:
  - as of 2022, any GRASS GIS 7+ and GRASS GIS 8+ version is compliant,
    with GRASS GIS 8+ recommended.

We expect low maintenance needs for this driver.

## Using milestones

For easier planning, each issue and pull request will be assigned
to a [milestone](https://github.com/OSGeo/gdal-grass/milestones).

## QA / CI

Any pull request opened in this repository is compiled and tested with
[GitHub Actions](https://github.com/OSGeo/gdal-grass/actions) against
the GDAL version included in Ubuntu (see related
[CI workflow](https://github.com/OSGeo/gdal-grass/blob/main/.github/workflows/ubuntu.yml)).
Improvements and other workflows are welcome, ideally as
a [pull request](https://github.com/OSGeo/gdal-grass/pulls).

## Found a bug?

Please open an [issue](https://github.com/OSGeo/gdal-grass/issues) describing
the problem along with a reproducible example.

## Who is involved here?

Please see the list of [contributors](https://github.com/OSGeo/gdal-grass/graphs/contributors).