[GRASS-dev] Planning GRASS GIS 7.0.0RC1

Markus Neteler neteler at osgeo.org
Mon Jan 19 09:08:33 PST 2015

On Mon, Jan 19, 2015 at 5:46 PM, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> On Sun, Jan 18, 2015 at 5:49 PM, Markus Neteler <neteler at osgeo.org> wrote:
>> >> If I turn the tests into a test suite script, I will use a vector from
>> >> the the full version of the North Carolina sample dataset. Is this ok?
>> >
>> > This is ok. MarkusN says we should use the new dataset but I think it is
>> > not
>> > yet stable.
>> I would invite everybody to switch to these simplified names:
>> http://trac.osgeo.org/grass/wiki/SampleDataset
>> At page bottom download the dataset (done by Helena).
> Is it stable enough?

What is "stable"? The names, the size of the package or the selection of maps?

> Anyway, first we have to solve the challenge of having
> the maps in different mapsets. How do you get them in examples and tests?
> Use name of mapset? Or expect everything to be on path?

Probably a simple "g.mapsets" call would be enough to get it in.

> Once we decide to switch (for example in 7.1/trunk) we should do it
> officially, so we avoid the unclear situation caused by full NC and basic NC
> where the locations were incompatible and it was not defined which one to
> use.

I haven't used NC basic at all but would be happy to replace (all) my
examples from full NC with the simplified names.

> Which data you use when running the tests on you computer is your choice, so
> you can experiment with any dataset and develop your tests with the dataset
> which will be used in the future.

Yes but the point is that we need to switch to the simplified names as
suggested by Helena (maybe with your collaboration in your lab):

At this point I could update the "Piemonte" location (also on the Web
site) accordingly.

> I might be able to improve location handling in tests next month, or at
> least add the new NC and basic NC locations to my test server to accommodate
> the different tests (before the situation will stabilize).

I am not sure what we are waiting for.


More information about the grass-dev mailing list