"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"
GeoSciML - Thematic View - Model Discussion

Summary

This page is the initial focis of design work. Below are tables outlining an initial structure that will evolve into the first release candidate. Comments and discussion will continue until the end of October 2010, at which point a release candidate schema will be created and tested as part of GeoSciML Testbed 4.

Notes

Naming conventions

Field names have tried to match the GeoSciML property names and have only been changed where the concatenation of a number of GeoSciML properties into one label has made a direct match impossible.

Properties beginning with 'representative' mean that the corresponding property in GeoSciML is multi-valued and for thematic mapping purposes one value, either a selection from the set of available values, or a generalized value, must be returned.

Concatenated Value column

The Concat Value column specifies whether or not the expected value is a single value ('N') or is a text string constructed from multiple values based-on the associated GeoSciML data model ('Y'). For example gsmltv:geologicHistory is a concatenated value that will include event age, process and environment descriptions. It must not include values for other, unrelated, properties.

Property 'Role'

The 'Role' column in the tables below describes the role the property plays in the context of the client, or GeoSciML.

Role Description
ID Document or service specific identifier. Not required to persist.
GeoSciML Reference Identifier of a 'full' GeoSciML representation of the geologic feature in question.
Label Human readable label. May be free-text but would best me some structured view of the full property value(s).
Hyperlink URL of a resource providing the actual property value. Point to local entities which are non-GeoSciML resources, for example HTML metadata pages.
Thematic Map Class Identifer of a class in a thematic map. For eample a lithology type in a lithology thematic map.
Map Geometric occurrence of the geologic feature.

XPath Columns

These columns are for reference and map the thematic property to it's equivalent in GeoSciML v2.x or v3.x. There may be a one-to-one match or the thematic view may summarise the content of an entire class in the GeoSciML model. In this case the Xpath stops at th class and the /* represents any possible property of that class. For the sake of space, XPaths were abbreviated using the following constants:

Constant GeoSciML 2.x Value GeoSciML 3.x Value
%MappedFeature% gsml:MappedFeature gsmlcore:MappedFeature
%GeologicUnit% gsml:MappedFeature/gsml:specification/gsml:GeologicUnit gsmlcore:MappedFeature/gsmlcore:specification/gsmlcore:GeologicUnit

Proposed Structure

GeologicUnitView

