[GRASS-dev] g.gui.metadata - wrong bounds if not in latlon

When creating a new metadata file (INSPIRE template) for a raster layer the bounds are automatically filled in (under the Geographic tab). The bounds are given in the units of that mapset. For example, create a metadata file for a layer in the nc_basic_spm_grass7 mapset and the bounds filled in are given in meters.

However, bounds should always be given in decimal degrees (as is also stated in the tooltip help). Besides being the standard, only if given in decimals the map in the pdf output is produced with extent.

Would it be possible to have the tool fill in the bounds in decimal degrees, independent of the projection details of the mapset? If so, should I create a ticket for that?

In addition to the issue mentioned below, it seems the fields for N, S, E, W are mixed up in the GUI?

west bound => north bound

south bound => south bound

south bound => east bound

north bound => west bound

Just to be clear, what should be changed is the names of the fields in the GUI (in the Geographic tab).

ยทยทยท

On Tue, Dec 22, 2015 at 2:11 PM, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:

When creating a new metadata file (INSPIRE template) for a raster layer the bounds are automatically filled in (under the Geographic tab). The bounds are given in the units of that mapset. For example, create a metadata file for a layer in the nc_basic_spm_grass7 mapset and the bounds filled in are given in meters.

However, bounds should always be given in decimal degrees (as is also stated in the tooltip help). Besides being the standard, only if given in decimals the map in the pdf output is produced with extent.

Would it be possible to have the tool fill in the bounds in decimal degrees, independent of the projection details of the mapset? If so, should I create a ticket for that?