I’d like to bring a proposal for the forthcoming GSoC, that is the support for INSPIRE. This proposal is twofold, one regarding the metadata support, the other regarding the support for the data transformation to meet the inspire schema. I would like to know your opinion before drafting the idea into the trac. I’m willing to mentor for the INSPIRE POV, and since I’m working at JRC I have the opportunity to take advantage of a direct contact with the very people who are developing the Directive. Martin Landa kindly made himself available to co-mentor from the GRASS POV.
cheers,
madi
–
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
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.
I’d like to bring a proposal for the forthcoming GSoC, that is the support for INSPIRE. This proposal is twofold, one regarding the metadata support, the other regarding the support for the data transformation to meet the inspire schema. I would like to know your opinion before drafting the idea into the trac. I’m willing to mentor for the INSPIRE POV, and since I’m working at JRC I have the opportunity to take advantage of a direct contact with the very people who are developing the Directive. Martin Landa kindly made himself available to co-mentor from the GRASS POV.
cheers,
madi
–
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
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.
I'd like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I'm willing to mentor
for the INSPIRE POV, and since I'm working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow the use of specific schemas such as INSPIRE.
QGIS metatools is a nice example of such a generic tool allowing for specification of different schemas and for different outputs through the use of XSLT conversion.
On Tue, Jan 28, 2014 at 11:12 AM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:
On 28/01/14 16:00, Margherita Di Leo wrote:
Hi All,
I'd like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I'm willing to mentor
for the INSPIRE POV, and since I'm working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow
the use of specific schemas such as INSPIRE.
INSPIRE is using some more general ISO standards, isn't it?
QGIS metatools is a nice example of such a generic tool allowing for
specification of different schemas and for different outputs through the
use of XSLT conversion.
QGIS compatibility would be appreciated by a lot of users and it might
even show the way to go.
Some other thing to consider is how this metadata support would interact
with existing r.support, r.timestamp etc. I remember that Yann and NikosA
was talking about this in Genova in 2013.
There are several entry points in GRASS GIS to create/(up)load some kind of information that can be part of a metadata system. We know that GRASS is lacking a unified system to report into a metadata format that is “modern”, interchangable and exportable into online systems.
Once GSoC starts, there will be some more discussions coming up indeed !
I’d like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I’m willing to mentor
for the INSPIRE POV, and since I’m working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow the use of specific schemas such as INSPIRE.
INSPIRE is using some more general ISO standards, isn’t it?
QGIS metatools is a nice example of such a generic tool allowing for specification of different schemas and for different outputs through the use of XSLT conversion.
QGIS compatibility would be appreciated by a lot of users and it might even show the way to go.
Some other thing to consider is how this metadata support would interact with existing r.support, r.timestamp etc. I remember that Yann and NikosA was talking about this in Genova in 2013.
On 28 January 2014 17:12, Moritz Lennert <mlennert@club.worldonline.be> wrote:
On 28/01/14 16:00, Margherita Di Leo wrote:
Hi All,
I'd like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I'm willing to mentor
for the INSPIRE POV, and since I'm working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow
the use of specific schemas such as INSPIRE.
+1, because INSPIRE is only for Europe and a lot of GRASS user are not EU based.
On Tue, Jan 28, 2014 at 11:12 AM, Moritz Lennert
<mlennert@club.worldonline.be <mailto:mlennert@club.worldonline.be>> wrote:
On 28/01/14 16:00, Margherita Di Leo wrote:
Hi All,
I'd like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I'm willing to
mentor
for the INSPIRE POV, and since I'm working at JRC I have the
opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself
available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then
allow the use of specific schemas such as INSPIRE.
INSPIRE is using some more general ISO standards, isn't it?
Yes, it is based on ISO 19115, but it is slightly different. My main idea is that any metadata tool should be capable of using whatever schema the user provides (possibly proposing a few predefined ones) and not hardwired to a specific schema.
Correct: it is build on ISO 19100 series of International Standards. See [1].
I fully agree that the general aim should be a unified system to handle metadata (as Yann said, interchangable and exportable into online systems).
As I see it, the editor should remain general, to meet the users needs. See for example Geonetwork, it’s possible to add or remove fields without restriction.
The INSPIRE schema is a plus for the user, meaning that there will be specific hints to guide the user, i.e. direct links with the parts of the regulation involved in the compilation of each field of the metadata (see for example [2]), the possibility to validate the metadata calling the API of the INSPIRE validator [3], etc.
I agree.
If the GSoC idea will be accepted, I’d appreciate their contribution to the discussion.
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.
I’d like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I’m willing to mentor
for the INSPIRE POV, and since I’m working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow the use of specific schemas such as INSPIRE.
INSPIRE is using some more general ISO standards, isn’t it?
QGIS metatools is a nice example of such a generic tool allowing for specification of different schemas and for different outputs through the use of XSLT conversion.
QGIS compatibility would be appreciated by a lot of users and it might even show the way to go.
Some other thing to consider is how this metadata support would interact with existing r.support, r.timestamp etc. I remember that Yann and NikosA was talking about this in Genova in 2013.
Correct: it is build on ISO 19100 series of International Standards. See [1].
I fully agree that the general aim should be a unified system to handle metadata (as Yann said, interchangable and exportable into online systems).
As I see it, the editor should remain general, to meet the users needs. See for example Geonetwork, it’s possible to add or remove fields without restriction.
The INSPIRE schema is a plus for the user, meaning that there will be specific hints to guide the user, i.e. direct links with the parts of the regulation involved in the compilation of each field of the metadata (see for example [2]), the possibility to validate the metadata calling the API of the INSPIRE validator [3], etc.
I agree.
If the GSoC idea will be accepted, I’d appreciate their contribution to the discussion.
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.
I’d like to bring a proposal for the forthcoming GSoC, that is the
support for INSPIRE. This proposal is twofold, one regarding the
metadata support, the other regarding the support for the data
transformation to meet the inspire schema. I would like to know your
opinion before drafting the idea into the trac. I’m willing to mentor
for the INSPIRE POV, and since I’m working at JRC I have the opportunity
to take advantage of a direct contact with the very people who are
developing the Directive. Martin Landa kindly made himself available to
co-mentor from the GRASS POV.
+1, but I think we should aim for generic metadata handling and then allow the use of specific schemas such as INSPIRE.
INSPIRE is using some more general ISO standards, isn’t it?
QGIS metatools is a nice example of such a generic tool allowing for specification of different schemas and for different outputs through the use of XSLT conversion.
QGIS compatibility would be appreciated by a lot of users and it might even show the way to go.
Some other thing to consider is how this metadata support would interact with existing r.support, r.timestamp etc. I remember that Yann and NikosA was talking about this in Genova in 2013.