[GRASS-dev] Different v.mkgrid table output depending on grid size

[Maris Nartiss]

As nobody objected, I would say - go for it (push to trunk). Still -
do we need so many backports instead of pushing next release?

Thanks, Markus, for keeping head up on such patches,
Maris.

2015-12-27 23:24 GMT+02:00 Markus Neteler <neteler at osgeo.org>:
> Hi Michel, Maris,
>
> On Wed, Dec 2, 2015 at 11:20 PM, Michel Wortmann
> <wortmann at pik-potsdam.de> wrote:
>> Hi Markus, sorry so late. Here is my diff of v.mkgrid/main.c
>>
>> diff --git a/vector/v.mkgrid/main.c b/vector/v.mkgrid/main.c
>> index db733fd..5004fa0 100644
>> --- a/vector/v.mkgrid/main.c
>> +++ b/vector/v.mkgrid/main.c
>> @@ -451,7 +451,7 @@ int main(int argc, char *argv[])
>>                     }
>>                     else {
>>                         sprintf(buf, "( %d, %d, %d )",
>> -                               attCount + 1, i + 1, j + 1);
>> +                              attCount + 1, grid_info.num_rows - i, j + 1);
>>                     }
>>                     if (db_append_string(&sql, buf) != DB_OK)
>>                         G_fatal_error(_("Unable to fill attribute table"));
>>
>>
>> It’s just this single line that is changed.
>> Regards,
>> Michel
>>
>
> Sorry for slow - to avoid that it gets lost, could you please open a ticket at
> https://trac.osgeo.org/grass/
>
> I locally applied your change and the result doesn't differ from
> before. Maybe I did too much backporting today and don't see it any
> more :)
>
> @Maris: or apply to SVN?
>
> thanks
> Markus