"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"

Base Feature types for XMML


Contents

Related pages


Schema documents

Model and document structure

A set of base feature-types for XMML are defined in XmmlCVS:XMML/feature.xsd. These are adapted from the basic GML components gml:AbstractFeatureType, gml:_Feature, gml:FeatureCollection, etc, but are preferred as the basis for more specific feature types in the context of XMML.

XMML Feature

Model from XmmlSchemaRepository:trunk/XMML/feature.xsd.

Model

Feature.png

Explanation

XMML Feature Collection is based on FeatureModel#GML_Feature

An XMML Feature adds the standard support properties and a (optional) generic relatedFeature property, which carries a pointer to another feature.

XMML Bounded Feature

Model from XmmlSchemaRepository:trunk/XMML/feature.xsd.

Model

BoundedFeature.png

Explanation

The XMML Bounded Feature makes the boundedBy property mandatory.

XMML Positioned Feature

Model from XmmlSchemaRepository:trunk/XMML/feature.xsd.

Model

PositionedFeature.png

Explanation

The XMML Positioned Feature adds
  • a mandatory gml:position property, whose value is a gml:Point, or which carries a reference to a point (following the GmlProperty pattern)
  • a (optional) positionMethod property, used to indicate the method used to determine the position above
  • a (optional) place property, used to indicate the location as a named place or map

XMML Feature Collection

Model from XmmlSchemaRepository:trunk/XMML/feature.xsd.

Model

FeatureCollection.png

Explanation

XMML Feature Collection is based on FeatureModel#GML_Feature_Collection

The XMML Feature Collection makes the boundedBy property mandatory, adds XMML's Standard Support Properties and relatedFeature, as well as the featureMember and featureMembers properties.


Issues and change requests

Readers are invited to add issues to this table - select [Edit Table] below. It is not mandatory to enter a solution, but change requests are more likely to be implemented if a concrete solution is proposed.

%EDITTABLE{ header="| # | By | Timestamp | Component(s) | Description of issue | Proposed solution | Resolution |" format="| row, -1 | text, 25, Unknown | label, 0, 23 Sep 2017 13:38 | textarea, 3x25, Component(s) | textarea, 3x25, Description | textarea, 3x25, Proposal | select, 1, Unaddressed, Progressing, Resolved |" changerows="on" }%
# By Timestamp Component(s) Description of issue Proposed solution Resolution
1 My org 14 May 2004 collar location A big whinge a proposed solution Unaddressed
Topic revision: r17 - 15 Oct 2010, UnknownUser
 

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