[GRASS-dev] Re: GRASS6.4.1

Markus Metz markus.metz.giswork at googlemail.com
Tue Nov 23 03:21:38 EST 2010


Markus Neteler wrote:
> On Mon, Nov 22, 2010 at 12:11 PM, Benjamin Ducke
> <benjamin.ducke at oxfordarch.co.uk> wrote:
>> Would it be possible to also sync r.in|out.gdal
>
> r.in.gdal: already identical
> r.out.gdal: only %f changed to %g many times (I would not backport to
> not ruin all translations
>
>> and v.in|out.ogr from 6.5?
>
> v.out.ogr: contains your improvements, not yet backported (has it been
> sufficiently tested?)
>
> v.in.ogr: contains this relevant fix (?):
>
> diff -ru '--exclude=.svn' grass64_release/vector/v.in.ogr/geom.c
> grass65_release/vector/v.in.ogr/geom.c
> --- grass64_release/vector/v.in.ogr/geom.c      2010-10-09 21:50:43.489449120 +0200
> +++ grass65_release/vector/v.in.ogr/geom.c      2010-09-22 09:25:14.917974961 +0200
> @@ -301,9 +301,9 @@
>            otype = GV_BOUNDARY;
>
>        if (split_distance > 0 && otype == GV_BOUNDARY)
> -           split_line(Map, otype, Points, BCats);
> +           split_line(Map, otype, Points, Cats);
>        else
> -           Vect_write_line(Map, otype, Points, BCats);
> +           Vect_write_line(Map, otype, Points, Cats);
>
>        /* Isles */
>        IPoints =
>
This fix is already included in 6.4 as of r43710. Please update your local copy.

About v.out.ogr, FWIW, I have been using it regularly and it works
fine, but I did not do in-depth testing. I would favor backporting
because of the new auto feature and I think a number of memory leaks
are still open in the 6.4 v.out.ogr.

Markus M


More information about the grass-dev mailing list