geoportal helpdesk - support #2791 - ies-svn.jrc.ec.europa.eu · geoportal helpdesk - support #2791...

Geoportal Helpdesk - Support #2791UK: Year 99 in Temporal Reference21 Jun 2016 03:10 pm - Angelo Quaglia

Status: Closed Start date: 21 Jun 2016Priority: Normal Due date:Assignee: Angelo Quaglia % Done: 0%Category: Harvesting results Estimated time: 0.00 hourTarget version:Submitting Organisation:UK Knowledge-Base relevant?:Proactive: Yes Keyword #1:Country: UK - United Kingdom Keyword #2:Originating UI: Keyword #3:Description

From: Angelo Quaglia [mailto:[email protected]]Sent: 21 June 2016 12:39To: 'Coley, Alex (DDTS)' Cc: '[email protected]' Subject: RE: Problematic metadata

Dear Alex,

The INSPIRE Geoportal has some difficulties processing quite a number of metadata because of unexpected values in the TemporalReference element.

For example:

2013-07-01

99

08 Dec 2020 1/16

It would be helpful to know what they want to express with “99” in the endPosition.

Most, if not all, of the documents seem to have been redacted by the Allerdale Borough Council.

Here is the list of the records on the INSPIRE Geoportal:

http://inspire-geoportal.ec.europa.eu/GeoportalProxyWebServices/resources/INSPIREResource/INSPIRE-f89f4772-05f5-11e1-b7de-2540004b857_20160620-221134/services/1/PullResults/181-200/datasets/13










http://inspire-geoportal.ec.europa.eu/GeoportalProxyWebServices/resources/INSPIREResource/INSPIRE-f89f4772-05f5-11e1-b7de-2540004b857_20160620-221134/services/1/PullResults/981-1000/series/15


http://inspire-geoportal.ec.europa.eu/GeoportalProxyWebServices/resources/INSPIREResource/INSPIRE-f89f4772-05f5-11e1-b7de-

08 Dec 2020 2/16


























2540004b857_20160620-221134/services/1/PullResults/1401-1420/datasets/11


















08 Dec 2020 3/16









































http://inspire-geoportal.ec.europa.eu/GeoportalProxyWebServices/resources/INSPIREResource/INSPIRE-f89f4772-05f5-11e1-b7de-2540004b857_20160620-221134/services/1/PullResults/5161-5180/services/15













08 Dec 2020 4/16























































08 Dec 2020 5/16























































08 Dec 2020 6/16























































08 Dec 2020 7/16















































Best regards,

Angelo

Related issues:Copied to Geoportal Helpdesk - Support # 2837: UK: Year 99 in Temporal Reference Assigned 21 Jun 2016

History#1 - 21 Jun 2016 03:11 pm - Angelo Quaglia

From: GIS [mailto:[email protected]]Sent: 21 June 2016 12:41To: 'Angelo Quaglia' ; [email protected]: RE: Problematic metadata

08 Dec 2020 8/16





















Hi Angelo & Alex

The use of 99 in the end position on Temporal Extent denotes there is no known end date to the protection area afforded by the policy team. As anopen space it is open to periodic reviews. The advice I got was to use 99 not to redact but to show an open temporal date. The use of any blank datecould be construed wrongly as a missing date.

If I can assist further please don’t hesitate to contact me.

Steve Roach-Evans

ICT Lead Officer

Allerdale Borough Council

#2 - 21 Jun 2016 03:11 pm - Angelo Quaglia- Status changed from Assigned to Feedback

From: Angelo Quaglia [mailto:[email protected]]Sent: 21 June 2016 15:08To: 'GIS' Cc: '[email protected]' Subject: RE: Problematic metadata

Dear Steve,

Many thanks for your prompt response.

The INSPIRE Geoportal does not recognize the value 99 as a special value but plainly as year 99.

To my knowledge, for cases like this one, ISO 19136 foresees the use of the indeterminatePosition attribute.

For example:

08 Dec 2020 9/16

http://www.opengis.net/gml/3.2" gml32:id="T1">

2013-07-01

2013-07-01

Or:

http://www.opengis.net/gml/3.2" gml32:id="T1">

2013-07-01

Where:

The enumerated data type TM_IndeterminateValue provides 4 values for indeterminate positions.

a) “unknown” shall be used with the parent class TM_TemporalPosition to indicate that no specific value for

08 Dec 2020 10/16

temporal position is provided.

b) “now” shall be used with any subtype of TM_TemporalPosition to indicate that the specified value shall be

replaced with the current temporal position whenever the value is accessed.

c) “before” shall be used with any subtype of TM_TemporalPosition to indicate that the actual temporal position is

unknown, but it is known to be before the specified value.

d) “after” shall be used with any subtype of TM_TemporalPosition to indicate that the actual temporal position is

unknown, but it is known to be after the specified value

Uncertain Times

The GML elements for describing time positions (beginPosition and endPosition) include the indeterminatePosition attribute that can have values ofbefore, after, now, and unknown. This attribute can be used with a time value to express uncertain times. For example, a dataset that began sometimebefore 1980 and continues to the present could be described as:

1980

Do you think you could consider using one of the constructs above?

Otherwise, I believe that for the sake of interoperability inside the INSPIRE infrastructure, this issue should be discussed and agreed inside the MIG(INSPIRE Maintenance and Implementation Group).

Best regards,

Angelo

#3 - 23 Jun 2016 10:28 am - Angelo Quaglia

08 Dec 2020 11/16

