Showing:

Annotations
Attributes
Diagrams
Properties
Source
Used by
Element metobj:AbstractPointObjectType / metobj:priority
Namespace http://xml.fmi.fi/namespace/meteorology/conceptual-model/meteorological-objects/2009/11/09
Diagram
Diagram
Type int
Properties
content: simple
minOccurs: 0
maxOccurs: 1
Source
<element name="priority" type="int" minOccurs="0" maxOccurs="1"/>
Schema location http://xml.fmi.fi/schema/meteorology/conceptual-model/meteorological-objects/2009/11/09/metobjects-base.xsd
Complex Type metobj:AbstractPointObjectType
Namespace http://xml.fmi.fi/namespace/meteorology/conceptual-model/meteorological-objects/2009/11/09
Annotations
Abstract parent type for all Met Objects located at a single
geosaptial point or point-like location (airport, city, observation station,..).
Moving point objects can be modeled using DynamicMeteorologicalObject with multiple
point objects as collection content. Mutual display priority levels of point-like
objects can be given with displayPriority property: The rendering engine should
start dropping the objects out in descending priority order if it cannot properly
position all the point objects into the given display size using the given
preferredRenderingSize (the ones with lowest numeric priority value will remain
visible last).
Diagram
Diagram docindex4.tmp#id52 docindex5.tmp#id34 docindex6.tmp#id47 docindex7.tmp#id49 docindex8.tmp#id33 docindex9.tmp#id32 docindex30.tmp#id53 docindex31.tmp#id83 docindex32.tmp#id31 docindex38.tmp#id113 docindex44.tmp#id124 docindex45.tmp#id133 docindex46.tmp#id112 docindex47.tmp#id30 docindex48.tmp#id134 docindex48.tmp#id159 docindex48.tmp#id160 docindex48.tmp#id161 docindex48.tmp#id163 docindex48.tmp#id166 docindex48.tmp#id192 docindex48.tmp#id29 docindex132.tmp#id177 docindex233.tmp#id205 docindex234.tmp#id213
Type extension of metobj:AbstractMeteorologicalObjectType
Type hierarchy
Properties
abstract: true
Used by
Model gml:metaDataProperty* , gml:description{0,1} , gml:name* , gml:boundedBy{0,1} , gml:location{0,1} , gml:validTime{0,1} , gml:history{0,1} , gml:dataSource{0,1} , metobj:metaData{0,1} , metobj:creationTime , metobj:latestModificationTime{0,1} , metobj:shortInfo* , metobj:longInfo* , metobj:uncertaintyArea{0,1} , metobj:historyInterpolationRule{0,1} , (gml:pointProperty | metobj:knownPlaceProperty) , metobj:priority{0,1}
Children gml:boundedBy, gml:dataSource, gml:description, gml:history, gml:location, gml:metaDataProperty, gml:name, gml:pointProperty, gml:validTime, metobj:creationTime, metobj:historyInterpolationRule, metobj:knownPlaceProperty, metobj:latestModificationTime, metobj:longInfo, metobj:metaData, metobj:priority, metobj:shortInfo, metobj:uncertaintyArea
Attributes
QName Type Fixed Default Use Annotation
gml:id ID optional
Database handle for the object.  It is of XML type ID, so is constrained to be unique in the XML document within which it occurs.  An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods.  This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.
Source
<complexType name="AbstractPointObjectType" abstract="true">
  <annotation>
    <documentation>Abstract parent type for all Met Objects located at a single geosaptial point or point-like location (airport, city, observation station,..). Moving point objects can be modeled using DynamicMeteorologicalObject with multiple point objects as collection content. Mutual display priority levels of point-like objects can be given with displayPriority property: The rendering engine should start dropping the objects out in descending priority order if it cannot properly position all the point objects into the given display size using the given preferredRenderingSize (the ones with lowest numeric priority value will remain visible last).</documentation>
  </annotation>
  <complexContent>
    <extension base="metobj:AbstractMeteorologicalObjectType">
      <sequence>
        <choice>
          <element ref="gml:pointProperty" minOccurs="1" maxOccurs="1"/>
          <element ref="metobj:knownPlaceProperty" minOccurs="1" maxOccurs="1"/>
        </choice>
        <element name="priority" type="int" minOccurs="0" maxOccurs="1"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>
Schema location http://xml.fmi.fi/schema/meteorology/conceptual-model/meteorological-objects/2009/11/09/metobjects-base.xsd