[GRASS-dev] v.buffer don't write metadata and v.info cut comments

Hi all, I would like to add a comment in the metadata of a generated vector map but the content is shortened. I'm in the NorthCarolina mapset, from an ipython shell: {{{ In [1]: !v.buffer --overwrite input=busroute6@PERMANENT output=buff__busroute6 distance=10 In [2]: !v.info buff__busroute6

Re: [GRASS-dev] v.buffer don't write metadata and v.info cut comments

Hi, 2014-12-16 12:30 GMT+01:00 Pietro peter.z...@gmail.com: The command that generate the map is missing! it's not missing. You need to use '-h' flag to print history of commands. Yes, r.info and v.info are inconsistent in printing history of commands. Martin -- Martin Landa

Re: [GRASS-dev] v.buffer don't write metadata and v.info cut comments

On Tue, Dec 16, 2014 at 12:30 PM, Pietro peter.z...@gmail.com wrote: Hi all, I would like to add a comment in the metadata of a generated vector map but the content is shortened. I'm in the NorthCarolina mapset, from an ipython shell: [...] The command that generate the map is missing!

Re: [GRASS-dev] v.buffer don't write metadata and v.info cut comments

Hi, 2014-12-16 14:28 GMT+01:00 Markus Metz markus.metz.gisw...@gmail.com: raster and vector maps. At some stage, this should be synchronized, e.g. raster maps should also have a history and vector maps should support multi-line comments. yes, I would say topic for G8. Martin -- Martin