Simplified view of a GeoSciML GeologicUnit. In GeoSciML terms this will be in instance of a MappedFeature with key property values from the associated GeologicUnit feature summarised as labels (unconstrained character strings) or arbitrarily selected classifiers to be used for thematic mapping purposes. The latter are the properties suffixed with '_uri' and will contain URIs referring to controlled concepts in published vocabularies.
Element Data Type Cardinality Concat Value Role Notes Equivalent GeoSciML 2.x Xpath Equivalent GeoSciML 3.x Xpath
@gml:id gml:id 1..1 N ID id for xml element within a document %MappedFeature%/@gml:id %MappedFeature%/@gml:id
gsmltv:identifier URI 1..1 N GeoSciML Reference Globally unique identifer. Should have the same value as the corresponding GeoSciML MappedFeature. %MappedFeature%/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %MappedFeature%/gml:identifier
gsmltv:name string 0..1 Y Label Display name for the the GeologicalUnit. %GeologicUnit%/gml:name[@codeSpace!='http://www.ietf.org/rfc/rfc2616'] %GeologicUnit%/gml:name
gsmltv:description string 0..1 Y Label Text description of the GeologicUnit, typically taken from an entry on a geological map legend. %GeologicUnit%/gml:description %GeologicUnit%/gml:description
gsmltv:geologicUnitType string 0..1 N Label Type of unit (as defined in GeoSciML) %GeologicUnit%/gsml:geologicUnitType/@xlink:title %GeologicUnit%/gsmlcore:geologicUnitType/@xlink:title
gsmltv:rank string 0..1 N Label Rank of unit (as defined in GeoSciML). %GeologicUnit%/gsml:rank %GeologicUnit%/gsmlcore:rank/@xlink:title
gsmltv:lithology string 0..1 Y Label Text (possibly formatted with formal syntax) description of the GeologicUnit's lithology. %GeologicUnit%/gsml:composition/gsml:CompositionPart/gsml:material/gsml:RockMaterial/gsml:lithology/@xlink:title %GeologicUnit%/gsmlcore:composition/gsmlcore:CompositionPart/gsmlcore:material/gsmlcore:RockMaterial/gsmlcore:lithology/cgu:CGI_Term/cgu:value/@xlink:title
gsmltv:geologicHistory string 0..1 Y Label Text (possibly formatted with formal syntax) description of the age of the GeologicUnit (where age is a sequence of events and may include process and environment information). %GeologicUnit%/gsml:geologicHistory/gsml:GeologicEvent/* %GeologicUnit%/gsmlcore:geologicHistory/gt:GeologicEvent/*
gsmltv:observationMethod string 0..1 Y Label Metadata snippet indicating how the spatial extent of the feature was determined. ObservationMethod is a convenience property that provides a quick and dirty approach to observation metadata when data are reported using a feature view (as opposed to observation view). %MappedFeature%/gsml:observationMethod/gsml:CGI_TermValue/gsml:value %MappedFeature%/gsmlcore:observationMethod/cgu:CGI_Term/cgu:value/@xlink:title
gsmltv:positionalAccuracy string 0..1 Y Label Quantitative values define the radius of an uncertainty buffer around a mappedFeature (eg: a positionAccuracy of 100 m for a line feature defines a buffer polygon of total width 200 m centred on the line). %MappedFeature%/gsml:positionalAccuracy/* %MappedFeature%/gsmlcore:positionalAccuracy/swe:Quantity/swe:value & uom/@link:title
gsmltv:geologicUnitType_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept from a vocabulary defining the GeologicUnit types. Mandatory propery - if not value is provided then a URI referring to a conctrolled concept explaining why the value is nil must be provided. %GeologicUnit%/gsml:geologicUnitType/@xlink:title %GeologicUnit%/gsmlcore:geologicUnitType/@xlink:href
gsmltv:representativeLithology_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the characteristic or represntative lithology of the unit. This may be a concept that defines the super-type of all lithology values present within a GeologicUnit or a concept defining the lithology of the dominant CompositionPart (as defined in GeoSciML) of the unit. %GeologicUnit%/gsml:composition/gsml:CompositionPart/gsml:material/gsml:RockMaterial/gsml:lithology/@xlink:href %GeologicUnit%/gsmlcore:composition/gsmlcore:CompositionPart/gsmlcore:material/gsmlcore:RockMaterial/gsmlcore:lithology/cgu:CGI_Term/cgu:value/@xlink:href
gsmltv:representativeAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative stratigraphic age interval for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %GeologicUnit%/gsml:geologicHistory/gsml:GeologicEvent/gsml:eventAge/*/gsml:CGI_TermValue/gsml:value %GeologicUnit%/gsmlcore:geologicHistory/gt:GeologicEvent/*/@xlink:href
gsmltv:representativeLowerAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative lower value in a range of stratigraphic age intervals for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %GeologicUnit%/gsml:geologicHistory/gsml:GeologicEvent/gsml:eventAge/gsml:CGI_TermRange/gsml:lower/gsml:CGI_TermValue/gsml:value %GeologicUnit%/gsmlcore:geologicHistory/gt:GeologicEvent/gt:olderNamedAge/@xlink:href
gsmltv:representativeUpperAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative upper value in a range of stratigraphic age intervals for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %GeologicUnit%/gsml:geologicHistory/gsml:GeologicEvent/gsml:eventAge/gsml:CGI_TermRange/gsml:upper/gsml:CGI_TermValue/gsml:value %GeologicUnit%/gsmlcore:geologicHistory/gt:GeologicEvent/gt:youngerNamedAge/@xlink:href
gsmltv:specification_uri URI 1..1 N GeoSciML Reference URI referring the the GeoSciML GeologicUnit feature that describes the instance in detail. Mandatory propery - if not value is provided then a URI referring to a conctrolled concept explaining why the value is nil must be provided. %GeologicUnit%/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %GeologicUnit%/gml:identifier
gsmltv:metadata_uri URI 1..1 N Hyperlink URI referring to a metadata record describing the provenance of data. local entity local entity
gsmltv:source_uri URI 1..1 N Hyperlink URI referring to reference material and publications describing the geologic feature. local entity local entity
gsmltv:genericSymbolizer string 0..1 N Thematic Map Class Identifier for a symbol from standard (locally or community defined) symbolization scheme for portrayal. local entity local entity
gsmltv:shape geometry 1..1 N Map Geometry defining the extent of the feature of interest. %MappedFeature%/gsml:shape %MappedFeature%/gsmlcore:shape

Discussion

gsmltv:identifier: should it be unique to the thematic view feature or be a link to the equivalent GeoSciML MappedFeature (as implied by the Role GeoSciML reference)? I'm inclined towards the former and we therefore should consider an, optional, mappedFeature_uri property. -- AlistairRitchie - 2010-09-15


I understand that gsmltv:geologicHistory (concat value YES) represents several attributes that are concatenated. But what if there are several geologicHistory?

For gsmltv:lithology, I guess that if there are several compositionPart, all the lithologies are concatenated, without role and proportion? -- AgnesTellezArenas - 2010-09-15

Here's some examples of a structured approach to the text strings that might be used in a flat file format to summarize the lithology and geologic history:

LITHOLOGY COMPOSITION (Text) – Composition of the mapped unit in terms of rock types from the standard lithology vocabulary, along with a proportion value for each constituent. Encoded as a set of {lithology:proportion} tuples. Rock types will be specified with preferred names from a CGI lithology vocabulary. Proportion values will also be specified from a controlled vocabulary, and definition for these terms will be accessible through the same mechanism as the lithology vocabulary. The format will be “Lith1:prop1;Lith2:prop2”. The lithology vocabulary includes some hierarchy, and the lithology terms could encode the hierarchy from most general to most specific (granitic rock/granodiorite). The first lithology listed will be considered the most abundant and used for symbolization in a lithology map portrayal.

GEOLOGIC History (Text) – Text string for geologic age of event(s) in genesis of unit. Specified as “Age(NNN.N)[?][-Age(NNN.N)[?]]:Event” tuples, with multiple values separated by semicolons. If two age values are included, separated by a hyphen, for an event, the event occurred during an age range. Older age bound of range is listed first. If a numeric age is known, it should be added after the corresponding stratigraphic age term in parenthesis. Numeric age values are in millions of years before 1950 (Ma). Hierarchy of stratigraphic ages is indicated from most general to most specific, with the named eras separated by ‘/’. To reduce the likelihood of the age string exceeding 255 characters and being truncated in shapefiles, stratigraphic era names do not need to be repeated if they have already been used. The confidence term is optional, defaulting to ‘std’, indicating that the age is considered reliable with a standard level of confidence. Other values allowed are ‘low’, used to indicate that the associated age assignment is uncertain, and ‘unk’ to indicate unknown reliability. Examples: “Phanerozoic/Mesozoic/Jurassic-Cretaceous:Deposition”, “Phanerozoic/­Cenozoic/­Neogene/­Miocene(12.5):Eruption”, “Precambrian/­Proterozoic/­Paleo­protero­zoic­(1750):­Eruption; Mesoproterozoic(1420):Intrusion; Phanerozoic/­Mesozoic/­Jurassic­(165):­Intrusion; Cenozoic/­Paleogene/Eocene?-Neogene/Miocene:Metamorphism; Miocene:­Cooling”. -- SteveRichard - 2010-09-15

An example from one of GSV's development WMSs is as follows:

LITHOLOGY
Format [lithology label], [proportion]; [lithology label], [proportion]; ...
Example 'mudstone, dominant; sandstone, minor'

GEOLOGIC HISTORY
Format [oldest age] to [youngest age], [process] - [environment]; [oldest age] to [youngest age], [process] - [environment]; ...
Example 'Early Cambrian to Late Cambrian, turbidity current - deep sea, Cambrian to Silurian, orogenic metamorphism - convergent plate boundary'
Question: do we mandate a format for these labels, or do we allow each service provider to determine the best way to present their data? Because they are just labels, not searchable data, I'm inclined towards the latter. -- AlistairRitchie - 2010-09-29


Regarding gsmltv:representativeLowerAge_uri and gsmltv:representativeUpperAge_uri, I remember that in 1GEurope project, some partners were not happy with having to choose between upperAge or lowerAge for portraying the data, they would prefere a representativeAge (If I am not wrong...). We had a lot of discussion on that subject. It was an issue also because of the harmonization between several country. I am honnestly not able to explain why and what! I think John would be able to give more explanation.

(or maybe I am totally wrong!) -- AgnesTellezArenas - 2010-09-22

In 1GE this was a portrayal issue. Ages were given as a term range but because we wanted to portray age in one of the services we arbitrarily decided this would be on the basis of lower age, which could clearly give misleading results for units covering a long time period. Alternatives would have been to go up the age hierarchy tree until we had a geochron unit that included the whole time period of the unit, but that could mean loss of a lot of resolution, or a geologist choosing an appropriate representative age. The latter would have been best but we decided against it because of the geologist time involved as I recall. In developing a data structure designed for portrayal a single term ‘representative age’ would be useful. -- JohnLaxton - 2010-09-22

The trouble is that all age representation are ranges (even a single term such as Silurian actually represents a range.) Because of the almost infinite age range combinations possible, the usual practise is to have the geologist pick a single age era term as the representative age for symbolising based on the appropriate age era, irrespective of the actual age range shown in the legend.

Perhaps a Thematic View age labelled "representative age era" would meet the 1GE user requirements and allow the application to know it will be one of the ISC eras? -- BruceSimons - 2010-09-23

Yes I agree – that is just what I was saying!. -- JohnLaxton - 2010-09-23

Indeed, but on maps the 'representative age' is usually restricted to a single Period (sorry I used Era by mistake), whereas the legend has an upper and lower age. So the tension we are trying to resolve is between wanting to show the map age vs the legend age.

As the data consumer (client) doesn't have control over what the data provider delivers they could put anything (including a range) in the 'representativer age', which would make using it in a portrayal very difficult.

Similarly we don't have control over what the client application chooses to use for display, so it could still portray any of the Lower Age, the Upper Age or the Representative Age (or any combination) and the data provider has no say in it.

The problem is if you provide all three (lower, upper and representative) then different data providers will populate them differently and different clients will use them differently - the worst of all possible worlds.

Alternatively, only providing the capacity to deliver a single age, the 'representative age', will encourage those who have an upper and lower age to provide this as a text range, which is not easily portrayed.

It is therefore probably best to allow for a lower and upper age, which makes it explicit what these are. It meets the requirements of those who want a minimum and maximum age. Those who want to deliver a single representative age can populate both with the same value, forcing clients to use this value. The data provider can decide what age they want portrayed, and those clients with the capacity to display the age based on various ranges will have the information to do so. -- BruceSimons - 2010-09-25

ContactView

Simplified view of a GeoSciML Contact. In GeoSciML terms this will be an instance of a MappedFeature with key property values from the associated Contact feature summarised as labels (unconstrained character strings) or arbitrarily selected classifiers to be used for thematic mapping purposes. The latter are the properties suffixed with '_uri' and will contain URIs referring to controlled concepts in published vocabularies.
Element Data Type Cardinality Concat Value Role Notes Equivalent GeoSciML 2.x Xpath Equivalent GeoSciML 3.x Xpath
@gml:id gml:id 1..1 N ID id for xml element within a document %MappedFeature%/@gml:id %MappedFeature%/@gml:id
gsmltv:identifier URI 1..1 N GeoSciML Reference Globally unique identifer. Should have the same value as the corresponding GeoSciML MappedFeature. %MappedFeature%/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %MappedFeature%/gml:identifier
gsmltv:name string 0..1 Y Label Display name for the the Contact. %MappedFeature%/gsml:specifcation/gsml:Contact/gml:name[@codeSpace!='http://www.ietf.org/rfc/rfc2616'] %MappedFeature%/gsmlcore:specifcation/gsmlcore:Contact/gml:name
gsmltv:description string 0..1 Y Label Text description of the Contact, typically taken from an entry on a geological map legend. %Contact%/gml:description %GeologicUnit%/gml:description
gsmltv:contactType string 0..1 N Label Type of Contact (as defined in GeoSciML). %MappedFeature%/gsml:specifcation/gsml:Contact/gsml:contactType/@xlink:title %MappedFeature%/gsmlcore:specifcation/gsmlcore:Contact/gsmlcore:contactType/@xlink:title
gsmltv:observationMethod string 0..1 Y Label Metadata snippet indicating how the spatial extent of the feature was determined. ObservationMethod is a convenience property that provides a quick and dirty approach to observation metadata when data are reported using a feature view (as opposed to observation view). %MappedFeature%/gsml:observationMethod/gsml:CGI_TermValue/gsml:value %MappedFeature%/gsmlcore:observationMethod/cgu:CGI_Term/cgu:value/@xlink:title
gsmltv:positionalAccuracy string 0..1 Y Label Quantitative values define the radius of an uncertainty buffer around a mappedFeature (eg: a positionAccuracy of 100 m for a line feature defines a buffer polygon of total width 200 m centred on the line). %MappedFeature%/gsml:positionalAccuracy/* %MappedFeature%/gsmlcore:positionalAccuracy/swe:Quantity/swe:value & uom/@link:title
gsmltv:contactType_uri string 1..1 N Thematic Map Class URI referring to a controlled concept from a vocabulary defining the Contact types. Mandatory propery - if not value is provided then a URI referring to a conctrolled concept explaining why the value is nil must be provided. %MappedFeature%/gsml:specifcation/gsml:Contact/gsml:contactType/@xlink:href %MappedFeature%/gsmlcore:specifcation/gsmlcore:Contact/gsmlcore:contactType/@xlink:href
gsmltv:specification_uri URI 1..1 N GeoSciML Reference URI referring the the GeoSciML Contact feature that describes the instance in detail. Mandatory propery - if not value is provided then a URI referring to a conctrolled concept explaining why the value is nil must be provided. %MappedFeature%/gsml:specifcation/gsml:Contact/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %MappedFeature%/gsmlcore:specifcation/gsmlcore:Contact/gml:identifier
gsmltv:metadata_uri URI 1..1 N Hyperlink URI referring to a metadata record describing the provenance of data. local entity local entity
gsmltv:source_uri URI 1..1 N Hyperlink URI referring to reference material and publications describing the geologic feature. local entity local entity
gsmltv:genericSymbolizer string 0..1 N Thematic Map Class Identifier for a symbol from standard (locally or community defined) symbolization scheme for portrayal. local entity local entity
gsmltv:shape geometry 1..1 N Map Geometry defining the extent of the feature of interest. %MappedFeature%/gsml:shape %MappedFeature%/gsmlcore:shape

Discussion

ShearDisplacementStructureView

Simplified view of a GeoSciML ShearDisplacementStructure. In GeoSciML terms this will be in instance of a MappedFeature with key property values from the associated ShearDisplacementStructure feature summarised as labels (unconstrained character strings) or arbitrarily selected classifiers to be used for thematic mapping purposes. The latter are the properties suffixed with '_uri' and will contain URIs referring to controlled concepts in published vocabularies.
Element Data Type Cardinality Concat Value Role Notes Equivalent GeoSciML 2.x Xpath Equivalent GeoSciML 3.x Xpath
@gml:id gml:id 1..1 N ID id for xml element within a document %MappedFeature%/@gml:id %MappedFeature%/@gml:id
gsmltv:identifier URI 1..1 N GeoSciML Reference Globally unique identifer. Should have the same value as the corresponding GeoSciML MappedFeature. %MappedFeature%/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %MappedFeature%/gml:identifier
gsmltv:name string 0..1 Y Label Display name for the the ShearDisplacementStructure. %ShearDisplacementStructure%/gml:name[@codeSpace!='http://www.ietf.org/rfc/rfc2616'] %ShearDisplacementStructure%/gml:name
gsmltv:description string 0..1 Y Label Text description of the ShearDisplacementStructure, typically taken from an entry on a geological map legend. %ShearDisplacementStructure%/gml:description %MappedFeature%/gsmlcore:specifcation/gsmlcore:Contact/gml:description
gsmltv:faultType string 0..1 N Label Type of ShearDisplacementStructure (as defined in GeoSciML). %ShearDisplacementStructure%/gsml:faultType/@xlink:title %ShearDisplacementStructure%/gsmlcore:faultType/@xlink:title
gsmltv:movementType string 0..1 N Label Summarises the type of movement (eg dip-slip, strike-slip) on the ShearDisplacementStructure. %ShearDisplacementStructure%/*/gsml:DisplacementValue/gsml:movementType/gsml:CGI_TermValue/gsml:value/@xlink:title %ShearDisplacementStructure%/*/gsml:DisplacementValue/gsmlcore:movementType/@xlink:title
gsmltv:deformationStyle string 0..1 N Label Describes the style of deformation (eg brittle, ductile etc) for the ShearDisplacementStructure. N/A %ShearDisplacementStructure%/gsmlcore:deformationStyle/@xlink:title
gsmltv:displacement string 0..1 Y Label Summarises the displacement across the ShearDisplacementStructure. %ShearDisplacementStructure%/*/gsml:DisplacementValue/* %ShearDisplacementStructure%/*/gsmlcore:DisplacementValue/*
gsmltv:geologicHistory string 0..1 Y Label Text (possibly formatted with formal syntax) description of the age of the ShearDisplacementStructure (where age is a sequence of events and may include process and environment information). %ShearDisplacementStructure%/gsml:geologicHistory/gsml:GeologicEvent/* %ShearDisplacementStructure%/gsmlcore:geologicHistory/gsmlcore:geologicHistory/gt:GeologicEvent/gt:youngerNamedAge & olderNamedAge/@xlink:title
gsmltv:observationMethod string 0..1 Y Label Metadata snippet indicating how the spatial extent of the feature was determined. ObservationMethod is a convenience property that provides a quick and dirty approach to observation metadata when data are reported using a feature view (as opposed to observation view). %MappedFeature%/gsml:observationMethod/gsml:CGI_TermValue/gsml:value %MappedFeature%/gsmlcore:observationMethod/cgu:CGI_Term/cgu:value/@xlink:title
gsmltv:positionalAccuracy string 0..1 Y Label Quantitative values define the radius of an uncertainty buffer around a mappedFeature (eg: a positionAccuracy of 100 m for a line feature defines a buffer polygon of total width 200 m centred on the line). %MappedFeature%/gsml:positionalAccuracy/* %MappedFeature%/gsmlcore:positionalAccuracy/swe:Quantity/swe:value & uom/@link:title
gsmltv:faultType_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept from a vocabulary defining the fault (ShearDisplacementStructure) type. Mandatory property - if not value is provided then a URI referring to a controlled concept explaining why the value is nil must be provided. %ShearDisplacementStructure%/gsml:faultType/@xlink:href %ShearDisplacementStructure%/gsml:faultType/@xlink:href
gsmltv:movementType_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept from a vocabulary defining the ShearDisplacementStructure movement type. Mandatory property - if not value is provided then a URI referring to a controlled concept explaining why the value is nil must be provided. %ShearDisplacementStructure%/*/gsml:DisplacementValue/gsml:movementType/gsml:CGI_TermValue/gsml:value/@xlink:href %ShearDisplacementStructure%/*/gsml:DisplacementValue/gsmlcore:movementType/@xlink:href
gsmltv:deformationStyle_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept from a vocabulary defining the ShearDisplacementStructure deformation style. Mandatory propery - if not value is provided then a URI referring to a conctrolled concept explaining why the value is nil must be provided. N/A %ShearDisplacementStructure%/gsmlcore:deformationStyle/@xlink:href
gsmltv:representativeAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative stratigraphic age interval for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %ShearDisplacementStructure%/gsml:geologicHistory/gsml:DisplacementEvent/gsml:eventAge/*/gsml:CGI_TermValue/gsml:value %ShearDisplacementStructure%/gsmlcore:geologicHistory/gsmlcore:geologicHistory/gt:GeologicEvent/*/@xlink:href
gsmltv:representativeLowerAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative lower value in a range of stratigraphic age intervals for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %ShearDisplacementStructure%/gsml:geologicHistory/gsml:DisplacementEvent/gsml:eventAge/gsml:CGI_TermRange/gsml:lower/gsml:CGI_TermValue/gsml:value %ShearDisplacementStructure%/gsmlcore:geologicHistory/gsmlcore:geologicHistory/gt:GeologicEvent/gt:olderNamedAge/@xlink:href
gsmltv:representativeUpperAge_uri URI 1..1 N Thematic Map Class URI referring to a controlled concept specifying the most representative upper value in a range of stratigraphic age intervals for the GeologicUnit. This will be defined entirely at the discretion of the data provider and may be a single event selected from the geologic feature's geological history or a value summarising the all or part of the feature's history. %ShearDisplacementStructure%/gsml:geologicHistory/gsml:DisplacementEvent/gsml:eventAge/gsml:CGI_TermRange/gsml:upper/gsml:CGI_TermValue/gsml:value %ShearDisplacementStructure%/gsmlcore:geologicHistory/gsmlcore:geologicHistory/gt:GeologicEvent/gt:youngerNamedAge/@xlink:href
gsmltv:specification_uri URI 1..1 N GeoSciML Reference URI referring the the GeoSciML ShearDisplacementStructure feature that describes the instance in detail. Mandatory propery - if not value is provided then a URI referring to a controlled concept explaining why the value is nil must be provided. %ShearDisplacementStructure%/gml:name[@codeSpace='http://www.ietf.org/rfc/rfc2616'] %ShearDisplacementStructure%/gml:identifier
gsmltv:metadata_uri URI 1..1 N Hyperlink URI referring to a metadata record describing the provenance of data. local entity local entity
gsmltv:source_uri URI 1..1 N Hyperlink URI referring to reference material and publications describing the geologic feature. local entity local entity
gsmltv:genericSymbolizer string 0..1 N Thematic Map Class Identifier for a symbol from standard (locally or community defined) symbolization scheme for portrayal. local entity local entity
gsmltv:shape geometry 1..1 N Map Geometry defining the extent of the feature of interest. %MappedFeature%/gsml:shape %MappedFeature%/gsmlcore:shape

Discussion

General Discussion

A couple of comments on this as requested:
  1. I think we need a faultType thematic map class in the ShearDisplacementStructure view
  2. I think in the GeologicUnit view gsmltv:type would be better named gsmltv:title as that it what it is as I understand it – it isn’t really holding information on the type of GeologicUnit
  3. I agree that gsmltv:identifier should be unique to the thematic view – areas are likely to be combined in thematic views so won’t necessarily relate directly to the originating MappedFeatures.
-- JohnLaxton - 2010-09-23

I'll add a type_uri (or faultType_uri, see below) property (point 1.) to the ShearDisplacementStructure type and update the documentation (the notes column) to refelct the current majority consensus (2 of 2 repsonses) for point 3.

For point 2: the GeologicUnit gsmltv:type property is holding the unit type information as a label. Values like 'lithodemic unit' are expected here.

Would it be clearer if the names of the gsmltv:type property was changed across all the feature types to gsmltv:geologicUnitType, gsmltv:contactType, gsmltv:faultType? If thematic mapping of a type is required then then there will be corresponding gsmltv:geologicUnitType_uri, gsmltv:contactType_uri or gsmltv:faultType_uri properties. -- AlistairRitchie - 2010-09-27


Could you clarify what you mean when you say this is not for setting up a simple GeoSciML WFS? Surely it is for setting up a simple WFS amongst other things? -- JohnLaxton - 2010-09-23

GeoSciML Thematic View is being desinged to meet thematic mapping/portrayal use cases. In terms of technology this relates to the standardisation of the deployment of map services - primarily WMS - making the consistent use of tools like SLD possible across multiple service instances.

WFSs may be set up as data sources for these map services, but they are not a mandatory requirement: depending on the technology being used, a source WFS may not be required. -- AlistairRitchie - 2010-09-27

By the way: to me, a 'simple GeoSciML WFS' means working with GeoSciML sensu stricto . If so, we have limited scope for simplification there - for example, it is impossible to create a GML-SF level 0 profile of GeoSciML because of our use of 'user-defined' data-types. GeoSciML TV would not an appropriate example of such a simplfication - the data are too simple and generalised (see the related representative age discussion) to be of any great value except in the most rudimentry examples of data exchange. -- AlistairRitchie - 2010-09-27

Shape file limitations

Since it is likely that SHP file will be used in many of those services, has the limitations of shape files have been taken into account ?

http://en.wikipedia.org/wiki/Shapefile#Limitations

The most proheminents I see in this list are

  • limited to 10 chars (representativeUpperAge_uri bust that limit)
  • No NULL (is this true for String as well). In this case, it should be stated that for 0..1 fields, an absence is represented as a 0 length string (which may be different from explicit NULL)
Note that I don't know if those limitations are still true.

-- EricBoisvert - 2010-10-05

As far as I am aware, these limitations still exist for shapefiles. But we are not delivering a shapefile, we are mapping a shapefile to a WMS, so we can define the WMS attributes how we like, can't we, without having to consider shapefile limitations? eg, the field called COMPOSTN in the my shapefile is called COMPOSITION_CATEGORY in my WFS SF0 or WMS.

-- OliverRaymond - 2010-10-06

Very good point. I was under the assumption that MapServer did not allow renaming fields. gml_[item name]_alias configuration actualy does the trick.

-- EricBoisvert - 2010-10-07
Topic attachments
I Attachment Action Size Date Who Comment
GeoSciML-3.x.eapeap GeoSciML-3.x.eap manage 55348.0 K 23 Nov 2010 - 07:25 AlistairRitchie Temp version of GeoSciML v3.0 EAP for Rob A.
Topic revision: r10 - 25 Nov 2010, AlistairRitchie
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).