Showing:

Annotations
Attributes
Diagrams
Properties
Source
Used by
Element womlcore:AbstractPointObjectType / womlcore:priority
Namespace http://xml.fmi.fi/namespace/woml/core/2010/09/13
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/woml/core/2010/09/13/woml-core.xsd
Element womlcore:AbstractPointObjectType / womlcore:effectiveRadius
Namespace http://xml.fmi.fi/namespace/woml/core/2010/09/13
Diagram
Diagram index123.tmp#id229 index123.tmp#id228
Type gml:MeasureType
Properties
content: complex
minOccurs: 0
maxOccurs: 1
Attributes
QName Type Fixed Default Use Annotation
uom anyURI required
Source
<element name="effectiveRadius" type="gml:MeasureType" minOccurs="0" maxOccurs="1"/>
Schema location http://xml.fmi.fi/schema/woml/core/2010/09/13/woml-core.xsd
Complex Type womlcore:AbstractPointObjectType
Namespace http://xml.fmi.fi/namespace/woml/core/2010/09/13
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. 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. The "effectiveRadius" element may be used to define the circular area around the single geospatial point that this object describes.
Diagram
Diagram index14.tmp#id49 index15.tmp#id31 index16.tmp#id44 index17.tmp#id46 index18.tmp#id30 index19.tmp#id29 index55.tmp#id50 index56.tmp#id80 index57.tmp#id28 index80.tmp#id115 index81.tmp#id126 index82.tmp#id135 index83.tmp#id114 index84.tmp#id27 index85.tmp#id137 index85.tmp#id162 index85.tmp#id163 index85.tmp#id164 index85.tmp#id166 index85.tmp#id136 index86.tmp#id169 index86.tmp#id205 index86.tmp#id26 index87.tmp#id189 index88.tmp#id218 index89.tmp#id226 index89.tmp#id227
Type extension of womlcore: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} , womlcore:metaData{0,1} , womlcore:creationTime , womlcore:latestModificationTime{0,1} , womlcore:shortInfo* , womlcore:longInfo* , womlcore:uncertaintyArea{0,1} , womlcore:historyInterpolationRule{0,1} , (gml:pointProperty | womlcore:knownPlaceProperty) , womlcore:priority{0,1} , womlcore:effectiveRadius{0,1}
Children gml:boundedBy, gml:dataSource, gml:description, gml:history, gml:location, gml:metaDataProperty, gml:name, gml:pointProperty, gml:validTime, womlcore:creationTime, womlcore:effectiveRadius, womlcore:historyInterpolationRule, womlcore:knownPlaceProperty, womlcore:latestModificationTime, womlcore:longInfo, womlcore:metaData, womlcore:priority, womlcore:shortInfo, womlcore: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. 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. The "effectiveRadius" element may be used to define the circular area around the single geospatial point that this object describes.</documentation>
  </annotation>
  <complexContent>
    <extension base="womlcore:AbstractMeteorologicalObjectType">
      <sequence>
        <choice>
          <element ref="gml:pointProperty" minOccurs="1" maxOccurs="1"/>
          <element ref="womlcore:knownPlaceProperty" minOccurs="1" maxOccurs="1"/>
        </choice>
        <element name="priority" type="int" minOccurs="0" maxOccurs="1"/>
        <element name="effectiveRadius" type="gml:MeasureType" minOccurs="0" maxOccurs="1"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>
Schema location http://xml.fmi.fi/schema/woml/core/2010/09/13/woml-core.xsd