[GRASS-dev] <GSoC 2015> <Improved metada for GRASS GIS> <week 4>

GRASS GIS GRASS GIS developer
1

Hi,
below is my report for “Improved metadata for GRASS GIS” project.

  1. What do I have completed this week?
  • I have finished support of metada for temporal framework.
  1. What am I going to achieve for next week?
  • Testing, debugging temporal metadata management
  • To make smome improvements for temporal metadata management
  • Main plan for next week is to start with designing pycsw catalogue browser
  1. Is there any blocking issue?
  • I spent more time than I expected with ISO 19108 documentation
2

Hi Matej,

Thank you for the updates.

I have one question concerning the metadata templates: do I understand correctly that by default, neither the basic, nor the inspire template contain a reference to the projection system ?

IIUC, INSPIRE currently does not impose this, but I don't really understand how such basic information can be missing from the metadata. What help is the bounding box info, if we don't know in which CRS it is ?

But maybe I'm just missing something...

Moritz

On 21/06/15 21:04, Matej Krejci wrote:

Hi,
below is my report for "Improved metadata for GRASS GIS" project.

1) What do I have completed this week?

  * I have finished support of metada for temporal framework.

2) What am I going to achieve for next week?

  * Testing, debugging temporal metadata management
  * To make smome improvements for temporal metadata management
  * Main plan for next week is to start with designing pycsw catalogue
    browser

3) Is there any blocking issue?

  * I spent more time than I expected with ISO 19108 documentation

3

Most of the local implementations of best practices for metadata that I have seen include projection information. Where I work, there are 6 possible projections that are commonly used.

Doug

···

On Mon, Jun 22, 2015 at 4:18 AM, Moritz Lennert <mlennert@club.worldonline.be> wrote:

Hi Matej,

Thank you for the updates.

I have one question concerning the metadata templates: do I understand correctly that by default, neither the basic, nor the inspire template contain a reference to the projection system ?

IIUC, INSPIRE currently does not impose this, but I don’t really understand how such basic information can be missing from the metadata. What help is the bounding box info, if we don’t know in which CRS it is ?

But maybe I’m just missing something…

Moritz

On 21/06/15 21:04, Matej Krejci wrote:

Hi,
below is my report for “Improved metadata for GRASS GIS” project.

  1. What do I have completed this week?
  • I have finished support of metada for temporal framework.
  1. What am I going to achieve for next week?
  • Testing, debugging temporal metadata management
  • To make smome improvements for temporal metadata management
  • Main plan for next week is to start with designing pycsw catalogue
    browser
  1. Is there any blocking issue?
  • I spent more time than I expected with ISO 19108 documentation

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

–

Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.gov

The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.

4

Hi,

···

On Mon, Jun 22, 2015 at 10:18 AM, Moritz Lennert <mlennert@club.worldonline.be> wrote:

Hi Matej,

Thank you for the updates.

I have one question concerning the metadata templates: do I understand correctly that by default, neither the basic, nor the inspire template contain a reference to the projection system ?

IIUC, INSPIRE currently does not impose this, but I don’t really understand how such basic information can be missing from the metadata. What help is the bounding box info, if we don’t know in which CRS it is ?

I agree that it sounds strange, however the bounding box is given in geographic (unprojected) coordinates, and the ISO 19115:2003, where the GeographicBoundingBox comes from, reads (B.3.2.1): "geographic position of the dataset NOTE This is only an approximate reference so specifying the coordinate reference system is unnecessary "

–

Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.

5

On 22/06/15 15:40, Margherita Di Leo wrote:

Hi,

On Mon, Jun 22, 2015 at 10:18 AM, Moritz Lennert
<mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>> wrote:

    Hi Matej,

    Thank you for the updates.

    I have one question concerning the metadata templates: do I
    understand correctly that by default, neither the basic, nor the
    inspire template contain a reference to the projection system ?

    IIUC, INSPIRE currently does not impose this, but I don't really
    understand how such basic information can be missing from the
    metadata. What help is the bounding box info, if we don't know in
    which CRS it is ?

I agree that it sounds strange, however the bounding box is given in
geographic (unprojected) coordinates, and the ISO 19115:2003, where the
GeographicBoundingBox comes from, reads (B.3.2.1): "geographic position
of the dataset NOTE This is only an approximate reference so specifying
the coordinate reference system is unnecessary "

Using g.gui.metadata on the hospitals map in nc_spm_08, I get:

       <gmd:extent>
                 <gmd:EX_Extent>
                     <gmd:geographicElement>
                         <gmd:EX_GeographicBoundingBox>
                             <gmd:westBoundLongitude>
                                 <gco:Decimal>308097.937400562</gco:Decimal>
                             </gmd:westBoundLongitude>
                             <gmd:eastBoundLongitude>
                                 <gco:Decimal>20235.5644005626</gco:Decimal>
                             </gmd:eastBoundLongitude>
                             <gmd:southBoundLatitude>
                                 <gco:Decimal>914347.8748615</gco:Decimal>
                             </gmd:southBoundLatitude>
                             <gmd:northBoundLatitude>
                                 <gco:Decimal>156998.1718615</gco:Decimal>
                             </gmd:northBoundLatitude>
                         </gmd:EX_GeographicBoundingBox>
                     </gmd:geographicElement>
                 </gmd:EX_Extent>
             </gmd:extent>

Looks like projected coordinates to me...

Moritz

6

On Mon, Jun 22, 2015 at 4:02 PM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:

On 22/06/15 15:40, Margherita Di Leo wrote:

Hi,

