1 |
mdittmar |
4290 |
<?xml version="1.0" encoding="UTF-8"?> |
2 |
|
|
<vo-dml:model xmlns:vo-dml="http://www.ivoa.net/xml/VODML/v1.0" |
3 |
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
4 |
|
|
xsi:schemaLocation="http://www.ivoa.net/xml/VODML/v1.0 http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/xsd/vo-dml-v1.0.xsd"> |
5 |
|
|
<name>stc2_coordinates</name> |
6 |
|
|
<description> |
7 |
|
|
TODO : Missing description : please, update your UML model asap. |
8 |
|
|
</description> |
9 |
|
|
<uri>http://ivoa.net/vodml/stc2_coordinates.vo-dml</uri> |
10 |
|
|
<title>STC2 Coordinates</title> |
11 |
|
|
<author>ahr</author> |
12 |
|
|
<version>2.0</version> |
13 |
|
|
<lastModified>2017-09-14T10:51:22</lastModified> |
14 |
|
|
<import> |
15 |
|
|
<name>ivoa</name> |
16 |
|
|
<url>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/ivoa/vo-dml/xml/IVOA-v1.0.vo-dml.xml</url> |
17 |
|
|
<documentationURL>http://volute.g-vo.org/svn/trunk/projects/dm/vo-dml/models/ivoa/vo-dml/IVOA.html</documentationURL> |
18 |
|
|
</import> |
19 |
|
|
|
20 |
|
|
<package> |
21 |
|
|
<vodml-id>CoordinateDomains</vodml-id> |
22 |
|
|
<name>CoordinateDomains</name> |
23 |
|
|
<description> |
24 |
|
|
TODO : Missing description : please, update your UML model asap. |
25 |
|
|
</description> |
26 |
|
|
|
27 |
|
|
|
28 |
|
|
<package> |
29 |
|
|
<vodml-id>CoordinateDomains.genericDomain</vodml-id> |
30 |
|
|
<name>genericDomain</name> |
31 |
|
|
<description> |
32 |
|
|
TODO : Missing description : please, update your UML model asap. |
33 |
|
|
</description> |
34 |
|
|
<dataType> |
35 |
|
|
<vodml-id>CoordinateDomains.genericDomain.GenericCoordValue</vodml-id> |
36 |
|
|
<name>GenericCoordValue</name> |
37 |
|
|
<description>This data type contains the generic coordinate value and a reference to a GenericFrame through a coordinate axis and Coordinate Space object.</description> |
38 |
|
|
<extends> |
39 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue</vodml-ref> |
40 |
|
|
</extends> |
41 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
42 |
|
|
<role> |
43 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
44 |
|
|
</role> |
45 |
|
|
<datatype> |
46 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
47 |
|
|
</datatype> |
48 |
|
|
</constraint> |
49 |
|
|
</dataType> |
50 |
|
|
|
51 |
|
|
<objectType> |
52 |
|
|
<vodml-id>CoordinateDomains.genericDomain.GenericFrame</vodml-id> |
53 |
|
|
<name>GenericFrame</name> |
54 |
|
|
<description>A Generic Coordinate Frame allows coordinates other than Time, Space, Spectral, Redshift, and Polarization to the defined; e.g., flux, temperature, pressure, etc. It SHALL contain one Generic Coordinate Space object.</description> |
55 |
|
|
<extends> |
56 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
57 |
|
|
</extends> |
58 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
59 |
|
|
<role> |
60 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
61 |
|
|
</role> |
62 |
|
|
<datatype> |
63 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.genericDomain.GenericCoordSpace</vodml-ref> |
64 |
|
|
</datatype> |
65 |
|
|
</constraint> |
66 |
|
|
</objectType> |
67 |
|
|
|
68 |
|
|
<objectType> |
69 |
|
|
<vodml-id>CoordinateDomains.genericDomain.GenericCoordSpace</vodml-id> |
70 |
|
|
<name>GenericCoordSpace</name> |
71 |
|
|
<description>The GenericCoordSpace SHALL include one CoordAxis object.</description> |
72 |
|
|
<extends> |
73 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
74 |
|
|
</extends> |
75 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
76 |
|
|
<role> |
77 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
78 |
|
|
</role> |
79 |
|
|
<datatype> |
80 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
81 |
|
|
</datatype> |
82 |
|
|
</constraint> |
83 |
|
|
</objectType> |
84 |
|
|
|
85 |
|
|
</package> |
86 |
|
|
|
87 |
|
|
|
88 |
|
|
|
89 |
|
|
<package> |
90 |
|
|
<vodml-id>CoordinateDomains.pixelDomain</vodml-id> |
91 |
|
|
<name>pixelDomain</name> |
92 |
|
|
<description> |
93 |
|
|
TODO : Missing description : please, update your UML model asap. |
94 |
|
|
</description> |
95 |
|
|
<enumeration> |
96 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.Handedness</vodml-id> |
97 |
|
|
<name>Handedness</name> |
98 |
|
|
<description>Handedness of a coordinate frame.</description> |
99 |
|
|
<literal> |
100 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.Handedness.right</vodml-id> |
101 |
|
|
<name>right</name> |
102 |
|
|
<description> |
103 |
|
|
TODO : Missing description : please, update your UML model asap. |
104 |
|
|
</description> |
105 |
|
|
</literal> |
106 |
|
|
<literal> |
107 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.Handedness.left</vodml-id> |
108 |
|
|
<name>left</name> |
109 |
|
|
<description> |
110 |
|
|
TODO : Missing description : please, update your UML model asap. |
111 |
|
|
</description> |
112 |
|
|
</literal> |
113 |
|
|
</enumeration> |
114 |
|
|
|
115 |
|
|
<dataType abstract="true"> |
116 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelCoordinate</vodml-id> |
117 |
|
|
<name>PixelCoordinate</name> |
118 |
|
|
<description>A PixelCoordinate is a real-valued coordinate in 1-, 2-, or 3-dimensional pixel space, with each component referenced to its pixel frame through its associated Pixel Axis. This data type specifies an arbitrary location in the Pixel Frame, rather than identifying a specific pixel. The vector is built up from RealPixelValue scalar components.</description> |
119 |
|
|
<extends> |
120 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue</vodml-ref> |
121 |
|
|
</extends> |
122 |
|
|
</dataType> |
123 |
|
|
|
124 |
|
|
<dataType> |
125 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelCoord1D</vodml-id> |
126 |
|
|
<name>PixelCoord1D</name> |
127 |
|
|
<description>The 1-dimensional Pixel Coordinate value.</description> |
128 |
|
|
<extends> |
129 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.PixelCoordinate</vodml-ref> |
130 |
|
|
</extends> |
131 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
132 |
|
|
<role> |
133 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
134 |
|
|
</role> |
135 |
|
|
<datatype> |
136 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.RealPixelValue</vodml-ref> |
137 |
|
|
</datatype> |
138 |
|
|
</constraint> |
139 |
|
|
</dataType> |
140 |
|
|
|
141 |
|
|
<dataType> |
142 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelCoord3D</vodml-id> |
143 |
|
|
<name>PixelCoord3D</name> |
144 |
|
|
<description>The 3-dimensional Pixel Coordinate value.</description> |
145 |
|
|
<extends> |
146 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.PixelCoordinate</vodml-ref> |
147 |
|
|
</extends> |
148 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
149 |
|
|
<role> |
150 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
151 |
|
|
</role> |
152 |
|
|
<datatype> |
153 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.RealPixelValue</vodml-ref> |
154 |
|
|
</datatype> |
155 |
|
|
</constraint> |
156 |
|
|
</dataType> |
157 |
|
|
|
158 |
|
|
<dataType> |
159 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelCoord2D</vodml-id> |
160 |
|
|
<name>PixelCoord2D</name> |
161 |
|
|
<description>The 2-dimensional Pixel Coordinate value.</description> |
162 |
|
|
<extends> |
163 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.PixelCoordinate</vodml-ref> |
164 |
|
|
</extends> |
165 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
166 |
|
|
<role> |
167 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
168 |
|
|
</role> |
169 |
|
|
<datatype> |
170 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.RealPixelValue</vodml-ref> |
171 |
|
|
</datatype> |
172 |
|
|
</constraint> |
173 |
|
|
</dataType> |
174 |
|
|
|
175 |
|
|
<dataType> |
176 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelIndex1D</vodml-id> |
177 |
|
|
<name>PixelIndex1D</name> |
178 |
|
|
<description>The 1-dimensional Pixel Index value.</description> |
179 |
|
|
<extends> |
180 |
|
|
<vodml-ref>stc2_coordinates:coords.IntegerCoordValue</vodml-ref> |
181 |
|
|
</extends> |
182 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
183 |
|
|
<role> |
184 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue.coordAxis</vodml-ref> |
185 |
|
|
</role> |
186 |
|
|
<datatype> |
187 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.PixelAxis</vodml-ref> |
188 |
|
|
</datatype> |
189 |
|
|
</constraint> |
190 |
|
|
</dataType> |
191 |
|
|
|
192 |
|
|
<dataType> |
193 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.RealPixelValue</vodml-id> |
194 |
|
|
<name>RealPixelValue</name> |
195 |
|
|
<description>The 1-dimensional pixel value, to be used for non-index (non-integer) pixel coordinate values, such as may result from analysis calculations.</description> |
196 |
|
|
<extends> |
197 |
|
|
<vodml-ref>stc2_coordinates:coords.RealCoordValue</vodml-ref> |
198 |
|
|
</extends> |
199 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
200 |
|
|
<role> |
201 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue.coordAxis</vodml-ref> |
202 |
|
|
</role> |
203 |
|
|
<datatype> |
204 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.PixelAxis</vodml-ref> |
205 |
|
|
</datatype> |
206 |
|
|
</constraint> |
207 |
|
|
</dataType> |
208 |
|
|
|
209 |
|
|
<objectType> |
210 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelFrame</vodml-id> |
211 |
|
|
<name>PixelFrame</name> |
212 |
|
|
<description>A PixelFrame forms the Coordinate Frame for a 1-D, 2-D, or 3-D PixelSpace, and is included in the PixelCoordSystem. It SHALL contain one PixelSpace object. Note that, unlike other coordinate frames, a Pixel Frame SHOULD have at least one Frame Transform mapping: pixels without reference to the wider world are meaningless.</description> |
213 |
|
|
<extends> |
214 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
215 |
|
|
</extends> |
216 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
217 |
|
|
<role> |
218 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
219 |
|
|
</role> |
220 |
|
|
<datatype> |
221 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.PixelSpace</vodml-ref> |
222 |
|
|
</datatype> |
223 |
|
|
</constraint> |
224 |
|
|
</objectType> |
225 |
|
|
|
226 |
|
|
<objectType> |
227 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelSpace</vodml-id> |
228 |
|
|
<name>PixelSpace</name> |
229 |
|
|
<description>A PixelSpace SHALL include one, two, or three ordered PixelAxis objects, defining a pixel object (sub)set that can be the native or target space for a FrameTransform mapping object.</description> |
230 |
|
|
<extends> |
231 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
232 |
|
|
</extends> |
233 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
234 |
|
|
<role> |
235 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
236 |
|
|
</role> |
237 |
|
|
<datatype> |
238 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.PixelAxis</vodml-ref> |
239 |
|
|
</datatype> |
240 |
|
|
</constraint> |
241 |
|
|
<attribute> |
242 |
|
|
<vodml-id>CoordinateDomains.pixelDomain.PixelSpace.handedness</vodml-id> |
243 |
|
|
<name>handedness</name> |
244 |
|
|
<description> |
245 |
|
|
TODO : Missing description : please, update your UML model asap. |
246 |
|
|
</description> |
247 |
|
|
<datatype> |
248 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.Handedness</vodml-ref> |
249 |
|
|
</datatype> |
250 |
|
|
<multiplicity> |
251 |
|
|
<minOccurs>0</minOccurs> |
252 |
|
|
<maxOccurs>1</maxOccurs> |
253 |
|
|
</multiplicity> |
254 |
|
|
</attribute> |
255 |
|
|
</objectType> |
256 |
|
|
|
257 |
|
|
</package> |
258 |
|
|
|
259 |
|
|
|
260 |
|
|
|
261 |
|
|
<package> |
262 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain</vodml-id> |
263 |
|
|
<name>polarizationDomain</name> |
264 |
|
|
<description> |
265 |
|
|
TODO : Missing description : please, update your UML model asap. |
266 |
|
|
</description> |
267 |
|
|
<enumeration> |
268 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircularEnum</vodml-id> |
269 |
|
|
<name>PolCircularEnum</name> |
270 |
|
|
<description>The four circular polarization coordinate values for a polarization coordinate.</description> |
271 |
|
|
<literal> |
272 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircularEnum.RR</vodml-id> |
273 |
|
|
<name>RR</name> |
274 |
|
|
<description> |
275 |
|
|
TODO : Missing description : please, update your UML model asap. |
276 |
|
|
</description> |
277 |
|
|
</literal> |
278 |
|
|
<literal> |
279 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircularEnum.LL</vodml-id> |
280 |
|
|
<name>LL</name> |
281 |
|
|
<description> |
282 |
|
|
TODO : Missing description : please, update your UML model asap. |
283 |
|
|
</description> |
284 |
|
|
</literal> |
285 |
|
|
<literal> |
286 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircularEnum.RL</vodml-id> |
287 |
|
|
<name>RL</name> |
288 |
|
|
<description> |
289 |
|
|
TODO : Missing description : please, update your UML model asap. |
290 |
|
|
</description> |
291 |
|
|
</literal> |
292 |
|
|
<literal> |
293 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircularEnum.LR</vodml-id> |
294 |
|
|
<name>LR</name> |
295 |
|
|
<description> |
296 |
|
|
TODO : Missing description : please, update your UML model asap. |
297 |
|
|
</description> |
298 |
|
|
</literal> |
299 |
|
|
</enumeration> |
300 |
|
|
|
301 |
|
|
<enumeration> |
302 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinearEnum</vodml-id> |
303 |
|
|
<name>PolLinearEnum</name> |
304 |
|
|
<description>The four linear polarization coordinate values for a polarization coordinate.</description> |
305 |
|
|
<literal> |
306 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinearEnum.XX</vodml-id> |
307 |
|
|
<name>XX</name> |
308 |
|
|
<description> |
309 |
|
|
TODO : Missing description : please, update your UML model asap. |
310 |
|
|
</description> |
311 |
|
|
</literal> |
312 |
|
|
<literal> |
313 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinearEnum.YY</vodml-id> |
314 |
|
|
<name>YY</name> |
315 |
|
|
<description> |
316 |
|
|
TODO : Missing description : please, update your UML model asap. |
317 |
|
|
</description> |
318 |
|
|
</literal> |
319 |
|
|
<literal> |
320 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinearEnum.XY</vodml-id> |
321 |
|
|
<name>XY</name> |
322 |
|
|
<description> |
323 |
|
|
TODO : Missing description : please, update your UML model asap. |
324 |
|
|
</description> |
325 |
|
|
</literal> |
326 |
|
|
<literal> |
327 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinearEnum.YX</vodml-id> |
328 |
|
|
<name>YX</name> |
329 |
|
|
<description> |
330 |
|
|
TODO : Missing description : please, update your UML model asap. |
331 |
|
|
</description> |
332 |
|
|
</literal> |
333 |
|
|
</enumeration> |
334 |
|
|
|
335 |
|
|
<enumeration> |
336 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokesEnum</vodml-id> |
337 |
|
|
<name>PolStokesEnum</name> |
338 |
|
|
<description>The four Stokes coordinate values for a polarization coordinate.</description> |
339 |
|
|
<literal> |
340 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokesEnum.I</vodml-id> |
341 |
|
|
<name>I</name> |
342 |
|
|
<description> |
343 |
|
|
TODO : Missing description : please, update your UML model asap. |
344 |
|
|
</description> |
345 |
|
|
</literal> |
346 |
|
|
<literal> |
347 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokesEnum.Q</vodml-id> |
348 |
|
|
<name>Q</name> |
349 |
|
|
<description> |
350 |
|
|
TODO : Missing description : please, update your UML model asap. |
351 |
|
|
</description> |
352 |
|
|
</literal> |
353 |
|
|
<literal> |
354 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokesEnum.U</vodml-id> |
355 |
|
|
<name>U</name> |
356 |
|
|
<description> |
357 |
|
|
TODO : Missing description : please, update your UML model asap. |
358 |
|
|
</description> |
359 |
|
|
</literal> |
360 |
|
|
<literal> |
361 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokesEnum.V</vodml-id> |
362 |
|
|
<name>V</name> |
363 |
|
|
<description> |
364 |
|
|
TODO : Missing description : please, update your UML model asap. |
365 |
|
|
</description> |
366 |
|
|
</literal> |
367 |
|
|
</enumeration> |
368 |
|
|
|
369 |
|
|
<enumeration> |
370 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVectorEnum</vodml-id> |
371 |
|
|
<name>PolVectorEnum</name> |
372 |
|
|
<description>The four polarization vector coordinate values for a polarization coordinate.</description> |
373 |
|
|
<literal> |
374 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVectorEnum.I</vodml-id> |
375 |
|
|
<name>I</name> |
376 |
|
|
<description> |
377 |
|
|
TODO : Missing description : please, update your UML model asap. |
378 |
|
|
</description> |
379 |
|
|
</literal> |
380 |
|
|
<literal> |
381 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVectorEnum.PF</vodml-id> |
382 |
|
|
<name>PF</name> |
383 |
|
|
<description> |
384 |
|
|
TODO : Missing description : please, update your UML model asap. |
385 |
|
|
</description> |
386 |
|
|
</literal> |
387 |
|
|
<literal> |
388 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVectorEnum.PP</vodml-id> |
389 |
|
|
<name>PP</name> |
390 |
|
|
<description> |
391 |
|
|
TODO : Missing description : please, update your UML model asap. |
392 |
|
|
</description> |
393 |
|
|
</literal> |
394 |
|
|
<literal> |
395 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVectorEnum.PA</vodml-id> |
396 |
|
|
<name>PA</name> |
397 |
|
|
<description> |
398 |
|
|
TODO : Missing description : please, update your UML model asap. |
399 |
|
|
</description> |
400 |
|
|
</literal> |
401 |
|
|
</enumeration> |
402 |
|
|
|
403 |
|
|
<enumeration> |
404 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum</vodml-id> |
405 |
|
|
<name>PolEnum</name> |
406 |
|
|
<description>PolEnum contains all polarization coordinate values. The values for each of the four types of polarization coordinates are contained in separate derived (by restriction) enumeration types.</description> |
407 |
|
|
<literal> |
408 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.I</vodml-id> |
409 |
|
|
<name>I</name> |
410 |
|
|
<description> |
411 |
|
|
TODO : Missing description : please, update your UML model asap. |
412 |
|
|
</description> |
413 |
|
|
</literal> |
414 |
|
|
<literal> |
415 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.Q</vodml-id> |
416 |
|
|
<name>Q</name> |
417 |
|
|
<description> |
418 |
|
|
TODO : Missing description : please, update your UML model asap. |
419 |
|
|
</description> |
420 |
|
|
</literal> |
421 |
|
|
<literal> |
422 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.U</vodml-id> |
423 |
|
|
<name>U</name> |
424 |
|
|
<description> |
425 |
|
|
TODO : Missing description : please, update your UML model asap. |
426 |
|
|
</description> |
427 |
|
|
</literal> |
428 |
|
|
<literal> |
429 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.V</vodml-id> |
430 |
|
|
<name>V</name> |
431 |
|
|
<description> |
432 |
|
|
TODO : Missing description : please, update your UML model asap. |
433 |
|
|
</description> |
434 |
|
|
</literal> |
435 |
|
|
<literal> |
436 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.RR</vodml-id> |
437 |
|
|
<name>RR</name> |
438 |
|
|
<description> |
439 |
|
|
TODO : Missing description : please, update your UML model asap. |
440 |
|
|
</description> |
441 |
|
|
</literal> |
442 |
|
|
<literal> |
443 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.LL</vodml-id> |
444 |
|
|
<name>LL</name> |
445 |
|
|
<description> |
446 |
|
|
TODO : Missing description : please, update your UML model asap. |
447 |
|
|
</description> |
448 |
|
|
</literal> |
449 |
|
|
<literal> |
450 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.RL</vodml-id> |
451 |
|
|
<name>RL</name> |
452 |
|
|
<description> |
453 |
|
|
TODO : Missing description : please, update your UML model asap. |
454 |
|
|
</description> |
455 |
|
|
</literal> |
456 |
|
|
<literal> |
457 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.LR</vodml-id> |
458 |
|
|
<name>LR</name> |
459 |
|
|
<description> |
460 |
|
|
TODO : Missing description : please, update your UML model asap. |
461 |
|
|
</description> |
462 |
|
|
</literal> |
463 |
|
|
<literal> |
464 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.XX</vodml-id> |
465 |
|
|
<name>XX</name> |
466 |
|
|
<description> |
467 |
|
|
TODO : Missing description : please, update your UML model asap. |
468 |
|
|
</description> |
469 |
|
|
</literal> |
470 |
|
|
<literal> |
471 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.YY</vodml-id> |
472 |
|
|
<name>YY</name> |
473 |
|
|
<description> |
474 |
|
|
TODO : Missing description : please, update your UML model asap. |
475 |
|
|
</description> |
476 |
|
|
</literal> |
477 |
|
|
<literal> |
478 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.XY</vodml-id> |
479 |
|
|
<name>XY</name> |
480 |
|
|
<description> |
481 |
|
|
TODO : Missing description : please, update your UML model asap. |
482 |
|
|
</description> |
483 |
|
|
</literal> |
484 |
|
|
<literal> |
485 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.YX</vodml-id> |
486 |
|
|
<name>YX</name> |
487 |
|
|
<description> |
488 |
|
|
TODO : Missing description : please, update your UML model asap. |
489 |
|
|
</description> |
490 |
|
|
</literal> |
491 |
|
|
<literal> |
492 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.I1</vodml-id> |
493 |
|
|
<name>I1</name> |
494 |
|
|
<description> |
495 |
|
|
TODO : Missing description : please, update your UML model asap. |
496 |
|
|
</description> |
497 |
|
|
</literal> |
498 |
|
|
<literal> |
499 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.PF</vodml-id> |
500 |
|
|
<name>PF</name> |
501 |
|
|
<description> |
502 |
|
|
TODO : Missing description : please, update your UML model asap. |
503 |
|
|
</description> |
504 |
|
|
</literal> |
505 |
|
|
<literal> |
506 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.PP</vodml-id> |
507 |
|
|
<name>PP</name> |
508 |
|
|
<description> |
509 |
|
|
TODO : Missing description : please, update your UML model asap. |
510 |
|
|
</description> |
511 |
|
|
</literal> |
512 |
|
|
<literal> |
513 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolEnum.PA</vodml-id> |
514 |
|
|
<name>PA</name> |
515 |
|
|
<description> |
516 |
|
|
TODO : Missing description : please, update your UML model asap. |
517 |
|
|
</description> |
518 |
|
|
</literal> |
519 |
|
|
</enumeration> |
520 |
|
|
|
521 |
|
|
<dataType abstract="true"> |
522 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCoordValue</vodml-id> |
523 |
|
|
<name>PolCoordValue</name> |
524 |
|
|
<description>The abstract data type PolCoordValue contains a reference to a PolarizationFrame through a DiscreteAxis and PolarizationSpace object and allows the equivalent data types PolStokes, PolCircular, PolLinear, and PolVector coordinate values to be specified as derived data types.</description> |
525 |
|
|
<extends> |
526 |
|
|
<vodml-ref>stc2_coordinates:coords.DiscreteCoordValue</vodml-ref> |
527 |
|
|
</extends> |
528 |
|
|
<attribute> |
529 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCoordValue.cval</vodml-id> |
530 |
|
|
<name>cval</name> |
531 |
|
|
<description> |
532 |
|
|
TODO : Missing description : please, update your UML model asap. |
533 |
|
|
</description> |
534 |
|
|
<datatype> |
535 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolEnum</vodml-ref> |
536 |
|
|
</datatype> |
537 |
|
|
<multiplicity> |
538 |
|
|
<minOccurs>1</minOccurs> |
539 |
|
|
<maxOccurs>1</maxOccurs> |
540 |
|
|
</multiplicity> |
541 |
|
|
</attribute> |
542 |
|
|
</dataType> |
543 |
|
|
|
544 |
|
|
<dataType> |
545 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolStokes</vodml-id> |
546 |
|
|
<name>PolStokes</name> |
547 |
|
|
<description>Stokes polarization coordinate value.</description> |
548 |
|
|
<extends> |
549 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue</vodml-ref> |
550 |
|
|
</extends> |
551 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
552 |
|
|
<role> |
553 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue.cval</vodml-ref> |
554 |
|
|
</role> |
555 |
|
|
<datatype> |
556 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolStokesEnum</vodml-ref> |
557 |
|
|
</datatype> |
558 |
|
|
</constraint> |
559 |
|
|
</dataType> |
560 |
|
|
|
561 |
|
|
<dataType> |
562 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolCircular</vodml-id> |
563 |
|
|
<name>PolCircular</name> |
564 |
|
|
<description>Circular polarization coordinate value.</description> |
565 |
|
|
<extends> |
566 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue</vodml-ref> |
567 |
|
|
</extends> |
568 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
569 |
|
|
<role> |
570 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue.cval</vodml-ref> |
571 |
|
|
</role> |
572 |
|
|
<datatype> |
573 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCircularEnum</vodml-ref> |
574 |
|
|
</datatype> |
575 |
|
|
</constraint> |
576 |
|
|
</dataType> |
577 |
|
|
|
578 |
|
|
<dataType> |
579 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolLinear</vodml-id> |
580 |
|
|
<name>PolLinear</name> |
581 |
|
|
<description>Linear polarization coordinate value.</description> |
582 |
|
|
<extends> |
583 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue</vodml-ref> |
584 |
|
|
</extends> |
585 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
586 |
|
|
<role> |
587 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue.cval</vodml-ref> |
588 |
|
|
</role> |
589 |
|
|
<datatype> |
590 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolLinearEnum</vodml-ref> |
591 |
|
|
</datatype> |
592 |
|
|
</constraint> |
593 |
|
|
</dataType> |
594 |
|
|
|
595 |
|
|
<dataType> |
596 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolVector</vodml-id> |
597 |
|
|
<name>PolVector</name> |
598 |
|
|
<description>Vector polarization coordinate value.</description> |
599 |
|
|
<extends> |
600 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue</vodml-ref> |
601 |
|
|
</extends> |
602 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
603 |
|
|
<role> |
604 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolCoordValue.cval</vodml-ref> |
605 |
|
|
</role> |
606 |
|
|
<datatype> |
607 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolVectorEnum</vodml-ref> |
608 |
|
|
</datatype> |
609 |
|
|
</constraint> |
610 |
|
|
</dataType> |
611 |
|
|
|
612 |
|
|
<objectType> |
613 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolarizationFrame</vodml-id> |
614 |
|
|
<name>PolarizationFrame</name> |
615 |
|
|
<description>A Polarization Frame SHALL contain one PolarizationSpace object. It may need a reference to a spatial frame (TBD).</description> |
616 |
|
|
<extends> |
617 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
618 |
|
|
</extends> |
619 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
620 |
|
|
<role> |
621 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
622 |
|
|
</role> |
623 |
|
|
<datatype> |
624 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolarizationSpace</vodml-ref> |
625 |
|
|
</datatype> |
626 |
|
|
</constraint> |
627 |
|
|
</objectType> |
628 |
|
|
|
629 |
|
|
<objectType> |
630 |
|
|
<vodml-id>CoordinateDomains.polarizationDomain.PolarizationSpace</vodml-id> |
631 |
|
|
<name>PolarizationSpace</name> |
632 |
|
|
<description>The PolarizationSpace SHALL include one DiscreteAxis object, since polarization is an enumerated coordinate.</description> |
633 |
|
|
<extends> |
634 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
635 |
|
|
</extends> |
636 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
637 |
|
|
<role> |
638 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
639 |
|
|
</role> |
640 |
|
|
<datatype> |
641 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.DiscreteAxis</vodml-ref> |
642 |
|
|
</datatype> |
643 |
|
|
</constraint> |
644 |
|
|
</objectType> |
645 |
|
|
|
646 |
|
|
</package> |
647 |
|
|
|
648 |
|
|
|
649 |
|
|
|
650 |
|
|
<package> |
651 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain</vodml-id> |
652 |
|
|
<name>redshiftDomain</name> |
653 |
|
|
<description> |
654 |
|
|
TODO : Missing description : please, update your UML model asap. |
655 |
|
|
</description> |
656 |
|
|
<enumeration> |
657 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerDefinition</vodml-id> |
658 |
|
|
<name>DopplerDefinition</name> |
659 |
|
|
<description>Doppler/redshift definition</description> |
660 |
|
|
<literal> |
661 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerDefinition.optical</vodml-id> |
662 |
|
|
<name>optical</name> |
663 |
|
|
<description> |
664 |
|
|
TODO : Missing description : please, update your UML model asap. |
665 |
|
|
</description> |
666 |
|
|
</literal> |
667 |
|
|
<literal> |
668 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerDefinition.radio</vodml-id> |
669 |
|
|
<name>radio</name> |
670 |
|
|
<description> |
671 |
|
|
TODO : Missing description : please, update your UML model asap. |
672 |
|
|
</description> |
673 |
|
|
</literal> |
674 |
|
|
<literal> |
675 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerDefinition.relativistic</vodml-id> |
676 |
|
|
<name>relativistic</name> |
677 |
|
|
<description> |
678 |
|
|
TODO : Missing description : please, update your UML model asap. |
679 |
|
|
</description> |
680 |
|
|
</literal> |
681 |
|
|
<literal> |
682 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerDefinition.redshift</vodml-id> |
683 |
|
|
<name>redshift</name> |
684 |
|
|
<description> |
685 |
|
|
TODO : Missing description : please, update your UML model asap. |
686 |
|
|
</description> |
687 |
|
|
</literal> |
688 |
|
|
</enumeration> |
689 |
|
|
|
690 |
|
|
<dataType abstract="true"> |
691 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.RedshiftValue</vodml-id> |
692 |
|
|
<name>RedshiftValue</name> |
693 |
|
|
<description>The abstract data type RedshiftValue contains a reference to a RedshiftFrame through the coordinate axis and Spectral Space objects and allows the equivalent data types Redshift and DopplerVelocity coordinate values to be specified as derived data types.</description> |
694 |
|
|
<extends> |
695 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue</vodml-ref> |
696 |
|
|
</extends> |
697 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
698 |
|
|
<role> |
699 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
700 |
|
|
</role> |
701 |
|
|
<datatype> |
702 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
703 |
|
|
</datatype> |
704 |
|
|
</constraint> |
705 |
|
|
</dataType> |
706 |
|
|
|
707 |
|
|
<dataType> |
708 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.Redshift</vodml-id> |
709 |
|
|
<name>Redshift</name> |
710 |
|
|
<description>The RedshiftValue expressed as a unitless redshift (z)</description> |
711 |
|
|
<extends> |
712 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.redshiftDomain.RedshiftValue</vodml-ref> |
713 |
|
|
</extends> |
714 |
|
|
</dataType> |
715 |
|
|
|
716 |
|
|
<dataType> |
717 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerVelocity</vodml-id> |
718 |
|
|
<name>DopplerVelocity</name> |
719 |
|
|
<description>The RedshiftValue expressed as a DopplerVelocity, requiring a DopplerDefinition (default: optical).</description> |
720 |
|
|
<extends> |
721 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.redshiftDomain.RedshiftValue</vodml-ref> |
722 |
|
|
</extends> |
723 |
|
|
<attribute> |
724 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.DopplerVelocity.dopplerDefinition</vodml-id> |
725 |
|
|
<name>dopplerDefinition</name> |
726 |
|
|
<description> |
727 |
|
|
TODO : Missing description : please, update your UML model asap. |
728 |
|
|
</description> |
729 |
|
|
<datatype> |
730 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.redshiftDomain.DopplerDefinition</vodml-ref> |
731 |
|
|
</datatype> |
732 |
|
|
<multiplicity> |
733 |
|
|
<minOccurs>0</minOccurs> |
734 |
|
|
<maxOccurs>1</maxOccurs> |
735 |
|
|
</multiplicity> |
736 |
|
|
</attribute> |
737 |
|
|
</dataType> |
738 |
|
|
|
739 |
|
|
<objectType> |
740 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.RedshiftFrame</vodml-id> |
741 |
|
|
<name>RedshiftFrame</name> |
742 |
|
|
<description>The RedshiftFrame is the Frame for redshift and Doppler velocity coordinates. It requires a Reference Position in the associated AstroCoordSystem object (which need to be specified in phase space) and SHALL include a RedshiftSpace.</description> |
743 |
|
|
<extends> |
744 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
745 |
|
|
</extends> |
746 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
747 |
|
|
<role> |
748 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
749 |
|
|
</role> |
750 |
|
|
<datatype> |
751 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.redshiftDomain.RedshiftSpace</vodml-ref> |
752 |
|
|
</datatype> |
753 |
|
|
</constraint> |
754 |
|
|
</objectType> |
755 |
|
|
|
756 |
|
|
<objectType> |
757 |
|
|
<vodml-id>CoordinateDomains.redshiftDomain.RedshiftSpace</vodml-id> |
758 |
|
|
<name>RedshiftSpace</name> |
759 |
|
|
<description>The RedshiftSpace SHALL include one CoordAxis object, which will typically not include any of its optional attributes other than Name.</description> |
760 |
|
|
<extends> |
761 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
762 |
|
|
</extends> |
763 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
764 |
|
|
<role> |
765 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
766 |
|
|
</role> |
767 |
|
|
<datatype> |
768 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
769 |
|
|
</datatype> |
770 |
|
|
</constraint> |
771 |
|
|
</objectType> |
772 |
|
|
|
773 |
|
|
</package> |
774 |
|
|
|
775 |
|
|
|
776 |
|
|
|
777 |
|
|
<package> |
778 |
|
|
<vodml-id>CoordinateDomains.spatialDomain</vodml-id> |
779 |
|
|
<name>spatialDomain</name> |
780 |
|
|
<description> |
781 |
|
|
TODO : Missing description : please, update your UML model asap. |
782 |
|
|
</description> |
783 |
|
|
<enumeration> |
784 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame</vodml-id> |
785 |
|
|
<name>SpaceStdRefFrame</name> |
786 |
|
|
<description>This is the enumerated list of allowed standard spatial reference frames.</description> |
787 |
|
|
<literal> |
788 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.ICRS</vodml-id> |
789 |
|
|
<name>ICRS</name> |
790 |
|
|
<description> |
791 |
|
|
TODO : Missing description : please, update your UML model asap. |
792 |
|
|
</description> |
793 |
|
|
</literal> |
794 |
|
|
<literal> |
795 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.FK4</vodml-id> |
796 |
|
|
<name>FK4</name> |
797 |
|
|
<description> |
798 |
|
|
TODO : Missing description : please, update your UML model asap. |
799 |
|
|
</description> |
800 |
|
|
</literal> |
801 |
|
|
<literal> |
802 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.FK5</vodml-id> |
803 |
|
|
<name>FK5</name> |
804 |
|
|
<description> |
805 |
|
|
TODO : Missing description : please, update your UML model asap. |
806 |
|
|
</description> |
807 |
|
|
</literal> |
808 |
|
|
<literal> |
809 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GALACTIC</vodml-id> |
810 |
|
|
<name>GALACTIC</name> |
811 |
|
|
<description> |
812 |
|
|
TODO : Missing description : please, update your UML model asap. |
813 |
|
|
</description> |
814 |
|
|
</literal> |
815 |
|
|
<literal> |
816 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.ECLIPTIC</vodml-id> |
817 |
|
|
<name>ECLIPTIC</name> |
818 |
|
|
<description> |
819 |
|
|
TODO : Missing description : please, update your UML model asap. |
820 |
|
|
</description> |
821 |
|
|
</literal> |
822 |
|
|
<literal> |
823 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.CUSTOM</vodml-id> |
824 |
|
|
<name>CUSTOM</name> |
825 |
|
|
<description> |
826 |
|
|
TODO : Missing description : please, update your UML model asap. |
827 |
|
|
</description> |
828 |
|
|
</literal> |
829 |
|
|
<literal> |
830 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GALACTIC_I</vodml-id> |
831 |
|
|
<name>GALACTIC_I</name> |
832 |
|
|
<description> |
833 |
|
|
TODO : Missing description : please, update your UML model asap. |
834 |
|
|
</description> |
835 |
|
|
</literal> |
836 |
|
|
<literal> |
837 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.SUPER_GALACTIC</vodml-id> |
838 |
|
|
<name>SUPER_GALACTIC</name> |
839 |
|
|
<description> |
840 |
|
|
TODO : Missing description : please, update your UML model asap. |
841 |
|
|
</description> |
842 |
|
|
</literal> |
843 |
|
|
<literal> |
844 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.AZ_EL</vodml-id> |
845 |
|
|
<name>AZ_EL</name> |
846 |
|
|
<description> |
847 |
|
|
TODO : Missing description : please, update your UML model asap. |
848 |
|
|
</description> |
849 |
|
|
</literal> |
850 |
|
|
<literal> |
851 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.BODY</vodml-id> |
852 |
|
|
<name>BODY</name> |
853 |
|
|
<description> |
854 |
|
|
TODO : Missing description : please, update your UML model asap. |
855 |
|
|
</description> |
856 |
|
|
</literal> |
857 |
|
|
<literal> |
858 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GEO_C</vodml-id> |
859 |
|
|
<name>GEO_C</name> |
860 |
|
|
<description> |
861 |
|
|
TODO : Missing description : please, update your UML model asap. |
862 |
|
|
</description> |
863 |
|
|
</literal> |
864 |
|
|
<literal> |
865 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GEO_D</vodml-id> |
866 |
|
|
<name>GEO_D</name> |
867 |
|
|
<description> |
868 |
|
|
TODO : Missing description : please, update your UML model asap. |
869 |
|
|
</description> |
870 |
|
|
</literal> |
871 |
|
|
<literal> |
872 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.MAG</vodml-id> |
873 |
|
|
<name>MAG</name> |
874 |
|
|
<description> |
875 |
|
|
TODO : Missing description : please, update your UML model asap. |
876 |
|
|
</description> |
877 |
|
|
</literal> |
878 |
|
|
<literal> |
879 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GSE</vodml-id> |
880 |
|
|
<name>GSE</name> |
881 |
|
|
<description> |
882 |
|
|
TODO : Missing description : please, update your UML model asap. |
883 |
|
|
</description> |
884 |
|
|
</literal> |
885 |
|
|
<literal> |
886 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.GSM</vodml-id> |
887 |
|
|
<name>GSM</name> |
888 |
|
|
<description> |
889 |
|
|
TODO : Missing description : please, update your UML model asap. |
890 |
|
|
</description> |
891 |
|
|
</literal> |
892 |
|
|
<literal> |
893 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.SM</vodml-id> |
894 |
|
|
<name>SM</name> |
895 |
|
|
<description> |
896 |
|
|
TODO : Missing description : please, update your UML model asap. |
897 |
|
|
</description> |
898 |
|
|
</literal> |
899 |
|
|
<literal> |
900 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HGC</vodml-id> |
901 |
|
|
<name>HGC</name> |
902 |
|
|
<description> |
903 |
|
|
TODO : Missing description : please, update your UML model asap. |
904 |
|
|
</description> |
905 |
|
|
</literal> |
906 |
|
|
<literal> |
907 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HGS</vodml-id> |
908 |
|
|
<name>HGS</name> |
909 |
|
|
<description> |
910 |
|
|
TODO : Missing description : please, update your UML model asap. |
911 |
|
|
</description> |
912 |
|
|
</literal> |
913 |
|
|
<literal> |
914 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HEEQ</vodml-id> |
915 |
|
|
<name>HEEQ</name> |
916 |
|
|
<description> |
917 |
|
|
TODO : Missing description : please, update your UML model asap. |
918 |
|
|
</description> |
919 |
|
|
</literal> |
920 |
|
|
<literal> |
921 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HRTN</vodml-id> |
922 |
|
|
<name>HRTN</name> |
923 |
|
|
<description> |
924 |
|
|
TODO : Missing description : please, update your UML model asap. |
925 |
|
|
</description> |
926 |
|
|
</literal> |
927 |
|
|
<literal> |
928 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HPC</vodml-id> |
929 |
|
|
<name>HPC</name> |
930 |
|
|
<description> |
931 |
|
|
TODO : Missing description : please, update your UML model asap. |
932 |
|
|
</description> |
933 |
|
|
</literal> |
934 |
|
|
<literal> |
935 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HPR</vodml-id> |
936 |
|
|
<name>HPR</name> |
937 |
|
|
<description> |
938 |
|
|
TODO : Missing description : please, update your UML model asap. |
939 |
|
|
</description> |
940 |
|
|
</literal> |
941 |
|
|
<literal> |
942 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HCC</vodml-id> |
943 |
|
|
<name>HCC</name> |
944 |
|
|
<description> |
945 |
|
|
TODO : Missing description : please, update your UML model asap. |
946 |
|
|
</description> |
947 |
|
|
</literal> |
948 |
|
|
<literal> |
949 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.HGI</vodml-id> |
950 |
|
|
<name>HGI</name> |
951 |
|
|
<description> |
952 |
|
|
TODO : Missing description : please, update your UML model asap. |
953 |
|
|
</description> |
954 |
|
|
</literal> |
955 |
|
|
<literal> |
956 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.MERCURY_C</vodml-id> |
957 |
|
|
<name>MERCURY_C</name> |
958 |
|
|
<description> |
959 |
|
|
TODO : Missing description : please, update your UML model asap. |
960 |
|
|
</description> |
961 |
|
|
</literal> |
962 |
|
|
<literal> |
963 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.VENUS_C</vodml-id> |
964 |
|
|
<name>VENUS_C</name> |
965 |
|
|
<description> |
966 |
|
|
TODO : Missing description : please, update your UML model asap. |
967 |
|
|
</description> |
968 |
|
|
</literal> |
969 |
|
|
<literal> |
970 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.LUNA_C</vodml-id> |
971 |
|
|
<name>LUNA_C</name> |
972 |
|
|
<description> |
973 |
|
|
TODO : Missing description : please, update your UML model asap. |
974 |
|
|
</description> |
975 |
|
|
</literal> |
976 |
|
|
<literal> |
977 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.MARS_C</vodml-id> |
978 |
|
|
<name>MARS_C</name> |
979 |
|
|
<description> |
980 |
|
|
TODO : Missing description : please, update your UML model asap. |
981 |
|
|
</description> |
982 |
|
|
</literal> |
983 |
|
|
<literal> |
984 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.JUPITER_C_III</vodml-id> |
985 |
|
|
<name>JUPITER_C_III</name> |
986 |
|
|
<description> |
987 |
|
|
TODO : Missing description : please, update your UML model asap. |
988 |
|
|
</description> |
989 |
|
|
</literal> |
990 |
|
|
<literal> |
991 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.SATURN_C_III</vodml-id> |
992 |
|
|
<name>SATURN_C_III</name> |
993 |
|
|
<description> |
994 |
|
|
TODO : Missing description : please, update your UML model asap. |
995 |
|
|
</description> |
996 |
|
|
</literal> |
997 |
|
|
<literal> |
998 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.URANUS_C_III</vodml-id> |
999 |
|
|
<name>URANUS_C_III</name> |
1000 |
|
|
<description> |
1001 |
|
|
TODO : Missing description : please, update your UML model asap. |
1002 |
|
|
</description> |
1003 |
|
|
</literal> |
1004 |
|
|
<literal> |
1005 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.NEPTUNE_C_III</vodml-id> |
1006 |
|
|
<name>NEPTUNE_C_III</name> |
1007 |
|
|
<description> |
1008 |
|
|
TODO : Missing description : please, update your UML model asap. |
1009 |
|
|
</description> |
1010 |
|
|
</literal> |
1011 |
|
|
<literal> |
1012 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.PLUTO_C</vodml-id> |
1013 |
|
|
<name>PLUTO_C</name> |
1014 |
|
|
<description> |
1015 |
|
|
TODO : Missing description : please, update your UML model asap. |
1016 |
|
|
</description> |
1017 |
|
|
</literal> |
1018 |
|
|
<literal> |
1019 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.MERCURY_G</vodml-id> |
1020 |
|
|
<name>MERCURY_G</name> |
1021 |
|
|
<description> |
1022 |
|
|
TODO : Missing description : please, update your UML model asap. |
1023 |
|
|
</description> |
1024 |
|
|
</literal> |
1025 |
|
|
<literal> |
1026 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.VENUS_G</vodml-id> |
1027 |
|
|
<name>VENUS_G</name> |
1028 |
|
|
<description> |
1029 |
|
|
TODO : Missing description : please, update your UML model asap. |
1030 |
|
|
</description> |
1031 |
|
|
</literal> |
1032 |
|
|
<literal> |
1033 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.LUNA_G</vodml-id> |
1034 |
|
|
<name>LUNA_G</name> |
1035 |
|
|
<description> |
1036 |
|
|
TODO : Missing description : please, update your UML model asap. |
1037 |
|
|
</description> |
1038 |
|
|
</literal> |
1039 |
|
|
<literal> |
1040 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.MARS_G</vodml-id> |
1041 |
|
|
<name>MARS_G</name> |
1042 |
|
|
<description> |
1043 |
|
|
TODO : Missing description : please, update your UML model asap. |
1044 |
|
|
</description> |
1045 |
|
|
</literal> |
1046 |
|
|
<literal> |
1047 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.JUPITER_G_III</vodml-id> |
1048 |
|
|
<name>JUPITER_G_III</name> |
1049 |
|
|
<description> |
1050 |
|
|
TODO : Missing description : please, update your UML model asap. |
1051 |
|
|
</description> |
1052 |
|
|
</literal> |
1053 |
|
|
<literal> |
1054 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.SATURN_G_III</vodml-id> |
1055 |
|
|
<name>SATURN_G_III</name> |
1056 |
|
|
<description> |
1057 |
|
|
TODO : Missing description : please, update your UML model asap. |
1058 |
|
|
</description> |
1059 |
|
|
</literal> |
1060 |
|
|
<literal> |
1061 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.URANUS_G_III</vodml-id> |
1062 |
|
|
<name>URANUS_G_III</name> |
1063 |
|
|
<description> |
1064 |
|
|
TODO : Missing description : please, update your UML model asap. |
1065 |
|
|
</description> |
1066 |
|
|
</literal> |
1067 |
|
|
<literal> |
1068 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.NEPTUNE_G_III</vodml-id> |
1069 |
|
|
<name>NEPTUNE_G_III</name> |
1070 |
|
|
<description> |
1071 |
|
|
TODO : Missing description : please, update your UML model asap. |
1072 |
|
|
</description> |
1073 |
|
|
</literal> |
1074 |
|
|
<literal> |
1075 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.PLUTO_G</vodml-id> |
1076 |
|
|
<name>PLUTO_G</name> |
1077 |
|
|
<description> |
1078 |
|
|
TODO : Missing description : please, update your UML model asap. |
1079 |
|
|
</description> |
1080 |
|
|
</literal> |
1081 |
|
|
<literal> |
1082 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceStdRefFrame.UNKNOWNFrame</vodml-id> |
1083 |
|
|
<name>UNKNOWNFrame</name> |
1084 |
|
|
<description> |
1085 |
|
|
TODO : Missing description : please, update your UML model asap. |
1086 |
|
|
</description> |
1087 |
|
|
</literal> |
1088 |
|
|
</enumeration> |
1089 |
|
|
|
1090 |
|
|
<enumeration> |
1091 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos</vodml-id> |
1092 |
|
|
<name>StdRefPos</name> |
1093 |
|
|
<description>This is the enumerated list of allowed standard spatial and temporal reference positions.</description> |
1094 |
|
|
<literal> |
1095 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.GEOCENTER</vodml-id> |
1096 |
|
|
<name>GEOCENTER</name> |
1097 |
|
|
<description> |
1098 |
|
|
TODO : Missing description : please, update your UML model asap. |
1099 |
|
|
</description> |
1100 |
|
|
</literal> |
1101 |
|
|
<literal> |
1102 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.TOPOCENTER</vodml-id> |
1103 |
|
|
<name>TOPOCENTER</name> |
1104 |
|
|
<description> |
1105 |
|
|
TODO : Missing description : please, update your UML model asap. |
1106 |
|
|
</description> |
1107 |
|
|
</literal> |
1108 |
|
|
<literal> |
1109 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.BARYCENTER</vodml-id> |
1110 |
|
|
<name>BARYCENTER</name> |
1111 |
|
|
<description> |
1112 |
|
|
TODO : Missing description : please, update your UML model asap. |
1113 |
|
|
</description> |
1114 |
|
|
</literal> |
1115 |
|
|
<literal> |
1116 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.HELIOCENTER</vodml-id> |
1117 |
|
|
<name>HELIOCENTER</name> |
1118 |
|
|
<description> |
1119 |
|
|
TODO : Missing description : please, update your UML model asap. |
1120 |
|
|
</description> |
1121 |
|
|
</literal> |
1122 |
|
|
<literal> |
1123 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.GALACTIC_CENTER</vodml-id> |
1124 |
|
|
<name>GALACTIC_CENTER</name> |
1125 |
|
|
<description> |
1126 |
|
|
TODO : Missing description : please, update your UML model asap. |
1127 |
|
|
</description> |
1128 |
|
|
</literal> |
1129 |
|
|
<literal> |
1130 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.EMBARYCENTER</vodml-id> |
1131 |
|
|
<name>EMBARYCENTER</name> |
1132 |
|
|
<description> |
1133 |
|
|
TODO : Missing description : please, update your UML model asap. |
1134 |
|
|
</description> |
1135 |
|
|
</literal> |
1136 |
|
|
<literal> |
1137 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.MOON</vodml-id> |
1138 |
|
|
<name>MOON</name> |
1139 |
|
|
<description> |
1140 |
|
|
TODO : Missing description : please, update your UML model asap. |
1141 |
|
|
</description> |
1142 |
|
|
</literal> |
1143 |
|
|
<literal> |
1144 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.MERCURY</vodml-id> |
1145 |
|
|
<name>MERCURY</name> |
1146 |
|
|
<description> |
1147 |
|
|
TODO : Missing description : please, update your UML model asap. |
1148 |
|
|
</description> |
1149 |
|
|
</literal> |
1150 |
|
|
<literal> |
1151 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.VENUS</vodml-id> |
1152 |
|
|
<name>VENUS</name> |
1153 |
|
|
<description> |
1154 |
|
|
TODO : Missing description : please, update your UML model asap. |
1155 |
|
|
</description> |
1156 |
|
|
</literal> |
1157 |
|
|
<literal> |
1158 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.MARS</vodml-id> |
1159 |
|
|
<name>MARS</name> |
1160 |
|
|
<description> |
1161 |
|
|
TODO : Missing description : please, update your UML model asap. |
1162 |
|
|
</description> |
1163 |
|
|
</literal> |
1164 |
|
|
<literal> |
1165 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.JUPITER</vodml-id> |
1166 |
|
|
<name>JUPITER</name> |
1167 |
|
|
<description> |
1168 |
|
|
TODO : Missing description : please, update your UML model asap. |
1169 |
|
|
</description> |
1170 |
|
|
</literal> |
1171 |
|
|
<literal> |
1172 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.SATURN</vodml-id> |
1173 |
|
|
<name>SATURN</name> |
1174 |
|
|
<description> |
1175 |
|
|
TODO : Missing description : please, update your UML model asap. |
1176 |
|
|
</description> |
1177 |
|
|
</literal> |
1178 |
|
|
<literal> |
1179 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.URANUS</vodml-id> |
1180 |
|
|
<name>URANUS</name> |
1181 |
|
|
<description> |
1182 |
|
|
TODO : Missing description : please, update your UML model asap. |
1183 |
|
|
</description> |
1184 |
|
|
</literal> |
1185 |
|
|
<literal> |
1186 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.NEPTUNE</vodml-id> |
1187 |
|
|
<name>NEPTUNE</name> |
1188 |
|
|
<description> |
1189 |
|
|
TODO : Missing description : please, update your UML model asap. |
1190 |
|
|
</description> |
1191 |
|
|
</literal> |
1192 |
|
|
<literal> |
1193 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.PLUTO</vodml-id> |
1194 |
|
|
<name>PLUTO</name> |
1195 |
|
|
<description> |
1196 |
|
|
TODO : Missing description : please, update your UML model asap. |
1197 |
|
|
</description> |
1198 |
|
|
</literal> |
1199 |
|
|
<literal> |
1200 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.LSR</vodml-id> |
1201 |
|
|
<name>LSR</name> |
1202 |
|
|
<description> |
1203 |
|
|
TODO : Missing description : please, update your UML model asap. |
1204 |
|
|
</description> |
1205 |
|
|
</literal> |
1206 |
|
|
<literal> |
1207 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.LSRK</vodml-id> |
1208 |
|
|
<name>LSRK</name> |
1209 |
|
|
<description> |
1210 |
|
|
TODO : Missing description : please, update your UML model asap. |
1211 |
|
|
</description> |
1212 |
|
|
</literal> |
1213 |
|
|
<literal> |
1214 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.LSRD</vodml-id> |
1215 |
|
|
<name>LSRD</name> |
1216 |
|
|
<description> |
1217 |
|
|
TODO : Missing description : please, update your UML model asap. |
1218 |
|
|
</description> |
1219 |
|
|
</literal> |
1220 |
|
|
<literal> |
1221 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.LOCAL_GROUP_CENTER</vodml-id> |
1222 |
|
|
<name>LOCAL_GROUP_CENTER</name> |
1223 |
|
|
<description> |
1224 |
|
|
TODO : Missing description : please, update your UML model asap. |
1225 |
|
|
</description> |
1226 |
|
|
</literal> |
1227 |
|
|
<literal> |
1228 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.RELOCATABLE</vodml-id> |
1229 |
|
|
<name>RELOCATABLE</name> |
1230 |
|
|
<description> |
1231 |
|
|
TODO : Missing description : please, update your UML model asap. |
1232 |
|
|
</description> |
1233 |
|
|
</literal> |
1234 |
|
|
<literal> |
1235 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdRefPos.UNKNOWNRefPos</vodml-id> |
1236 |
|
|
<name>UNKNOWNRefPos</name> |
1237 |
|
|
<description> |
1238 |
|
|
TODO : Missing description : please, update your UML model asap. |
1239 |
|
|
</description> |
1240 |
|
|
</literal> |
1241 |
|
|
</enumeration> |
1242 |
|
|
|
1243 |
|
|
<enumeration> |
1244 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.EpochType</vodml-id> |
1245 |
|
|
<name>EpochType</name> |
1246 |
|
|
<description>Epoch type: Julian or Besselian.</description> |
1247 |
|
|
<literal> |
1248 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.EpochType.J</vodml-id> |
1249 |
|
|
<name>J</name> |
1250 |
|
|
<description> |
1251 |
|
|
TODO : Missing description : please, update your UML model asap. |
1252 |
|
|
</description> |
1253 |
|
|
</literal> |
1254 |
|
|
<literal> |
1255 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.EpochType.B</vodml-id> |
1256 |
|
|
<name>B</name> |
1257 |
|
|
<description> |
1258 |
|
|
TODO : Missing description : please, update your UML model asap. |
1259 |
|
|
</description> |
1260 |
|
|
</literal> |
1261 |
|
|
</enumeration> |
1262 |
|
|
|
1263 |
|
|
<dataType abstract="true"> |
1264 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Location</vodml-id> |
1265 |
|
|
<name>Location</name> |
1266 |
|
|
<description>The abstract data type that specifies a specific spatial location. It may either be a StdLocation (which absolute location in phase space is known by definition, if necessary aided by a planetary ephemeris) or a Custom Spatial Location (which provides coordinates in an associated SpaceFrame). Although this data type may be used anywhere, it is especially designed for us as a Reference Position in the AstroCoordSystem object.</description> |
1267 |
|
|
</dataType> |
1268 |
|
|
|
1269 |
|
|
<dataType> |
1270 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdLocation</vodml-id> |
1271 |
|
|
<name>StdLocation</name> |
1272 |
|
|
<description>Derived from data type Location. An absolute a priori known location in phase space (position and velocity), chosen from the StdRefPos enumeration. Considering that the GEOCENTER is really the only place for which we know the absolute location at all times, all other locations require the specification of a planetary ephemeris, although that may be defaulted to DE405. LSR[KD] are reserved for spectrall and redshift frames. TOPOCENTER (location of the observer) is special in that it assumes that the observing location is available through other means (e.g., a geographic location or an orbit ephemeris). RELOCATABLE is availlable for simulations. UNKNOWNRefPos should only be used if absolutely necessary.</description> |
1273 |
|
|
<extends> |
1274 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Location</vodml-ref> |
1275 |
|
|
</extends> |
1276 |
|
|
<attribute> |
1277 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.StdLocation.location</vodml-id> |
1278 |
|
|
<name>location</name> |
1279 |
|
|
<description> |
1280 |
|
|
TODO : Missing description : please, update your UML model asap. |
1281 |
|
|
</description> |
1282 |
|
|
<datatype> |
1283 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.StdRefPos</vodml-ref> |
1284 |
|
|
</datatype> |
1285 |
|
|
<multiplicity> |
1286 |
|
|
<minOccurs>1</minOccurs> |
1287 |
|
|
<maxOccurs>1</maxOccurs> |
1288 |
|
|
</multiplicity> |
1289 |
|
|
</attribute> |
1290 |
|
|
</dataType> |
1291 |
|
|
|
1292 |
|
|
<dataType> |
1293 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.CustomLocation</vodml-id> |
1294 |
|
|
<name>CustomLocation</name> |
1295 |
|
|
<description>Derived from data type Location. This is the abstract data type (to be instantiated as a set of 1D, 2D, or 3D cpatial coordinates specifying the position and/or velocity. This abstract data type contains a reference to an instance of a SpatialFrame and, optionally, an Epoch.</description> |
1296 |
|
|
<extends> |
1297 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Location</vodml-ref> |
1298 |
|
|
</extends> |
1299 |
|
|
<attribute> |
1300 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.CustomLocation.epoch</vodml-id> |
1301 |
|
|
<name>epoch</name> |
1302 |
|
|
<description> |
1303 |
|
|
TODO : Missing description : please, update your UML model asap. |
1304 |
|
|
</description> |
1305 |
|
|
<datatype> |
1306 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Epoch</vodml-ref> |
1307 |
|
|
</datatype> |
1308 |
|
|
<multiplicity> |
1309 |
|
|
<minOccurs>0</minOccurs> |
1310 |
|
|
<maxOccurs>1</maxOccurs> |
1311 |
|
|
</multiplicity> |
1312 |
|
|
</attribute> |
1313 |
|
|
<attribute> |
1314 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.CustomLocation.position</vodml-id> |
1315 |
|
|
<name>position</name> |
1316 |
|
|
<description> |
1317 |
|
|
TODO : Missing description : please, update your UML model asap. |
1318 |
|
|
</description> |
1319 |
|
|
<datatype> |
1320 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialValue</vodml-ref> |
1321 |
|
|
</datatype> |
1322 |
|
|
<multiplicity> |
1323 |
|
|
<minOccurs>1</minOccurs> |
1324 |
|
|
<maxOccurs>1</maxOccurs> |
1325 |
|
|
</multiplicity> |
1326 |
|
|
</attribute> |
1327 |
|
|
<attribute> |
1328 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.CustomLocation.velocity</vodml-id> |
1329 |
|
|
<name>velocity</name> |
1330 |
|
|
<description> |
1331 |
|
|
TODO : Missing description : please, update your UML model asap. |
1332 |
|
|
</description> |
1333 |
|
|
<datatype> |
1334 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialValue</vodml-ref> |
1335 |
|
|
</datatype> |
1336 |
|
|
<multiplicity> |
1337 |
|
|
<minOccurs>0</minOccurs> |
1338 |
|
|
<maxOccurs>1</maxOccurs> |
1339 |
|
|
</multiplicity> |
1340 |
|
|
</attribute> |
1341 |
|
|
</dataType> |
1342 |
|
|
|
1343 |
|
|
<dataType> |
1344 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Epoch</vodml-id> |
1345 |
|
|
<name>Epoch</name> |
1346 |
|
|
<description>Epoch data type, containing EpochType (default: J) and epoch expressed in years.</description> |
1347 |
|
|
<attribute> |
1348 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Epoch.type</vodml-id> |
1349 |
|
|
<name>type</name> |
1350 |
|
|
<description> |
1351 |
|
|
TODO : Missing description : please, update your UML model asap. |
1352 |
|
|
</description> |
1353 |
|
|
<datatype> |
1354 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.EpochType</vodml-ref> |
1355 |
|
|
</datatype> |
1356 |
|
|
<multiplicity> |
1357 |
|
|
<minOccurs>0</minOccurs> |
1358 |
|
|
<maxOccurs>1</maxOccurs> |
1359 |
|
|
</multiplicity> |
1360 |
|
|
</attribute> |
1361 |
|
|
<attribute> |
1362 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Epoch.year</vodml-id> |
1363 |
|
|
<name>year</name> |
1364 |
|
|
<description> |
1365 |
|
|
TODO : Missing description : please, update your UML model asap. |
1366 |
|
|
</description> |
1367 |
|
|
<datatype> |
1368 |
|
|
<vodml-ref>ivoa:real</vodml-ref> |
1369 |
|
|
</datatype> |
1370 |
|
|
<multiplicity> |
1371 |
|
|
<minOccurs>1</minOccurs> |
1372 |
|
|
<maxOccurs>1</maxOccurs> |
1373 |
|
|
</multiplicity> |
1374 |
|
|
</attribute> |
1375 |
|
|
</dataType> |
1376 |
|
|
|
1377 |
|
|
<dataType abstract="true"> |
1378 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialValue</vodml-id> |
1379 |
|
|
<name>SpatialValue</name> |
1380 |
|
|
<description>The abstract data type SpatialValue contains a reference to a SpatialFrame through the coordinate axis and Spatial Space and allows the 1-, 2-, and 3-dimensional coordinate values to be specified as derived data types. It MAY include an epoch. The spatial coordinate value is built from SpatialCoordValue scalar components. Note that SpatialValue may contain either positions or velocities. The latter are restricted to true space velocities; Doppler velocities belong in the redshift domain.</description> |
1381 |
|
|
<extends> |
1382 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue</vodml-ref> |
1383 |
|
|
</extends> |
1384 |
|
|
<attribute> |
1385 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialValue.epoch</vodml-id> |
1386 |
|
|
<name>epoch</name> |
1387 |
|
|
<description> |
1388 |
|
|
TODO : Missing description : please, update your UML model asap. |
1389 |
|
|
</description> |
1390 |
|
|
<datatype> |
1391 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Epoch</vodml-ref> |
1392 |
|
|
</datatype> |
1393 |
|
|
<multiplicity> |
1394 |
|
|
<minOccurs>0</minOccurs> |
1395 |
|
|
<maxOccurs>1</maxOccurs> |
1396 |
|
|
</multiplicity> |
1397 |
|
|
</attribute> |
1398 |
|
|
</dataType> |
1399 |
|
|
|
1400 |
|
|
<dataType> |
1401 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialValue1D</vodml-id> |
1402 |
|
|
<name>SpatialValue1D</name> |
1403 |
|
|
<description>1-dimensional spatial coordinate value.</description> |
1404 |
|
|
<extends> |
1405 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialValue</vodml-ref> |
1406 |
|
|
</extends> |
1407 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1408 |
|
|
<role> |
1409 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
1410 |
|
|
</role> |
1411 |
|
|
<datatype> |
1412 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialCoordValue</vodml-ref> |
1413 |
|
|
</datatype> |
1414 |
|
|
</constraint> |
1415 |
|
|
</dataType> |
1416 |
|
|
|
1417 |
|
|
<dataType> |
1418 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialValue2D</vodml-id> |
1419 |
|
|
<name>SpatialValue2D</name> |
1420 |
|
|
<description>2-dimensional spatial coordinate value. Each component references its own axis.</description> |
1421 |
|
|
<extends> |
1422 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialValue</vodml-ref> |
1423 |
|
|
</extends> |
1424 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1425 |
|
|
<role> |
1426 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
1427 |
|
|
</role> |
1428 |
|
|
<datatype> |
1429 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialCoordValue</vodml-ref> |
1430 |
|
|
</datatype> |
1431 |
|
|
</constraint> |
1432 |
|
|
</dataType> |
1433 |
|
|
|
1434 |
|
|
<dataType> |
1435 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialValue3D</vodml-id> |
1436 |
|
|
<name>SpatialValue3D</name> |
1437 |
|
|
<description>3-dimensional spatial coordinate value. Each component references its own axis.</description> |
1438 |
|
|
<extends> |
1439 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialValue</vodml-ref> |
1440 |
|
|
</extends> |
1441 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1442 |
|
|
<role> |
1443 |
|
|
<vodml-ref>stc2_coordinates:coords.MultiCoordValue.cmpt</vodml-ref> |
1444 |
|
|
</role> |
1445 |
|
|
<datatype> |
1446 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialCoordValue</vodml-ref> |
1447 |
|
|
</datatype> |
1448 |
|
|
</constraint> |
1449 |
|
|
</dataType> |
1450 |
|
|
|
1451 |
|
|
<dataType> |
1452 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialCoordValue</vodml-id> |
1453 |
|
|
<name>SpatialCoordValue</name> |
1454 |
|
|
<description>Single-axis spatial coordinate value, to be used as component in the general SpatialValue data type.</description> |
1455 |
|
|
<extends> |
1456 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue</vodml-ref> |
1457 |
|
|
</extends> |
1458 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1459 |
|
|
<role> |
1460 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
1461 |
|
|
</role> |
1462 |
|
|
<datatype> |
1463 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
1464 |
|
|
</datatype> |
1465 |
|
|
</constraint> |
1466 |
|
|
</dataType> |
1467 |
|
|
|
1468 |
|
|
<objectType> |
1469 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceFrame</vodml-id> |
1470 |
|
|
<name>SpaceFrame</name> |
1471 |
|
|
<description>A Spatial Frame is specified by its Reference Frame (currently only standard reference frames are allowed), a Reference Position (provided in the associated AstroCoordSystem object), and a SpatialSpace object; an Equinox is optional and only required for pre-ICRS reference frames; an epoh is also optional. It is to be referenced by spatial coordinates (Position and Velocity). </description> |
1472 |
|
|
<extends> |
1473 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
1474 |
|
|
</extends> |
1475 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1476 |
|
|
<role> |
1477 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
1478 |
|
|
</role> |
1479 |
|
|
<datatype> |
1480 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialSpace</vodml-ref> |
1481 |
|
|
</datatype> |
1482 |
|
|
</constraint> |
1483 |
|
|
<attribute> |
1484 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceFrame.spaceRefFrame</vodml-id> |
1485 |
|
|
<name>spaceRefFrame</name> |
1486 |
|
|
<description> |
1487 |
|
|
TODO : Missing description : please, update your UML model asap. |
1488 |
|
|
</description> |
1489 |
|
|
<datatype> |
1490 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpaceStdRefFrame</vodml-ref> |
1491 |
|
|
</datatype> |
1492 |
|
|
<multiplicity> |
1493 |
|
|
<minOccurs>1</minOccurs> |
1494 |
|
|
<maxOccurs>1</maxOccurs> |
1495 |
|
|
</multiplicity> |
1496 |
|
|
</attribute> |
1497 |
|
|
<attribute> |
1498 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceFrame.equinox</vodml-id> |
1499 |
|
|
<name>equinox</name> |
1500 |
|
|
<description> |
1501 |
|
|
TODO : Missing description : please, update your UML model asap. |
1502 |
|
|
</description> |
1503 |
|
|
<datatype> |
1504 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Epoch</vodml-ref> |
1505 |
|
|
</datatype> |
1506 |
|
|
<multiplicity> |
1507 |
|
|
<minOccurs>0</minOccurs> |
1508 |
|
|
<maxOccurs>1</maxOccurs> |
1509 |
|
|
</multiplicity> |
1510 |
|
|
</attribute> |
1511 |
|
|
<attribute> |
1512 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpaceFrame.epoch</vodml-id> |
1513 |
|
|
<name>epoch</name> |
1514 |
|
|
<description> |
1515 |
|
|
TODO : Missing description : please, update your UML model asap. |
1516 |
|
|
</description> |
1517 |
|
|
<datatype> |
1518 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Epoch</vodml-ref> |
1519 |
|
|
</datatype> |
1520 |
|
|
<multiplicity> |
1521 |
|
|
<minOccurs>0</minOccurs> |
1522 |
|
|
<maxOccurs>1</maxOccurs> |
1523 |
|
|
</multiplicity> |
1524 |
|
|
</attribute> |
1525 |
|
|
</objectType> |
1526 |
|
|
|
1527 |
|
|
<objectType abstract="true"> |
1528 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.SpatialSpace</vodml-id> |
1529 |
|
|
<name>SpatialSpace</name> |
1530 |
|
|
<description>The abstract SpatialSpace is derived from CoordSpace and SHALL contain one, two, or three coordinate axes whose attributes may all be relevant. Different flavors may be derived from this class: Spherical, Cartesian, Cylindrical, Polar, UnitSphere, HTM, HealPix. At this time only Spherical and Cartesian are provided.</description> |
1531 |
|
|
<extends> |
1532 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
1533 |
|
|
</extends> |
1534 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1535 |
|
|
<role> |
1536 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
1537 |
|
|
</role> |
1538 |
|
|
<datatype> |
1539 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
1540 |
|
|
</datatype> |
1541 |
|
|
</constraint> |
1542 |
|
|
</objectType> |
1543 |
|
|
|
1544 |
|
|
<objectType> |
1545 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Spherical</vodml-id> |
1546 |
|
|
<name>Spherical</name> |
1547 |
|
|
<description>To be used for Spherical spatiall coordinates. The native order is: longitude, latitude, radius.</description> |
1548 |
|
|
<extends> |
1549 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialSpace</vodml-ref> |
1550 |
|
|
</extends> |
1551 |
|
|
</objectType> |
1552 |
|
|
|
1553 |
|
|
<objectType> |
1554 |
|
|
<vodml-id>CoordinateDomains.spatialDomain.Cartesian</vodml-id> |
1555 |
|
|
<name>Cartesian</name> |
1556 |
|
|
<description>To be used for Cartesian spatial coordinates, 1-, 2-, or 3-dimensional. The native order is X, Y, Z; right-handed.</description> |
1557 |
|
|
<extends> |
1558 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpatialSpace</vodml-ref> |
1559 |
|
|
</extends> |
1560 |
|
|
</objectType> |
1561 |
|
|
|
1562 |
|
|
</package> |
1563 |
|
|
|
1564 |
|
|
|
1565 |
|
|
|
1566 |
|
|
<package> |
1567 |
|
|
<vodml-id>CoordinateDomains.spectralDomain</vodml-id> |
1568 |
|
|
<name>spectralDomain</name> |
1569 |
|
|
<description> |
1570 |
|
|
TODO : Missing description : please, update your UML model asap. |
1571 |
|
|
</description> |
1572 |
|
|
<dataType abstract="true"> |
1573 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.SpectralValue</vodml-id> |
1574 |
|
|
<name>SpectralValue</name> |
1575 |
|
|
<description>The abstract data type SpectralValue contains a reference to a SpectralFrame through the coordinate axis and Spectral Space and allows the equivalent data types Frequency, Energy, and Wavelength coordinate values to be specified as derived data types.</description> |
1576 |
|
|
<extends> |
1577 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue</vodml-ref> |
1578 |
|
|
</extends> |
1579 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1580 |
|
|
<role> |
1581 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
1582 |
|
|
</role> |
1583 |
|
|
<datatype> |
1584 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
1585 |
|
|
</datatype> |
1586 |
|
|
</constraint> |
1587 |
|
|
</dataType> |
1588 |
|
|
|
1589 |
|
|
<dataType> |
1590 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.Frequency</vodml-id> |
1591 |
|
|
<name>Frequency</name> |
1592 |
|
|
<description>Spectral coordinate value expressed as a frequency.</description> |
1593 |
|
|
<extends> |
1594 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spectralDomain.SpectralValue</vodml-ref> |
1595 |
|
|
</extends> |
1596 |
|
|
</dataType> |
1597 |
|
|
|
1598 |
|
|
<dataType> |
1599 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.Energy</vodml-id> |
1600 |
|
|
<name>Energy</name> |
1601 |
|
|
<description>Spectral coordinate value expressed as an energy.</description> |
1602 |
|
|
<extends> |
1603 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spectralDomain.SpectralValue</vodml-ref> |
1604 |
|
|
</extends> |
1605 |
|
|
</dataType> |
1606 |
|
|
|
1607 |
|
|
<dataType> |
1608 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.Wavelength</vodml-id> |
1609 |
|
|
<name>Wavelength</name> |
1610 |
|
|
<description>Spectral coordinate value expressed as a wavelength. Note that a refractive index is required for proper interpretation of wavelength; if absent, a value of 0.0 (vacuum) will be assumed.</description> |
1611 |
|
|
<extends> |
1612 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spectralDomain.SpectralValue</vodml-ref> |
1613 |
|
|
</extends> |
1614 |
|
|
<attribute> |
1615 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.Wavelength.refrindex</vodml-id> |
1616 |
|
|
<name>refrindex</name> |
1617 |
|
|
<description>Refractive index of the medium in which the wavelength is measured; default=0.0.</description> |
1618 |
|
|
<datatype> |
1619 |
|
|
<vodml-ref>ivoa:real</vodml-ref> |
1620 |
|
|
</datatype> |
1621 |
|
|
<multiplicity> |
1622 |
|
|
<minOccurs>0</minOccurs> |
1623 |
|
|
<maxOccurs>1</maxOccurs> |
1624 |
|
|
</multiplicity> |
1625 |
|
|
</attribute> |
1626 |
|
|
</dataType> |
1627 |
|
|
|
1628 |
|
|
<objectType> |
1629 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.SpectralFrame</vodml-id> |
1630 |
|
|
<name>SpectralFrame</name> |
1631 |
|
|
<description>The SpectralFrame is the Frame for spectral coordinates. It requires a Reference Position (in the AstroCoordSystem and which need to be specified in phase space) and SHALL contain a Spectral Space object.</description> |
1632 |
|
|
<extends> |
1633 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
1634 |
|
|
</extends> |
1635 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1636 |
|
|
<role> |
1637 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
1638 |
|
|
</role> |
1639 |
|
|
<datatype> |
1640 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spectralDomain.SpectralSpace</vodml-ref> |
1641 |
|
|
</datatype> |
1642 |
|
|
</constraint> |
1643 |
|
|
</objectType> |
1644 |
|
|
|
1645 |
|
|
<objectType> |
1646 |
|
|
<vodml-id>CoordinateDomains.spectralDomain.SpectralSpace</vodml-id> |
1647 |
|
|
<name>SpectralSpace</name> |
1648 |
|
|
<description>The SpectralSpace SHALL include one CoordAxis object, which will typically not include any of its optional attributes other than Name, although domainMin could trivially be set to zero, of course.</description> |
1649 |
|
|
<extends> |
1650 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
1651 |
|
|
</extends> |
1652 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1653 |
|
|
<role> |
1654 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
1655 |
|
|
</role> |
1656 |
|
|
<datatype> |
1657 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
1658 |
|
|
</datatype> |
1659 |
|
|
</constraint> |
1660 |
|
|
</objectType> |
1661 |
|
|
|
1662 |
|
|
</package> |
1663 |
|
|
|
1664 |
|
|
|
1665 |
|
|
|
1666 |
|
|
<package> |
1667 |
|
|
<vodml-id>CoordinateDomains.timeDomain</vodml-id> |
1668 |
|
|
<name>timeDomain</name> |
1669 |
|
|
<description> |
1670 |
|
|
TODO : Missing description : please, update your UML model asap. |
1671 |
|
|
</description> |
1672 |
|
|
<enumeration> |
1673 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale</vodml-id> |
1674 |
|
|
<name>TimeScale</name> |
1675 |
|
|
<description>The enumerated list of recognized Time Scales</description> |
1676 |
|
|
<literal> |
1677 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TT</vodml-id> |
1678 |
|
|
<name>TT</name> |
1679 |
|
|
<description> |
1680 |
|
|
TODO : Missing description : please, update your UML model asap. |
1681 |
|
|
</description> |
1682 |
|
|
</literal> |
1683 |
|
|
<literal> |
1684 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TDT</vodml-id> |
1685 |
|
|
<name>TDT</name> |
1686 |
|
|
<description> |
1687 |
|
|
TODO : Missing description : please, update your UML model asap. |
1688 |
|
|
</description> |
1689 |
|
|
</literal> |
1690 |
|
|
<literal> |
1691 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.ET</vodml-id> |
1692 |
|
|
<name>ET</name> |
1693 |
|
|
<description> |
1694 |
|
|
TODO : Missing description : please, update your UML model asap. |
1695 |
|
|
</description> |
1696 |
|
|
</literal> |
1697 |
|
|
<literal> |
1698 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TAI</vodml-id> |
1699 |
|
|
<name>TAI</name> |
1700 |
|
|
<description> |
1701 |
|
|
TODO : Missing description : please, update your UML model asap. |
1702 |
|
|
</description> |
1703 |
|
|
</literal> |
1704 |
|
|
<literal> |
1705 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.IAT</vodml-id> |
1706 |
|
|
<name>IAT</name> |
1707 |
|
|
<description> |
1708 |
|
|
TODO : Missing description : please, update your UML model asap. |
1709 |
|
|
</description> |
1710 |
|
|
</literal> |
1711 |
|
|
<literal> |
1712 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.UTC</vodml-id> |
1713 |
|
|
<name>UTC</name> |
1714 |
|
|
<description> |
1715 |
|
|
TODO : Missing description : please, update your UML model asap. |
1716 |
|
|
</description> |
1717 |
|
|
</literal> |
1718 |
|
|
<literal> |
1719 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.GPS</vodml-id> |
1720 |
|
|
<name>GPS</name> |
1721 |
|
|
<description> |
1722 |
|
|
TODO : Missing description : please, update your UML model asap. |
1723 |
|
|
</description> |
1724 |
|
|
</literal> |
1725 |
|
|
<literal> |
1726 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TDB</vodml-id> |
1727 |
|
|
<name>TDB</name> |
1728 |
|
|
<description> |
1729 |
|
|
TODO : Missing description : please, update your UML model asap. |
1730 |
|
|
</description> |
1731 |
|
|
</literal> |
1732 |
|
|
<literal> |
1733 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TEB</vodml-id> |
1734 |
|
|
<name>TEB</name> |
1735 |
|
|
<description> |
1736 |
|
|
TODO : Missing description : please, update your UML model asap. |
1737 |
|
|
</description> |
1738 |
|
|
</literal> |
1739 |
|
|
<literal> |
1740 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TCG</vodml-id> |
1741 |
|
|
<name>TCG</name> |
1742 |
|
|
<description> |
1743 |
|
|
TODO : Missing description : please, update your UML model asap. |
1744 |
|
|
</description> |
1745 |
|
|
</literal> |
1746 |
|
|
<literal> |
1747 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.TCB</vodml-id> |
1748 |
|
|
<name>TCB</name> |
1749 |
|
|
<description> |
1750 |
|
|
TODO : Missing description : please, update your UML model asap. |
1751 |
|
|
</description> |
1752 |
|
|
</literal> |
1753 |
|
|
<literal> |
1754 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.LST</vodml-id> |
1755 |
|
|
<name>LST</name> |
1756 |
|
|
<description> |
1757 |
|
|
TODO : Missing description : please, update your UML model asap. |
1758 |
|
|
</description> |
1759 |
|
|
</literal> |
1760 |
|
|
<literal> |
1761 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeScale.LOCAL</vodml-id> |
1762 |
|
|
<name>LOCAL</name> |
1763 |
|
|
<description> |
1764 |
|
|
TODO : Missing description : please, update your UML model asap. |
1765 |
|
|
</description> |
1766 |
|
|
</literal> |
1767 |
|
|
</enumeration> |
1768 |
|
|
|
1769 |
|
|
<dataType> |
1770 |
|
|
<vodml-id>CoordinateDomains.timeDomain.ISOtime</vodml-id> |
1771 |
|
|
<name>ISOtime</name> |
1772 |
|
|
<description>ISOtime is a Time Stamp expressed as an ISO-8601 string, within the restrictions imposed by the IVOA: no time zone information is allowed, the string needs to be of the form [+|-c]ccyy-mm-dd[Thh:mm:ss[.s...]]</description> |
1773 |
|
|
<extends> |
1774 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeStamp</vodml-ref> |
1775 |
|
|
</extends> |
1776 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1777 |
|
|
<role> |
1778 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
1779 |
|
|
</role> |
1780 |
|
|
<datatype> |
1781 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.DatetimeQuantity</vodml-ref> |
1782 |
|
|
</datatype> |
1783 |
|
|
</constraint> |
1784 |
|
|
</dataType> |
1785 |
|
|
|
1786 |
|
|
<dataType> |
1787 |
|
|
<vodml-id>CoordinateDomains.timeDomain.JD</vodml-id> |
1788 |
|
|
<name>JD</name> |
1789 |
|
|
<description>JD is a Time Stamp expressed in Julian Days. Note that JD does not properly specify a time stamp, unless it is related to a time scale and a reference position. One shoulld be aware that precision can easily become an issue with JD, as the numbers tend to be large.</description> |
1790 |
|
|
<extends> |
1791 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.JDTime</vodml-ref> |
1792 |
|
|
</extends> |
1793 |
|
|
</dataType> |
1794 |
|
|
|
1795 |
|
|
<dataType> |
1796 |
|
|
<vodml-id>CoordinateDomains.timeDomain.MJD</vodml-id> |
1797 |
|
|
<name>MJD</name> |
1798 |
|
|
<description>MJD is a Time Stamp expressed in Modified Julian Days. T(MJD)=T(JD)-2440000.5.</description> |
1799 |
|
|
<extends> |
1800 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.JDTime</vodml-ref> |
1801 |
|
|
</extends> |
1802 |
|
|
</dataType> |
1803 |
|
|
|
1804 |
|
|
<dataType> |
1805 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeOffset</vodml-id> |
1806 |
|
|
<name>TimeOffset</name> |
1807 |
|
|
<description>TimeOffset specifies the offset in time of the Time Stamp relative to the Time Origin in the associated Time Frame</description> |
1808 |
|
|
<extends> |
1809 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeStamp</vodml-ref> |
1810 |
|
|
</extends> |
1811 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1812 |
|
|
<role> |
1813 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
1814 |
|
|
</role> |
1815 |
|
|
<datatype> |
1816 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
1817 |
|
|
</datatype> |
1818 |
|
|
</constraint> |
1819 |
|
|
</dataType> |
1820 |
|
|
|
1821 |
|
|
<dataType abstract="true"> |
1822 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeStamp</vodml-id> |
1823 |
|
|
<name>TimeStamp</name> |
1824 |
|
|
<description>A TimeStamp specifies a specific time instance and may be expressed as JD, MJD, ISO-8601, or an offset from a specific point in time (which has to be a Time Stamp). The contents of the Time Stamp references an instance of a time axis.</description> |
1825 |
|
|
<extends> |
1826 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue</vodml-ref> |
1827 |
|
|
</extends> |
1828 |
|
|
</dataType> |
1829 |
|
|
|
1830 |
|
|
<dataType abstract="true"> |
1831 |
|
|
<vodml-id>CoordinateDomains.timeDomain.JDTime</vodml-id> |
1832 |
|
|
<name>JDTime</name> |
1833 |
|
|
<description>Basic astronomical time is specified as Julian Dates (or Modified Julian Dates). The numbers are unitlless, although the implied unit is, of course, 'd'.</description> |
1834 |
|
|
<extends> |
1835 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeStamp</vodml-ref> |
1836 |
|
|
</extends> |
1837 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1838 |
|
|
<role> |
1839 |
|
|
<vodml-ref>stc2_coordinates:coords.PhysicalCoordValue.cval</vodml-ref> |
1840 |
|
|
</role> |
1841 |
|
|
<datatype> |
1842 |
|
|
<vodml-ref>ivoa:RealQuantity</vodml-ref> |
1843 |
|
|
</datatype> |
1844 |
|
|
</constraint> |
1845 |
|
|
</dataType> |
1846 |
|
|
|
1847 |
|
|
<dataType> |
1848 |
|
|
<vodml-id>CoordinateDomains.timeDomain.DatetimeQuantity</vodml-id> |
1849 |
|
|
<name>DatetimeQuantity</name> |
1850 |
|
|
<description> |
1851 |
|
|
TODO : Missing description : please, update your UML model asap. |
1852 |
|
|
</description> |
1853 |
|
|
<extends> |
1854 |
|
|
<vodml-ref>ivoa:Quantity</vodml-ref> |
1855 |
|
|
</extends> |
1856 |
|
|
<attribute> |
1857 |
|
|
<vodml-id>CoordinateDomains.timeDomain.DatetimeQuantity.value</vodml-id> |
1858 |
|
|
<name>value</name> |
1859 |
|
|
<description> |
1860 |
|
|
TODO : Missing description : please, update your UML model asap. |
1861 |
|
|
</description> |
1862 |
|
|
<datatype> |
1863 |
|
|
<vodml-ref>ivoa:datetime</vodml-ref> |
1864 |
|
|
</datatype> |
1865 |
|
|
<multiplicity> |
1866 |
|
|
<minOccurs>1</minOccurs> |
1867 |
|
|
<maxOccurs>1</maxOccurs> |
1868 |
|
|
</multiplicity> |
1869 |
|
|
</attribute> |
1870 |
|
|
</dataType> |
1871 |
|
|
|
1872 |
|
|
<objectType> |
1873 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeFrame</vodml-id> |
1874 |
|
|
<name>TimeFrame</name> |
1875 |
|
|
<description>A TimeFrame SHALL include a Time Scale and a TimeSpace and MAY include a Reference Direction, and/or a Time Origin (for elapsed time).</description> |
1876 |
|
|
<extends> |
1877 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame</vodml-ref> |
1878 |
|
|
</extends> |
1879 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1880 |
|
|
<role> |
1881 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordFrame.coordSpace</vodml-ref> |
1882 |
|
|
</role> |
1883 |
|
|
<datatype> |
1884 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeSpace</vodml-ref> |
1885 |
|
|
</datatype> |
1886 |
|
|
</constraint> |
1887 |
|
|
<attribute> |
1888 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeFrame.timeScale</vodml-id> |
1889 |
|
|
<name>timeScale</name> |
1890 |
|
|
<description>The Time Scale sets the reference frame for the Time Frame.</description> |
1891 |
|
|
<datatype> |
1892 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeScale</vodml-ref> |
1893 |
|
|
</datatype> |
1894 |
|
|
<multiplicity> |
1895 |
|
|
<minOccurs>1</minOccurs> |
1896 |
|
|
<maxOccurs>1</maxOccurs> |
1897 |
|
|
</multiplicity> |
1898 |
|
|
</attribute> |
1899 |
|
|
<attribute> |
1900 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeFrame.refDirection</vodml-id> |
1901 |
|
|
<name>refDirection</name> |
1902 |
|
|
<description>The reference direction is needed if time stampes are transformed to a time frame with a different reference position (contained in the (Astro)CoordSystem). In those situations the solar system ephemeris also comes into play.</description> |
1903 |
|
|
<datatype> |
1904 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Location</vodml-ref> |
1905 |
|
|
</datatype> |
1906 |
|
|
<multiplicity> |
1907 |
|
|
<minOccurs>0</minOccurs> |
1908 |
|
|
<maxOccurs>1</maxOccurs> |
1909 |
|
|
</multiplicity> |
1910 |
|
|
</attribute> |
1911 |
|
|
<attribute> |
1912 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeFrame.timeOrigin</vodml-id> |
1913 |
|
|
<name>timeOrigin</name> |
1914 |
|
|
<description>The Time Origin needs to refer to the same TimeAxis as the TimeOffsets that refer to this TimeFrame. This may seem like a recursive anomaly, but is necessary in order to prevent accidents.</description> |
1915 |
|
|
<datatype> |
1916 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeStamp</vodml-ref> |
1917 |
|
|
</datatype> |
1918 |
|
|
<multiplicity> |
1919 |
|
|
<minOccurs>0</minOccurs> |
1920 |
|
|
<maxOccurs>1</maxOccurs> |
1921 |
|
|
</multiplicity> |
1922 |
|
|
</attribute> |
1923 |
|
|
</objectType> |
1924 |
|
|
|
1925 |
|
|
<objectType> |
1926 |
|
|
<vodml-id>CoordinateDomains.timeDomain.TimeSpace</vodml-id> |
1927 |
|
|
<name>TimeSpace</name> |
1928 |
|
|
<description>The TimeSpace SHALL include one CoordAxis object, which will typically not include any of its optional attributes orther than Name, although this will be left open in case it is deemed desirable to allow derived time axes such as phase to be specified.</description> |
1929 |
|
|
<extends> |
1930 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
1931 |
|
|
</extends> |
1932 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
1933 |
|
|
<role> |
1934 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace.coordAxis</vodml-ref> |
1935 |
|
|
</role> |
1936 |
|
|
<datatype> |
1937 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
1938 |
|
|
</datatype> |
1939 |
|
|
</constraint> |
1940 |
|
|
</objectType> |
1941 |
|
|
|
1942 |
|
|
</package> |
1943 |
|
|
|
1944 |
|
|
</package> |
1945 |
|
|
|
1946 |
|
|
|
1947 |
|
|
|
1948 |
|
|
<package> |
1949 |
|
|
<vodml-id>coords</vodml-id> |
1950 |
|
|
<name>coords</name> |
1951 |
|
|
<description> |
1952 |
|
|
TODO : Missing description : please, update your UML model asap. |
1953 |
|
|
</description> |
1954 |
|
|
<dataType abstract="true"> |
1955 |
|
|
<vodml-id>coords.CoordValue</vodml-id> |
1956 |
|
|
<name>CoordValue</name> |
1957 |
|
|
<description>Abstract top level 1-dimensional coordinate value data type. There are four sub-types: simple integer and real for pixel spaces; discrete for enumerated coordinates; and the most commonly used physical coordinate value. It refers to a CoordFrame using coordAxis through an Axis and a CoordSpace object.</description> |
1958 |
|
|
<extends> |
1959 |
|
|
<vodml-ref>stc2_coordinates:coords.BasicCoordValue</vodml-ref> |
1960 |
|
|
</extends> |
1961 |
|
|
<reference> |
1962 |
|
|
<vodml-id>coords.CoordValue.coordAxis</vodml-id> |
1963 |
|
|
<name>coordAxis</name> |
1964 |
|
|
<description> |
1965 |
|
|
TODO : Missing description : please, update your UML model asap. |
1966 |
|
|
</description> |
1967 |
|
|
<datatype> |
1968 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.Axis</vodml-ref> |
1969 |
|
|
</datatype> |
1970 |
|
|
<multiplicity> |
1971 |
|
|
<minOccurs>1</minOccurs> |
1972 |
|
|
<maxOccurs>1</maxOccurs> |
1973 |
|
|
</multiplicity> |
1974 |
|
|
</reference> |
1975 |
|
|
</dataType> |
1976 |
|
|
|
1977 |
|
|
<dataType abstract="true"> |
1978 |
|
|
<vodml-id>coords.MultiCoordValue</vodml-id> |
1979 |
|
|
<name>MultiCoordValue</name> |
1980 |
|
|
<description>The value for vector coordinates. The vector is built up from scalar CoordValue components.</description> |
1981 |
|
|
<extends> |
1982 |
|
|
<vodml-ref>stc2_coordinates:coords.BasicCoordValue</vodml-ref> |
1983 |
|
|
</extends> |
1984 |
|
|
<attribute> |
1985 |
|
|
<vodml-id>coords.MultiCoordValue.cmpt</vodml-id> |
1986 |
|
|
<name>cmpt</name> |
1987 |
|
|
<description> |
1988 |
|
|
TODO : Missing description : please, update your UML model asap. |
1989 |
|
|
</description> |
1990 |
|
|
<datatype> |
1991 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue</vodml-ref> |
1992 |
|
|
</datatype> |
1993 |
|
|
<multiplicity> |
1994 |
|
|
<minOccurs>1</minOccurs> |
1995 |
|
|
<maxOccurs>-1</maxOccurs> |
1996 |
|
|
</multiplicity> |
1997 |
|
|
</attribute> |
1998 |
|
|
</dataType> |
1999 |
|
|
|
2000 |
|
|
<dataType abstract="true"> |
2001 |
|
|
<vodml-id>coords.PhysicalCoordValue</vodml-id> |
2002 |
|
|
<name>PhysicalCoordValue</name> |
2003 |
|
|
<description>Most common coordinate value type. The value is an (abstract) Quantity that needs to be further specified in each domain. The coordAxis is subsetted to an object of type CoordAxis.</description> |
2004 |
|
|
<extends> |
2005 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue</vodml-ref> |
2006 |
|
|
</extends> |
2007 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
2008 |
|
|
<role> |
2009 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue.coordAxis</vodml-ref> |
2010 |
|
|
</role> |
2011 |
|
|
<datatype> |
2012 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordAxis</vodml-ref> |
2013 |
|
|
</datatype> |
2014 |
|
|
</constraint> |
2015 |
|
|
<attribute> |
2016 |
|
|
<vodml-id>coords.PhysicalCoordValue.cval</vodml-id> |
2017 |
|
|
<name>cval</name> |
2018 |
|
|
<description> |
2019 |
|
|
TODO : Missing description : please, update your UML model asap. |
2020 |
|
|
</description> |
2021 |
|
|
<datatype> |
2022 |
|
|
<vodml-ref>ivoa:Quantity</vodml-ref> |
2023 |
|
|
</datatype> |
2024 |
|
|
<multiplicity> |
2025 |
|
|
<minOccurs>1</minOccurs> |
2026 |
|
|
<maxOccurs>1</maxOccurs> |
2027 |
|
|
</multiplicity> |
2028 |
|
|
</attribute> |
2029 |
|
|
</dataType> |
2030 |
|
|
|
2031 |
|
|
<dataType abstract="true"> |
2032 |
|
|
<vodml-id>coords.IntegerCoordValue</vodml-id> |
2033 |
|
|
<name>IntegerCoordValue</name> |
2034 |
|
|
<description>Integer-valued coordinate specifically intended for pixel index values.</description> |
2035 |
|
|
<extends> |
2036 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue</vodml-ref> |
2037 |
|
|
</extends> |
2038 |
|
|
<attribute> |
2039 |
|
|
<vodml-id>coords.IntegerCoordValue.cval</vodml-id> |
2040 |
|
|
<name>cval</name> |
2041 |
|
|
<description> |
2042 |
|
|
TODO : Missing description : please, update your UML model asap. |
2043 |
|
|
</description> |
2044 |
|
|
<datatype> |
2045 |
|
|
<vodml-ref>ivoa:integer</vodml-ref> |
2046 |
|
|
</datatype> |
2047 |
|
|
<multiplicity> |
2048 |
|
|
<minOccurs>1</minOccurs> |
2049 |
|
|
<maxOccurs>1</maxOccurs> |
2050 |
|
|
</multiplicity> |
2051 |
|
|
</attribute> |
2052 |
|
|
</dataType> |
2053 |
|
|
|
2054 |
|
|
<dataType abstract="true"> |
2055 |
|
|
<vodml-id>coords.RealCoordValue</vodml-id> |
2056 |
|
|
<name>RealCoordValue</name> |
2057 |
|
|
<description>Real-valued coordinate specifically intended for use in pixel spaces.</description> |
2058 |
|
|
<extends> |
2059 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue</vodml-ref> |
2060 |
|
|
</extends> |
2061 |
|
|
<attribute> |
2062 |
|
|
<vodml-id>coords.RealCoordValue.cval</vodml-id> |
2063 |
|
|
<name>cval</name> |
2064 |
|
|
<description> |
2065 |
|
|
TODO : Missing description : please, update your UML model asap. |
2066 |
|
|
</description> |
2067 |
|
|
<datatype> |
2068 |
|
|
<vodml-ref>ivoa:real</vodml-ref> |
2069 |
|
|
</datatype> |
2070 |
|
|
<multiplicity> |
2071 |
|
|
<minOccurs>1</minOccurs> |
2072 |
|
|
<maxOccurs>1</maxOccurs> |
2073 |
|
|
</multiplicity> |
2074 |
|
|
</attribute> |
2075 |
|
|
</dataType> |
2076 |
|
|
|
2077 |
|
|
<dataType abstract="true"> |
2078 |
|
|
<vodml-id>coords.BasicCoordValue</vodml-id> |
2079 |
|
|
<name>BasicCoordValue</name> |
2080 |
|
|
<description>Abstract top-level coordinate value data type. Derived from this are various 1-dimensional coordinate value types and one multi-dimensional type.</description> |
2081 |
|
|
</dataType> |
2082 |
|
|
|
2083 |
|
|
<dataType abstract="true"> |
2084 |
|
|
<vodml-id>coords.DiscreteCoordValue</vodml-id> |
2085 |
|
|
<name>DiscreteCoordValue</name> |
2086 |
|
|
<description>Coordinate value for discrete (enumerated) coordinate axes. The actual type of the value needs to be specified in the coordinate domain. The coordAxis is subsetted to DiscreteAxis. For an example, see the polarization domain.</description> |
2087 |
|
|
<extends> |
2088 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue</vodml-ref> |
2089 |
|
|
</extends> |
2090 |
|
|
<constraint xsi:type="vo-dml:SubsettedRole"> |
2091 |
|
|
<role> |
2092 |
|
|
<vodml-ref>stc2_coordinates:coords.CoordValue.coordAxis</vodml-ref> |
2093 |
|
|
</role> |
2094 |
|
|
<datatype> |
2095 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.DiscreteAxis</vodml-ref> |
2096 |
|
|
</datatype> |
2097 |
|
|
</constraint> |
2098 |
|
|
</dataType> |
2099 |
|
|
|
2100 |
|
|
</package> |
2101 |
|
|
|
2102 |
|
|
|
2103 |
|
|
|
2104 |
|
|
<package> |
2105 |
|
|
<vodml-id>coordsystem</vodml-id> |
2106 |
|
|
<name>coordsystem</name> |
2107 |
|
|
<description> |
2108 |
|
|
TODO : Missing description : please, update your UML model asap. |
2109 |
|
|
</description> |
2110 |
|
|
<objectType abstract="true"> |
2111 |
|
|
<vodml-id>coordsystem.CoordFrame</vodml-id> |
2112 |
|
|
<name>CoordFrame</name> |
2113 |
|
|
<description>This is the abstract empty base class for all coordinate frames. A Frame SHALL contain one corresponding Coordinate Space.</description> |
2114 |
|
|
<composition> |
2115 |
|
|
<vodml-id>coordsystem.CoordFrame.coordSpace</vodml-id> |
2116 |
|
|
<name>coordSpace</name> |
2117 |
|
|
<description> |
2118 |
|
|
TODO : Missing description : please, update your UML model asap. |
2119 |
|
|
</description> |
2120 |
|
|
<datatype> |
2121 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSpace</vodml-ref> |
2122 |
|
|
</datatype> |
2123 |
|
|
<multiplicity> |
2124 |
|
|
<minOccurs>1</minOccurs> |
2125 |
|
|
<maxOccurs>1</maxOccurs> |
2126 |
|
|
</multiplicity> |
2127 |
|
|
</composition> |
2128 |
|
|
</objectType> |
2129 |
|
|
|
2130 |
|
|
<objectType> |
2131 |
|
|
<vodml-id>coordsystem.AstroCoordSystem</vodml-id> |
2132 |
|
|
<name>AstroCoordSystem</name> |
2133 |
|
|
<description>An AstroCoordSystem MAY contain any number of coordinate frames: GenericFrame, TimeFrame, SpaceFrame, SpectralFrame, RedshiftFrame, PolarizationFrame. In addition, it SHALL contain the common reference position (refPosition) for the astronomical frames and it MAY contain the name of a planetary ephemeris (which SHOULD be included when appropriate).</description> |
2134 |
|
|
<extends> |
2135 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.CoordSys</vodml-ref> |
2136 |
|
|
</extends> |
2137 |
|
|
<attribute> |
2138 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.refPosition</vodml-id> |
2139 |
|
|
<name>refPosition</name> |
2140 |
|
|
<description> |
2141 |
|
|
TODO : Missing description : please, update your UML model asap. |
2142 |
|
|
</description> |
2143 |
|
|
<datatype> |
2144 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.Location</vodml-ref> |
2145 |
|
|
</datatype> |
2146 |
|
|
<multiplicity> |
2147 |
|
|
<minOccurs>1</minOccurs> |
2148 |
|
|
<maxOccurs>1</maxOccurs> |
2149 |
|
|
</multiplicity> |
2150 |
|
|
</attribute> |
2151 |
|
|
<attribute> |
2152 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.planetaryEphem</vodml-id> |
2153 |
|
|
<name>planetaryEphem</name> |
2154 |
|
|
<description> |
2155 |
|
|
TODO : Missing description : please, update your UML model asap. |
2156 |
|
|
</description> |
2157 |
|
|
<datatype> |
2158 |
|
|
<vodml-ref>ivoa:string</vodml-ref> |
2159 |
|
|
</datatype> |
2160 |
|
|
<multiplicity> |
2161 |
|
|
<minOccurs>0</minOccurs> |
2162 |
|
|
<maxOccurs>1</maxOccurs> |
2163 |
|
|
</multiplicity> |
2164 |
|
|
</attribute> |
2165 |
|
|
<reference> |
2166 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.timeFrame</vodml-id> |
2167 |
|
|
<name>timeFrame</name> |
2168 |
|
|
<description> |
2169 |
|
|
TODO : Missing description : please, update your UML model asap. |
2170 |
|
|
</description> |
2171 |
|
|
<datatype> |
2172 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.timeDomain.TimeFrame</vodml-ref> |
2173 |
|
|
</datatype> |
2174 |
|
|
<multiplicity> |
2175 |
|
|
<minOccurs>0</minOccurs> |
2176 |
|
|
<maxOccurs>-1</maxOccurs> |
2177 |
|
|
</multiplicity> |
2178 |
|
|
</reference> |
2179 |
|
|
<reference> |
2180 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.spaceFrame</vodml-id> |
2181 |
|
|
<name>spaceFrame</name> |
2182 |
|
|
<description> |
2183 |
|
|
TODO : Missing description : please, update your UML model asap. |
2184 |
|
|
</description> |
2185 |
|
|
<datatype> |
2186 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spatialDomain.SpaceFrame</vodml-ref> |
2187 |
|
|
</datatype> |
2188 |
|
|
<multiplicity> |
2189 |
|
|
<minOccurs>0</minOccurs> |
2190 |
|
|
<maxOccurs>-1</maxOccurs> |
2191 |
|
|
</multiplicity> |
2192 |
|
|
</reference> |
2193 |
|
|
<reference> |
2194 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.redshiftFrame</vodml-id> |
2195 |
|
|
<name>redshiftFrame</name> |
2196 |
|
|
<description> |
2197 |
|
|
TODO : Missing description : please, update your UML model asap. |
2198 |
|
|
</description> |
2199 |
|
|
<datatype> |
2200 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.redshiftDomain.RedshiftFrame</vodml-ref> |
2201 |
|
|
</datatype> |
2202 |
|
|
<multiplicity> |
2203 |
|
|
<minOccurs>0</minOccurs> |
2204 |
|
|
<maxOccurs>-1</maxOccurs> |
2205 |
|
|
</multiplicity> |
2206 |
|
|
</reference> |
2207 |
|
|
<reference> |
2208 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.polarizationFrame</vodml-id> |
2209 |
|
|
<name>polarizationFrame</name> |
2210 |
|
|
<description> |
2211 |
|
|
TODO : Missing description : please, update your UML model asap. |
2212 |
|
|
</description> |
2213 |
|
|
<datatype> |
2214 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.polarizationDomain.PolarizationFrame</vodml-ref> |
2215 |
|
|
</datatype> |
2216 |
|
|
<multiplicity> |
2217 |
|
|
<minOccurs>0</minOccurs> |
2218 |
|
|
<maxOccurs>-1</maxOccurs> |
2219 |
|
|
</multiplicity> |
2220 |
|
|
</reference> |
2221 |
|
|
<reference> |
2222 |
|
|
<vodml-id>coordsystem.AstroCoordSystem.spectralFrame</vodml-id> |
2223 |
|
|
<name>spectralFrame</name> |
2224 |
|
|
<description> |
2225 |
|
|
TODO : Missing description : please, update your UML model asap. |
2226 |
|
|
</description> |
2227 |
|
|
<datatype> |
2228 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.spectralDomain.SpectralFrame</vodml-ref> |
2229 |
|
|
</datatype> |
2230 |
|
|
<multiplicity> |
2231 |
|
|
<minOccurs>0</minOccurs> |
2232 |
|
|
<maxOccurs>-1</maxOccurs> |
2233 |
|
|
</multiplicity> |
2234 |
|
|
</reference> |
2235 |
|
|
</objectType> |
2236 |
|
|
|
2237 |
|
|
<objectType> |
2238 |
|
|
<vodml-id>coordsystem.CoordSys</vodml-id> |
2239 |
|
|
<name>CoordSys</name> |
2240 |
|
|
<description>A Coordinate System is a collection of Coordinate Frames.
This class is the base-level coordinate system and MAY contain any number of generic coordinate frames.
</description> |
2241 |
|
|
<reference> |
2242 |
|
|
<vodml-id>coordsystem.CoordSys.genericFrame</vodml-id> |
2243 |
|
|
<name>genericFrame</name> |
2244 |
|
|
<description> |
2245 |
|
|
TODO : Missing description : please, update your UML model asap. |
2246 |
|
|
</description> |
2247 |
|
|
<datatype> |
2248 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.genericDomain.GenericFrame</vodml-ref> |
2249 |
|
|
</datatype> |
2250 |
|
|
<multiplicity> |
2251 |
|
|
<minOccurs>0</minOccurs> |
2252 |
|
|
<maxOccurs>-1</maxOccurs> |
2253 |
|
|
</multiplicity> |
2254 |
|
|
</reference> |
2255 |
|
|
</objectType> |
2256 |
|
|
|
2257 |
|
|
<objectType> |
2258 |
|
|
<vodml-id>coordsystem.PixelCoordSystem</vodml-id> |
2259 |
|
|
<name>PixelCoordSystem</name> |
2260 |
|
|
<description>A Pixel Coordinate System contains one or more Pixel Frames.</description> |
2261 |
|
|
<composition> |
2262 |
|
|
<vodml-id>coordsystem.PixelCoordSystem.pixelFrame</vodml-id> |
2263 |
|
|
<name>pixelFrame</name> |
2264 |
|
|
<description> |
2265 |
|
|
TODO : Missing description : please, update your UML model asap. |
2266 |
|
|
</description> |
2267 |
|
|
<datatype> |
2268 |
|
|
<vodml-ref>stc2_coordinates:CoordinateDomains.pixelDomain.PixelFrame</vodml-ref> |
2269 |
|
|
</datatype> |
2270 |
|
|
<multiplicity> |
2271 |
|
|
<minOccurs>1</minOccurs> |
2272 |
|
|
<maxOccurs>-1</maxOccurs> |
2273 |
|
|
</multiplicity> |
2274 |
|
|
</composition> |
2275 |
|
|
</objectType> |
2276 |
|
|
|
2277 |
|
|
<objectType abstract="true"> |
2278 |
|
|
<vodml-id>coordsystem.Axis</vodml-id> |
2279 |
|
|
<name>Axis</name> |
2280 |
|
|
<description>Axis is the abstract parent class for all coordinate axes. It SHALL contain the name of the axis.</description> |
2281 |
|
|
<attribute> |
2282 |
|
|
<vodml-id>coordsystem.Axis.name</vodml-id> |
2283 |
|
|
<name>name</name> |
2284 |
|
|
<description>Label for the first axis.</description> |
2285 |
|
|
<datatype> |
2286 |
|
|
<vodml-ref>ivoa:string</vodml-ref> |
2287 |
|
|
</datatype> |
2288 |
|
|
<multiplicity> |
2289 |
|
|
<minOccurs>1</minOccurs> |
2290 |
|
|
<maxOccurs>1</maxOccurs> |
2291 |
|
|
</multiplicity> |
2292 |
|
|
</attribute> |
2293 |
|
|
</objectType> |
2294 |
|
|
|
2295 |
|
|
<objectType abstract="true"> |
2296 |
|
|
<vodml-id>coordsystem.CoordSpace</vodml-id> |
2297 |
|
|
<name>CoordSpace</name> |
2298 |
|
|
<description>The CoordSpace is the abstract class from which all coordinate spaces are derived. It contains up to three coordinate axes.</description> |
2299 |
|
|
<composition> |
2300 |
|
|
<vodml-id>coordsystem.CoordSpace.coordAxis</vodml-id> |
2301 |
|
|
<name>coordAxis</name> |
2302 |
|
|
<description> |
2303 |
|
|
TODO : Missing description : please, update your UML model asap. |
2304 |
|
|
</description> |
2305 |
|
|
<datatype> |
2306 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.Axis</vodml-ref> |
2307 |
|
|
</datatype> |
2308 |
|
|
<multiplicity> |
2309 |
|
|
<minOccurs>1</minOccurs> |
2310 |
|
|
<maxOccurs>3</maxOccurs> |
2311 |
|
|
</multiplicity> |
2312 |
|
|
</composition> |
2313 |
|
|
</objectType> |
2314 |
|
|
|
2315 |
|
|
<objectType> |
2316 |
|
|
<vodml-id>coordsystem.CoordAxis</vodml-id> |
2317 |
|
|
<name>CoordAxis</name> |
2318 |
|
|
<description>CoordAxis is the most common type of coordinate axis, derived from Axis. It MAY contain a nativeAxisIndex if its coordinate space consists of more than one axis; the minimum and maximum allowable coordinate value along the axis in its domain (only if meaningful, of course); and a flag indicating whether the axis is cyclic (default: false).</description> |
2319 |
|
|
<extends> |
2320 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.Axis</vodml-ref> |
2321 |
|
|
</extends> |
2322 |
|
|
<attribute> |
2323 |
|
|
<vodml-id>coordsystem.CoordAxis.nativeAxisIndex</vodml-id> |
2324 |
|
|
<name>nativeAxisIndex</name> |
2325 |
|
|
<description> |
2326 |
|
|
TODO : Missing description : please, update your UML model asap. |
2327 |
|
|
</description> |
2328 |
|
|
<datatype> |
2329 |
|
|
<vodml-ref>ivoa:nonnegativeInteger</vodml-ref> |
2330 |
|
|
</datatype> |
2331 |
|
|
<multiplicity> |
2332 |
|
|
<minOccurs>0</minOccurs> |
2333 |
|
|
<maxOccurs>1</maxOccurs> |
2334 |
|
|
</multiplicity> |
2335 |
|
|
</attribute> |
2336 |
|
|
<attribute> |
2337 |
|
|
<vodml-id>coordsystem.CoordAxis.domainMin</vodml-id> |
2338 |
|
|
<name>domainMin</name> |
2339 |
|
|
<description> |
2340 |
|
|
TODO : Missing description : please, update your UML model asap. |
2341 |
|
|
</description> |
2342 |
|
|
<datatype> |
2343 |
|
|
<vodml-ref>ivoa:Quantity</vodml-ref> |
2344 |
|
|
</datatype> |
2345 |
|
|
<multiplicity> |
2346 |
|
|
<minOccurs>0</minOccurs> |
2347 |
|
|
<maxOccurs>1</maxOccurs> |
2348 |
|
|
</multiplicity> |
2349 |
|
|
</attribute> |
2350 |
|
|
<attribute> |
2351 |
|
|
<vodml-id>coordsystem.CoordAxis.domainMax</vodml-id> |
2352 |
|
|
<name>domainMax</name> |
2353 |
|
|
<description> |
2354 |
|
|
TODO : Missing description : please, update your UML model asap. |
2355 |
|
|
</description> |
2356 |
|
|
<datatype> |
2357 |
|
|
<vodml-ref>ivoa:Quantity</vodml-ref> |
2358 |
|
|
</datatype> |
2359 |
|
|
<multiplicity> |
2360 |
|
|
<minOccurs>0</minOccurs> |
2361 |
|
|
<maxOccurs>1</maxOccurs> |
2362 |
|
|
</multiplicity> |
2363 |
|
|
</attribute> |
2364 |
|
|
<attribute> |
2365 |
|
|
<vodml-id>coordsystem.CoordAxis.cyclic</vodml-id> |
2366 |
|
|
<name>cyclic</name> |
2367 |
|
|
<description> |
2368 |
|
|
TODO : Missing description : please, update your UML model asap. |
2369 |
|
|
</description> |
2370 |
|
|
<datatype> |
2371 |
|
|
<vodml-ref>ivoa:boolean</vodml-ref> |
2372 |
|
|
</datatype> |
2373 |
|
|
<multiplicity> |
2374 |
|
|
<minOccurs>0</minOccurs> |
2375 |
|
|
<maxOccurs>1</maxOccurs> |
2376 |
|
|
</multiplicity> |
2377 |
|
|
</attribute> |
2378 |
|
|
</objectType> |
2379 |
|
|
|
2380 |
|
|
<objectType> |
2381 |
|
|
<vodml-id>coordsystem.DiscreteAxis</vodml-id> |
2382 |
|
|
<name>DiscreteAxis</name> |
2383 |
|
|
<description>DiscreteAxis is specifically intended for enumerated coordinates, such as polarization.</description> |
2384 |
|
|
<extends> |
2385 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.Axis</vodml-ref> |
2386 |
|
|
</extends> |
2387 |
|
|
</objectType> |
2388 |
|
|
|
2389 |
|
|
<objectType> |
2390 |
|
|
<vodml-id>coordsystem.PixelAxis</vodml-id> |
2391 |
|
|
<name>PixelAxis</name> |
2392 |
|
|
<description>PixelAxis is the derived Axis class for pixel spaces. It SHALL contain its axis index in the PixelSpace and the number of pixels along the axis.</description> |
2393 |
|
|
<extends> |
2394 |
|
|
<vodml-ref>stc2_coordinates:coordsystem.Axis</vodml-ref> |
2395 |
|
|
</extends> |
2396 |
|
|
<attribute> |
2397 |
|
|
<vodml-id>coordsystem.PixelAxis.naxis</vodml-id> |
2398 |
|
|
<name>naxis</name> |
2399 |
|
|
<description> |
2400 |
|
|
TODO : Missing description : please, update your UML model asap. |
2401 |
|
|
</description> |
2402 |
|
|
<datatype> |
2403 |
|
|
<vodml-ref>ivoa:integer</vodml-ref> |
2404 |
|
|
</datatype> |
2405 |
|
|
<multiplicity> |
2406 |
|
|
<minOccurs>1</minOccurs> |
2407 |
|
|
<maxOccurs>1</maxOccurs> |
2408 |
|
|
</multiplicity> |
2409 |
|
|
</attribute> |
2410 |
|
|
<attribute> |
2411 |
|
|
<vodml-id>coordsystem.PixelAxis.numPix</vodml-id> |
2412 |
|
|
<name>numPix</name> |
2413 |
|
|
<description> |
2414 |
|
|
TODO : Missing description : please, update your UML model asap. |
2415 |
|
|
</description> |
2416 |
|
|
<datatype> |
2417 |
|
|
<vodml-ref>ivoa:integer</vodml-ref> |
2418 |
|
|
</datatype> |
2419 |
|
|
<multiplicity> |
2420 |
|
|
<minOccurs>1</minOccurs> |
2421 |
|
|
<maxOccurs>1</maxOccurs> |
2422 |
|
|
</multiplicity> |
2423 |
|
|
</attribute> |
2424 |
|
|
</objectType> |
2425 |
|
|
|
2426 |
|
|
</package> |
2427 |
|
|
|
2428 |
|
|
</vo-dml:model> |