landam / grass-gis-git-migration-test

0 stars 0 forks source link

r.to.vect: Flag -e: Erase vector map if empty #130

Open landam opened 5 years ago

landam commented 5 years ago

Reported by martin on 17 Aug 2014 22:04 UTC Avoid creating a pile of empty vector maps upon vectorization of a non-rectangular image in smaller chunks.

GRASS GIS version and provenance

svn-releasebranch70

Migrated-From: https://trac.osgeo.org/grass/ticket/2394

landam commented 5 years ago

Comment by neteler on 17 Aug 2014 22:20 UTC An option might be to add a new flag

-e: Erase new vector map if empty

Perhaps there are better options?

landam commented 5 years ago

Comment by @landam on 17 Aug 2014 22:24 UTC Replying to [comment:1 neteler]:

Perhaps there are better options?

Just delete the output map automatically if it's empty and print a warning?

landam commented 5 years ago

Comment by neteler on 17 Jan 2015 12:39 UTC Does this module lack the error handler like:

Vect_set_error_handler_io(&In, &Out);

?

landam commented 5 years ago

Modified by @landam on 12 May 2016 06:44 UTC

landam commented 5 years ago

Comment by @landam on 23 Aug 2016 12:57 UTC In [changeset:"69234\"] https://trac.osgeo.org/grass/changeset/69234:

r.to.vect: delete output on error (see #130) - merge https://trac.osgeo.org/grass/changeset/69233 from trunk
landam commented 5 years ago

Comment by @landam on 23 Aug 2016 12:58 UTC Replying to [comment:3 neteler]:

Does this module lack the error handler like:

Vect_set_error_handler_io(&In, &Out);

Fixed, anyway this function just delete output map only on failure.

landam commented 5 years ago

Comment by @landam on 23 Aug 2016 13:00 UTC In [changeset:"69235\"] https://trac.osgeo.org/grass/changeset/69235:

r.to.vect: delete output on error (see #130) - merge https://trac.osgeo.org/grass/changeset/69233 from trunk
landam commented 5 years ago

Modified by @landam on 23 Aug 2016 13:00 UTC

landam commented 5 years ago

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:53 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:08 UTC Ticket retargeted after milestone closed