Add gdal-grass plugin to OSGeo4W

[sbl]

GDAL and the new GDAL-GRASS plugin have been updated to support GRASS 7 raster and vector.

The plugin-code awaits a tiny little fix, which is already in gdal-trunk and will be introduced in the next bugfix release:

​http://permalink.gmane.org/gmane.comp.gis.gdal.devel/39950

I could not find the gdal-grass plugin among the current OSGeo4W-packes and neither among the supported GDAL/OGR formats (in my OSGeo4W installation), so it seems to be missing. Would be great to have it available also on Windows...

[jef]

Is there a reason to keep the gdal-grass driver separate from GRASS? I imaging that gdal-grass could be integrated into GRASS (and (optionally?) be built for the GDAL it depends on anyway).

[sbl]

It could be integrated into the GRASS package, I guess.

Recently, the plugin code was separated out into it`s own repo: ​https://github.com/OSGeo/gdal-grass

From what I understand, devs there dealt with potential circle dependencies of the plugin. So, it should be OK to build separately, but if you perfer it to be part of the GRASS package(s) I could have a look at than...

[jef]

Replying to sbl:

It could be integrated into the GRASS package, I guess.

Recently, the plugin code was separated out into it`s own repo: ​https://github.com/OSGeo/gdal-grass

Sure. That's why I ask.

From what I understand, devs there dealt with potential circle dependencies of the plugin. So, it should be OK to build separately, but if you prefer it to be part of the GRASS package(s) I could have a look at than...

Yes, GRASS needs GDAL to build and GDAL needed GRASS to build the driver. So you couldn't fully build either package and had to first build GDAL without the driver, GRASS with the GDAL w/o driver and then GDAL with the driver.

Now that the driver is separate you can fully build GDAL, GRASS and then driver. I guess the driver should be rebuilt with (each package of) GRASS anyway, so having it in the GRASS package could be beneficial.