On Mon, Jun 22, 2015 at 10:18 AM, Moritz Lennert
<mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>>
wrote:

    Hi Matej,

    Thank you for the updates.

    I have one question concerning the metadata templates: do I
    understand correctly that by default, neither the basic, nor the
    inspire template contain a reference to the projection system ?

    IIUC, INSPIRE currently does not impose this, but I don't really
    understand how such basic information can be missing from the
    metadata. What help is the bounding box info, if we don't know in
    which CRS it is ?

I agree that it sounds strange, however the bounding box is given in
geographic (unprojected) coordinates, and the ISO 19115:2003, where the
GeographicBoundingBox comes from, reads (B.3.2.1): "geographic position
of the dataset NOTE This is only an approximate reference so specifying
the coordinate reference system is unnecessary "

Using g.gui.metadata on the hospitals map in nc_spm_08, I get:

      <gmd:extent>
                <gmd:EX_Extent>
                    <gmd:geographicElement>
                        <gmd:EX_GeographicBoundingBox>
                            <gmd:westBoundLongitude>
                                <gco:Decimal>308097.937400562</gco:Decimal>
                            </gmd:westBoundLongitude>
                            <gmd:eastBoundLongitude>
                                <gco:Decimal>20235.5644005626</gco:Decimal>
                            </gmd:eastBoundLongitude>
                            <gmd:southBoundLatitude>
                                <gco:Decimal>914347.8748615</gco:Decimal>
                            </gmd:southBoundLatitude>
                            <gmd:northBoundLatitude>
                                <gco:Decimal>156998.1718615</gco:Decimal>
                            </gmd:northBoundLatitude>
                        </gmd:EX_GeographicBoundingBox>
                    </gmd:geographicElement>
                </gmd:EX_Extent>
            </gmd:extent>

Looks like projected coordinates to me...

I would say this is a bug.

--
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.

7

On Mon, Jun 22, 2015 at 4:12 PM, Margherita Di Leo <diregola@gmail.com>
wrote:

On Mon, Jun 22, 2015 at 4:02 PM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:

On 22/06/15 15:40, Margherita Di Leo wrote:

Hi,

On Mon, Jun 22, 2015 at 10:18 AM, Moritz Lennert
<mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>>
wrote:

    Hi Matej,

    Thank you for the updates.

    I have one question concerning the metadata templates: do I
    understand correctly that by default, neither the basic, nor the
    inspire template contain a reference to the projection system ?

    IIUC, INSPIRE currently does not impose this, but I don't really
    understand how such basic information can be missing from the
    metadata. What help is the bounding box info, if we don't know in
    which CRS it is ?

I agree that it sounds strange, however the bounding box is given in
geographic (unprojected) coordinates, and the ISO 19115:2003, where the
GeographicBoundingBox comes from, reads (B.3.2.1): "geographic position
of the dataset NOTE This is only an approximate reference so specifying
the coordinate reference system is unnecessary "

Using g.gui.metadata on the hospitals map in nc_spm_08, I get:

      <gmd:extent>
                <gmd:EX_Extent>
                    <gmd:geographicElement>
                        <gmd:EX_GeographicBoundingBox>
                            <gmd:westBoundLongitude>

<gco:Decimal>308097.937400562</gco:Decimal>
                            </gmd:westBoundLongitude>
                            <gmd:eastBoundLongitude>

<gco:Decimal>20235.5644005626</gco:Decimal>
                            </gmd:eastBoundLongitude>
                            <gmd:southBoundLatitude>
                                <gco:Decimal>914347.8748615</gco:Decimal>
                            </gmd:southBoundLatitude>
                            <gmd:northBoundLatitude>
                                <gco:Decimal>156998.1718615</gco:Decimal>
                            </gmd:northBoundLatitude>
                        </gmd:EX_GeographicBoundingBox>
                    </gmd:geographicElement>
                </gmd:EX_Extent>
            </gmd:extent>

Looks like projected coordinates to me...

I would say this is a bug.

(known)
https://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS#TODOIDEAS

--
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.

8

Hi,

2015-06-22 16:32 GMT+02:00 Margherita Di Leo <diregola@gmail.com>:>>

(known)
https://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS#TODOIDEAS

probably should be moved (merged) to

https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata

?

Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

9

On Mon, Jun 22, 2015 at 4:35 PM, Martin Landa <landa.martin@gmail.com>
wrote:

Hi,

2015-06-22 16:32 GMT+02:00 Margherita Di Leo <diregola@gmail.com>:>>
> (known)
> https://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS#TODOIDEAS

probably should be moved (merged) to

https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata

<http://gismentors.cz/mentors/landa&gt;

I would keep the two pages separated for historical reasons (two GSoC
projects in two different years) but I suggest to cross link the two pages
and move the todo list to the new one. Maybe also to file a bug request for
each task?

--
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.

10

On Mon, Jun 22, 2015 at 4:44 PM, Margherita Di Leo <diregola@gmail.com>
wrote:

On Mon, Jun 22, 2015 at 4:35 PM, Martin Landa <landa.martin@gmail.com>
wrote:

Hi,

2015-06-22 16:32 GMT+02:00 Margherita Di Leo <diregola@gmail.com>:>>
> (known)
> https://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS#TODOIDEAS

probably should be moved (merged) to

https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata

<http://gismentors.cz/mentors/landa&gt;

I would keep the two pages separated for historical reasons (two GSoC
projects in two different years) but I suggest to cross link the two pages
and move the todo list to the new one. Maybe also to file a bug request for
each task?

whereas I suppose the stable documentation should eventually land on the

(same as last year project) wiki page
http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support

--
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.