[GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019

Clemens Portele portele at interactive-instruments.de
Tue Jun 11 00:38:02 EDT 2019


James,

thanks, yes, I see that the statement is misleading (at best). "Native" probably was meant as CRS84, but the current wording of the informative text is not clear. I will fix this.

Best regards,
Clemens

> Am 10.06.2019 um 17:47 schrieb Passmore, James H. <jpass at bgs.ac.uk>:
> 
> Clemens,
> 
> So the para  that Scott quoted with "...The Core also does not specify a capability to request feature geometries in a different coordinate reference system than the native one of the published features. "  is incorrect if my data is natively in say EPSG:3035.   The core requires me to publish as CRS:84
> 
> Cheers
> 
> James
> 
> 
> -----Original Message-----
> From: Clemens Portele <portele at interactive-instruments.de>
> Sent: 10 June 2019 16:21
> To: Passmore, James H. <jpass at bgs.ac.uk>
> Cc: Scott Simmons <ssimmons at opengeospatial.org>; Public: A mailing list for GeoSciML <geosciml at lists.opengeospatial.org>; Boisvert2, Eric (NRCan/RNCan) <eric.boisvert2 at canada.ca>; Carlo Cipolloni <carlo.cipolloni at isprambiente.it>; Panagiotis Vretanos <pvretano at cubewerx.com>
> Subject: Re: [GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019
> 
> James,
> 
> in the interest of interoperability all implementations have to support WGS84 lon/lat. See http://docs.opengeospatial.org/DRAFTS/17-069r1.html#_coordinate_reference_systems. Implementations may support additonal CRSs and Part 2 will specify how to do it. Several implementations have already implemented CRS support based on the current draft of part 2.
> 
> I understand this is not your preferred approach, but I hope you also understand the reasons for the requirement. There have not been any comments on this in the public review or from any of the implementations since the first draft release in April 2018.
> 
> Best regards,
> Clemens
> 
> 
> Am 10.06.2019 um 16:49 schrieb Passmore, James H. <jpass at bgs.ac.uk <mailto:jpass at bgs.ac.uk> >:
> 
> Thanks Scott for that clarification.
> 
> as far as "The implementations compliant with the Core are not required to support publishing feature geometries in coordinate reference systems other than http://www.opengis.net/def/crs/OGC/1.3/CRS84. The Core also does not specify a capability to request feature geometries in a different coordinate reference system than the native one of the published features. Such a capability will be specified in another part(s) of the OGC API Features series.”  goes, to clarify does that mean that software must support it, but any one service can be configured not to use it or that if I offer up a service it must allow CRS:84?  I'm thinking/hoping it means the hoping the former.
> 
> Can you clarify whether 'WGS84' in the phrase " but defaults to WGS84 for the Core" implies any axis order for lat/long such that a OGC API - Features  service that defaults to EPSG:4326 (WGS84 lat/long) would be core complaint?
> 
> Best regards
> 
> James
> 
> -----Original Message-----
> From: Scott Simmons <ssimmons at opengeospatial.org <mailto:ssimmons at opengeospatial.org> >
> Sent: 10 June 2019 15:29
> To: Public: A mailing list for GeoSciML <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org> >
> Cc: Boisvert2, Eric (NRCan/RNCan) <eric.boisvert2 at canada.ca <mailto:eric.boisvert2 at canada.ca> >; Carlo Cipolloni <carlo.cipolloni at isprambiente.it <mailto:carlo.cipolloni at isprambiente.it> >; Passmore, James H. <jpass at bgs.ac.uk <mailto:jpass at bgs.ac.uk> >; Panagiotis (Peter) A. Vretanos <pvretano at cubewerx.com <mailto:pvretano at cubewerx.com> >; Clemens Portele <portele at interactive-instruments.de <mailto:portele at interactive-instruments.de> >
> Subject: Re: [GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019
> 
> OGC API - Features (formerly known as WFS 3.0) supports any native CRS, but defaults to WGS84 for the Core:
> 
> "The implementations compliant with the Core are not required to support publishing feature geometries in coordinate reference systems other than http://www.opengis.net/def/crs/OGC/1.3/CRS84. The Core also does not specify a capability to request feature geometries in a different coordinate reference system than the native one of the published features. Such a capability will be specified in another part(s) of the OGC API Features series.”
> 
> GeoJSON is an allowed feature encoding, but not mandatory (no encodings are mandatory). The first extension to the core under work is the CRS extension.
> 
> I’ve copied the main editors on the candidate standard for more information.
> 
> 
> Best Regards,
> Scott
> 
> 
> 
> On Jun 10, 2019, at 8:12 AM, Passmore, James H. via GeoSciML <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org>  <mailto:geosciml at lists.opengeospatial.org> > wrote:
> 
> I have at the moment OpenAPI as a discussion point for the TIG, which is indeed a discussion about what the policy should be with regards adopting the OGC (OpenAPI) APIs such as WFS 3, when they become standards.
> 
> For WFS 3.0 (core) isn't one issue with geometries that only CRS:84 (a constraint of GeoJSON) is supported?
> 
> https://github.com/OneGeology/TechnicalDiscussion/wiki/OneGeology-TIG-Agenda-for-Face-to-Face-meeting-Friday-28th-June-2019
> 
> James
> 
> -----Original Message-----
> From: Boisvert2, Eric (NRCan/RNCan) <eric.boisvert2 at canada.ca <mailto:eric.boisvert2 at canada.ca> >
> Sent: 10 June 2019 12:30
> To: Carlo Cipolloni <carlo.cipolloni at isprambiente.it <mailto:carlo.cipolloni at isprambiente.it> >; Public: A mailing list for GeoSciML <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org> >
> Cc: Passmore, James H. <jpass at bgs.ac.uk <mailto:jpass at bgs.ac.uk> >
> Subject: RE: [GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019
> 
> Hi Carlo
> 
> 
> 
> Too bad you won’t be able to make it.
> 
> 
> 
> 
> 
> I’m very interested to know what you have done on ontology
> 
> 
> 
> 
> 
> It’s essentially Boyan and Steve work.  Haven’t seen any of it yet.
> 
> 
> 
> Is the WFS 3.0 part connected with WFS3 SWG?
> 
> 
> 
> 
> 
> Indirectly.  WFS 3.0 is gaining popularity and it brings back the discussion of JSON (as oppose to JSON-LD  - there is a standing issue with geometry , but I’m not sure if it’s a JSON-LD issue or an issue related to using JSON-LD to encode RDF).  Some discussion item for OneGeology maybe.
> 
> 
> 
> Eric
> 
> 
> 
> 
> 
> From: Carlo Cipolloni <carlo.cipolloni at isprambiente.it <mailto:carlo.cipolloni at isprambiente.it> >
> Sent: June 10, 2019 03:25
> To: Public: A mailing list for GeoSciML <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org> >
> Cc: Boisvert2, Eric (NRCan/RNCan) <eric.boisvert2 at canada.ca <mailto:eric.boisvert2 at canada.ca> >
> Subject: Re: [GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019
> 
> 
> 
> Dear Eric,
> 
> Unfortunately I’m not able to join physically, but I will connect remotely for sure. I’m very interested to know what you have done on ontology, I work in other domain (Environmental Monitoring Network) to provide data using OGC/W3C and INSPIRE ontology.
> 
> Is the WFS 3.0 part connected with WFS3 SWG?
> 
> Best Regards,
> 
> Carlo
> 
> 
> 
> ---------------------------------------------------
> 
> Carlo Cipolloni
> 
> Information System & INSPIRE Unit Head
> 
> ISPRA DG-SINA (Division for the National Environmental Information System)
> 
> INSPIRE MIG Italian Representative Member
> 
> Italian INSPIRE National Board
> 
> SNPA TIC V SINANET e Reporting
> 
> Tel. +390650074262
> 
> Mobile +393355312119
> 
> skype: cipocarlo
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Da: GeoSciML <geosciml-bounces at lists.opengeospatial.org <mailto:geosciml-bounces at lists.opengeospatial.org>  <mailto:geosciml-bounces at lists.opengeospatial.org> > per conto di "Boisvert2, Eric (NRCan/RNCan) via GeoSciML" <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org>  <mailto:geosciml at lists.opengeospatial.org> >
> Risposta: "Public: A mailing list for GeoSciML" <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org>  <mailto:geosciml at lists.opengeospatial.org> >
> Data: venerdì 7 giugno 2019 20:32
> A: GeoSciml OGC mainling list <geosciml at lists.opengeospatial.org <mailto:geosciml at lists.opengeospatial.org>  <mailto:geosciml at lists.opengeospatial.org> >
> Cc: "Boisvert2, Eric (NRCan/RNCan)" <eric.boisvert2 at canada.ca <mailto:eric.boisvert2 at canada.ca>  <mailto:eric.boisvert2 at canada.ca> >
> Oggetto: [GeoSciML] GeoSciML meeting during TC Tuesday 25th June 2019
> 
> 
> 
> Greetings
> 
> 
> 
> We have a small time slot at OGC in Leuven on Tuesday June 25  from 11h00 to 12h00 for GeoSciML SWG meeting - shared with GWML SWG.
> 
> A goto meeting will be set up and I’ll circulate details  as soon as I have them.
> 
> 
> 
> Agenda
> 
> 1.Potential change to GeoSciML 4.2 (AbstractProperty missing)
> 2.WFS 3.0 and encodings
> 3.Progress report on Borehole IE and potential impact of GeoSciML (borehole package)
> 4.Progress report on some ontology work done by GSC
> 
> 
> 
> Cordialement
> 
> Eric
> 
> 
> 
> Eric Boisvert
> 
> Directeur - Commission géologique du Canada - Québec (intérimaire)
> 
> Director - Geological Survey of Canada – Quebec (acting)
> 
> Gestionnaire du programme de géosciences environnementales (intérimaire)
> 
> Environmental Geoscience Program Manager (acting)
> 
> eric.boisvert2 at canada.ca <mailto:eric.boisvert2 at canada.ca>  <mailto:eric.boisvert2 at canada.ca> ,
> 
> orcid: http://orcid.org/0000-0001-6256-2912 <http://orcid.org/0000-0001-6256-2912>
> 
> phone 418-654-3705,
> 
> facsimile/télécopieur 418-654-2615
> 
> 490, rue de la Couronne, Québec (Québec),
> 
> G1K 9A9, Canada
> 
> 
> 
> Commission géologique du Canada  (Québec) / Geological Survey of Canada (Quebec)
> 
> Lands and Minerasl Sector / Secteur des terres et des minéraux
> 
> Ressources naturelles Canada / Natural Resources Canada Gouvernement du Canada  / Government of Canada
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________ You may visit our Privacy Policy at http://www.opengeospatial.org/privacy <http://www.opengeospatial.org/privacy> . GeoSciML mailing list GeoSciML at lists.opengeospatial.org <mailto:GeoSciML at lists.opengeospatial.org>  <mailto:GeoSciML at lists.opengeospatial.org>  You may also unsubscribe or manage your OGC public list subscriptions at https://lists.opengeospatial.org/mailman/listinfo/geosciml
> 
> 
> 
> This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system.
> UK Research and Innovation has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UK Research and Innovation does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.
> Opinions, conclusions or other information in this message and attachments that are not related directly to UK Research and Innovation business are solely those of the author and do not represent the views of UK Research and Innovation.
> 
> _______________________________________________
> You may visit our Privacy Policy at http://www.opengeospatial.org/privacy <http://www.opengeospatial.org/privacy> .
> GeoSciML mailing list
> GeoSciML at lists.opengeospatial.org <mailto:GeoSciML at lists.opengeospatial.org>
> You may also unsubscribe or manage your OGC public list subscriptions at
> https://lists.opengeospatial.org/mailman/listinfo/geosciml
> 
> 
> 
> 
> 
> This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system.
> UK Research and Innovation has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UK Research and Innovation does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.
> Opinions, conclusions or other information in this message and attachments that are not related directly to UK Research and Innovation business are solely those of the author and do not represent the views of UK Research and Innovation.
> 
> 
> 
> 
> This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system.
> UK Research and Innovation has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UK Research and Innovation does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.
> Opinions, conclusions or other information in this message and attachments that are not related directly to UK Research and Innovation business are solely those of the author and do not represent the views of UK Research and Innovation.
> 



More information about the GeoSciML mailing list