element <Polygon>
Namespace:
Type:
Content:
complex, 15 attributes, 3 elements
Subst.Gr:
may substitute for elements: Region, PositionInterval, PositionInterval, Region
Nillable:
(can be declared as nil using xsi:nil attribute in instance XML documents)
Defined:
globally in stc-v1.30.xsd; see XML source
Used:
never
XML Representation Summary
<Polygon
    IDREF_type
 = 
xs:string
    ID_type
 = 
xs:string
    coord_system_id
 = 
xs:IDREF
    epoch
 = 
xs:decimal
    fill_factor
 = 
xs:float : "1.0"
    frame_id
 = 
xs:IDREF
    hi_include
 = 
xs:boolean : "true"
    id
 = 
xs:ID
    idref
 = 
xs:IDREF
    lo_include
 = 
xs:boolean : "true"
    note
 = 
xs:string
    ucd
 = 
xs:string
    unit
 = 
("deg" | "deg deg m" | "deg deg Mpc" | "rad" | "h" | "arcmin" | "arcsec" | "m" | "km" | "mm" | "AU" | "pc" | "kpc" | "Mpc" | "lyr" | "")
    xlink:href
 = 
xs:anyURI
    xlink:type
 = 
("simple" | "extended" | "locator" | "arc" | "resource" | "title") : "simple"
    >
   
Content: 
Area?, Vertex+
</Polygon>
Content model elements (2):
Annotation
A polygon is a shape delineated by a list of vertices connected with lines, great circles, or small circles; the inside of the polygon is circumscribed counter-clockwise by the list of vertices; the polygon may be concave but not self-intersecting; the last vertex in the list is the predecessor of the first. For celestial coordinates it is assumed that we are looking at the sphere from the inside, with Right Ascension increasing to the left. Sides should span less than 180 deg in each coordinate.
XML Source (see within schema source)
<xs:element name="Polygon" nillable="true" substitutionGroup="Region" type="polygonType">
<xs:annotation>
<xs:documentation>
A polygon is a shape delineated by a list of vertices connected with lines, great circles, or small circles; the inside of the polygon is circumscribed counter-clockwise by the list of vertices; the polygon may be concave but not self-intersecting; the last vertex in the list is the predecessor of the first. For celestial coordinates it is assumed that we are looking at the sphere from the inside, with Right Ascension increasing to the left. Sides should span less than 180 deg in each coordinate.
</xs:documentation>
</xs:annotation>
</xs:element>
Attribute Detail (all declarations; 15)
coord_system_id
Type:
Use:
optional
Defined:
locally within regionType complexType
XML Source (see within schema source)
<xs:attribute name="coord_system_id" type="xs:IDREF" use="optional"/>

epoch
Type:
Use:
optional
Defined:
locally within spatialIntervalType complexType
XML Source (see within schema source)
<xs:attribute name="epoch" type="xs:decimal" use="optional"/>

fill_factor
Type:
Use:
optional
Default:
"1.0"
Defined:
locally within coordIntervalType complexType
Fraction of interval that is occupied by data
XML Source (see within schema source)
<xs:attribute default="1.0" name="fill_factor" type="xs:float" use="optional">
<xs:annotation>
<xs:documentation>Fraction of interval that is occupied by data</xs:documentation>
</xs:annotation>
</xs:attribute>

frame_id
Type:
Use:
optional
Defined:
locally within coordIntervalType complexType
XML Source (see within schema source)
<xs:attribute name="frame_id" type="xs:IDREF" use="optional"/>

hi_include
Type:
Use:
optional
Default:
"true"
Defined:
locally within coordIntervalType complexType
Limit to be included?
XML Source (see within schema source)
<xs:attribute default="true" name="hi_include" type="xs:boolean">
<xs:annotation>
<xs:documentation>Limit to be included?</xs:documentation>
</xs:annotation>
</xs:attribute>

id
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="id" type="xs:ID" use="optional"/>

ID_type
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="ID_type" type="xs:string" use="optional"/>

idref
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="idref" type="xs:IDREF" use="optional"/>

IDREF_type
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="IDREF_type" type="xs:string" use="optional"/>

lo_include
Type:
Use:
optional
Default:
"true"
Defined:
locally within coordIntervalType complexType
Limit to be included?
XML Source (see within schema source)
<xs:attribute default="true" name="lo_include" type="xs:boolean">
<xs:annotation>
<xs:documentation>Limit to be included?</xs:documentation>
</xs:annotation>
</xs:attribute>

note
Type:
Use:
optional
Defined:
locally within regionType complexType
XML Source (see within schema source)
<xs:attribute name="note" type="xs:string" use="optional"/>

ucd
Type:
Use:
optional
Defined:
locally within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute name="ucd" type="xs:string" use="optional"/>

unit
Type:
Use:
optional
Defined:
locally within spatialIntervalType complexType
XML Source (see within schema source)
<xs:attribute name="unit" type="posUnitType" use="optional"/>

xlink:href
Type:
Use:
optional
Defined:
by reference within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute ref="xlink:href" use="optional"/>

xlink:type
Type:
anonymous (restriction of xs:NMTOKEN)
Use:
optional
Default:
"simple"
Defined:
by reference within STCReference attributeGroup
XML Source (see within schema source)
<xs:attribute default="simple" ref="xlink:type" use="optional"/>
Content Element Detail (all declarations; 3)
Area
Type:
regionAreaType, simple content
Defined:
locally within regionType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" name="Area" type="regionAreaType"/>

Area
Type:
regionAreaType, simple content
Defined:
locally within regionType complexType
XML Source (see within schema source)
<xs:element minOccurs="0" name="Area" type="regionAreaType"/>

Vertex
Type:
vertexType, complex content
Defined:
locally within polygonType complexType
In order to form polygons, vertices are to be connected with straight line segments. In the case of spherical coordinates: greatcircle segments; if a smallCircle element si present, the vertex and its predecessor are to be connected with a smallcircle, by default in the CoordSys that is referenced; optionally, a pole may be specified (other than the CoordSys pole) that defines the smallcircle system
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" name="Vertex" type="vertexType">
<xs:annotation>
<xs:documentation>
In order to form polygons, vertices are to be connected with straight line segments. In the case of spherical coordinates: greatcircle segments; if a smallCircle element si present, the vertex and its predecessor are to be connected with a smallcircle, by default in the CoordSys that is referenced; optionally, a pole may be specified (other than the CoordSys pole) that defines the smallcircle system
</xs:documentation>
</xs:annotation>
</xs:element>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/