From: GIS [mailto:[email protected]]Sent: 23 June 2016 09:51To: Angelo Quaglia Cc: Ward, Julie Subject: RE: Problematic metadata

Hi Angelo

Sorry for the delay.

You of course are correct. As a practitioner I wasn’t aware of the ramifications and made a unilateral judgement as in many of our systems the use of99 refers to an open ended date as opposed to an unknown date - which was also accepted by the schema- The available Indeterminate variables to me do not adequately define the end dates which for Open Space Protection can never be fully determined – the features were created for a set policywhich came into force with the formal adoption of the policy from a set date and theoretically will remain in force until :

- The individual policy feature is removed where evolving local needs may take precedent. - Change of governmental / local policy - The formal plan is revoked - The formal plan is refreshed – recently revised in 2014 and re-adopted to 2029 - Even after the 2029 is not an actual end date as policies will remain unless explicitly rescinded

In short there is no effective end date and none of the variables adequately define the end date.

I take your point on standards and interoperability so I would propose to add the info about the blank date in the abstract and leave the date blank. Thisto me remains from ideal as a blank date can imply missing date but will at least get around the interoperability issue.

I trust this will be satisfactory?

Steve Roach-Evans

ICT Lead Officer



From: Angelo Quaglia [mailto:[email protected]]Sent: 23 June 2016 10:33To: 'GIS' Cc: 'Ward, Julie'

08 Dec 2020 12/16

Subject: RE: Problematic metadata

Hi Steve,

Many thanks for coming back to me.

Yes, leaving the end date blank would address the interoperability issue as this is expected by the standard:

ISO 19108:

For a variety of reasons, the position of the TM_Instant designated by begin or end may be indeterminate. See

5.4.3 for a discussion of indeterminate temporal positions.

You could also avoid the indeterminatePosition attribute:

-indeterminatePosition: TM_IndeterminateValue is an optional attribute

The metadata would still be valid with respect to the XML schema.

However, the current XML schema specification is not powerful enough to capture all constraints.

It is just an indication that the syntactical structure of the document is good enough for tools to read the document.

I would recommend you pick the value that is “less wrong”, like, for example:

a) “unknown” shall be used with the parent class TM_TemporalPosition to indicate that no specific value for

temporal position is provided.

Please note that it is likely that other people in other contexts share your feeling that none of the values proposed by the standard match yoursituation.

08 Dec 2020 13/16

I recommend you raise this issue with your National Contact Point for INSPIRE who will then bring it to the attention of the MIG.

If you do that, please join the Collaboration Platform of the INSPIRE Geoportal following the instructions written below (**).

This issue is being tracked at https://ies-svn.jrc.ec.europa.eu/issues/2791

Best regards,

Angelo

(**)Getting access

In order to get access to this Geoportal project on the MIG collaboration space, please send an e-mail to [email protected](or reply tothis mail).If you have never used the MIG collaboration space for other projects, please also send us your ECAS login.

If you have any questions, please let us know.

Best regards,

The JRC INSPIRE team.

Best regards,

Angelo

#5 - 23 Jun 2016 11:02 am - Alex Ramage

Angelo,

Could you please include me ([email protected]) in e-mail relating to calls from the UK relating to the Geoportal. Also Alex Coley hasleft government service and I do not believe that his e-mail address is operating anymore.

Alex Ramage


Dear Alex,

08 Dec 2020 14/16

https://ies-svn.jrc.ec.europa.eu/issues/2791

mailto:[email protected]

https://ecas.cc.cec.eu.int:7002/cas/login

mailto:[email protected]

I will. All communications are in any case tracked here and you are already set as a watcher from the start so, you should have been receiving emailnotification.

Could you please confirm?

I took Alex Coley's email address from the list of INSPIRE National Conctact Points at:

http://inspire.ec.europa.eu/cms/contactpoints.cfm

The information given there is, currently:

[email protected]

[email protected]

Please instruct us how to update the information found there.

#7 - 31 Aug 2016 08:56 am - Angelo Quaglia- Category set to Harvesting results

#8 - 01 Sep 2016 07:07 pm - Angelo Quaglia- Status changed from Feedback to Resolved

From: Angelo Quaglia [mailto:[email protected]]Sent: 01 September 2016 19:07To: 'GIS' Cc: '[email protected]' Subject: RE: Problematic metadata

Dear Steve,

Many thanks for cleaning up the issue with the temporal reference, i.e. the 99 in “99”

Best regards,

Angelo

#9 - 02 Sep 2016 01:55 pm - Angelo Quaglia- Status changed from Resolved to Closed

From: Evans, Steve [mailto:[email protected]]Sent: 01 September 2016 19:30To: 'Angelo Quaglia'

08 Dec 2020 15/16

http://inspire.ec.europa.eu/cms/contactpoints.cfm

Subject: RE: Problematic metadata

Hi Angelo

Not a problem – Apologies it took so long - I had some issues when attempting to re-harvest with Datagov to effect the changes. Hopefully all datasetsare now fully synched to their respective hubs.

Steve Roach-Evans

ICT Lead Officer


#10 - 12 Sep 2016 11:25 am - Angelo Quaglia- Proactive set to Yes

#11 - 21 Sep 2016 06:50 pm - Angelo Quaglia- Country set to UK - United Kingdom

08 Dec 2020 16/16

geoportal helpdesk - support #2791 - ies-svn.jrc.ec.europa.eu · geoportal helpdesk - support #2791...

Documents