GeoSciML v4 teleconference - Tuesday, June 16, 2015 - 13:00 GMT

Join meeting by clicking this link:

Access Code: 331-548-605

For audio, either use headphones/microphone on your computer, or dial in using your phone

Australia : +61 2 8355 1039
Austria : +43 (0) 7 2088 2172
Belgium : +32 (0) 42 68 0180
Canada : +1 (647) 497-9379
Denmark : +45 (0) 89 88 05 39
Finland : +358 (0) 931 58 4588
France : +33 (0) 170 950 589
Germany : +49 (0) 692 5736 7301
Ireland : +353 (0) 19 036 187
Italy : +39 0 294 75 15 37
Netherlands : +31 (0) 108 080 116
New Zealand : +64 (0) 9 801 0294
Norway : +47 21 51 81 86
Spain : +34 911 23 4248
Sweden : +46 (0) 852 500 516
Switzerland : +41 (0) 435 0824 41
United Kingdom : +44 (0) 330 221 0099
United States : +1 (224) 501-3318
Location Local time Time zone UTC offset
Canberra (Australia - Australian Capital Territory) Tuesday, 16 June 2015 at 11:00:00 PM AEST UTC+10 hours
Melbourne (Australia - Victoria) Tuesday, 16 June 2015 at 11:00:00 PM AEST UTC+10 hours
Phoenix (U.S.A. - Arizona) Tuesday, 16 June 2015 at 6:00:00 AM MST UTC-7 hours
Québec (Canada - Quebec) Tuesday, 16 June 2015 at 9:00:00 AM EDT UTC-4 hours
Edinburgh (United Kingdom - Scotland) Tuesday, 16 June 2015 at 2:00:00 PM BST UTC+1 hour
London (United Kingdom - England) Tuesday, 16 June 2015 at 2:00:00 PM BST UTC+1 hour
Berlin (Germany - Berlin) Tuesday, 16 June 2015 at 3:00:00 PM CEST UTC+2 hours
Rome (Italy) Tuesday, 16 June 2015 at 3:00:00 PM CEST UTC+2 hours
Helsinki (Finland) Tuesday, 16 June 2015 at 4:00:00 PM EEST UTC+3 hours
Corresponding UTC (GMT) Tuesday, 16 June 2015 at 13:00:00    



1. Report on change from FullMoon to ShapeChange and impact on UML (they need slightly different tagged values)

2. Need for clean up of tagged values

3. Issues with schema generation

- still a couple of things that must be edited manually in the generated XSD, but it was also the case with FullMoon apparently

- metadata comes from two different versions

- inclusion of GML 3.3 elements (might not be a problem after all, Marcus explained to me they are just extensions to 3.2 and not brand new version of 3.2)


4. Example instance documents for INSPIRE


5. Issues in the UML discovered during testing of Eric's schemas.


  1. EricBoisvert described some quirks of ShapeChange that required some manual editing of the schemas.UML tags (particularly encoding rules) that are required for ShapeChange are different to FullMoon's requirements.
  2. Have to use GML3.3 encoding rules to get ShapeChange to encode byReference tags. But then have to remove GML3.3 from the XSD files because we want to stick with GML3.2 in the schemas for the time being.
  3. EricBoisvert has generated one schema per UML App Schema package (ie, not one for every leaf package like we did in v3). This produces significantly less XSD files and it met with no opposition for the teleconference participants.
  4. Need to generate schema for GeologicTime app schema (like we did in GeoSciML v3)
  5. OllieRaymond will notify EricBoisvert when to re-run the schema generation after corrections to the UML have been made.
  6. Ideal target date is July 27 to get a robust set of schemas and HTML documentation finished and published (at least as a soft release) so that they can be used by EU EGDI and OneGeology. (Tim Duffy)

  1. Need to write a general GeoSciML schematron to enforce the use of basic desirable properties (eg: upperValue and lowerValue in GSML_QuantityRange, RockMaterial /lithology, Mineral/mineralName, Foliation/foliationType)
    • need to compile this list of essential attributes for Marcus.
  2. All SWG members need to go through Marcus's schematrons and provide feedback to him on:
    • the comments that Marcus has put in the schematron files
    • the validity of the existing schematrons, and
    • any additional required schematron constraints.
  3. Carlo is involved with a Natural Risk Zones project that has developed schematrons. Request that Carlo provide access for MarcusSen to these schematrons so that the GeoSciML SWG may learn from the work of the Natural Risk Zones project.

Example Instance Documents
  1. Discussion about using URN's or URL's. It seems that gml:srs EPSG references are the only place where URN's are still seen. Need to move to using URL's for EPSG references for complete consistency.
  2. MarcusSen circulated the draft INSPIRE GeoSciML v4 encoding cookbook for review and comments
  3. All SWG members need to contribute example instance documents. These documents can be as small or as large as you like, but prefer many smaller ones that show examples of just one feature class rather than very large documents. These smaller xml snippets can then be used in OGC spec documentation.
    • TimDuffy to follow up with Tomas Lindberg about contributions to this work

UML Model Issues
  1. Need to further test the Event-to-Event relations part of the model. There are currently two ways to relate Events to other Events --> 1. via the geologicHistory association, and 2. via the generic GeologicFeature --> GeologicFeature association. This may create confusion among users. Need to have one agreed way of relating Events to other Events.
  2. GeologicEvent extension package needs reconstruction.
  3. Both OllieRaymond and EricBoisvert have noticed odd behaviours in EA - association links that have been deleted from packages, and classes that have been deleted from diagrams, have been re-appearing in the model and diagrams without warning. Suggest that these are bugs in EA? Ollie to raise issue with Sparx Systems.
  4. OllieRaymond described problems with the EarthMaterials model (eg, links between basic and extended) that needed fixing. Duplicated link from Layering feature class to lithology was removed too.
  5. Need to ensure that all associations have sequence numbers on them, and ensure that extension associations are encoded last in the order of properties (just for ease of XML encoding).
    • EricBoisvert suggested that ShapeChange may be ignoring sequence numbers? Eric needs to check that ShapeChange is accurately implementing our sequence numbering from the UML.
  6. OllieRaymond suggested that we don't need nillable/voidable tags now that we have moved to "all optional". But the group agreed that nillable tags are still useful to be able to use the xsi:nilReason property, even on optional properties.
    • Need to check that nillable/voidable tags are on all properties that require it - currently there are some properties that are without nillable/voidable tags.

Other business
  1. TimDuffy requested Ollie to find the GeoSciML statement of open source access so that we can add it to schemas and schematrons. (OllieRaymond notes that anything developed under the OGC banner is covered by the general requirement that all OGC standards are open source and provided free of charge).
  2. EricBoisvert circulated the GroundWaterML v2 draft OGC spec documentation as an example for the GeoSciML SWG. Eric offered to do a first cut of a GeoSciML OGC spec in the GWML style.
  3. GeologicHistoryRelation vocabulary needs to be published for GeoSciML v3.2 (TimDuffy to follow up with Tomas Lindberg and MarkRattenbury to get at least a first draft vocabulary compiled and published at
Topic revision: r2 - 18 Jun 2015, OllieRaymond
This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback