[GRASS-dev] r.info -e removes line breaks in output

GRASS GRASS developer
1

Hi,

I am trying to add some metadata (angles and quality indices) to a Sentinel raster map (https://github.com/OSGeo/grass-addons/pull/53).

That works in principle fine, but unfortunately, the stored meta information is not really reusable, because r.info -e seems to remove all line breaks from the comments. Thus, all meta information is returned in one long string. Would it be possible to maintain line breaks that are in the comments?

In r.info without e-flags line breaks seem to be preserved. However new ones are introduced (I guess depending on the length of the line, but that actually varies quite a bit), so output looks a bit messy…

The issue seems to be somewhere here: https://github.com/OSGeo/grass/blob/master/raster/r.info/main.c#L497
Should I open a ticket?

Cheers
Stefan

2

On Mon, Nov 11, 2019 at 12:00 PM Stefan Blumentrath
<Stefan.Blumentrath@nina.no> wrote:

Hi,

I am trying to add some metadata (angles and quality indices) to a Sentinel raster map (https://github.com/OSGeo/grass-addons/pull/53).

That works in principle fine, but unfortunately, the stored meta information is not really reusable, because r.info -e seems to remove all line breaks from the comments. Thus, all meta information is returned in one long string. Would it be possible to maintain line breaks that are in the comments?

In r.info without e-flags line breaks seem to be preserved. However new ones are introduced (I guess depending on the length of the line, but that actually varies quite a bit), so output looks a bit messy...

The issue seems to be somewhere here: https://github.com/OSGeo/grass/blob/master/raster/r.info/main.c#L497
Should I open a ticket?

What if we changed/extended (for compatibility reasons) the metadata
storage to some JSON based approach?
We have that already for the band reference management of satellite data.

Best
Markus