diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000..d668cd9 --- /dev/null +++ b/.gitattributes @@ -0,0 +1,2 @@ +iwxxm.sh eol=lf +iwxxm.cmd eol=crlf \ No newline at end of file diff --git a/LICENSE.txt b/LICENSE.txt new file mode 100644 index 0000000..d645695 --- /dev/null +++ b/LICENSE.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/NOTICE.txt b/NOTICE.txt new file mode 100644 index 0000000..21b8f6e --- /dev/null +++ b/NOTICE.txt @@ -0,0 +1,99 @@ + +IBL IWXXM Validator +=================== + +NOTICE +------ + +The IWXXM Validator source code contains modified source code based on the following contribution: + +Command-line Refuter of Unshapely XML (CRUX) +Copyright © 2016 University Corporation for Atmospheric Research (UCAR). All rights reserved., +The BSD 3-Clause License + +https://github.com/NCAR/crux +https://github.com/NCAR/crux/blob/master/LICENSE + +The following files are based on CRUX source code: + validator/SchematronValidator.java, + validator/ValidationError.java + validator/XML10Validator.java + validator/XmlCalatogResolver.java + validator/IwxxmValidator.java + +-------------------------- + +The IWXXM Validator source code contains the following contributions as unmodified dependencies: + +Guava, Copyright (C) 2009 The Guava Authors +Apache License Version 2.0 +https://github.com/google/guava + +Apache Commons IO, Copyright 2002-2012 The Apache Software Foundation +Apache License Version 2.0 +http://commons.apache.org/proper/commons-io/ + +Apache Commons CLI, Copyright 2001-2015 The Apache Software Foundation +Apache License Version 2.0 +https://commons.apache.org/proper/commons-cli/ + +OWNER, Copyright (c) 2012-2015, Luigi R. Viggian +The BSD 3-Clause License +http://owner.aeonbits.org/ + +Apache Ant, Copyright © 1999-2016 Apache Software Foundation +Apache License Version 2.0 +http://ant.apache.org + +Logback, Copyright (C) 1999-2015, QOS.ch +Lesser General Public License version 2.1 +https://github.com/qos-ch/logback + +Jetty Web Container, Copyright 1995-2016 Mort Bay Consulting Pty Ltd. +Apache License Version 2.0 +http://www.eclipse.org/jetty/ + +Xerces, Copyright © 1999-2012 Apache Software Foundation +Apache License Version 2.0 +https://xerces.apache.org/index.html + +XML Resolver, Copyright © 2001-2009 Apache Software Foundation +Apache License Version 2.0 +http://xerces.apache.org/xml-commons/components/resolver/ + +Saxon HE, Copyright © 2015 Saxonica Limited +Mozilla Public License Version 2.0 +http://www.saxonica.com/ + +ISO Schematron XSLT, Copyright © 2000,2001 Rick Jelliffe and Academia Sinica Computing Center +http://www.ascc.net/xml/resource/schematron/schematron.html + +FasterXML Jackson, Copyright ©2009 FasterXML, LLC +Apache License Version 2.0 +https://github.com/FasterXML/jackson + +jsonrpc4j, Copyright (c) 2013 Brian +The MIT License (MIT) +https://github.com/briandilley/jsonrpc4j + +JUnit, Copyright © 2002-2016 JUnit +Eclipse Public License - v 1.0 +http://junit.org/ + +-------------------------- + +XSD schemas of IWXXM and its dependencies are included as part of source code. +For more information see http://schemas.wmo.int. + +AIXM, http://www.aixm.aero +Copyright (c) 2016, EUROCONTROL & FAA +BSD License, https://opensource.org/licenses/bsd-license.php + +GML Schemas +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ + +Observations and Measurements - XML Implementation is an OGC Standard. +Copyright (c) [2010] Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. + diff --git a/README.md b/README.md new file mode 100644 index 0000000..0965268 --- /dev/null +++ b/README.md @@ -0,0 +1,168 @@ +IWXXM Validation Web Service +============================ + +IWXXM Validation Web Service is a JSON-RPC 2.0 web service which allows to validate +IWXXM messages against XSD schemas and Schematron rules stored in the local application cache. + +It is possible to run application as json-rpc web service or as a command line tool to validate provided files. + +Requirements +------------ + +Requires JDK 1.7 or higher. To build application, Maven 3.2.3 is required. + +Building the application +------------------------ + +To build application use Maven 3.2.3 or later. Go to the directory with pom.xml file and type following command: +``` +mvn clean install +``` + +Running as a json-rpc web service +--------------------------------- + +On Linux machine, it is possible to start json-rpc service by command +``` +./iwxxm.sh --service +``` + +On Windows machine, it is possible to start json-rpc service by command +``` +iwxxm.cmd --service +``` + +By default, service is running by default on the port `8040`, on the url `http://:8040/json-rpc`. + +**Input request:** +* *requestVersion*: version of message request, now must be set to "1.0". +* *iwxxmVersion*: IWXXM version which will be used for validation, if omitted, than version is detected from provided IWXXM data +* *iwxxmData*: content of validated IWXXM XML report or report collection + +```json +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "method": "validate", + "params": { + "request": { + "requestVersion": "1.0", + "iwxxmData": "" + } +} +``` + +**Output response:** + +* *responseVersion*: version of response message, now always 1.0 +* *valid*: true or false, indicates if validated message is valid or not +* *validationErrors*: list of validation errors if report or report collection is not valid. If provided iwxxm data are valid, than this property is omitted + +Example of response for valid IWXXM data: +```json +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "result": { + "responseVersion": "1.0", + "valid": true + } +} +``` + +Example of response for invalid IWXXM data: +```json +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "result": { + "validationErrors": [ + { + "errorMessage": "cvc-complex-type.4: Attribute 'permissibleUsage' must appear on element 'iwxxm:SIGMET'.", + "lineNumber": 1, + "columnNumber": 1108 + }, + { + "errorMessage": "cvc-complex-type.4: Attribute 'uom' must appear on element 'iwxxm:directionOfMotion'.", + "lineNumber": 1, + "columnNumber": 4399 + }, + { + "errorMessage": "SIGMET.EMC1: directionOfMotion shall be reported in degrees (deg). ((if(exists(iwxxm:directionOfMotion) and (not(exists(iwxxm:directionOfMotion/@xsi:nil)) or iwxxm:directionOfMotion/@xsi:nil != 'true')) then (iwxxm:directionOfMotion/@uom = 'deg') else true()))" + } + ], + "responseVersion": "1.0", + "valid": false + } +} +``` + +**Validation of multiple IWXXM messages in one HTTP request** + +It is possible to validate multiple IWXXM messages in one HTTP request. JSON-RPC batching +can be used for this purpose - add multiple JSON-RPC request in array and send it to the +web service. + +Example of batch request: +```json +[ + { + "jsonrpc": "2.0", + "id": "iwxxm1", + "method": "validate", + "params": { ... } + }, + { + "jsonrpc": "2.0", + "id": "iwxxm2", + "method": "validate", + "params": { ... } + } +] +``` + +Example of batch response: +```json +[ + { + "jsonrpc": "2.0", + "id": "iwxxm1", + "result": { ... } + }, + { + "jsonrpc": "2.0", + "id": "iwxxm2", + "result": { ... } + } +] +``` + +Running validation from command line +------------------------------------ + +It is possible to validate IWXXM reports stored in local files by following command: +``` +./iwxxm.sh --validate file1.xml file2.xml file_with_wildcars.xml +``` + +or on Windows machine: +``` +iwxxm.cmd --validate file1.xml file2.xml file_with_wildcars.xml +``` + +Updating XML Schema catalog +--------------------------- + +To prevent download of XSD schemas from the network, XML Schema catalog is stored +on the local disk in the directory `config/schemas`. Content of XML schema catalog +(together with schematron rules) is extracted from ZIP file downloaded from +[http://schemas.wmo.int/iwxxm/2.0/zip/iwxxm-schema-bundle-2.0.zip]. + +Configuration of web service +---------------------------- + +Default web service configuration can be changed in the file `config/iwxxm-webservice-config.properties`. +Location of this configuration file can be change by setting JVM property `-DconfigDir=`. + + + diff --git a/config/iwxxm-webservice-config.properties b/config/iwxxm-webservice-config.properties new file mode 100644 index 0000000..0445608 --- /dev/null +++ b/config/iwxxm-webservice-config.properties @@ -0,0 +1,38 @@ +# +# Copyright (C) 2016, IBL Software Engineering spol. s r. o. +# +# Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except +# in compliance with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software distributed under the License +# is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express +# or implied. See the License for the specific language governing permissions and limitations under +# the License. +# +############################################################################################################## + +#server.port=8040 +#server.allow-access-allow-origin=* + +#log.dir=./logs/ +#log.filename-pattern=ibl-vw-iwxxm-webservice.yyyy_mm_dd.log +#log.retain-in-days=30 + +#access-log.enabled=true +#access-log.dir=logs/ +#access-log.filename-pattern=ibl-vw-iwxxm-webservice.yyyy_mm_dd.access.log +#access-log.retain-in-days=90 +#access-log.format.time-zone=GMT +#access-log.format.date-time-format=yyyy-MM-dd'T'HH:mm:ssZ +#access-log.format.extended=true +#access-log.format.prefer-proxied=true + +#iwxxm.default-version= +#iwxxm.validation.schemas-dir=${configDir}/schemas +#iwxxm.validation.catalog-file=${iwxxm.validation.schemas-dir}/catalog.xml +#iwxxm.validation.rules-dir=${iwxxm.validation.schemas-dir}/rule +#iwxxm.validation.service-url=/json-rpc + +# note: empty value (default) for iwxxm.default-version means auto detection of iwxxm version from iwxxm namespace \ No newline at end of file diff --git a/config/schemas/catalog.xml b/config/schemas/catalog.xml new file mode 100644 index 0000000..0d43763 --- /dev/null +++ b/config/schemas/catalog.xml @@ -0,0 +1,23 @@ + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/rule/1.0/collect.sch b/config/schemas/rule/1.0/collect.sch new file mode 100644 index 0000000..24613be --- /dev/null +++ b/config/schemas/rule/1.0/collect.sch @@ -0,0 +1,10 @@ + + + Schematron validation + + + + MeteorologicalBulletin: Substituted element in all meteorologicalInformation(s) should be the same + + + diff --git a/config/schemas/rule/1.0/iwxxm.sch b/config/schemas/rule/1.0/iwxxm.sch new file mode 100644 index 0000000..69a8c15 --- /dev/null +++ b/config/schemas/rule/1.0/iwxxm.sch @@ -0,0 +1,377 @@ + + Schematron validation + + + + + + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + AerodromeRecentWeather: link tag should be named ok + + + + + AerodromePresentWeather: link tag should be named ok + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingVisibility when + cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0/metce.sch b/config/schemas/rule/1.0/metce.sch new file mode 100644 index 0000000..31f64c3 --- /dev/null +++ b/config/schemas/rule/1.0/metce.sch @@ -0,0 +1,28 @@ + + Schematron validation + + + + + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0/opm.sch b/config/schemas/rule/1.0/opm.sch new file mode 100644 index 0000000..2f29aaa --- /dev/null +++ b/config/schemas/rule/1.0/opm.sch @@ -0,0 +1,39 @@ + + Schematron validation + + + + + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0/saf.sch b/config/schemas/rule/1.0/saf.sch new file mode 100644 index 0000000..b1904a9 --- /dev/null +++ b/config/schemas/rule/1.0/saf.sch @@ -0,0 +1,64 @@ + + Schematron validation + + + + + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + Service: name not match with pattern TextNameType + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC1/metarSpeci.sch b/config/schemas/rule/1.0RC1/metarSpeci.sch new file mode 100644 index 0000000..ba5b8b1 --- /dev/null +++ b/config/schemas/rule/1.0RC1/metarSpeci.sch @@ -0,0 +1,87 @@ + + + + + + + + + + + + + + + Result should be a MeteorologicalAerodromeObservationRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + Result should be a MeteorologicalAerodromeTrendForecastRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + + + + Result should be a MeteorologicalAerodromeObservationRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + Result should be a MeteorologicalAerodromeTrendForecastRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC1/sigmet.sch b/config/schemas/rule/1.0RC1/sigmet.sch new file mode 100644 index 0000000..04be099 --- /dev/null +++ b/config/schemas/rule/1.0RC1/sigmet.sch @@ -0,0 +1,72 @@ + + + + + + + + + + + + + + Result should be a EvolvingMeteorologicalCondition + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingSurface) + + + + + + Result should be a EvolvingMeteorologicalCondition + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingSurface) + + + Result should be a MeteorologicalFeatureCollection + + + + + + + Result should be a EvolvingMeteorologicalCondition + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingSurface) + + + Result should be a MeteorologicalFeatureCollection + + + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC1/taf.sch b/config/schemas/rule/1.0RC1/taf.sch new file mode 100644 index 0000000..2b00f87 --- /dev/null +++ b/config/schemas/rule/1.0RC1/taf.sch @@ -0,0 +1,47 @@ + + + + + + + + + + + + + + Result should be a MeteorologicalAerodromeForecastRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + + Result should be a MeteorologicalAerodromeForecastRecord + + + featureOfInterest should be an SF_SamplingPoint (type is an xlink:href to http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/SF_SamplingPoint) + + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC2/iwxxm.sch b/config/schemas/rule/1.0RC2/iwxxm.sch new file mode 100644 index 0000000..7fe5b18 --- /dev/null +++ b/config/schemas/rule/1.0RC2/iwxxm.sch @@ -0,0 +1,407 @@ + + Schematron validation + + + + + + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingHorizontalVisibility + when cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + SIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + SIGMET: A canceled SIGMET should not have an analysis + + + + + SIGMET: There must be at least one analysis when a SIGMET does not have canceled status + + + + + SIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC2/metce.sch b/config/schemas/rule/1.0RC2/metce.sch new file mode 100644 index 0000000..31f64c3 --- /dev/null +++ b/config/schemas/rule/1.0RC2/metce.sch @@ -0,0 +1,28 @@ + + Schematron validation + + + + + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC2/opm.sch b/config/schemas/rule/1.0RC2/opm.sch new file mode 100644 index 0000000..2f29aaa --- /dev/null +++ b/config/schemas/rule/1.0RC2/opm.sch @@ -0,0 +1,39 @@ + + Schematron validation + + + + + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + \ No newline at end of file diff --git a/config/schemas/rule/1.0RC2/saf.sch b/config/schemas/rule/1.0RC2/saf.sch new file mode 100644 index 0000000..5272b77 --- /dev/null +++ b/config/schemas/rule/1.0RC2/saf.sch @@ -0,0 +1,64 @@ + + Schematron validation + + + + + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + Service: name not match with pattern TextNameType + + + \ No newline at end of file diff --git a/config/schemas/rule/1.1/collect.sch b/config/schemas/rule/1.1/collect.sch new file mode 100644 index 0000000..24613be --- /dev/null +++ b/config/schemas/rule/1.1/collect.sch @@ -0,0 +1,10 @@ + + + Schematron validation + + + + MeteorologicalBulletin: Substituted element in all meteorologicalInformation(s) should be the same + + + diff --git a/config/schemas/rule/1.1/iwxxm.sch b/config/schemas/rule/1.1/iwxxm.sch new file mode 100644 index 0000000..61c3dd5 --- /dev/null +++ b/config/schemas/rule/1.1/iwxxm.sch @@ -0,0 +1,377 @@ + + Schematron validation + + + + + + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + AerodromeRecentWeather: link tag should be named ok + + + + + AerodromePresentWeather: link tag should be named ok + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingVisibility when + cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + diff --git a/config/schemas/rule/1.1/metce.sch b/config/schemas/rule/1.1/metce.sch new file mode 100644 index 0000000..31f64c3 --- /dev/null +++ b/config/schemas/rule/1.1/metce.sch @@ -0,0 +1,28 @@ + + Schematron validation + + + + + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + \ No newline at end of file diff --git a/config/schemas/rule/1.1/opm.sch b/config/schemas/rule/1.1/opm.sch new file mode 100644 index 0000000..2f29aaa --- /dev/null +++ b/config/schemas/rule/1.1/opm.sch @@ -0,0 +1,39 @@ + + Schematron validation + + + + + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + \ No newline at end of file diff --git a/config/schemas/rule/1.1/saf.sch b/config/schemas/rule/1.1/saf.sch new file mode 100644 index 0000000..167c41a --- /dev/null +++ b/config/schemas/rule/1.1/saf.sch @@ -0,0 +1,64 @@ + + Schematron validation + + + + + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + Service: name not match with pattern TextNameType + + + diff --git a/config/schemas/rule/1.2/collect.sch b/config/schemas/rule/1.2/collect.sch new file mode 100644 index 0000000..adee24f --- /dev/null +++ b/config/schemas/rule/1.2/collect.sch @@ -0,0 +1,16 @@ + + + Schematron validation + + + + + + + + + + COLLECT.MB1: All meteorologicalInformation instances in MeteorologicalBulletin must be of the same type + + + diff --git a/config/schemas/rule/1.2/metce.sch b/config/schemas/rule/1.2/metce.sch new file mode 100644 index 0000000..cbe97ea --- /dev/null +++ b/config/schemas/rule/1.2/metce.sch @@ -0,0 +1,26 @@ + + + Schematron validation + + + + + + + + + + METCE.MC2: if measuringInterval or resolutionScale or both are given then unitOfMeasure must also be provided + + + + + METCE.MC1: If unitOfMeasure exists it shall be appropriate for measurand + + + + + METCE.RB1: The extreme lower limit of the range of interval must be less than the extreme upper limit + + + diff --git a/config/schemas/rule/1.2/opm.sch b/config/schemas/rule/1.2/opm.sch new file mode 100644 index 0000000..f6ebf9b --- /dev/null +++ b/config/schemas/rule/1.2/opm.sch @@ -0,0 +1,36 @@ + + + Schematron validation + + + + + + + + + + OPM.SC1: If unitOfMeasure exists it shall be appropriate for contraintProperty + + + + + OPM.COP1: Attribute 'count' shall specify the number of observed physical properties (specified via the 'property' association role) aggregated within this composite observable property + + + + + OPM.RC1: If unitOfMeasure exists it shall be appropriate for constraintProperty + + + + + OPM.QOP1: If unitOfMeasure exists it shall be appropriate for baseProperty + + + + + OPM.RB1: The extreme lower limit of the range of interval must be less than the extreme upper limit + + + diff --git a/config/schemas/rule/1.2RC1/collect.sch b/config/schemas/rule/1.2RC1/collect.sch new file mode 100644 index 0000000..1a2747a --- /dev/null +++ b/config/schemas/rule/1.2RC1/collect.sch @@ -0,0 +1,9 @@ + + Schematron validation + + + + COLLECT.MB1: Feature collection instances in MeteorologicalBulletin should be of the same type + + + diff --git a/config/schemas/rule/1.2RC1/metce.sch b/config/schemas/rule/1.2RC1/metce.sch new file mode 100644 index 0000000..cd29974 --- /dev/null +++ b/config/schemas/rule/1.2RC1/metce.sch @@ -0,0 +1,28 @@ + + Schematron validation + + + + + + + + + METCE.MC1: unitOfMeasure shall be appropriate for measurand + + + + + METCE.MC2: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + METCE.RB1: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + diff --git a/config/schemas/rule/1.2RC1/opm.sch b/config/schemas/rule/1.2RC1/opm.sch new file mode 100644 index 0000000..e1ea7de --- /dev/null +++ b/config/schemas/rule/1.2RC1/opm.sch @@ -0,0 +1,39 @@ + + Schematron validation + + + + + + + + + OPM.COP1: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + OPM.QOP1: unitOfMeasure shall be appropriate for baseProperty + + + + + OPM.RB1: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + OPM.RC1: unitOfMeasure shall be appropriate for constraintProperty + + + + + OPM.SC1: unitOfMeasure shall be appropriate for constraintProperty + + + diff --git a/config/schemas/rule/2.0/collect.sch b/config/schemas/rule/2.0/collect.sch new file mode 100644 index 0000000..adee24f --- /dev/null +++ b/config/schemas/rule/2.0/collect.sch @@ -0,0 +1,16 @@ + + + Schematron validation + + + + + + + + + + COLLECT.MB1: All meteorologicalInformation instances in MeteorologicalBulletin must be of the same type + + + diff --git a/config/schemas/rule/2.0/iwxxm-collect.sch.txt b/config/schemas/rule/2.0/iwxxm-collect.sch.txt new file mode 100644 index 0000000..397d0ab --- /dev/null +++ b/config/schemas/rule/2.0/iwxxm-collect.sch.txt @@ -0,0 +1,6 @@ + + + Schematron validation + + + diff --git a/config/schemas/rule/2.0/iwxxm.sch b/config/schemas/rule/2.0/iwxxm.sch new file mode 100644 index 0000000..e8ef82b --- /dev/null +++ b/config/schemas/rule/2.0/iwxxm.sch @@ -0,0 +1,612 @@ + + + Schematron validation + + + + + + + + + + + METAR_SPECI.ARS1: When all runways are being reported upon, no specific Runway should be reported + + + + + METAR_SPECI.ARS2: When a single Runway is reported upon, the allRunways flag should be missing or false + + + + + METAR_SPECI.ARVR1: meanRVR shall be reported in metres (m). + + + + + METAR_SPECI.MAORep2: When no clouds are detected by the auto system, this report must be an auto report + + + + + METAR_SPECI.MAORep1: Missing reports only include identifying information (time, aerodrome) and no other information + + + + + METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast + + + + + METAR_SPECI.MAORep3: The sampled feature for a METAR/SPECI observation is an aerodrome + + + + + METAR_SPECI.MAORep7: The procedure of a METAR/SPECI observation should be a metce:Process + + + + + METAR_SPECI.MAORep4: The result of a METAR/SPECI observation should be a MeteorologicalAerodromeObservationRecord + + + + + METAR_SPECI.MAORep5: The result of a METAR/SPECI trendForecast should be a MeteorologicalAerodromeTrendForecastRecord + + + + + METAR_SPECI.ASS1: If the sea state is set, significantWaveHeight is not reported (one or the other) + + + + + METAR_SPECI.ASS3: Either seaState or significantWaveHeight must be present + + + + + METAR_SPECI.ASS4: seaSurfaceTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.ASS2: If the significantWaveHeight is set, seaState is not reported (one or the other) + + + + + METAR_SPECI.ASS5: significantWaveHeight shall be reported in metres (m). + + + + + METAR_SPECI.AWS1: When all runways are affected by wind shear, no specific runways should be reported + + + + + METAR_SPECI.MATFR5: prevailingVisibility, prevailingVisibilityOperator, clouds, forecastWeather and cloudAndVisibilityOK should be absent when changeIndicator equals 'NO_SIGNIFICANT_CHANGES' + + + + + METAR_SPECI.MATFR1: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR2: forecastWeather should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR4: prevailingVisibility and prevailingVisibilityOperator should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR3: prevailingVisibility shall be reported in metres (m). + + + + + METAR_SPECI.MAORec6: airTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec3: presentWeather should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec2: rvr should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec1: visibility should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec7: dewpointTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec8: qnh shall be reported in hectopascals (hPa). + + + + + METAR_SPECI.MAORec5: Table A3-2 Note 7 states: "To be included if visibility or RVR &lt; 1500 m; for up to a maximum of four runways". This is interpreted to mean that if the prevailing visibility is below 1500 meters, RVR should always be included + + + + + METAR_SPECI.AOC1: Vertical visibility cannot be reported with cloud layers + + + + + METAR_SPECI.AOC2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + METAR_SPECI.ASW3: extremeClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW4: extremeCounterClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW5: meanWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kt_i]). + + + + + METAR_SPECI.ASW2: Wind direction is not reported when variable winds are indicated + + + + + METAR_SPECI.ASW7: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + METAR_SPECI.ASW1: All wind UOMs must be the same + + + + + METAR_SPECI.AHV1: minimumVisibility shall be reported in metres (m). + + + + + METAR_SPECI.AHV2: minimumVisibilityDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.AHV3: prevailingVisibility shall be reported in metres (m). + + + + + TAF.MAFR2: cloud should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR1: prevailingVisibility should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR3: weather should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR4: prevailingVisibility shall be reported in metres (m). + + + + + TAF.AATF1: maximumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.AATF2: minimumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.TAF1: Forecast conditions cannot include temperature information. They are otherwise identical to the prevailing conditions + + + + + TAF.TAF3: An amended report must also include the valid time of the amended report + + + + + TAF.TAF4: A cancelled report must also include the valid time of the cancelled report + + + + + TAF.TAF5: A corrected report must reference + + + + + TAF.TAF9: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF.TAF2: previousReportValidPeriod must be null unless this cancels, corrects or amends a previous report + + + + + TAF.TAF11: Non-missing TAF reports must contains validTime + + + + + TAF.TAF8: Base conditions may not have a change indicator + + + + + TAF.TAF14: The sampled feature of baseForecast is always an aerodrome + + + + + TAF.TAF16: The procedure of a TAF baseForecast should be a metce:Process + + + + + TAF.TAF12: The O&amp;M validTime of baseForecast must be a time period for TAF forecasts + + + + + TAF.TAF15: The sampled feature of changeForecast is always an aerodrome + + + + + TAF.TAF17: The procedure of a TAF changeForecast should be a metce:Process + + + + + TAF.TAF13: The O&amp;M validTime of changeForecast must be a time period for TAF forecasts + + + + + TAF.TAF6: resultTime for the baseForecast and the changeForecasts must match + + + + + SIGMET.SIGMET9: SIGMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + + + + + SIGMET.SIGMET1: A cancelled SIGMET should only include identifying information (time and airspace) and no other information + + + + + SIGMET.SIGMET2: There must be at least one analysis when a SIGMET does not have canceled status + + + + + SIGMET.SIGMET10: SIGMET must have a cancelled status if reporting volcanicAshMovedToFIR + + + + + SIGMET.SIGMET4: Sampled feature in analysis and forecastPositionAnalysis must be an FIR, UIR, or CTA + + + + + SIGMET.SIGMET7: The procedure of a SIGMET analysis should be a metce:Process + + + + + SIGMET.SIGMET3: OBS and FCST analyses must have a result type of EvolvingMeteorologicalCondition + + + + + SIGMET.SIGMET8: The procedure of a SIGMET forecastPositionAnalysis should be a metce:Process + + + + + SIGMET.SIGMET5: The result of a forecastPositionAnalysis should be a MeteorologicalPositionCollection + + + + + SIGMET.EMC1: directionOfMotion shall be reported in degrees (deg). + + + + + SIGMET.EMC5: geometryLowerLimitOperator can either be NULL or BELOW. + + + + + SIGMET.EMC6: geometryUpperLimitOperator can either be NULL or ABOVE + + + + + SIGMET.EMC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + SIGMET.EMC4: When SIGMET EvolvingMeteorologicalCondition timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + + + SIGMET.EMC3: When SIGMET EvolvingMeteorologicalCondition timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + + + AIRMET.AEMC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEMC2: cloudTop shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEMC3: directionOfMotion shall be reported in degrees (deg). + + + + + AIRMET.AEMC11: geometryLowerLimitOperator can either be NULL or BELOW. + + + + + AIRMET.AEMC12: geometryUpperLimitOperator can either be NULL or ABOVE + + + + + AIRMET.AEMC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + AIRMET.AEMC5: surfaceVisibility shall be reported in metres (m). + + + + + AIRMET.AEMC9: surfaceWindDirection shall be reported in the degrees unit of measure ('deg'). + + + + + AIRMET.AEMC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + AIRMET.AEMC10: surfaceWindDirection and surfaceWindSpeed must be reported together + + + + + AIRMET.AEMC8: When AIRMETEvolvingMeteorologicalCondition timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + + + AIRMET.AEMC7: When AIRMETEvolvingMeteorologicalCondition timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + + + AIRMET.AIRMET5: AIRMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + + + + + AIRMET.AIRMET2: A canceled AIRMET only include identifying information (time and airspace) and no other information + + + + + AIRMET.AIRMET3: There must be at least one analysis when a AIRMET does not have canceled status + + + + + AIRMET.AIRMET4: The procedure of an AIRMET analysis should be a metce:Process + + + + + AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingMeteorologicalCondition + + + + + TCA.TCFC1: maximumSurfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCA4: The procedure of a TCA forecast should be a metce:Process + + + + + TCA.TCA2: The result of a TCA forecast should be a TropicalCycloneForecastConditions + + + + + TCA.TCA3: The procedure of a TCA observation should be a metce:Process + + + + + TCA.TCA1: The result of a TCA observation should be a TropicalCycloneObservedConditions + + + + + TCA.TCOC1: centralPressure shall be reported in hectopascals (hPa). + + + + + TCA.TCOC2: meanMaxSurfaceWind shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCOC3: movementDirection shall be reported in degrees (deg). + + + + + TCA.TCOC4: movementSpeed shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC1: directionOfMotion shall be reported in degrees (deg). + + + + + VAA.VAC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC3: windDirection shall be reported in degrees (deg). + + + + + VAA.VAC4: windSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + VAA.VAA2: The procedure of a VAA analysis should be a metce:Process + + + + + VAA.VAA1: The result of a VAA analysis should be a VolcanicAshConditions + + + + + COMMON.CL1: base shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.Report4: Total size of extension content must not exceed 5000 characters per report + + + + + COMMON.Report2: Operational reports should not include a permissibleUsageReason + + + + + COMMON.Report1: Non-operational reports must include a permissibleUsageReason + + + + + COMMON.Report3: Translated reports must include translatedBulletinID, translatedBulletinReceptionTime, translationCentreDesignator, translationCentreName, translationTime and optionally translationFailedTAC if translation failed + + + + + COMMON.ACF1: Vertical visibility cannot be reported together with cloud layers + + + + + COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.ASWF1: Wind direction is not reported when variable winds are indicated + + + + + COMMON.ASWTF1: meanWindDirection shall be reported in degrees (deg). + + + + + COMMON.ASWTF2: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + COMMON.ASWTF3: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + diff --git a/config/schemas/rule/2.0RC1/iwxxm.sch b/config/schemas/rule/2.0RC1/iwxxm.sch new file mode 100644 index 0000000..6b889a7 --- /dev/null +++ b/config/schemas/rule/2.0RC1/iwxxm.sch @@ -0,0 +1,502 @@ + + + Schematron validation + + + + + + + + + + + METAR_SPECI.ARS3: When all runways are being reported upon, no specific Runway should be reported + + + + + METAR_SPECI.ARS1: Estimated surface friction must be between 0 and 0.9 + + + + + METAR_SPECI.ARS2: When surface friction is unreliable, no surface friction is reported + + + + + METAR_SPECI.ARS4: When a single Runway is reported upon, the allRunways flag should be missing or false + + + + + METAR_SPECI.ARVR1: meanRVR shall be reported in metres (m). + + + + + METAR_SPECI.MAORep2: When no clouds are detected by the auto system, this report must be an auto report + + + + + METAR_SPECI.MAORep1: Missing reports only include identifying information (time, aerodrome) and no other information + + + + + METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast + + + + + METAR_SPECI.MAORep3: The sampled feature for a METAR/SPECI observation is an aerodrome + + + + + METAR_SPECI.MAORep4: The result of a METAR/SPECI observation should be a MeteorologicalAerodromeObservationRecord + + + + + METAR_SPECI.MAORep5: The result of a METAR/SPECI trendForecast should be a MeteorologicalAerodromeTrendForecastRecord + + + + + METAR_SPECI.ASS1: If the sea state is set, significantWaveHeight is not reported (one or the other) + + + + + METAR_SPECI.ASS3: Either seaState or significantWaveHeight must be present + + + + + METAR_SPECI.ASS4: seaSurfaceTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.ASS2: If the significantWaveHeight is set, seaState is not reported (one or the other) + + + + + METAR_SPECI.ASS5: significantWaveHeight shall be reported in metres (m). + + + + + METAR_SPECI.AWS1: When all runways are affected by wind shear, no specific runways should be reported + + + + + METAR_SPECI.MATFR1: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR2: forecastWeather should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR3: prevailingVisibility shall be reported in metres (m). + + + + + METAR_SPECI.MAORec6: airTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec3: presentWeather should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec2: rvr should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec1: visibility should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec7: dewpointTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec8: qnh shall be reported in hectopascals (hPa). + + + + + METAR_SPECI.MAORec5: Table A3-2 Note 7 states: "To be included if visibility or RVR &lt; 1500 m; for up to a maximum of four runways". This is interpreted to mean that if the prevailing visibility is below 1500 meters, RVR should always be included + + + + + METAR_SPECI.AOC1: Vertical visibility cannot be reported with cloud layers + + + + + METAR_SPECI.AOC2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + METAR_SPECI.ASW3: extremeClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW4: extremeCounterClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW5: meanWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kt_i]). + + + + + METAR_SPECI.ASW2: Wind direction is not reported when variable winds are indicated + + + + + METAR_SPECI.ASW7: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + METAR_SPECI.ASW1: All wind UOMs must be the same + + + + + METAR_SPECI.AHV1: minimumVisibility shall be reported in metres (m). + + + + + METAR_SPECI.AHV2: minimumVisibilityDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.AHV3: prevailingVisibility shall be reported in metres (m). + + + + + TAF.MAFR2: cloud should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR1: prevailingVisibility should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR3: weather should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR4: prevailingVisibility shall be reported in metres (m). + + + + + TAF.AATF1: maximumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.AATF2: minimumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.TAF1: Forecast conditions cannot include temperature information. They are otherwise identical to the prevailing conditions + + + + + TAF.TAF3: An amended report must also include the valid time of the amended report + + + + + TAF.TAF4: A cancelled report must also include the valid time of the cancelled report + + + + + TAF.TAF5: A corrected report must reference + + + + + TAF.TAF9: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF.TAF2: previousReportValidPeriod must be null unless this cancels, corrects or amends a previous report + + + + + TAF.TAF11: Non-missing TAF reports must contains validTime + + + + + TAF.TAF10: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF.TAF8: Base conditions may not have a change indicator + + + + + TAF.TAF14: The sampled feature of baseForecast is always an aerodrome + + + + + TAF.TAF12: The O&amp;M validTime of baseForecast must be a time period for TAF forecasts + + + + + TAF.TAF15: The sampled feature of changeForecast is always an aerodrome + + + + + TAF.TAF13: The O&amp;M validTime of changeForecast must be a time period for TAF forecasts + + + + + TAF.TAF6: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF.TAF7: TAF issue time must match the baseForecast resultTime + + + + + SIGMET.SIGMET1: A cancelled SIGMET should only include identifying information (time and airspace) and no other information + + + + + SIGMET.SIGMET2: There must be at least one analysis when a SIGMET does not have canceled status + + + + + SIGMET.SIGMET4: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMET.SIGMET3: OBS and FCST analyses must have a result type of EvolvingMeteorologicalCondition + + + + + SIGMET.EMC1: directionOfMotion shall be reported in degrees (deg). + + + + + SIGMET.EMC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + SIGMET.TCS2: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMET.TCS1: The result of forecastPositionAnalysis should be a MeteorologicalPositionCollection + + + + + SIGMET.VAS2: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMET.VAS1: The result of a forecastPositionAnalysis should be a MeteorologicalPositionCollection + + + + + AIRMET.AEMC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEMC2: cloudTop shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEMC3: directionOfMotion shall be reported in degrees (deg). + + + + + AIRMET.AEMC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + AIRMET.AEMC5: surfaceVisibility shall be reported in metres (m). + + + + + AIRMET.AEMC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + AIRMET.AIRMET2: A canceled AIRMET only include identifying information (time and airspace) and no other information + + + + + AIRMET.AIRMET3: There must be at least one analysis when a AIRMET does not have canceled status + + + + + AIRMET.AIRMET4: surfaceVisibility shall be reported in metres (m). + + + + + AIRMET.AIRMET5: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingMeteorologicalCondition + + + + + TCA.TCFC1: maximumSurfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCOC1: centralPressure shall be reported in hectopascals (hPa). + + + + + TCA.TCOC2: meanMaxSurfaceWind shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCOC3: movementDirection shall be reported in degrees (deg). + + + + + TCA.TCOC4: movementSpeed shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC1: directionOfMotion shall be reported in degrees (deg). + + + + + VAA.VAC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC3: windDirection shall be reported in degrees (deg). + + + + + VAA.VAC4: windSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + COMMON.CL1: base shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.ACF1: Vertical visibility cannot be reported together with cloud layers + + + + + COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.ASWF1: Wind direction is not reported when variable winds are indicated + + + + + COMMON.ASWTF1: meanWindDirection shall be reported in degrees (deg). + + + + + COMMON.ASWTF2: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + COMMON.ASWTF3: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1/AIXM_AbstractGML_ObjectTypes.xsd b/config/schemas/schema/aero/aixm/5.1.1/AIXM_AbstractGML_ObjectTypes.xsd new file mode 100644 index 0000000..e3ecc85 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1/AIXM_AbstractGML_ObjectTypes.xsd @@ -0,0 +1,236 @@ + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + This derives from gml:DynamicFeatureType, as all AIXM features are expected to have temporal properties modeled using the Timeslice model. While the GML specification does not mandate that dynamic features derive from gml:DynamicFeatureType, many GML-aware applications may only detect a dynamic feature by this type hierarchy. Note that all temporal properties of gml:DynamicFeatureType are removed during this restriction, because they will be added for each AIXM feature specifically, based on the TimeSlice model + + + + + + + + + + + + + + + + + + + + + + Adds the FeatureMetadata, which is common to all AIXM features + + + + + + + + + + + + Substitution head for AIXM features. + + + + + Base type for AIXM complex types that are NOT features. For example, City, ContactInformation, AirspaceVolume, etc. It derives from AbstractGMLType so that AIXM objects are recognised as GML objects, thus ensuring that GML-aware applications recognise them properly. Retains only the mandatory gml:id attribute. + + + + + + + + + + + + + Substitution head for AIXM objects. + + + + + It provides a basis for deriving AIXM feature/object properties. It defines the nilReason attribute and currently, it is only used for properties that are derived from association with an AIM object. + + + + + + + + + Base type of AIXM Timeslices. Removes option attributes that are not used in AIXM. + + + + + + + + The efffectivity of the TimeSlice. + + + + + + + + + + + Adds in the AIXM specific properties, such as 'interpretation'. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Property indicating how the timeslice is to be interpreted. See the AIXM Temporality model for details. + + + + + + + + + + + + + Used for the identification of the Time Slice concerned. See the AIXM Temporality model for details. + + + + + + + + Used for indicating the order of the corrections of a Time Slice. See the AIXM Temporality model for details. + + + + + + + + The start and end of life of the feature. See the AIXM Temporality model for details. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1/AIXM_DataTypes.xsd b/config/schemas/schema/aero/aixm/5.1.1/AIXM_DataTypes.xsd new file mode 100644 index 0000000..ebc51e8 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1/AIXM_DataTypes.xsd @@ -0,0 +1,8099 @@ + + + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1/AIXM_Features.xsd b/config/schemas/schema/aero/aixm/5.1.1/AIXM_Features.xsd new file mode 100644 index 0000000..8752ad3 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1/AIXM_Features.xsd @@ -0,0 +1,11369 @@ + + + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_AbstractGML_ObjectTypes.xsd b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_AbstractGML_ObjectTypes.xsd new file mode 100644 index 0000000..39f7c81 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_AbstractGML_ObjectTypes.xsd @@ -0,0 +1,240 @@ + + + + + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + This derives from gml:DynamicFeatureType, as all AIXM features are expected to have temporal properties modeled using the Timeslice model. While the GML specification does not mandate that dynamic features derive from gml:DynamicFeatureType, many GML-aware applications may only detect a dynamic feature by this type hierarchy. Note that all temporal properties of gml:DynamicFeatureType are removed during this restriction, because they will be added for each AIXM feature specifically, based on the TimeSlice model + + + + + + + + + + + + + + + + + + + + + + Adds the FeatureMetadata, which is common to all AIXM features + + + + + + + + + + + + Substitution head for AIXM features. + + + + + Base type for AIXM complex types that are NOT features. For example, City, ContactInformation, AirspaceVolume, etc. It derives from AbstractGMLType so that AIXM objects are recognised as GML objects, thus ensuring that GML-aware applications recognise them properly. Retains only the mandatory gml:id attribute. + + + + + + + + + + + + + Substitution head for AIXM objects. + + + + + It provides a basis for deriving AIXM feature/object properties. It defines the nilReason attribute and currently, it is only used for properties that are derived from association with an AIM object. + + + + + + + + + Base type of AIXM Timeslices. Removes option attributes that are not used in AIXM. + + + + + + + + The efffectivity of the TimeSlice. + + + + + + + + + + + Adds in the AIXM specific properties, such as 'interpretation'. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Property indicating how the timeslice is to be interpreted. See the AIXM Temporality model for details. + + + + + + + + + + + + + Used for the identification of the Time Slice concerned. See the AIXM Temporality model for details. + + + + + + + + Used for indicating the order of the corrections of a Time Slice. See the AIXM Temporality model for details. + + + + + + + + The start and end of life of the feature. See the AIXM Temporality model for details. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_DataTypes.xsd b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_DataTypes.xsd new file mode 100644 index 0000000..2363174 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_DataTypes.xsd @@ -0,0 +1,443 @@ + + + + + + + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_Features.xsd b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_Features.xsd new file mode 100644 index 0000000..50d838d --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/AIXM_Features.xsd @@ -0,0 +1,522 @@ + + + + + + + + + + + + + + + + + http://external.schemas.opengis.net/gmlAIXMProfile/1.1/gml321forAIXM.xsd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/README.txt b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/README.txt new file mode 100644 index 0000000..6146b51 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/README.txt @@ -0,0 +1,17 @@ +AIXM_WX is an AIXM Profile for use in the weather community based upon AIXM 5.1.1. +As an AIXM profile, this schema is identical to the original except +that unneeded AIXM content has been removed. This profile may be used in XML +schemaLocations as an alternative to the full AIXM schema. + +The AIXM_WX profile contains those portions of AIXM that are needed to identify and locate +aeronautical regions related to weather reporting. This profile includes a selected set of +properties from the following AIXM types: + + -AirportHeliport + -Airspace + -AirspaceVolume + -Runway + -RunwayDirection + -Unit + +Questions or comments may be directed to braeckel AT ucar.edu diff --git a/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/message/AIXM_BasicMessage.xsd b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/message/AIXM_BasicMessage.xsd new file mode 100644 index 0000000..3f88e97 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1.1_profiles/AIXM_WX/5.1.1a/message/AIXM_BasicMessage.xsd @@ -0,0 +1,60 @@ + + + + + + + + + + + + + + + + + Basic Message.xsd + The definition of a simple data product, that contains just a collection of AIXM features. + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_AbstractGML_ObjectTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_AbstractGML_ObjectTypes.xsd new file mode 100644 index 0000000..ff46147 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_AbstractGML_ObjectTypes.xsd @@ -0,0 +1,239 @@ + + + + + + + + + + + http://www.aixm.aero/schema/5.1/profile/gml4aixm.xsd + + + + AIXM_AbstractGML_ObjectTypesFeatures.xsd + + + + + + + + + + + + + + This derives from gml:DynamicFeatureType, as all AIXM features are expected to have temporal properties modeled using the Timeslice model. While the GML specification does not mandate that dynamic features derive from gml:DynamicFeatureType, many GML-aware applications may only detect a dynamic feature by this type hierarchy. Note that all temporal properties of gml:DynamicFeatureType are removed during this restriction, because they will be added for each AIXM feature specifically, based on the TimeSlice model + + + + + + + + + + + + + + + + + + + + + + Adds the FeatureMetadata, which is common to all AIXM features + + + + + + + + + + + + Substitution head for AIXM features. + + + + + Base type for AIXM complex types that are NOT features. For example, City, ContactInformation, AirspaceVolume, etc. It derives from AbstractGMLType so that AIXM objects are recognised as GML objects, thus ensuring that GML-aware applications recognise them properly. Retains only the mandatory gml:id attribute. + + + + + + + + + + + + + Substitution head for AIXM objects. + + + + + It provides a basis for deriving AIXM feature/object properties. It defines the nilReason attribute and currently, it is only used for properties that are derived from association with an AIM object. + + + + + + + + + Base type of AIXM Timeslices. Removes option attributes that are not used in AIXM. + + + + + + + + The efffectivity of the TimeSlice. + + + + + + + + + + + Adds in the AIXM specific properties, such as 'interpretation'. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Property indicating how the timeslice is to be interpreted. See the AIXM Temporality model for details. + + + + + + + + + + + + + Used for the identification of the Time Slice concerned. See the AIXM Temporality model for details. + + + + + + + + Used for indicating the order of the corrections of a Time Slice. See the AIXM Temporality model for details. + + + + + + + + The start and end of life of the feature. See the AIXM Temporality model for details. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_DataTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_DataTypes.xsd new file mode 100644 index 0000000..88910e8 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_DataTypes.xsd @@ -0,0 +1,1404 @@ + + + + + + + + + + + + + + + + + http://www.aixm.aero/schema/5.1/profile/gml4aixm.xsd + + + + AIXM_DataTypes.xsd + + + Package containing the datatypes that are used throughout the AIXM. + +There are three different types of datatypes: +- datatype - This is basic data type that specifies a pattern to use. +- enumeration - This codes a fixed list of values. The OTHER value is important for mapping future changes to the list. If a value is added in the future and is not recognised by the current enumeration, it is mapped to the OTHER value. +- codelist - This is similar to an enumeration in that it is used to indicate a list of possible values. However, the list can be expanded, which means that the codelist is a union between the explicitly enumerated values and free text. + + + + + A type representing a combination of alphabetic characters. + + + + + + + + + + A type representing a combination of alphabetic and numeric characters. + + + + + + + + + + A string of Simple Latin upper case letters and/or digits and/or a few special characters (space, plus sign, minus sign, solidus -'/'). + + + + + + + + + + A string of Simple Latin upper case letters and/or digits and/or more special characters (space| exclamation mark| double quote| number sign| dollar sign| percent| ampersand| quote| left paren| right paren| asterisk| plus sign| comma| minus sign| period| solidus| colon| semicolon| less than operator| equals operator| greater than operator| question mark| commercial at| left bracket| reverse solidus| right bracket| circumflex| underscore| vertical bar| left brace| right brace). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A unit of measurement for a horizontal distance. +For example, metres, feet, nautical miles, kilometres, etc... + + + + + + + + + Nautical miles. + + + + + + + Kilometres. + + + + + + + Metres. + + + + + + + Feet. + + + + + + + Statute Mile + + + + + + + Centimetre. + + + + + + + + + + + + + + + + A unit of measurement for a vertical distance. +For example, Flight Level, metres, feet. + + + + + + + + + Feet. + + + + + + + Meters. + + + + + + + Flight level in hundreds of feet. + + + + + + + Standard meters (tens of meters). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A code indicating the reference for a vertical distance. +Two series of values exist: +1) real distance: from GND, from the MSL, from the WGS-84 ellipsoid; +2) distance based on a difference of pressures, according to the standard atmosphere. + + + + + + + + + The distance measured from the surface of the Earth (equivalent to AGL - Above Ground Level). + + + + + + + The distance measured from mean sea level (equivalent to altitude). + + + + + + + The distance measured from the WGS84 ellipsoid. + + + + + + + The vertical distance is measured with an altimeter set to the standard atmosphere. + + + + + + + + + + + + + + + + A coded identifier for an Aerodrome/Heliport. +The rules according to which this identifier should be formed are as follows: +1) If the AD/HP has an ICAO four letter location indicator, this will become the CODE_ID for the Aerodrome/Heliport; +2) If the AD/HP does not have an ICAO four letter location indicator but has an IATA three letter code, then this will become the CODE_ID for the Aerodrome/Heliport; +3) If the AD/HP does not have either an ICAO four letter location indicator or an IATA three letter code, an artificially generated code will be used. This will contain a group of letters and a number. The group of letters could be the 2 letter code of the State responsible for the Aerodrome/Heliport (or one of these, if there are more than one, like ED and ET for Germany) and the number could be an integer between 0001 and 9999. + + + + + + + + + + + Allowed types of airspace. + + + + + + + + + + + The coded identifier of an organisation, authority, agency or unit. + + + + + + + + + + + The three letter coded location identifier of an airport/heliport according to the IATA Resolution 763. + + + + + + + + + + + The four letter coded location identifier as published in the ICAO DOC 7910 - Location Indicators. + + + + + + + + + + + A code specifying whether a particular entity occurrence is an Aerodrome or a Heliport. + + + + + + + + + Aerodrome only. + + + + + + + Aerodrome with heliport landing area. + + + + + + + Heliport only. + + + + + + + Landing site. + + + + + + + + + + + + + + + + A coded list of values that indicates a type of airspace. + + + + + + + + + National Airspace System. +[note: The airspace within which a State provides Air Traffic Services is usually composed of:1) the territories over which the State has jurisdiction;2) those portions of the airspace over the high seas or in airspace of undetermined sovereignty where the provision of ATS are provided as determined by regional agreements. It can usually be determined by the UNION of FIRs (including, where appropriate, NO-FIRs) of the UNION of NAS-P. .] + + + + + + + + Flight information region. Airspace of defined dimensions within which flight information service and alerting service are provided. +Description: +ICAO Recognized. +Might, for example, be used if service provided by more than one unit. + + + + + + + + Part of an FIR. + + + + + + + Upper flight information region. An upper airspace of defined dimensions within which flight information service and alerting service are provided. +Description: +Non-ICAO Recognized. +Each state determines its definition for upper airspace. + + + + + + + + Part of a UIR. +[note: Might, for example, be used if more than one unites provide service in different parts of a UIR .] + + + + + + + + Control area. A controlled airspace extending upwards from a specified limit above the earth. +Description: +ICAO Recognized. + + + + + + + + Part of a CTA. + + + + + + + Part of an OCA. + + + + + + + Oceanic control area. A Control Area extending upwards in the upper airspace. +Description: +Non-ICAO Recognized. + + + + + + + + Upper control area. A Control Area extending upwards in the upper airspace. +Description: +Non-ICAO Recognized. + + + + + + + + Part of a UTA. + + + + + + + Terminal control area. Control area normally established at the confluence of ATS routes in the vicinity of one or more major aerodromes. +Description: +Non-ICAO Recognized. +Mainly used in Europe under the Flexible Use of Airspace concept. + + + + + + + + Part of a TMA. + + + + + + + Control zone. A controlled airspace extending upwards from the surface of the earth to a specified upper limit. +Description: +ICAO Recognized. + + + + + + + + Part of a CTR. + + + + + + + Oceanic transition area. + + + + + + + Control sector. A subdivision of a designated control area within which responsibility is assigned to one controller or to a small group of controllers. +Description: +ICAO Recognized. + + + + + + + + Temporary consolidated (collapsed) sector. + + + + + + + Temporary segregated area (FUA). Airspace of pre-defined dimensions within which activities require the reservation of airspace for the exclusive use of specific users during a predetermined period of time. +Description: +(NATO) An area in which there are special restrictive measures employed to prevent or minimize interference between friendly forces. +An area under military jurisdiction in which special security measures are employed to prevent unauthorized entry. + + + + + + + + Cross border area (FUA). Airspace of defined dimensions, above the land areas or territorial waters of more than one state. +Description: +Non-ICAO Recognized. +Mainly used in Europe under the Flexible Use of Airspace concept. + + + + + + + + Reduced co-ordination area (FUA). Portion of airspace of defined dimensions within which general aviation traffic is permitted "off-route" without requiring general aviation traffic controllers to initiate co-ordination with OAT controllers. +Description: +Non-ICAO Recognized. +Mainly used in Europe under the Flexible Use of Airspace concept. + + + + + + + + Regulated airspace (not otherwise covered). + + + + + + + Airway (corridor). A control area or portion thereof established in the form of a corridor. + + + + + + + + Military Training Route buffer. A control area or portion thereof, established in the form of a corridor around a military training route in order to protect it from other traffic. + + + + + + + + Prohibited area. Airspace of defined dimensions, above the land areas or territorial waters of a State, within which the flight of aircraft is prohibited. +Description: +ICAO Recognized. + + + + + + + + Restricted area. Airspace of defined dimensions, above the land areas or territorial waters of a State, within which the flight of aircraft is restricted in accordance with certain specified conditions. +Description: +ICAO Recognized. + + + + + + + + Danger area. Airspace of defined dimensions within which activities dangerous to the flight of aircraft may exist at specified times. +Description: +ICAO Recognized. + + + + + + + + Air Defence Identification Zone. Special designated airspace of defined dimensions within which aircraft are required to comply with special identification and/or reporting procedures additional to those related to the provision of air traffic services (ATS). +Description: +ICAO Recognized. + + + + + + + + Airspace for which not even an FIR is defined. +[note: There are parts in the world for which there is neither an FIR nor any other airspace-type is defined. These airspaces will be marked as NO-FIR .] + + + + + + + + Part of an airspace (used in airspace aggregation). + + + + + + + Airspace having a specified class. + + + + + + + Political/administrative area. + + + + + + + Activities of dangerous nature (other than a danger area). + + + + + + + Temporary reserved area (FUA). Airspace of pre-defined dimensions within which activities require the reservation of airspace during a predetermined period of time. +Description: +Non-ICAO Recognized. +Mainly used in Europe under the Flexible Use of Airspace concept. + + + + + + + + Alert area. Airspace which may contain a high volume of pilot training activities or unusual type of aerial activity, neither of which is hazardous to aircraft. +Description: +Non-ICAO Recognized. +Mainly used in contiguous United States and its territories. + + + + + + + + Warning area. A non-regulatory airspace of defined dimensions designated over international waters that contains activity which may be hazardous to aircraft not participating in the activity. The purpose of such warning areas is to warn non participating pilots of the potential danger. +Description: +Non-ICAO Recognized. +Mainly used in contiguous United States and its territories. + + + + + + + + Airspace protected from specific air traffic. + + + + + + + Minimum altitude area. The lowest altitude to be used under instrument meteorological conditions (IMC) which will provide a minimum vertical clearance of 300 m (1 000 ft) or in designated mountainous terrain 600 m (2 000 ft) above all obstacles located in the area specified. +Description: +ICAO Recognized. +Published by many States as rectangles of 1 x 1 degree on the ENR 6 charts. Note - In the exact calculation 984 feet can be used as an equivalent to 300 metres. + + + + + + + + Altimeter setting region. Airspace of defined dimensions within which standardized altimeter setting procedures apply. +Description: +Non-ICAO Recognized. +For example, during flight the altimeter shall be set to the current altimeter setting of the nearest station along the route of flight. + + + + + + + + Advisory Area. An area of defined dimensions within which air traffic advisory service is available. +Description: +ICAO Recognized. +Air traffic control service provides a much more complete service than air traffic advisory service; advisory areas and routes are therefore not established within controlled airspace, but air traffic advisory service may be provided below and above. + + + + + + + + Upper Advisory Area. An area of defined dimensions in upper airspace within which air traffic advisory service is available. +Description: +ICAO Recognized. +Air traffic control service provides a much more complete service than air traffic advisory service; advisory areas and routes are therefore not established within controlled airspace, but air traffic advisory service may be provided below and above. + + + + + + + + Airport Traffic Zone. Airspace of defined dimensions established around an airport for the protection of airport traffic. +Description: +ICAO Recognized. + + + + + + + + Part of an airport traffic zone + + + + + + + Helicopter traffic zone + + + + + + + A part of a national airspace system + + + + + + + + + + + + + + + + + + + + + + + A code that makes a distinction between runways for airplanes and FATO for helicopters. + + + + + + + + + Runway for airplanes + + + + + + + Final Approach and Take Off Area for helicopters + + + + + + + + + + + + + + + A unit providing particular ATS services. + + + + + + + + + Area control centre. + + + + + + + Automatic dependent surveillance unit. + + + + + + + Advisory centre. + + + + + + + Alerting post. + + + + + + + Aeronautical information services office. + + + + + + + Approach control office. + + + + + + + Arrivals approach control office. + + + + + + + Departures approach control office. + + + + + + + Aerodrome reporting office/ATS reporting office. + + + + + + + Air traffic control centre. + + + + + + + Air traffic flow management unit. + + + + + + + Air traffic management unit. + + + + + + + Air traffic services unit. + + + + + + + Briefing office (note: Note ICAO listed by nonetheless used.) + + + + + + + Commercial broadcasting station. + + + + + + + Communications office/centre. + + + + + + + Forecasting office. + + + + + + + Flight information centre. + + + + + + + Ground controlled approach systems office. + + + + + + + Meteorological office. + + + + + + + Meteorological watch office. + + + + + + + International NOTAM office. + + + + + + + Ocean control centre. + + + + + + + Precision approach radar centre. + + + + + + + Radar unit/office. + + + + + + + Regional area forecast centre. + + + + + + + Rescue co-ordination centre. + + + + + + + Rescue sub-centre. + + + + + + + Search and rescue centre. + + + + + + + Surface movement control office. + + + + + + + Surface movement radar office. + + + + + + + Surveillance radar approach office/centre. + + + + + + + Secondary surveillance radar office/centre. + + + + + + + Terminal area surveillance radar office/centre. + + + + + + + Aerodrome control tower. + + + + + + + Upper area control centre. + + + + + + + UHF direction finding station. + + + + + + + Upper information centre. + + + + + + + VHF direction finding station. + + + + + + + World area forecast centre. + + + + + + + Air route traffic control centre. + + + + + + + Flight service station. + + + + + + + Terminal radar approach control. + + + + + + + Military station/unit (or military office in general). + + + + + + + Planning/briefing office for military flight operations. + + + + + + + + + + + + + + + + A code for a logical value: Yes or No. + + + + + + + + + Yes. + + + + + + + No. + + + + + + + + + + + + + + + + A textual designator. + + + + + + + + + + + The official name of a State, an aerodrome, a unit, etc.. + + + + + + + + + + + The value of a bearing indication (at a given point) measured as the angle between the bearing and either True North or Magnetic North (this should appear explicitly or implicitly). The angle is measured clockwise from 0 degrees up to and including 360 degrees. The value can also be a VOR radial. For example, Westward is expressed as 270. + + + + + + + + + + + A (positive) distance. + + + + + + + + + + A vertical distance value. +For example, Upper and lower limits of an airspace, an ATS route, FL100, 600M, 300 FT, etc.. + +This data type also allows some special non-numerical values: + +GND - meaning "the Surface of the Earth"; +UNL - meaning "unlimited"; +FLOOR - meaning "the bottom of the airspace"; necessary to express usages for Airspace that have a non-constant lower limit; +CEILING - meaning "the top of the airspace"; necessary to express usages for Airspace that have a non-constant upper limit. + + + + + + + + + + List of vertical datums. + + + + + + + + + (ICAO Doc 9674) Earth gravitational model 1996. ICAO recommended vertical datum. + + + + + + + Australian Height Datum + + + + + + + North American Vertical Datum of 1988 + + + + + + + + + + + + + + + + A signed distance. + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_Features.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_Features.xsd new file mode 100644 index 0000000..d23602a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/AIXM_Features.xsd @@ -0,0 +1,719 @@ + + + + + + + + + + + + + + + + + + + + http://www.aixm.aero/schema/5.0/profile/gml4aixm.xsd + + + + AIXM_Features.xsd + + + Package containing the definition of the core AIXM Features and Objects. + +- The AIXM Features describe real world entities and are fundamental in AIXM. AIXM features can be concrete and tangible, or abstract and conceptual and can change in time. Features are represented as classes with a stereotype {feature}. + +- The AIXM Objects are abstractions of real world entities or, more frequently, properties of these entities, which do not exist outside of a feature. Objects are represented as classes with a stereotype {object}. + + + + + + + + + One of the two landing and take-off directions of a runway for which attributes like TORA, TODA, LDA, etc. may be defined. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The full textual designator of the landing and take-off direction. +Examples: 27, 35L, 01R. + + + + + + + + The measured angle between the runway direction and True North at a given position. Note : The True North is the north point at which the meridian lines meet. + + + + + + + The measured angle between the runway direction and Magnetic North at a given position. + + + + + + + The runway used by the RunwayDirection. + + + + + + + + + + + + + + A defined rectangular area on a land aerodrome/heliport prepared for the landing and take-off of aircraft. +Note: this includes the concept of Final Approach and Take-Off Area (FATO) for helicopters. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport which has more than one. +E.g. 09/27, 02R/20L, RWY 1. + + + + + + + The type can be either runway for airplanes or final approach and take off area (FATO) for helicopters. + + + + + + + The Airport the Runway is associated with. + + + + + + + + + + + + + + A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A coded designator for an Aerodrome/Heliport. + The rules according to which this identifier should be formed are as follows: + 1. If the AD/HP has an ICAO four letter location indicator, then this one will become the CODE_ID for the Aerodrome/Heliport; + 2. If the AD/HP does not have an ICAO four letter location indicator, but it has an IATA three letter code, then this one will become the CODE_ID for the Aerodrome/Heliport; + 3. If the AD/HP has neither an ICAO four letter location indicator nor an IATA three letter code, then an artificial generated code will be used. This will contain a group of letters and a number. The group of letters could be the 2 letter code of the State being responsible for the Aerodrome/Heliport and the number could be an integer between 0001 and 9999. + + + + + + + The primary official name of an aerodrome as designated by an appropriate authority. + + + + + + + The four letter ICAO location indicator of the aerodrome/heliport, as listed in ICAO DOC 7910. + + + + + + + + The identifier that is assigned to a location in accordance with rules (resolution 767) governed by the International Air Transport Association (IATA). + + + + + + + + The vertical distance above Mean Sea Level (MSL) of the highest point of the landing area. + + + + + + + Airport reference point. + + + + + + + + + + + + + + A defined three dimensional region of space relevant to air traffic. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A code indicating the general structure or characteristics of a particular airspace. + + + + + + + A published sequence of characters allowing the identification of the airspace. +Description: +Typical examples are the ID of the Danger, Prohibited, Temporary segregated Areas, etc. + + + + + + + + + The name given to an airspace by a responsible authority. +Description: +It should be written as published, with no significance to upper or lower case letters. + + + + + + + + A code indicating the Airspace designator is recorded in ICAO Doc. 7910. + + + + + + + + An portion of airspace that contributes to the defintion of an Airspace geometry. + + + + + + + + + + + + + + + + + + + The role of the component in the airspace geometry. If the geometry of an airspace is composed of single volume, then the attributes of this association class may be left empty. + + + + + + + + + + + + + + + + + + + + + + + + + + An portion of airspace that contributes to the defintion of an Airspace geometry. + + + + + + + + + + + + + + + + + + + A defined volume in the air, described as horizontal projection with vertical limits. + + + + + + + + + + + + + + + + + + + + + + + + + + The vertical position of the airspace ceiling. + + + + + + + + The reference surface used for the value of the upper limit. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + + + + The vertical position of the airspace floor. + + + + + + + The reference surface used for the value of the lower limit. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + + + The surface defining the horizontal shape of the AirspaceVolume. + + + + + + + + + + + + + + A generic term meaning variously all types of 'units' providing all types of services. This includes particularly Air Traffic Management (ATM) Units but also units which are not express verbs included in ATM such as SAR, MET, COM etc. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The full textual name of a unit. This name must be established according to the rules specified by ICAO, viz.: in the official language of the country, transposed into the Latin Alphabet where necessary. + + + + + + + A type by which the Unit is recognised, usually related to the standard type of services provided by it (e.g. area control centre, advisory centre, aeronautical information services office). + + + + + + + + A coded designator associated with the Unit. For example, the ICAO Location Indicator of an ACC, as listed in DOC 7910. + + + + + + + + + + + + + + + + + + + + An AIXM Point derived from GM_Point that includes properties for describing a point with elevation and vertical extent. Used in obstacles, navaids, etc. + + + + + + + + + + + + + + + + + + + + + + + + + + The vertical distance of the point measured from Mean Sea Level (MSL). + + + + + + + The distance of the geoid above (positive) or below (negative) the mathematical reference ellipsoid at the location of the point. + + + + + + + The set of reference points or a mathematical model of the Earth's surface (a datum) against which vertical position measurements are made as basis for measuring elevations. + + + + + + + The difference between the recorded elevation of a feature and its true elevation referenced to the same vertical datum expressed as a linear error at 95 percent probability. + + + + + + + + + + + + + + + + + + + AIXM Point containing horizontal accuracy data. In AIXM horizontal accuracy is considered a property of the geometry. + + + + + + + + + + + + + + + + + + The difference between the recorded horizontal coordinates of a feature and its true position referenced to the same geodetic datum expressed as a circular error at 95 percent probability. + + + + + + + + + + + + + + + + + + An AIXM surface derived from GM_Surface and extended to include Horizontal Accuracy Properties + + + + + + + + + + + + + + + + + + The difference between the recorded horizontal coordinates of a feature and its true position referenced to the same geodetic datum expressed as a circular error at 95 percent probability. + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/SchematronConstraints.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/SchematronConstraints.xml new file mode 100644 index 0000000..6cfd40f --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/SchematronConstraints.xml @@ -0,0 +1,71 @@ + + Schematron constraints for GML / ISO 19136 + + + + + + ValueArray may not carry both a reference to a codeSpace and a uom + + + + + All components shall be of the same type + All components shall be of the same type + + + + + The presence of a dimension attribute implies the presence of the srsName attribute. + The presence of an axisLabels attribute implies the presence of the srsName attribute. + The presence of an uomLabels attribute implies the presence of the srsName attribute. + The presence of an uomLabels attribute implies the presence of the axisLabels attribute and vice versa. + + + + + All patches shall be gml:PolygonPatch elements or an element in the substitution group of gml:PolygonPatch. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All patches shall be gml:Triangle elements or an element in the substitution group of gml:PolygonPatch. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + Property element may not carry both a reference to an object and contain an object. + Property element shall either carry a reference to an object or contain an object. + + + + + All values in the domain set shall be gml:MultiPoint elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiCurve elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiSurface elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiSolid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:Grid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:RectifiedGrid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/basicTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/basicTypes.xsd new file mode 100644 index 0000000..d05faea --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/basicTypes.xsd @@ -0,0 +1,262 @@ + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in “simple” types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values “+” (plus) and “-“ (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for “units Of measure”. The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: “:” (colon), “ “ (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as “kg”, “m/s”, etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the “Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: “#”, “./”, “../”, or a string of characters followed by a “:”. These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. “./m/s”). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default=”.” a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default=”,” a comma) +ts symbol used to separate tuples or coordinate strings (default=” “ a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateOperations.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateOperations.xsd new file mode 100644 index 0000000..f5fc4de --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateOperations.xsd @@ -0,0 +1,519 @@ + + + + coordinateOperations.xsd + See ISO/DIS 19136 13.6. +The spatial or temporal coordinate operations schema components can be divided into five logical parts, which define elements and types for XML encoding of the definitions of: +- Multiple abstract coordinate operations +- Multiple concrete types of coordinate operations, including Transformations and Conversions +- Abstract and concrete parameter values and groups +- Operation methods +- Abstract and concrete operation parameters and groups +These schema component encodes the Coordinate Operation package of the UML Model for ISO 19111 Clause 11. + + + + + + + gml:AbstractCoordinateOperation is a mathematical operation on coordinates that transforms or converts coordinates to another coordinate reference system. Many but not all coordinate operations (from CRS A to CRS B) also uniquely define the inverse operation (from CRS B to CRS A). In some cases, the operation method algorithm for the inverse operation is the same as for the forward algorithm, but the signs of some operation parameter values shall be reversed. In other cases, different algorithms are required for the forward and inverse operations, but the same operation parameter values are used. If (some) entirely different parameter values are needed, a different coordinate operation shall be defined. +The optional coordinateOperationAccuracy property elements provide estimates of the impact of this coordinate operation on point position accuracy. + + + + + + + + + + + + + + + + + + + gml:operationVersion is the version of the coordinate transformation (i.e., instantiation due to the stochastic nature of the parameters). Mandatory when describing a transformation, and should not be supplied for a conversion. + + + + + gml:coordinateOperationAccuracy is an association role to a DQ_PositionalAccuracy object as encoded in ISO/TS 19139, either referencing or containing the definition of that positional accuracy. That object contains an estimate of the impact of this coordinate operation on point accuracy. That is, it gives position error estimates for the target coordinates of this coordinate operation, assuming no errors in the source coordinates. + + + + + + + + + + + gml:sourceCRS is an association role to the source CRS (coordinate reference system) of this coordinate operation. + + + + + gml:targetCRS is an association role to the target CRS (coordinate reference system) of this coordinate operation. + + + + + gml:CoordinateOperationPropertyType is a property type for association roles to a coordinate operation, either referencing or containing the definition of that coordinate operation. + + + + + + + + + gml:AbstractSingleOperation is a single (not concatenated) coordinate operation. + + + + + gml:SingleOperationPropertyType is a property type for association roles to a single operation, either referencing or containing the definition of that single operation. + + + + + + + + + gm:AbstractGeneralConversion is an abstract operation on coordinates that does not include any change of datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters. The operationVersion, sourceCRS, and targetCRS elements are omitted in a coordinate conversion. +This abstract complex type is expected to be extended for well-known operation methods with many Conversion instances, in GML Application Schemas that define operation-method-specialized element names and contents. This conversion uses an operation method, usually with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references the "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include zero or more elements each named "uses...Value" that each use the type of an element substitutable for the "AbstractGeneralParameterValue" element. + + + + + + + + + + + + + + + + + + + + + + + gml:GeneralConversionPropertyType is a property type for association roles to a general conversion, either referencing or containing the definition of that conversion. + + + + + + + + + gml:AbstractGeneralTransformation is an abstract operation on coordinates that usually includes a change of Datum. The parameters of a coordinate transformation are empirically derived from data containing the coordinates of a series of points in both coordinate reference systems. This computational process is usually "over-determined", allowing derivation of error (or accuracy) estimates for the transformation. Also, the stochastic nature of the parameters may result in multiple (different) versions of the same coordinate transformation. The operationVersion, sourceCRS, and targetCRS proeprty elements are mandatory in a coordinate transformation. +This abstract complex type is expected to be extended for well-known operation methods with many Transformation instances, in Application Schemas that define operation-method-specialized value element names and contents. This transformation uses an operation method with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references one "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include one or more elements each named "uses...Value" that each use the type of an element substitutable for the "AbstractGeneralParameterValue" element. + + + + + + + + + + + + + + + + + + + + + + + + + + gml:GeneralTransformationPropertyType is a property type for association roles to a general transformation, either referencing or containing the definition of that transformation. + + + + + + + + + + gml:ConcatenatedOperation is an ordered sequence of two or more coordinate operations. This sequence of operations is constrained by the requirement that the source coordinate reference system of step (n+1) must be the same as the target coordinate reference system of step (n). The source coordinate reference system of the first step and the target coordinate reference system of the last step are the source and target coordinate reference system associated with the concatenated operation. Instead of a forward operation, an inverse operation may be used for one or more of the operation steps mentioned above, if the inverse operation is uniquely defined by the forward operation. +The gml:coordOperation property elements are an ordered sequence of associations to the two or more operations used by this concatenated operation. The AggregationAttributeGroup should be used to specify that the coordOperation associations are ordered. + + + + + + + + + + + + + gml:coordOperation is an association role to a coordinate operation. + + + + + gml:ConcatenatedOperationPropertyType is a property type for association roles to a concatenated operation, either referencing or containing the definition of that concatenated operation. + + + + + + + + + gml:PassThroughOperation is a pass-through operation specifies that a subset of a coordinate tuple is subject to a specific coordinate operation. +The modifiedCoordinate property elements are an ordered sequence of positive integers defining the positions in a coordinate tuple of the coordinates affected by this pass-through operation. The AggregationAttributeGroup should be used to specify that the modifiedCoordinate elements are ordered. + + + + + + + + + + + + + + + + gml:modifiedCoordinate is a positive integer defining a position in a coordinate tuple. + + + + + gml:PassThroughOperationPropertyType is a property type for association roles to a pass through operation, either referencing or containing the definition of that pass through operation. + + + + + + + + + gml:Conversion is a concrete operation on coordinates that does not include any change of Datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters. +This concrete complex type can be used without using a GML Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Conversion instance. +The usesValue property elements are an unordered list of composition associations to the set of parameter values used by this conversion operation. + + + + + + + + + + + + + + + gml:method is an association role to the operation method used by a coordinate operation. + + + + + gml:parameterValue is a composition association to a parameter value or group of parameter values used by a coordinate operation. + + + + + gml:ConversionPropertyType is a property type for association roles to a concrete general-purpose conversion, either referencing or containing the definition of that conversion. + + + + + + + + + gml:Transformation is a concrete object element derived from gml:GeneralTransformation (13.6.2.13). +This concrete object can be used for all operation methods, without using a GML Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Transformation instance. +The parameterValue elements are an unordered list of composition associations to the set of parameter values used by this conversion operation. + + + + + + + + + + + + + + + gml:TransformationPropertyType is a property type for association roles to a transformation, either referencing or containing the definition of that transformation. + + + + + + + + + gml:AbstractGeneralParameterValue is an abstract parameter value or group of parameter values. +This abstract complexType is expected to be extended and restricted for well-known operation methods with many instances, in Application Schemas that define operation-method-specialized element names and contents. Specific parameter value elements are directly contained in concrete subtypes, not in this abstract type. All concrete types derived from this type shall extend this type to include one "...Value" element with an appropriate type, which should be one of the element types allowed in the ParameterValueType. In addition, all derived concrete types shall extend this type to include a "operationParameter" property element that references one element substitutable for the "OperationParameter" object element. + + + + + + + + gml:AbstractGeneralParameterValuePropertyType is a property type for inline association roles to a parameter value or group of parameter values, always containing the values. + + + + + + + + gml:ParameterValue is a parameter value, an ordered sequence of values, or a reference to a file of parameter values. This concrete complex type may be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one instance. This complex type may be used, extended, or restricted for well-known operation methods, especially for methods with many instances. + + + + + + + + + + + + + + + + + + + + + + + + gml:value is a numeric value of an operation parameter, with its associated unit of measure. + + + + + gml:stringValue is a character string value of an operation parameter. A string value does not have an associated unit of measure. + + + + + gml:integerValue is a positive integer value of an operation parameter, usually used for a count. An integer value does not have an associated unit of measure. + + + + + gml:booleanValue is a boolean value of an operation parameter. A Boolean value does not have an associated unit of measure. + + + + + gml:valueList is an ordered sequence of two or more numeric values of an operation parameter list, where each value has the same associated unit of measure. An element of this type contains a space-separated sequence of double values. + + + + + gml:integerValueList is an ordered sequence of two or more integer values of an operation parameter list, usually used for counts. These integer values do not have an associated unit of measure. An element of this type contains a space-separated sequence of integer values. + + + + + gml:valueFile is a reference to a file or a part of a file containing one or more parameter values, each numeric value with its associated unit of measure. When referencing a part of a file, that file shall contain multiple identified parts, such as an XML encoded document. Furthermore, the referenced file or part of a file may reference another part of the same or different files, as allowed in XML documents. + + + + + gml:operationParameter is an association role to the operation parameter of which this is a value. + + + + + gml:ParameterValueGroup is a group of related parameter values. The same group can be repeated more than once in a Conversion, Transformation, or higher level ParameterValueGroup, if those instances contain different values of one or more parameterValues which suitably distinquish among those groups. This concrete complex type can be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents. This complex type may be used, extended, or restricted for well-known operation methods, especially for methods with only one instance. +The parameterValue elements are an unordered set of composition association roles to the parameter values and groups of values included in this group. + + + + + + + + + + + + + + + gml:group is an association role to the operation parameter group for which this element provides parameter values. + + + + + gml:OperationMethod is a method (algorithm or procedure) used to perform a coordinate operation. Most operation methods use a number of operation parameters, although some coordinate conversions use none. Each coordinate operation using the method assigns values to these parameters. +The parameter elements are an unordered list of associations to the set of operation parameters and parameter groups used by this operation method. + + + + + + + + + + + + + + + + + + + + gml:formulaCitation provides a reference to a publication giving the formula(s) or procedure used by an coordinate operation method. + + + + + + + + + + + gml:formula Formula(s) or procedure used by an operation method. The use of the codespace attribite has been deprecated. The property value shall be a character string. + + + + + gml:sourceDimensions is the number of dimensions in the source CRS of this operation method. + + + + + gml:targetDimensions is the number of dimensions in the target CRS of this operation method. + + + + + gml:parameter is an association to an operation parameter or parameter group. + + + + + gml:OperationMethodPropertyType is a property type for association roles to a concrete general-purpose operation method, either referencing or containing the definition of that method. + + + + + + + + + gml:GeneralOperationParameter is the abstract definition of a parameter or group of parameters used by an operation method. + + + + + + + + + + + + + + gml:minimumOccurs is the minimum number of times that values for this parameter group or parameter are required. If this attribute is omitted, the minimum number shall be one. + + + + + gml:AbstractGeneralOperationParameterPropertyType is a property type for association roles to an operation parameter or group, either referencing or containing the definition of that parameter or group. + + + + + + + + + gml:OperationParameter is the definition of a parameter used by an operation method. Most parameter values are numeric, but other types of parameter values are possible. This complex type is expected to be used or extended for all operation methods, without defining operation-method-specialized element names. + + + + + + + + + + + + gml:OperationParameterPropertyType is a property type for association roles to an operation parameter, either referencing or containing the definition of that parameter. + + + + + + + + + gml:OperationParameterGroup is the definition of a group of parameters used by an operation method. This complex type is expected to be used or extended for all applicable operation methods, without defining operation-method-specialized element names. +The generalOperationParameter elements are an unordered list of associations to the set of operation parameters that are members of this group. + + + + + + + + + + + + + + + gml:maximumOccurs is the maximum number of times that values for this parameter group may be included. If this attribute is omitted, the maximum number shall be one. + + + + + gml:OperationParameterPropertyType is a property type for association roles to an operation parameter group, either referencing or containing the definition of that parameter group. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateReferenceSystems.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateReferenceSystems.xsd new file mode 100644 index 0000000..8832344 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateReferenceSystems.xsd @@ -0,0 +1,367 @@ + + + + coordinateReferenceSystems.xsd + See ISO/DIS 19136 13.3. +The spatial-temporal coordinate reference systems schema components are divided into two logical parts. One part defines elements and types for XML encoding of abstract coordinate reference systems definitions. The larger part defines specialized constructs for XML encoding of definitions of the multiple concrete types of spatial-temporal coordinate reference systems. +These schema components encode the Coordinate Reference System packages of the UML Models of ISO 19111 Clause 8 and ISO/DIS 19136 D.3.10, with the exception of the abstract "SC_CRS" class. + + + + + + + gml:AbstractSingleCRS implements a coordinate reference system consisting of one coordinate system and one datum (as opposed to a Compound CRS). + + + + + gml:SingleCRSPropertyType is a property type for association roles to a single coordinate reference system, either referencing or containing the definition of that coordinate reference system. + + + + + + + + + gml:AbstractGeneralDerivedCRS is a coordinate reference system that is defined by its coordinate conversion from another coordinate reference system. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + gml:conversion is an association role to the coordinate conversion used to define the derived CRS. + + + + + gml:CompundCRS is a coordinate reference system describing the position of points through two or more independent coordinate reference systems. It is associated with a non-repeating sequence of two or more instances of SingleCRS. + + + + + + + + + + + + + + + The gml:componentReferenceSystem elements are an ordered sequence of associations to all the component coordinate reference systems included in this compound coordinate reference system. The gml:AggregationAttributeGroup should be used to specify that the gml:componentReferenceSystem properties are ordered. + + + + + gml:CompoundCRSPropertyType is a property type for association roles to a compound coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + + gml:GeodeticCRS is a coordinate reference system based on a geodetic datum. + + + + + + + + + + + + + + + + + gml:ellipsoidalCS is an association role to the ellipsoidal coordinate system used by this CRS. + + + + + gml:cartesianCS is an association role to the Cartesian coordinate system used by this CRS. + + + + + gml:sphericalCS is an association role to the spherical coordinate system used by this CRS. + + + + + gml:geodeticDatum is an association role to the geodetic datum used by this CRS. + + + + + + gml:GeodeticCRSPropertyType is a property type for association roles to a geodetic coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:VerticalCRS is a 1D coordinate reference system used for recording heights or depths. Vertical CRSs make use of the direction of gravity to define the concept of height or depth, but the relationship with gravity may not be straightforward. By implication, ellipsoidal heights (h) cannot be captured in a vertical coordinate reference system. Ellipsoidal heights cannot exist independently, but only as an inseparable part of a 3D coordinate tuple defined in a geographic 3D coordinate reference system. + + + + + + + + + + + + + + + gml:verticalCS is an association role to the vertical coordinate system used by this CRS. + + + + + gml:verticalDatum is an association role to the vertical datum used by this CRS. + + + + + gml:VerticalCRSPropertyType is a property type for association roles to a vertical coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:ProjectedCRS is a 2D coordinate reference system used to approximate the shape of the earth on a planar surface, but in such a way that the distortion that is inherent to the approximation is carefully controlled and known. Distortion correction is commonly applied to calculated bearings and distances to produce values that are a close match to actual field values. + + + + + + + + + + + + + + + + + + gml:baseGeodeticCRS is an association role to the geodetic coordinate reference system used by this projected CRS. + + + + + gml:ProjectedCRSPropertyType is a property type for association roles to a projected coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:DerivedCRS is a single coordinate reference system that is defined by its coordinate conversion from another single coordinate reference system known as the base CRS. The base CRS can be a projected coordinate reference system, if this DerivedCRS is used for a georectified grid coverage as described in ISO 19123, Clause 8. + + + + + + + + + + + + + + + + gml:baseCRS is an association role to the coordinate reference system used by this derived CRS. + + + + + The gml:derivedCRSType property describes the type of a derived coordinate reference system. The required codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + An association role to the coordinate system used by this CRS. + + + + + gml:DerivedCRSPropertyType is a property type for association roles to a non-projected derived coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:EngineeringCRS is a contextually local coordinate reference system which can be divided into two broad categories: +- earth-fixed systems applied to engineering activities on or near the surface of the earth; +- CRSs on moving platforms such as road vehicles, vessels, aircraft, or spacecraft, see ISO 19111 8.3. + + + + + + + + + + + + + + + + + deprecated + + + + + + + + + + + gml:cylindricalCS is an association role to the cylindrical coordinate system used by this CRS. + + + + + gml:linearCS is an association role to the linear coordinate system used by this CRS. + + + + + gml:polarCS is an association role to the polar coordinate system used by this CRS. + + + + + gml:userDefinedCS is an association role to the user defined coordinate system used by this CRS. + + + + + gml:engineeringDatum is an association role to the engineering datum used by this CRS. + + + + + gml:EngineeringCRSPropertyType is a property type for association roles to an engineering coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:ImageCRS is an engineering coordinate reference system applied to locations in images. Image coordinate reference systems are treated as a separate sub-type because the definition of the associated image datum contains two attributes not relevant to other engineering datums. + + + + + + + + + + + + + + + + + + + gml:affineCS is an association role to the affine coordinate system used by this CRS. + + + + + gml:imageDatum is an association role to the image datum used by this CRS. + + + + + gml:ImageCRSPropertyType is a property type for association roles to an image coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:TemporalCRS is a 1D coordinate reference system used for the recording of time. + + + + + + + + + + + + + + + + + + gml:timeCS is an association role to the time coordinate system used by this CRS. + + + + + gml:temporalDatum is an association role to the temporal datum used by this CRS. + + + + + gml:TemporalCRSPropertyType is a property type for association roles to a temporal coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateSystems.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateSystems.xsd new file mode 100644 index 0000000..ced6368 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coordinateSystems.xsd @@ -0,0 +1,291 @@ + + + + coordinateSystems.xsd + See ISO/DIS 19136 13.4. +The coordinate systems schema components can be divded into three logical parts, which define elements and types for XML encoding of the definitions of: +- Coordinate system axes +- Abstract coordinate system +- Multiple concrete types of spatial-temporal coordinate systems +These schema components encode the Coordinate System packages of the UML Models of ISO 19111 Clause 9 and ISO/DIS 19136 D.3.10. + + + + + gml:CoordinateSystemAxis is a definition of a coordinate system axis. + + + + + + + + + + + + + + + The uom attribute provides an identifier of the unit of measure used for this coordinate system axis. The value of this coordinate in a coordinate tuple shall be recorded using this unit of measure, whenever those coordinates use a coordinate reference system that uses a coordinate system that uses this axis. + + + + + + + + gml:axisAbbrev is the abbreviation used for this coordinate system axis; this abbreviation is also used to identify the coordinates in the coordinate tuple. The codeSpace attribute may reference a source of more information on a set of standardized abbreviations, or on this abbreviation. + + + + + gml:axisDirection is the direction of this coordinate system axis (or in the case of Cartesian projected coordinates, the direction of this coordinate system axis at the origin). +Within any set of coordinate system axes, only one of each pair of terms may be used. For earth-fixed CRSs, this direction is often approximate and intended to provide a human interpretable meaning to the axis. When a geodetic datum is used, the precise directions of the axes may therefore vary slightly from this approximate direction. +The codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + The gml:minimumValue and gml:maximumValue properties allow the specification of minimum and maximum value normally allowed for this axis, in the unit of measure for the axis. For a continuous angular axis such as longitude, the values wrap-around at this value. Also, values beyond this minimum/maximum can be used for specified purposes, such as in a bounding box. A value of minus infinity shall be allowed for the gml:minimumValue element, a value of plus infiniy for the gml:maximumValue element. If these elements are omitted, the value is unspecified. + + + + + The gml:minimumValue and gml:maximumValue properties allow the specification of minimum and maximum value normally allowed for this axis, in the unit of measure for the axis. For a continuous angular axis such as longitude, the values wrap-around at this value. Also, values beyond this minimum/maximum can be used for specified purposes, such as in a bounding box. A value of minus infinity shall be allowed for the gml:minimumValue element, a value of plus infiniy for the gml:maximumValue element. If these elements are omitted, the value is unspecified. + + + + + gml:rangeMeaning describes the meaning of axis value range specified by gml:minimumValue and gml:maximumValue. This element shall be omitted when both gml:minimumValue and gml:maximumValue are omitted. This element should be included when gml:minimumValue and/or gml:maximumValue are included. If this element is omitted when the gml:minimumValue and/or gml:maximumValue are included, the meaning is unspecified. The codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + gml:CoordinateSystemAxisPropertyType is a property type for association roles to a coordinate system axis, either referencing or containing the definition of that axis. + + + + + + + + + gml:AbstractCoordinateSystem is a coordinate system (CS) is the non-repeating sequence of coordinate system axes that spans a given coordinate space. A CS is derived from a set of mathematical rules for specifying how coordinates in a given space are to be assigned to points. The coordinate values in a coordinate tuple shall be recorded in the order in which the coordinate system axes associations are recorded. This abstract complex type shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + The gml:axis property is an association role (ordered sequence) to the coordinate system axes included in this coordinate system. The coordinate values in a coordinate tuple shall be recorded in the order in which the coordinate system axes associations are recorded, whenever those coordinates use a coordinate reference system that uses this coordinate system. The gml:AggregationAttributeGroup should be used to specify that the axis objects are ordered. + + + + + gml:CoordinateSystemPropertyType is a property type for association roles to a coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:EllipsoidalCS is a two- or three-dimensional coordinate system in which position is specified by geodetic latitude, geodetic longitude, and (in the three-dimensional case) ellipsoidal height. An EllipsoidalCS shall have two or three gml:axis property elements; the number of associations shall equal the dimension of the CS. + + + + + + + + + + gml:EllipsoidalCSPropertyType is a property type for association roles to an ellipsoidal coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:CartesianCS is a 1-, 2-, or 3-dimensional coordinate system. In the 1-dimensional case, it contains a single straight coordinate axis. In the 2- and 3-dimensional cases gives the position of points relative to orthogonal straight axes. In the multi-dimensional case, all axes shall have the same length unit of measure. A CartesianCS shall have one, two, or three gml:axis property elements. + + + + + + + + + + gml:CartesianCSPropertyType is a property type for association roles to a Cartesian coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:VerticalCS is a one-dimensional coordinate system used to record the heights or depths of points. Such a coordinate system is usually dependent on the Earth's gravity field, perhaps loosely as when atmospheric pressure is the basis for the vertical coordinate system axis. A VerticalCS shall have one gml:axis property element. + + + + + + + + + + gml:VerticalCSPropertyType is a property type for association roles to a vertical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:TimeCS is a one-dimensional coordinate system containing a time axis, used to describe the temporal position of a point in the specified time units from a specified time origin. A TimeCS shall have one gml:axis property element. + + + + + + + + + + gml:TimeCSPropertyType is a property type for association roles to a time coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:LinearCS is a one-dimensional coordinate system that consists of the points that lie on the single axis described. The associated coordinate is the distance – with or without offset – from the specified datum to the point along the axis. A LinearCS shall have one gml:axis property element. + + + + + + + + + + gml:LinearCSPropertyType is a property type for association roles to a linear coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:UserDefinedCS is a two- or three-dimensional coordinate system that consists of any combination of coordinate axes not covered by any other coordinate system type. A UserDefinedCS shall have two or three gml:axis property elements; the number of property elements shall equal the dimension of the CS. + + + + + + + + + + gml:UserDefinedCSPropertyType is a property type for association roles to a user-defined coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:SphericalCS is a three-dimensional coordinate system with one distance measured from the origin and two angular coordinates. A SphericalCS shall have three gml:axis property elements. + + + + + + + + + + gml:SphericalCSPropertyType is property type for association roles to a spherical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:PolarCS ia s two-dimensional coordinate system in which position is specified by the distance from the origin and the angle between the line from the origin to a point and a reference direction. A PolarCS shall have two gml:axis property elements. + + + + + + + + + + gml:PolarCSPropertyType is a property type for association roles to a polar coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:CylindricalCS is a three-dimensional coordinate system consisting of a polar coordinate system extended by a straight coordinate axis perpendicular to the plane spanned by the polar coordinate system. A CylindricalCS shall have three gml:axis property elements. + + + + + + + + + + gml:CylindricalCSPropertyType is a property type for association roles to a cylindrical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:AffineCS is a two- or three-dimensional coordinate system with straight axes that are not necessarily orthogonal. An AffineCS shall have two or three gml:axis property elements; the number of property elements shall equal the dimension of the CS. + + + + + + + + + + gml:AffineCSPropertyType is a property type for association roles to an affine coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coverage.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coverage.xsd new file mode 100644 index 0000000..84679f4 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/coverage.xsd @@ -0,0 +1,287 @@ + + + + coverage.xsd + See ISO/DIS 19136 20.3. +A coverage incorporates a mapping from a spatiotemporal domain to a range set, the latter providing the set in which the attribute values live. The range set may be an arbitrary set including discrete lists, integer or floating point ranges, and multi-dimensional vector spaces. +A coverage can be viewed as the graph of the coverage function f:A à B, that is as the set of ordered pairs {(x, f(x)) | where x is in A}. This view is especially applicable to the GML encoding of a coverage. In the case of a discrete coverage, the domain set A is partitioned into a collection of subsets (typically a disjoint collection) A = UAi and the function f is constant on each Ai. For a spatial domain, the Ai are geometry elements, hence the coverage can be viewed as a collection of (geometry,value) pairs, where the value is an element of the range set. If the spatial domain A is a topological space then the coverage can be viewed as a collection of (topology,value) pairs, where the topology element in the pair is a topological n-chain (in GML terms this is a gml:TopoPoint, gml:TopoCurve, gml:TopoSurface or gml:TopoSolid). +A coverage is implemented as a GML feature. We can thus speak of a “temperature distribution feature”, or a “remotely sensed image feature”, or a “soil distribution feature”. +As is the case for any GML object, a coverage object may also be the value of a property of a feature. + + + + + + + + + The base type for coverages is gml:AbstractCoverageType. The basic elements of a coverage can be seen in this content model: the coverage contains gml:domainSet and gml:rangeSet properties. The gml:domainSet property describes the domain of the coverage and the gml:rangeSet property describes the range of the coverage. + + + + + + + + + + + + + This element serves as the head of a substitution group which may contain any coverage whose type is derived from gml:AbstractCoverageType. It may act as a variable in the definition of content models where it is required to permit any coverage to be valid. + + + + + + + + + + + + + + A discrete coverage consists of a domain set, range set and optionally a coverage function. The domain set consists of either spatial or temporal geometry objects, finite in number. The range set is comprised of a finite number of attribute values each of which is associated to every direct position within any single spatiotemporal object in the domain. In other words, the range values are constant on each spatiotemporal object in the domain. This coverage function maps each element from the coverage domain to an element in its range. The coverageFunction element describes the mapping function. +This element serves as the head of a substitution group which may contain any discrete coverage whose type is derived from gml:DiscreteCoverageType. + + + + + + + + + + + + + + A continuous coverage as defined in ISO 19123 is a coverage that can return different values for the same feature attribute at different direct positions within a single spatiotemporal object in its spatiotemporal domain. The base type for continuous coverages is AbstractContinuousCoverageType. +The coverageFunction element describes the mapping function. +The abstract element gml:AbstractContinuousCoverage serves as the head of a substitution group which may contain any continuous coverage whose type is derived from gml:AbstractContinuousCoverageType. + + + + + The gml:domainSet property element describes the spatio-temporal region of interest, within which the coverage is defined. Its content model is given by gml:DomainSetType. +The value of the domain is thus a choice between a gml:AbstractGeometry and a gml:AbstractTimeObject. In the instance these abstract elements will normally be substituted by a geometry complex or temporal complex, to represent spatial coverages and time-series, respectively. +The presence of the gml:AssociationAttributeGroup means that domainSet follows the usual GML property model and may use the xlink:href attribute to point to the domain, as an alternative to describing the domain inline. Ownership semantics may be provided using the gml:OwnershipAttributeGroup. + + + + + + + + + + + + + + + + The gml:rangeSet property element contains the values of the coverage (sometimes called the attribute values). Its content model is given by gml:RangeSetType. +This content model supports a structural description of the range. The semantic information describing the range set is embedded using a uniform method, as part of the explicit values, or as a template value accompanying the representation using gml:DataBlock and gml:File. +The values from each component (or “band”) in the range may be encoded within a gml:ValueArray element or a concrete member of the gml:AbstractScalarValueList substitution group . Use of these elements satisfies the value-type homogeneity requirement. + + + + + + + + + + + + + gml:DataBlock describes the Range as a block of text encoded values similar to a Common Separated Value (CSV) representation. +The range set parameterization is described by the property gml:rangeParameters. + + + + + + + + + + + + + + + gml:CoordinatesType consists of a list of coordinate tuples, with each coordinate tuple separated by the ts or tuple separator (whitespace), and each coordinate in the tuple by the cs or coordinate separator (comma). +The gml:tupleList encoding is effectively “band-interleaved”. + + + + + gml:doubleOrNilReasonList consists of a list of gml:doubleOrNilReason values, each separated by a whitespace. The gml:doubleOrNilReason values are grouped into tuples where the dimension of each tuple in the list is equal to the number of range parameters. + + + + + for efficiency reasons, GML also provides a means of encoding the range set in an arbitrary external encoding, such as a binary file. This encoding may be “well-known” but this is not required. This mode uses the gml:File element. +The values of the coverage (attribute values in the range set) are transmitted in a external file that is referenced from the XML structure described by gml:FileType. The external file is referenced by the gml:fileReference property that is an anyURI (the gml:fileName property has been deprecated). This means that the external file may be located remotely from the referencing GML instance. +The gml:compression property points to a definition of a compression algorithm through an anyURI. This may be a retrievable, computable definition or simply a reference to an unambiguous name for the compression method. +The gml:mimeType property points to a definition of the file mime type. +The gml:fileStructure property is defined by a codelist. Note further that all values shall be enclosed in a single file. Multi-file structures for values are not supported in GML. +The semantics of the range set is described as above using the gml:rangeParameters property. +Note that if any compression algorithm is applied, the structure above applies only to the pre-compression or post-decompression structure of the file. +Note that the fields within a record match the gml:valueComponents of the gml:CompositeValue in document order. + + + + + + + + + deprecated + + + + + + + + + + + + The gml:coverageFunction property describes the mapping function from the domain to the range of the coverage. +The value of the CoverageFunction is one of gml:CoverageMappingRule and gml:GridFunction. +If the gml:coverageFunction property is omitted for a gridded coverage (including rectified gridded coverages) the gml:startPoint is assumed to be the value of the gml:low property in the gml:Grid geometry, and the gml:sequenceRule is assumed to be linear and the gml:axisOrder property is assumed to be “+1 +2”. + + + + + + + + + + + + gml:CoverageMappingRule provides a formal or informal description of the coverage function. +The mapping rule may be defined as an in-line string (gml:ruleDefinition) or via a remote reference through xlink:href (gml:ruleReference). +If no rule name is specified, the default is ‘Linear’ with respect to members of the domain in document order. + + + + + + + + + + + gml:GridFunction provides an explicit mapping rule for grid geometries, i.e. the domain shall be a geometry of type grid. It describes the mapping of grid posts (discrete point grid coverage) or grid cells (discrete surface coverage) to the values in the range set. +The gml:startPoint is the index position of a point in the grid that is mapped to the first point in the range set (this is also the index position of the first grid post). If the gml:startPoint property is omitted the gml:startPoint is assumed to be equal to the value of gml:low in the gml:Grid geometry. Subsequent points in the mapping are determined by the value of the gml:sequenceRule. + + + + + + + + + + + The gml:SequenceRuleType is derived from the gml:SequenceRuleEnumeration through the addition of an axisOrder attribute. The gml:SequenceRuleEnumeration is an enumerated type. The rule names are defined in ISO 19123. If no rule name is specified the default is “Linear”. + + + + + + deprecated + + + + + + + + + + + + + + + + + + + The different values in a gml:AxisDirectionList indicate the incrementation order to be used on all axes of the grid. Each axis shall be mentioned once and only once. + + + + + + The value of a gml:AxisDirection indicates the incrementation order to be used on an axis of the grid. + + + + + + + + In a gml:MultiPointCoverage the domain set is a gml:MultiPoint, that is a collection of arbitrarily distributed geometric points. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiPoint. +In a gml:MultiPointCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the points of the gml:MultiPoint are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the points of the gml:MultiPoint are mapped to the members of the composite value in document order. +- For gml:File encodings the points of the gml:MultiPoint are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiCurveCoverage the domain is partioned into a collection of curves comprising a gml:MultiCurve. The coverage function then maps each curve in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiCurve. +In a gml:MultiCurveCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the curves of the gml:MultiCurve are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the curves of the gml:MultiCurve are mapped to the members of the composite value in document order. +- For gml:File encodings the curves of the gml:MultiCurve are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiSurfaceCoverage the domain is partioned into a collection of surfaces comprising a gml:MultiSurface. The coverage function than maps each surface in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiSurface. +In a gml:MultiSurfaceCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the surfaces of the gml:MultiSurface are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the surfaces of the gml:MultiSurface are mapped to the members of the composite value in document order. +- For gml:File encodings the surfaces of the gml:MultiSurface are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiSolidCoverage the domain is partioned into a collection of solids comprising a gml:MultiSolid. The coverage function than maps each solid in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiSolid. +In a gml:MultiSolidCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the solids of the gml:MultiSolid are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the solids of the gml:MultiSolid are mapped to the members of the composite value in document order. +- For gml:File encodings the solids of the gml:MultiSolid are mapped to the records of the file in sequential order. + + + + + + A gml:GriddedCoverage is a discrete point coverage in which the domain set is a geometric grid of points. +Note that this is the same as the gml:MultiPointCoverage except that we have a gml:Grid to describe the domain. +The simple gridded coverage is not geometrically referenced and hence no geometric positions are assignable to the points in the grid. Such geometric positioning is introduced in the gml:RectifiedGridCoverage. + + + + + The gml:RectifiedGridCoverage is a discrete point coverage based on a rectified grid. It is similar to the grid coverage except that the points of the grid are geometrically referenced. The rectified grid coverage has a domain that is a gml:RectifiedGrid geometry. + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/datums.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/datums.xsd new file mode 100644 index 0000000..bf0103e --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/datums.xsd @@ -0,0 +1,281 @@ + + + + + datums.xsd + See ISO/DIS 19136 13.5 +The datums schema components can be divided into three logical parts, which define elements and types for XML encoding of the definitions of: +- Abstract datum +- Geodetic datums, including ellipsoid and prime meridian +- Multiple other concrete types of spatial or temporal datums +These schema components encode the Datum packages of the UML Models of ISO 19111 Clause 10 and ISO/DIS 19136 D.3.10. + + + + + + A gml:AbstractDatum specifies the relationship of a coordinate system to the earth, thus creating a coordinate reference system. A datum uses a parameter or set of parameters that determine the location of the origin of the coordinate reference system. Each datum subtype may be associated with only specific types of coordinate systems. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + + + gml:anchorDefinition is a description, possibly including coordinates, of the definition used to anchor the datum to the Earth. Also known as the "origin", especially for engineering and image datums. The codeSpace attribute may be used to reference a source of more detailed on this point or surface, or on a set of such descriptions. +- For a geodetic datum, this point is also known as the fundamental point, which is traditionally the point where the relationship between geoid and ellipsoid is defined. In some cases, the "fundamental point" may consist of a number of points. In those cases, the parameters defining the geoid/ellipsoid relationship have been averaged for these points, and the averages adopted as the datum definition. +- For an engineering datum, the anchor definition may be a physical point, or it may be a point with defined coordinates in another CRS.may +- For an image datum, the anchor definition is usually either the centre of the image or the corner of the image. +- For a temporal datum, this attribute is not defined. Instead of the anchor definition, a temporal datum carries a separate time origin of type DateTime. + + + + + gml:realizationEpoch is the time after which this datum definition is valid. See ISO 19111 Table 32 for details. + + + + + gml:DatumPropertyType is a property type for association roles to a datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:GeodeticDatum is a geodetic datum defines the precise location and orientation in 3-dimensional space of a defined ellipsoid (or sphere), or of a Cartesian coordinate system centered in this ellipsoid (or sphere). + + + + + + + + + + + + + + + gml:primeMeridian is an association role to the prime meridian used by this geodetic datum. + + + + + gml:ellipsoid is an association role to the ellipsoid used by this geodetic datum. + + + + + gml:GeodeticDatumPropertyType is a property type for association roles to a geodetic datum, either referencing or containing the definition of that datum. + + + + + + + + + A gml:Ellipsoid is a geometric figure that may be used to describe the approximate shape of the earth. In mathematical terms, it is a surface formed by the rotation of an ellipse about its minor axis. + + + + + + + + + + + + + + + gml:semiMajorAxis specifies the length of the semi-major axis of the ellipsoid, with its units. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a length, such as metres or feet. + + + + + gml:secondDefiningParameter is a property containing the definition of the second parameter that defines the shape of an ellipsoid. An ellipsoid requires two defining parameters: semi-major axis and inverse flattening or semi-major axis and semi-minor axis. When the reference body is a sphere rather than an ellipsoid, only a single defining parameter is required, namely the radius of the sphere; in that case, the semi-major axis "degenerates" into the radius of the sphere. +The inverseFlattening element contains the inverse flattening value of the ellipsoid. This value is a scale factor (or ratio). It uses gml:LengthType with the restriction that the unit of measure referenced by the uom attribute must be suitable for a scale factor, such as percent, permil, or parts-per-million. +The semiMinorAxis element contains the length of the semi-minor axis of the ellipsoid. When the isSphere element is included, the ellipsoid is degenerate and is actually a sphere. The sphere is completely defined by the semi-major axis, which is the radius of the sphere. + + + + + + + + + + + + + + + + + + + gml:EllipsoidPropertyType is a property type for association roles to an ellipsoid, either referencing or containing the definition of that ellipsoid. + + + + + + + + + A gml:PrimeMeridian defines the origin from which longitude values are determined. The default value for the prime meridian gml:identifier value is "Greenwich". + + + + + + + + + + + + + + gml:greenwichLongitude is the longitude of the prime meridian measured from the Greenwich meridian, positive eastward. If the value of the prime meridian “name” is "Greenwich" then the value of greenwichLongitude shall be 0 degrees. + + + + + gml:PrimeMeridianPropertyType is a property type for association roles to a prime meridian, either referencing or containing the definition of that meridian. + + + + + + + + + gml:EngineeringDatum defines the origin of an engineering coordinate reference system, and is used in a region around that origin. This origin may be fixed with respect to the earth (such as a defined point at a construction site), or be a defined point on a moving vehicle (such as on a ship or satellite). + + + + + + + + + + gml:EngineeringDatumPropertyType is a property type for association roles to an engineering datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:ImageDatum defines the origin of an image coordinate reference system, and is used in a local context only. For an image datum, the anchor definition is usually either the centre of the image or the corner of the image. For more information, see ISO 19111 B.3.5. + + + + + + + + + + + + + + gml:pixelInCell is a specification of the way an image grid is associated with the image data attributes. The required codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + gml:ImageDatumPropertyType is a property type for association roles to an image datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:VerticalDatum is a textual description and/or a set of parameters identifying a particular reference level surface used as a zero-height surface, including its position with respect to the Earth for any of the height types recognized by this International Standard. + + + + + + + + + + gml:VerticalDatumPropertyType is property type for association roles to a vertical datum, either referencing or containing the definition of that datum. + + + + + + + + + A gml:TemporalDatum defines the origin of a Temporal Reference System. This type omits the "anchorDefinition" and "realizationEpoch" elements and adds the "origin" element with the dateTime type. + + + + + + + + + + + + + + The TemporalDatumBaseType partially defines the origin of a temporal coordinate reference system. This type restricts the AbstractDatumType to remove the "anchorDefinition" and "realizationEpoch" elements. + + + + + + + + + + + + + + + + + + + + gml:origin is the date and time origin of this temporal datum. + + + + + gml:TemporalDatumPropertyType is a property type for association roles to a temporal datum, either referencing or containing the definition of that datum. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/defaultStyle.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/defaultStyle.xsd new file mode 100644 index 0000000..0b17712 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/defaultStyle.xsd @@ -0,0 +1,447 @@ + + + + defaultStyle.xsd + + + + + + + + Top-level property. Used in application schemas to "attach" the styling information to GML data. The link between the data and the style should be established through this property only. + + + + + + [complexType of] Top-level property. Used in application schemas to "attach" the styling information to GML data. The link between the data and the style should be established through this property only. + + + + + + + + + + + The value of the top-level property. It is an abstract element. Used as the head element of the substitution group for extensibility purposes. + + + + + + [complexType of] The value of the top-level property. It is an abstract element. Used as the head element of the substitution group for extensibility purposes. + + + + + + + + + Predefined concrete value of the top-level property. Encapsulates all other styling information. + + + + + + [complexType of] Predefined concrete value of the top-level property. Encapsulates all other styling information. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for features. + + + + + + [complexType of] The style descriptor for features. + + + + + + + + + + + + + + + + + + + Used to specify the grammar of the feature query mechanism. + + + + + + + + + + + Base complex type for geometry, topology, label and graph styles. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for geometries of a feature. + + + + + + [complexType of] The style descriptor for geometries of a feature. + + + + + + + + + deprecated + Deprecated in GML version 3.1.0. Use symbol with inline content instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for topologies of a feature. Describes individual topology elements styles. + + + + + + [complexType of] The style descriptor for topologies of a feature. Describes individual topology elements styles. + + + + + + + + + deprecated + Deprecated in GML version 3.1.0. Use symbol with inline content instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for labels of a feature, geometry or topology. + + + + + + [complexType of] The style descriptor for labels of a feature, geometry or topology. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for a graph consisting of a number of features. Describes graph-specific style attributes. + + + + + + [complexType of] The style descriptor for a graph consisting of a number of features. Describes graph-specific style attributes. + + + + + + + + + + + + + + + + + + + + + The symbol property. Extends the gml:AssociationType to allow for remote referencing of symbols. + + + + + + [complexType of] The symbol property. Allows for remote referencing of symbols. + + + + + + + + + + + + + Used to specify the type of the symbol used. + + + + + + + + + + + Label is mixed -- composed of text and XPath expressions used to extract the useful information from the feature. + + + + + + + + + + Defines the geometric transformation of entities. There is no particular grammar defined for this value. + + + + + + Used to vary individual graphic parameters and attributes of the style, symbol or text. + + + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/deprecatedTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/deprecatedTypes.xsd new file mode 100644 index 0000000..b334e73 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/deprecatedTypes.xsd @@ -0,0 +1,1128 @@ + + + + deprecatedTypes.xsd + All global schema components that are part of the GML schema, but were deprecated. See Annex I. + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dictionary.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dictionary.xsd new file mode 100644 index 0000000..53e3479 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dictionary.xsd @@ -0,0 +1,84 @@ + + + + dictionary.xsd + See ISO/DIS 19136 Clause 16. +Many applications require definitions of terms which are used within instance documents as the values of certain properties or as reference information to tie properties to standard information values in some way. Units of measure and descriptions of measurable phenomena are two particular examples. +It will often be convenient to use definitions provided by external authorities. These may already be packaged for delivery in various ways, both online and offline. In order that they may be referred to from GML documents it is generally necessary that a URI be available for each definition. Where this is the case then it is usually preferable to refer to these directly. +Alternatively, it may be convenient or necessary to capture definitions in XML, either embedded within an instance document containing features or as a separate document. The definitions may be transcriptions from an external source, or may be new definitions for a local purpose. In order to support this case, some simple components are provided in GML in the form of +- a generic gml:Definition, which may serve as the basis for more specialized definitions +- a generic gml:Dictionary, which allows a set of definitions or references to definitions to be collected +These components may be used directly, but also serve as the basis for more specialised definition elements in GML, in particular: coordinate operations, coordinate reference systems, datums, temporal reference systems, and units of measure. +Note that the GML definition and dictionary components implement a simple nested hierarchy of definitions with identifiers. The latter provide handles which may be used in the description of more complex relationships between terms. However, the GML dictionary components are not intended to provide direct support for complex taxonomies, ontologies or thesauri. Specialised XML tools are available to satisfy the more sophisticated requirements. + + + + + The basic gml:Definition element specifies a definition, which can be included in or referenced by a dictionary. +The content model for a generic definition is a derivation from gml:AbstractGMLType. +The gml:description property element shall hold the definition if this can be captured in a simple text string, or the gml:descriptionReference property element may carry a link to a description elsewhere. +The gml:identifier element shall provide one identifier identifying this definition. The identifier shall be unique within the dictionaries using this definition. +The gml:name elements shall provide zero or more terms and synonyms for which this is the definition. +The gml:remarks element shall be used to hold additional textual information that is not conceptually part of the definition but is useful in understanding the definition. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Sets of definitions may be collected into dictionaries or collections. +A gml:Dictionary is a non-abstract collection of definitions. +The gml:Dictionary content model adds a list of gml:dictionaryEntry properties that contain or reference gml:Definition objects. A database handle (gml:id attribute) is required, in order that this collection may be referred to. The standard gml:identifier, gml:description, gml:descriptionReference and gml:name properties are available to reference or contain more information about this dictionary. The gml:description and gml:descriptionReference property elements may be used for a description of this dictionary. The derived gml:name element may be used for the name(s) of this dictionary. for remote definiton references gml:dictionaryEntry shall be used. If a Definition object contained within a Dictionary uses the descriptionReference property to refer to a remote definition, then this enables the inclusion of a remote definition in a local dictionary, giving a handle and identifier in the context of the local dictionary. + + + + + + + + + + + + + + + + This property element contains or refers to the definitions which are members of a dictionary. +The content model follows the standard GML property pattern, so a gml:dictionaryEntry may either contain or refer to a single gml:Definition. Since gml:Dictionary is substitutable for gml:Definition, the content of an entry may itself be a lower level dictionary. +Note that if the value is provided by reference, this definition does not carry a handle (gml:id) in this context, so does not allow external references to this specific definition in this context. When used in this way the referenced definition will usually be in a dictionary in the same XML document. + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/direction.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/direction.xsd new file mode 100644 index 0000000..fbfc714 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/direction.xsd @@ -0,0 +1,78 @@ + + + + direction.xsd + See ISO/DIS 19136 Clause 18. +The direction schema components provide the GML Application Schema developer with a standard property element to describe direction, and associated objects that may be used to express orientation, direction, heading, bearing or other directional aspects of geographic features. + + + + + The property gml:direction is intended as a pre-defined property expressing a direction to be assigned to features defined in a GML application schema. + + + + + + + + + + + + + + + + Direction vectors are specified by providing components of a vector. + + + + + + deprecated + + + + + + + + + direction descriptions are specified by a compass point code, a keyword, a textual description or a reference to a description. +A gml:compassPoint is specified by a simple enumeration. +In addition, thre elements to contain text-based descriptions of direction are provided. +If the direction is specified using a term from a list, gml:keyword should be used, and the list indicated using the value of the codeSpace attribute. +if the direction is decribed in prose, gml:direction or gml:reference should be used, allowing the value to be included inline or by reference. + + + + + + + + + + + These directions are necessarily approximate, giving direction with a precision of 22.5°. It is thus generally unnecessary to specify the reference frame, though this may be detailed in the definition of a GML application language. + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dynamicFeature.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dynamicFeature.xsd new file mode 100644 index 0000000..54ff921 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/dynamicFeature.xsd @@ -0,0 +1 @@ + dynamicFeature.xsd See ISO/DIS 19136 15.6. A number of types and relationships are defined to represent the time-varying properties of geographic features. In a comprehensive treatment of spatiotemporal modeling, Langran (see Bibliography) distinguished three principal temporal entities: states, events, and evidence; the schema specified in the following Subclauses incorporates elements for each. Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data. The remote link attributes of the gml:dataSource element have been deprecated along with its current type. Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data. A convenience group. This allows an application schema developer to include dynamic properties in a content model in a standard fashion. States are captured by time-stamped instances of a feature. The content model extends the standard gml:AbstractFeatureType with the gml:dynamicProperties model group. Each time-stamped instance represents a ‘snapshot’ of a feature. The dynamic feature classes will normally be extended to suit particular applications. A dynamic feature bears either a time stamp or a history. A gml:DynamicFeatureCollection is a feature collection that has a gml:validTime property (i.e. is a snapshot of the feature collection) or which has a gml:history property that contains one or more gml:AbstractTimeSlices each of which contain values of the time varying properties of the feature collection. Note that the gml:DynamicFeatureCollection may be one of the following: 1. A feature collection which consists of static feature members (members do not change in time) but which has properties of the collection object as a whole that do change in time . 2. A feature collection which consists of dynamic feature members (the members are gml:DynamicFeatures) but which also has properties of the collection as a whole that vary in time. To describe an event — an action that occurs at an instant or over an interval of time — GML provides the gml:AbtractTimeSlice element. A timeslice encapsulates the time-varying properties of a dynamic feature -- it shall be extended to represent a time stamped projection of a specific feature. The gml:dataSource property describes how the temporal data was acquired. A gml:AbstractTimeSlice instance is a GML object that encapsulates updates of the dynamic—or volatile—properties that reflect some change event; it thus includes only those feature properties that have actually changed due to some process. gml:AbstractTimeSlice basically provides a facility for attribute-level time stamping, in contrast to the object-level time stamping of dynamic feature instances. The time slice can thus be viewed as event or process-oriented, whereas a snapshot is more state or structure-oriented. A timeslice has richer causality, whereas a snapshot merely portrays the status of the whole. A generic sequence of events constitute a gml:history of an object. The gml:history element contains a set of elements in the substitution group headed by the abstract element gml:AbstractTimeSlice, representing the time-varying properties of interest. The history property of a dynamic feature associates a feature instance with a sequence of time slices (i.e. change events) that encapsulate the evolution of the feature. \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/feature.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/feature.xsd new file mode 100644 index 0000000..877ce73 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/feature.xsd @@ -0,0 +1 @@ + feature.xsd See ISO/DIS 19136 Clause 9. A GML feature is a (representation of a) identifiable real-world object in a selected domain of discourse. The feature schema provides a framework for the creation of GML features and feature collections. The basic feature model is given by the gml:AbstractFeatureType. The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. The value of the gml:location property describes the extent, position or relative location of the feature. This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. gml:AbstractFeature may be thought of as “anything that is a GML feature” and may be used to define variables or templates in which the value of a GML property is “any feature”. This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. This property describes the minimum bounding box or rectangle that encloses the entire feature. gml:EnvelopeWithTimePeriod is provided for envelopes that include a temporal extent. It adds two time position properties, gml:beginPosition and gml:endPosition, which describe the extent of a time-envelope. Since gml:EnvelopeWithTimePeriod is assigned to the substitution group headed by gml:Envelope, it may be used whenever gml:Envelope is valid. The gml:locationName property element is a convenience property where the text value describes the location of the feature. If the location names are selected from a controlled list, then the list shall be identified in the codeSpace attribute. The gml:locationReference property element is a convenience property where the text value referenced by the xlink:href attribute describes the location of the feature. To create a collection of GML features, a property type shall be derived by extension from gml:AbstractFeatureMemberType. By default, this abstract property type does not imply any ownership of the features in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of a feature in the collection. A collection shall not own a feature already owned by another object. \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryAggregates.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryAggregates.xsd new file mode 100644 index 0000000..98f05f4 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryAggregates.xsd @@ -0,0 +1,191 @@ + + + + geometryAggregates.xsd + See ISO/DIS 19136 12.3. +Geometric aggregates (i.e. instances of a subtype of gml:AbstractGeometricAggregateType) are arbitrary aggregations of geometry elements. They are not assumed to have any additional internal structure and are used to "collect" pieces of geometry of a specified type. Application schemas may use aggregates for features that use multiple geometric objects in their representations. + + + + + + + + + + + + gml:AbstractGeometricAggregate is the abstract head of the substitution group for all geometric aggregates. + + + + + + + + + + + + + + + gml:MultiGeometry is a collection of one or more GML geometry objects of arbitrary type. +The members of the geometric aggregate may be specified either using the "standard" property (gml:geometryMember) or the array property (gml:geometryMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a geometry element via the XLink-attributes or contains the geometry element. + + + + + This property element contains a list of geometry elements. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a geometric aggregate as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiPoint consists of one or more gml:Points. +The members of the geometric aggregate may be specified either using the "standard" property (gml:pointMember) or the array property (gml:pointMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a Point via the XLink-attributes or contains the Point element. + + + + + This property element contains a list of points. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of points as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiCurve is defined by one or more gml:AbstractCurves. +The members of the geometric aggregate may be specified either using the "standard" property (gml:curveMember) or the array property (gml:curveMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element contains a list of curves. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of curves as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiSurface is defined by one or more gml:AbstractSurfaces. +The members of the geometric aggregate may be specified either using the "standard" property (gml:surfaceMember) or the array property (gml:surfaceMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element contains a list of surfaces. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of surfaces as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiSolid is defined by one or more gml:AbstractSolids. +The members of the geometric aggregate may be specified either using the "standard" property (gml:solidMember) or the array property (gml:solidMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a solid via the XLink-attributes or contains the solid element. A solid element is any element, which is substitutable for gml:AbstractSolid. + + + + + This property element contains a list of solids. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of solids as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic0d1d.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic0d1d.xsd new file mode 100644 index 0000000..feec59b --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic0d1d.xsd @@ -0,0 +1 @@ + geometryBasic0d1d.xsd See ISO/DIS 19136 Clause 10. Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. The geometry model distinguishes geometric primitives, aggregates and complexes. Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). The following rules shall be adhered to: - Every geometry type shall derive from this abstract type. - Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). pos elements are positions that are “owned” by the geometric primitive encapsulating this geometric position. pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. For some applications the components of the position may be adjusted to yield a unit vector. deprecated Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). The use of the properties “coordinates” and “pos” has been deprecated. The explicitly named properties “lowerCorner” and “upperCorner” shall be used instead. gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic2d.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic2d.xsd new file mode 100644 index 0000000..32deb9d --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryBasic2d.xsd @@ -0,0 +1,118 @@ + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substituition group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryComplexes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryComplexes.xsd new file mode 100644 index 0000000..30fda63 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryComplexes.xsd @@ -0,0 +1,89 @@ + + + + geometryComplexes.xsd + See ISO/DIS 19136 12.2. +Geometric complexes (i.e. instances of gml:GeometricComplexType) are closed collections of geometric primitives, i.e. they will contain their boundaries. +A geometric complex (gml:GeometricComplex) is defined by ISO 19107:2003, 6.6.1 as “a set of primitive geometric objects (in a common coordinate system) whose interiors are disjoint. Further, if a primitive is in a geometric complex, then there exists a set of primitives in that complex whose point-wise union is the boundary of this first primitive.” +A geometric composite (gml:CompositeCurve, gml:CompositeSurface and gml:CompositeSolid) represents a geometric complex with an underlying core geometry that is isomorphic to a primitive, i.e. it can be viewed as a primitive and as a complex. See ISO 19107:2003, 6.1 and 6.6.3 for more details on the nature of composite geometries. +Geometric complexes and composites are intended to be used in application schemas where the sharing of geometry is important. + + + + + + + + + + + + + + + + A property that has a geometric complex as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + + + + + A gml:CompositeCurve is represented by a sequence of (orientable) curves such that each curve in the sequence terminates at the start point of the subsequent curve in the list. +curveMember references or contains inline one curve in the composite curve. +The curves are contiguous, the collection of curves is ordered. Therefore, if provided, the aggregationType attribute shall have the value “sequence”. + + + + + + + + + + + + + + + A gml:CompositeSurface is represented by a set of orientable surfaces. It is geometry type with all the geometric properties of a (primitive) surface. Essentially, a composite surface is a collection of surfaces that join in pairs on common boundary curves and which, when considered as a whole, form a single surface. +surfaceMember references or contains inline one surface in the composite surface. +The surfaces are contiguous. + + + + + + + + + + + + + + + gml:CompositeSolid implements ISO 19107 GM_CompositeSolid (see ISO 19107:2003, 6.6.7) as specified in D.2.3.6. +A gml:CompositeSolid is represented by a set of orientable surfaces. It is a geometry type with all the geometric properties of a (primitive) solid. Essentially, a composite solid is a collection of solids that join in pairs on common boundary surfaces and which, when considered as a whole, form a single solid. +solidMember references or contains one solid in the composite solid. The solids are contiguous. + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryPrimitives.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryPrimitives.xsd new file mode 100644 index 0000000..d6126c4 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/geometryPrimitives.xsd @@ -0,0 +1,841 @@ + + + + geometryPrimitives.xsd + See ISO/DIS 19136 Clause 11. +Beside the “simple” geometric primitives specified in the previous Clause, this Clause specifies additional primitives to describe real world situations which require a more expressive geometry model. + + + + + + + + + + + + + + + A curve is a 1-dimensional primitive. Curves are continuous, connected, and have a measurable length in terms of the coordinate system. +A curve is composed of one or more curve segments. Each curve segment within a curve may be defined using a different interpolation method. The curve segments are connected to one another, with the end point of each segment except the last being the start point of the next segment in the segment list. +The orientation of the curve is positive. +The element segments encapsulates the segments of the curve. + + + + + + + + + + + + + + + The property baseCurve references or contains the base curve, i.e. it either references the base curve via the XLink-attributes or contains the curve element. A curve element is any element which is substitutable for AbstractCurve. The base curve has positive orientation. + + + + + OrientableCurve consists of a curve and an orientation. If the orientation is "+", then the OrientableCurve is identical to the baseCurve. If the orientation is "-", then the OrientableCurve is related to another AbstractCurve with a parameterization that reverses the sense of the curve traversal. + + + + + + + + + + A curve segment defines a homogeneous segment of a curve. +The attributes numDerivativesAtStart, numDerivativesAtEnd and numDerivativesInterior specify the type of continuity as specified in ISO 19107:2003, 6.4.9.3. +The AbstractCurveSegment element is the abstract head of the substituition group for all curve segment elements, i.e. continuous segments of the same interpolation mechanism. +All curve segments shall have an attribute interpolation with type gml:CurveInterpolationType specifying the curve interpolation mechanism used for this segment. This mechanism uses the control points and control parameters to determine the position of this curve segment. + + + + + gml:CurveSegmentArrayPropertyType is a container for an array of curve segments. + + + + + + + + This property element contains a list of curve segments. The order of the elements is significant and shall be preserved when processing the array. + + + + + gml:CurveInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an application schema. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A LineStringSegment is a curve segment that is defined by two or more control points including the start and end point, with linear interpolation between them. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + An ArcString is a curve segment that uses three-point circular arc interpolation (“circularArc3Points”). The number of arcs in the arc string may be explicitly stated in the attribute numArc. The number of control points in the arc string shall be 2 * numArc + 1. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + An Arc is an arc string with only one arc unit, i.e. three control points including the start and end point. As arc is an arc string consisting of a single arc, the attribute “numArc” is fixed to "1". + + + + + + + + + + A Circle is an arc whose ends coincide to form a simple closed loop. The three control points shall be distinct non-co-linear points for the circle to be unambiguously defined. The arc is simply extended past the third control point until the first control point is encountered. + + + + + + + + + + + + + + + + + + + + + + + + + + This variant of the arc computes the mid points of the arcs instead of storing the coordinates directly. The control point sequence consists of the start and end points of each arc plus the bulge (see ISO 19107:2003, 6.4.17.2). The normal is a vector normal (perpendicular) to the chord of the arc (see ISO 19107:2003, 6.4.17.4). +The interpolation is fixed as "circularArc2PointWithBulge". +The number of arcs in the arc string may be explicitly stated in the attribute numArc. The number of control points in the arc string shall be numArc + 1. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + + An ArcByBulge is an arc string with only one arc unit, i.e. two control points, one bulge and one normal vector. +As arc is an arc string consisting of a single arc, the attribute “numArc” is fixed to "1". + + + + + + + + + + + + + + + + + + + + + + + + + + + This variant of the arc requires that the points on the arc shall be computed instead of storing the coordinates directly. The single control point is the center point of the arc plus the radius and the bearing at start and end. This representation can be used only in 2D. +The element radius specifies the radius of the arc. +The element startAngle specifies the bearing of the arc at the start. +The element endAngle specifies the bearing of the arc at the end. +The interpolation is fixed as "circularArcCenterPointWithRadius". +Since this type describes always a single arc, the attribute “numArc” is fixed to "1". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + A gml:CircleByCenterPoint is an gml:ArcByCenterPoint with identical start and end angle to form a full circle. Again, this representation can be used only in 2D. + + + + + + + + + + + + + + + + + + + + + + + + + + The number of control points shall be at least three. +vectorAtStart is the unit tangent vector at the start point of the spline. vectorAtEnd is the unit tangent vector at the end point of the spline. Only the direction of the vectors shall be used to determine the shape of the cubic spline, not their length. +interpolation is fixed as "cubicSpline". +degree shall be the degree of the polynomial used for the interpolation in this spline. Therefore the degree for a cubic spline is fixed to "3". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + + + + A B-Spline is a piecewise parametric polynomial or rational curve described in terms of control points and basis functions as specified in ISO 19107:2003, 6.4.30. Therefore, interpolation may be either "polynomialSpline" or "rationalSpline" depending on the interpolation type; default is "polynomialSpline". +degree shall be the degree of the polynomial used for interpolation in this spline. +knot shall be the sequence of distinct knots used to define the spline basis functions (see ISO 19107:2003, 6.4.26.2). +The attribute isPolynomial shall be set to “true” if this is a polynomial spline (see ISO 19107:2003, 6.4.30.5). +The attribute knotType shall provide the type of knot distribution used in defining this spline (see ISO 19107:2003, 6.4.30.4). +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + gml:KnotPropertyType encapsulates a knot to use it in a geometric type. + + + + + A knot is a breakpoint on a piecewise spline curve. +value is the value of the parameter at the knot of the spline (see ISO 19107:2003, 6.4.24.2). +multiplicity is the multiplicity of this knot used in the definition of the spline (with the same weight). +weight is the value of the averaging weight used for this knot of the spline. + + + + + + + This enumeration type specifies values for the knots’ type (see ISO 19107:2003, 6.4.25). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Bezier curves are polynomial splines that use Bezier or Bernstein polynomials for interpolation purposes. It is a special case of the B-Spline curve with two knots. +degree shall be the degree of the polynomial used for interpolation in this spline. +knot shall be the sequence of distinct knots used to define the spline basis functions. +interpolation is fixed as "polynomialSpline". +isPolynomial is fixed as “true”. +knotType is not relevant for Bezier curve segments. + + + + + + + + + + + + + + + + + An offset curve is a curve at a constant distance from the basis curve. offsetBase is the base curve from which this curve is defined as an offset. distance and refDirection have the same meaning as specified in ISO 19107:2003, 6.4.23. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + location, refDirection, inDimension and outDimension have the same meaning as specified in ISO 19107:2003, 6.4.21. + + + + + + + + + + + + + + + + + + + + + + + + A clothoid, or Cornu's spiral, is plane curve whose curvature is a fixed function of its length. +refLocation, startParameter, endParameter and scaleFactor have the same meaning as specified in ISO 19107:2003, 6.4.22. +interpolation is fixed as "clothoid". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + A sequence of geodesic segments. +The number of control points shall be at least two. +interpolation is fixed as "geodesic". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + A Surface is a 2-dimensional primitive and is composed of one or more surface patches as specified in ISO 19107:2003, 6.3.17.1. The surface patches are connected to one another. +patches encapsulates the patches of the surface. + + + + + + + + + + + + + + + The property baseSurface references or contains the base surface. The property baseSurface either references the base surface via the XLink-attributes or contains the surface element. A surface element is any element which is substitutable for gml:AbstractSurface. The base surface has positive orientation. + + + + + OrientableSurface consists of a surface and an orientation. If the orientation is "+", then the OrientableSurface is identical to the baseSurface. If the orientation is "-", then the OrientableSurface is a reference to a gml:AbstractSurface with an up-normal that reverses the direction for this OrientableSurface, the sense of "the top of the surface". + + + + + + A surface patch defines a homogenuous portion of a surface. +The AbstractSurfacePatch element is the abstract head of the substituition group for all surface patch elements describing a continuous portion of a surface. +All surface patches shall have an attribute interpolation (declared in the types derived from gml:AbstractSurfacePatchType) specifying the interpolation mechanism used for the patch using gml:SurfaceInterpolationType. + + + + + gml:SurfacePatchArrayPropertyType is a container for a sequence of surface patches. + + + + + + + + The patches property element contains the sequence of surface patches. The order of the elements is significant and shall be preserved when processing the array. + + + + + gml:SurfaceInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an application schema. + + + + + + + + + + + + + + + + + + + + + + + + + + + + A gml:PolygonPatch is a surface patch that is defined by a set of boundary curves and an underlying surface to which these curves adhere. The curves shall be coplanar and the polygon uses planar interpolation in its interior. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + gml:Triangle represents a triangle as a surface patch with an outer boundary consisting of a linear ring. Note that this is a polygon (subtype) with no inner boundaries. The number of points in the linear ring shall be four. +The ring (element exterior) shall be a gml:LinearRing and shall form a triangle, the first and the last position shall be coincident. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + gml:Rectangle represents a rectangle as a surface patch with an outer boundary consisting of a linear ring. Note that this is a polygon (subtype) with no inner boundaries. The number of points in the linear ring shall be five. +The ring (element exterior) shall be a gml:LinearRing and shall form a rectangle; the first and the last position shall be coincident. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + A ring is used to represent a single connected component of a surface boundary as specified in ISO 19107:2003, 6.3.6. +Every gml:curveMember references or contains one curve, i.e. any element which is substitutable for gml:AbstractCurve. In the context of a ring, the curves describe the boundary of the surface. The sequence of curves shall be contiguous and connected in a cycle. +If provided, the aggregationType attribute shall have the value “sequence”. + + + + + + A property with the content model of gml:RingPropertyType encapsulates a ring to represent a component of a surface boundary. + + + + + + + + A gml:PointGrid group contains or references points or positions which are organised into sequences or grids. All rows shall have the same number of positions (columns). + + + + + + + + + + + + + + + + + + + + + + + + + The element provides a substitution group head for the surface patches based on parametric curves. All properties are specified in the derived subtypes. All derived subtypes shall conform to the constraints specified in ISO 19107:2003, 6.4.40. +If provided, the aggregationType attribute shall have the value “set”. + + + + + + + + + + + + + + + + if provided, rows gives the number of rows, columns the number of columns in the parameter grid. The parameter grid is represented by an instance of the gml:PointGrid group. +The element provides a substitution group head for the surface patches based on a grid. All derived subtypes shall conform to the constraints specified in ISO 19107:2003, 6.4.41. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A polyhedral surface is a surface composed of polygon patches connected along their common boundary curves. This differs from the surface type only in the restriction on the types of surface patches acceptable. +polygonPatches encapsulates the polygon patches of the polyhedral surface. + + + + + A triangulated surface is a polyhedral surface that is composed only of triangles. There is no restriction on how the triangulation is derived. +trianglePatches encapsulates the triangles of the triangulated surface. + + + + + + + + + + + + + + + + + + + + + + + + A tin is a triangulated surface that uses the Delauny algorithm or a similar algorithm complemented with consideration of stoplines (stopLines), breaklines (breakLines), and maximum length of triangle sides (maxLength). controlPoint shall contain a set of the positions (three or more) used as posts for this TIN (corners of the triangles in the TIN). See ISO 19107:2003, 6.4.39 for details. + + + + + gml:LineStringSegmentArrayPropertyType provides a container for line strings. + + + + + + + + gml:AbstractSolidType is an abstraction of a solid to support the different levels of complexity. The solid may always be viewed as a geometric primitive, i.e. is contiguous. + + + + + + + + The AbstractSolid element is the abstract head of the substituition group for all (continuous) solid elements. + + + + + A property that has a solid as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a solid via the XLink-attributes or contains the solid element. solidProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSolid. + + + + + gml:SolidArrayPropertyType is a container for an array of solids. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements is not supported. + + + + + + + + + + + + + + + + + + + A solid is the basis for 3-dimensional geometry. The extent of a solid is defined by the boundary surfaces as specified in ISO 19107:2003, 6.3.18. exterior specifies the outer boundary, interior the inner boundary of the solid. + + + + + + + + + + + A shell is used to represent a single connected component of a solid boundary as specified in ISO 19107:2003, 6.3.8. +Every gml:surfaceMember references or contains one surface, i.e. any element which is substitutable for gml:AbstractSurface. In the context of a shell, the surfaces describe the boundary of the solid. +If provided, the aggregationType attribute shall have the value “set”. + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. A surface element is any element, which is substitutable for gml:AbstractSurface. + + + + + A property with the content model of gml:ShellPropertyType encapsulates a shell to represent a component of a solid boundary. + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gml.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gml.xsd new file mode 100644 index 0000000..c7f53cd --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gml.xsd @@ -0,0 +1,15 @@ + + + + gml.xsd + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gmlBase.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gmlBase.xsd new file mode 100644 index 0000000..91ce208 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/gmlBase.xsd @@ -0,0 +1,179 @@ + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is “any GML object having identity”. It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to „by-reference only“ (see 7.2.3.7), +- the encoding to „inline only“ (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the “ownership” of the contained or referenced GML Object, i.e. the encoding style shall not imply any “deep-copy” or “deep-delete” semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be “owned”. +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a “by-reference only” encoding. + + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/grids.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/grids.xsd new file mode 100644 index 0000000..560d8cc --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/grids.xsd @@ -0,0 +1,58 @@ + + + + grids.xsd + See ISO/DIS 19136 20.2. +An implicit description of geometry is one in which the items of the geometry do not explicitly appear in the encoding. Instead, a compact notation records a set of parameters, and a set of objects may be generated using a rule with these parameters. This Clause provides grid geometries that are used in the description of gridded coverages and other applications. +In GML two grid structures are defined, namely gml:Grid and gml:RectifiedGrid. + + + + + The gml:Grid implicitly defines an unrectified grid, which is a network composed of two or more sets of curves in which the members of each set intersect the members of the other sets in an algorithmic way. The region of interest within the grid is given in terms of its gml:limits, being the grid coordinates of diagonally opposed corners of a rectangular region. gml:axisLabels is provided with a list of labels of the axes of the grid (gml:axisName has been deprecated). gml:dimension specifies the dimension of the grid. +The gml:limits element contains a single gml:GridEnvelope. The gml:low and gml:high property elements of the envelope are each integerLists, which are coordinate tuples, the coordinates being measured as offsets from the origin of the grid along each axis, of the diagonally opposing corners of a “rectangular” region of interest. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A rectified grid is a grid for which there is an affine transformation between the grid coordinates and the coordinates of an external coordinate reference system. It is defined by specifying the position (in some geometric space) of the grid “origin” and of the vectors that specify the post locations. +Note that the grid limits (post indexes) and axis name properties are inherited from gml:GridType and that gml:RectifiedGrid adds a gml:origin property (contains or references a gml:Point) and a set of gml:offsetVector properties. + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/measures.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/measures.xsd new file mode 100644 index 0000000..16a87ba --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/measures.xsd @@ -0,0 +1,63 @@ + + + + measures.xsd + See ISO/DIS 19136 17.3. +gml:MeasureType is defined in the basicTypes schema. The measure types defined here correspond with a set of convenience measure types described in ISO/TS 19103. The XML implementation is based on the XML Schema simple type “double” which supports both decimal and scientific notation, and includes an XML attribute “uom” which refers to the units of measure for the value. Note that, there is no requirement to store values using any particular format, and applications receiving elements of this type may choose to coerce the data to any other type as convenient. + + + + + + The value of a physical quantity, together with its unit. + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The gml:angle property element is used to record the value of an angle quantity as a single number, with its units. + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/observation.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/observation.xsd new file mode 100644 index 0000000..40667ba --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/observation.xsd @@ -0,0 +1,90 @@ + + + + observation.xsd + See ISO/DIS 19136 Clause 19. +A GML observation models the act of observing, often with a camera, a person or some form of instrument. An observation feature describes the “metadata” associated with an information capture event, together with a value for the result of the observation. This covers a broad range of cases, from a tourist photo (not the photo but the act of taking the photo), to images acquired by space borne sensors or the measurement of a temperature 5 meters below the surfaces of a lake. +The basic structures introduced in this schema are intended to serve as the foundation for more comprehensive schemas for scientific, technical and engineering measurement schemas. + + + + + + + + The content model is a straightforward extension of gml:AbstractFeatureType; it automatically has the gml:identifier, gml:description, gml:descriptionReference, gml:name, and gml:boundedBy properties. +The gml:validTime element describes the time of the observation. Note that this may be a time instant or a time period. +The gml:using property contains or references a description of a sensor, instrument or procedure used for the observation. +The gml:target property contains or references the specimen, region or station which is the object of the observation. This property is particularly useful for remote observations, such as photographs, where a generic location property might apply to the location of the camera or the location of the field of view, and thus may be ambiguous. +The gml:subject element is provided as a convenient synonym for gml:target. This is the term commonly used in phtotography. +The gml:resultOf property indicates the result of the observation. The value may be inline, or a reference to a value elsewhere. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A gml:DirectedObservation is the same as an observation except that it adds an additional gml:direction property. This is the direction in which the observation was acquired. Clearly this applies only to certain types of observations such as visual observations by people, or observations obtained from terrestrial cameras. + + + + + + + + + + + + + + gml:DirectedObservationAtDistance adds an additional distance property. This is the distance from the observer to the subject of the observation. Clearly this applies only to certain types of observations such as visual observations by people, or observations obtained from terrestrial cameras. + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/referenceSystems.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/referenceSystems.xsd new file mode 100644 index 0000000..d1e3b84 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/referenceSystems.xsd @@ -0,0 +1,64 @@ + + + + referenceSystems.xsd + See ISO/DIS 19136 13.2. +The reference systems schema components have two logical parts, which define elements and types for XML encoding of the definitions of: +- Identified Object, inherited by the ten types of GML objects used for coordinate reference systems and coordinate operations +- High-level part of the definitions of coordinate reference systems +This schema encodes the Identified Object and Reference System packages of the UML Model for ISO 19111. + + + + + + gml:IdentifiedObjectType provides identification properties of a CRS-related object. In gml:DefinitionType, the gml:identifier element shall be the primary name by which this object is identified, encoding the "name" attribute in the UML model. +Zero or more of the gml:name elements can be an unordered set of "identifiers", encoding the "identifier" attribute in the UML model. Each of these gml:name elements can reference elsewhere the object's defining information or be an identifier by which this object can be referenced. +Zero or more other gml:name elements can be an unordered set of "alias" alternative names by which this CRS related object is identified, encoding the "alias" attributes in the UML model. An object may have several aliases, typically used in different contexts. The context for an alias is indicated by the value of its (optional) codeSpace attribute. +Any needed version information shall be included in the codeSpace attribute of a gml:identifier and gml:name elements. In this use, the gml:remarks element in the gml:DefinitionType shall contain comments on or information about this object, including data source information. + + + + + + + + gml:AbstractCRS specifies a coordinate reference system which is usually single but may be compound. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + The gml:domainOfValidity property implements an association role to an EX_Extent object as encoded in ISO/TS 19139, either referencing or containing the definition of that extent. + + + + + + + + + + + The gml:scope property provides a description of the usage, or limitations of usage, for which this CRS-related object is valid. If unknown, enter "not known". + + + + + gml:CRSPropertyType is a property type for association roles to a CRS abstract coordinate reference system, either referencing or containing the definition of that CRS. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporal.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporal.xsd new file mode 100644 index 0000000..d45270a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporal.xsd @@ -0,0 +1,263 @@ + + + + temporal.xsd + See ISO/DIS 19136 15.2. +The GML temporal schemas include components for describing temporal geometry and topology, temporal reference systems, and the temporal characteristics of geographic data. The model underlying the representation constitutes a profile of the conceptual schema described in ISO 19108. The underlying spatiotemporal model strives to accommodate both feature-level and attribute-level time stamping; basic support for tracking moving objects is also included. +Time is measured on two types of scales: interval and ordinal. An interval scale offers a basis for measuring duration, an ordinal scale provides information only about relative position in time. +Two other ISO standards are relevant to describing temporal objects: ISO 8601 describes encodings for time instants and time periods, as text strings with particular structure and punctuation; ISO 11404 provides a detailed description of time intervals as part of a general discussion of language independent datatypes. +The temporal schemas cover two interrelated topics and provide basic schema components for representing temporal instants and periods, temporal topology, and reference systems; more specialized schema components defines components used for dynamic features. Instances of temporal geometric types are used as values for the temporal properties of geographic features. + + + + + gml:AbstractTimeObject acts as the head of a substitution group for all temporal primitives and complexes. + + + + + + + + + + gml:AbstractTimePrimitive acts as the head of a substitution group for geometric and topological temporal primitives. + + + + + + + + + + + + + + gml:TimePrimitivePropertyType provides a standard content model for associations between an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive and another object. + + + + + + + + + + gml:validTime is a convenience property element. + + + + + gml:RelatedTimeType provides a content model for indicating the relative position of an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive. It extends the generic gml:TimePrimitivePropertyType with an XML attribute relativePosition, whose value is selected from the set of 13 temporal relationships identified by Allen (1983) + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:AbstractTimeComplex is an aggregation of temporal primitives and acts as the head of a substitution group for temporal complexes. + + + + + + + + + + gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. +A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. +The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. + + + + + + + + + + + + gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. + + + + + + + + + + + + + + gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. + + + + + + + + + + gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. +The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. +Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. +Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. + + + + + + + + + + + + + + + + + + + + + + gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. + + + + + + + + + + The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. +Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system . +In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps. +Three XML attributes appear on gml:TimePositionType: +A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI. +For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era. +Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration. + + + + + + + + + + + + These values are interpreted as follows: +- “unknown” indicates that no specific value for temporal position is provided. +- “now” indicates that the specified value shall be replaced with the current temporal position whenever the value is accessed. +- “before” indicates that the actual temporal position is unknown, but it is known to be before the specified value. +- “after” indicates that the actual temporal position is unknown, but it is known to be after the specified value. +A value for indeterminatePosition may +- be used either alone, or +- qualify a specific value for temporal position. + + + + + + + + + + + The simple type gml:TimePositionUnion is a union of XML Schema simple types which instantiate the subtypes for temporal position described in ISO 19108. + An ordinal era may be referenced via URI. A decimal value may be used to indicate the distance from the scale origin . time is used for a position that recurs daily (see ISO 19108:2002 5.4.4.2). + Finally, calendar and clock forms that support the representation of time in systems based on years, months, days, hours, minutes and seconds, in a notation following ISO 8601, are assembled by gml:CalDate + + + + + + + + + This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. + + + + + The length of a time period. + + + + + + + + + gml:duration conforms to the ISO 8601 syntax for temporal length as implemented by the XML Schema duration type. + + + + + gml:timeInterval conforms to ISO 11404 which is based on floating point values for temporal length. +ISO 11404 syntax specifies the use of a positiveInteger together with appropriate values for radix and factor. The resolution of the time interval is to one radix ^(-factor) of the specified time unit. +The value of the unit is either selected from the units for time intervals from ISO 31-1:1992, or is another suitable unit. The encoding is defined for GML in gml:TimeUnitType. The second component of this union type provides a method for indicating time units other than the six standard units given in the enumeration. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalReferenceSystems.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalReferenceSystems.xsd new file mode 100644 index 0000000..8f78dee --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalReferenceSystems.xsd @@ -0,0 +1,183 @@ + + + + temporalReferenceSystems.xsd + See ISO/DIS 19136 15.5. +A value in the time domain is measured relative to a temporal reference system. Common types of reference systems include calendars, ordinal temporal reference systems, and temporal coordinate systems (time elapsed since some epoch). The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. The Julian day numbering system is a temporal coordinate system that has an origin earlier than any known calendar, at noon on 1 January 4713 BC in the Julian proleptic calendar, and is useful in transformations between dates in different calendars. +In GML seven concrete elements are used to describe temporal reference systems: gml:TimeReferenceSystem, gml:TimeCoordinateSystem, gml:TimeCalendar, gml:TimeCalendarEra, gml:TimeClock, gml:TimeOrdinalReferenceSystem, and gml:TimeOrdinalEra. + + + + + + A reference system is characterized in terms of its domain of validity: the spatial and temporal extent over which it is applicable. The basic GML element for temporal reference systems is gml:TimeReferenceSystem. Its content model extends gml:DefinitionType with one additional property, gml:domainOfValidity. + + + + + + + + + + + + + + A temporal coordinate system shall be based on a continuous interval scale defined in terms of a single time interval. +The differences to ISO 19108 TM_CoordinateSystem are: +- the origin is specified either using the property gml:originPosition whose value is a direct time position, or using the property gml:origin whose model is gml:TimeInstantPropertyType; this permits more flexibility in representation and also supports referring to a value fixed elsewhere; +- the interval uses gml:TimeIntervalLengthType. + + + + + + + + + + + + + + + + + + + A calendar is a discrete temporal reference system that provides a basis for defining temporal position to a resolution of one day. +gml:TimeCalendar adds one property to those inherited from gml:TimeReferenceSystem. A gml:referenceFrame provides a link to a gml:TimeCalendarEra that it uses. A gml:TimeCalendar may reference more than one calendar era. +The referenceFrame element follows the standard GML property model, allowing the association to be instantiated either using an inline description using the gml:TimeCalendarEra element, or a link to a gml:TimeCalendarEra which is explicit elsewhere. + + + + + + + + + + + + + + gml:TimeCalendarEra inherits basic properties from gml:DefinitionType and has the following additional properties: +- gml:referenceEvent is the name or description of a mythical or historic event which fixes the position of the base scale of the calendar era. This is given as text or using a link to description held elsewhere. +- gml:referenceDate specifies the date of the referenceEvent expressed as a date in the given calendar. In most calendars, this date is the origin (i.e., the first day) of the scale, but this is not always true. +- gml:julianReference specifies the Julian date that corresponds to the reference date. The Julian day number is an integer value; the Julian date is a decimal value that allows greater resolution. Transforming calendar dates to and from Julian dates provides a relatively simple basis for transforming dates from one calendar to another. +- gml:epochOfUse is the period for which the calendar era was used as a basis for dating. + + + + + + + + + + + + + + + + + gml:TimeCalendarPropertyType provides for associating a gml:TimeCalendar with an object. + + + + + + + + + + gml:TimeCalendarEraPropertyType provides for associating a gml:TimeCalendarEra with an object. + + + + + + + + + + A clock provides a basis for defining temporal position within a day. A clock shall be used with a calendar in order to provide a complete description of a temporal position within a specific day. +gml:TimeClock adds the following properties to those inherited from gml:TimeReferenceSystemType: +- gml:referenceEvent is the name or description of an event, such as solar noon or sunrise, which fixes the position of the base scale of the clock. +- gml:referenceTime specifies the time of day associated with the reference event expressed as a time of day in the given clock. The reference time is usually the origin of the clock scale. +- gml:utcReference specifies the 24 hour local or UTC time that corresponds to the reference time. +- gml:dateBasis contains or references the calendars that use this clock. + + + + + + + + + + + + + + + + + gml:TimeClockPropertyType provides for associating a gml:TimeClock with an object. + + + + + + + + + + In some applications of geographic information — such as geology and archaeology — relative position in time is known more precisely than absolute time or duration. The order of events in time can be well established, but the magnitude of the intervals between them cannot be accurately determined; in such cases, the use of an ordinal temporal reference system is appropriate. An ordinal temporal reference system is composed of a sequence of named coterminous eras, which may in turn be composed of sequences of member eras at a finer scale, giving the whole a hierarchical structure of eras of verying resolution. +An ordinal temporal reference system whose component eras are not further subdivided is effectively a temporal topological complex constrained to be a linear graph. An ordinal temporal reference system some or all of whose component eras are subdivided is effectively a temporal topological complex with the constraint that parallel branches may only be constructed in pairs where one is a single temporal ordinal era and the other is a sequence of temporal ordinal eras that are called "members" of the "group". This constraint means that within a single temporal ordinal reference system, the relative position of all temporal ordinal eras is unambiguous. +The positions of the beginning and end of a given era may calibrate the relative time scale. +gml:TimeOrdinalReferenceSystem adds one or more gml:component properties to the generic temporal reference system model. + + + + + + + + + + + + + + Its content model follows the pattern of gml:TimeEdge, inheriting standard properties from gml:DefinitionType, and adding gml:start, gml:end and gml:extent properties, a set of gml:member properties which indicate ordered gml:TimeOrdinalEra elements, and a gml:group property which points to the parent era. +The recursive inclusion of gml:TimeOrdinalEra elements allow the construction of an arbitrary depth hierarchical ordinal reference schema, such that an ordinal era at a given level of the hierarchy includes a sequence of shorter, coterminous ordinal eras. + + + + + + + + + + + + + + + + + + + gml:TimeOrdinalEraPropertyType provides for associating a gml:TimeOrdinalEra with an object. + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalTopology.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalTopology.xsd new file mode 100644 index 0000000..879d858 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/temporalTopology.xsd @@ -0,0 +1,113 @@ + + + + temporalTopology.xsd + See ISO/DIS 19136 15.3. +Temporal topology is described in terms of time complexes, nodes, and edges, and the connectivity between these. Temporal topology does not directly provide information about temporal position. It is used in the case of describing a lineage or a history (e.g. a family tree expressing evolution of species, an ecological cycle, a lineage of lands or buildings, or a history of separation and merger of administrative boundaries). The following Subclauses specifies the temporal topology as temporal characteristics of features in compliance with ISO 19108. + + + + + gml:TimeTopologyPrimitive acts as the head of a substitution group for topological temporal primitives. +Temporal topology primitives shall imply the ordering information between features or feature properties. The temporal connection of features can be examined if they have temporal topology primitives as values of their properties. Usually, an instantaneous feature associates with a time node, and a static feature associates with a time edge. A feature with both modes associates with the temporal topology primitive: a supertype of time nodes and time edges. +A topological primitive is always connected to one or more other topological primitives, and is, therefore, always a member of a topological complex. In a GML instance, this will often be indicated by the primitives being described by elements that are descendents of an element describing a complex. However, in order to support the case where a temporal topological primitive is described in another context, the optional complex property is provided, which carries a reference to the parent temporal topological complex. + + + + + + + + + + + + + + gml:TimeTopologyPrimitivePropertyType provides for associating a gml:AbstractTimeTopologyPrimitive with an object. + + + + + + + + + + A temporal topology complex shall be the connected acyclic directed graph composed of temporal topological primitives, i.e. time nodes and time edges. Because a time edge may not exist without two time nodes on its boundaries, static features have time edges from a temporal topology complex as the values of their temporal properties, regardless of explicit declarations. +A temporal topology complex expresses a linear or a non-linear graph. A temporal linear graph, composed of a sequence of time edges, provides a lineage described only by “substitution” of feature instances or feature element values. A time node as the start or the end of the graph connects with at least one time edge. A time node other than the start and the end shall connect to at least two time edges: one of starting from the node, and another ending at the node. +A temporal topological complex is a set of connected temporal topological primitives. The member primtives are indicated, either by reference or by value, using the primitive property. + + + + + + + + + + + + + + gml:TimeTopologyComplexPropertyType provides for associating a gml:TimeTopologyComplex with an object. + + + + + + + + + + A time node is a zero-dimensional topological primitive that represents an identifiable node in time (it is equivalent to a point in space). A node may act as the termination or initiation of any number of time edges. A time node may be realised as a geometry, its position, whose value is a time instant. + + + + + + + + + + + + + + + + gml:TimeNodePropertyType provides for associating a gml:TimeNode with an object + + + + + + + + + + A time edge is a one-dimensional topological primitive. It is an open interval that starts and ends at a node. The edge may be realised as a geometry whose value is a time period. + + + + + + + + + + + + + + + + gml:TimeEdgePropertyType provides for associating a gml:TimeEdge with an object. + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/topology.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/topology.xsd new file mode 100644 index 0000000..322f4e8 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/topology.xsd @@ -0,0 +1,380 @@ + + + + topology.xsd + See ISO/DIS 19136 Clause 14. +Topology is the branch of mathematics describing the properties of objects which are invariant under continuous deformation. For example, a circle is topologically equivalent to an ellipse because one can be transformed into the other by stretching. In geographic modelling, the foremost use of topology is in accelerating computational geometry. The constructs of topology allow characterisation of the spatial relationships between objects using simple combinatorial or algebraic algorithms. Topology, realised by the appropriate geometry, also allows a compact and unambiguous mechanism for expressing shared geometry among geographic features. +There are four instantiable classes of primitive topology objects, one for each dimension up to 3D. In addition, topological complexes are supported, too. +There is strong symmetry in the (topological boundary and coboundary) relationships between topology primitives of adjacent dimensions. Topology primitives are bounded by directed primitives of one lower dimension. The coboundary of each topology primitive is formed from directed topology primitives of one higher dimension. + + + + + This abstract type supplies the root or base type for all topological elements including primitives and complexes. It inherits AbstractGMLType and hence can be identified using the gml:id attribute. + + + + + + + + + + + + + + gml:AbstractTopoPrimitive acts as the base type for all topological primitives. Topology primitives are the atomic (smallest possible) units of a topology complex. +Each topology primitive may contain references to other topology primitives of codimension 2 or more (gml:isolated). Conversely, nodes may have faces as containers and nodes and edges may have solids as containers (gml:container). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + In the case of planar topology, a gml:Node must have a clockwise sequence of gml:directedEdge properties, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). + + + + + + + + + + + gml:Node represents the 0-dimensional primitive. +The optional coboundary of a node (gml:directedEdge) is a sequence of directed edges which are incident on this node. Edges emanating from this node appear in the node coboundary with a negative orientation. +If provided, the aggregationType attribute shall have the value “sequence”. +A node may optionally be realised by a 0-dimensional geometric primitive (gml:pointProperty). + + + + + A gml:directedNode property element describes the boundary of topology edges and is used in the support of topological point features via the gml:TopoPoint expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included node is used: start (“-“) or end (“+”) node. + + + + + + + + + + + + + + + + + + + + + + + + + + gml:Edge represents the 1-dimensional primitive. +The topological boundary of an Edge (gml:directedNode) consists of a negatively directed start Node and a positively directed end Node. +The optional coboundary of an edge (gml:directedFace) is a circular sequence of directed faces which are incident on this edge in document order. In the 2D case, the orientation of the face on the left of the edge is "+"; the orientation of the face on the right on its right is "-". +If provided, the aggregationType attribute shall have the value “sequence”. +An edge may optionally be realised by a 1-dimensional geometric primitive (gml:curveProperty). + + + + + A gml:directedEdge property element describes the boundary of topology faces, the coBoundary of topology nodes and is used in the support of topological line features via the gml:TopoCurve expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included edge is used, i.e. forward or reverse. + + + + + + + + + + + + + + + + + + + + + + + If the topological representation exists an unbounded manifold (e.g. Euclidean plane), a gml:Face must indicate whether it is a universal face or not, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). The optional universal attribute of type boolean is used to indicate this. NOTE The universal face is normally not part of any feature, and is used to represent the unbounded portion of the data set. Its interior boundary (it has no exterior boundary) would normally be considered the exterior boundary of the map represented by the data set. + + + + + + + + gml:Face represents the 2-dimensional topology primitive. +The topological boundary of a face (gml:directedEdge) consists of a sequence of directed edges. If provided, the aggregationType attribute shall have the value “sequence”. +The optional coboundary of a face (gml:directedTopoSolid) is a pair of directed solids which are bounded by this face. A positively directed solid corresponds to a solid which lies in the direction of the negatively directed normal to the face in any geometric realisation. +A face may optionally be realised by a 2-dimensional geometric primitive (gml:surfaceProperty). + + + + + The gml:directedFace property element describes the boundary of topology solids, in the coBoundary of topology edges and is used in the support of surface features via the gml:TopoSurface expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included face is used i.e. inward or outward with respect to the surface normal in any geometric realisation. + + + + + + + + + + + + + + + + + + + + + + A gml:TopoSolid must indicate whether it is a universal topo-solid or not, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). The optional universal attribute of type boolean is used to indicate this and the default is fault. NOTE The universal topo-solid is normally not part of any feature, and is used to represent the unbounded portion of the data set. Its interior boundary (it has no exterior boundary) would normally be considered the exterior boundary of the data set. + + + + + + + + gml:TopoSolid represents the 3-dimensional topology primitive. +The topological boundary of a solid (gml:directedFace) consists of a set of directed faces. +A solid may optionally be realised by a 3-dimensional geometric primitive (gml:solidProperty). + + + + + The gml:directedSolid property element describes the coBoundary of topology faces and is used in the support of volume features via the gml:TopoVolume expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included solid appears in the face coboundary. In the context of a gml:TopoVolume the orientation attribute has no meaning. + + + + + + + + + + + + + + + + + + + + + + The intended use of gml:TopoPoint is to appear within a point feature to express the structural and possibly geometric relationships of this feature to other features via shared node definitions. + + + + + + + + + + + The gml:topoPointProperty property element may be used in features to express their relationship to the referenced topology node. + + + + + + + + + + + + + + + gml:TopoCurve represents a homogeneous topological expression, a sequence of directed edges, which if realised are isomorphic to a geometric curve primitive. The intended use of gml:TopoCurve is to appear within a line feature to express the structural and geometric relationships of this feature to other features via the shared edge definitions. +If provided, the aggregationType attribute shall have the value “sequence”. + + + + + + + + + + + The gml:topoCurveProperty property element may be used in features to express their relationship to the referenced topology edges. + + + + + + + + + + + + + + + gml:TopoSurface represents a homogeneous topological expression, a set of directed faces, which if realised are isomorphic to a geometric surface primitive. The intended use of gml:TopoSurface is to appear within a surface feature to express the structural and possibly geometric relationships of this surface feature to other features via the shared face definitions. + + + + + + + + + + + The gml:topoSurfaceProperty property element may be used in features to express their relationship to the referenced topology faces. + + + + + + + + + + + + + + + gml:TopoVolume represents a homogeneous topological expression, a set of directed topologic solids, which if realised are isomorphic to a geometric solid primitive. The intended use of gml:TopoVolume is to appear within a solid feature to express the structural and geometric relationships of this solid feature to other features via the shared solid definitions. + + + + + + + + + + + The gml:topoVolumeProperty element may be used in features to express their relationship to the referenced topology volume. + + + + + + + + + + + + + + + + + + + + gml:TopoComplex is a collection of topological primitives. +Each complex holds a reference to its maximal complex (gml:maximalComplex) and optionally to sub- or super-complexes (gml:subComplex, gml:superComplex). +A topology complex contains its primitive and sub-complex members. + + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The gml:topoPrimitiveMember property element encodes for the relationship between a topology complex and a single topology primitive. + + + + + + + + + + + + The gml:topoPrimitiveMembers property element encodes the relationship between a topology complex and an arbitrary number of topology primitives. + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/units.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/units.xsd new file mode 100644 index 0000000..b8a4338 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/units.xsd @@ -0,0 +1,156 @@ + + + + units.xsd + See ISO/DIS 17.2. +Several GML Schema components concern or require a reference scale or units of measure. Units are required for quantities that may occur as values of properties of feature types, as the results of observations, in the range parameters of a coverage, and for measures used in Coordinate Reference System definitions. +The basic unit definition is an extension of the general gml:Definition element defined in 16.2.1. Three specialized elements for unit definition are further derived from this. +This model is based on the SI system of units [ISO 1000], which distinguishes between Base Units and Derived Units. +- Base Units are the preferred units for a set of orthogonal fundamental quantities which define the particular system of units, which may not be derived by combination of other base units. +- Derived Units are the preferred units for other quantities in the system, which may be defined by algebraic combination of the base units. +In some application areas Conventional units are used, which may be converted to the preferred units using a scaling factor or a formula which defines a re-scaling and offset. The set of preferred units for all physical quantity types in a particular system of units is composed of the union of its base units and derived units. +Unit definitions are substitutable for the gml:Definition element declared as part of the dictionary model. A dictionary that contains only unit definitions and references to unit definitions is a units dictionary. + + + + + The element gml:unitOfMeasure is a property element to refer to a unit of measure. This is an empty element which carries a reference to a unit of measure definition. + + + + + + + + + A gml:UnitDefinition is a general definition of a unit of measure. This generic element is used only for units for which no relationship with other units or units systems is known. +The content model of gml:UnitDefinition adds three additional properties to gml:Definition, gml:quantityType, gml:quantityTypeReference and gml:catalogSymbol. +The gml:catalogSymbol property optionally gives the short symbol used for this unit. This element is usually used when the relationship of this unit to other units or units systems is unknown. + + + + + + + + + + + + + + + + The gml:quantityType property indicates the phenomenon to which the units apply. This element contains an informal description of the phenomenon or type of physical quantity that is measured or observed. When the physical quantity is the result of an observation or measurement, this term is known as observable type or measurand. +The use of gml:quantityType for references to remote values is deprecated. + + + + + The gml:quantityTypeReference property indicates the phenomenon to which the units apply. The content is a reference to a remote value. + + + + + The catalogSymbol is the preferred lexical symbol used for this unit of measure. +The codeSpace attribute in gml:CodeType identifies a namespace for the catalog symbol value, and might reference the external catalog. The string value in gml:CodeType contains the value of a symbol that should be unique within this catalog namespace. This symbol often appears explicitly in the catalog, but it could be a combination of symbols using a specified algebra of units. + + + + + A base unit is a unit of measure that cannot be derived by combination of other base units within a particular system of units. For example, in the SI system of units, the base units are metre, kilogram, second, Ampere, Kelvin, mole, and candela, for the physical quantity types length, mass, time interval, electric current, thermodynamic temperature, amount of substance and luminous intensity, respectively. +gml:BaseUnit extends generic gml:UnitDefinition with the property gml:unitsSystem, which carries a reference to the units system to which this base unit is asserted to belong. + + + + + + + + + + + + + + Derived units are defined by combination of other units. Derived units are used for quantities other than those corresponding to the base units, such as hertz (s-1) for frequency, Newton (kg.m/s2) for force. Derived units based directly on base units are usually preferred for quantities other than the fundamental quantities within a system. If a derived unit is not the preferred unit, the gml:ConventionalUnit element should be used instead. +The gml:DerivedUnit extends gml:UnitDefinition with the property gml:derivationUnitTerms. + + + + + + + + + + + + + + A set of gml:derivationUnitTerm elements describes a derived unit of measure. Each element carries an integer exponent. The terms are combined by raising each referenced unit to the power of its exponent and forming the product. +This unit term references another unit of measure (uom) and provides an integer exponent applied to that unit in defining the compound unit. The exponent may be positive or negative, but not zero. + + + + + + + + + + + + Conventional units that are neither base units nor defined by direct combination of base units are used in many application domains. For example electronVolt for energy, feet and nautical miles for length. In most cases there is a known, usually linear, conversion to a preferred unit which is either a base unit or derived by direct combination of base units. +The gml:ConventionalUnit extends gml:UnitDefinition with a property that describes a conversion to a preferred unit for this physical quantity. When the conversion is exact, the element gml:conversionToPreferredUnit should be used, or when the conversion is not exact the element gml:roughConversionToPreferredUnit is available. Both of these elements have the same content model. The gml:derivationUnitTerm property defined above is included to allow a user to optionally record how this unit may be derived from other (“more primitive”) units. + + + + + + + + + + + + + + + + + + The elements gml:conversionToPreferredUnit and gml:roughConversionToPreferredUnit represent parameters used to convert conventional units to preferred units for this physical quantity type. A preferred unit is either a Base Unit or a Derived Unit that is selected for all values of one physical quantity type. + + + + + The elements gml:conversionToPreferredUnit and gml:roughConversionToPreferredUnit represent parameters used to convert conventional units to preferred units for this physical quantity type. A preferred unit is either a Base Unit or a Derived Unit that is selected for all values of one physical quantity type. + + + + + The inherited attribute uom references the preferred unit that this conversion applies to. The conversion of a unit to the preferred unit for this physical quantity type is specified by an arithmetic conversion (scaling and/or offset). The content model extends gml:UnitOfMeasureType, which has a mandatory attribute uom which identifies the preferred unit for the physical quantity type that this conversion applies to. The conversion is specified by a choice of +- gml:factor, which defines the scale factor, or +- gml:formula, which defines a formula +by which a value using the conventional unit of measure can be converted to obtain the corresponding value using the preferred unit of measure. +The formula defines the parameters of a simple formula by which a value using the conventional unit of measure can be converted to the corresponding value using the preferred unit of measure. The formula element contains elements a, b, c and d, whose values use the XML Schema type double. These values are used in the formula y = (a + bx) / (c + dx), where x is a value using this unit, and y is the corresponding value using the base unit. The elements a and d are optional, and if values are not provided, those parameters are considered to be zero. If values are not provided for both a and d, the formula is equivalent to a fraction with numerator and denominator parameters. + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/valueObjects.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/valueObjects.xsd new file mode 100644 index 0000000..6d24a1c --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19136_Schemas/valueObjects.xsd @@ -0,0 +1,199 @@ + + + + valueObjects.xsd + See ISO/DIS 19136 17.5. +The elements declared in this Clause build on other GML schema components, in particular gml:AbstractTimeObject, gml:AbstractGeometry, and the following types: gml:MeasureType, gml:MeasureListType, gml:CodeType, gml:CodeOrNilReasonListType, gml:BooleanOrNilReasonListType, gml:IntegerOrNilReasonList. +Of particular interest are elements that are the heads of substitution groups, and one named choice group. These are the primary reasons for the value objects schema, since they may act as variables in the definition of content models, such as Observations, when it is desired to permit alternative value types to occur some of which may have complex content such as arrays, geometry and time objects, and where it is useful not to prescribe the actual value type in advance. The members of the groups include quantities, category classifications, boolean, count, temporal and spatial values, and aggregates of these. +The value objects are defined in a hierarchy. The following relationships are defined: +- Concrete elements gml:Quantity, gml:Category, gml:Count and gml:Boolean are substitutable for the abstract element gml:AbstractScalarValue. +- Concrete elements gml:QuantityList, gml:CategoryList, gml:CountList and gml:BooleanList are substitutable for the abstract element gml:AbstractScalarValueList. +- Concrete element gml:ValueArray is substitutable for the concrete element gml:CompositeValue. +- Abstract elements gml:AbstractScalarValue and gml:AbstractScalarValueList, and concrete elements gml:CompositeValue, gml:ValueExtent, gml:CategoryExtent, gml:CountExtent and gml:QuantityExtent are substitutable for abstract element gml:AbstractValue. +- Abstract elements gml:AbstractValue, gml:AbstractTimeObject and gml:AbstractGeometry are all in a choice group named gml:Value, which is used for compositing in gml:CompositeValue and gml:ValueExtent. +- Schemas which need values may use the abstract element gml:AbstractValue in a content model in order to permit any of the gml:AbstractScalarValues, gml:AbstractScalarValueLists, gml:CompositeValue or gml:ValueExtent to occur in an instance, or the named group gml:Value to also permit gml:AbstractTimeObjects, gml:AbstractGeometrys. + + + + + + + + + + + + + + + + A gml:Category has an optional XML attribute codeSpace, whose value is a URI which identifies a dictionary, codelist or authority for the term. + + + + + + + + + + + + + + + + + + + + + + + An XML attribute uom (“unit of measure”) is required, whose value is a URI which identifies the definition of a ratio scale or units by which the numeric value shall be multiplied, or an interval or position scale on which the value occurs. + + + + + + + + + + + + + gml:AbstractValue is an abstract element which acts as the head of a substitution group which contains gml:AbstractScalarValue, gml:AbstractScalarValueList, gml:CompositeValue and gml:ValueExtent, and (transitively) the elements in their substitution groups. +These elements may be used in an application schema as variables, so that in an XML instance document any member of its substitution group may occur. + + + + + gml:AbstractScalarValue is an abstract element which acts as the head of a substitution group which contains gml:Boolean, gml:Category, gml:Count and gml:Quantity, and (transitively) the elements in their substitution groups. + + + + + gml:AbstractScalarValueList is an abstract element which acts as the head of a substitution group which contains gml:BooleanList, gml:CategoryList, gml:CountList and gml:QuantityList, and (transitively) the elements in their substitution groups. + + + + + This is a convenience choice group which unifies generic values defined in this Clause with spatial and temporal objects and the measures described above, so that any of these may be used within aggregate values. + + + + + + + + + + + Property that refers to, or contains, a Value. Convenience element for general use. + + + + + Property that refers to, or contains, a Value. + + + + + + + + + + + + Property that contains Values. + + + + + + + + + + + gml:CompositeValue is an aggregate value built from other values . It contains zero or an arbitrary number of gml:valueComponent elements, and zero or one gml:valueComponents property elements. It may be used for strongly coupled aggregates (vectors, tensors) or for arbitrary collections of values. + + + + + + + + + + + + + + + + A Value Array is used for homogeneous arrays of primitive and aggregate values. +The member values may be scalars, composites, arrays or lists. +ValueArray has the same content model as CompositeValue, but the member values shall be homogeneous. The element declaration contains a Schematron constraint which expresses this restriction precisely. Since the members are homogeneous, the gml:referenceSystem (uom, codeSpace) may be specified on the gml:ValueArray itself and inherited by all the members if desired. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/basicTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/basicTypes.xsd new file mode 100644 index 0000000..2e49b18 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/basicTypes.xsd @@ -0,0 +1,429 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:00:05 ====== + + + + + + + + + + + + A TypeName is a LocalName that references either a recordType or object type in some form of schema. The stored value "aName" is the returned value for the "aName()" operation. This is the types name. - For parsing from types (or objects) the parsible name normally uses a "." navigation separator, so that it is of the form [class].[member].[memberOfMember]. ...) + + + + + + + + + + + + + + + + + + + + + + + A MemberName is a LocalName that references either an attribute slot in a record or recordType or an attribute, operation, or association role in an object instance or type description in some form of schema. The stored value "aName" is the returned value for the "aName()" operation. + + + + + + + + + + + + + + + + + + + + + + + + Use to represent the possible cardinality of a relation. Represented by a set of simple multiplicity ranges. + + + + + + + + + + + + + + + + + + + + + + + A component of a multiplicity, consisting of an non-negative lower bound, and a potentially infinite upper bound. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gco.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gco.xsd new file mode 100644 index 0000000..65af021 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gco.xsd @@ -0,0 +1,12 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:00:06 ====== + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gcoBase.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gcoBase.xsd new file mode 100644 index 0000000..e79a36c --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gco/gcoBase.xsd @@ -0,0 +1,61 @@ + + + + + This schema provides: + 1. tools to handle specific objects like "code lists" and "record"; + 2. Some XML types representing that do not follow the general encoding rules. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/applicationSchema.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/applicationSchema.xsd new file mode 100644 index 0000000..fbf8f52 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/applicationSchema.xsd @@ -0,0 +1,42 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ====== + + + + + + + + + + Information about the application schema used to build the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/citation.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/citation.xsd new file mode 100644 index 0000000..b4508da --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/citation.xsd @@ -0,0 +1,275 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:04 ====== + + + + + + + + + + Identification of, and means of communication with, person(s) and organisations associated with the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + + Standardized resource reference + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Location of the responsible individual or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information about online sources from which the dataset, specification, or community profile name and extended metadata elements can be obtained. + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information required enabling contact with the responsible person and/or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + Telephone numbers for contacting the responsible individual or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/constraints.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/constraints.xsd new file mode 100644 index 0000000..d3cf941 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/constraints.xsd @@ -0,0 +1,106 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:01 ====== + + + + + + + + + Restrictions on the access and use of a dataset or metadata + + + + + + + + + + + + + + + + + + + + + + + Restrictions and legal prerequisites for accessing and using the dataset. + + + + + + + + + + + + + + + + + + + + + + + + + Handling restrictions imposed on the dataset because of national security, privacy, or other concerns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/content.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/content.xsd new file mode 100644 index 0000000..9089c36 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/content.xsd @@ -0,0 +1,188 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ====== + + + + + + + + + + Information identifing the feature catalogue + + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the domain of the raster cell + + + + + + + + + + + + + + + + + + + + + + + + + Information about an image's suitability for use + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Set of adjacent wavelengths in the electro-magnetic spectrum with a common characteristic, such as the visible band + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/dataQuality.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/dataQuality.xsd new file mode 100644 index 0000000..70762bf --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/dataQuality.xsd @@ -0,0 +1,554 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:01 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + quantitative_result from Quality Procedures - - renamed to remove implied use limitiation. + + + + + + + + + + + + + + + + + + + + + + + + + Quantitative_conformance_measure from Quality Procedures. - - Renamed to remove implied use limitation - - OCL - -- result is type specified by valueDomain - result.tupleType = valueDomain + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/distribution.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/distribution.xsd new file mode 100644 index 0000000..fee05da --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/distribution.xsd @@ -0,0 +1,202 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ====== + + + + + + + + + + Information about the media on which the data can be distributed + + + + + + + + + + + + + + + + + + + + + + + + + + + + Technical means and media by which a dataset is obtained from the distributor + + + + + + + + + + + + + + + + + + + + + + + + + + Common ways in which the dataset may be obtained or received, and related instructions and fee information + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the distributor + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the distributor of and options for obtaining the dataset + + + + + + + + + + + + + + + + + + + + + + + + + Description of the form of the data to be distributed + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/extent.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/extent.xsd new file mode 100644 index 0000000..47d2a38 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/extent.xsd @@ -0,0 +1,205 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:04 ====== + + + + + + + + + + + + + Time period covered by the content of the dataset + + + + + + + + + + + + + + + + + + + + + + + Vertical domain of dataset + + + + + + + + + + + + + + + + + + + + + + + + + Boundary enclosing the dataset expressed as the closed set of (x,y) coordinates of the polygon (last point replicates first point) + + + + + + + + + + + + + + + + + + + + + + + Information about spatial, vertical, and temporal extent + + + + + + + + + + + + + + + + + + + + + + + + + + Geographic area of the dataset + + + + + + + + + + + + + + + + + + + + + + + Geographic area of the entire dataset referenced to WGS 84 + + + + + + + + + + + + + + + + + + + + + + + + + + Extent with respect to date and time + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/freeText.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/freeText.xsd new file mode 100644 index 0000000..ec541c9 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/freeText.xsd @@ -0,0 +1,122 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 03-17-2005 17:21:53 ====== Informative package (concepts are not implementable) - pragmatic approach for encoding + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/gmd.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/gmd.xsd new file mode 100644 index 0000000..5a5975a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/gmd.xsd @@ -0,0 +1,12 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:04 ====== + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/identification.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/identification.xsd new file mode 100644 index 0000000..852babb --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/identification.xsd @@ -0,0 +1,348 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:05 ====== + + + + + + + + + + + + Basic information about data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Graphic that provides an illustration of the dataset (should include a legend for the graphic) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + See 19119 for further info + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Brief description of ways in which the dataset is currently used. + + + + + + + + + + + + + + + + + + + + + + + + + + Keywords, their type and reference source + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Encapsulates the dataset aggregation information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + High-level geospatial data thematic classification to assist in the grouping and search of available geospatial datasets + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/maintenance.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/maintenance.xsd new file mode 100644 index 0000000..7d1d9b1 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/maintenance.xsd @@ -0,0 +1,86 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:04 ====== Status of the dataset or progress of a review + + + + + + + + + + + Information about the scope and frequency of updating + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of the class of information covered by the information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataApplication.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataApplication.xsd new file mode 100644 index 0000000..d63ec41 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataApplication.xsd @@ -0,0 +1,175 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:05 ====== + + + + + + + + + + Identifiable collection of datasets + + + + + + + + + + + + + + + + + + + + + + + + + + Identifiable collection of data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataEntity.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataEntity.xsd new file mode 100644 index 0000000..77c4a27 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataEntity.xsd @@ -0,0 +1,70 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:00 ====== + + + + + + + + + + + + + + + + + Information about the metadata + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataExtension.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataExtension.xsd new file mode 100644 index 0000000..21202ec --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/metadataExtension.xsd @@ -0,0 +1,99 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ====== Method used to represent geographic information in the dataset + + + + + + + + + + New metadata element, not found in ISO 19115, which is required to describe geographic data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information describing metadata extensions. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/portrayalCatalogue.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/portrayalCatalogue.xsd new file mode 100644 index 0000000..0b774c6 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/portrayalCatalogue.xsd @@ -0,0 +1,36 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ====== + + + + + + + + + + Information identifing the portrayal catalogue used + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/referenceSystem.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/referenceSystem.xsd new file mode 100644 index 0000000..bf3864b --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/referenceSystem.xsd @@ -0,0 +1,100 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:04 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of the spatial and temporal reference systems used in the dataset + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/spatialRepresentation.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/spatialRepresentation.xsd new file mode 100644 index 0000000..e67de38 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmd/spatialRepresentation.xsd @@ -0,0 +1,237 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:02 ====== Frequency with which modifications and deletations are made to the data after it is first produced + + + + + + + + + + + Types and numbers of raster spatial objects in the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the vector spatial objects in the dataset + + + + + + + + + + + + + + + + + + + + + + + + Digital mechanism used to represent spatial information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/catalogues.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/catalogues.xsd new file mode 100644 index 0000000..6746f22 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/catalogues.xsd @@ -0,0 +1,112 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 04-27-2005 17:16:11 ====== Handcrafted + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/codelistItem.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/codelistItem.xsd new file mode 100644 index 0000000..ded0a8f --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/codelistItem.xsd @@ -0,0 +1,168 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 03-15-2005 09:14:50 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Constraints: - 1) metadataProperty.card = 0 - 2) dictionaryEntry.card = 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Constraint: codeEntry.type = ML_CodeListDefinition + + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/crsItem.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/crsItem.xsd new file mode 100644 index 0000000..c39e2a5 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/crsItem.xsd @@ -0,0 +1,1030 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 03-15-2005 09:15:11 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/extendedTypes.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/extendedTypes.xsd new file mode 100644 index 0000000..1daa07a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/extendedTypes.xsd @@ -0,0 +1,78 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 03-14-2005 12:00:20 ====== Handcrafted + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmx.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmx.xsd new file mode 100644 index 0000000..aa0ab27 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmx.xsd @@ -0,0 +1,2 @@ + +This file was generated from ISO TC/211 UML class diagrams == 03-18-2005 11:12:17 ====== \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmxUsage.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmxUsage.xsd new file mode 100644 index 0000000..e9b4b7f --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/gmxUsage.xsd @@ -0,0 +1,127 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 04-27-2005 17:15:30 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/uomItem.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/uomItem.xsd new file mode 100644 index 0000000..9354663 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gmx/uomItem.xsd @@ -0,0 +1,162 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 03-15-2005 09:15:02 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + XML attributes contraints: - 1) Id is mandatory - 2) codeSpace (type xsd:anyURI) is mandatory + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/gsr.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/gsr.xsd new file mode 100644 index 0000000..8f7f428 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/gsr.xsd @@ -0,0 +1,12 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:24:48 ====== + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/spatialReferencing.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/spatialReferencing.xsd new file mode 100644 index 0000000..a48334c --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gsr/spatialReferencing.xsd @@ -0,0 +1,24 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:24:48 ====== + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/geometry.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/geometry.xsd new file mode 100644 index 0000000..9235a8a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/geometry.xsd @@ -0,0 +1,35 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:14:37 ====== The geometry packages (Figure 4) contain the various classes for coordinate geometry. All of these classes through the root class GM_Object inherit an optional association to a coordinate reference system. All direct positions exposed through the interfaces defined in this standard shall be in the coordinate reference system of the geometric object accessed. All elements of a geometric complex, composite, or aggregate shall be associated to the same coordinate reference system. When instances of GM_Object are aggregated in another GM_Object (such as a GM_Aggregate, or GM_Complex) which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. - The geometry package has several internal packages that separate primitive geometric objects, aggregates and complexes, which have a more elaborate internal structure than simple aggregates. Figure 4 shows the dependencies between the geometry packages as well as a list of classes for each package - Figure 5 shows the basic classes defined in the geometry packages. Any object that inherits the semantics of the GM_Object acts as a set of direct positions. Its behavior will be determined by which direct positions it contains. Objects under GM_Primitive will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. Objects under GM_Complex will be closed, that is, they will contain their boundary points. This leads to some apparent ambiguity. A representation of a line as a primitive must reference its end points, but will not contain these points as a set of direct positions. A representation of a line as a complex will also reference its end points, and will contain these points as a set of direct positions. This means that identical digital representations will have slightly different semantics depending on whether they are accessed as primitives or complexes. - This difference of semantics is most striking in the GM_CompositeCurve. Composite curves are used to represent features whose geometry could also be represented as curve primitives. From a cartographic point of view, these two representations are not different. From a topological point of view, they are different. This distinction appears in the inheritance diagram (Figure 5) as an inheritance relationship between GM_CompositeCurve and GM_OrientableCurve. The primary semantics of a GM_CompositeCurve (see 6.6.5) is as a closed GM_Object, but it may also act as an open GM_Object under GM_Primitive operations (see 6.3.10). Interface protocols depending upon the topological details of this object will have to be distinguished as to whether they have been inherited from GM_Primitive or GM_Complex, where the distinction first occurs. Even though these protocols have been inherited from the same operations defined at GM_Object, they will act differently depending upon the branch of the inheritance tree from which they have inherited semantics. Creators of implementation profiles may take this into account and use a proxy mechanism for realization relationships that cause semantic dissonance. Such a procedure will be necessary in object-oriented programming and databases in systems that disallow multiple inheritance or make limiting assumptions about method binding. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/gss.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/gss.xsd new file mode 100644 index 0000000..f8cac18 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gss/gss.xsd @@ -0,0 +1,12 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:14:37 ====== This package contains the normative (Geometry and Topology) parts of the model for ISO 19107. This document should be referred to as the official description of the Model. If there are any differences, then ISO 19107 takes precedence. - - This packages also contains example (informative) of applications of 19107. + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/gts.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/gts.xsd new file mode 100644 index 0000000..a4edb52 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/gts.xsd @@ -0,0 +1,12 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:18:09 ====== + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/temporalObjects.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/temporalObjects.xsd new file mode 100644 index 0000000..c7fa081 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/gts/temporalObjects.xsd @@ -0,0 +1,34 @@ + + + + + This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:18:09 ====== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml new file mode 100644 index 0000000..1a15854 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml @@ -0,0 +1,819 @@ + + + + + ML_gmxCodelists + + + Codelists for description of metadata datasets compliant with ISO/TC 211 19115:2003 and 19139 + + + Listes de codes pour la description de lots de métadonnées conforme ISO TC/211 19115:2003 et 19139 + + + + + GMX (and imported) namespace + + + 0.0 + + + 2005-03-18 + + + + English + UTF 8 + + + + French + France + UTF 8 + + + + + + + + + identification of when a given event occurred + CI_DateTypeCode + + + date identifies when the resource was brought into existence + creation + creation + + + date identifiant la création de la ressource + creation + création + + + + + + + + date identifies when the resource was issued + publication + publication + + + date identifiant la publication de la ressource + publication + publication + + + + + + + + date identifies when the resource was examined or re-examined and imporved or amended + revision + revision + + + amélioration ou amendement de la ressource + revision + révision + + + + + + + + identification de quand un événement s'est produit + CI_DateTypeCode + + + + + + + + + function performed by the resource + CI_OnLineFunctionCode + + + online instructions for transferring data from one storage device or system to another + download + Download + + + transfert de la ressource d'un système à un autre + download + Téléchargement + + + + + + + + online information about the resource + information + Information + + + description de la ressource en ligne + information + Information + + + + + + + + online instructions for requesting the resource from the provider + offlineAccess + Off line access + + + information pour requérir la ressource + offlineAccess + Accès hors ligne + + + + + + + + online order process for obtening the resource + order + Order + + + formulaire pour obtenir la ressource + order + commande en ligne + + + + + + + + online search interface for seeking out information about the resource + search + Search + + + interface de recherche d'information sur la ressource + search + Moteur de recherche + + + + + + + + Fonctionnalité offerte par la ressource + CI_OnLineFunctionCode + + + + + + + + + name of the character coding standard used in the resource + MD_CharacterSetCode + + + 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 + ucs2 + + + 16 bits ISO/IEC 10646 + ucs2 + + + + + + + + 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 + ucs4 + + + 32 bits ISO/IEC 10646 + ucs4 + + + + + + + + 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf7 + + + 7 bits ISO/IEC 10646 + utf7 + + + + + + + + 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf8 + + + 8 bits ISO/IEC 10646 + utf8 + + + + + + + + 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf16 + + + 16 bits ISO/IEC 10646 + utf16 + + + + + + + + ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 + 8859part1 + + + ISO/IEC 8859-1, alphabet latin 1 + 8859part1 + + + + + + + + ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 + 8859part2 + + + ISO/IEC 8859-2, alphabet latin 2 + 8859part2 + + + + + + + + ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 + 8859part3 + + + ISO/IEC 8859-3, alphabet latin 3 + 8859part3 + + + + + + + + ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 + 8859part4 + + + ISO/IEC 8859-4, alphabet latin 4 + 8859part4 + + + + + + + + ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet + 8859part5 + + + ISO/IEC 8859-5, alphabet latin/cyrillique + 8859part5 + + + + + + + + ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet + 8859part6 + + + ISO/IEC 8859-6, alphabet latin/arabe + 8859part6 + + + + + + + + ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet + 8859part7 + + + ISO/IEC 8859-7, alphabet latin/grec + 8859part7 + + + + + + + + ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet + 8859part8 + + + ISO/IEC 8859-8, alphabet latin/hébreu + 8859part8 + + + + + + + + ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 + 8859part9 + + + ISO/IEC 8859-9, alphabet latin 5 + 8859part9 + + + + + + + + ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 + 8859part10 + + + ISO/IEC 8859-10, alphabet latin 6 + 8859part10 + + + + + + + + ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet + 8859part11 + + + ISO/IEC 8859-11, alphabet latin/Thaï + 8859part11 + + + + + + + + + ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 + 8859part13 + + + ISO/IEC 8859-13, alphabet latin 7 + 8859part13 + + + + + + + + ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) + 8859part14 + + + ISO/IEC 8859-14, alphabet latin 8 (celtique) + 8859part14 + + + + + + + + ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 + 8859part15 + + + ISO/IEC 8859-15, alphabet latin 9 + 8859part15 + + + + + + + + ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 + 8859part16 + + + ISO/IEC 8859-16, alphabet latin 10 + 8859part16 + + + + + + + + japanese code set used for electronic transmission + jis + + + Japonais + jis + + + + + + + + japanese code set used on MS-DOS machines + shiftJIS + + + Japonais pour MS-DOS + shiftJIS + + + + + + + + japanese code set used on UNIX based machines + eucJP + + + Japonais pour UNIX + eucJP + + + + + + + + United States ASCII code set (ISO 646 US) + usAscii + + + ISO 646 US + usAscii + + + + + + + + IBM mainframe code set + ebcdic + + + IBM + ebcdic + + + + + + + + Korean code set + eucKR + + + Koréen + eucKR + + + + + + + + traditional Chinese code set used in Taiwan, Hong Kong of China and other areas + big5 + + + Chinois traditionel (Taiwan, Hong Kong, Chine) + big5 + + + + + + + + simplified Chinese code set + GB2312 + + + Chinois simplifié + GB2312 + + + + + + + + Jeu de caractères + MD_CharacterSetCode + + + + + + + + + class of information to which the referencing entity applies + MD_ScopeCode + + + Information applies to the attribute class + attribute + Attribute + + + Information qui s’applique à une classe d’attributs + attribute + Attribut + + + + + + + + Information applies to the characteristic of a feature + attributeType + Attribute type + + + Information qui s’applique à la caractéristique d’une entité géographique + attributeType + Type d’attribut + + + + + + + + Information applies to the dataset + dataset + Dataset + + + Information qui s’applique au jeu de données + dataset + Jeu de données + + + + + + Information applies to the dataset + dataset + 005 + + + + + + + Information applies to the series + series + Series + + + Information qui s’applique à une série + series + Série + + + + + + + + Information applies to non-geographic data + nonGeographicDataset + Non geographic dataset + + + Information qui s’applique à des données non-géographiques + nonGeographicDataset + Jeu de données non géographiques + + + + + + + + Information applies to a feature + feature + Feature + + + Information qui s’applique à un élément (entité géographique) + feature + Elément + + + + + + + + Information applies to a feature type + featureType + Feature type + + + Information qui s’applique à un type d’élément + featureType + Type d’élément + + + + + + + + Information applies to a property type + propertyType + Property type + + + Information qui s’applique à un type de propriété + propertyType + Type de propriété + + + + + + + + Information applies to a tile, a spatial subset of geographic data + tile + Tile + + + Information qui s’applique à une tuile, un sous-ensemble spatial de données géographiques + tile + Tuile + + + + + + + + information sur l'entité sur laquelle les métadonnées s'appliquent + MD_ScopeCode + + + + + + + + + + Language : ISO 639-2 (3 characters) + LanguageCode + + + English + eng + English + + + Anglais + eng + Anglais + + + + + + + + French + fra + French + + + Français + fra + Français + + + + + + + + Langue : ISO 639-2 (3 caractères) + LanguageCode + + + + + + + + + Country : ISO 3166-2 (2 characters) + Country + + + United Kingdom + UK + United Kingdom + + + Royaume-Uni + UK + Royaume-Uni + + + + + + + + France + FR + France + + + France + FR + France + + + + + + + + Pays : ISO 3166-2 (2 caractères) + Country + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml new file mode 100644 index 0000000..3cc1c2d --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml @@ -0,0 +1,1858 @@ + + + + + gmxCodelists + + + Codelists for description of metadata datasets compliant with ISO/TC 211 19115:2003 and 19139 + + + GMX (and imported) namespace + + + 0.0 + + + 2005-03-18 + + + + + + + + identification of when a given event occurred + CI_DateTypeCode + + + date identifies when the resource was brought into existence + creation + + + + + date identifies when the resource was issued + publication + + + + + date identifies when the resource was examined or re-examined and imporved or amended + revision + + + + + + + + function performed by the resource + CI_OnLineFunctionCode + + + online instructions for transferring data from one storage device or system to another + download + + + + + online information about the resource + information + + + + + online instructions for requesting the resource from the provider + offlineAccess + + + + + online order process for obtening the resource + order + + + + + online search interface for seeking out information about the resource + search + + + + + + + + mode in which the data is represented + CI_PresentationFormCode + + + digital representation of a primarily textual item (can contain illustrations also) + documentDigital + + + + + representation of a primarily textual item (can contain illustrations also) on paper, photograhic material, or other media + imageDigital + + + + + likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format + documentHardcopy + + + + + likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user + imageHardcopy + + + + + map represented in raster or vector form + mapDigital + + + + + map printed on paper, photographic material, or other media for use directly by the human user + mapHardcopy + + + + + multi-dimensional digital representation of a feature, process, etc. + modelDigital + + + + + 3-dimensional, physical model + modelHardcopy + + + + + vertical cross-section in digital form + profileDigital + + + + + vertical cross-section printed on paper, etc. + profileHardcopy + + + + + digital representation of facts or figures systematically displayed, especially in columns + tableDigital + + + + + representation of facts or figures systematically displayed, especially in columns, printed onpapers, photographic material, or other media + tableHardcopy + + + + + digital video recording + videoDigital + + + + + video recording on film + videoHardcopy + + + + + + + + function performed by the responsible party + CI_RoleCode + + + party that supplies the resource + resourceProvider + + + + + party that accepts accountability and responsability for the data and ensures appropriate care and maintenance of the resource + custodian + + + + + party that owns the resource + owner + + + + + party who uses the resource + user + + + + + party who distributes the resource + distributor + + + + + party who created the resource + originator + + + + + party who can be contacted for acquiring knowledge about or acquisition of the resource + pointOfContact + + + + + key party responsible for gathering information and conducting research + principalInvestigator + + + + + party wha has processed the data in a manner such that the resource has been modified + processor + + + + + party who published the resource + publisher + + + + + party who authored the resource + author + + + + + + + + type or method for evaluating an identified data quality measure + DQ_EvaluationMethodTypeCode + + + method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated + directInternal + + + + + method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required + directExternal + + + + + method of evaluating the quality of a dataset based on external knowledge + indirect + + + + + + + + justification for the correlation of two datasets + DS_AssociationTypeCode + + + reference from one dataset to another + crossReference + + + + + reference to a master dataset of which this one is a part + largerWorkCitation + + + + + part of the same structured set of data held in a computer + partOfSeamlessDatabase + + + + + mapping and charting information from which the dataset content originates + source + + + + + part of a set of imagery that when used together, provides three-dimensional images + stereoMate + + + + + + + + type of aggregation activity in which datasets are related + DS_InitiativeTypeCode + + + series of organized planned actions + campaign + + + + + accumulation of datasets assembled for a specific purpose + collection + + + + + specific performance of a function or group of functions + exercise + + + + + process designed to find if something is effective or valid + experiment + + + + + search or systematic inquiry + investigation + + + + + specific operation of a data collection system + mission + + + + + device or piece of equipment which detects or records + sensor + + + + + action that is part of a series of actions + operation + + + + + vehicle or other support base that holds a sensor + platform + + + + + method of doing something involving a number of steps + process + + + + + specific planned activity + program + + + + + organized undertaking, research, or development + project + + + + + examination or investigation + study + + + + + piece of work + task + + + + + process of testing to discover or demonstrate something + trial + + + + + + + + code indicating whether grid data is point or area + MD_CellGeometryCode + + + each cell represents a point + point + + + + + each cell represents an area + area + + + + + + + + name of the character coding standard used in the resource + MD_CharacterSetCode + + + 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 + ucs2 + + + + + 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 + ucs4 + + + + + 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf7 + + + + + 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf8 + + + + + 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 + utf16 + + + + + ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 + 8859part1 + + + + + ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 + 8859part2 + + + + + ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 + 8859part3 + + + + + ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 + 8859part4 + + + + + ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet + 8859part5 + + + + + ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet + 8859part6 + + + + + ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet + 8859part7 + + + + + ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet + 8859part8 + + + + + ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 + 8859part9 + + + + + ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 + 8859part10 + + + + + ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet + 8859part11 + + + + + + ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 + 8859part13 + + + + + ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) + 8859part14 + + + + + ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 + 8859part15 + + + + + ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 + 8859part16 + + + + + japanese code set used for electronic transmission + jis + + + + + japanese code set used on MS-DOS machines + shiftJIS + + + + + japanese code set used on UNIX based machines + eucJP + + + + + United States ASCII code set (ISO 646 US) + usAscii + + + + + IBM mainframe code set + ebcdic + + + + + Korean code set + eucKR + + + + + traditional Chinese code set used in Taiwan, Hong Kong of China and other areas + big5 + + + + + simplified Chinese code set + GB2312 + + + + + + + + name of the handling restrictions on the dataset + MD_ClassificationCode + + + available for general disclosure + unclassified + + + + + not for general disclosure + restricted + + + + + available for someone who can be entrusted with information + confidential + + + + + kept or meant to be kept private, unknown, or hidden from all but a select group of people + secret + + + + + of the highest secrecy + topSecret + + + + + + + + specific type of information represented in the cell + MD_CoverageContentTypeCode + + + meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter + image + + + + + code value with no quantitative meaning, used to represent a physical quantity + thematicClassification + + + + + value in physical units of the quantity being measured + physicalMeasurement + + + + + + + + datatype of element or entity + MD_DatatypeCode + + + descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior + class + + + + + descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior + codelist + + + + + data type whose instances form a list of named literal values, not extendable + enumeration + + + + + permissible value for a codelist or enumeration + codelistElement + + + + + class that cannot be directly instantiated + abstractClass + + + + + class that is composed of classes it is connected to by an aggregate relationship + aggregateClass + + + + + subclass that may be substituted for its superclass + specifiedClass + + + + + class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage + datatypeClass + + + + + named set of operations that characterize the behavior of an element + interfaceClass + + + + + class describing a selection of one of the specified types + unionClass + + + + + class whose instances are classes + metaClass + + + + + class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations + typeClass + + + + + free text field + characterString + + + + + numerical field + integer + + + + + semantic relationship between two classes that involves connections among their instances + association + + + + + + + + name of the dimension + MD_DimensionNameTypeCode + + + ordinate (y) axis + row + + + + + abscissa (x) axis + column + + + + + vertical (z) axis + vertical + + + + + along the direction of motion of the scan point + track + + + + + perpendicular to the direction of motion of the scan point + crossTrack + + + + + scan line of a sensor + line + + + + + element along a scan line + sample + + + + + duration + time + + + + + + + + name of point or vector objects used to locate zero-, one-, two-, or three-dimensional spatial locations in the dataset + MD_GeometricObjectTypeCode + + + set of geometric primitives such that their boundaries can be represented as a union of other primitives + complex + + + + + connected set of curves, solids or surfaces + composite + + + + + bounded, 1-dimensional geometric primitive, representing the continuous image of a line + curve + + + + + zero-dimensional geometric primitive, representing a position but not having an extent + point + + + + + bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space + solid + + + + + bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane + surface + + + + + + + + code which indicates conditions which may affect the image + MD_ImagingConditionCode + + + portion of the image is blurred + blurredImage + + + + + portion of the image is partially obscured by cloud cover + cloud + + + + + acute angle between the plane of the ecliptic (the plane of the Earth s orbit) and the plane of the celestial equator + degradingObliquity + + + + + portion of the image is partially obscured by fog + fog + + + + + portion of the image is partially obscured by heavy smoke or dust + heavySmokeOrDust + + + + + image was taken at night + night + + + + + image was taken during rainfall + rain + + + + + image was taken during semi-dark conditions -- twilight conditions + semiDarkness + + + + + portion of the image is obscured by shadow + shadow + + + + + portion of the image is obscured by snow + snow + + + + + the absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest + terrainMasking + + + + + + + + methods used to group similar keywords + MD_KeywordTypeCode + + + keyword identifies a branch of instruction or specialized learning + discipline + + + + + keyword identifies a location + place + + + + + keyword identifies the layer(s) of any deposited substance + stratum + + + + + keyword identifies a time period related to the dataset + temporal + + + + + keyword identifies a particular subject or topic + theme + + + + + + + + frequency with which modifications and deletions are made to the data after it is first produced + MD_MaintenanceFrequencyCode + + + data is repeatedly and frequently updated + continual + + + + + data is updated each day + daily + + + + + data is updated on a weekly basis + weekly + + + + + data is updated every two weeks + fortnightly + + + + + data is updated each month + monthly + + + + + data is updated every three months + quartely + + + + + data is updated twice each year + biannually + + + + + data is updated every year + annually + + + + + data is updated as deemed necessary + asNeeded + + + + + data is updated in intervals that are uneven in duration + irregular + + + + + there are no plans to update the data + notPlanned + + + + + frequency of maintenance for the data is not known + unknwon + + + + + + + + method used to write to the medium + MD_MediumFormatCode + + + CoPy In / Out (UNIX file format and command) + cpio + + + + + Tape ARchive + tar + + + + + high sierra file system + highSierra + + + + + information processing volume and file structure of CD-ROM + iso9660 + + + + + rock ridge interchange protocol (UNIX) + iso9660RockRidge + + + + + hierarchical file system (Macintosh) + iso9660AppleHFS + + + + + + + + name of the medium + MD_MediumNameCode + + + read-only optical disk + cdRom + + + + + digital versatile disk + dvd + + + + + digital versatile disk, read only + dvdRom + + + + + 3,5 inch magnetic disk + 3halfInchFloppy + + + + + 5,25 inch magnetic disk + 5quarterInchFloppy + + + + + 7 track magnetic tape + 7trackTape + + + + + 9 track magnetic tape + 9trackType + + + + + 3480 cartridge tape drive + 3480Cartridge + + + + + 3490 cartridge tape drive + 3490Cartridge + + + + + 3580 cartridge tape drive + 3580Cartridge + + + + + 4 millimetre magnetic tape + 4mmCartridgeTape + + + + + 8 millimetre magnetic tape + 8mmCartridgeTape + + + + + 0,25 inch magnetic tape + 1quarterInchCartridgeTape + + + + + half inch cartridge streaming tape drive + digitalLinearTape + + + + + direct computer linkage + onLine + + + + + linkage through a satellite communication system + satellite + + + + + communication through a telephone network + telephoneLink + + + + + pamphlet or leaflet giving descriptive information + hardcopy + + + + + + + + obligation of the element or entity + MD_ObligationCode + + + element is always required + mandatory + + + + + element is not required + optional + + + + + element is required when a specific condition is met + conditional + + + + + + + + point in a pixel corresponding to the Earth location of the pixel + MD_PixelOrientationCode + + + point halfway between the lower left and the upper right of the pixel + center + + + + + the corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value + lowerLeft + + + + + next corner counterclockwise from the lower left + lowerRight + + + + + next corner counterclockwise from the lower right + upperRight + + + + + next corner counterclockwise from the upper right + upperLeft + + + + + + + + status of the dataset or progress of a review + MD_ProgressCode + + + production of the data has been completed + completed + + + + + data has been stored in an offline storage facility + historicalArchive + + + + + data is no longer relevant + obsolete + + + + + data is continually being updated + onGoing + + + + + fixed date has been established upon or by which the data will be created or updated + planned + + + + + data needs to be generated or updated + required + + + + + data is currently in the process of being created + underDevelopment + + + + + + + + limitation(s) placed upon the access or use of the data + MD_RestrictionCode + + + exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor + copyright + + + + + government has granted exclusive right to make, sell, use or license an invention or discovery + patent + + + + + produced or sold information awaiting a patent + patentPending + + + + + a name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer + trademark + + + + + formal permission to do something + license + + + + + rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity + intellectualPropertyRights + + + + + withheld from general circulation or disclosure + restricted + + + + + limitation not listed + otherRestrictions + + + + + + + + class of information to which the referencing entity applies + MD_ScopeCode + + + information applies to the attribute class + attribute + + + + + information applies to the characteristic of a feature + attributeType + + + + + information applies to the collection hardware class + collectionHardware + + + + + information applies to the collection session + collectionSession + + + + + information applies to the dataset + dataset + + + + + information applies to the series + series + + + + + information applies to non-geographic data + nonGeographicDataset + + + + + information applies to a dimension group + dimensionGroup + + + + + information applies to a feature + feature + + + + + information applies to a feature type + featureType + + + + + information applies to a property type + propertyType + + + + + information applies to a field session + fieldSession + + + + + information applies to a computer program or routine + software + + + + + information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case + service + + + + + information applies to a copy or imitation of an existing or hypothetical object + model + + + + + information applies to a tile, a spatial subset of geographic data + tile + + + + + + + + method used to represent geographic information in the dataset + MD_SpatialRepresentationTypeCode + + + vector data is used to represent geographic data + vector + + + + + grid data is used to represent geographic data + grid + + + + + textual or tabular data is used to represent geographic data + textTable + + + + + triangulated irregular network + tin + + + + + three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images + stereoModel + + + + + scene from a video recording + video + + + + + + + + high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets. Can be used to group keywords as well. Listed examples are not exhaustive. + MD_TopicCategoryCode + + + rearing of animals and/or cultivation of plants. Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock + farming + + + + + flora and/or fauna in natural environment. Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat + biota + + + + + legal land descriptions. Examples: political and administrative boundaries + boundaries + + + + + processes and phenomena of the atmosphere. Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation + climatologyMeteorologyAtmosphere + + + + + economic activities, conditions and employment. Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas + economy + + + + + height above or below sea level. Examples: altitude, bathymetry, digital elevation models, slope, derived products + elevation + + + + + environmental resources, protection and conservation. Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape + environment + + + + + information pertaining to earth sciences. Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion + geoscientificInformation + + + + + health, health services, human ecology, and safety. Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services + health + + + + + base maps. Examples: land cover, topographic maps, imagery, unclassified images, annotations + imageryBaseMapsEarthCover + + + + + military bases, structures, activities. Examples: barracks, training grounds, military transportation, information collection + intelligenceMilitary + + + + + inland water features, drainage systems and their characteristics. Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts + inlandWaters + + + + + positional information and services. Examples: addresses, geodetic networks, control points, postal zones and services, place names + location + + + + + features and characteristics of salt water bodies (excluding inland waters). Examples: tides, tidal waves, coastal information, reefs + oceans + + + + + information used for appropriate actions for future use of the land. Examples: land use maps, zoning maps, cadastral surveys, land ownership + planningCadastre + + + + + characteristics of society and cultures. Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information + society + + + + + man-made construction. Examples: buildings, museums, churches, factories, housing, monuments, shops, towers + structure + + + + + means and aids for conveying persons and/or goods. Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways + transportation + + + + + energy, water and waste systems and communications infrastructure and services. Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks + utilitiesCommunication + + + + + + + + degree of complexity of the spatial relationships + MD_TopologyLevelCode + + + geometry objects without any additional structure which describes topology + geometryOnly + + + + + 1-dimensional topological complex -- commonly called chain-node topology + topology1D + + + + + 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) + planarGraph + + + + + 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment.) + fullPlanarGraph + + + + + 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) + surfaceGraph + + + + + 2-dimensional topological complex that is isomorphic to a subset of a surface + fullSurfaceGraph + + + + + 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) + topology3D + + + + + complete coverage of a 3D Euclidean coordinate space + fullTopology3D + + + + + topological complex without any specified geometric realisation + abstract + + + + + + + + Extension of MD_ScopeCode for the needs of GMX application schemas and in the context of a transfer + MX_ScopeCode + + + + information applies to the attribute class + attribute + + + + + information applies to the characteristic of a feature + attributeType + + + + + information applies to the collection hardware class + collectionHardware + + + + + information applies to the collection session + collectionSession + + + + + information applies to the dataset + dataset + + + + + information applies to the series + series + + + + + information applies to non-geographic data + nonGeographicDataset + + + + + information applies to a dimension group + dimensionGroup + + + + + information applies to a feature + feature + + + + + information applies to a feature type + featureType + + + + + information applies to a property type + propertyType + + + + + information applies to a field session + fieldSession + + + + + information applies to a computer program or routine + software + + + + + information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case + service + + + + + information applies to a copy or imitation of an existing or hypothetical object + model + + + + + information applies to a tile, a spatial subset of geographic data + tile + + + + + + The referencing entity applies to a transfer aggregate which was originally identified as an initiative (DS_Initiative) + initiative + + + + + The referencing entity applies to a transfer aggregate which was originally identified as a stereo mate (DS_StereoMate) + stereomate + + + + + The referencing entity applies to a transfer aggregate which was originally identified as a sensor (DS_Sensor) + sensor + + + + + The referencing entity applies to a transfer aggregate which was originally identified as a platform series (DS_PlatformSeries) + platformSeries + + + + + The referencing entity applies to a transfer aggregate which was originally identified as a sensor series (DS_SensorSeries) + sensorSeries + + + + + The referencing entity applies to a transfer aggregate which was originally identified as a production series (DS_ProductionSeries) + productionSeries + + + + + The referencing entity applies to a transfer aggregate which has no existence outside of the transfer context + transferAggregate + + + + + The referencing entity applies to a transfer aggregate which has an existence outside of the transfer context, but which does not pertains to a specific aggregate type. + otherAggregate + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/ML_gmxCrs.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/ML_gmxCrs.xml new file mode 100644 index 0000000..15acb62 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/ML_gmxCrs.xml @@ -0,0 +1 @@ + ML_gmxCrs CRS catalogue for description of gmx metadata dataset Catalogue des paramètres géodésiques pour la description de jeux de métadonnées conformes aux schémas gmx GMX (and imported) namespace 0.0 2005-03-29 English UTF 8 French France UTF 8 4326 WGS84G World Geodetic System 1984 World not known 4326 WGS84G WGS 1984 Monde inconnu 6422 ellipsoidal2Ddeg 9901 Geodetic latitude Lat North 9902 Geodetic longitude Lon East 6326 World Geodetic System 1984 not known 7030 WGS 84 6378137 298.2572 8901 Greenwich 0 \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/gmxCrs.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/gmxCrs.xml new file mode 100644 index 0000000..e27ab3e --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/crs/gmxCrs.xml @@ -0,0 +1 @@ + gmxCrs CRS parameters dictionary GMX (and imported) namespace 0.0 2005-03-18 4326 WGS84G World Geodetic System 1984 World: Afghanistan, Albania, Algeria, American Samoa, Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Australia, Austria, Azerbaijan, Bahamas, Bahrain, Bangladesh, Barbados, Belgium, Belgium, Belize, Benin, Bermuda, Bhutan, Bolivia, Bosnia and Herzegowina, Botswana, Bouvet Island, Brazil, British Indian Ocean Territory, British Virgin Islands, Brunei Darussalam, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Canada, Cape Verde, Cayman Islands, Central African Republic, Chad, Chile, China, Christmas Island, Cocos (Keeling) Islands, Comoros, Congo, Cook Islands, Costa Rica, Côte d'Ivoire (Ivory Coast), Croatia, Cuba, Cyprus, Czech Republic, Denmark, Djibouti, Dominica, Dominican Republic, East Timor, Ecuador, Egypt, El Salvador, Equatorial Guinea, Eritrea, Estonia, Ethiopia, Falkland Islands (Malvinas), Faroe Islands, Fiji, Finland, France, French Guiana, French Polynesia, French Southern Territories, Gabon, Gambia, Georgia, Germany, Ghana, Gibraltar, Greece, Greenland, Grenada, Guadeloupe, Guam, Guatemala, Guinea, Guinea-Bissau, Guyana, Haiti, Heard Island and McDonald Islands, Holy See (Vatican City State), Honduras, China - Hong Kong, Hungary, Iceland, India, Indonesia, Islamic Republic of Iran, Iraq, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kazakstan, Kenya, Kiribati, Democratic People's Republic of Korea (North Korea), Republic of Korea (South Korea), Kuwait, Kyrgyzstan, Lao People's Democratic Republic (Laos), Latvia, Lebanon, Lesotho, Liberia, Libyan Arab Jamahiriya, Liechtenstein, Lithuania, Luxembourg, China - Macau, The Former Yugoslav Republic of Macedonia, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Marshall Islands, Martinique, Mauritania, Mauritius, Mayotte, Mexico, Federated States of Micronesia, Monaco, Mongolia, Montserrat, Morocco, Mozambique, Myanmar (Burma), Namibia, Nauru, Nepal, Netherlands, Netherlands Antilles, New Caledonia, New Zealand, Nicaragua, Niger, Nigeria, Niue, Norfolk Island, Northern Mariana Islands, Norway, Oman, Pakistan, Palau, Panama, Papua New Guinea (PNG), Paraguay, Peru, Philippines, Pitcairn, Poland, Portugal, Puerto Rico, Qatar, Reunion, Romania, Russian Federation, Rwanda, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the Grenadines, Samoa, San Marino, Sao Tome and Principe, Saudi Arabia, Senegal, Seychelles, Sierra Leone, Singapore, Slovakia (Slovak Republic), Slovenia, Solomon Islands, Somalia, South Africa, South Georgia and the South Sandwich Islands, Spain, Sri Lanka, Saint Helena, Saint Pierre and Miquelon, Sudan, Suriname, Svalbard and Jan Mayen, Swaziland, Sweden, Switzerland, Syrian Arab Republic, Taiwan, Tajikistan, United Republic of Tanzania, Thailand, The Democratic Republic of the Congo (Zaire), Togo, Tokelau, Tonga, Trinidad and Tobago, Tunisia, Turkey, Turkmenistan, Turks and Caicos Islands, Tuvalu, Uganda, Ukraine, United Arab Emirates (UAE), United Kingdom (UK), United States (USA), United States Minor Outlying Islands, Uruguay, Uzbekistan, Vanuatu, Venezuela, Vietnam, US Virgin Islands, Wallis and Futuna, Western Sahara, Yemen, Yugoslavia - Union of Serbia and Montenegro, Zambia, Zimbabwe. not known 32638 UTM38W84 WGS 84 / UTM zone 38N Between 42 and 48 deg East; northern hemisphere. Armenia. Azerbaijan. Djibouti. Eritrea. Ethiopia. Georgia. Islamic Republic of Iran. Iraq. Kazakstan. Kuwait. Russian Federation. Saudi Arabia. Somalia. Tukey. Yemen. not known Ellipsoidal 2D CS. Axes: latitude, longitude. Orientations: north, east. UoM: deg 6422 CS ellipsoidal2D Cartesian 2D CS. Axes: easting, northing (E,N). Orientations: east, north. UoM: m. 4400 Cs cartesian2D 9901 Geodetic latitude Lat North 9902 Geodetic longitude Lon East 9907 Northing N North 9906 Easting E east 6326 World Geodetic System 1984 not known 7030 WGS 84 6378137 298.2572 8901 Greenwich 0 16038 UTM Zone 38 N not known 0 45 0.9996 500000 0 9807 PRCM040 Transverse Mercator Transverse Mercator 2 2 8801 Latitude of natural origin 8802 Longitude of natural origin 8805 Scale factor at natural origin 8806 False Easting 8807 False Northing \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/example/fr-fr.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/example/fr-fr.xml new file mode 100644 index 0000000..cf4c6b3 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/example/fr-fr.xml @@ -0,0 +1 @@ + France-France French FR UTF 8 2005-03-18 création 2006-02-03 révision french translation team auteur Résumé succint du contenu du jeu de données \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/ML_gmxUom.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/ML_gmxUom.xml new file mode 100644 index 0000000..8b1c404 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/ML_gmxUom.xml @@ -0,0 +1 @@ + uom units of measure dictionary compliant with SI definitions dictionnaire d'unités de mesure conforme avec les définitions du Système International (SI) GMX (and imported) namespace 0.0 2005-06-18 English UTF 8 French France UTF 8 The metre is the length of the path travelled by ligth in vaccum during a time interval of 1/299 792 458 of a second metre length m unité de longueur de référence dans le système international, correspond à la distance parcourue par la lumière dans le vide pendant 1/299 792 458 seconde metre mètre longueur Measure of angle equal to Pi/180 radians, widely used in geography degree angle 1.74532925199433E-02 Unité d'angle de référence en géographie égale à Pi/180 radians. degree degré angle Radian is an unit of angle measure. It is defined as the ratio of arc length to the radius of the circle. radian plane angle rad Le radian est une unité de mesaure angulaire définie comme le ratio entre le rayon et la longueur de l'arc. radian radian angle planaire \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/gmxUom.xml b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/gmxUom.xml new file mode 100644 index 0000000..61c119a --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/ISO_19139_Schemas/resources/uom/gmxUom.xml @@ -0,0 +1 @@ + gmxUom units of measure dictionary compliant with SI definitions ISO/TC 211 GMX (and imported) namespace 0.0 2005-03-18 The metre is the length of the path travelled by ligth in vaccum during a time interval of 1/299 792 458 of a second metre length m Measure of angle equal to Pi/180 radians, widely used in geography degree angle 1.74532925199433E-02 Radian is an unit of angle measure. It is defined as the ratio of arc length to the radius of the circle. radian plane angle rad \ No newline at end of file diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/README.txt b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/README.txt new file mode 100644 index 0000000..fc27e10 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/README.txt @@ -0,0 +1,21 @@ +AIXM_WX is an AIXM Profile for use in the weather community. This profile is based +on AIXM 5.1, which was released on 2010-02-01. As an AIXM profile, this schema is identical +to AIXM 5.1 except that unneeded AIXM content has been removed. This profile +may be used in XML schemaLocations as an alternative to the original AIXM 5.1 +schema. + +The AIXM_WX profile contains those portions of AIXM that are needed to identify and locate +aeronautical regions related to weather reporting. This profile includes a selected set of +properties from the following AIXM types: + + -AirportHeliport + -Airspace + -AirspaceVolume + -Runway + -RunwayDirection + -Unit + +Two files differ from the original AIXM versions: AIXM_Features.xsd and AIXM_DataTypes.xsd. +All other files are unchanged. + +Questions or comments may be directed to braeckel AT ucar.edu diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/message/AIXM_BasicMessage.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/message/AIXM_BasicMessage.xsd new file mode 100644 index 0000000..24f0818 --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/message/AIXM_BasicMessage.xsd @@ -0,0 +1,58 @@ + + + + + + + + + + + + + + + Basic Message.xsd + The definition of a simple data product, that contains just a collection of AIXM features. + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/xlink/xlinks.xsd b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/xlink/xlinks.xsd new file mode 100644 index 0000000..faef81d --- /dev/null +++ b/config/schemas/schema/aero/aixm/5.1_profiles/AIXM_WX/5.1a/xlink/xlinks.xsd @@ -0,0 +1,122 @@ + + + + + xlinks.xsd v3.0b2 2001-07 + + GML 3.0 candidate xlinks schema. Copyright (c) 2001 OGC, All Rights Reserved. + + + + + + + + + + + + + + The 'show' attribute is used to communicate the desired presentation + of the ending resource on traversal from the starting resource; it's + value should be treated as follows: + new - load ending resource in a new window, frame, pane, or other + presentation context + replace - load the resource in the same window, frame, pane, or + other presentation context + embed - load ending resource in place of the presentation of the + starting resource + other - behavior is unconstrained; examine other markup in the + link for hints + none - behavior is unconstrained + + + + + + + + + + + + + + + + The 'actuate' attribute is used to communicate the desired timing + of traversal from the starting resource to the ending resource; + it's value should be treated as follows: + onLoad - traverse to the ending resource immediately on loading + the starting resource + onRequest - traverse from the starting resource to the ending + resource only on a post-loading event triggered for + this purpose + other - behavior is unconstrained; examine other markup in link + for hints + none - behavior is unconstrained + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/collect/1.0/collect.xsd b/config/schemas/schema/int/wmo/collect/1.0/collect.xsd new file mode 100644 index 0000000..a22fea5 --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.0/collect.xsd @@ -0,0 +1,43 @@ + + + + + + A Meteorological Bulletin is a text comprising meteorological information preceded by an appropriate heading. + +Paragraph 2.3.3 of the WMO Manual on the Global Telecommunication System (WMO No. 386) defines the contents of meteorological bulletins. Clauses applicable here include: + + - The text of a bulletin shall be in one code form only. + - The text of a bulletin shall not contain both ¡§essential¡¨ and ¡§additional¡¨ data as defined in Resolution 40 (Cg-XII). + + + + + + + + + General file naming convention described in Attachment II-15 to WMO Manual on the Global Telecommunication System (WMO No. 386) is being used for bulletinIdentifier, which also makes references to the abbreviated headings described in Paragraph 2.3.2. + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/collect/1.1/collect.xsd b/config/schemas/schema/int/wmo/collect/1.1/collect.xsd new file mode 100644 index 0000000..b48950a --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.1/collect.xsd @@ -0,0 +1,43 @@ + + + + + + A Meteorological Bulletin is a text comprising meteorological information preceded by an appropriate heading. + +Paragraph 2.3.3 of the WMO Manual on the Global Telecommunication System (WMO No. 386) defines the contents of meteorological bulletins. Clauses applicable here include: + + - The text of a bulletin shall be in one code form only. + - The text of a bulletin shall not contain both ¡§essential¡¨ and ¡§additional¡¨ data as defined in Resolution 40 (Cg-XII). + + + + + + + + + General file naming convention described in Attachment II-15 to WMO Manual on the Global Telecommunication System (WMO No. 386) is being used for bulletinIdentifier, which also makes references to the abbreviated headings described in Paragraph 2.3.2. + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/collect/1.2/collect.xsd b/config/schemas/schema/int/wmo/collect/1.2/collect.xsd new file mode 100644 index 0000000..7e73d65 --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.2/collect.xsd @@ -0,0 +1,56 @@ + + + + + The WMO Feature Collection Model is used to represent a collection of GML feature instances of the same type of meteorological information. The intent is to allow XML encoded meteorological information to be packaged in a way that emulates the existing data distribution practices used within the Global Telecommunication System (GTS) and Aeronautical Fixed System (AFS). + +Note: The collection of meteorological information is often referred to as a bulletin. + +Note: XML encodings of meteorological information are defined in Part D; for example FM 205-15 EXT IWXXM-XML. + +Note: Aggregation of meteorological information in form of meteorological bulletins usually takes place at a station or centre originating or compiling the bulletin, as agreed internationally. A meteorological bulletin may have one or more instances of meteorological information. If meteorological reports of routine messages are not available during compilation, a NIL report of that station should be included in the published contents of the bulletin. + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + gmlcollect.xsd + + + + + A Meteorological Bulletin is a text comprising meteorological information preceded by an appropriate heading. + +Paragraph 2.3.3 of the WMO Manual on the Global Telecommunication System (WMO No. 386) defines the contents of meteorological bulletins. Clauses applicable here include: + + - The text of a bulletin shall be in one code form only. + - The text of a bulletin shall not contain both “essential” and “additional” data as defined in Resolution 40 (Cg-XII). + + + + + + + + + + General file naming convention described in Attachment II-15 to WMO Manual on the Global Telecommunication System (WMO No. 386) is being used for bulletinIdentifier, which also makes references to the abbreviated headings described in Paragraph 2.3.2. + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/collect/1.2/gmlcollect.xsd b/config/schemas/schema/int/wmo/collect/1.2/gmlcollect.xsd new file mode 100644 index 0000000..036189b --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.2/gmlcollect.xsd @@ -0,0 +1,430 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + diff --git a/config/schemas/schema/int/wmo/collect/1.2RC1/collect.xsd b/config/schemas/schema/int/wmo/collect/1.2RC1/collect.xsd new file mode 100644 index 0000000..7261560 --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.2RC1/collect.xsd @@ -0,0 +1,55 @@ + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + The WMO Feature Collection Model is used to represent a collection of GML feature instances of the same type of meteorological information. The intent is to allow XML encoded meteorological information to be packaged in a way that emulates the existing data distribution practices used within the Global Telecommunication System (GTS) and Aeronautical Fixed System (AFS). + +Note: The collection of meteorological information is often referred to as a bulletin. + +Note: XML encodings of meteorological information are defined in Part D; for example FM 205-15 EXT IWXXM-XML. + +Note: Aggregation of meteorological information in form of meteorological bulletins usually takes place at a station or centre originating or compiling the bulletin, as agreed internationally. A meteorological bulletin may have one or more instances of meteorological information. If meteorological reports of routine messages are not available during compilation, a NIL report of that station should be included in the published contents of the bulletin. + + gmlcollect.xsd + + + + + A Meteorological Bulletin is a text comprising meteorological information preceded by an appropriate heading. + +Paragraph 2.3.3 of the WMO Manual on the Global Telecommunication System (WMO No. 386) defines the contents of meteorological bulletins. Clauses applicable here include: + + - The text of a bulletin shall be in one code form only. + - The text of a bulletin shall not contain both “essential” and “additional” data as defined in Resolution 40 (Cg-XII). + + + + + + + + + + General file naming convention described in Attachment II-15 to WMO Manual on the Global Telecommunication System (WMO No. 386) is being used for bulletinIdentifier, which also makes references to the abbreviated headings described in Paragraph 2.3.2. + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/collect/1.2RC1/gmlcollect.xsd b/config/schemas/schema/int/wmo/collect/1.2RC1/gmlcollect.xsd new file mode 100644 index 0000000..036189b --- /dev/null +++ b/config/schemas/schema/int/wmo/collect/1.2RC1/gmlcollect.xsd @@ -0,0 +1,430 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0/common.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0/common.xsd new file mode 100644 index 0000000..e65dd0e --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0/common.xsd @@ -0,0 +1,253 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Common constructs used across multiple packages. This package includes constructs + closely related to the aviation weather domain. + + + Schematron validation + + + + + + + + + + + + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/verticalVisibility + + The vertical visibility. Vertical visibility is defined as the vertical visual range + into an obscuring medium. + + quantity: http://codes.wmo.int/common/c-15/ae/verticalVisibility + + + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. This extends AerodromeSurfaceWindTrendForecast + to allow for a variable wind direction to be reported. This class differs from a + aerodrome wind observation in that the observations may include a min/max directional + variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type + + + + + + + The observed cloud amount + + + + + + http://codes.wmo.int/common/c-15/me/heightOfBaseOfCloud + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at + which the air contains a perceptible quantity of cloud particles. + + quantity: http://codes.wmo.int/common/c-15/me/heightOfBaseOfCloud + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The forecast average wind direction from which wind is blowing + quantity: http://codes.wmo.int/common/c-15/me/windDirection + + + + + + + http://codes.wmo.int/common/c-15/me/windSpeed + + The forecast average wind speed + quantity: http://codes.wmo.int/common/c-15/me/windSpeed + + + + + + + http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + The forecast maximum speed of a gust. + quantity: http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + + + + + + + + + + + + + RelationalOperator defines the restricted set of operators that may be specified alongside + numerical quantities in ICAO Annex 3/WMO No. 49. These operators are used in cases + where a precise value is not measurable, not precisely known due to measurement limitations, + or not reported due to reporting restrictions. For example, the "above" operator + in conjunction with the reported quantity 10.6 indicates that the actual physical + quantity is above 10.6 (at least 10.6). + + + + + + The actual value is above the maximum value that can be determined by the system ("ABV", + "P") + + + + + + The actual value is below the minimum value that can be determined by the system ("BLW", + "M") + + + + + + + + + http://codes.wmo.int/49-2/AerodromeForecastWeather + none + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + Only a specific set of weather phenomenon are reported within aviation meteorology + as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This ?CodeList? is specifically + defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions + are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromeForecastWeather + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/SigConvectiveCloudType + none + + Genus of cloud of operational significance to aviation: significant convective clouds + only. - Cumulonimbus - Towering cumulus This ?CodeList? is specifically defined + for aviation purposes, as defined in WMO No. 49-2. A superset of definitions are defined + in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 012 "Cloud type". + + vocabulary: http://codes.wmo.int/49-2/SigConvectiveCloudType + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + none + + Amount of cloud - assessed by category: - Sky clear (0 oktas) - Few (1 - 2 oktas) + - Scattered (3 - 4 oktas) - Broken (5 - 7 oktas) - Overcast (8 oktas) This ?CodeList? + is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset + of cloud-amount categories are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 20 008 "Cloud distribution for aviation". + + vocabulary: http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + extensibility: none + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0/iwxxm.xsd new file mode 100644 index 0000000..2cf8d36 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0/iwxxm.xsd @@ -0,0 +1,37 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, + SPECI, TAF, and SIGMET reports as defined in ICAO Annex 3, Amendment 76. These four + reports are essential operational meteorology products used to enable safe and efficient + air travel worldwide. The report types in this package include: <b> </b><b>== </b>METAR + <b>==</b> Routine report of meteorological conditions made at an aerodrome. METARs + may also include short-term forecasts of meteorological conditions <b> </b>== SPECI + == Special (i.e., non-routine) report of meteorological conditions made at an aerodrome + as needed. SPECIs may also include short-term forecasts of meteorological conditions + <b> </b>== TAF == Routine forecast report of meteorological conditions at an aerodrome + <b> </b>== SIGMET == Meteorological advisory concerning the occurrence and/or expected + occurrence of weather phenomena which may affect the safety of aircraft operations, + such as severe thunderstorms or turbulence This package builds upon the ISO 19100 + family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, + the constructs in this application schema refer to a number of aviation constructs + such as FIR, Aerodrome, and Runway from the Simple Aviation Features package. The + full relationship of this package with external dependencies are shown in the 'Package + Dependencies' diagram. While only four of the reports from Annex 3 are currently + represented, this may be expanded in a future version. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0/metarSpeci.xsd new file mode 100644 index 0000000..1c1257b --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0/metarSpeci.xsd @@ -0,0 +1,1042 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. METAR + and SPECI reports include identical information but are issued for different purposes. + METAR reports are routine observations made at an aerodrome throughout the day. METAR + observations are made (and distributed) at intervals of one hour or, if so determined + by regional air navigation agreement, at intervals of one half-hour. SPECI reports + are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI + observations are made (and distributed) in accordance with criteria established by + the meteorological authority, in consultation with the appropriate ATS authority, + operators and others concerned. + + + Schematron validation + + + + + + + + + + + + + + + + + + A report of observed and trend forecast weather phenomenon from the surface near an + aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical + reported information. + + + + + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast. When no change is expected to occur + during a forecast period ("NOSIG") this is indicated by a single missing trend forecast + with a nil reason of noSignificantChange + + + + + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations + are made (and distributed) in accordance with criteria established by the meteorological + authority, in consultation with the appropriate ATS authority, operators and others + concerned. The information contained in METAR and SPECI is identical. SPECI is issued + when conditions merit a non-routine report on conditions at an aerodrome. SPECI reports + are used for dissemination beyond the aerodrome of origin (mainly intended for flight + planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly intervals. + SPECI is issued following the resumption of the issuance of METAR, as necessary, at + aerodromes that are not operational throughout 24 hours in accordance with ICAO Annex + 3 Section 4.3.1. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations + are made (and distributed) at intervals of one hour or, if so determined by regional + air navigation agreement, at intervals of one half-hour. The information contained + in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine + report on conditions at an aerodrome. METARs are a routine report produced for dissemination + beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET + broadcasts and D-VOLMET. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions for trend forecasting + at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord + which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the NothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. When no clouds + were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason + should be used for the cloud association. + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The prevailing horizontal visibility reported in a trend forecast + quantity: http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions observed at an aerodrome. + When no clouds of operational significance or no weather of operational significance + is observed, the NothingOfOperationalSignificance nilReason is used for the cloud + or presentWeather association. When no clouds were detected by the automatic observing + system, the NotDetectedByAutoSystem nilReason is used for the cloud association. + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The observed air temperature. This is the temperature indicated by a thermometer + exposed to the air in a place sheltered from direct solar radiation. + + quantity: http://codes.wmo.int/common/c-15/me/airTemperature + + + + + + + http://codes.wmo.int/common/c-15/me/dewPointTemperature + + The observed dew point temperature. This is the temperature to which a given air + parcel must be cooled at constant pressure and constant water vapor content in order + for saturation to occur. + + quantity: http://codes.wmo.int/common/c-15/me/dewPointTemperature + + + + + + + http://codes.wmo.int/common/c-15/me/altimeterSettingQnh + + The observed QNH altimeter setting. Altitude setting (also known as QNH) is defined + as barometric pressure adjusted to sea level. It is a pressure setting used by pilots, + air traffic control (ATC), and low frequency weather beacons to refer to the barometric + setting which, when set on an aircraft's altimeter, will cause the altimeter to read + altitude above mean sea level within a certain defined region. + + quantity: http://codes.wmo.int/common/c-15/me/altimeterSettingQnh + + + + + + + + + + + + + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including + the runway contamination, friction, and deposits. + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + + + + + + The runway to which the conditions apply. The runway may be missing in cases where + all runways are closed due to snow + + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. WMO 306: Table + 0919 + + + + + + + http://codes.wmo.int/common/c-15/ae/runwayContamination + + Proportion of runway surface that is contaminated - usually expressed as a percentage + of the total runway area. WMO reporting procedures require that contamination is + reported in the following categories: - less than 10%; - between 11% and 25%; - between + 26% and 50%; and - more than 50%. See WMO No. 306: - WMO Code table 0519 - BUFR + Code table 0 20 087 + + quantity: http://codes.wmo.int/common/c-15/ae/runwayContamination + + + + + + + http://codes.wmo.int/common/c-15/ae/depthOfRunwayDeposit + + Depth of deposit on the surface of the runway. See WMO No. 306 WMO Code table 1079. + quantity: http://codes.wmo.int/common/c-15/ae/depthOfRunwayDeposit + + + + + + + http://codes.wmo.int/common/c-15/ae/runwayFrictionCoefficient + + The estimated surface friction for the affected runway. Between 0.0 and 0.9. When + braking conditions are not reported and/or the runway is not operational estimatedSurfaceFriction + will not be reported. WMO 306: Table 0366 + + quantity: http://codes.wmo.int/common/c-15/ae/runwayFrictionCoefficient + + + + + + + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported + together at an aerodrome + + + + + + + + The runway to which reported runway visual range information applies + + + + + + http://codes.wmo.int/common/c-15/ae/runwayVisualRangeRvr + + The mean recent runway visual range value observed. This mean represents the 10 minute + average for observed RVR except when the 10-minute period immediately preceding the + observation includes a marked discontinuity in runway visual range values, only those + values occurring after the discontinuity is used for obtaining mean values. To report + a mean RVR of at least 2000 meters, mean RVR is reported as 2000 meters and the operator + is reported as "above" Annex 3: Table A3-2 "RVR/RVR" Section 4.3.6.6 + + quantity: http://codes.wmo.int/common/c-15/ae/runwayVisualRangeRvr + + + + + + The reported relational operator for the mean RVR. When reported, this operator is + reported in conjunction with mean RVR. To report a mean RVR of at least 2000 meters, + mean RVR is reported as 2000 meters and the operator is reported as "above". When + no operator is reported, mean RVR represents an exact value with identical semantics + to other measured quantities + + + + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. + This includes information on sea-surface temperature and either the state of the sea + or significant wave height from aeronautical meteorological stations established on + offshore structures in support of helicopter operations + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + + + + + + + http://codes.wmo.int/common/c-15/oc/seaSurfaceTemperature + + The sea-surface temperature observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations. The term sea surface + temperature is generally meant to be representative of the upper few meters of the + ocean as opposed to the skin temperature, which is the temperature of the upper few + centimeters. ICAO Annex 3 / WMO No. 49-2: Section 4.8.1.5a + + quantity: http://codes.wmo.int/common/c-15/oc/seaSurfaceTemperature + + + + + + The significant wave height observed + + + + + The state of the sea observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations ICAO Annex 3 / WMO No. + 49-2: Section 4.8.1.5a WMO 306: Table 3700 + + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, + including the set of affected runways. + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + + + + + + The specific runway(s) affected by wind shear at this aerodrome. No specific runways + are reported when all runways are affected by wind shear + + + + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, + including cloud types, cloud layers, and vertical visibility. + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/verticalVisibility + + The reported vertical visibility. Vertical visibility is defined as the vertical + visual range into an obscuring medium. Note: vertical visibility is only reported + in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus + prevailing visibility is considered to be an aviation-specific quantity. When the + sky is obscured and the value of the vertical visibility cannot be determined by the + automatic observing system due to a temporary failure of the system/sensor ("VV///") + the vertical visibility is missing with a nil reason of notObservable + + quantity: http://codes.wmo.int/common/c-15/ae/verticalVisibility + + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, + including wind direction information, wind speed, and wind gusts. Wind direction + is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: "variations + from the mean wind direction during the past 10 minutes is reported as follows, if + the total variation is 60 or more: 1) when the total variation is 60 or more and less + than 180 and the wind speed is 1.5 m/s (3 kt) or more, such directional variations + are reported as the two extreme directions between which the surface wind has varied; + 2) when the total variation is 60 or more and less than 180 and the wind speed is + less than 1.5 m/s (3 kt), the wind direction is reported as variable with no mean + wind direction; or 3) when the total variation is 180 or more, the wind direction + is reported as variable with no mean wind direction" + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The observed average wind direction from which the wind is blowing over the past ten + minutes. Not reported when winds are variable + + quantity: http://codes.wmo.int/common/c-15/me/windDirection + + + + + + + http://codes.wmo.int/common/c-15/me/windSpeed + + The average observed wind speed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2a + + quantity: http://codes.wmo.int/common/c-15/me/windSpeed + + + + + + + http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + The maximum wind speed observed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2c + + quantity: http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The extreme clockwise direction from which the wind is blowing, inclusive. ICAO Annex + 3 / WMO No. 49-2: Section 4.1.5.2b + + quantity: http://codes.wmo.int/common/c-15/me/windDirection + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The extreme counter-clockwise direction from which the wind is blowing, inclusive. + ICAO Annex 3 / WMO No. 49-2: Section 4.1.5.2b + + quantity: http://codes.wmo.int/common/c-15/me/windDirection + + + + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at + an aerodrome, including the prevailing visibility and minimum visibility. + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The reported prevailing horizontal visibility at the surface that is representative + of the aerodrome. The greatest visibility value, observed in accordance with the + definition of "visibility", which is reached within at least half the horizon circle + or within at least half of the surface of the aerodrome. These areas could comprise + contiguous or non-contiguous sectors. Note: This value may be assessed by human observation + and/or instrumented systems. When instruments are installed, they are used to obtain + the best estimate of the prevailing visibility. To report a prevailing visibility + of at least 10000 meters, prevailing visibility is reported as 10000 meters and the + prevailing visibility operator is reported as "above". ICAO Annex 3 / WMO No. 49-2: + Section 4.2.4.4b + + quantity: http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + http://codes.wmo.int/common/c-15/ae/minimumHorizontalVisibility + + The minimum observed visibility. ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: "When + the visibility is not the same in different directions and a) when the lowest visibility + is different from the prevailing visibility, and 1) less than 1 500 m or 2) + less than 50 percent of the prevailing visibility and less than 5000 m; the lowest + visibility observed should also be reported and,when possible, its general direction + in relation to the aerodrome reference point indicated by reference to one of the + eight points of the compass. If the lowest visibility is observed in more than one + direction, then the most operationally significant direction should be reported; and + b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot + be determined, only the lowest visibility should be reported, with no indication of + direction." + + quantity: http://codes.wmo.int/common/c-15/ae/minimumHorizontalVisibility + + + + + + + http://codes.wmo.int/common/c-15/ae/minimumVisibilityDirection + + The direction of the minimum visibility relative to the reporting station. This is + optional in cases where minimum visibility is reported but the visibility is fluctuating + rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions + (N, NE, E, SE, S, SW, W, and NW) + + quantity: http://codes.wmo.int/common/c-15/ae/minimumVisibilityDirection + + + + + + + + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. Defined in WMO + No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. Also see WMO No. 306 Vol + I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or + an aerodrome forecast'. + + + + + + No significant changes are forecast (NOSIG) + + + + + When the change is forecast to commence at the beginning of the forecast period and + be completed by the end of that period, or when the change is forecast to occur within + the forecast period but the time of the change is uncertain (possibly shortly after + the beginning of the forecast period, or midway or near the end of that period), the + change is indicated by only the change indicator BECMG. + + + + + + The change indicator TEMPO is used to describe expected temporary fluctuations to + meteorological conditions which reach or pass specified threshold criteria and last + for a period of less than one hour in each instance and in the aggregate cover less + than half of the forecast period during which the fluctuations are expected to occur. + + + + + + + + The tendency of visual range (e.g., upward, downward). Defined for the purposes of + aviation meteorology reporting of the visual range on runways (WMO No. 49-2). If + the [runway] visual range (RVR) values during the 10-minute period preceding the nominal + observation time show a distinct upward or downward tendency such that the mean during + the first five minutes varies by 100 metres or more from the mean in the second five + minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency is recorded. When no + distinct change in RVR is observed, NO CHANGE [N] is recorded. See WMO No. 306 Vol + I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visual range". + + + + + + Upward (increasing) tendency + + + + + No change + + + + + Downward (decreasing) tendency + + + + + + + The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, + correction of an earlier report, etc.) + + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + + + + http://codes.wmo.int/49-2/AerodromeRecentWeather + none + + Weather phenomenon of operational significance to aviation observed during the period + since the last routine report, or last hour, whichever is shorter, but not at the + time of observation. Only a specific set of weather phenomenon are reported within + aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This CodeList + is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset + of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather + phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromeRecentWeather + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-22-061 + none + + Categorical assessment of sea surface state (or other large open body of water) based + on height of waves. Height in metres : Category - 0 metres : Calm (glassy) - 0-0.1 + metres : Calm (rippled) - 0.1-0.5 metres : Smooth - 0.5-1.25 metres : Slight - 1.25-2.5 + metres : Moderate - 2.5-4 metres : Rough - 4-6 metres : Very rough - 6-9 metres : + High - 9-14 metres : Very high - &gt;14 metres : Phenomenal See WMO No. 306 Vol I.1 + code table 3700 "State of the sea" and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 + 22 061 "State of the sea". + + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-22-061 + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-20-086 + none + + Type of deposit on a runway. See WMO No. 306 Vol I.1 code table 0919 and WMO No. + 306 Vol I.2 FM 94 BUFR code table 0 20 086 "Runway deposits". + + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-20-086 + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-20-087 + none + + Extent of runway surface that is contaminated (covered) + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-20-087 + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/AerodromePresentWeather + none + + The present weather observed at, or in near vicinity of, an aerodrome. Only a specific + set of weather phenomenon are reported within aviation meteorology as defined in Regulation + ICAO Annex 3 / WMO No. 49-2. This CodeList is specifically defined for aviation purposes + as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol + I.1 code-table 4678 "Significant weather phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromePresentWeather + extensibility: none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0/sigmet.xsd new file mode 100644 index 0000000..be21b34 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0/sigmet.xsd @@ -0,0 +1,456 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. SIGMETs report + the occurrence and/or expected occurrence of specified en-route weather phenomena + which may affect the safety of aircraft operations, and of the development of those + phenomena in time and space. These weather phenomena are reported as impacted regions + of airspace. + + + Schematron validation + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. + TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. + For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit + of 500FL. In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA + or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to + the sampled feature for this SIGMET. + + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, + volcanic ash, etc.). This geometry covers all combinations of phenomenon historically + reported in Annex 3: a boundary with a base and top, a TC center position, and a VA + line with a width + + + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or + expected occurrence of specified en-route weather phenomena which may affect the safety + of aircraft operations, and of the development of those phenomena over time. The + SIGMET report class represents the base SIGMET types that may be reported such as + squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic + ash SIGMET reports are subclasses of SIGMET due to their ability to report additional + information, including volcano/tropical cyclone identification and forecast position(s). + SIGMETs may report either observed or forecast hazardous conditions. Additionally, + a forecast position may be reported. + + + + + + + + + + The ATS unit serving the FIR or CTA to which the SIGMET refers ICAO Annex 3 / WMO + No. 49-2: A6-1: "Location indicator of FIR/CTA" + + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. + Each observation/forecast phenomenon includes its own period of validity for described + meteorological conditions, which is represented as the O&amp;M Observation validTime. + For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 + UTC with an observed position at 1600 UTC and a forecast position of the centre of + the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 + UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis + validTime would be 2200 UTC. + + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, + must be missing otherwise Examples: YUDD SIGMET 2 VALID ... YUDD SIGMET A3 VALID + ... + + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory + when this is a cancellation report, must be missing otherwise + + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, + etc. The expected end of occurrence of volcanic ash ("NO VA EXP") is indicated with + a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance + + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, + as well as observed and forecast conditions for each of these reported areas. All + combinations of observations and forecasts of meteorological conditions, including + changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon + area within an FIR. These are modeled as a single OM_Observation sub-type with a + feature collection result due to the shared time and other observation metadata for + all forecast positions. + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, + speed, and direction. These conditions are reported with OBS/FCST conditions on all + SIGMET types. TC TOP (ABV and BLW) conditions are represented by the vertical component + of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit + and an upperLimit of 500FL. Design note: This class is no longer a subclass of + MeteorologicalPosition. This change was made to ensure that there is no confusion + between the two classes when results from different OM_Observation types are populated. + Constraints could be used to ensure a specific superclass but not its subclasses are + valid, but this would disallow the use of sub-classes of this type for other purposes + such as regional extension + + + + + + + + + + The expected direction of movement of a meteorological condition. When no movement + is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason + and the speedOfMotion will be 0. + + + + + + The expected geographic region affected by the reported phenomenon at a particular + time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of + phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a + base and top, a TC center position, and a VA line with a width + + + + + + The expected speed of movement of a meteorological condition. When no movement is + expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable + nilReason. + + + + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends + the base SIGMET type by including additional information necessary for tropical cyclones. + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The tropical cyclone being reported in this SIGMET + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions hazardous to flight. + This extends the base SIGMET type by including additional information necessary for + volcanoes and volcanic ash. + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The volcano that is erupting + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological + conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. See WMO + No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. + + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + The status of a SIGMET report (e.g., a normal issuance, a cancellation of an earlier + SIGMET) + + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + + + + http://codes.wmo.int/49-2/SigWxPhenomena + none + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET + reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 + sub-clause 1.1.4 + + vocabulary: http://codes.wmo.int/49-2/SigWxPhenomena + extensibility: none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0/taf.xsd new file mode 100644 index 0000000..977079e --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0/taf.xsd @@ -0,0 +1,421 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. An Aerodrome + Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome + intended for distribution. TAF reports include base forecast conditions, and modifications + to those conditions throughout the valid period. + + + Schematron validation + + + + + + + + + + + + + + + + + + + An Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended for distribution + beyond an aerodrome. TAF reports report base forecast conditions, and modifications + to those conditions throughout the valid period. TAF reports include similar information + to a METAR/SPECI trend forecast. However, TAF forecast information includes additional + detail. Aerodromes can issue both METAR/SPECI and TAF reports on a routine basis, + but TAFs are not issued by every METAR-reporting aerodrome. The issuance of a new + forecast by a meteorological office, such as a TAF, cancels any forecast of the same + type previously issued for the same place and for the same period of validity or part + thereof. Prevailing conditions and forecast changes differ in that the prevailing + conditions can include temperatures, base conditions do not include a change indicator, + and that forecast changes may report no significant weather (NSW). Rather than have + two class hierarchies, constraints are present ensuring that each (base and forecast + conditions) only include relevant information + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + + + + + + + + The time at which this report was issued. Note that this should be identical to the + resultTime of each MeteorologicalAerodromeForecast, whose results are made available + at the same time as this report. TAF reports have an issueTime to assist in discovery + and to provide unambiguous semantics at the report level. + + + + + + The time frame at which this report is valid. All forecast elements should be valid + within this period + + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, + this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO + No. 49-2: Section 1.5: "The number of change and probability groups should be kept + to a minimum and should not normally exceed five groups". + + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions forecast at an aerodrome. + This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, + which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the nothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. Note that + the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime + on the change forecast (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime + with a TimePeriod (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod + (start is beginning of forecast validity and end is TL) FM - a phenomenonTime + with a TimePeriod (start is FM and end is end of forecast validity) AT - a phenomenonTime + with a TimeInstant + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingVisibility when + cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The prevailing horizontal visibility, mandatory except when ceiling and visibility + is reported as OK + + quantity: http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + + + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together + at an aerodrome, including the minimum and maximum anticipated air temperatures and + when they occur. AerodromeAirTemperatureForecast is only reported on base conditions + on a TAF, not change forecasts. + + + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The maximum air temperature ICAO Annex 3 / WMO No. 49-2: "TX" + quantity: http://codes.wmo.int/common/c-15/me/airTemperature + + + + + + The time of occurrence of the maximum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TX" + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The minimum air temperature ICAO Annex 3 / WMO No. 49-2: "TN" + quantity: http://codes.wmo.int/common/c-15/me/airTemperature + + + + + + The time of occurrence of the minimum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TN" + + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. + This is an extension of ForecastChangeIndicator that includes report-specific entries, + and in particular the 30 and 40% probability conditions. Note that the TAC representations + for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast + (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime with a TimePeriod + (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod (start is + beginning of forecast validity and end is TL) FM - a phenomenonTime with a TimePeriod + (start is FM and end is end of forecast validity) AT - a phenomenonTime with a + TimeInstant Design note: These values represent the operationally-representable types, + but are not very general-purpose. Especially with temporary conditions and probability + it might be better to turn these into a "probability" property and constraints could + be applied to the value to match operational constraints + + + + + + Conditions are expected to reach or pass through specified threshold values at a regular + or irregular rate and at an unspecified time during the time period. The time period + should normally not exceed 2 hours but in any case should not exceed 4 hours. ICAO + Annex 3 / WMO No. 49-2: "BECMG" + + + + + + Expected temporary fluctuations to meteorological conditions which reach or pass specified + threshold criteria and last for a period of less than one hour in each instance and + in the aggregate cover less than half of the forecast period during which the fluctuations + are expected to occur. ICAO Annex 3 / WMO No. 49-2: "TEMPO" + + + + + + One set of prevailing weather conditions is expected to change significantly and more + or less completely to a different set of conditions. Conditions in a FROM group supersede + conditions in earlier groups. ICAO Annex 3 / WMO No. 49-2: "FM" + + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB30" + + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB30 TEMPO" + + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB40" + + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB40 TEMPO" + + + + + + + + The report status for a TAF report (e.g., a normal issuance, an amendment of an earlier + report, a cancellation of an earlier report) + + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/common.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/common.xsd new file mode 100644 index 0000000..d90245a --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/common.xsd @@ -0,0 +1,139 @@ + + + + Common constructs used across multiple packages. This package includes constructs + closely related to the aviation weather domain. + + + Schematron validation + + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. This extends AerodromeSurfaceWindTrendForecast + to allow for a variable wind direction to be reported. This class differs from a + aerodrome wind observation in that the observations may include a min/max directional + variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type + + + + + + + The observed cloud amount + + + + + The observed cloud base + + + + + Optional cloud type, either cumulonimbus or towering cumulus + + + + + + + + + + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + AerodromeCloudForecast: Vertical visibility cannot be reported together with cloud + layers + + + + + + + + + + + The vertical visibility + + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + The forecast average wind direction. Not reported when winds have variable direction + + + + + The forecast maximum wind speed + + + + + The forecast wind speed + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/dataTypes.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/dataTypes.xsd new file mode 100644 index 0000000..234767d --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/dataTypes.xsd @@ -0,0 +1,50 @@ + + + + Reusable data types used across multiple packages. In contrast to the Common package, + the Data Types package includes basic constructs not directly associated with the + aviation or weather domains. This package includes basic constructs not available + from ISO or other authorities. + + + + + + + Text string with the language of the string identified as recommended in the XML 1.0 + W3C Recommendation, section 2.12. Identifies an ISO language and optional country + code. The language is identified by either a 2-letter ISO 639-1 or 3-letter ISO 639-2T. + The country portion is optional and identified by ISO 3166. This class is modeled + after the xml:lang attribute but is intended to be mapped into existing, appropriate + representations in each format (XML, JSON, etc.). Combined language and country code + examples: "en-us", "en-pg", "en", "fr", "deu-at" This type is developed as an alternative + to importing ISO 19115/19139, which are packages of significant size. + + + + + + + + Optional ISO country code identified by ISO 3166 This attribute is modeled after + the xml:lang attribute but is intended to be mapped into existing, appropriate representations + in each format (XML, JSON, etc.). Examples: "us", "pg", "at" + + + + + + The ISO language identified by either a 2-letter ISO 639-1 or 3-letter ISO 639-2T. + Examples: "en", "fr", "deu" + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/iwxxm.xsd new file mode 100644 index 0000000..f60d4db --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/iwxxm.xsd @@ -0,0 +1,35 @@ + + + + The ICAO Weather Information Exchange Model (IWXXM) package, including METAR, SPECI, + TAF, and SIGMET reports as defined in ICAO Annex 3, 17th edition. These four reports + are essential operational meteorology products used to enable safe and efficient air + travel worldwide. The report types in this package include: <b> </b><b>== </b>METAR + <b>==</b> Routine observation of meteorological conditions made at an aerodrome throughout + the day. METARs may also include short-term forecasts of meteorological conditions + <b> </b>== SPECI == Special (i.e., non-routine) observation of meteorological conditions + made at an aerodrome as needed. SPECIs may also include short-term forecasts of meteorological + conditions <b> </b>== TAF == Routine aerodrome forecasts of meteorological conditions + <b> </b>== SIGMET == Meteorological advisory concerning the occurrence and/or expected + occurrence of weather phenomena which may affect the safety of aircraft operations, + such as severe thunderstorms or turbulence This package builds upon the ISO 19100 + family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, + the constructs in this application schema refer to a number of aviation constructs + such as FIR, Aerodrome, and Runway from the Simple Aviation Features package. The + full relationship of this package with external dependencies are shown in the 'Package + Dependencies' diagram. While only four of the reports from Annex 3 are currently + represented, this may be expanded in a future version. + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/metarSpeci.xsd new file mode 100644 index 0000000..7d82cb6 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/metarSpeci.xsd @@ -0,0 +1,714 @@ + + + + METAR and SPECI reporting constructs as defined in ICAO Annex 3. METAR and SPECI + reports include identical information but are issued for different purposes. METAR + reports are routine observations made at an aerodrome throughout the day. METAR observations + are made (and distributed) at intervals of one hour or, if so determined by regional + air navigation agreement, at intervals of one half-hour. SPECI reports are special + (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations + are made (and distributed) in accordance with criteria established by the meteorological + authority, in consultation with the appropriate ATS authority, operators and others + concerned. + + + Schematron validation + + + + + + + + + + + + + + + + + + + + + Class MeteorologicalAerodromeObservation (a subclass of WMO::ComplexSamplingMeasurement) + is intended for use where the observation event is concerned with the evaluation of + multiple observed (as opposed to forecast) measurands at a specified Aerodrome. The + result of this observation type shall refer to an entity of type MeteorologicalAerodromeObservationRecord. + ComplexSamplingMeasurement enforces the sampled feature be an Aerodrome. MeteorologicalAerodromeObservation + has a sister Class for forecast information at an Aerodrome: MeteorologicalAerodromeTrendForecast. + + + + + MeteorologicalAerodromeObservation: [missing message] + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + + + + + + Class MeteorologicalAerodromeTrendForecast (a subclass of WMO::ComplexSamplingMeasurement) + is intended for use where the observation event is concerned with the evaluation of + multiple forecast measurands at a specified Aerodrome. The result of this observation + type shall refer to an entity of type MeteorologicalAerodromeTrendForecastRecord. + MeteorologicalAerodromeTrendForecast additionally enforces that the sampled feature + must be an Aerodrome MeteorologicalAerodromeTrendForecasts are reported in surface + observation reports such as SPECI and METAR. MeteorologicalAerodromeTrendForecast + has a sister class for trend forecast information at an Aerodrome (MeteorologicalAerodromeObservation) + which is also reported on a METAR and SPECI for observed phenomena. This class is + also related but not identical to MeteorologicalAerodromeForecast which is reported + on a TAF - conditions reported in trend forecasts in METAR/SPECI differ from forecast + groups in a TAF. + + + + + + + + + + + + + + + + + + + + + + + A report of observed and trend forecast weather phenomenon from the surface near an + aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical + reported information. + + + + + + + + + + Human-readable, descriptive text that cannot be sensibly represented in any other + form. This report element encapsulates the human-generated text that is intended + for other downstream human recipients. All other elements of the report capture machine-readable + information that can be anticipated in advance as part of the reporting structure. + It is not valid to include any machine-readable information or extended content in + this text under any circumstances. Human-readable text may be considered opaque to + parsing software and should be used minimally. This text is not to be confused with + Traditional Alphanumeric Code (TAC) form remarks ("RMK"), which have been used for + many purposes beyond human-readable text. + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast + + + + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations + are made (and distributed) in accordance with criteria established by the meteorological + authority, in consultation with the appropriate ATS authority, operators and others + concerned. The information contained in METAR and SPECI is identical. SPECI is + issued when conditions merit a non-routine report on conditions at an aerodrome. + SPECI reports are used for dissemination beyond the aerodrome of origin (mainly intended + for flight planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly + intervals. SPECI shall be issued following the resumption of the issuance of METAR, + as necessary, at aerodromes that are not operational throughout 24 hours in accordance + with ICAO Annex 3 Section 4.3.1. See ICAO Annex 3 Table A3-2 + + + + + SPECI: [missing message] + + + + + + + + + + + + + + + + + + + + A Record containing meteorological trend forecasting conditions at an aerodrome. + This class is the result of MeteorologicalAerodromeTrendForecast observations. This + class is also related but not identical to MeteorologicalAerodromeForecastRecord which + is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI differ + from forecast groups in a TAF. When no clouds of operational significance or no weather + of operational significance is predicted, the NothingOfOperationalSignificance nilReason + should be used for the cloud or presentWeather association. When no clouds were detected + by the automatic observing system, the NotDetectedByAutoSystem nilReason should be + used for the cloud association. + + + + + + + + + + The prevailing horizontal visibility reported in a trend forecast + + + + + + + + + + + + + + + + + + + + + A Record that is intended to contain meteorological conditions observed at an aerodrome. + This class is the result of MeteorologicalAerodromeObservation observations. When + no clouds of operational significance or no weather of operational significance is + observed, the NothingOfOperationalSignificance nilReason should be used for the cloud + or presentWeather association. When no clouds were detected by the automatic observing + system, the NotDetectedByAutoSystem nilReason should be used for the cloud association. + + + + + MeteorologicalAerodromeObservationRecord: [missing message] + + + + + MeteorologicalAerodromeObservationRecord: [missing message] + + + + + MeteorologicalAerodromeObservationRecord: [missing message] + + + + + MeteorologicalAerodromeObservationRecord: [missing message] + + + + + MeteorologicalAerodromeObservationRecord: [missing message] + + + + + + + + + + + + The observed air temperature + + + + + The observed dew point temperature + + + + + The observed QNH altimeter setting + + + + + + + + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations + are made (and distributed) at intervals of one hour or, if so determined by regional + air navigation agreement, at intervals of one half-hour. The information contained + in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine + report on conditions at an aerodrome. METARs are a routine report produced for dissemination + beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET + broadcasts and D-VOLMET. See Annex 3 Table A3-2 + + + + + METAR: [missing message] + + + + + + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including + the runway contamination, friction, and deposits. + + + + + AerodromeRunwayState: Braking action and friction coefficient cannot both be reported + + + + + + + + + + The reported braking conditions. May not be reported together with a friction coefficient + Annex 3: Section 4.8.1.5b, Section 4.8.1.5 Note 2 WMO 306: Table 0366 + + + + + + Between 0 and 100 percent contamination. Example: "50 to 75 percent" Based upon + WMO 306 Code Table 0519 + + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. WMO 306: Table + 0919 + + + + + + The depth of meteorological deposit on the runway. WMO 306: Table 1079 + + + + + The friction coefficient for the affected runway. Between 0.0 and 0.9. May not be + reported together with braking action. WMO 306: Table 0366 + + + + + + The runway to which the conditions apply. The runway may be missing in cases where + all runways are closed due to snow + + + + + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported + together at an aerodrome. + + + + + + + + The mean recent RVR value observed. This mean represents the 10 minute average for + observed RVR except when the 10-minute period immediately preceding the observation + includes a marked discontinuity in runway visual range values, only those values occurring + after the discontinuity shall be used for obtaining mean values Annex 3: Table A3-2 + "RVR/RVR" Section 4.3.6.6 + + + + + + The observed 1-minute mean maximum variations for the runway visual range. If the + 1-minute runway visual range values during the 10-minute period vary from the mean + value by more than 50 m or more than 20 per cent of the mean value, whichever is greater, + the 1-minute mean minimum and the 1-minute mean maximum values should be reported + instead of the 10-minute mean value. If the 10-minute period immediately preceding + the observation includes a marked discontinuity in runway visual range values, only + those values occurring after the discontinuity should be used to obtain variations. + Annex 3: Table A3-2 "RVR/RVR variations" Section 4.3.6.6 + + + + + + The observed 1-minute mean minimum variations for the runway visual range. If the + 1-minute runway visual range values during the 10-minute period vary from the mean + value by more than 50 m or more than 20 per cent of the mean value, whichever is greater, + the 1-minute mean minimum and the 1-minute mean maximum values should be reported + instead of the 10-minute mean value. If the 10-minute period immediately preceding + the observation includes a marked discontinuity in runway visual range values, only + those values occurring after the discontinuity should be used to obtain variations. + Annex 3: Table A3-2 "RVR/RVR variations" Section 4.3.6.6 + + + + + + The runway to which reported RVR information applies + + + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. + This includes information on sea-surface temperature and the state of the sea from + aeronautical meteorological stations established on offshore structures in support + of helicopter operations + + + + + + + + The state of the sea observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations Annex 3: Section 4.8.1.5a + WMO 306: Table 3700 + + + + + + The sea-surface temperature observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations Annex 3: Section 4.8.1.5a + + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, + including the set of affected runways. + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + + + + + + The specific runways affected by wind shear at this aerodrome. No specific runways + are reported when all runways are affected by wind shear + + + + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, + including cloud types, cloud layers, and vertical visibility. + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + The observed vertical visibility + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, + including wind direction information, wind speed, and wind gusts. Wind direction + is reported according to ICAO Annex 3 Section 4.1.5.2b: "variations from the mean + wind direction during the past 10 minutes shall be reported as follows, if the total + variation is 60 or more: 1) when the total variation is 60 or more and less than 180 + and the wind speed is 1.5 m/s (3 kt) or more, such directional variations shall be + reported as the two extreme directions between which the surface wind has varied; + 2) when the total variation is 60 or more and less than 180 and the wind speed is + less than 1.5 m/s (3 kt), the wind direction shall be reported as variable with no + mean wind direction; or 3) when the total variation is 180 or more, the wind direction + shall be reported as variable with no mean wind direction" + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + + + + + + The extreme clockwise direction from which the wind has blown, inclusive. Annex 3: + Section 4.1.5.2b + + + + + + The extreme counter-clockwise direction from which the wind has blown, inclusive. + Annex 3: Section 4.1.5.2b + + + + + + The observed average wind direction from which the wind is blowing. Not reported + when winds are variable + + + + + + The maximum wind speed observed during the past 10 minutes Annex 3: Section 4.1.5.2c + + + + + The observed wind speed Annex 3: Section 4.1.5.2a + + + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at + an aerodrome, including the prevailing visibility and minimum visibility. + + + + + AerodromeHorizontalVisibility: Minimum visibility and the direction must be reported + together + + + + + + + + + + + Section 4.2.4.4a: "When the visibility is not the same in different directions and + a) when the lowest visibility is different from the prevailing visibility, and + 1) less than 1 500 m or 2) less than 50 percent of the prevailing visibility and + less than 5 000 m; the lowest visibility observed should also be reported and,when + possible, its general direction in relation to the aerodrome reference point indicated + by reference to one of the eight points of the compass. If the lowest visibility is + observed in more than one direction, then the most operationally significant direction + should be reported; and b) when the visibility is fluctuating rapidly, and the prevailing + visibility cannot be determined, only the lowest visibility should be reported, with + no indication of direction." + + + + + + The direction of the minimum visibility relative to the reporting station. This is + optional in cases where minimum visibility is reported but the visibility is fluctuating + rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions + (N, NE, E, SE, S, SW, W, and NW) + + + + + + The reported prevailing horizontal visibility at the surface that is representative + of the aerodrome. The greatest visibility value, observed in accordance with the + definition of "visibility¨, which is reached within at least half the horizon circle + or within at least half of the surface of the aerodrome. These areas could comprise + contiguous or non-contiguous sectors. Note: This value may be assessed by human observation + and/or instrumented systems. When instruments are installed, they are used to obtain + the best estimate of the prevailing visibility. Annex 3: Section 4.2.4.4b + + + + + + + + + + + + + + The status of a MeteorologicalAerodromeObservationReport, either a normal issuance + or a correction of an earlier report + + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/sigmet.xsd new file mode 100644 index 0000000..5b06131 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/sigmet.xsd @@ -0,0 +1,440 @@ + + + + SIGMET reporting constructs as defined in ICAO Annex 3. SIGMETs report the occurrence + and/or expected occurrence of specified en-route weather phenomena which may affect + the safety of aircraft operations, and of the development of those phenomena in time + and space. These weather phenomena are reported as impacted regions of airspace. + Only a single SIGMET of a given type (e.g., Thunderstorm) shall be in force within + a specific FIR at any given time. + + + Schematron validation + + + + + + + + + + + + + + + + + + + + A MeteorologicalPosition is a result of a SIGMETPositionAnalysis process, and indicates + the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm. + MeteorologicalPositions are used to represent the forecast positions with VolcanicAshSIGMET + and TropicalCycloneSIGMET. TC TOP (ABV and BLW) conditions are represented by the + vertical component of the geometry. For example: CB TOP FL500 is represented as a + base of 0 and a top of 500FL + + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, + volcanic ash, etc.). This geometry covers all combinations of phenomenon historically + reported in Annex 3: a boundary with a base and top, a TC center position, and a VA + line with a width + + + + + + + + + + + + + + + + + An EvolvingMeteorologicalCondition is a result of a SIGMETEvolvingConditionAnalysis + process, and indicates the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm along with expected changes to the phenomenon such as intensity, + speed, and direction. These conditions are reported with OBS/FCST conditions on all + SIGMET types. TC TOP (ABV and BLW) conditions are represented by the vertical component + of the geometry. For example: CB TOP FL500 is represented as a base of 0 and a top + of 500FL. Design note: This class is no longer a subclass of MeteorologicalPosition. + This change was made to ensure that there is no confusion between the two classes + when results from different OM_Observation types are populated. The oclIsTypeOf constraint + can be used to ensure a specific superclass but not its subclasses are valid, but + this would disallow the use of sub-classes of this type for other purposes such as + regional extension + + + + + + + + + + The direction of movement of a meteorological phenomenon. When no movement is expected, + this will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the + speedOfMotion will be 0. + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, + volcanic ash, etc.). This geometry covers all combinations of phenomenon historically + reported in Annex 3: a boundary with a base and top, a TC center position, and a VA + line with a width + + + + + + The speed of movement of a meteorological phenomenon. When no movement is expected, + this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable + nilReason. + + + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological + conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + + + + + + + + + + + + + A specialization of SamplingObservation whose featureOfInterest is a SpatialSamplingFeature + which refers to an FIR, the result of which is a single EvolvingMeteorologicalCondition + which represents a SIGMET observation or forecast of meteorological conditions. + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + + + + + + + + + + + + + + + + + + + + + A specialization of SamplingObservation whose featureOfInterest is a SpatialSamplingFeature + which refers to an FIR, the result of which is one or more MeteorologicalPositions + which represent the forecast positions of SIGMET phenomenon + + + + + SIGMETPositionAnalysis: [missing message] + + + + + SIGMETPositionAnalysis: [missing message] + + + + + + + + + + + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or + expected occurrence of specified en-route weather phenomena which may affect the safety + of aircraft operations, and of the development of those phenomena in time and space. + Only a single SIGMET of a given type (e.g., Thunderstorm) shall be in force within + a specific FIR at any given time. The SIGMET report class represents the base SIGMET + types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, + etc. Tropical cyclone and volcanic ash SIGMET reports are subclasses of SIGMET due + to their ability to report additional information, including volcano/tropical cyclone + identification and forecast position(s). Non-tropical cyclone and volcanic ash SIGMETs + may report either an observation or a forecast. SIGMETs may include both an observation + ("OBS") as well as a forecast ("FCST"). Volcanic ash and tropical cyclones may additionally + include a set of forecast positions + + + + + + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR, + as well as observed and forecast conditions for each of these reported areas. All + combinations of observations and forecasts of meteorological conditions, including + changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, + must be missing otherwise Examples: YUDD SIGMET 2 VALID ... YUDD SIGMET A3 VALID + ... + + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory + when this is a cancellation report, must be missing otherwise + + + + + + Human-readable, descriptive text that cannot be sensibly represented in any other + form. This report element encapsulates the human-generated text that is intended + for other downstream human recipients. All other elements of the report capture machine-readable + information that can be anticipated in advance as part of the reporting structure. + It is not valid to include any machine-readable information or extended content in + this text under any circumstances. Human-readable text may be considered opaque to + parsing software and should be used minimally. This text is not to be confused with + Traditional Alphanumeric Code (TAC) form remarks ("RMK"), which have been used for + many purposes beyond human-readable text. + + + + + + ICAO location indicator of the ATS unit serving the FIR or CTA to which the SIGMET + refers Annex 3: A6-1: "Location indicator of FIR/CTA" + + + + + + MWO originating this report + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, + etc. + + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecasts. + Each observation/forecast also includes its own applicable period of validity + + + + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends + the base SIGMET type by including additional information regarding forecast positions + and tropical cyclone identification. + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: [missing message] + + + + + + + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon + area within an FIR. These are modeled as a single OM_Observation sub-type with a + feature collection result due to the shared time and other observation metadata for + all forecast positions. + + + + + + The tropical cyclone being reported in this SIGMET + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions. This extends the base + SIGMET type by including additional information regarding forecast positions and volcano + identification. + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: [missing message] + + + + + + + + + + + + The volcano that is erupting + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon + area within an FIR. These are modeled as a single OM_Observation sub-type with a + feature collection result due to the shared time and other observation metadata for + all forecast positions. + + + + + + + + + + + + + + + + + The status of a SIGMET report, either a normal issuance or a cancellation of an earlier + SIGMET + + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC1/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/taf.xsd new file mode 100644 index 0000000..1c6cc0b --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC1/taf.xsd @@ -0,0 +1,404 @@ + + + + TAF reporting constructs as defined in ICAO Annex 3. A Terminal Aerodrome Forecast + (TAF) report is a routine aerodrome forecast intended for distribution beyond an aerodrome. + TAF reports include base forecast conditions, and modifications to those conditions + throughout the valid period. + + + Schematron validation + + + + + + + + + + + + + + + + + + + + + Class MeteorologicalAerodromeForecast (a subclass of WMO::ComplexSamplingMeasurement) + is intended for use where the observation event is concerned with the evaluation of + multiple forecast measurands at a specified Aerodrome. The result of this observation + type shall refer to an entity of type MeteorologicalAerodromeForecastRecord. MeteorologicalAerodromeForecast + enforces the following additional constraints: <ul> <li>The sampled feature must + be an Aerodrome</li> </ul> This class is also related but not identical to MeteorologicalAerodromeTrendForecast + which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. The TAF forecast group from/to variants (FM, + TL, AT, etc.) are represented on the OM_Observation validTime, which is always an + instance of TM_Period. When there is only an instant at which a condition occurs, + the start and end time are the same + + + + + + + + + + + + + + + + + + + + + + + A Record that is intended to contain meteorological forecasting conditions at an aerodrome. + This class is the result of MeteorologicalAerodromeForecast observations. This class + is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, which + is reported on a METAR/SPECI. Conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the nothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingHorizontalVisibility + while ceilingAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report presentWeather while ceilingAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report surfaceWind while ceilingAndVisibilityOK + is true + + + + + + + + + + + + + The prevailing horizontal visibility, mandatory except when ceiling and visibility + is reported as OK + + + + + + + + + + + + + + + + + + + + + + + A Terminal Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended + for distribution beyond an aerodrome. TAF reports report base forecast conditions, + and modifications to those conditions throughout the valid period. TAF reports include + similar information to a METAR/SPECI trend forecast. However, TAF forecast information + includes additional detail. Aerodromes can issue both METAR/SPECI and TAF reports + on a routine basis, but TAFs are not issued by every METAR-reporting aerodrome. The + issuance of a new forecast by a meteorological office, such as a TAF, cancels any + forecast of the same type previously issued for the same place and for the same period + of validity or part thereof. Prevailing conditions and forecast changes differ in + that the prevailing conditions can include temperatures, base conditions do not include + a change indicator, and that forecast changes may report no significant weather (NSW). + Rather than have two class hierarchies, constraints are present ensuring that each + (base and forecast conditions) only include relevant information + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: previousReportValidPeriod must be null unless this cancels or amends a previous + report + + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + + + + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, + this should normally not exceed five in number (Annex 3 Section 1.5). <b><u> </u></b>Annex + 3: Section 1.5: "The number of change and probability groups should be kept to a minimum + and should not normally exceed five groups". + + + + + + Human-readable, descriptive text that cannot be sensibly represented in any other + form. This report element encapsulates the human-generated text that is intended + for other downstream human recipients. All other elements of the report capture machine-readable + information that can be anticipated in advance as part of the reporting structure. + It is not valid to include any machine-readable information or extended content in + this text under any circumstances. Human-readable text may be considered opaque to + parsing software and should be used minimally. This text is not to be confused with + Traditional Alphanumeric Code (TAC) form remarks ("RMK"), which have been used for + many purposes beyond human-readable text. + + + + + + The time at which this report was issued. Note that this should be identical to the + resultTime of each MeteorologicalAerodromeForecast, whose results are made available + at the same time as this report. TAF reports have an issueTime to assist in discovery + and to provide unambiguous semantics at the report level. + + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + The time frame at which this report is valid. All forecast elements should be valid + within this period + + + + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together + at an aerodrome, including the minimum and maximum anticipated air temperatures and + when they occur. AerodromeAirTemperatureForecast is only reported on base conditions + on a TAF, not change forecasts. + + + + + + + + The maximum air temperature Annex 3: "TX" + + + + + The time of occurrence of the maximum air temperature. This must be within the period + of the phenomenon time for this forecast record Annex 3: "TX" + + + + + + The minimum air temperature Annex 3: "TX" + + + + + The time of occurrence of the minimum air temperature. This must be within the period + of the phenomenon time for this forecast record Annex 3: "TX" + + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. + This is an extension of ForecastChangeIndicator that includes report-specific entries, + and in particular the 30 and 40% probability conditions. Design note: These values + represent the operationally-representable types, but are not very general-purpose. + Especially with temporary conditions and probability it might be better to turn these + into a "probability" property and constraints could be applied to the value to match + operational constraints + + + + + + When the change is forecast to commence at the beginning of the forecast period and + be completed by the end of that period, or when the change is forecast to occur within + the forecast period but the time of the change is uncertain (possibly shortly after + the beginning of the forecast period, or midway or near the end of that period), the + change shall be indicated by only the change indicator BECMG. Enumerations can not + inherit from other enumeration types in HollowWorld. This class duplicates the enumerated + types present in WMO ForecastChangeIndicator. + + + + + + The change indicator TEMPO shall be used to describe expected temporary fluctuations + to meteorological conditions which reach or pass specified threshold criteria and + last for a period of less than one hour in each instance and in the aggregate cover + less than half of the forecast period during which the fluctuations are expected to + occur. Enumerations can not inherit from other enumeration types in HollowWorld. + This class duplicates the enumerated types present in WMO ForecastChangeIndicator. + + + + + + The change indicator FROM shall be used to describe expected permanent fluctuations + to meteorological conditions. Forecast conditions given before the FROM group are + superseded by the conditions indicated after the group. Annex 3: "FROM" + + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + Annex 3: "PROB30" + + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. Annex 3: "PROB30 TEMPO" + + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + Annex 3: "PROB40" + + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. Annex 3: "PROB40 TEMPO" + + + + + + + + The report status for a TAF report, either a normal issuance, an amendment of an earlier + report, a cancellation of an earlier report, or a correction of an earlier report + + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC2/common.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/common.xsd new file mode 100644 index 0000000..adcd63c --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/common.xsd @@ -0,0 +1,203 @@ + + + + Common constructs used across multiple packages. This package includes constructs + closely related to the aviation weather domain. + + + Schematron validation + + + + + + + + + + + + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/verticalVisibility + + The vertical visibility. Vertical visibility is defined as the vertical visual range + into an obscuring medium. + + + + + + Cloud type (e.g., cumulonimbus, towering cumulus) + + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. This extends AerodromeSurfaceWindTrendForecast + to allow for a variable wind direction to be reported. This class differs from a + aerodrome wind observation in that the observations may include a min/max directional + variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type + + + + + + + The observed cloud amount + + + + + + http://codes.wmo.int/common/c-15/me/heightOfBaseOfCloud + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at + which the air contains a perceptible quantity of cloud particles. + + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The forecast average wind direction from which wind is blowing + + + + + + http://codes.wmo.int/common/c-15/me/windSpeed + + The forecast average wind speed + + + + + + http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + The forecast maximum speed of a gust. + + + + + + + + + + + + + + http://codes.wmo.int/49-2/AerodromeForecastWeather + none + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + Only a specific set of weather phenomenon are reported within aviation meteorology + as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This ?CodeList? is specifically + defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions + are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + + + + + + + + + http://codes.wmo.int/49-2/SigConvectiveCloudType + none + + Genus of cloud of operational significance to aviation: significant convective clouds + only. - Cumulonimbus - Towering cumulus This ?CodeList? is specifically defined + for aviation purposes, as defined in WMO No. 49-2. A superset of definitions are defined + in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 012 "Cloud type". + + + + + + + + + + http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + none + + Amount of cloud - assessed by category: - Sky clear (0 oktas) - Few (1 - 2 oktas) + - Scattered (3 - 4 oktas) - Broken (5 - 7 oktas) - Overcast (8 oktas) This ?CodeList? + is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset + of cloud-amount categories are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 20 008 "Cloud distribution for aviation". + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC2/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/iwxxm.xsd new file mode 100644 index 0000000..d23c1fe --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/iwxxm.xsd @@ -0,0 +1,32 @@ + + + + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, + SPECI, TAF, and SIGMET reports as defined in ICAO Annex 3, Amendment 76. These four + reports are essential operational meteorology products used to enable safe and efficient + air travel worldwide. The report types in this package include: <b> </b><b>== </b>METAR + <b>==</b> Routine report of meteorological conditions made at an aerodrome. METARs + may also include short-term forecasts of meteorological conditions <b> </b>== SPECI + == Special (i.e., non-routine) report of meteorological conditions made at an aerodrome + as needed. SPECIs may also include short-term forecasts of meteorological conditions + <b> </b>== TAF == Routine forecast report of meteorological conditions at an aerodrome + <b> </b>== SIGMET == Meteorological advisory concerning the occurrence and/or expected + occurrence of weather phenomena which may affect the safety of aircraft operations, + such as severe thunderstorms or turbulence This package builds upon the ISO 19100 + family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, + the constructs in this application schema refer to a number of aviation constructs + such as FIR, Aerodrome, and Runway from the Simple Aviation Features package. The + full relationship of this package with external dependencies are shown in the 'Package + Dependencies' diagram. While only four of the reports from Annex 3 are currently + represented, this may be expanded in a future version. + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC2/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/metarSpeci.xsd new file mode 100644 index 0000000..b891c92 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/metarSpeci.xsd @@ -0,0 +1,998 @@ + + + + METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. METAR + and SPECI reports include identical information but are issued for different purposes. + METAR reports are routine observations made at an aerodrome throughout the day. METAR + observations are made (and distributed) at intervals of one hour or, if so determined + by regional air navigation agreement, at intervals of one half-hour. SPECI reports + are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI + observations are made (and distributed) in accordance with criteria established by + the meteorological authority, in consultation with the appropriate ATS authority, + operators and others concerned. + + + Schematron validation + + + + + + + + + + + + + + + + + + A report of observed and trend forecast weather phenomenon from the surface near an + aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical + reported information. + + + + + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast. When no change is expected to occur + during a forecast period ("NOSIG") this shall be indicated by a single missing trend + forecast with a nil reason of noSignificantChange + + + + + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations + are made (and distributed) in accordance with criteria established by the meteorological + authority, in consultation with the appropriate ATS authority, operators and others + concerned. The information contained in METAR and SPECI is identical. SPECI is issued + when conditions merit a non-routine report on conditions at an aerodrome. SPECI reports + are used for dissemination beyond the aerodrome of origin (mainly intended for flight + planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly intervals. + SPECI shall be issued following the resumption of the issuance of METAR, as necessary, + at aerodromes that are not operational throughout 24 hours in accordance with ICAO + Annex 3 Section 4.3.1. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations + are made (and distributed) at intervals of one hour or, if so determined by regional + air navigation agreement, at intervals of one half-hour. The information contained + in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine + report on conditions at an aerodrome. METARs are a routine report produced for dissemination + beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET + broadcasts and D-VOLMET. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + A specialized OM_Observation type used for reporting an aggregate set of observed + meteorological conditions at an Aerodrome. The result of this observation type shall + refer to an entity of type MeteorologicalAerodromeObservationRecord. ComplexSamplingMeasurement + enforces the sampled feature be an Aerodrome. MeteorologicalAerodromeObservation + has a sister Class for forecast information at an Aerodrome: MeteorologicalAerodromeTrendForecast. + + + + + + + + + + + + + + + + + + + + + + A specialized OM_Observation type used for reporting an aggregate set of forecast + meteorological conditions at an Aerodrome. The result of this observation type shall + refer to an entity of type MeteorologicalAerodromeTrendForecastRecord. MeteorologicalAerodromeTrendForecast + additionally enforces that the sampled feature must be an Aerodrome MeteorologicalAerodromeTrendForecasts + are reported in surface observation reports such as SPECI and METAR. MeteorologicalAerodromeTrendForecast + has a sister class for trend forecast information at an Aerodrome (MeteorologicalAerodromeObservation) + which is also reported on a METAR and SPECI for observed phenomena. This class is + also related but not identical to MeteorologicalAerodromeForecast which is reported + on a TAF - conditions reported in trend forecasts in METAR/SPECI differ from forecast + groups in a TAF. + + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions for trend forecasting + at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord + which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the NothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. When no clouds + were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason + should be used for the cloud association. + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The prevailing horizontal visibility reported in a trend forecast + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions observed at an aerodrome. + When no clouds of operational significance or no weather of operational significance + is observed, the NothingOfOperationalSignificance nilReason should be used for the + cloud or presentWeather association. When no clouds were detected by the automatic + observing system, the NotDetectedByAutoSystem nilReason should be used for the cloud + association. + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The observed air temperature. This is the temperature indicated by a thermometer + exposed to the air in a place sheltered from direct solar radiation. + + + + + + + http://codes.wmo.int/common/c-15/me/dewPointTemperature + + The observed dew point temperature. This is the temperature to which a given air + parcel must be cooled at constant pressure and constant water vapor content in order + for saturation to occur. + + + + + + + http://codes.wmo.int/common/c-15/me/altimeterSettingQnh + + The observed QNH altimeter setting. Altitude setting (also known as QNH) is defined + as barometric pressure adjusted to sea level. It is a pressure setting used by pilots, + air traffic control (ATC), and low frequency weather beacons to refer to the barometric + setting which, when set on an aircraft's altimeter, will cause the altimeter to read + altitude above mean sea level within a certain defined region. + + + + + + + + + + + + + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including + the runway contamination, friction, and deposits. + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + + + + + + The runway to which the conditions apply. The runway may be missing in cases where + all runways are closed due to snow + + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. WMO 306: Table + 0919 + + + + + + + http://codes.wmo.int/common/c-15/ae/runwayContamination + + Proportion of runway surface that is contaminated - usually expressed as a percentage + of the total runway area. WMO reporting procedures require that contamination is + reported in the following categories: - less than 10%; - between 11% and 25%; - between + 26% and 50%; and - more than 50%. See WMO No. 306: - WMO Code table 0519 - BUFR + Code table 0 20 087 + + + + + + + http://codes.wmo.int/common/c-15/ae/depthOfRunwayDeposit + + Depth of deposit on the surface of the runway. See WMO No. 306 WMO Code table 1079. + + + + + + http://codes.wmo.int/common/c-15/ae/runwayFrictionCoefficient + + The estimated surface friction for the affected runway. Between 0.0 and 0.9. When + braking conditions are not reported and/or the runway is not operational estimatedSurfaceFriction + will not be reported. WMO 306: Table 0366 + + + + + + + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported + together at an aerodrome. + + + + + + + + The runway to which reported runway visual range information applies + + + + + + http://codes.wmo.int/common/c-15/ae/runwayVisualRangeRvr + + The mean recent runway visual range value observed. This mean represents the 10 minute + average for observed RVR except when the 10-minute period immediately preceding the + observation includes a marked discontinuity in runway visual range values, only those + values occurring after the discontinuity shall be used for obtaining mean values + Annex 3: Table A3-2 "RVR/RVR" Section 4.3.6.6 + + + + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. + This includes information on sea-surface temperature and either the state of the sea + or significant wave height from aeronautical meteorological stations established on + offshore structures in support of helicopter operations + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + + + + + + + http://codes.wmo.int/common/c-15/oc/seaSurfaceTemperature + + The sea-surface temperature observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations. The term sea surface + temperature is generally meant to be representative of the upper few meters of the + ocean as opposed to the skin temperature, which is the temperature of the upper few + centimeters. ICAO Annex 3 / WMO No. 49-2: Section 4.8.1.5a + + + + + + The significant wave height observed + + + + + The state of the sea observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations ICAO Annex 3 / WMO No. + 49-2: Section 4.8.1.5a WMO 306: Table 3700 + + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, + including the set of affected runways. + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + + + + + + The specific runway(s) affected by wind shear at this aerodrome. No specific runways + are reported when all runways are affected by wind shear + + + + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, + including cloud types, cloud layers, and vertical visibility. + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/verticalVisibility + + The reported vertical visibility. Vertical visibility is defined as the vertical + visual range into an obscuring medium. Note: vertical visibility is only reported + in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus + we consider prevailing visibility to be an aviation-specific quantity. When the sky + is obscured and the value of the vertical visibility cannot be determined by the automatic + observing system due to a temporary failure of the system/sensor ("VV///") the vertical + visibility shall be missing with a nil reason of notObservable + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, + including wind direction information, wind speed, and wind gusts. Wind direction + is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: "variations + from the mean wind direction during the past 10 minutes shall be reported as follows, + if the total variation is 60 or more: 1) when the total variation is 60 or more and + less than 180 and the wind speed is 1.5 m/s (3 kt) or more, such directional variations + shall be reported as the two extreme directions between which the surface wind has + varied; 2) when the total variation is 60 or more and less than 180 and the wind speed + is less than 1.5 m/s (3 kt), the wind direction shall be reported as variable with + no mean wind direction; or 3) when the total variation is 180 or more, the wind direction + shall be reported as variable with no mean wind direction" + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The observed average wind direction from which the wind is blowing over the past ten + minutes. Not reported when winds are variable + + + + + + + http://codes.wmo.int/common/c-15/me/windSpeed + + The average observed wind speed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2a + + + + + + + http://codes.wmo.int/common/c-15/me/maximumWindGustSpeed + + The maximum wind speed observed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2c + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The extreme clockwise direction from which the wind is blowing, inclusive. ICAO Annex + 3 / WMO No. 49-2: Section 4.1.5.2b + + + + + + + http://codes.wmo.int/common/c-15/me/windDirection + + The extreme counter-clockwise direction from which the wind is blowing, inclusive. + ICAO Annex 3 / WMO No. 49-2: Section 4.1.5.2b + + + + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at + an aerodrome, including the prevailing visibility and minimum visibility. + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The reported prevailing horizontal visibility at the surface that is representative + of the aerodrome. The greatest visibility value, observed in accordance with the + definition of "visibility?, which is reached within at least half the horizon circle + or within at least half of the surface of the aerodrome. These areas could comprise + contiguous or non-contiguous sectors. Note: This value may be assessed by human observation + and/or instrumented systems. When instruments are installed, they are used to obtain + the best estimate of the prevailing visibility. ICAO Annex 3 / WMO No. 49-2: Section + 4.2.4.4b + + + + + + + http://codes.wmo.int/common/c-15/ae/minimumHorizontalVisibility + + The minimum observed visibility. ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: "When + the visibility is not the same in different directions and a) when the lowest visibility + is different from the prevailing visibility, and 1) less than 1 500 m or 2) + less than 50 percent of the prevailing visibility and less than 5000 m; the lowest + visibility observed should also be reported and,when possible, its general direction + in relation to the aerodrome reference point indicated by reference to one of the + eight points of the compass. If the lowest visibility is observed in more than one + direction, then the most operationally significant direction should be reported; and + b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot + be determined, only the lowest visibility should be reported, with no indication of + direction." + + + + + + The direction of the minimum visibility relative to the reporting station. This is + optional in cases where minimum visibility is reported but the visibility is fluctuating + rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions + (N, NE, E, SE, S, SW, W, and NW) + + + + + + + + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. Defined in WMO + No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. Also see WMO No. 306 Vol + I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or + an aerodrome forecast'. + + + + + + No significant changes are forecast (NOSIG) + + + + + When the change is forecast to commence at the beginning of the forecast period and + be completed by the end of that period, or when the change is forecast to occur within + the forecast period but the time of the change is uncertain (possibly shortly after + the beginning of the forecast period, or midway or near the end of that period), the + change shall be indicated by only the change indicator BECMG. + + + + + + The change indicator TEMPO shall be used to describe expected temporary fluctuations + to meteorological conditions which reach or pass specified threshold criteria and + last for a period of less than one hour in each instance and in the aggregate cover + less than half of the forecast period during which the fluctuations are expected to + occur. + + + + + + + + The tendency of visual range (e.g., upward, downward). Defined for the purposes of + aviation meteorology reporting of the visual range on runways (WMO No. 49-2). If + the [runway] visual range (RVR) values during the 10-minute period preceding the nominal + observation time show a distinct upward or downward tendency such that the mean during + the first five minutes varies by 100 metres or more from the mean in the second five + minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency shall be recorded. When + no distinct change in RVR is observed, NO CHANGE [N] shall be recorded. See WMO No. + 306 Vol I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visual range". + + + + + + Upward (increasing) tendency + + + + + No change + + + + + Downward (decreasing) tendency + + + + + + + The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, + correction of an earlier report, etc.) + + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + + + + http://codes.wmo.int/49-2/AerodromeRecentWeather + none + + Weather phenomenon of operational significance to aviation observed during the period + since the last routine report, or last hour, whichever is shorter, but not at the + time of observation. Only a specific set of weather phenomenon are reported within + aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This ?CodeList? + is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset + of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather + phenomena". + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-22-061 + none + + Categorical assessment of sea surface state (or other large open body of water) based + on height of waves. Height in metres : Category - 0 metres : Calm (glassy) - 0-0.1 + metres : Calm (rippled) - 0.1-0.5 metres : Smooth - 0.5-1.25 metres : Slight - 1.25-2.5 + metres : Moderate - 2.5-4 metres : Rough - 4-6 metres : Very rough - 6-9 metres : + High - 9-14 metres : Very high - &gt;14 metres : Phenomenal See WMO No. 306 Vol I.1 + code table 3700 "State of the sea" and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 + 22 061 "State of the sea". + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-20-086 + none + + Type of deposit on a runway. See WMO No. 306 Vol I.1 code table 0919 and WMO No. + 306 Vol I.2 FM 94 BUFR code table 0 20 086 "Runway deposits". + + + + + + + + + + http://codes.wmo.int/49-2/AerodromePresentWeather + none + + The present weather observed at, or in near vicinity of, an aerodrome. Only a specific + set of weather phenomenon are reported within aviation meteorology as defined in Regulation + ICAO Annex 3 / WMO No. 49-2. This ?CodeList? is specifically defined for aviation + purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO + No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC2/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/sigmet.xsd new file mode 100644 index 0000000..0214f11 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/sigmet.xsd @@ -0,0 +1,538 @@ + + + + SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. SIGMETs report + the occurrence and/or expected occurrence of specified en-route weather phenomena + which may affect the safety of aircraft operations, and of the development of those + phenomena in time and space. These weather phenomena are reported as impacted regions + of airspace. + + + Schematron validation + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. + TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. + For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit + of 500FL. In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA + or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to + the sampled feature for this SIGMET. + + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, + volcanic ash, etc.). This geometry covers all combinations of phenomenon historically + reported in Annex 3: a boundary with a base and top, a TC center position, and a VA + line with a width + + + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or + expected occurrence of specified en-route weather phenomena which may affect the safety + of aircraft operations, and of the development of those phenomena over time. The + SIGMET report class represents the base SIGMET types that may be reported such as + squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic + ash SIGMET reports are subclasses of SIGMET due to their ability to report additional + information, including volcano/tropical cyclone identification and forecast position(s). + SIGMETs may report either observed or forecast hazardous conditions. Additionally, + a forecast position may be reported. + + + + + SIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + SIGMET: A canceled SIGMET should not have an analysis + + + + + SIGMET: There must be at least one analysis when a SIGMET does not have canceled status + + + + + SIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The ATS unit serving the FIR or CTA to which the SIGMET refers ICAO Annex 3 / WMO + No. 49-2: A6-1: "Location indicator of FIR/CTA" + + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. + Each observation/forecast phenomenon includes its own period of validity for described + meteorological conditions, which is represented as the O&amp;M Observation validTime. + For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 + UTC with an observed position at 1600 UTC and a forecast position of the centre of + the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 + UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis + validTime would be 2200 UTC. + + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, + must be missing otherwise Examples: YUDD SIGMET 2 VALID ... YUDD SIGMET A3 VALID + ... + + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory + when this is a cancellation report, must be missing otherwise + + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, + etc. The expected end of occurrence of volcanic ash ("NO VA EXP") shall be indicated + with a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance + + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, + as well as observed and forecast conditions for each of these reported areas. All + combinations of observations and forecasts of meteorological conditions, including + changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon + area within an FIR. These are modeled as a single OM_Observation sub-type with a + feature collection result due to the shared time and other observation metadata for + all forecast positions. + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, + speed, and direction. These conditions are reported with OBS/FCST conditions on all + SIGMET types. TC TOP (ABV and BLW) conditions are represented by the vertical component + of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit + and an upperLimit of 500FL. Design note: This class is no longer a subclass of + MeteorologicalPosition. This change was made to ensure that there is no confusion + between the two classes when results from different OM_Observation types are populated. + Constraints could be used to ensure a specific superclass but not its subclasses are + valid, but this would disallow the use of sub-classes of this type for other purposes + such as regional extension + + + + + + + + + + The expected direction of movement of a meteorological condition. When no movement + is expected, this will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason + and the speedOfMotion will be 0. + + + + + + The expected geographic region affected by the reported phenomenon at a particular + time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of + phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a + base and top, a TC center position, and a VA line with a width + + + + + + The expected speed of movement of a meteorological condition. When no movement is + expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable + nilReason. + + + + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends + the base SIGMET type by including additional information necessary for tropical cyclones. + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The tropical cyclone being reported in this SIGMET + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions hazardous to flight. + This extends the base SIGMET type by including additional information necessary for + volcanoes and volcanic ash. + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The volcano that is erupting + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological + conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + + + + + + + + + + + + + A specialized OM_Observation type used for reporting an aggregate set of meteorological + conditions hazardous to flight over a large airspace, including anticipated characteristics. + The result of this observation type shall refer to a single EvolvingMeteorologicalCondition + which represents a SIGMET observation or forecast of meteorological conditions. + + + + + + + + + + + + + + + + + + + + + + A specialized OM_Observation type used for reporting the forecast position of meteorological + conditions hazardous to flight. The result of this observation type shall refer to + one or more MeteorologicalPositions which represents the forecast positions of SIGMET + phenomena. + + + + + + + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. See WMO + No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. + + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + The status of a SIGMET report (e.g., a normal issuance, a cancellation of an earlier + SIGMET) + + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + + + + http://codes.wmo.int/49-2/SigWxPhenomena + none + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET + reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 + sub-clause 1.1.4 + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.0RC2/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/taf.xsd new file mode 100644 index 0000000..e97ac9f --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.0RC2/taf.xsd @@ -0,0 +1,429 @@ + + + + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. An Aerodrome + Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome + intended for distribution. TAF reports include base forecast conditions, and modifications + to those conditions throughout the valid period. + + + Schematron validation + + + + + + + + + + + + + + + + + + A specialized OM_Observation type used for reporting an aggregate set of forecast + meteorological conditions at an Aerodrome. The result of this observation type shall + refer to an entity of type MeteorologicalAerodromeForecastRecord. MeteorologicalAerodromeForecast + enforces the following additional constraints: <ul> <li>The sampled feature must + be an Aerodrome</li> </ul> This class is also related but not identical to MeteorologicalAerodromeTrendForecast + which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. The TAF forecast group from/to variants (FM, + TL, AT, etc.) are represented on the OM_Observation validTime, which is always an + instance of TM_Period. When there is only an instant at which a condition occurs, + the start and end time are the same + + + + + + + + + + + + + + + + + + + + + + An Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended for distribution + beyond an aerodrome. TAF reports report base forecast conditions, and modifications + to those conditions throughout the valid period. TAF reports include similar information + to a METAR/SPECI trend forecast. However, TAF forecast information includes additional + detail. Aerodromes can issue both METAR/SPECI and TAF reports on a routine basis, + but TAFs are not issued by every METAR-reporting aerodrome. The issuance of a new + forecast by a meteorological office, such as a TAF, cancels any forecast of the same + type previously issued for the same place and for the same period of validity or part + thereof. Prevailing conditions and forecast changes differ in that the prevailing + conditions can include temperatures, base conditions do not include a change indicator, + and that forecast changes may report no significant weather (NSW). Rather than have + two class hierarchies, constraints are present ensuring that each (base and forecast + conditions) only include relevant information + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + + + + + + + + The time at which this report was issued. Note that this should be identical to the + resultTime of each MeteorologicalAerodromeForecast, whose results are made available + at the same time as this report. TAF reports have an issueTime to assist in discovery + and to provide unambiguous semantics at the report level. + + + + + + The time frame at which this report is valid. All forecast elements should be valid + within this period + + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, + this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO + No. 49-2: Section 1.5: "The number of change and probability groups should be kept + to a minimum and should not normally exceed five groups". + + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions forecast at an aerodrome. + This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, + which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the nothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. Note that + the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime + on the change forecast (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime + with a TimePeriod (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod + (start is beginning of forecast validity and end is TL) FM - a phenomenonTime + with a TimePeriod (start is FM and end is end of forecast validity) AT - a phenomenonTime + with a TimeInstant + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingHorizontalVisibility + when cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + + + + + + + + + http://codes.wmo.int/common/c-15/ae/prevailingHorizontalVisibility + + The prevailing horizontal visibility, mandatory except when ceiling and visibility + is reported as OK + + + + + + + + + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together + at an aerodrome, including the minimum and maximum anticipated air temperatures and + when they occur. AerodromeAirTemperatureForecast is only reported on base conditions + on a TAF, not change forecasts. + + + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The maximum air temperature ICAO Annex 3 / WMO No. 49-2: "TX" + + + + + The time of occurrence of the maximum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TX" + + + + + + + http://codes.wmo.int/common/c-15/me/airTemperature + + The minimum air temperature ICAO Annex 3 / WMO No. 49-2: "TN" + + + + + The time of occurrence of the minimum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TN" + + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. + This is an extension of ForecastChangeIndicator that includes report-specific entries, + and in particular the 30 and 40% probability conditions. Note that the TAC representations + for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast + (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime with a TimePeriod + (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod (start is + beginning of forecast validity and end is TL) FM - a phenomenonTime with a TimePeriod + (start is FM and end is end of forecast validity) AT - a phenomenonTime with a + TimeInstant Design note: These values represent the operationally-representable types, + but are not very general-purpose. Especially with temporary conditions and probability + it might be better to turn these into a "probability" property and constraints could + be applied to the value to match operational constraints + + + + + + Conditions are expected to reach or pass through specified threshold values at a regular + or irregular rate and at an unspecified time during the time period. The time period + should normally not exceed 2 hours but in any case should not exceed 4 hours. ICAO + Annex 3 / WMO No. 49-2: "BECMG" + + + + + + Expected temporary fluctuations to meteorological conditions which reach or pass specified + threshold criteria and last for a period of less than one hour in each instance and + in the aggregate cover less than half of the forecast period during which the fluctuations + are expected to occur. ICAO Annex 3 / WMO No. 49-2: "TEMPO" + + + + + + One set of prevailing weather conditions is expected to change significantly and more + or less completely to a different set of conditions. Conditions in a FROM group supersede + conditions in earlier groups. ICAO Annex 3 / WMO No. 49-2: "FM" + + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB30" + + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB30 TEMPO" + + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB40" + + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB40 TEMPO" + + + + + + + + The report status for a TAF report (e.g., a normal issuance, an amendment of an earlier + report, a cancellation of an earlier report) + + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/iwxxm/1.1/common.xsd b/config/schemas/schema/int/wmo/iwxxm/1.1/common.xsd new file mode 100644 index 0000000..de46b6c --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.1/common.xsd @@ -0,0 +1,253 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Common constructs used across multiple packages. This package includes constructs + closely related to the aviation weather domain. + + + Schematron validation + + + + + + + + + + + + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + The vertical visibility. Vertical visibility is defined as the vertical visual range + into an obscuring medium. + + quantity: http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. This extends AerodromeSurfaceWindTrendForecast + to allow for a variable wind direction to be reported. This class differs from a + aerodrome wind observation in that the observations may include a min/max directional + variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type + + + + + + + The observed cloud amount + + + + + + http://codes.wmo.int/common/quantity-kind/heightOfBaseOfCloud + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at + which the air contains a perceptible quantity of cloud particles. + + quantity: http://codes.wmo.int/common/quantity-kind/heightOfBaseOfCloud + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + + http://codes.wmo.int/common/quantity-kind/windDirection + + The forecast average wind direction from which wind is blowing + quantity: http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + http://codes.wmo.int/common/quantity-kind/windSpeed + + The forecast average wind speed + quantity: http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + The forecast maximum speed of a gust. + quantity: http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + + + + + + + + + RelationalOperator defines the restricted set of operators that may be specified alongside + numerical quantities in ICAO Annex 3/WMO No. 49. These operators are used in cases + where a precise value is not measurable, not precisely known due to measurement limitations, + or not reported due to reporting restrictions. For example, the "above" operator + in conjunction with the reported quantity 10.6 indicates that the actual physical + quantity is above 10.6 (at least 10.6). + + + + + + The actual value is above the maximum value that can be determined by the system ("ABV", + "P") + + + + + + The actual value is below the minimum value that can be determined by the system ("BLW", + "M") + + + + + + + + + http://codes.wmo.int/49-2/AerodromeForecastWeather + none + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + Only a specific set of weather phenomenon are reported within aviation meteorology + as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This ?CodeList? is specifically + defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions + are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromeForecastWeather + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/SigConvectiveCloudType + none + + Genus of cloud of operational significance to aviation: significant convective clouds + only. - Cumulonimbus - Towering cumulus This ?CodeList? is specifically defined + for aviation purposes, as defined in WMO No. 49-2. A superset of definitions are defined + in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 012 "Cloud type". + + vocabulary: http://codes.wmo.int/49-2/SigConvectiveCloudType + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + none + + Amount of cloud - assessed by category: - Sky clear (0 oktas) - Few (1 - 2 oktas) + - Scattered (3 - 4 oktas) - Broken (5 - 7 oktas) - Overcast (8 oktas) This ?CodeList? + is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset + of cloud-amount categories are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 20 008 "Cloud distribution for aviation". + + vocabulary: http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + extensibility: none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.1/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/1.1/iwxxm.xsd new file mode 100644 index 0000000..9dfb7f5 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.1/iwxxm.xsd @@ -0,0 +1,37 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, + SPECI, TAF, and SIGMET reports as defined in ICAO Annex 3, Amendment 76. These four + reports are essential operational meteorology products used to enable safe and efficient + air travel worldwide. The report types in this package include: <b> </b><b>== </b>METAR + <b>==</b> Routine report of meteorological conditions made at an aerodrome. METARs + may also include short-term forecasts of meteorological conditions <b> </b>== SPECI + == Special (i.e., non-routine) report of meteorological conditions made at an aerodrome + as needed. SPECIs may also include short-term forecasts of meteorological conditions + <b> </b>== TAF == Routine forecast report of meteorological conditions at an aerodrome + <b> </b>== SIGMET == Meteorological advisory concerning the occurrence and/or expected + occurrence of weather phenomena which may affect the safety of aircraft operations, + such as severe thunderstorms or turbulence This package builds upon the ISO 19100 + family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, + the constructs in this application schema refer to a number of aviation constructs + such as FIR, Aerodrome, and Runway from the Simple Aviation Features package. The + full relationship of this package with external dependencies are shown in the 'Package + Dependencies' diagram. While only four of the reports from Annex 3 are currently + represented, this may be expanded in a future version. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.1/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/1.1/metarSpeci.xsd new file mode 100644 index 0000000..2894d6c --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.1/metarSpeci.xsd @@ -0,0 +1,1042 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. METAR + and SPECI reports include identical information but are issued for different purposes. + METAR reports are routine observations made at an aerodrome throughout the day. METAR + observations are made (and distributed) at intervals of one hour or, if so determined + by regional air navigation agreement, at intervals of one half-hour. SPECI reports + are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI + observations are made (and distributed) in accordance with criteria established by + the meteorological authority, in consultation with the appropriate ATS authority, + operators and others concerned. + + + Schematron validation + + + + + + + + + + + + + + + + + + A report of observed and trend forecast weather phenomenon from the surface near an + aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical + reported information. + + + + + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast. When no change is expected to occur + during a forecast period ("NOSIG") this is indicated by a single missing trend forecast + with a nil reason of noSignificantChange + + + + + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations + are made (and distributed) in accordance with criteria established by the meteorological + authority, in consultation with the appropriate ATS authority, operators and others + concerned. The information contained in METAR and SPECI is identical. SPECI is issued + when conditions merit a non-routine report on conditions at an aerodrome. SPECI reports + are used for dissemination beyond the aerodrome of origin (mainly intended for flight + planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly intervals. + SPECI is issued following the resumption of the issuance of METAR, as necessary, at + aerodromes that are not operational throughout 24 hours in accordance with ICAO Annex + 3 Section 4.3.1. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + SPECI: sampledFeature should be equal in observation and trendForecast + + + + + SPECI: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + SPECI: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations + are made (and distributed) at intervals of one hour or, if so determined by regional + air navigation agreement, at intervals of one half-hour. The information contained + in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine + report on conditions at an aerodrome. METARs are a routine report produced for dissemination + beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET + broadcasts and D-VOLMET. See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + METAR: sampledFeature should be equal in observation and trendForecast + + + + + METAR: Missing reports only include identifying information (time, aerodrome) and + no other information + + + + + + METAR: When no clouds are detected by the auto system, this report must be an auto + report + + + + + + MeteorologicalAerodromeObservation: The sampled feature for a METAR/SPECI is an aerodrome + + + + + MeteorologicalAerodromeObservation: Result should be of appropriate type + + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions for trend forecasting + at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord + which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the NothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. When no clouds + were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason + should be used for the cloud association. + + + + + MeteorologicalAerodromeTrendForecastRecord: clouds should be absent when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeTrendForecastRecord: forecastWeather should be absent when + cloudAndVisibilityOK is true + + + + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + The prevailing horizontal visibility reported in a trend forecast + quantity: http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions observed at an aerodrome. + When no clouds of operational significance or no weather of operational significance + is observed, the NothingOfOperationalSignificance nilReason is used for the cloud + or presentWeather association. When no clouds were detected by the automatic observing + system, the NotDetectedByAutoSystem nilReason is used for the cloud association. + + + + + MeteorologicalAerodromeObservationRecord: should not report visibility when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report rvr when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report presentWeather when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeObservationRecord: Table A3-2 Note 7 states: To be included + if visibility or RVR < 1500 m; for up to a maximum of four runways. This is interpreted + to mean that if the prevailing visibility is below 1500 meters, RVR should always + be included + + + + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/airTemperature + + The observed air temperature. This is the temperature indicated by a thermometer + exposed to the air in a place sheltered from direct solar radiation. + + quantity: http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + + http://codes.wmo.int/common/quantity-kind/dewPointTemperature + + The observed dew point temperature. This is the temperature to which a given air + parcel must be cooled at constant pressure and constant water vapor content in order + for saturation to occur. + + quantity: http://codes.wmo.int/common/quantity-kind/dewPointTemperature + + + + + + + http://codes.wmo.int/common/quantity-kind/altimeterSettingQnh + + The observed QNH altimeter setting. Altitude setting (also known as QNH) is defined + as barometric pressure adjusted to sea level. It is a pressure setting used by pilots, + air traffic control (ATC), and low frequency weather beacons to refer to the barometric + setting which, when set on an aircraft's altimeter, will cause the altimeter to read + altitude above mean sea level within a certain defined region. + + quantity: http://codes.wmo.int/common/quantity-kind/altimeterSettingQnh + + + + + + + + + + + + + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including + the runway contamination, friction, and deposits. + + + + + AerodromeRunwayState: Estimated surface friction must be between 0 and 0.9 + + + + + AerodromeRunwayState: When surface friction is unreliable, no surface friction is + reported + + + + + + AerodromeRunwayState: When all runways are being reported upon, no specific Runway + should be reported + + + + + + AerodromeRunwayState: When a single Runway is reported upon, the allRunways flag should + be missing or false + + + + + + + + + + + The runway to which the conditions apply. The runway may be missing in cases where + all runways are closed due to snow + + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. WMO 306: Table + 0919 + + + + + + + http://codes.wmo.int/common/quantity-kind/runwayContaminationCoverage + + Proportion of runway surface that is contaminated - usually expressed as a percentage + of the total runway area. WMO reporting procedures require that contamination is + reported in the following categories: - less than 10%; - between 11% and 25%; - between + 26% and 50%; and - more than 50%. See WMO No. 306: - WMO Code table 0519 - BUFR + Code table 0 20 087 + + quantity: http://codes.wmo.int/common/quantity-kind/runwayContaminationCoverage + + + + + + + http://codes.wmo.int/common/quantity-kind/depthOfRunwayDeposit + + Depth of deposit on the surface of the runway. See WMO No. 306 WMO Code table 1079. + quantity: http://codes.wmo.int/common/quantity-kind/depthOfRunwayDeposit + + + + + + + http://codes.wmo.int/common/quantity-kind/runwayFrictionCoefficient + + The estimated surface friction for the affected runway. Between 0.0 and 0.9. When + braking conditions are not reported and/or the runway is not operational estimatedSurfaceFriction + will not be reported. WMO 306: Table 0366 + + quantity: http://codes.wmo.int/common/quantity-kind/runwayFrictionCoefficient + + + + + + + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported + together at an aerodrome + + + + + + + + The runway to which reported runway visual range information applies + + + + + + http://codes.wmo.int/common/quantity-kind/runwayVisualRangeRvr + + The mean recent runway visual range value observed. This mean represents the 10 minute + average for observed RVR except when the 10-minute period immediately preceding the + observation includes a marked discontinuity in runway visual range values, only those + values occurring after the discontinuity is used for obtaining mean values. To report + a mean RVR of at least 2000 meters, mean RVR is reported as 2000 meters and the operator + is reported as "above" Annex 3: Table A3-2 "RVR/RVR" Section 4.3.6.6 + + quantity: http://codes.wmo.int/common/quantity-kind/runwayVisualRangeRvr + + + + + + The reported relational operator for the mean RVR. When reported, this operator is + reported in conjunction with mean RVR. To report a mean RVR of at least 2000 meters, + mean RVR is reported as 2000 meters and the operator is reported as "above". When + no operator is reported, mean RVR represents an exact value with identical semantics + to other measured quantities + + + + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. + This includes information on sea-surface temperature and either the state of the sea + or significant wave height from aeronautical meteorological stations established on + offshore structures in support of helicopter operations + + + + + AerodromeSeaState: If the sea state is set, significantWaveHeight is not reported + (one or the other) + + + + + + AerodromeSeaState: If the significantWaveHeight is set, seaState is not reported (one + or the other) + + + + + + AerodromeSeaState: Either seaState or significantWaveHeight must be present + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/seaSurfaceTemperature + + The sea-surface temperature observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations. The term sea surface + temperature is generally meant to be representative of the upper few meters of the + ocean as opposed to the skin temperature, which is the temperature of the upper few + centimeters. ICAO Annex 3 / WMO No. 49-2: Section 4.8.1.5a + + quantity: http://codes.wmo.int/common/quantity-kind/seaSurfaceTemperature + + + + + + The significant wave height observed + + + + + The state of the sea observed by aeronautical meteorological stations established + on offshore structures in support of helicopter operations ICAO Annex 3 / WMO No. + 49-2: Section 4.8.1.5a WMO 306: Table 3700 + + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, + including the set of affected runways. + + + + + AerodromeWindShear: When all runways are affected by wind shear, no specific runways + should be reported + + + + + + + + + + + The specific runway(s) affected by wind shear at this aerodrome. No specific runways + are reported when all runways are affected by wind shear + + + + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, + including cloud types, cloud layers, and vertical visibility. + + + + + AerodromeObservedClouds: Vertical visibility cannot be reported with cloud layers + + + + + AerodromeObservedClouds: When amountAndHeightUnobservableByAutoSystem is true, no + cloud layers may be reported + + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + The reported vertical visibility. Vertical visibility is defined as the vertical + visual range into an obscuring medium. Note: vertical visibility is only reported + in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus + prevailing visibility is considered to be an aviation-specific quantity. When the + sky is obscured and the value of the vertical visibility cannot be determined by the + automatic observing system due to a temporary failure of the system/sensor ("VV///") + the vertical visibility is missing with a nil reason of notObservable + + quantity: http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, + including wind direction information, wind speed, and wind gusts. Wind direction + is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: "variations + from the mean wind direction during the past 10 minutes is reported as follows, if + the total variation is 60 or more: 1) when the total variation is 60 or more and less + than 180 and the wind speed is 1.5 m/s (3 kt) or more, such directional variations + are reported as the two extreme directions between which the surface wind has varied; + 2) when the total variation is 60 or more and less than 180 and the wind speed is + less than 1.5 m/s (3 kt), the wind direction is reported as variable with no mean + wind direction; or 3) when the total variation is 180 or more, the wind direction + is reported as variable with no mean wind direction" + + + + + AerodromeSurfaceWind: All wind UOMs must be the same + + + + + AerodromeSurfaceWind: Wind direction is not reported when variable winds are indicated + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/windDirection + + The observed average wind direction from which the wind is blowing over the past ten + minutes. Not reported when winds are variable + + quantity: http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + http://codes.wmo.int/common/quantity-kind/windSpeed + + The average observed wind speed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2a + + quantity: http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + The maximum wind speed observed over the past ten minutes ICAO Annex 3 / WMO No. + 49-2: Section 4.1.5.2c + + quantity: http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + + http://codes.wmo.int/common/quantity-kind/windDirection + + The extreme clockwise direction from which the wind is blowing, inclusive. ICAO Annex + 3 / WMO No. 49-2: Section 4.1.5.2b + + quantity: http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + http://codes.wmo.int/common/quantity-kind/windDirection + + The extreme counter-clockwise direction from which the wind is blowing, inclusive. + ICAO Annex 3 / WMO No. 49-2: Section 4.1.5.2b + + quantity: http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at + an aerodrome, including the prevailing visibility and minimum visibility. + + + + + + + + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + The reported prevailing horizontal visibility at the surface that is representative + of the aerodrome. The greatest visibility value, observed in accordance with the + definition of "visibility", which is reached within at least half the horizon circle + or within at least half of the surface of the aerodrome. These areas could comprise + contiguous or non-contiguous sectors. Note: This value may be assessed by human observation + and/or instrumented systems. When instruments are installed, they are used to obtain + the best estimate of the prevailing visibility. To report a prevailing visibility + of at least 10000 meters, prevailing visibility is reported as 10000 meters and the + prevailing visibility operator is reported as "above". ICAO Annex 3 / WMO No. 49-2: + Section 4.2.4.4b + + quantity: http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + http://codes.wmo.int/common/quantity-kind/aeronauticalVisibility + + The minimum observed visibility. ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: "When + the visibility is not the same in different directions and a) when the lowest visibility + is different from the prevailing visibility, and 1) less than 1 500 m or 2) + less than 50 percent of the prevailing visibility and less than 5000 m; the lowest + visibility observed should also be reported and,when possible, its general direction + in relation to the aerodrome reference point indicated by reference to one of the + eight points of the compass. If the lowest visibility is observed in more than one + direction, then the most operationally significant direction should be reported; and + b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot + be determined, only the lowest visibility should be reported, with no indication of + direction." + + quantity: http://codes.wmo.int/common/quantity-kind/aeronauticalVisibility + + + + + + + http://codes.wmo.int/common/quantity-kind/aerodromeMinimumVisibilityDirection + + The direction of the minimum visibility relative to the reporting station. This is + optional in cases where minimum visibility is reported but the visibility is fluctuating + rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions + (N, NE, E, SE, S, SW, W, and NW) + + quantity: http://codes.wmo.int/common/quantity-kind/aerodromeMinimumVisibilityDirection + + + + + + + + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. Defined in WMO + No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. Also see WMO No. 306 Vol + I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or + an aerodrome forecast'. + + + + + + No significant changes are forecast (NOSIG) + + + + + When the change is forecast to commence at the beginning of the forecast period and + be completed by the end of that period, or when the change is forecast to occur within + the forecast period but the time of the change is uncertain (possibly shortly after + the beginning of the forecast period, or midway or near the end of that period), the + change is indicated by only the change indicator BECMG. + + + + + + The change indicator TEMPO is used to describe expected temporary fluctuations to + meteorological conditions which reach or pass specified threshold criteria and last + for a period of less than one hour in each instance and in the aggregate cover less + than half of the forecast period during which the fluctuations are expected to occur. + + + + + + + + The tendency of visual range (e.g., upward, downward). Defined for the purposes of + aviation meteorology reporting of the visual range on runways (WMO No. 49-2). If + the [runway] visual range (RVR) values during the 10-minute period preceding the nominal + observation time show a distinct upward or downward tendency such that the mean during + the first five minutes varies by 100 metres or more from the mean in the second five + minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency is recorded. When no + distinct change in RVR is observed, NO CHANGE [N] is recorded. See WMO No. 306 Vol + I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visual range". + + + + + + Upward (increasing) tendency + + + + + No change + + + + + Downward (decreasing) tendency + + + + + + + The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, + correction of an earlier report, etc.) + + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + + + + http://codes.wmo.int/49-2/AerodromeRecentWeather + none + + Weather phenomenon of operational significance to aviation observed during the period + since the last routine report, or last hour, whichever is shorter, but not at the + time of observation. Only a specific set of weather phenomenon are reported within + aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. This CodeList + is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset + of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather + phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromeRecentWeather + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-22-061 + none + + Categorical assessment of sea surface state (or other large open body of water) based + on height of waves. Height in metres : Category - 0 metres : Calm (glassy) - 0-0.1 + metres : Calm (rippled) - 0.1-0.5 metres : Smooth - 0.5-1.25 metres : Slight - 1.25-2.5 + metres : Moderate - 2.5-4 metres : Rough - 4-6 metres : Very rough - 6-9 metres : + High - 9-14 metres : Very high - &gt;14 metres : Phenomenal See WMO No. 306 Vol I.1 + code table 3700 "State of the sea" and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 + 22 061 "State of the sea". + + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-22-061 + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-20-086 + none + + Type of deposit on a runway. See WMO No. 306 Vol I.1 code table 0919 and WMO No. + 306 Vol I.2 FM 94 BUFR code table 0 20 086 "Runway deposits". + + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-20-086 + extensibility: none + + + + + + + + + + http://codes.wmo.int/bufr4/codeflag/0-20-087 + none + + Extent of runway surface that is contaminated (covered) + vocabulary: http://codes.wmo.int/bufr4/codeflag/0-20-087 + extensibility: none + + + + + + + + + + http://codes.wmo.int/49-2/AerodromePresentWeather + none + + The present weather observed at, or in near vicinity of, an aerodrome. Only a specific + set of weather phenomenon are reported within aviation meteorology as defined in Regulation + ICAO Annex 3 / WMO No. 49-2. This CodeList is specifically defined for aviation purposes + as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol + I.1 code-table 4678 "Significant weather phenomena". + + vocabulary: http://codes.wmo.int/49-2/AerodromePresentWeather + extensibility: none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.1/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/1.1/sigmet.xsd new file mode 100644 index 0000000..5f0b919 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.1/sigmet.xsd @@ -0,0 +1,456 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. SIGMETs report + the occurrence and/or expected occurrence of specified en-route weather phenomena + which may affect the safety of aircraft operations, and of the development of those + phenomena in time and space. These weather phenomena are reported as impacted regions + of airspace. + + + Schematron validation + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. + TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. + For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit + of 500FL. In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA + or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to + the sampled feature for this SIGMET. + + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, + volcanic ash, etc.). This geometry covers all combinations of phenomenon historically + reported in Annex 3: a boundary with a base and top, a TC center position, and a VA + line with a width + + + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or + expected occurrence of specified en-route weather phenomena which may affect the safety + of aircraft operations, and of the development of those phenomena over time. The + SIGMET report class represents the base SIGMET types that may be reported such as + squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic + ash SIGMET reports are subclasses of SIGMET due to their ability to report additional + information, including volcano/tropical cyclone identification and forecast position(s). + SIGMETs may report either observed or forecast hazardous conditions. Additionally, + a forecast position may be reported. + + + + + + + + + + The ATS unit serving the FIR or CTA to which the SIGMET refers ICAO Annex 3 / WMO + No. 49-2: A6-1: "Location indicator of FIR/CTA" + + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. + Each observation/forecast phenomenon includes its own period of validity for described + meteorological conditions, which is represented as the O&amp;M Observation validTime. + For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 + UTC with an observed position at 1600 UTC and a forecast position of the centre of + the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 + UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis + validTime would be 2200 UTC. + + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, + must be missing otherwise Examples: YUDD SIGMET 2 VALID ... YUDD SIGMET A3 VALID + ... + + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory + when this is a cancellation report, must be missing otherwise + + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, + etc. The expected end of occurrence of volcanic ash ("NO VA EXP") is indicated with + a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance + + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, + as well as observed and forecast conditions for each of these reported areas. All + combinations of observations and forecasts of meteorological conditions, including + changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon + area within an FIR. These are modeled as a single OM_Observation sub-type with a + feature collection result due to the shared time and other observation metadata for + all forecast positions. + + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic + ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, + speed, and direction. These conditions are reported with OBS/FCST conditions on all + SIGMET types. TC TOP (ABV and BLW) conditions are represented by the vertical component + of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit + and an upperLimit of 500FL. Design note: This class is no longer a subclass of + MeteorologicalPosition. This change was made to ensure that there is no confusion + between the two classes when results from different OM_Observation types are populated. + Constraints could be used to ensure a specific superclass but not its subclasses are + valid, but this would disallow the use of sub-classes of this type for other purposes + such as regional extension + + + + + + + + + + The expected direction of movement of a meteorological condition. When no movement + is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason + and the speedOfMotion will be 0. + + + + + + The expected geographic region affected by the reported phenomenon at a particular + time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of + phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a + base and top, a TC center position, and a VA line with a width + + + + + + The expected speed of movement of a meteorological condition. When no movement is + expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable + nilReason. + + + + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends + the base SIGMET type by including additional information necessary for tropical cyclones. + + + + + TropicalCycloneSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + TropicalCycloneSIGMET: A canceled SIGMET should not have an analysis + + + + + TropicalCycloneSIGMET: There must be at least one analysis when a SIGMET does not + have canceled status + + + + + + TropicalCycloneSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The tropical cyclone being reported in this SIGMET + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions hazardous to flight. + This extends the base SIGMET type by including additional information necessary for + volcanoes and volcanic ash. + + + + + VolcanicAshSIGMET: OBS and FCST classifications must have a result type of EvolvingMeteorologicalCondition + + + + + VolcanicAshSIGMET: A canceled SIGMET should not have an analysis + + + + + VolcanicAshSIGMET: There must be at least one analysis when a SIGMET does not have + canceled status + + + + + + VolcanicAshSIGMET: MeteorologicalPosition must be member of MeteorologicalPositionCollection + + + + + SIGMETEvolvingConditionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETEvolvingConditionAnalysis: Result must be a single EvolvingMeteorologicalPosition + + + + + SIGMETPositionAnalysis: Sampled feature must be an FIR, UIR, or CTA + + + + + SIGMETPositionAnalysis: result must be MeteorologicalPositionCollection + + + + + + + + + + + + The volcano that is erupting + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological + conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. See WMO + No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. + + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + The status of a SIGMET report (e.g., a normal issuance, a cancellation of an earlier + SIGMET) + + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + + + + http://codes.wmo.int/49-2/SigWxPhenomena + none + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET + reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 + sub-clause 1.1.4 + + vocabulary: http://codes.wmo.int/49-2/SigWxPhenomena + extensibility: none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/1.1/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/1.1/taf.xsd new file mode 100644 index 0000000..a88b95d --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/1.1/taf.xsd @@ -0,0 +1,421 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. An Aerodrome + Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome + intended for distribution. TAF reports include base forecast conditions, and modifications + to those conditions throughout the valid period. + + + Schematron validation + + + + + + + + + + + + + + + + + + + An Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended for distribution + beyond an aerodrome. TAF reports report base forecast conditions, and modifications + to those conditions throughout the valid period. TAF reports include similar information + to a METAR/SPECI trend forecast. However, TAF forecast information includes additional + detail. Aerodromes can issue both METAR/SPECI and TAF reports on a routine basis, + but TAFs are not issued by every METAR-reporting aerodrome. The issuance of a new + forecast by a meteorological office, such as a TAF, cancels any forecast of the same + type previously issued for the same place and for the same period of validity or part + thereof. Prevailing conditions and forecast changes differ in that the prevailing + conditions can include temperatures, base conditions do not include a change indicator, + and that forecast changes may report no significant weather (NSW). Rather than have + two class hierarchies, constraints are present ensuring that each (base and forecast + conditions) only include relevant information + + + + + TAF: Forecast conditions cannot include temperature information. They are otherwise + identical to the prevailing conditions + + + + + + TAF: previousReportValidPeriod must be null unless this cancels, corrects or amends + a previous report + + + + + + TAF: An amended report must also include the valid time of the amended report + + + + + TAF: A cancelled report must also include the valid time of the cancelled report + + + + + TAF: A corrected report must reference + + + + + TAF: resultTime for the baseForecast and the changeForecasts must match + + + + + TAF: TAF issue time must match the baseForecast resultTime + + + + + TAF: Base conditions may not have a change indicator + + + + + TAF: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF: PROB30/PROB40 never follows a FROM or BECOMING group + + + + + TAF: Non-missing TAF reports must contains validTime + + + + + MeteorologicalAerodromeForecast: The OM validTime must be a time period for TAF forecasts + + + + + MeteorologicalAerodromeForecast: The sampled feature is always an aerodrome + + + + + + + + + + + + The time at which this report was issued. Note that this should be identical to the + resultTime of each MeteorologicalAerodromeForecast, whose results are made available + at the same time as this report. TAF reports have an issueTime to assist in discovery + and to provide unambiguous semantics at the report level. + + + + + + The time frame at which this report is valid. All forecast elements should be valid + within this period + + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, + this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO + No. 49-2: Section 1.5: "The number of change and probability groups should be kept + to a minimum and should not normally exceed five groups". + + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions forecast at an aerodrome. + This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, + which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI + differ from forecast groups in a TAF. When no clouds of operational significance + or no weather of operational significance is predicted, the nothingOfOperationalSignificance + nilReason should be used for the cloud or presentWeather association. Note that + the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime + on the change forecast (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime + with a TimePeriod (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod + (start is beginning of forecast validity and end is TL) FM - a phenomenonTime + with a TimePeriod (start is FM and end is end of forecast validity) AT - a phenomenonTime + with a TimeInstant + + + + + MeteorologicalAerodromeForecastRecord: Should not report prevailingVisibility when + cloudAndVisibilityOK is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report cloud when cloudAndVisibilityOK + is true + + + + + + MeteorologicalAerodromeForecastRecord: Should not report weather when cloudAndVisibilityOK + is true + + + + + + + + + + + + + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + The prevailing horizontal visibility, mandatory except when ceiling and visibility + is reported as OK + + quantity: http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, + this operator is reported in conjunction with prevailing visibility. To report a + prevailing visibility of at least 10000 meters, prevailing visibility is reported + as 10000 meters and the operator is reported as "above". When no operator is reported, + prevailing visibility represents an exact value with identical semantics to other + measured quantities + + + + + + + + + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together + at an aerodrome, including the minimum and maximum anticipated air temperatures and + when they occur. AerodromeAirTemperatureForecast is only reported on base conditions + on a TAF, not change forecasts. + + + + + + + + + http://codes.wmo.int/common/quantity-kind/airTemperature + + The maximum air temperature ICAO Annex 3 / WMO No. 49-2: "TX" + quantity: http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the maximum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TX" + + + + + + + http://codes.wmo.int/common/quantity-kind/airTemperature + + The minimum air temperature ICAO Annex 3 / WMO No. 49-2: "TN" + quantity: http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the minimum air temperature. This must be within the period + of the phenomenon time for this forecast record ICAO Annex 3 / WMO No. 49-2: "TN" + + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. + This is an extension of ForecastChangeIndicator that includes report-specific entries, + and in particular the 30 and 40% probability conditions. Note that the TAC representations + for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast + (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime with a TimePeriod + (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod (start is + beginning of forecast validity and end is TL) FM - a phenomenonTime with a TimePeriod + (start is FM and end is end of forecast validity) AT - a phenomenonTime with a + TimeInstant Design note: These values represent the operationally-representable types, + but are not very general-purpose. Especially with temporary conditions and probability + it might be better to turn these into a "probability" property and constraints could + be applied to the value to match operational constraints + + + + + + Conditions are expected to reach or pass through specified threshold values at a regular + or irregular rate and at an unspecified time during the time period. The time period + should normally not exceed 2 hours but in any case should not exceed 4 hours. ICAO + Annex 3 / WMO No. 49-2: "BECMG" + + + + + + Expected temporary fluctuations to meteorological conditions which reach or pass specified + threshold criteria and last for a period of less than one hour in each instance and + in the aggregate cover less than half of the forecast period during which the fluctuations + are expected to occur. ICAO Annex 3 / WMO No. 49-2: "TEMPO" + + + + + + One set of prevailing weather conditions is expected to change significantly and more + or less completely to a different set of conditions. Conditions in a FROM group supersede + conditions in earlier groups. ICAO Annex 3 / WMO No. 49-2: "FM" + + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB30" + + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB30 TEMPO" + + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + ICAO Annex 3 / WMO No. 49-2: "PROB40" + + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of + a forecast element or elements. ICAO Annex 3 / WMO No. 49-2: "PROB40 TEMPO" + + + + + + + + The report status for a TAF report (e.g., a normal issuance, an amendment of an earlier + report, a cancellation of an earlier report) + + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/airmet.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/airmet.xsd new file mode 100644 index 0000000..fac88d1 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/airmet.xsd @@ -0,0 +1,279 @@ + + + + + + + + AIRMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These weather phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An AIRMET (significant meteorological) report. AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + +The AIRMET report class represents the base AIRMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. AIRMETs may report either observed or forecast hazardous conditions. + + + + + + + + + The ATS unit serving the FIR or CTA to which the AIRMET refers. ICAO Annex 3 / WMO No. 49-2: A6-1: "Location indicator of FIR/CTA" + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. Each observation/forecast phenomenon includes its own period of validity for described meteorological conditions, which is represented as the O&M Observation validTime. + + + + + The cancelled AIRMET sequence number. Mandatory when this is a cancellation report, must be missing otherwise + +Examples: +YUDD AIRMET 2 VALID ... +YUDD AIRMET A3 VALID ... + + + + + The valid period of a previous AIRMET that is cancelled by this AIRMET. Mandatory when this is a cancellation report, must be missing otherwise + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. + + + + + AIRMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own AIRMETEvolvingMeteorologicalCondition. + +Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + Extension block for optional and/or additional parameters + + + + + + The AIRMET report status - cancelled or normal + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific AIRMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + + + + + + + + + The expected direction of movement of a meteorological condition. When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. Direction of motion to shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The expected geographic region(s) affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. + +To report an airspace lower limit of below FL 300, airspace lower limit is reported as FL 300 and the operator is reported as "below". When no operator is reported, the airspace lower limit represents an exact value with identical semantics to other measured quantities + + + + + The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. + +To report an airspace upper limit of above FL 300, airspace upper limit is reported as FL 300 and the operator is reported as "above". When no operator is reported, the airspace upper limit represents an exact value with identical semantics to other measured quantities + + + + + The expected speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. Speed of movement shall be given in either "km/h" or "[kn_i]" (knot). + + + + + The cloud base of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud base shall be given in either "m" (metres) or "[ft_i]" (feet). + +Cloud base and top may differ from but should be within the AIRMET base and top which are reported in airspace upper and lower limits. + + + + + The reference surface used for the value of the cloud base. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + The cloud top of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud top shall be given in either "m" (metres) or "[ft_i]" (feet). + +Cloud base and top may differ from but should be within the AIRMET base and top which are reported in airspace upper and lower limits. + + + + + The reference surface used for the value of the cloud base. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + The surface visibility. Only used with SFC VIS AIRMETs. Horizontal surface visibility unit of measure shall be given as "m" (metre). + +ICAO Annex 3 / WMO No. 49-2: +Appendix 6 Section 2.1 + + + + + The weather condition(s) causing reduced visibility. + + + + + The widespread surface wind direction. Only used with SFC WIND AIRMETs. Unit of measure shall be given as "deg" in degrees from true North. A true north wind is indicated with a direction of 360. + + + + + The widespread surface wind speed. Only used with SFC WIND AIRMETs. Surface wind speed unit of measure shall be given as "m/s" or "[kn_i]" (knot). + + + + + Extension block for optional and/or additional parameters + + + + + + The expected change in intensity for the reported meteorological condition (e.g., intensifying, weakening, or no change) determined at the time of AIRMET analysis based on the current state of the meteorological condition + + + + + Indication whether the information is observed and expected to continue, or forecast + + + + + Indicator of whether the location of phenomena is approximate. If not reported locations are not approximate + + + + + + + + + + + + + + + The status of an AIRMET report (e.g., a normal issuance, a cancellation of an earlier AIRMET) + + + + + A normal AIRMET report (not a cancellation) + + + + + A cancellation of an earlier AIRMET report + + + + + + + Expected change in intensity for (significant) meteorological phenomena. + +This is a copy of the ExpectedIntensityChange enumeration found in IWXXM 1.0. This copy removes the need for a dependency on IWXXM. + +See WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + Weather phenomenon of significance to aviation operations; used in AIRMET reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 sub-clause 1.1.4 + + http://codes.wmo.int/49-2/AirWxPhenomena + none + + + + + + + + + A weather condition reducing visibility, such as dust, rain or volcanic ash. + +See ICAO Annex 3/ WMO No. 49-2 Appendix 6 Section 2.1. + + http://codes.wmo.int/49-2/WeatherCausingVisibilityReduction + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/common.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/common.xsd new file mode 100644 index 0000000..bfe3164 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/common.xsd @@ -0,0 +1,407 @@ + + + + + + + Common constructs used across multiple packages. This package includes constructs closely related to the aviation weather domain. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + The base type for all reports, including information that is common across all report types + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + The permissible usage of this report (operational or non-operational) + + + + + The permissible usage reason of this report. Only populated when the permissible usage is non-operational + + + + + Additional human-readable descriptive information regarding the permissible usage. Only populated when the permissible usage is non-operational + + + + + The TAC bulletin ID that was translated, of the form 'TTAAiiCCCYYGGgg' + + + + + The time at which the translated TAC bulletin was received by the translation centre + + + + + The ICAO designator of the centre which performed translation from TAC to XML + + + + + The name of the translation centre which performed translation from TAC to XML + + + + + The time at which translation was performed from TAC to XML + + + + + The full, original TAC that could not be translated. When translation fails only the report type (i.e, SIGMET or METAR), translation information and other basic report metadata should be provided. In this case no translated content will be included other than the original TAC. Translation is considered to have failed when either not all of the TAC could be understood by the translation software or not all of the mandatory TAC content could be found. Permissible usage may be set as normal and TAC that failed translation may still be used for operational purposes, but under no circumstances should partially translated content be distributed or marked as operational + + + + + + + + + + + + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + +A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + + + + The vertical visibility. Vertical visibility is defined as the vertical visual range into an obscuring medium. + +Vertical visibility shall be reported either in meters ("m") or feet ("[ft_i]"). + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. Wind speeds and gusts, if present, shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + +This extends AerodromeSurfaceWindTrendForecast to allow for a variable wind direction to be reported. This class differs from a aerodrome wind observation in that the observations may include a min/max directional variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + Indicates variable wind direction. Cannot be reported with a mean wind direction + + + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + The forecast average wind direction from which wind is blowing. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The forecast average wind speed. + +Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". + +When no operator is reported, wind speed is an exact value with identical semantics to other measured quantities. + + + + + The forecast maximum speed of a gust. + +Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". + +When no operator is reported, wind gust speed is an exact value with identical semantics to other measured quantities. + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type. + + + + + + + The observed cloud amount + + + + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at which the air contains a perceptible quantity of cloud particles. + +Measured cloud bases shall be reported in meters ("m") or feet ("[ft_i]"). + + http://codes.wmo.int/common/quantity-kind/heightOfBaseOfCloud + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + + + + + + + + + RelationalOperator defines the restricted set of operators that may be specified alongside numerical quantities in ICAO Annex 3/WMO No. 49. + +These operators are used in cases where a precise value is not measurable, not precisely known due to measurement limitations, or not reported due to reporting restrictions. + +For example, the "above" operator in conjunction with the reported quantity 10.6 indicates that the actual physical quantity is above 10.6 (at least 10.6). + + + + + The actual value is above the maximum value that can be determined by the system ("ABV", "P") + + + + + The actual value is below the minimum value that can be determined by the system ("BLW", "M") + + + + + + + PermissibleUsage defines the restricted set of permitted usages of data + + + + + Data may be used for operational purposes + + + + + Data should not be used for operational purposes, but may be used for other purposes + + + + + + + PermissibleUsageReason defines the restricted set of reasons for non-operational data + + + + + Data is part of a test activity and should not be used for operational purposes. This may include circumstances such as issuing a single message to assess a new data network path, or as part of a more organized test of message distribution/availability such as a regional SIGMET test + + + + + Data is part of a test exercise and should not be used for operational purposes. This may include circumstances where realistic data is issued to be used in organized exercises where users will practice or train for potential scenarios. For example, VA SIGMET exercises may include realistic data which is intended to be considered by users participating in the exercise but is not intended for operational use + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Whether the information is observed and expected to continue, or forecast + + + + + The information is observed + + + + + The information is predicated or estimated to occur at some point in the future + + + + + + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather + none + + + + + + + + + Genus of cloud of operational significance to aviation: significant convective clouds only. + +- Cumulonimbus +- Towering cumulus + +This CodeList is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 012 "Cloud type". + + http://codes.wmo.int/49-2/SigConvectiveCloudType + none + + + + + + + + + Amount of cloud - assessed by category: + +- Sky clear (0 oktas) +- Few (1 - 2 oktas) +- Scattered (3 - 4 oktas) +- Broken (5 - 7 oktas) +- Overcast (8 oktas) + +This CodeList is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset of cloud-amount categories are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 008 "Cloud distribution for aviation". + + http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/gmliwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/gmliwxxm.xsd new file mode 100644 index 0000000..88bce36 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/gmliwxxm.xsd @@ -0,0 +1,748 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AngleType,gml:SpeedType,gml:LengthType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:ReferenceType,gml:TimePeriodPropertyType,gml:AbstractGML,gml:AbstractGMLType,gml:AbstractObject,gml:NilReasonType,gml:MeasureType,gml:ScaleType,gml:TimeInstantPropertyType, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. + + + + + + + + + + gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. +The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. +Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. +Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:RelatedTimeType provides a content model for indicating the relative position of an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive. It extends the generic gml:TimePrimitivePropertyType with an XML attribute relativePosition, whose value is selected from the set of 13 temporal relationships identified by Allen (1983) + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:TimePrimitivePropertyType provides a standard content model for associations between an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive and another object. + + + + + + + + + + gml:AbstractTimePrimitive acts as the head of a substitution group for geometric and topological temporal primitives. + + + + + gml:AbstractTimeObject acts as the head of a substitution group for all temporal primitives and complexes. + + + + + The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. +Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system . +In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps. +Three XML attributes appear on gml:TimePositionType: +A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI. +For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era. +Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration. + + + + + + + + + + + + The simple type gml:TimePositionUnion is a union of XML Schema simple types which instantiate the subtypes for temporal position described in ISO 19108. + An ordinal era may be referenced via URI. A decimal value may be used to indicate the distance from the scale origin . time is used for a position that recurs daily (see ISO 19108:2002 5.4.4.2). + Finally, calendar and clock forms that support the representation of time in systems based on years, months, days, hours, minutes and seconds, in a notation following ISO 8601, are assembled by gml:CalDate + + + + + + + + + + + + + + + These values are interpreted as follows: +- "unknown" indicates that no specific value for temporal position is provided. +- "now" indicates that the specified value shall be replaced with the current temporal position whenever the value is accessed. +- "before" indicates that the actual temporal position is unknown, but it is known to be before the specified value. +- "after" indicates that the actual temporal position is unknown, but it is known to be after the specified value. +A value for indeterminatePosition may +- be used either alone, or +- qualify a specific value for temporal position. + + + + + + + + + + + gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. + + + + + + + + + + gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. + + + + + + + + + + + + + + This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. + + + + + gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. +A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. +The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. + + + + + The length of a time period. + + + + + + + + + gml:duration conforms to the ISO 8601 syntax for temporal length as implemented by the XML Schema duration type. + + + + + gml:timeInterval conforms to ISO 11404 which is based on floating point values for temporal length. +ISO 11404 syntax specifies the use of a positiveInteger together with appropriate values for radix and factor. The resolution of the time interval is to one radix ^(-factor) of the specified time unit. +The value of the unit is either selected from the units for time intervals from ISO 31-1:1992, or is another suitable unit. The encoding is defined for GML in gml:TimeUnitType. The second component of this union type provides a method for indicating time units other than the six standard units given in the enumeration. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm-collect.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm-collect.xsd new file mode 100644 index 0000000..a5b3591 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm-collect.xsd @@ -0,0 +1,8 @@ + + + + + + A convenience schema file for validating against IWXXM and WMO Collect. This is useful for XML validators (such as libxml2) that allow only a single schema location. + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm.xsd new file mode 100644 index 0000000..6bed9d7 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/iwxxm.xsd @@ -0,0 +1,27 @@ + + + + + + + + + + + + + + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, SPECI, TAF, and other reports as defined in ICAO Annex 3, Amendment 76. IWXXM reports are essential operational meteorology products used to enable safe and efficient air travel worldwide. + +The report types in this package include METAR, SPECI, TAF, SIGMET, AIRMET, Volcanic Ash Advisory (VAA), and Tropical Cyclone Advisory (TCA). + +This package builds upon the ISO 19100 family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, the constructs in this application schema refer to a number of aviation constructs such Runway and Airspace from AIXM. The full relationship of this package with external dependencies are shown in the 'Package Dependencies' diagram. + +Not all of the reports types from Annex 3 are currently represented, this may be expanded in a future version. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + gmliwxxm.xsd + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/measures.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/measures.xsd new file mode 100644 index 0000000..24cba26 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/measures.xsd @@ -0,0 +1,45 @@ + + + + + Common measured quantities used across multiple packages. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + A nillable Angle quantity. Unlike the base Angle measure, references to this type may be nil and may include a nilReason + + + + + + + + + + + + A nillable Distance quantity. Unlike the base Distance measure, references to this type may be nil and may include a nilReason + + + + + + + + + + + + A nillable Length quantity. Unlike the base Length measure, references to this type may be nil and include a nilReason + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/metarSpeci.xsd new file mode 100644 index 0000000..a697ee7 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/metarSpeci.xsd @@ -0,0 +1,850 @@ + + + + + + + + METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +METAR and SPECI reports include identical information but are issued for different purposes. + +METAR reports are routine observations made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. + +SPECI reports are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + A report of observed and trend forecast weather phenomenon from the surface near an aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical reported information. + + + + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast. When no change is expected to occur during a forecast period ("NOSIG") this is indicated by a single missing trend forecast with a nil reason of noSignificantChange + + + + + Extension block for optional and/or additional parameters + + + + + + The report status (e.g., normal, corrected) + + + + + When true, this report was reported by an automated station. + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. + +The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. + +SPECI reports are used for dissemination beyond the aerodrome of origin (mainly intended for flight planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly intervals. + +SPECI is issued following the resumption of the issuance of METAR, as necessary, at aerodromes that are not operational throughout 24 hours in accordance with ICAO Annex 3 Section 4.3.1. + +See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. + +The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. + +METARs are a routine report produced for dissemination beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET broadcasts and D-VOLMET. + +See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions for trend forecasting at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. + +When no clouds of operational significance or no weather of operational significance is predicted, the NothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. When no clouds were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason should be used for the cloud association. + + + + + + + + + The prevailing horizontal visibility reported in a trend forecast. + +Prevailing horizontal visibility shall be reported in meters ("m"). + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + + + + Extension block for optional and/or additional parameters + + + + + + The change indicator for this trend forecast - becoming, temporary conditions, or no significant change + + + + + When true, indicates that the observed cloud ceiling, horizontal visibility, and weather conditions are of no operational significance. See ICAO Annex 3 / WMO No. 49-2 Section 2.2. Also known as "CAVOK" + +When CAVOK conditions are observed, no other information on visibility, runway visual range, present weather, cloud amount, or cloud type is reported + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions observed at an aerodrome. + +When no clouds of operational significance or no weather of operational significance is observed, the NothingOfOperationalSignificance nilReason is used for the cloud or presentWeather association. When no clouds were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason is used for the cloud association. + + + + + + + + + The observed air temperature. This is the temperature indicated by a thermometer exposed to the air in a place sheltered from direct solar radiation. + +Measured air temperature shall be given in degrees Celsius ("Cel"). + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The observed dew point temperature. This is the temperature to which a given air parcel must be cooled at constant pressure and constant water vapor content in order for saturation to occur. + +Measured dew-point temperature shall be given in degrees Celsius ("Cel"). + + http://codes.wmo.int/common/quantity-kind/dewPointTemperature + + + + + + The observed QNH altimeter setting. + +Altitude setting (also known as QNH) is defined as barometric pressure adjusted to sea level. It is a pressure setting used by pilots, air traffic control (ATC), and low frequency weather beacons to refer to the barometric setting which, when set on an aircraft's altimeter, will cause the altimeter to read altitude above mean sea level within a certain defined region. + +Measured altimeter setting shall be given in hectoPascals ("hPa"). + + http://codes.wmo.int/common/quantity-kind/altimeterSettingQnh + + + + + + + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + When true, indicates that the observed cloud ceiling, horizontal visibility, and weather conditions are of no operational significance. See ICAO Annex 3 / WMO No. 49-2 Section 2.2. Also known as "CAVOK" + +When CAVOK conditions are observed, no other information on visibility, runway visual range, present weather, cloud amount, or cloud type is reported + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including the runway contamination, friction, and deposits. + + + + + + + The runway to which the conditions apply. The runway may be missing in cases where all runways are closed due to snow + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. + +WMO 306: +Table 0919 + + + + + Proportion of runway surface that is contaminated - usually expressed as a percentage of the total runway area. + +WMO reporting procedures require that contamination is reported in the following categories: +- less than 10%; +- between 11% and 25%; +- between 26% and 50%; and +- more than 50%. + +See WMO No. 306: +- WMO Code table 0519 +- BUFR Code table 0 20 087 + + http://codes.wmo.int/common/quantity-kind/runwayContaminationCoverage + + + + + + Depth of deposit on the surface of the runway. + +Measured depth of deposit shall be given in millimeters ("mm"). + +See WMO No. 306 WMO Code table 1079. + + http://codes.wmo.int/common/quantity-kind/depthOfRunwayDeposit + + + + + + The estimated surface friction or braking action for the affected runway. When braking conditions are not reported and/or the runway is not operational estimatedSurfaceFrictionOrBrakingAction will not be reported. + +WMO 306: +Table 0366 + + + + + + When true, indicates the reported conditions apply to all runways + + + + + Indicates that reported runway has been cleared of meteorological deposits, such as snow. + +ICAO Annex 3 / WMO No. 49-2: +"CLRD" + +Section 4.8.1.5, Table A3-2 "State of the runway" + + + + + Indicates whether the aerodrome is closed due to an extreme deposit of snow. This affects all runways +<b> +</b>WMO 306: +Section 15.13.6.1 + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported together at an aerodrome + + + + + + + The runway to which reported runway visual range information applies + + + + + The mean recent runway visual range value observed. This mean represents the 10 minute average for observed RVR except when the 10-minute period immediately preceding the observation includes a marked discontinuity in runway visual range values, only those values occurring after the discontinuity is used for obtaining mean values. + +Mean runway visual range distance shall be reported in meters ("m"). + +To report a mean RVR of at least 2000 meters, mean RVR is reported as 2000 meters and the operator is reported as "above" + +Annex 3: +Table A3-2 "RVR/RVR" +Section 4.3.6.6 + + http://codes.wmo.int/common/quantity-kind/runwayVisualRangeRvr + + + + + + The reported relational operator for the mean RVR. When reported, this operator is reported in conjunction with mean RVR. + +To report a mean RVR of at least 2000 metres, mean RVR is reported as 2000 metres and the operator is reported as "above". To report a mean RVR of less than 50 metres, mean RVR is reported as 50 metres and the operator is reported as "below". When no operator is reported, mean RVR represents an exact value with identical semantics to other measured quantities + + + + + + The runway visual range tendency (up, down, none). + +If the runway visual range values during the 10-minute period have shown a distinct tendency, such that the mean during the first 5 minutes varies by 100 m or more from the mean during the second 5 minutes of the period, this should be indicated. When the variation of the runway visual range values shows an upward or downward tendency, this should be indicated by "Up" or "Down", respectively. In circumstances when actual fluctuations during the 10-minute period show no distinct tendency, this should be indicated using "No Change?. When indications of tendency are not available, no information should be reported + +ICAO Annex 3 / WMO No. 49: +Table A3-2 Note 9 +Section 4.3.6.6a + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. This includes information on sea-surface temperature and either the state of the sea or significant wave height from aeronautical meteorological stations established on offshore structures in support of helicopter operations + + + + + + + The sea-surface temperature observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations. + +The term sea surface temperature is generally meant to be representative of the upper few meters of the ocean as opposed to the skin temperature, which is the temperature of the upper few centimeters. + +Temperatures shall be reported in degrees Celsius ("Cel"). + +ICAO Annex 3 / WMO No. 49-2: +Section 4.8.1.5a + + http://codes.wmo.int/common/quantity-kind/seaSurfaceTemperature + + + + + + The significant wave height observed. + +Significant wave height shall be reported in meters ("m"). + + + + + The state of the sea observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations + +ICAO Annex 3 / WMO No. 49-2: +Section 4.8.1.5a + +WMO 306: +Table 3700 + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, including the set of affected runways. + + + + + + + The specific runway(s) affected by wind shear at this aerodrome. No specific runways are reported when all runways are affected by wind shear + + + + + + When true, all runways are observed to have wind shear + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, including cloud types, cloud layers, and vertical visibility. + + + + + + + The reported vertical visibility. Vertical visibility is defined as the vertical visual range into an obscuring medium. + +Measured vertical visibility shall be reported in either two units of measures: meters ("m") or feet ("[ft_i]"). + +Note: vertical visibility is only reported in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus prevailing visibility is considered to be an aviation-specific quantity. + +When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing system due to a temporary failure of the system/sensor ("VV///") the vertical visibility is missing with a nil reason of notObservable + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, including wind direction information, wind speed, and wind gusts. + +Wind direction is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: +"variations from the mean wind direction during the past 10 minutes is reported as follows, if the total variation is 60 or more: +1) when the total variation is 60 or more and less than 180 and the wind speed is 1.5 m/s (3 kt) or more, such directional variations are reported as the two extreme directions between which the surface wind has varied; +2) when the total variation is 60 or more and less than 180 and the wind speed is less than 1.5 m/s (3 kt), the wind direction is reported as variable with no mean wind direction; or +3) when the total variation is 180 or more, the wind direction is reported as variable with no mean wind direction" + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. Wind speeds and gusts, if present, shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + + + + + + The observed average wind direction from which the wind is blowing over the past ten minutes. Not reported when winds are variable. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The average observed wind speed over the past ten minutes + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2a + +Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". + +When no operator is reported, wind speed is an exact value with identical semantics to other measured quantities. + + + + + The maximum wind speed observed over the past ten minutes + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2c + +Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". + +When no operator is reported, wind gust speed is an exact value with identical semantics to other measured quantities. + + + + + The extreme clockwise direction from which the wind is blowing, inclusive. + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2b + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The extreme counter-clockwise direction from which the wind is blowing, inclusive. + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2b + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + When true, indicates that the wind direction is variable. A wind direction value may still be reported + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at an aerodrome, including the prevailing visibility and minimum visibility. + +Direction of minimum visibility shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". +Measured prevailing and minimum horizontal visibility, if present, shall be reported in meters ("m") only. + + + + + + + The reported prevailing horizontal visibility at the surface that is representative of the aerodrome. + +Measured prevailing horizontal visibility shall be reported in meters ("m") only. + +The greatest visibility value, observed in accordance with the definition of "visibility", which is reached within at least half the horizon circle or within at least half of the surface of the aerodrome. These areas could comprise contiguous or non-contiguous sectors. + +Note: This value may be assessed by human observation and/or instrumented systems. When instruments are installed, they are +used to obtain the best estimate of the prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the prevailing visibility operator is reported as "above". + +ICAO Annex 3 / WMO No. 49-2: +Section 4.2.4.4b + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + The minimum observed visibility. + +Measured minimum visibility shall be reported in meters ("m") only. + +ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: +"When the visibility is not the same in different directions and +a) when the lowest visibility is different from the prevailing visibility, and + 1) less than 1 500 m or + 2) less than 50 percent of the prevailing visibility and less than 5000 m; the lowest visibility observed should also be reported and,when possible, its general direction in relation to the aerodrome reference point indicated by reference to one of the +eight points of the compass. If the lowest visibility is observed in more than one direction, then the most +operationally significant direction should be reported; and +b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot be determined, only the lowest visibility +should be reported, with no indication of direction." + + http://codes.wmo.int/common/quantity-kind/aeronauticalVisibility + + + + + + The direction of the minimum visibility relative to the reporting station. This is optional in cases where minimum visibility is reported but the visibility is fluctuating rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions (N, NE, E, SE, S, SW, W, and NW) + +Direction of minimum visibility shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + http://codes.wmo.int/common/quantity-kind/aerodromeMinimumVisibilityDirection + + + + + + + + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. + +Defined in WMO No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. + +Also see WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or an aerodrome forecast'. + + + + + No significant changes are forecast (NOSIG) + + + + + When the change is forecast to commence at the beginning of the forecast period and be completed by the end of that period, or when the change is forecast to occur within the forecast period but the time of the change is uncertain (possibly shortly after the beginning of the forecast period, or midway or near the end of that period), the change is indicated by only the change indicator BECMG. + + + + + The change indicator TEMPO is used to describe expected temporary fluctuations to meteorological conditions which reach or pass specified threshold criteria and last for a period of less than one hour in each instance and in the aggregate cover less than half of the forecast period during which the fluctuations are expected to occur. + + + + + + + The tendency of visual range (e.g., upward, downward). Defined for the purposes of aviation meteorology reporting of the visual range on runways (WMO No. 49-2). + +If the [runway] visual range (RVR) values during the 10-minute period preceding the nominal observation time show a distinct upward or downward tendency such that the mean during the first five minutes varies by 100 metres or more from the mean in the second five minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency is recorded. When no distinct change in RVR is observed, NO CHANGE [N] is recorded. When it is not possible to determine the tendency, MISSING VALUE is recorded. + +See WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visual range". + + + + + Upward (increasing) tendency + + + + + No distinct change + + + + + Downward (decreasing) tendency + + + + + Missing value + + + + + + + The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, correction of an earlier report, etc.) + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + + + Weather phenomenon of operational significance to aviation observed during the period since the last routine report, or last hour, whichever is shorter, but not at the time of observation. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromeRecentWeather + none + + + + + + + + + Categorical assessment of sea surface state (or other large open body of water) based on height of waves. + +Height in metres : Category +- 0 metres : Calm (glassy) +- 0-0.1 metres : Calm (rippled) +- 0.1-0.5 metres : Smooth +- 0.5-1.25 metres : Slight +- 1.25-2.5 metres : Moderate +- 2.5-4 metres : Rough +- 4-6 metres : Very rough +- 6-9 metres : High +- 9-14 metres : Very high +- >14 metres : Phenomenal + +See WMO No. 306 Vol I.1 code table 3700 "State of the sea" and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 22 061 "State of the sea". + + http://codes.wmo.int/bufr4/codeflag/0-22-061 + none + + + + + + + + + Type of deposit on a runway. + +See WMO No. 306 Vol I.1 code table 0919 and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 20 086 "Runway deposits". + + http://codes.wmo.int/bufr4/codeflag/0-20-086 + none + + + + + + + + + Extent of runway surface that is contaminated (covered) + + http://codes.wmo.int/bufr4/codeflag/0-20-087 + none + + + + + + + + + + Extent of runway surface that is contaminated (covered) + + http://codes.wmo.int/bufr4/codeflag/0-20-089 + none + + + + + + + + + The present weather observed at, or in near vicinity of, an aerodrome. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/sigmet.xsd new file mode 100644 index 0000000..e4826bf --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/sigmet.xsd @@ -0,0 +1,371 @@ + + + + + + + + + SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These weather phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + +In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to the sampled feature for this SIGMET. + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in Annex 3: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + Extension block for optional and/or additional parameters + + + + + + Indicator of whether the location of phenomena is approximate. If not reported locations are not approximate + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + +The SIGMET report class represents the base SIGMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic ash SIGMET reports are subclasses of SIGMET due to their ability to report additional information, including volcano/tropical cyclone identification and forecast position(s). + +SIGMETs may report either observed or forecast hazardous conditions. Additionally, a forecast position may be reported. + + + + + + + + + The ATS unit serving the FIR or CTA to which the SIGMET refers + +ICAO Annex 3 / WMO No. 49-2: +A6-1: "Location indicator of FIR/CTA" + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. Each observation/forecast phenomenon includes its own period of validity for described meteorological conditions, which is represented as the O&M Observation validTime. + +For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 UTC with an observed position at 1600 UTC and a forecast position of the centre of the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis validTime would be 2200 UTC. + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, must be missing otherwise + +Examples: +YUDD SIGMET 2 VALID ... +YUDD SIGMET A3 VALID ... + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory when this is a cancellation report, must be missing otherwise + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. + +The expected end of occurrence of volcanic ash ("NO VA EXP") is indicated with a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + +Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon area within an FIR. These are modeled as a single OM_Observation sub-type with a feature collection result due to the shared time and other observation metadata for all forecast positions. + + + + + The FIR to which volcanic ash has moved. Reported only on SIGMET cancellation reports + + + + + Extension block for optional and/or additional parameters + + + + + + The SIGMET report status - cancelled or normal + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + +directionOfMotion element refers to the direction which the phenomenon is moving towards, .e.g, "moving to the east". directionOfMotion is given in degrees from true North. Plane angle unit of measure (uom) is "deg". + +speedOfMotion can be provided in either two units of measures: "km/h" or "kn_i" (knots). + + + + + + + + + This element refers to the expected direction of movement which the phenomenon is moving towards, .e.g, "moving east". When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. + +This element value is given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The expected geographic region(s) affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. + +To report an airspace lower limit of below FL 300, airspace lower limit is reported as FL 300 and the operator is reported as "below". When no operator is reported, the airspace lower limit represents an exact value with identical semantics to other measured quantities + + + + + The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. + +To report an airspace upper limit of above FL 300, airspace upper limit is reported as FL 300 and the operator is reported as "above". When no operator is reported, the airspace upper limit represents an exact value with identical semantics to other measured quantities + + + + + The expected speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. + +speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i]" (knots). + + + + + Extension block for optional and/or additional parameters + + + + + + The expected change in intensity for the reported meteorological condition (e.g., intensifying, weakening, or no change) determined at the time of SIGMET analysis based on the current state of the meteorological condition + + + + + Indication whether the information is observed and expected to continue, or forecast + + + + + Indicator of whether the location of phenomena is approximate. If not reported locations are not approximate + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends the base SIGMET type by including additional information necessary for tropical cyclones. + + + + + + + + + The tropical cyclone being reported in this SIGMET. + +When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclone is unnamed + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions hazardous to flight. This extends the base SIGMET type by including additional information necessary for volcanoes and volcanic ash. + + + + + + + + + The volcano that is erupting + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. + +See WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity' + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + The status of a SIGMET report (e.g., a normal issuance, a cancellation of an earlier SIGMET) + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 sub-clause 1.1.4 + + http://codes.wmo.int/49-2/SigWxPhenomena + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/taf.xsd new file mode 100644 index 0000000..816adb6 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/taf.xsd @@ -0,0 +1,309 @@ + + + + + + + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +An Aerodrome Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome intended for distribution. TAF reports include base forecast conditions, and modifications to those conditions throughout the valid period. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended for distribution beyond an aerodrome. TAF reports report base forecast conditions, and modifications to those conditions throughout the valid period. + +TAF reports include similar information to a METAR/SPECI trend forecast. However, TAF forecast information includes additional detail. + +Aerodromes can issue both METAR/SPECI and TAF reports on a routine basis, but TAFs are not issued by every METAR-reporting aerodrome. + +The issuance of a new forecast by a meteorological office, such as a TAF, cancels any forecast of the same type previously issued for the same place and for the same period of validity or part thereof. + +Prevailing conditions and forecast changes differ in that the prevailing conditions can include temperatures, base conditions do not include a change indicator, and that forecast changes may report no significant weather (NSW). Rather than have two class hierarchies, constraints are present ensuring that each (base and forecast conditions) only include relevant information + + + + + + + + + The time at which this report was issued. Note that this should be identical to the resultTime of each MeteorologicalAerodromeForecast, whose results are made available at the same time as this report. TAF reports have an issueTime to assist in discovery and to provide unambiguous semantics at the report level. + + + + + The time frame at which this report is valid. All forecast elements should be valid within this period + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO No. 49-2: Section 1.5: "The number of change and probability groups should be kept to a minimum and should not normally exceed five groups". + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + Extension block for optional and/or additional parameters + + + + + + The status of this report, including amended, cancelled, normal, or corrected. + +Missing reports indicate that a report was not issued from the responsible reporting party as expected. Missing reports are typically issued by third parties that were expecting a report. + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions forecast at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. + +When no clouds of operational significance or no weather of operational significance is predicted, the nothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. + +Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): + FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) + TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL) + FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity) + AT - a phenomenonTime with a TimeInstant + + + + + + + + + The prevailing horizontal visibility, mandatory except when ceiling and visibility is reported as OK + +Prevailing horizontal visibility shall be reported in meters ("m"). + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + The type of change being reported (FROM, BECOMING, TEMPORARY, etc.). + +A change indicator is required for all MeteorologicalAerodromeForecastRecords excepting reported base conditions. + + + + + When true, indicates that the observed cloud ceiling, horizontal visibility, and weather conditions are of no operational significance. See ICAO Annex 3 / WMO No. 49-2 Section 2.2. Also known as "CAVOK" + +When CAVOK conditions are observed, no other information on visibility, runway visual range, present weather, cloud amount, or cloud type is reported + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together at an aerodrome, including the minimum and maximum anticipated air temperatures and when they occur. + +AerodromeAirTemperatureForecast is only reported on base conditions on a TAF, not change forecasts. + + + + + + + The maximum air temperature expressed in degrees Celsius ("Cel") + +ICAO Annex 3 / WMO No. 49-2: +"TX" + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the maximum air temperature. This must be within the period of the phenomenon time for this forecast record + +ICAO Annex 3 / WMO No. 49-2: +"TX" + + + + + The minimum air temperature expressed in degrees Celsius ("Cel") + +ICAO Annex 3 / WMO No. 49-2: +"TN" + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the minimum air temperature. This must be within the period of the phenomenon time for this forecast record + +ICAO Annex 3 / WMO No. 49-2: +"TN" + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. This is an extension of ForecastChangeIndicator that includes report-specific entries, and in particular the 30 and 40% probability conditions. + +Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): + FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) + TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL) + FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity) + AT - a phenomenonTime with a TimeInstant + + + + + Conditions are expected to reach or pass through specified threshold values at a regular or irregular rate and at an unspecified time during the time period. The time period should normally not exceed 2 hours but in any case should not exceed 4 hours. + +ICAO Annex 3 / WMO No. 49-2: +"BECMG" + + + + + Expected temporary fluctuations to meteorological conditions which reach or pass specified threshold criteria and last for a period of less than one hour in each instance and in the aggregate cover less than half of the forecast period during which the fluctuations are expected to occur. + +ICAO Annex 3 / WMO No. 49-2: +"TEMPO" + + + + + One set of prevailing weather conditions is expected to change significantly and more or less completely to a different set of conditions. Conditions in a FROM group supersede conditions in earlier groups. + +ICAO Annex 3 / WMO No. 49-2: +"FM" + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB30" + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB30 TEMPO" + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB40" + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB40 TEMPO" + + + + + + + The report status for a TAF report (e.g., a normal issuance, an amendment of an earlier report, a cancellation of an earlier report) + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/tropicalCycloneAdvisory.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/tropicalCycloneAdvisory.xsd new file mode 100644 index 0000000..6c2686a --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/tropicalCycloneAdvisory.xsd @@ -0,0 +1,182 @@ + + + + + + + Tropical Cyclone Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +Tropical Cyclone Advisories (TCA) report the occurrence and/or expected occurrence of tropical cyclone phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An advisory of tropical cyclone conditions of significance to aviation as represented in ICAO Annex 3 / WMO No. 49-2. Tropical cyclone advisories are issued by tropical cyclone advisory centres (TCACs) + + + + + + + + + The time at which this advisory was issued + + + + + The issuing TCAC + + + + + The tropical cyclone name. If the tropical cyclone is unnamed, 'NN' may be used + + + + + Advisory number, starting with 1 for each cyclone + + + + + The observed conditions of the tropical cyclone + + + + + The forecast conditions of the tropical cyclone, one each for the 6 hour, 12 hour, 18 hour, and 24 hour forecast periods + + + + + Remarks, as necessary + + + + + The time at which the next advisory is expected to be issued. + +When no subsequent advisory is expected to be issued it should be indicated by a missing expected advisory time with a nil reason of 'inapplicable' + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + Observed conditions of a tropical cyclone + + + + + + + + + The movement observed for the tropical cyclone + + + + + The movement direction observed. Only reported when the tropical cyclone is moving at least 6 km/hour or 3 knots. Direction of movement shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The movement speed observed. Only reported when the tropical cyclone is moving at least 6 km/hour or 3 knots. Speed of movement shall be provided in either two units of measures: "km/h" or "[kn_i]" (knot). + + + + + The central pressure of the tropical cyclone. Central pressure of cyclone shall be provided in hectoPascals (hPa). + + + + + The mean maximum surface wind near the cyclone centre over 10 minutes. Mean maximum wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + Forecast conditions of a tropical cyclone + + + + + + + + + The forecast maximum surface wind speed. Maximum wind speeds shall be provided in either two units of measures: "m/s"or "[kn_i]" (knot). + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + The movement type for a tropical cyclone, either MOVING, MOVING_SLOWLY, or STATIONARY + + + + + The tropical cyclone is moving and will be reported with the associated movement speed and direction + + + + + The tropical cyclone is moving slowly (< 6 km/h or 3 kt) and will not have a reported movement speed or direction + + + + + The tropical cyclone is stationary (< 2 km/h or 1 kt) and will not have a reported movement speed or direction + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0/volcanicAshAdvisory.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0/volcanicAshAdvisory.xsd new file mode 100644 index 0000000..a5818f1 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0/volcanicAshAdvisory.xsd @@ -0,0 +1,199 @@ + + + + + + + + + Volcanic Ash Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +Volcanic Ash Advisories report the occurrence and/or expected occurrence of specified en-route volcanic ash phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An advisory of volcanic ash conditions of significance to aviation as represented in ICAO Annex 3 / WMO No. 49-2. Volcanic ash advisories are issued by volcanic ash advisory centres (VAACs) + + + + + + + + + + The issuing VAAC + + + + + The erupting volcano that is the source of volcanic ash + + + + + Advisory number: year in full and message number (separate sequence for each volcano) + + + + + Information source - described in free text + + + + + The aviation colour code + + + + + The observed and estimated positions of volcanic ash clouds. Each analysis represents an observed or 6/12/18 hour forecast of volcanic ash. + + + + + Remarks, as necessary + + + + + The latest time at which the next advisory will be issued + + + + + The earliest time at which the next advisory will be issued + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + Conditions that indicate the presence of volcanic ash. + + + + + + + + + + Extension block for optional and/or additional parameters + + + + + + + + + + + + + + + + A volcanic ash cloud, including a horizontal and vertical extent, as well as the speed and direction of motion + + + + + + + + + The horizontal and vertical extent of the ash cloud + + + + + The direction of movement of the ash cloud. Not included on estimated/forecast conditions. Direction of movement of the ash cloud is moving to shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The speed of motion of the ash cloud. Not included on estimated/forecast conditions. Speed of movement of ash cloud shall be given in either "km/h" or "[kn_i]" (knot). + + + + + The wind speed. Only reported when volcanic ash is not identifiable from satellite data. If speed of motion of ash cloud is estimated from wind speed, unit of measure shall be given in "m/s" or "[kn_i]" (knot). + + + + + The wind direction. Only reported when volcanic ash is not identifiable from satellite data, and not reported when winds are variable. Direction of movement shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The lower limits of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The lower limit vertical reference of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The upper limits of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The lower limit vertical reference of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + Extension block for optional and/or additional parameters + + + + + + When true, indicates that the wind direction is variable. Only reported when volcanic ash is not identifiable from satellite data. + + + + + + + + + + + + + + + A CodeList representing the values for aviation colour codes specified in ICAO Annex 3 / WMO No. 49-2, such as RED, ORANGE, YELLOW, and GREEN + + http://codes.wmo.int/49-2/AviationColourCode + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/airmet.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/airmet.xsd new file mode 100644 index 0000000..f99ce6f --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/airmet.xsd @@ -0,0 +1,250 @@ + + + + + + + + AIRMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These weather phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Conditions that indicate the presence of a specific AIRMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + +Design note: +This class is no longer a subclass of MeteorologicalPosition. This change was made to ensure that there is no confusion between the two classes when results from different OM_Observation types are populated. Constraints could be used to ensure a specific superclass but not its subclasses are valid, but this would disallow the use of sub-classes of this type for other purposes such as regional extension + + + + + + + + + The expected direction of movement of a meteorological condition. When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. Direction of motion to shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The expected geographic region affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + The expected speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. Speed of movement shall be given in either "km/h" or "[kn_i]" (knot). + + + + + The cloud base of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud base shall be given in either "m" (metres) or "[ft_i]" (feet). + + + + + The reference surface used for the value of the cloud base. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + The cloud top of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud top shall be given in either "m" (metres) or "[ft_i]" (feet). + + + + + The reference surface used for the value of the cloud base. For example, Mean Sea Level, Ground, standard pressure, etc.. + + + + + The surface visibility. Only used with SFC VIS AIRMETs. Horizontal surface visibility unit of measure shall be given as "m" (metre). + +ICAO Annex 3 / WMO No. 49-2: +Appendix 6 Section 2.1 + + + + + The weather condition(s) causing reduced visibility. + + + + + The surface wind speed. Only used with SFC VIS AIRMETs. Surface wind speed unit of measure shall be given as "m/s" or "[kn_i]" (knot). + +ICAO Annex 3 / WMO No. 49-2: +Appendix 6 Section 2.1 + + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. + +This is a copy of the ExpectedIntensityChange enumeration found in IWXXM 1.0. This copy removes the need for a dependency on IWXXM. + +See WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. + + + + + Forecast to intensify (INTSF) + + + + + Forecast to weaken (WKN) + + + + + No change (NC) + + + + + + + A weather condition reducing visibility, such as dust, rain or volcanic ash. + +See ICAO Annex 3/ WMO No. 49-2 Appendix 6 Section 2.1. + + http://codes.wmo.int/bufr4/codeflag/0-20-025 + none + + + + + + + + + A AIRMET (significant meteorological) report. AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + +The AIRMET report class represents the base AIRMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. AIRMETs may report either observed or forecast hazardous conditions. + + + + + + + + + The ATS unit serving the FIR or CTA to which the AIRMET refers. ICAO Annex 3 / WMO No. 49-2: A6-1: "Location indicator of FIR/CTA" + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. Each observation/forecast phenomenon includes its own period of validity for described meteorological conditions, which is represented as the O&M Observation validTime. + + + + + The cancelled AIRMET sequence number. Mandatory when this is a cancellation report, must be missing otherwise + +Examples: +YUDD AIRMET 2 VALID ... +YUDD AIRMET A3 VALID ... + + + + + The valid period of a previous AIRMET that is cancelled by this AIRMET. Mandatory when this is a cancellation report, must be missing otherwise + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. + + + + + AIRMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own AIRMETEvolvingMeteorologicalCondition. + +Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + The horizontal surface visibility. Only used with SFC VIS AIRMETs. Horizontal surface visibility unit of measure shall be given as "m" (metre). + +ICAO Annex 3 / WMO No. 49-2: +Appendix 6 Section 2.1 + + + + + The surface wind speed. Only used with SFC WSPD AIRMETs. Surface wind speed unit of measure shall be given as "m/s" or "[kn_i]" (knot). + +ICAO Annex 3 / WMO No. 49-2: +Appendix 6 Section 2.1 + + + + + + + + + + + + + + + + + Weather phenomenon of significance to aviation operations; used in AIRMET reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 sub-clause 1.1.4 + + http://codes.wmo.int/49-2/AirWxPhenomena + none + + + + + + + + + The status of an AIRMET report (e.g., a normal issuance, a cancellation of an earlier AIRMET) + + + + + A normal AIRMET report (not a cancellation) + + + + + A cancellation of an earlier AIRMET report + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/common.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/common.xsd new file mode 100644 index 0000000..36bdc23 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/common.xsd @@ -0,0 +1,267 @@ + + + + + + + Common constructs used across multiple packages. This package includes constructs closely related to the aviation weather domain. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Forecast cloud conditions, including predicted vertical visibility and cloud layers. + +A single vertical visibility may be reported, but cannot be reported with cloud layers. + + + + + + + + + The vertical visibility. Vertical visibility is defined as the vertical visual range into an obscuring medium. + +Vertical visibility shall be reported either in meters ("m") or feet ("[ft_i]"). + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + + + + + + + + + + + + A forecast of wind conditions at an aerodrome. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. Wind speeds and gusts, if present, shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + +This extends AerodromeSurfaceWindTrendForecast to allow for a variable wind direction to be reported. This class differs from a aerodrome wind observation in that the observations may include a min/max directional variability. This class only carries a true/false indication that it will be variable. + + + + + + + + + + + + + + + + + + + + A cloud layer, including a cloud amount, cloud base and cloud type. + + + + + + + The observed cloud amount + + + + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at which the air contains a perceptible quantity of cloud particles. + +Measured cloud bases shall be reported in meters ("m") or feet ("[ft_i]"). + + http://codes.wmo.int/common/quantity-kind/heightOfBaseOfCloud + + + + + + The observed significant cloud types: cumulonimbus or towering cumulus + + + + + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. + + + + + + + The forecast average wind direction from which wind is blowing. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The forecast average wind speed. + +Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + The forecast maximum speed of a gust. + +Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + + + + + + + + + RelationalOperator defines the restricted set of operators that may be specified alongside numerical quantities in ICAO Annex 3/WMO No. 49. + +These operators are used in cases where a precise value is not measurable, not precisely known due to measurement limitations, or not reported due to reporting restrictions. + +For example, the "above" operator in conjunction with the reported quantity 10.6 indicates that the actual physical quantity is above 10.6 (at least 10.6). + + + + + The actual value is below the minimum value that can be determined by the system ("BLW", "M") + + + + + The actual value is above the maximum value that can be determined by the system ("ABV", "P") + + + + + + + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromeForecastWeather + none + + + + + + + + + + Genus of cloud of operational significance to aviation: significant convective clouds only. + +- Cumulonimbus +- Towering cumulus + +This CodeList is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 012 "Cloud type". + + http://codes.wmo.int/49-2/SigConvectiveCloudType + none + + + + + + + + + + Amount of cloud - assessed by category: + +- Sky clear (0 oktas) +- Few (1 - 2 oktas) +- Scattered (3 - 4 oktas) +- Broken (5 - 7 oktas) +- Overcast (8 oktas) + +This CodeList is specifically defined for aviation purposes, as defined in WMO No. 49-2. A superset of cloud-amount categories are defined in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 008 "Cloud distribution for aviation". + + http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + none + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/gmliwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/gmliwxxm.xsd new file mode 100644 index 0000000..88bce36 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/gmliwxxm.xsd @@ -0,0 +1,748 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AngleType,gml:SpeedType,gml:LengthType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:ReferenceType,gml:TimePeriodPropertyType,gml:AbstractGML,gml:AbstractGMLType,gml:AbstractObject,gml:NilReasonType,gml:MeasureType,gml:ScaleType,gml:TimeInstantPropertyType, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. + + + + + + + + + + gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. +The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. +Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. +Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:RelatedTimeType provides a content model for indicating the relative position of an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive. It extends the generic gml:TimePrimitivePropertyType with an XML attribute relativePosition, whose value is selected from the set of 13 temporal relationships identified by Allen (1983) + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:TimePrimitivePropertyType provides a standard content model for associations between an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive and another object. + + + + + + + + + + gml:AbstractTimePrimitive acts as the head of a substitution group for geometric and topological temporal primitives. + + + + + gml:AbstractTimeObject acts as the head of a substitution group for all temporal primitives and complexes. + + + + + The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. +Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system . +In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps. +Three XML attributes appear on gml:TimePositionType: +A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI. +For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era. +Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration. + + + + + + + + + + + + The simple type gml:TimePositionUnion is a union of XML Schema simple types which instantiate the subtypes for temporal position described in ISO 19108. + An ordinal era may be referenced via URI. A decimal value may be used to indicate the distance from the scale origin . time is used for a position that recurs daily (see ISO 19108:2002 5.4.4.2). + Finally, calendar and clock forms that support the representation of time in systems based on years, months, days, hours, minutes and seconds, in a notation following ISO 8601, are assembled by gml:CalDate + + + + + + + + + + + + + + + These values are interpreted as follows: +- "unknown" indicates that no specific value for temporal position is provided. +- "now" indicates that the specified value shall be replaced with the current temporal position whenever the value is accessed. +- "before" indicates that the actual temporal position is unknown, but it is known to be before the specified value. +- "after" indicates that the actual temporal position is unknown, but it is known to be after the specified value. +A value for indeterminatePosition may +- be used either alone, or +- qualify a specific value for temporal position. + + + + + + + + + + + gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. + + + + + + + + + + gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. + + + + + + + + + + + + + + This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. + + + + + gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. +A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. +The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. + + + + + The length of a time period. + + + + + + + + + gml:duration conforms to the ISO 8601 syntax for temporal length as implemented by the XML Schema duration type. + + + + + gml:timeInterval conforms to ISO 11404 which is based on floating point values for temporal length. +ISO 11404 syntax specifies the use of a positiveInteger together with appropriate values for radix and factor. The resolution of the time interval is to one radix ^(-factor) of the specified time unit. +The value of the unit is either selected from the units for time intervals from ISO 31-1:1992, or is another suitable unit. The encoding is defined for GML in gml:TimeUnitType. The second component of this union type provides a method for indicating time units other than the six standard units given in the enumeration. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/iwxxm.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/iwxxm.xsd new file mode 100644 index 0000000..d11c507 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/iwxxm.xsd @@ -0,0 +1,27 @@ + + + + + + + + + + + + + + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, SPECI, TAF, and other reports as defined in ICAO Annex 3, Amendment 76. IWXXM reports are essential operational meteorology products used to enable safe and efficient air travel worldwide. + +The report types in this package include METAR, SPECI, TAF, SIGMET, AIRMET, Volcanic Ash Advisory (VAA), and Tropical Cyclone Advisory (TCA). + +This package builds upon the ISO 19100 family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, the constructs in this application schema refer to a number of aviation constructs such Runway and Airspace from AIXM. The full relationship of this package with external dependencies are shown in the 'Package Dependencies' diagram. + +Not all of the reports types from Annex 3 are currently represented, this may be expanded in a future version. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + gmliwxxm.xsd + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/measures.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/measures.xsd new file mode 100644 index 0000000..7dc3faf --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/measures.xsd @@ -0,0 +1,35 @@ + + + + + Common measured quantities used across multiple packages. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + A nillable Distance quantity. Unlike the base Distance measure, references to this type may be nil and may include a nilReason + + + + + + + + + + + + + A nillable Length quantity. Unlike the base Length measure, references to this type may be nil and include a nilReason + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/metarSpeci.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/metarSpeci.xsd new file mode 100644 index 0000000..6bb6086 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/metarSpeci.xsd @@ -0,0 +1,749 @@ + + + + + + + + METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +METAR and SPECI reports include identical information but are issued for different purposes. + +METAR reports are routine observations made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. + +SPECI reports are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + A report of observed and trend forecast weather phenomenon from the surface near an aerodrome. This is a shared superclass for METAR and SPECI reports, which have identical reported information. + + + + + + + + + The observation which resulted in the current meteorological conditions at an aerodrome + + + + + The process that results in a trend forecast. When no change is expected to occur during a forecast period ("NOSIG") this is indicated by a single missing trend forecast with a nil reason of noSignificantChange + + + + + + + + + + + + + + + + + + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. + +The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. + +SPECI reports are used for dissemination beyond the aerodrome of origin (mainly intended for flight planning, VOLMET broadcasts and D-VOLMET) unless METAR are issued at half-hourly intervals. + +SPECI is issued following the resumption of the issuance of METAR, as necessary, at aerodromes that are not operational throughout 24 hours in accordance with ICAO Annex 3 Section 4.3.1. + +See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + + + + + + + + + + + + + + + A routine observation made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. + +The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. + +METARs are a routine report produced for dissemination beyond the aerodrome of origin, and are mainly intended for flight planning, VOLMET broadcasts and D-VOLMET. + +See ICAO Annex 3 / WMO No. 49-2 Table A3-2 + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions for trend forecasting at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. + +When no clouds of operational significance or no weather of operational significance is predicted, the NothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. When no clouds were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason should be used for the cloud association. + + + + + + + + + The prevailing horizontal visibility reported in a trend forecast. + +Prevailing horizontal visibility shall be reported in meters ("m"). + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions observed at an aerodrome. + +When no clouds of operational significance or no weather of operational significance is observed, the NothingOfOperationalSignificance nilReason is used for the cloud or presentWeather association. When no clouds were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason is used for the cloud association. + + + + + + + + + The observed air temperature. This is the temperature indicated by a thermometer exposed to the air in a place sheltered from direct solar radiation. + +Measured air temperature shall be given in degrees Celsius ("Cel"). + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The observed dew point temperature. This is the temperature to which a given air parcel must be cooled at constant pressure and constant water vapor content in order for saturation to occur. + +Measured dew-point temperature shall be given in degrees Celsius ("Cel"). + + http://codes.wmo.int/common/quantity-kind/dewPointTemperature + + + + + + The observed QNH altimeter setting. + +Altitude setting (also known as QNH) is defined as barometric pressure adjusted to sea level. It is a pressure setting used by pilots, air traffic control (ATC), and low frequency weather beacons to refer to the barometric setting which, when set on an aircraft's altimeter, will cause the altimeter to read altitude above mean sea level within a certain defined region. + +Measured altimeter setting shall be given in hectoPascals ("hPa"). + + http://codes.wmo.int/common/quantity-kind/altimeterSettingQnh + + + + + + + + + + + + + + + + + + + + + + + + + + + An aggregation of runway conditions typically reported together at an aerodrome, including the runway contamination, friction, and deposits. + + + + + + + The runway to which the conditions apply. The runway may be missing in cases where all runways are closed due to snow + + + + + The type of runway deposit, such as damp conditions, wet snow, or ice. + +WMO 306: +Table 0919 + + + + + Proportion of runway surface that is contaminated - usually expressed as a percentage of the total runway area. + +WMO reporting procedures require that contamination is reported in the following categories: +- less than 10%; +- between 11% and 25%; +- between 26% and 50%; and +- more than 50%. + +See WMO No. 306: +- WMO Code table 0519 +- BUFR Code table 0 20 087 + + http://codes.wmo.int/common/quantity-kind/runwayContaminationCoverage + + + + + + Depth of deposit on the surface of the runway. + +Measured depth of deposit shall be given in millimeters ("mm"). + +See WMO No. 306 WMO Code table 1079. + + http://codes.wmo.int/common/quantity-kind/depthOfRunwayDeposit + + + + + + The estimated surface friction for the affected runway. Between 0.0 and 0.9. + +When braking conditions are not reported and/or the runway is not operational estimatedSurfaceFriction will not be reported. + +WMO 306: +Table 0366 + + http://codes.wmo.int/common/quantity-kind/runwayFrictionCoefficient + + + + + + + + + + + + + + + + + + An aggregation of runway visual range conditions for a single runway, typically reported together at an aerodrome + + + + + + + The runway to which reported runway visual range information applies + + + + + The mean recent runway visual range value observed. This mean represents the 10 minute average for observed RVR except when the 10-minute period immediately preceding the observation includes a marked discontinuity in runway visual range values, only those values occurring after the discontinuity is used for obtaining mean values. + +Mean runway visual range distance shall be reported in meters ("m"). + +To report a mean RVR of at least 2000 meters, mean RVR is reported as 2000 meters and the operator is reported as "above" + +Annex 3: +Table A3-2 "RVR/RVR" +Section 4.3.6.6 + + http://codes.wmo.int/common/quantity-kind/runwayVisualRangeRvr + + + + + + The reported relational operator for the mean RVR. When reported, this operator is reported in conjunction with mean RVR. + +To report a mean RVR of at least 2000 meters, mean RVR is reported as 2000 meters and the operator is reported as "above". + +When no operator is reported, mean RVR represents an exact value with identical semantics to other measured quantities + + + + + + + + + + + + + + An aggregation of sea state conditions typically reported together at an aerodrome. This includes information on sea-surface temperature and either the state of the sea or significant wave height from aeronautical meteorological stations established on offshore structures in support of helicopter operations + + + + + + + The sea-surface temperature observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations. + +The term sea surface temperature is generally meant to be representative of the upper few meters of the ocean as opposed to the skin temperature, which is the temperature of the upper few centimeters. + +Temperatures shall be reported in degrees Celsius ("Cel"). + +ICAO Annex 3 / WMO No. 49-2: +Section 4.8.1.5a + + http://codes.wmo.int/common/quantity-kind/seaSurfaceTemperature + + + + + + The significant wave height observed. + +Significant wave height shall be reported in meters ("m"). + + + + + The state of the sea observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations + +ICAO Annex 3 / WMO No. 49-2: +Section 4.8.1.5a + +WMO 306: +Table 3700 + + + + + + + + + + + + + An aggregation of wind shear conditions typically reported together at an aerodrome, including the set of affected runways. + + + + + + + The specific runway(s) affected by wind shear at this aerodrome. No specific runways are reported when all runways are affected by wind shear + + + + + + + + + + + + + + An aggregation of observed cloud conditions typically reported together at an aerodrome, including cloud types, cloud layers, and vertical visibility. + + + + + + + The reported vertical visibility. Vertical visibility is defined as the vertical visual range into an obscuring medium. + +Measured vertical visibility shall be reported in either two units of measures: meters ("m") or feet ("[ft_i]"). + +Note: vertical visibility is only reported in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus prevailing visibility is considered to be an aviation-specific quantity. + +When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing system due to a temporary failure of the system/sensor ("VV///") the vertical visibility is missing with a nil reason of notObservable + + http://codes.wmo.int/common/quantity-kind/verticalVisibility + + + + + + + + + + + + + + + An aggregation of surface wind conditions typically reported together at an aerodrome, including wind direction information, wind speed, and wind gusts. + +Wind direction is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: +"variations from the mean wind direction during the past 10 minutes is reported as follows, if the total variation is 60 or more: +1) when the total variation is 60 or more and less than 180 and the wind speed is 1.5 m/s (3 kt) or more, such directional variations are reported as the two extreme directions between which the surface wind has varied; +2) when the total variation is 60 or more and less than 180 and the wind speed is less than 1.5 m/s (3 kt), the wind direction is reported as variable with no mean wind direction; or +3) when the total variation is 180 or more, the wind direction is reported as variable with no mean wind direction" + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. Wind speeds and gusts, if present, shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + + + + + + The observed average wind direction from which the wind is blowing over the past ten minutes. Not reported when winds are variable. + +Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The average observed wind speed over the past ten minutes + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2a + +Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/windSpeed + + + + + + The maximum wind speed observed over the past ten minutes + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2c + +Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + http://codes.wmo.int/common/quantity-kind/maximumWindGustSpeed + + + + + + The extreme clockwise direction from which the wind is blowing, inclusive. + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2b + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + The extreme counter-clockwise direction from which the wind is blowing, inclusive. + +ICAO Annex 3 / WMO No. 49-2: +Section 4.1.5.2b + + http://codes.wmo.int/common/quantity-kind/windDirection + + + + + + + + + + + + + + + An aggregation of horizontal visibility conditions typically reported together at an aerodrome, including the prevailing visibility and minimum visibility. + +Direction of minimum visibility shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". +Measured prevailing and minimum horizontal visibility, if present, shall be reported in meters ("m") only. + + + + + + + The reported prevailing horizontal visibility at the surface that is representative of the aerodrome. + +Measured prevailing horizontal visibility shall be reported in meters ("m") only. + +The greatest visibility value, observed in accordance with the definition of "visibility", which is reached within at least half the horizon circle or within at least half of the surface of the aerodrome. These areas could comprise contiguous or non-contiguous sectors. + +Note: This value may be assessed by human observation and/or instrumented systems. When instruments are installed, they are +used to obtain the best estimate of the prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the prevailing visibility operator is reported as "above". + +ICAO Annex 3 / WMO No. 49-2: +Section 4.2.4.4b + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + The minimum observed visibility. + +Measured minimum visibility shall be reported in meters ("m") only. + +ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: +"When the visibility is not the same in different directions and +a) when the lowest visibility is different from the prevailing visibility, and + 1) less than 1 500 m or + 2) less than 50 percent of the prevailing visibility and less than 5000 m; the lowest visibility observed should also be reported and,when possible, its general direction in relation to the aerodrome reference point indicated by reference to one of the +eight points of the compass. If the lowest visibility is observed in more than one direction, then the most +operationally significant direction should be reported; and +b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot be determined, only the lowest visibility +should be reported, with no indication of direction." + + http://codes.wmo.int/common/quantity-kind/aeronauticalVisibility + + + + + + The direction of the minimum visibility relative to the reporting station. This is optional in cases where minimum visibility is reported but the visibility is fluctuating rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions (N, NE, E, SE, S, SW, W, and NW) + +Direction of minimum visibility shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + http://codes.wmo.int/common/quantity-kind/aerodromeMinimumVisibilityDirection + + + + + + + + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. + +Defined in WMO No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. + +Also see WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or an aerodrome forecast'. + + + + + No significant changes are forecast (NOSIG) + + + + + When the change is forecast to commence at the beginning of the forecast period and be completed by the end of that period, or when the change is forecast to occur within the forecast period but the time of the change is uncertain (possibly shortly after the beginning of the forecast period, or midway or near the end of that period), the change is indicated by only the change indicator BECMG. + + + + + The change indicator TEMPO is used to describe expected temporary fluctuations to meteorological conditions which reach or pass specified threshold criteria and last for a period of less than one hour in each instance and in the aggregate cover less than half of the forecast period during which the fluctuations are expected to occur. + + + + + + + The tendency of visual range (e.g., upward, downward). Defined for the purposes of aviation meteorology reporting of the visual range on runways (WMO No. 49-2). + +If the [runway] visual range (RVR) values during the 10-minute period preceding the nominal observation time show a distinct upward or downward tendency such that the mean during the first five minutes varies by 100 metres or more from the mean in the second five minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency is recorded. When no distinct change in RVR is observed, NO CHANGE [N] is recorded. + +See WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visual range". + + + + + Upward (increasing) tendency + + + + + No change + + + + + Downward (decreasing) tendency + + + + + + + The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, correction of an earlier report, etc.) + + + + + Normal report status: not a correction of an earlier report + + + + + A correction of an earlier report + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + + + Weather phenomenon of operational significance to aviation observed during the period since the last routine report, or last hour, whichever is shorter, but not at the time of observation. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromeRecentWeather + none + + + + + + + + + Categorical assessment of sea surface state (or other large open body of water) based on height of waves. + +Height in metres : Category +- 0 metres : Calm (glassy) +- 0-0.1 metres : Calm (rippled) +- 0.1-0.5 metres : Smooth +- 0.5-1.25 metres : Slight +- 1.25-2.5 metres : Moderate +- 2.5-4 metres : Rough +- 4-6 metres : Very rough +- 6-9 metres : High +- 9-14 metres : Very high +- >14 metres : Phenomenal + +See WMO No. 306 Vol I.1 code table 3700 "State of the sea" and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 22 061 "State of the sea". + + http://codes.wmo.int/bufr4/codeflag/0-22-061 + none + + + + + + + + + Type of deposit on a runway. + +See WMO No. 306 Vol I.1 code table 0919 and WMO No. 306 Vol I.2 FM 94 BUFR code table 0 20 086 "Runway deposits". + + http://codes.wmo.int/bufr4/codeflag/0-20-086 + none + + + + + + + + + Extent of runway surface that is contaminated (covered) + + http://codes.wmo.int/bufr4/codeflag/0-20-087 + none + + + + + + + + + The present weather observed at, or in near vicinity of, an aerodrome. + +Only a specific set of weather phenomenon are reported within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49-2. + +This CodeList is specifically defined for aviation purposes as defined in WMO No. 49-2. A superset of definitions are defined in WMO No. 306 Vol I.1 code-table 4678 "Significant weather phenomena". + + http://codes.wmo.int/49-2/AerodromePresentWeather + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/sigmet.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/sigmet.xsd new file mode 100644 index 0000000..002cfb5 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/sigmet.xsd @@ -0,0 +1,305 @@ + + + + + + + + SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These weather phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + +In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to the sampled feature for this SIGMET. + + + + + + + + + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in Annex 3: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + + + + + + + + + + + + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + +The SIGMET report class represents the base SIGMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic ash SIGMET reports are subclasses of SIGMET due to their ability to report additional information, including volcano/tropical cyclone identification and forecast position(s). + +SIGMETs may report either observed or forecast hazardous conditions. Additionally, a forecast position may be reported. + + + + + + + + + The ATS unit serving the FIR or CTA to which the SIGMET refers + +ICAO Annex 3 / WMO No. 49-2: +A6-1: "Location indicator of FIR/CTA" + + + + + MWO originating this report + + + + + The sequence number of this message. For example: "5", "A3", or "2" + + + + + The valid period for the entire report, including all observations and forecast conditions. Each observation/forecast phenomenon includes its own period of validity for described meteorological conditions, which is represented as the O&M Observation validTime. + +For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 UTC with an observed position at 1600 UTC and a forecast position of the centre of the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis validTime would be 2200 UTC. + + + + + The cancelled SIGMET sequence number. Mandatory when this is a cancellation report, must be missing otherwise + +Examples: +YUDD SIGMET 2 VALID ... +YUDD SIGMET A3 VALID ... + + + + + The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory when this is a cancellation report, must be missing otherwise + + + + + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. + +The expected end of occurrence of volcanic ash ("NO VA EXP") is indicated with a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance + + + + + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. + +Each analysis has a single EvolvingMeteorologicalCondition as its result. + + + + + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. + +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. + +directionOfMotion element refers to the direction which the phenomenon is moving towards, .e.g, "moving to the east". directionOfMotion is given in degrees from true North. Plane angle unit of measure (uom) is "deg". + +speedOfMotion can be provided in either two units of measures: "km/h" or "kn_i" (knots). + + +Design note: +This class is no longer a subclass of MeteorologicalPosition. This change was made to ensure that there is no confusion between the two classes when results from different OM_Observation types are populated. Constraints could be used to ensure a specific superclass but not its subclasses are valid, but this would disallow the use of sub-classes of this type for other purposes such as regional extension + + + + + + + + + This element refers to the expected direction of movement which the phenomenon is moving towards, .e.g, "moving east". When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. + +This element value is given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The expected geographic region affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width + + + + + The expected speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. + +speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i]" (knots). + + + + + + + + + + + + + + + + + A SIGMET that reports the presence of a tropical cyclone conditions. This extends the base SIGMET type by including additional information necessary for tropical cyclones. + + + + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon area within an FIR. These are modeled as a single OM_Observation sub-type with a feature collection result due to the shared time and other observation metadata for all forecast positions. + + + + + The tropical cyclone being reported in this SIGMET + + + + + + + + + + + + + + + + A SIGMET that reports the presence of volcanic ash conditions hazardous to flight. This extends the base SIGMET type by including additional information necessary for volcanoes and volcanic ash. + + + + + + + + + One or more forecast positions at the end of the valid period - one for each phenomenon area within an FIR. These are modeled as a single OM_Observation sub-type with a feature collection result due to the shared time and other observation metadata for all forecast positions. + + + + + The volcano that is erupting + + + + + + + + + + + + + + + + A collection of MeteorologicalPositions, each representing a location where meteorological conditions exist. All members of this collection are of type MeteorologicalPosition. + + + + + + + + + + + + + + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. + +See WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity' + + + + + No change (NC) + + + + + Forecast to weaken (WKN) + + + + + Forecast to intensify (INTSF) + + + + + + + The status of a SIGMET report (e.g., a normal issuance, a cancellation of an earlier SIGMET) + + + + + A normal SIGMET report (not a cancellation) + + + + + A cancellation of an earlier SIGMET report + + + + + + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET reports. The set of permitted options are defined in ICAO Annex 3 / WMO No. 49-2 C.3.1 sub-clause 1.1.4 + + http://codes.wmo.int/49-2/SigWxPhenomena + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/taf.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/taf.xsd new file mode 100644 index 0000000..2f21e4f --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/taf.xsd @@ -0,0 +1,284 @@ + + + + + + + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +An Aerodrome Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome intended for distribution. TAF reports include base forecast conditions, and modifications to those conditions throughout the valid period. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An Aerodrome Forecast (TAF) report is a routine aerodrome forecast intended for distribution beyond an aerodrome. TAF reports report base forecast conditions, and modifications to those conditions throughout the valid period. + +TAF reports include similar information to a METAR/SPECI trend forecast. However, TAF forecast information includes additional detail. + +Aerodromes can issue both METAR/SPECI and TAF reports on a routine basis, but TAFs are not issued by every METAR-reporting aerodrome. + +The issuance of a new forecast by a meteorological office, such as a TAF, cancels any forecast of the same type previously issued for the same place and for the same period of validity or part thereof. + +Prevailing conditions and forecast changes differ in that the prevailing conditions can include temperatures, base conditions do not include a change indicator, and that forecast changes may report no significant weather (NSW). Rather than have two class hierarchies, constraints are present ensuring that each (base and forecast conditions) only include relevant information + + + + + + + + + The time at which this report was issued. Note that this should be identical to the resultTime of each MeteorologicalAerodromeForecast, whose results are made available at the same time as this report. TAF reports have an issueTime to assist in discovery and to provide unambiguous semantics at the report level. + + + + + The time frame at which this report is valid. All forecast elements should be valid within this period + + + + + The prevailing conditions. Mandatory in all cases except missing or cancelled reports + + + + + Forecast that modifies the base forecast. While there is no maximum number of forecasts, this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO No. 49-2: Section 1.5: "The number of change and probability groups should be kept to a minimum and should not normally exceed five groups". + + + + + The aerodrome of the previously-issued report being amended or cancelled + + + + + The valid time period for the previously amended and/or cancelled report + + + + + + + + + + + + + + + + + A specialized Record type containing meteorological conditions forecast at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. + +When no clouds of operational significance or no weather of operational significance is predicted, the nothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. + +Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): + FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) + TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL) + FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity) + AT - a phenomenonTime with a TimeInstant + + + + + + + + + The prevailing horizontal visibility, mandatory except when ceiling and visibility is reported as OK + +Prevailing horizontal visibility shall be reported in meters ("m"). + + http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility + + + + + + The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. + +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". + +When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities + + + + + + + + + + + + + + + + + + + + + + An aggregation of air temperature forecast conditions typically reported together at an aerodrome, including the minimum and maximum anticipated air temperatures and when they occur. + +AerodromeAirTemperatureForecast is only reported on base conditions on a TAF, not change forecasts. + + + + + + + The maximum air temperature expressed in degrees Celsius ("Cel") + +ICAO Annex 3 / WMO No. 49-2: +"TX" + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the maximum air temperature. This must be within the period of the phenomenon time for this forecast record + +ICAO Annex 3 / WMO No. 49-2: +"TX" + + + + + The minimum air temperature expressed in degrees Celsius ("Cel") + +ICAO Annex 3 / WMO No. 49-2: +"TN" + + http://codes.wmo.int/common/quantity-kind/airTemperature + + + + + + The time of occurrence of the minimum air temperature. This must be within the period of the phenomenon time for this forecast record + +ICAO Annex 3 / WMO No. 49-2: +"TN" + + + + + + + + + + + + + The forecast change indicator type, including temporary, permanent, or probable conditions. This is an extension of ForecastChangeIndicator that includes report-specific entries, and in particular the 30 and 40% probability conditions. + +Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): + FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) + TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL) + FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity) + AT - a phenomenonTime with a TimeInstant + +Design note: +These values represent the operationally-representable types, but are not very general-purpose. Especially with temporary conditions and probability it might be better to turn these into a "probability" property and constraints could be applied to the value to match operational constraints + + + + + Conditions are expected to reach or pass through specified threshold values at a regular or irregular rate and at an unspecified time during the time period. The time period should normally not exceed 2 hours but in any case should not exceed 4 hours. + +ICAO Annex 3 / WMO No. 49-2: +"BECMG" + + + + + Expected temporary fluctuations to meteorological conditions which reach or pass specified threshold criteria and last for a period of less than one hour in each instance and in the aggregate cover less than half of the forecast period during which the fluctuations are expected to occur. + +ICAO Annex 3 / WMO No. 49-2: +"TEMPO" + + + + + One set of prevailing weather conditions is expected to change significantly and more or less completely to a different set of conditions. Conditions in a FROM group supersede conditions in earlier groups. + +ICAO Annex 3 / WMO No. 49-2: +"FM" + + + + + A 30% probability of occurrence of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB30" + + + + + A 30% probability of occurrence of temporary conditions of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB30 TEMPO" + + + + + A 40% probability of occurrence of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB40" + + + + + A 40% probability of occurrence of temporary conditions of an alternative value of a forecast element or elements. + +ICAO Annex 3 / WMO No. 49-2: +"PROB40 TEMPO" + + + + + + + The report status for a TAF report (e.g., a normal issuance, an amendment of an earlier report, a cancellation of an earlier report) + + + + + An normal issuance of a TAF + + + + + An amendment of an earlier TAF + + + + + A cancellation of an earlier TAF + + + + + A correction of an earlier TAF + + + + + The report is missing ("NIL" from ICAO Annex 3 / WMO No. 49) + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/tropicalCycloneAdvisory.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/tropicalCycloneAdvisory.xsd new file mode 100644 index 0000000..3ae36ae --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/tropicalCycloneAdvisory.xsd @@ -0,0 +1,167 @@ + + + + + + + Tropical Cyclone Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +Tropical Cyclone Advisories (TCA) report the occurrence and/or expected occurrence of tropical cyclone phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An advisory of tropical cyclone conditions of significance to aviation as represented in ICAO Annex 3 / WMO No. 49-2. Tropical cyclone advisories are issued by tropical cyclone advisory centres (TCACs) + + + + + + + + + The time at which this advisory was issued + + + + + The issuing TCAC + + + + + The tropical cyclone name + + + + + Advisory number, starting with 1 for each cyclone + + + + + The observed conditions of the tropical cyclone + + + + + The forecast conditions of the tropical cyclone, one each for the 6 hour, 12 hour, 18 hour, and 24 hour forecast periods + + + + + Remarks, as necessary + + + + + The time at which the next advisory is expected to be issued. + +When no subsequent advisory is expected to be issued it should be indicated by a missing expected advisory time with a nil reason of 'inapplicable' + + + + + + + + + + + + + + + + Forecast conditions of a tropical cyclone + + + + + + + + + The forecast maximum surface wind speed. Maximum wind speeds shall be provided in either two units of measures: "m/s"or "[kn_i]" (knot). + + + + + + + + + + + + + + + + The movement type for a tropical cyclone, either MOVING, MOVING_SLOWLY, or STATIONARY + + + + + The tropical cyclone is stationary (< 2 km/h or 1 kt) and will not have a reported movement speed or direction + + + + + The tropical cyclone is moving slowly (< 6 km/h or 3 kt) and will not have a reported movement speed or direction + + + + + The tropical cyclone is moving and will be reported with the associated movement speed and direction + + + + + + + Observed conditions of a tropical cyclone + + + + + + + + + The movement observed for the tropical cyclone + + + + + The movement direction observed. Only reported when the tropical cyclone is moving at least 6 km/hour or 3 knots. Direction of movement shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The movement speed observed. Only reported when the tropical cyclone is moving at least 6 km/hour or 3 knots. Speed of movement shall be provided in either two units of measures: "km/h" or "[kn_i]" (knot). + + + + + The central pressure of the tropical cyclone. Central pressure of cyclone shall be provided in hectoPascals (hPa). + + + + + The mean maximum surface wind near the cyclone centre over 10 minutes. Mean maximum wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/iwxxm/2.0RC1/volcanicAshAdvisory.xsd b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/volcanicAshAdvisory.xsd new file mode 100644 index 0000000..7a31d25 --- /dev/null +++ b/config/schemas/schema/int/wmo/iwxxm/2.0RC1/volcanicAshAdvisory.xsd @@ -0,0 +1,184 @@ + + + + + + + + + Volcanic Ash Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +Volcanic Ash Advisories report the occurrence and/or expected occurrence of specified en-route volcanic ash phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These phenomena are reported as impacted regions of airspace. + +References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An advisory of volcanic ash conditions of significance to aviation as represented in ICAO Annex 3 / WMO No. 49-2. Volcanic ash advisories are issued by volcanic ash advisory centres (VAACs) + + + + + + + + + + The issuing VAAC + + + + + The erupting volcano that is the source of volcanic ash + + + + + Advisory number: year in full and message number (separate sequence for each volcano) + + + + + Information source - described in free text + + + + + The aviation colour code + + + + + The observed and estimated positions of volcanic ash clouds. Each analysis represents an observed or 6/12/18 hour forecast of volcanic ash. + + + + + Remarks, as necessary + + + + + The latest time at which the next advisory will be issued + + + + + The earliest time at which the next advisory will be issued + + + + + + + + + + + + + + + + A CodeList representing the values for aviation colour codes specified in ICAO Annex 3 / WMO No. 49-2, such as RED, ORANGE, YELLOW, and GREEN + + http://codes.wmo.int/49-2/AviationColourCode + none + + + + + + + + + A volcanic ash cloud, including a horizontal and vertical extent, as well as the speed and direction of motion + + + + + + + + + The horizontal and vertical extent of the ash cloud + + + + + The direction of movement of the ash cloud. Not included on estimated/forecast conditions. Direction of movement of the ash cloud is moving to shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + The speed of motion of the ash cloud. Not included on estimated/forecast conditions. Speed of movement of ash cloud shall be given in either "km/h" or "[kn_i]" (knot). + + + + + The wind speed. Only reported when volcanic ash is not identifiable from satellite data. If speed of motion of ash cloud is estimated from wind speed, unit of measure shall be given in "m/s" or "[kn_i]" (knot). + + + + + The wind direction. Only reported when volcanic ash is not identifiable from satellite data, and not reported when winds are variable. Direction of movement shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + + + + When true, indicates that the wind direction is variable. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The lower limits of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The lower limit vertical reference of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The upper limits of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + The lower limit vertical reference of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. + + + + + + + + + + + + + + + + Conditions that indicate the presence of volcanic ash. + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/aeronauticalMeteorology.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/aeronauticalMeteorology.xsd new file mode 100644 index 0000000..a9d13dc --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/aeronauticalMeteorology.xsd @@ -0,0 +1,18 @@ + + + + In accordance with the working arrangements between WMO and ICAO, WMO governs and + maintains the set of definitions and codes associated with routine exchange of meteorological + information to support aviation operations. This 'Aviation Meteorology' package defines + physical properties and «CodeList» classes pertaining to the joint ICAO Annex 3 / + WMO No. 49 Regulation - hence their inclusion in WMO METCE. Often the entities defined + herein are specialisations of generic meteorological entities. [<font color="#ff0000"><i>Note + the inconsistent use of "aviation" vs. "aeronautical"; please indicate preference</i></font>] + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloud.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloud.xsd new file mode 100644 index 0000000..9dd7501 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloud.xsd @@ -0,0 +1,77 @@ + + + + + + + For a given cloud or cloud layer, height of the lowest level in the atmosphere at + which the air contains a perceptible quantity of cloud particles. In FM-92 GRIB, + encoded as GRIB Code-table 4.2 discipline 0 (meteorology), category 6 (cloud), #11 + cloud base. + + + + + + + + + + + Quantitative amount of cloud; measured in % or oktas. <font color="#ff0000"> </font><font + color="#ff0000">WARNING: the terminology "Cloud amount" (GRIB 4.2 0.6.7) and "Cloud + cover" (GRIB 4.2 0.6.22) is ambiguous. The WMO terminology specifies "Cloud cover" + as a synonym for "Cloud amount"! The terminology needs to be clarified.</font> <font + color="#ff0000"> </font><font color="#ff0000">... definition "Cloud cover" (ECMWF): + "horizontal fraction of the grid box covered by cloud"</font> <font color="#ff0000">... + definition "Cloud amount (ECMWF): "eigths of sky covered in cloud as seen by an observer + on the ground"</font> In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline 0 + (meteorology), category 6 (cloud), #7 cloud amount (%) or #22 cloud cover (%) . + + + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-012 + any + + Genus of cloud. In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline 0 (meteorology), + category 6 (cloud), #8 cloud type. See WMO No. 306: - GRIB Code table 4.203; - BUFR + Code table 0 20 012 "Cloud type"; - WMO Code table 0500 "Genus of cloud"; - WMO Code + table 0509 "Clouds of the genera cirrus, cirrocumulus and cirrostratus"; - WMO Code + table 0513 "Clouds of the genera stratocumulus, stratus, cumulus and cumulonimbus"; + - WMO Code table 0515 "Clouds of the genera altocumulus, altostratus and nimbostratus"; + and - WMO Code table 0521 "Special clouds" + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-011 + any + + Amount of cloud - assessed by category: - 0 oktas - 1 oktas or less (but not zero) + - 2 oktas - 3 oktas - 4 oktas - 5 oktas - 6 oktas - 7 oktas or more (but not 8) - + 8 oktas - Sky obscured by fog and/or other meteorological phenomena - Sky partially + obscured by fog and/or other meteorological phenomena - Sky clear (0 oktas) - Few + (1 - 2 oktas) - Scattered (3 - 4 oktas) - Broken (5 - 7 oktas) - Overcast (8 oktas) + - Cloud cover is indiscernible for reasons other than fog or other meteorological + phenomena, or observation is not made See WMO No. 306 BUFR Table B class 20 'Observed + phenomena' #11 [Element 0 20 011]. + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloudAeronautical.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloudAeronautical.xsd new file mode 100644 index 0000000..ddd3be1 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/cloudAeronautical.xsd @@ -0,0 +1,41 @@ + + + + + + + + http://data.wmo.int/def/49-2/SigConvectiveCloudType + none + + Genus of cloud of operational significance to aviation: significant convective clouds + only. - Cumulonimbus - Towering cumulus This &lt;CodeList&gt; is specifically defined + for aviation purposes therefore it is provisioned within the vocabulary associated + with WMO No. 49 (e.g. http://data.wmo.int/def/49). Note that the definitions are a + subset from BUFR code-table 0 20 012. See WMO No. 306 BUFR Code table 0 20 012 "Cloud + type" + + + + + + + + + + http://data.wmo.int/def/49-2/CloudAmountReportedAtAerodrome + none + + Amount of cloud - assessed by category: - Sky clear (0 oktas) - Few (1 - 2 oktas) + - Scattered (3 - 4 oktas) - Broken (5 - 7 oktas) - Overcast (8 oktas) This &lt;CodeList&gt; + is specifically defined for aviation purposes therefore it is provisioned within the + vocabulary associated with WMO No. 49 (e.g. http://data.wmo.int/def/49). However, + note that the definitions are a subset from BUFR code-table 0 20 008. See WMO No. + 306 BUFR Code table 0 20 008 "Cloud distribution for aviation" + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/mass.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/mass.xsd new file mode 100644 index 0000000..62f7c20 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/mass.xsd @@ -0,0 +1,63 @@ + + + + + + + The atmospheric pressure at mean sea level, either directly measured or, most commonly, + empirically determined from the observed station pressure. In FM-92 GRIB, encoded + as GRIB Code-table 4.2 discipline 0 (meteorology), category 3 (mass), #1 pressure + reduced to MSL. + + + + + + + + + + + The rate of change in atmospheric pressure. In FM-92 GRIB, encoded as GRIB Code-table + 4.2 discipline 0 (meteorology), category 3 (mass), #2 pressure tendency. + + + + + + + + + + + Altitude setting (also known as QNH) is defined as barometric pressure adjusted to + sea level. It is a pressure setting used by pilots, air traffic control (ATC), and + low frequency weather beacons to refer to the barometric setting which, when set on + an aircraft's altimeter, will cause the altimeter to read altitude above mean sea + level within a certain defined region. In FM-92 GRIB, encoded as GRIB Code-table + 4.2 discipline 0 (meteorology), category 3 (mass), #11 altimeter setting. <i>Note: + whilst QNH is an aviation term, it appears in the GRIB parameter scheme within this + category - hence its inclusion here.</i> + + + + + + + + + + + (Also known as geometric altitude) Vertical distance (Z) of a level, a point or an + object considered as a point, measured from mean sea level. In FM-92 GRIB, encoded + as GRIB Code-table 4.2 discipline 0 (meteorology), category 3 (mass), #6 geometric + height. + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorologicalBasicTypes.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorologicalBasicTypes.xsd new file mode 100644 index 0000000..aa23c59 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorologicalBasicTypes.xsd @@ -0,0 +1,22 @@ + + + + Package 'Meteorological basic types' contains: - a palette of quantity value [1] classes + specialising Measure (or subclasses thereof) for meteorological, hydrological and + oceanographic physical properties; - a palette of «CodeList» classes for expressing + nominal values of meteorological, hydrological and oceanographic physical properties; + and - various other common basic types used in describing meteorological phenomena. + As GML is currently specified, Measure (from ISO 19103 Basic types) _CANNOT_ be specialised. + Therefore, the definition of quantity-value classes such as ThermodynamicTemperature + and AirTemperature as specialisations of Measure is _ILLEGAL_ with respect to GML. + For this reason 'Meteorological basic types' is published as a separate package outside + the scope of METCE. As a complement to "ISO 19103 Basic types", "Meteorological basic + types" will provide a set of classes and XML types required to describe the physical + quantities of interest to meteorologists. [1] Quantity Value: number and reference + together expressing magnitude of a Quantity (from the 'International vocabulary of + metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorology.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorology.xsd new file mode 100644 index 0000000..65fbaae --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/meteorology.xsd @@ -0,0 +1,17 @@ + + + + [<font color="#ff0000">Currently only a restricted set of categories are provided + in order to support the ICAO OPMET requirement</font>] + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/moisture.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/moisture.xsd new file mode 100644 index 0000000..c5b9577 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/moisture.xsd @@ -0,0 +1,57 @@ + + + + + + + Rate of total precipitation. In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline + 0 (meteorology), category 1 (moisture), #52 total precipitation rate. + + + + + + + + + + + Total amount of precipitation measured over a defined period. In FM-92 GRIB, encoded + as GRIB Code-table 4.2 discipline 0 (meteorology), category 1 (moisture), #8 total + precipitation. Whilst this parameter is currently marked as 'deprecated', this quantity + is expected to be reinstated into GRIB in the next release as the use of 'accumulations' + of 'total-precipitation-rate' over a period to determine the total precipitation was + overly complex! Also see BUFR Table-B element 0 13 011 'Total precipitation'. + + + + + + + + + + + In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline 0 (meteorology), category + 1 (moisture), #60 snow depth water equivalent. + + + + + + + + + + + In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline 0 (meteorology), category + 1 (moisture), #11 snow depth. + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/momentum.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/momentum.xsd new file mode 100644 index 0000000..0b6dc9d --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/momentum.xsd @@ -0,0 +1,58 @@ + + + + + + + Maximum speed of a gust during a given period. In FM-92 GRIB, encoded as GRIB Code-table + 4.2 discipline 0 (meteorology), category 2 (momentum), #22 wind speed (gust). + + + + + + + + + + + Ratio of the distance covered by the air to the time taken to cover it. The instantaneous + speed corresponds to the case of an infinitely small time interval. The mean speed + corresponds to the case of a finite time interval. It is one component of wind velocity, + the other being wind direction). In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline + 0 (meteorology), category 2 (momentum), #1 wind speed. + + + + + + + + + + + Direction from which wind is blowing. In FM-92 GRIB, encoded as GRIB Code-table 4.2 + discipline 0 (meteorology), category 2 (momentum), #0 wind direction. <font color="#ff0000"> + </font><font color="#ff0000">Note that BUFR Table B provides additional descriptors + with further refined semantics:</font> <font color="#ff0000">- 0 11 016 : Extreme + counter clockwise direction of a variable wind; and</font> <font color="#ff0000">- + 0 11 017 : Extreme clockwise direction of a variable wind.</font> <font color="#ff0000"> + </font><font color="#ff0000">There seems little or no value in defining UML classes + that match this detailed level of semantic specification. In usage, the class WindDirection + will be qualified by the semantics of an attribute or association role. The model + documentation should express the associated refined semantics. Other scenarios where + a Measure class may be qualified include _MINIMUM_ visibility, _MINIMUM ONE MINUTE + MEAN_ RVR etc. Again, in these situations the semantics of the base class can be cleanly + expressed using model documentation.</font> <font color="#ff0000"> </font><font color="#ff0000">In + contrast, prevailing visibility has complex semantics when compared to the base visibility + definition. Here, there is value in ensuring consistent semantics are expressed by + defining a specialised class for PrevailingVisibility.</font> + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/oceanography.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/oceanography.xsd new file mode 100644 index 0000000..e9603c5 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/oceanography.xsd @@ -0,0 +1,6 @@ + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericProperties.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericProperties.xsd new file mode 100644 index 0000000..77bd9ec --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericProperties.xsd @@ -0,0 +1,99 @@ + + + + [<font color="#ff0000">Weather phenomenon not present in GRIB Code-table 4.2 (category + 19: Physical atmospheric properties) - but included here</font>] [<font color="#ff0000">Maximum + diameter of hailstones not present in GRIB Code-table 4.2 (category 19: Physical atmospheric + properties) - but included here. This property is defined in BUFR Table B class 20 + 'Observed phenomena' #66 (Element 0 20 066)</font>] + + + + + + + Maximum diameter (size) of hailstone (observed). See WMO No. 306 BUFR Table B class + 20 'Observed phenomena' #66 [Element 0 20 066] + + + + + + + + + + + The greatest distance that prominent objects can be seen and identified by unaided, + normal eyes. Unless otherwise stated, visibility is determined in the horizontal + plane at the ground surface. In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline + 0 (meteorology), category 19 (physical atmospheric properties), #0 visibility. <i>Note: + WMO Regulation for synoptic observations (Code form FM-12 SYNOP) assert that When + the horizontal visibility is not the same in different directions, the shortest distance + shall be given. However, national reporting practices vary.</i> + + + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-023 + any + + Additional weather phenomena not described in RecentWeather or PresentWeather. See + WMO No. 306 BUFR Code-table 0 20 023 + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-025 + any + + Any collection of particles, aloft or in contact with the earth's surface, dense enough + to be discernible to the observer. See WMO No. 306 BUFR Code table 0 20 025 + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-004 + any + + Weather phenomenon observed during the period since the last routine report, or last + hour, whichever is shorter, but not at the time of observation. See WMO No. 306 BUFR + Code-tables 0 20 004 and 005 + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-003 + any + + Weather phenomena observed or forecast to occur. See WMO No. 306 BUFR Code-table + 0 20 003 + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericPropertiesAeronautical.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericPropertiesAeronautical.xsd new file mode 100644 index 0000000..51004e9 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalAtmosphericPropertiesAeronautical.xsd @@ -0,0 +1,169 @@ + + + + + + + Vertical visibility is defined as the vertical visual range into an obscuring medium. + <i>Note: vertical visibility is only reported in aviation-specific WMO Code-forms + (FM-15 METAR, FM-16 SPECI and FM-51 TAF) thus we consider prevailing visibility to + be aviation-specific quantity.</i> + + + + + + + + + + + The greatest visibility value observed which is reached within at least half the horizon + circle or within at least half of the surface of the aerodrome. These areas could + comprise contiguous or non-contiguous sectors. <i>Note: prevailing visibility is + only reported in aviation-specific WMO Code-forms (FM-15 METAR, FM-16 SPECI and FM-51 + TAF) thus we consider prevailing visibility to be aviation-specific quantity.</i> + + + + + + + + + + + (Abbreviated RVR) The range [distance] over which the pilot of an aircraft on the + center line of a runway can see the runway surface markings or the lights delineating + the runway or identifying its center line. + + + + + + + + + + + Visibility for aeronautical purposes; the greater of: (a) The greatest distance at + which a black object of suitable dimensions, situated near the ground, can be seen + and recognised when observed against a bright background; (b) The greatest distance + at which lights in the vicinity of 1000 candelas can be seen and identified against + an unlit background. Note that visibility for aeronautical purposes is a more rigorously + defined than general visibility. + + + + + + + + + + + If the runway visual range values during the 10-minute period preceding the nominal + observation time show a distinct upward or downward tendency such that the mean during + the first five minutes varies by 100 metres or more from the mean in the second five + minutes of the period, an UPWARD [U] or DOWNWARD [D] tendency shall be recorded. When + no distinct change in RVR is observed, NO CHANGE [N] shall be recorded. + + + + + + Upward (increasing) tendency + + + + + No change + + + + + Downward (decreasing) tendency + + + + + + + + http://data.wmo.int/def/49-2/AerodromeForecastWeather + none + + AerodromeForecastWeather enables the forecast weather at an aerodrome to be reported. + Only a specific set of weather phenomenon are reported within aviation meteorology + as defined in Regulation ICAO Annex 3 / WMO No. 49. This &lt;CodeList&gt; is specifically + defined for aviation purposes therefore it is provisioned within the vocabulary associated + with WMO No. 49 (e.g. http://data.wmo.int/def/49). However, the definitions are a + subset from WMO code-table 4678. See WMO No. 306 Vol I.1 Code table 4678 "Significant + weather phenomena". Note: WMO BUFR code-table 0 20 003 'present weather' _MAY_ provide + a complete enumeration of the options from code-table 4678. + + + + + + + + + + http://data.wmo.int/def/49-2/AerodromeRecentWeather + none + + Weather phenomenon of operational significance to aviation observed during the period + since the last routine report, or last hour, whichever is shorter, but not at the + time of observation. Only a specific set of weather phenomenon are reported within + aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49. This &lt;CodeList&gt; + is specifically defined for aviation purposes therefore it is provisioned within the + vocabulary associated with WMO No. 49 (e.g. http://data.wmo.int/def/49). However, + the definitions are a subset from WMO code-table 4678. See WMO No. 306 Vol I.1 Code + table 4678 "Significant weather phenomena". Note: WMO BUFR code-table 0 20 004/005 + 'past weather' _MAY_ provide a complete enumeration of the options from code-table + 4678. + + + + + + + + + + http://data.wmo.int/def/306/4678 + any + + Categorisation of local significant atmospheric activity; weather type. See WMO No. + 306 WMO Code table 4678 "Significant present and forecast weather". Note: WMO BUFR + code-table 0 20 003 'present weather' _MAY_ provide a complete enumeration of the + options from code-table 4678. + + + + + + + + + + http://data.wmo.int/def/49-2/AerodromePresentWeather + none + + AerodromePresentWeather enables the present weather observed at, or in near vicinity + of, an aerodrome to be reported. Only a specific set of weather phenomenon are reported + within aviation meteorology as defined in Regulation ICAO Annex 3 / WMO No. 49. This + &lt;CodeList&gt; is specifically defined for aviation purposes therefore it is provisioned + within the vocabulary associated with WMO No. 49 (e.g. http://data.wmo.int/def/49). + However, the definitions are a subset from WMO code-table 4678. See WMO No. 306 Vol + I.1 Code table 4678 "Significant weather phenomena". Note: WMO BUFR code-table 0 + 20 003 'present weather' _MAY_ provide a complete enumeration of the options from + code-table 4678. + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalProperties.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalProperties.xsd new file mode 100644 index 0000000..de2d711 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/physicalProperties.xsd @@ -0,0 +1,106 @@ + + + + The package 'Physical properties' contains: - a palette of quantity value [1] classes + specialising Measure (from ISO 19103), or subclasses thereof, for sensible, well-defined, + standard meteorological, hydrological and oceanographic physical properties - usually + derived from BUFR or GRIB definitions; and - a palette of «CodeList» classes for expressing + nominal values of meteorological, hydrological and oceanographic physical properties. + These classes describing meteorological, hydrologic and oceanographic quantity values + and nominal property values, governed by WMO, can be imported into Application Schema + ensuring consistent application of semantics. All 'quantity value' classes are defined + as specialisations of Measure (from ISO 19103 Basic types) or sub-classes thereof + (e.g. Visibility is a specialisation of Distance (from ISO 19103 Basic types), which + is itself a specialisation of Measure). An instance of a 'quantity value' class provides + both the value of the quantity (e.g. "15.2") and the unit of measure that that value + is specified in (e.g. "degrees Celsius"). Each 'quantity value' class asserts semantics + associated with a specific physical quantity enabling one to determine the physical + quantity that the value describes (e.g. AirTemperature/value = "15.2" is a value of + air temperature). It is crucial that Measure (from ISO 19103) is the root class for + quantity value classes because it is consistently used throughout the ISO 19100 series + of International Standards to express the numeric value of a property obtained through + measurement or assertion (for example, see ISO 19156 OM_Measurement). Each quantity + value class is associated with a physical property defined (or referenced) in the + WMO Table Driven Code Forms (e.g. BUFR or GRIB). This association is currently specified + as a note (e.g. AirTemperature has the following annotation: "The temperature indicated + by a thermometer exposed to the air in a place sheltered from direct solar radiation. + In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline 0 (meteorology), category + 0 (temperature), #0 temperature." The UML tag [tagged-value] "quantityName" is intended + to support automated mapping from the UML model to the WMO Table Driven Code Forms + (TDCF); each 'quantity value' class shall use the "quantityName" tagged-value to refer + to a canonical identifier for the physical quantity (e.g. AirTemperature is defined + as: "quantityName" = "http://data.wmo.int/def/grib2/codeflag/4.2/0.0.0"). The URI + for the "quantityName" is intended to be short whilst retaining human readability. + All 'quantities' will now be identified with URI of the form: [http://data.wmo.int/def/quantities/{quantity}]. + Note that all {quantity} names must be unique; these are anticipated to be derived + from the 'shortnames' defined by IPET-DRC for BUFR elements. Registers for meteorological, + aeronautical-meteorology and oceanography will be created with identifiers as follows: + - meteorological properties: [http://data.wmo.int/def/common/quantities/meteorology]; + - aeronautical meteorological properties: [http://data.wmo.int/def/common/quantities/aeronautical-meteorology]; + and - oceanographical properties: [http://data.wmo.int/def/common/quantities/oceanography]. + These 'quantity value' classes are intended to be used as Types for attributes in + Application Schema that build on the WMO METCE foundation (e.g. the MeteorologicalAerodromeObservationRecord + (from ICAO MetCC) defines an attribute 'airTemperature' of type 'AirTemperature'). + Note that where a physical property is required for an Application Schema that is + _NOT_ listed in here (e.g. feels-like temperature [2]), one can submit a request to + WMO to have this added to the model. In the interim (or for the longer term if there + need to establish a standard definition for the property) use a generic measure type + from ISO 19103 or meteorological measure type from MetBasic (e.g. ThermodynamicTemperature) + and apply the semantics to the attribute (e.g. 'feelsLikeTemperature' of type 'ThermodynamicTemperature' + from MetBasic). Also note that in order to limit the number of 'quantity value' classes + to a manageable collection, qualifying semantics like maximum, minumum, mean etc. + are expected to be provided from the attribute in the Application Schema subscribing + to a given 'quantity value' type (e.g. attribute 'maxAirTemperature' of type 'met-basic:AirTemperature' + may be defined in an Application Schema wherein the modeler should ensure they include + documentation that describes that attribute as a 'maximum'. Further qualification + of the attribute may be provided using the Observable Property Model if necessary. + <font color="#0f0f0f">Finally, it is also worth noting that if deemed necessary one + may include additional constraints against a the attribute within an Application Schema + that specifies the acceptable set of units of measure for that may be used to specify + the quantity-value within their domain of application. This may be implemented as + schematron.</font> «CodeList» classes will reference the controlled vocabulary that + provides the set of permissible values [tagged value "vocabulary"] and specify the + level of governance applied to validation of the use of terms for that «CodeList» + class [tagged value "extensibility"]. - Tagged value "vocabulary" is used to refer + to the authoritative list of terms using an HTTP URI. This authoritative list may + be implemented as a GML dictionary, SKOS concept scheme etc.; and - Tagged value "extensibility" + indicates the governance regime applied to evaluation of terms used as values of the + &lt;CodeList&gt; class; "none", "narrower" or "any". Basically, "none" implies _ONLY_ + terms from the specified code list are permitted, "narrower" implies you can use terms + with more refined definitions (e.g. narrower semantics), and "any" implies that anything + goes and the specified code list is simply a recommendation! The physical properties + are organised according to the scheme used in WMO FM-92 (GRIB): discipline | category + | parameter. Whilst this scheme is product centric, it provides a well-known categorisation + for physical properties within the meteorological community. In support of the ICAO + aviation requirement, 'Meteorological basic types' includes an additional 'Aviation' + discipline that does not occur in GRIB Code-table 0.0 "Discipline". <font color="#0000ff">Note: + should these quantity value and «CodeList» classes need to be reorganised in future, + this should not affect Application Schema that have imported these classes as the + class GUIDs will be unaffected.</font> <font color="#0000ff">Note: missing value + codes identified thus far ... {incomplete}</font> <font color="#0000ff">i) Cloud cover:</font> + <font color="#0000ff">- sky obscured by fog and/or other meteorological phenomena</font> + <font color="#0000ff">- cloud cover is indiscernible for reasons other than fog or + other meteorological phenomena, or observation is not made</font> <font color="#0000ff">ii) + Cloud type:</font> <font color="#0000ff">- cloud not visible owing to darkness, fog, + duststorm, sandstorm, or other analogous phenomena</font> <font color="#0000ff">iii) + runway deposit</font> <font color="#0000ff">- not reported (e.g. due to runway clearance + in progress)</font> <font color="#0000ff">iv) depth of runway deposit</font> <font + color="#0000ff">- runway or runways non-operational due to snow, slush, ice, large + drifts or runway clearance, but depth not reported</font> <font color="#0000ff">- + depth of deposit operationally not significant or not measurable</font> <font color="#0000ff">v) + friction coefficient / braking action</font> <font color="#0000ff">- braking conditions + not reported and/or runway not operational</font> [1] Quantity Value: number and + reference together expressing magnitude of a Quantity (from the 'International vocabulary + of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] 'Feels-like temperature' is used by the Met Office (UK) and takes into account + wind speed to give a more representative indication of how the temperature will feel. + For example if the temperature is 0 °C it will feel much colder with a wind speed + of 25 than with a wind speed of 10. [source: http://www.metoffice.gov.uk/guide/weather/symbols] + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/runwaySurfaceProperties.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/runwaySurfaceProperties.xsd new file mode 100644 index 0000000..34df940 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/runwaySurfaceProperties.xsd @@ -0,0 +1,89 @@ + + + + + + + Quantitative assessment of friction coefficient of runway surface. See WMO No. 306: + - WMO Code table 0366 "Friction coefficient / braking action"; and - BUFR Code table + 0 20 089 "Runway friction coefficient". + + + + + + + + + + + Proportion of runway surface that is contaminated - usually expressed as a percentage + of the total runway area. WMO reporting procedures require that contamination is + reported in the following categories: - less than 10%; - between 11% and 25%; - between + 26% and 50%; and - more than 50%. See WMO No. 306: - WMO Code table 0519 - BUFR + Code table 0 20 087 + + + + + + + + + + + Depth of deposit on surface of runway. See WMO No. 306 WMO Code table 1079. + + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-087 + none + + Proportion of runway surface that is contaminated expressed as a category based on + the percentage of the total runway area. WMO reporting procedures require that contamination + is reported in the following categories: - less than 10%; - between 11% and 25%; - + between 26% and 50%; and - more than 50%. See WMO No. 306: - WMO Code table 0519 + - BUFR Code table 0 20 087 + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-20-086 + none + + Type of deposit on runway. See WMO No. 306: - WMO Code table 0919; and - BUFR Code + table 0 20 086 + + + + + + + + + + http://data.wmo.int/def/49-2/BrakingAction + none + + Category of braking action associated with runway surface. See WMO No. 306: - WMO + Code table 0366 "Friction coefficient / braking action"; and - BUFR Code table 0 + 20 089 "Runway friction coefficient". + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/shortWaveRadiation.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/shortWaveRadiation.xsd new file mode 100644 index 0000000..d74344b --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/shortWaveRadiation.xsd @@ -0,0 +1,20 @@ + + + + + + + Global Solar UVI is formulated using the International Commission on Illumination + (CIE) reference action spectrum for UV-induced erythema on the human skin (ISO 17166:1999/CIE + S 007/E-1998). It is a measure of the UV radiation that is relevant to and defined + for a horizontal surface. In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline + 0 (meteorology), category 4 (short wave radiation), #51 UV index. + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/surfaceProperties.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/surfaceProperties.xsd new file mode 100644 index 0000000..215875a --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/surfaceProperties.xsd @@ -0,0 +1,44 @@ + + + + [<font color="#ff0000">Sea-surface state not present in GRIB Code-table 4.2 (category + 3: Surface properties) - but included here ... although it may be more appropriately + placed in category 0 "waves"</font>] + + + + + + + The temperature of the ocean surface. The term sea surface temperature is generally + meant to be representative of the upper few meters of the ocean as opposed to the + skin temperature, which is the temperature of the upper few centimeters. In FM-92 + GRIB, encoded as GRIB Code-table 4.2 discipline 10 (oceanography), category 3 (surface + properties), #0 water temperature. + + + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-22-061 + none + + Categorical assessment of sea surface state (or other large open body of water) based + on height of waves. Height in metres : Category - 0 metres : Calm (glassy) - 0-0.1 + metres : Calm (rippled) - 0.1-0.5 metres : Smooth - 0.5-1.25 metres : Slight - 1.25-2.5 + metres : Moderate - 2.5-4 metres : Rough - 4-6 metres : Very rough - 6-9 metres : + High - 9-14 metres : Very high - &gt;14 metres : Phenomenal See WMO No. 306: - WMO + Code table 3700 "State of the sea" - BUFR Code table 0 22 061 "State of the sea" + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/met-basic/1.0RC1/temperature.xsd b/config/schemas/schema/int/wmo/met-basic/1.0RC1/temperature.xsd new file mode 100644 index 0000000..bbf2c63 --- /dev/null +++ b/config/schemas/schema/int/wmo/met-basic/1.0RC1/temperature.xsd @@ -0,0 +1,32 @@ + + + + + + + The temperature indicated by a thermometer exposed to the air in a place sheltered + from direct solar radiation. In FM-92 GRIB, encoded as GRIB Code-table 4.2 discipline + 0 (meteorology), category 0 (temperature), #0 temperature. + + + + + + + + + + + The temperature to which a given air parcel must be cooled at constant pressure and + constant water vapor content in order for saturation to occur. In FM-92 GRIB, encoded + as GRIB Code-table 4.2 discipline 0 (meteorology), category 0 (temperature), #6 dew-point + temperature. + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0/metce.xsd b/config/schemas/schema/int/wmo/metce/1.0/metce.xsd new file mode 100644 index 0000000..9a19c3a --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0/metce.xsd @@ -0,0 +1,31 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + This Logical Data Model is intended to support the entire scope of WMO concerns: weather, + climate and water. To reflect this scope, the model is named 'Modele pour l'Echange + des informations sur le Temps, le Climat et l'Eau' (METCE). In English, it may also + be known as the ‘METeorological Community Exchange’ model. METCE is intended to provide + conceptual definitions of meteorological phenomena, entities and concepts in order + to underpin semantic interoperability in the weather, climate and water domain. The + «Application Schema» includes: (i) specialisations of OM_Observation, OM_ComplexObservation + and OM_DiscreteCoverageObservation classes (from ISO 19156); (ii) a concrete implementation + of OM_Process (from ISO 19156); (iii) a number of meteorological feature types schemes + thereof; and (iv) some miscellaneous items (e.g. ?enumerations? for specifying intensity + changes). The 'METCE' «Application Schema» will typically be imported to provide + a baseline conceptual model framework upon which community-specific Application Schema + are based. + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.0/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.0/phenomena.xsd new file mode 100644 index 0000000..338cba6 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0/phenomena.xsd @@ -0,0 +1,121 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The package 'Meteorological Phenomena' contains «FeatureType» entities that have a + significant role in meteorology; e.g. volcanoes and tropical cyclones. A list of + meteorological phenomena are provided in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 08 011 'Meteorological Feature' (see below). It is anticipated that in future releases + the additional meteorological features listed therein will be incorporated. Meteorological + Features (from WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011): - Quasi-stationary + front at the surface - Quasi-stationary front above the surface - Warm front at the + surface - Warm front above the surface - Cold front at the surface - Cold front above + the surface - Occlusion - Instability line - Intertropical front - Convergence line + - Jet stream - Cloud clear - Cloud - Turbulence - Storm - Airframe icing - [Erupting] + Volcano - Atmospherics - Special clouds - Thunderstorm - Tropical cyclone - Mountain + wave - Duststorm - Sandstorm + + + + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum + surface pressure in some cases less than 900 hPa, very violent winds and torrential + rain; sometimes accompanied by thunderstorms. It usually contains a central region, + known as the “eye” of the storm, with a diameter of the order of some tens of kilometres, + and with light winds and more or less lightly clouded sky. WMO No. 306 Vol I.1 code-table + 3704 "Shape and definition of the eye of the tropical cyclone" and WMO No. 306 Vol + I.1 code-table 3790 "Intensity of the tropical cyclone" provide additional candidate + attributes that may be incorporated within this «FeatureType» in subsequent versions + of METCE. + + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + A volcano irrespective of the volcano's current state (e.g. passive or erupting). + Note that the "Global Volcanism Program" provides an online, searchable catalogue + of volcanoes which may assist in identifying the authoritative name for a given volcano + feature [http://www.volcano.si.edu/world/]. (informative) + + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + A volcano that is currently erupting, or has recently erupted, that is the source + of volcanic ash or other significant meteorological phenomena described in operational + weather reports. + + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.0/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.0/procedure.xsd new file mode 100644 index 0000000..5ea63c0 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0/procedure.xsd @@ -0,0 +1,232 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The 'Procedure' package provides a concrete implementation of the abstract OM_Process + class (from ISO 19156). The implementation is intended to support the following requirements: + 1) reference to supporting documentation (attribute "documentationRef"); e.g. online + documentation describing the procedure in detail; 2) specification of parameters that + remain fixed within a particular configuration of the procedure (Configuration); a + soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + Schematron validation + + + + + + + + + + + + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. An instance + of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated + state), but it may be a human observer executing a set of instructions, a simulator + or process algorithm. The 'Procedure' should provide sufficient information to interpret + the result of an observation; thus if a sensor is recalibrated or its height above + local ground is changed, a new instance of OM_Process should be created and associated + with subsequent observations from that sensor (at least until the sensor is changed + again). Predominantly we expect the Process instance to be externally published / + defined and 'static' (e.g. perhaps changing less often than once per month due to + amendments to operational protocols etc.). The class 'Process' provides a concrete + implementation of OM_Process (from ISO 19156). The implementation is intended to + support the following requirements: 1) reference to supporting documentation (documentationRef); + e.g. online documentation describing the procedure in detail; 2) specification of + parameters that remain fixed within a particular configuration of the procedure (Configuration); + a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + Reference to an external process definition providing information about relevant documentation + that describes the associated Process. + + + + + + The association role 'parameter' references an instance of NamedValue that specifies + parameters associated with a particular configuration of the procedure (Configuration) + + + + + + The association role 'context' references an instance of MeasurementContext class + that defines resolution and measuring interval for a specific measurand. + + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring + interval [2] for a given physical property in the context of this measurement procedure. + [1] Resolution: smallest change in a quantity being measured that causes a perceptible + change in the corresponding indication (from the 'International vocabulary of metrology' + [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) [2] Measuring + interval: set of values of quantities of the same kind that can be measured by a given + measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' + and 'measuring interval' are specified in. Typically, this will also be the unit + of measure used to specify the measured quantity values. Unless otherwise specified, + this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + + The attribute 'measurand' [1] specifies the physical property that the associated + 'resolution' and 'measuring interval' apply to. The measurand may be sourced from + an external controlled vocabulary, thesaurus or ontology or defined locally. The + measurand may reference a qualified observable property if required. If the measurand + references an observable physical property that serves as the base property for a + qualified observable property, the measurement context is assumed to apply to ALL + the qualified observable properties that reference this base property unless otherwise + stated. For example, observable physical property 'radiance' may be qualified to measure + wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated + with 'radiance' would be inferred to apply to all of these qualified radiance properties. + [1] Measurand: quantity intended to be measured (from the 'International vocabulary + of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits + of property values of the 'measurand' that can measured within this procedure, using + the unit of measure 'uom'. [1] Measuring interval: set of values of quantities of + the same kind that can be measured by a given measuring instrument or measuring system + with specified instrumental uncertainty, under defined conditions (from the 'International + vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' + [1]) in property value of the 'measurand' that is intended to be measured within this + procedure, using the unit of measure 'uom'. This shall be provided as a scaling factor. + For example: <ul> <li>scale = -2 implies a precision of 100 units </li> <li>scale + = -1 implies a precision of 10 units</li> <li>scale = 0 implies a precision of 1 + unit</li> <li>scale = 1 implies a precision of 0.1 units</li> <li>scale = 2 implies + a precision of 0.01 units </li> </ul> etc. [1] Resolution: smallest change in a quantity + being measured that causes a perceptible change in the corresponding indication (from + the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.0RC1/metce.xsd b/config/schemas/schema/int/wmo/metce/1.0RC1/metce.xsd new file mode 100644 index 0000000..775f1a7 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC1/metce.xsd @@ -0,0 +1,27 @@ + + + + The WMO Logical Data Model is intended to support the entire scope of WMO concerns: + weather, climate and water. To reflect this scope, the WMO Logical Data Model is named + 'Modèle pour l'Échange des informations sur le Temps, le Climat et l'Eau' (METCE). + In English, it may also be known as the ‘METeorological Community Exchange’ model. + WMO METCE is intended to provide conceptual definitions of meteorological phenomena, + entities and concepts in order to underpin semantic interoperability in the weather, + climate and water domain. The «Application Schema» includes: <ul> <li>specialisations + of OM_Observation, OM_ComplexObservation and OM_DiscreteCoverageObservation classes + (from ISO 19156)</li> <li>a concrete implementation of OM_Process (from ISO 19156)</li> + <li>a number of meteorological feature types and categorisation schemes thereof.</li> + </ul> The 'WMO METCE' «Application Schema» will typically be imported to provide + a baseline conceptual model framework upon which community-specific Application Schema + are based. + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC1/observationTypes.xsd b/config/schemas/schema/int/wmo/metce/1.0RC1/observationTypes.xsd new file mode 100644 index 0000000..b20ce4a --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC1/observationTypes.xsd @@ -0,0 +1,324 @@ + + + + ISO 19156 ‘Observations and measurements’ provides a conceptual schema for observations + and the features involved in sampling when making observations, and specifically designed + to support the exchange of information describing both the observing event and the + results of the observation between different scientific and technical communities. + Whilst the name of the model invokes a particular concept to meteorologists (e.g. + ‘observation’, the measurement of physical phenomena with an instrument or sensor + – disjoint from the concept of ‘forecast’) it is important to consider the semantics + of the model. The class OM_Observation is defined as ‘an estimate of the value of + some property of some Thing using some specified Process’. The process may be an instrument/sensor + (directly) measuring some physical parameter or a numerical simulation predicting + future values. Thus the ‘Observations and measurements’ conceptual model may be used + to represent both observations and forecasts. Meteorological observations or forecasts + clearly relate to the real world. For example, we may observe the weather for Exeter + or provide a weather forecast for the ‘North Atlantic European’ area. However, there + is a level of abstraction to resolve: - An observation of the weather for the city + of Exeter happens at some representative location within the city or some representative + locale nearby; or - The forecast domain for ‘North Atlantic European’ is specified + so that it covers the areas for which a forecast is required In each case, the ‘observation’ + event relates to some sampling regime that is a proxy for the real entity of interest + (e.g. the site of the weather station, or the extent of the forecast domain). The + observation or forecast is not directly related to real-world entities. ISO 19156 + ‘Observations and measurements’ provides a conceptual model for describing this layer + of indirection: Sampling Features. Further specialisations of Sampling Feature are + provided based on spatial topology (SF_SpatialSamplingFeature and sub-types thereof). + In all cases identified thus far in meteorology, it appears useful to describe an + observation, measurement or forecast with respect to the sampling regime (e.g. the + Sampling Feature) and indirectly refer to the real-world entity for which the Sampling + Feature is a proxy. Spatial Sampling Features are considered an essential part of + WMO METCE: all observations, measurements and forecasts of meteorological phenomena + shall define the ‘featureOfInterest’ as a concrete sub-type of SF_SpatialSamplingFeature. + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. In order to + ensure a consistent implementation of the abstract OM_Process class, *ALL* Application + Schema based on WMO METCE shall use the WMO Process class (or sub-class thereof) to + describe the observation procedure. WMO METCE provides three specialised types of + OM_Observation; each of which enforce the constraints that 'featureOfInterest' shall + refer to an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass + thereof, and 'procedure' shall refer to an entity of type Process (from WMO METCE), + or subclass thereof. - SamplingObservation: subclass of OM_Observation providing a + general purpose observation type; - ComplexSamplingMeasurement: subclass of OM_ComplexObservation + for use where the observation event is concerned with the evaluation of multiple measurands + at a specified location and time instant or duration - the result of this observation + type shall refer to an entity of type Record (from ISO 19103), or subclass thereof; + and - SamplingCoverageMeasurement: subclass of OM_DiscreteCoverageObservation for + use where the observation is concerned with the evaluation of measurands that vary + with respect to space and/or time - the result of this observation type shall refer + to an entity of type CV_DiscreteCoverage (from ISO 19123). --- <i>A note on the + application of OM_Observation/observedProperty:</i> If one looks at the examples + in ISO 19156 and Sensor Observation Service specification, examples of observedProperty + include 'mass', 'salinity', 'water height' and 'effective temperature'. In the case + of the third and fourth example, these are drawn from the NASA SWEET ontology. Using + the terminology from the International vocabulary of metrology [1] these are 'Quantities'. + Although observedProperty is specified in ISO 19156 as type GF_PropertyType (from + ISO 19109), the behaviour inferred from the examples indicates that observedProperty + is used to refer to specific entities rather than the relationships between entities. + The General Feature Model (as defined in ISO 19109) specifies instances of a «metaclass» + (e.g. GF_PropertyType) as UML Classes. In contrast, the rules for Application Schema + require that properties are implemented as attributes, association roles and operations + resulting in a contradicting duality of 'classes-that-are-properties'. However, + given that observedProperty is implemented in GML as gml:ReferenceType, observedProperty + can only refer to its target value via xlink:href (e.g. using HTTP URI). No type checking + of the xlink target is implied. Thus we can *ASSUME* that the observedProperty behaves + like an instance of a Class without adverse side effects, thus matching the behaviour + we see in the examples. We don't need to get too hung up with ensuring that the entities + referenced by observedProperty are faithful implementations of GF_PropertyType (e.g. + FC_PropertyType); we can reference definitions of Quantities from external thesauri, + ontologies or feature type catalogues that meet the desired semantics. In some cases + the Quantity referenced via observedProperty *MAY* genuinely be GF_PropertyType that + is used in the Feature Type specification of a domain feature; for example GF_PropertyType + 'salinity' may be an attribute of a WaterBody «FeatureType». Alternatively, one may + publish a definition of «FeatureType» WaterBody and the associated GF_AttributeType + 'salinity' in a Feature Type Catalogue and the assert that GF_AttributeType WaterBody.salinity + is equivalent to an existing definition of salinity Quantity (e.g. http://sweet.jpl.nasa.gov/2.3/propChemical.owl#Salinity) + that is used as the value of observedProperty in observation datasets. This would + allow one to reconcile these 'properties' and match domain feature to observation + result. However, we must note that the observedProperty is only meant to provide + a metadata hook to find observations associated with a given quantity. Previously, + the role of observedProperty has been over interpreted: it is not a binding mechanism + between domain feature and observation result - just metadata describing the quantity + observed. As an aside, note that within the Sensor Observation Service, the observedProperty + is a key used within the query API to select observations. This is why observedProperty + is implemented as gml:ReferenceType: the identifier is used as the well-known key + to extract appropriate data. It is not uncommon for an observation or measurement + event to evaluate multiple measurands. For example: - a 'water quality' measurement + may evaluate properties such as salinity, nitrate, dissolved oxygen, pH and turbidity; + - a weather forecast produced from a numerical simulation may simultaneously evaluate + dozens of parameters. One of the most useful 'discovery paths' for finding observation + data is anticipated to use the observed physical phenomenon; "find me all the Observations + that include 'air-temperature' data". Crucially, the Observation provides metadata + about the resultant datasets, mitigating the need for a data-consumer to parse the + data-payload to discover physical phenomena are included. This is especially important + for coverage datasets where it is not unusual for the data-payload may be many gigabytes + in size - or larger! OM_Observation/observedProperty provides one such mechanism + to discover Observations. However, observedProperty is specified with cardinality + of one; only a single property can be referenced. Thus in the example above, observedProperty + can only be used to reference an aggregate property such as 'water quality'. To discover + observations based on the individual quantities (e.g. salinity, nitrate, dissolved + oxygen, pH or turbidity) the observedProperty must be supplemented. One option is + to put the physical property information in the OM_Observation/procedure/OM_Process. + The 'procedure' may include a description of the set of measured phenomena. However, + as the OM_Process object will typically be re-used across a number of Observation + events, it is likely that the object will be published as a separate entity that is + _REFERENCED_ from the Observation. Finding specific Observations that include measurements + of a given physical phenomenon would require the OM_Process object to be fully resolved + for indexing to support search. Two options are proposed: i) External definition + of aggregate property: - An external definition of 'water quality' may be provided + that aggregates 'salinity', 'nitrate', 'dissolved oxygen', 'pH' and 'turbidity'. + - A user searching for data on 'turbidity' would first search those external definitions + for references to property 'turbidity', resulting in the property 'water quality' + being discovered. - Subsequently, the user would search for observations with observedProperty + specified as 'turbidity' -OR- 'water quality'. ii) Internal definition of aggregate + property using Observable Property model: - The individual properties 'salinity', + 'nitrate', 'dissolved oxygen', 'pH' and 'turbidity' may be specified via OM_Observation/parameter + using the soft-typed NamedValue class. - The appropriate semantics are found in the + GF_AssociationRole 'property' within the Observable Property model; the valueType + is specified as AbstractObservableProperty enabling an instance of either CompositeObservableProperty + -OR- ObservableProperty to be referenced. - NamedValue/name is specified as Type + 'GenericName'. To enable software systems to identify the ObservedProperty entities + when parsing the observation, 'name' must be specified consistently. - Assuming that + the Observed Property model is published within a Feature Type Catalogue as part of + WMO METCE as an instance of FC_AssociationRole, GF_AssociationRole 'property' will + be identified with the HTTP URI http://data.wmo.int/def/observable-property/property. + - NamedValue/value is specified as Type 'Any'; in this case, 'value' shall be defined + as an instance of CompositeObservableProperty enabling each of the individual physical + properties to be specified within the composite. - Data management systems can be + configured to index observation instances based on the Observable Property. Use of + the Observable Property model also enables a data publisher to explicitly specify + any constraints or qualifications associated with the observed physical properties. + Please refer to the Observed Property model for more details. [1] http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf + + + Schematron validation + + + + + + + + + + + + + + + + + + Class SamplingCoverageMeasurement (a subclass of OM_DiscreteCoverageObservation) is + intended for use where the observation is concerned with the evaluation of measurands + that vary with respect to space and/or time - the result of this observation type + shall refer to an entity of type CV_DiscreteCoverage (from ISO 19123). ComplexSamplingMeasurement + enforces the following additional constraints: - 'featureOfInterest' shall refer to + an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass thereof; + and - 'procedure' shall refer to an entity of type Process (from WMO METCE), or subclass + thereof A critical concern of meteorology is the understanding of the variation of + physical phenomena with either space and/or time. This is exactly what the Coverage + model is designed to convey. Coverages are defined in 2 distinct categories: Discrete + and Continuous. The main difference is that Continuous coverages provide an interpolation + function to evaluate the phenomena at any point within the coverage domain, which + Discrete coverages do not. A Discrete coverage is comprised of a number of domain + elements (e.g. discrete locations where the phenomenon is sampled) and the associated + range elements (e.g. the data). Where the phenomena are considered to be continuously + varying within the Coverage domain, a user may apply their own interpolation algorithm + as meets their specific requirement. When describing properties that vary in space + and/or time, WMO METCE shall make exclusive use only of Discrete coverages. The Class + ‘SamplingCoverageMeasurement’ is based on the SamplingCoverageObservation which is + defined in an informative annex of ISO 19156. However, the term ‘measurement’ is used + in the name in an attempt to reduce confusion arising from the overloading of the + term ‘observation’. + + + + + SamplingCoverageMeasurement: [missing message] + + + + + SamplingCoverageMeasurement: [missing message] + + + + + SamplingCoverageMeasurement: [missing message] + + + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + + + Class SamplingObservation (a subclass of OM_Observation) provides a general purpose + observation type. It enforces the following additional constraints: - 'featureOfInterest' + shall refer to an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass + thereof; and - 'procedure' shall refer to an entity of type Process (from WMO METCE), + or subclass thereof SamplingObservation is intended for use where measurement of + physical phenomena is not the goal of the procedure. For example, the procedure executed + to define SIGMET reports results in the identification of areas of turbulence, icing + or other meteorological phenomena. + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + + + Class ComplexSamplingMeasurement (a subclass of OM_ComplexObservation) is intended + for use where the observation event is concerned with the evaluation of multiple measurands + at a specified location and time instant or duration. The result of this observation + type shall refer to an entity of type Record (from ISO 19103), or subclass thereof + ComplexSamplingMeasurement enforces the following additional constraints: - 'featureOfInterest' + shall refer to an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass + thereof; and - 'procedure' shall refer to an entity of type Process (from WMO METCE), + or subclass thereof The OM_ComplexObservation is used because the 'result' of this + class of observations is a group of measures, provided as a Record. Again, this matches + the WMO application domain wherein multiple phenomena are measured within a single + 'observation event'. The term ‘measurement’ is used in the name in an attempt to + reduce confusion arising from the overloading of the term ‘observation’. + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC1/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.0RC1/phenomena.xsd new file mode 100644 index 0000000..95939cf --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC1/phenomena.xsd @@ -0,0 +1,131 @@ + + + + The package 'Meteorological Phenomena' contains: - «FeatureType» entities that have + a significant role in meteorology; e.g. volcanoes and tropical cyclones. - «CodeList» + class(es) providing a categorisation of meteorological phenonema. + + + + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum + surface pressure in some cases less than 900 hPa, very violent winds and torrential + rain; sometimes accompanied by thunderstorms. It usually contains a central region, + known as the &ldquo;eye&rdquo; of the storm, with a diameter of the order of some + tens of kilometres, and with light winds and more or less lightly clouded sky. See + WMO Code table 3704 "Shape and definition of the eye of the tropical cyclone" and + WMO Code table 3790 "Intensity of the tropical cyclone" for candidate attributes for + this class. + + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + The class 'Volcano' describes a volcano irrespective of the volcano's current state. + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + The class 'EruptingVolcano' describes a volcano that is currently erupting, or has + recently erupted, that is the source of volcanic ash or other significant meteorological + phenomena described in current operational weather reports. + + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + + + + http://data.wmo.int/def/49-2/SigWxPhenomena + none + + Weather phenomenon of significance to aviation operations; used in SIGMET and AIRMET + reports. The set of permitted options are defined in WMO No. 49 C.3.1. sub-clause + 1.1.4. + + + + + + + + + + http://data.wmo.int/def/bufr4/codeflag/0-08-011 + any + + Categorisation of meteorological phenomena. See WMO No. 306 BUFR Code-table 0 08 + 011 "Meteorological Feature" + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC1/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.0RC1/procedure.xsd new file mode 100644 index 0000000..72c566e --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC1/procedure.xsd @@ -0,0 +1,296 @@ + + + + The 'Procedure' package provides a concrete implementation of the abstract OM_Process + class (from ISO 19156). The implementation is intended to support the following requirements: + 1) reference to supporting documentation (ProcessDocumentation); e.g. online documentation + describing the procedure in detail; 2) specification of parameters that remain fixed + within a particular configuration of the procedure (Configuration); a soft-typed approach + is used here following the pattern adopted for OM_Observation/parameter; 3) specification + of the resolution [1] with which each observed physical phenomenon is measured; and + 4) specification of the measuring interval [2] of the instrument or sensor for each + observed physical phenomenon. [1] Resolution: smallest change in a quantity being + measured that causes a perceptible change in the corresponding indication (from the + 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + Schematron validation + + + + + + + + + + + + + + + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. An instance + of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated + state), but it may be a human observer executing a set of instructions, a simulator + or process algorithm. The 'Procedure' should provide sufficient information to interpret + the result of an observation; thus if a sensor is recalibrated or its height above + local ground is changed, a new instance of OM_Process should be created and associated + with subsequent observations from that sensor (at least until the sensor is changed + again). Predominantly we expect the Process instance to be externally published / + defined and 'static' (e.g. perhaps changing less often than once per month due to + amendments to operational protocols etc.). The class 'Process' provides a concrete + implementation of OM_Process (from ISO 19156). The implementation is intended to + support the following requirements: 1) reference to supporting documentation (ProcessDocumentation); + e.g. online documentation describing the procedure in detail; 2) specification of + parameters that remain fixed within a particular configuration of the procedure (Configuration); + a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + Reference to an external process definition providing information about relevant documentation + that describes the associated Process. + + + + + + The association role 'context' references an instance of MeasurementContext class + that defines resolution and measuring interval for a specific measurand. + + + + + + The association role 'parameter' references an instance of NamedValue that specifies + parameters associated with a particular configuration of the procedure (Configuration) + + + + + + + + + + + + + + + + + The granularity of an Observation or Measurement event is somewhat arbitrary; largely + dependent on how the measurement results are packaged for consumption. For example, + a WMO synoptic observation aggregates data from multiple procedures each of which + are considered to be part of an aggregate procedure defined in regulation. The execution + of this aggregate procedure is considered to be a single event, and is thus described + using a single Observation instance. Thus a single Procedure may evaluate a number + of physical properties. Where quantitative properties are evaluated, it is essential + that the resolution [1] and measuring interval [2] of the measurement procedure can + be specified. The abstract class 'AbstractMeasurementContext' enables either a simple + context definition (where a single quantity is evaluated as a result of the procedure) + or a complex context definition comprising of 2 or more simple definitions. [1] Resolution: + smallest change in a quantity being measured that causes a perceptible change in the + corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + In the case where a procedure measures multiple physical quantities, the class 'CompositeMeasurementContext' + enables a measurement context to be defined for each measurand. + + + + + CompositeMeasurementContext: The attribute 'count' defines the number of associated + instances of MeasurementContext, referenced via the association role 'context' + + + + + + + + + + + + + The number of measurement context instances (each associated with a specific measurand) + aggregated within this composite. + + + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring + interval [2] for a given physical property in the context of this measurement procedure. + [<i>Note that attribute measuringInterval may be inferred to mean temporal duration; + please provide feedback</i>] [1] Resolution: smallest change in a quantity being + measured that causes a perceptible change in the corresponding indication (from the + 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + MeasurementContext: [missing message] + + + + + + + + + + + + The attribute 'measurand' [1] specifies the physical property that the associated + 'resolution' and 'measuring interval' apply to. The measurand may be sourced from + an external controlled vocabulary, thesaurus or ontology or defined locally. The + measurand may reference a qualified observable property if required. If the measurand + references an observable physical property that serves as the base property for a + qualified observable property, the measurement context is assumed to apply to ALL + the qualified observable properties that reference this base property unless otherwise + stated. For example, observable physical property 'radiance' may be qualified to measure + wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated + with 'radiance' would be inferred to apply to all of these qualified radiance properties. + [1] Measurand: quantity intended to be measured (from the 'International vocabulary + of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits + of property values of the 'measurand' that can measured within this procedure, using + the unit of measure 'uom'. [1] Measuring interval: set of values of quantities of + the same kind that can be measured by a given measuring instrument or measuring system + with specified instrumental uncertainty, under defined conditions (from the 'International + vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' + [1]) in property value of the 'measurand' that is intended to be measured within this + procedure, using the unit of measure 'uom'. This shall be provided as a scaling factor. + For example: <ul> <li>scale = -2 implies a precision of 100 units </li> <li>scale + = -1 implies a precision of 10 units</li> <li>scale = 0 implies a precision of 1 + unit</li> <li>scale = 1 implies a precision of 0.1 units</li> <li>scale = 2 implies + a precision of 0.01 units </li> </ul> etc. [1] Resolution: smallest change in a quantity + being measured that causes a perceptible change in the corresponding indication (from + the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' + and 'measuring interval' are specified in. Typically, this will also be the unit + of measure used to specify the measured quantity values. Unless otherwise specified, + this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC1/qualifiers.xsd b/config/schemas/schema/int/wmo/metce/1.0RC1/qualifiers.xsd new file mode 100644 index 0000000..2e34a24 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC1/qualifiers.xsd @@ -0,0 +1,66 @@ + + + + The 'Qualifiers' package contains classes that provide additional context about some + entity (e.g. they 'qualify' that entity). Examples include &lt;enumeration&gt; ExpectedIntensityChange + and &lt;enumeration&gt; ForecastChangeIndicator. + + + + + + + Change qualifier of a trend-type forecast or an aerodrome forecast. Defined in WMO + No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. See also BUFR Code-table + 0 08 016. Conditions typically reported as NO_SIGNFICANT_CHANGE (NSC) shall be encoded + using the "nothingOfOperationalSignificance" nil-reason code. [<font color="#ff0000">http://data.wmo.int/def/nil-reason/nothingOfOperationalSignificance</font>] + + + + + + When the change is forecast to commence at the beginning of the forecast period and + be completed by the end of that period, or when the change is forecast to occur within + the forecast period but the time of the change is uncertain (possibly shortly after + the beginning of the forecast period, or midway or near the end of that period), the + change shall be indicated by only the change indicator BECMG. + + + + + + The change indicator TEMPO shall be used to describe expected temporary fluctuations + to meteorological conditions which reach or pass specified threshold criteria and + last for a period of less than one hour in each instance and in the aggregate cover + less than half of the forecast period during which the fluctuations are expected to + occur. + + + + + + + + Expected change in intensity for (significant) meteorological phenomena. See WMO + No. 306 BUFR Code table 0 20 028 + + + + + + No change + + + + + Weakening + + + + + Intensifying + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC2/metce.xsd b/config/schemas/schema/int/wmo/metce/1.0RC2/metce.xsd new file mode 100644 index 0000000..0d4f49f --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC2/metce.xsd @@ -0,0 +1,26 @@ + + + + This Logical Data Model is intended to support the entire scope of WMO concerns: weather, + climate and water. To reflect this scope, the model is named 'Modele pour l'Echange + des informations sur le Temps, le Climat et l'Eau' (METCE). In English, it may also + be known as the ‘METeorological Community Exchange’ model. METCE is intended to provide + conceptual definitions of meteorological phenomena, entities and concepts in order + to underpin semantic interoperability in the weather, climate and water domain. The + ?Application Schema? includes: (i) specialisations of OM_Observation, OM_ComplexObservation + and OM_DiscreteCoverageObservation classes (from ISO 19156); (ii) a concrete implementation + of OM_Process (from ISO 19156); (iii) a number of meteorological feature types schemes + thereof; and (iv) some miscellaneous items (e.g. ?enumerations? for specifying intensity + changes). The 'METCE' ?Application Schema? will typically be imported to provide + a baseline conceptual model framework upon which community-specific Application Schema + are based. + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC2/observation-types.xsd b/config/schemas/schema/int/wmo/metce/1.0RC2/observation-types.xsd new file mode 100644 index 0000000..879dbd3 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC2/observation-types.xsd @@ -0,0 +1,213 @@ + + + + ISO 19156 ‘Observations and measurements’ provides a conceptual schema for observations + and the features involved in sampling when making observations, and specifically designed + to support the exchange of information describing both the observing event and the + results of the observation between different scientific and technical communities. + Whilst the name of the model invokes a particular concept to meteorologists (e.g. + ‘observation’, the measurement of physical phenomena with an instrument or sensor + – disjoint from the concept of ‘forecast’) it is important to consider the semantics + of the model. The class OM_Observation is defined as ‘an estimate of the value of + some property of some Thing using some specified Process’. The process may be an instrument/sensor + (directly) measuring some physical parameter or a numerical simulation predicting + future values. Thus the ‘Observations and measurements’ conceptual model may be used + to represent both observations and forecasts. Meteorological observations or forecasts + clearly relate to the real world. For example, we may observe the weather for Exeter + or provide a weather forecast for the ‘North Atlantic European’ area. However, there + is a level of abstraction to resolve: - An observation of the weather for the city + of Exeter happens at some representative location within the city or some representative + locale nearby; or - The forecast domain for ‘North Atlantic European’ is specified + so that it covers the areas for which a forecast is required In each case, the ‘observation’ + event relates to some sampling regime that is a proxy for the real entity of interest + (e.g. the site of the weather station, or the extent of the forecast domain). The + observation or forecast is not directly related to real-world entities. ISO 19156 + ‘Observations and measurements’ provides a conceptual model for describing this layer + of indirection: Sampling Features. Further specialisations of Sampling Feature are + provided based on spatial topology (SF_SpatialSamplingFeature and sub-types thereof). + In all cases identified thus far in meteorology, it appears useful to describe an + observation, measurement or forecast with respect to the sampling regime (e.g. the + Sampling Feature) and indirectly refer to the real-world entity for which the Sampling + Feature is a proxy. Spatial Sampling Features are considered an essential part of + METCE: all observations, measurements and forecasts of meteorological phenomena shall + define the ‘featureOfInterest’ as a concrete sub-type of SF_SpatialSamplingFeature. + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. In order to + ensure a consistent implementation of the abstract OM_Process class, *ALL* Application + Schema based on METCE shall use the Process class defined therein (or sub-class thereof) + to describe the observation procedure. METCE provides three specialised types of + OM_Observation; each of which enforce the constraints that 'featureOfInterest' shall + refer to an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass + thereof, and 'procedure' shall refer to an entity of type Process (from METCE), or + subclass thereof. - SamplingObservation: subclass of OM_Observation providing a general + purpose observation type; - ComplexSamplingMeasurement: subclass of OM_ComplexObservation + for use where the observation event is concerned with the evaluation of multiple measurands + at a specified location and time instant or duration - the result of this observation + type shall refer to an entity of type Record (from ISO 19103), or subclass thereof; + and - SamplingCoverageMeasurement: subclass of OM_DiscreteCoverageObservation for + use where the observation is concerned with the evaluation of measurands that vary + with respect to space and/or time - the result of this observation type shall refer + to an entity of type CV_DiscreteCoverage (from ISO 19123). + + + + + + + + + Class SamplingCoverageMeasurement (a subclass of OM_DiscreteCoverageObservation) is + intended for use where the observation is concerned with the evaluation of measurands + that vary with respect to space and/or time - the result of this observation type + shall refer to an entity of type CV_DiscreteCoverage (from ISO 19123). ComplexSamplingMeasurement + enforces the following additional constraints: - 'featureOfInterest' shall refer to + an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass thereof; + and - 'procedure' shall refer to an entity of type Process (from METCE), or subclass + thereof A critical concern of meteorology is the understanding of the variation of + physical phenomena with either space and/or time. This is exactly what the Coverage + model is designed to convey. Coverages are defined in 2 distinct categories: Discrete + and Continuous. The main difference is that Continuous coverages provide an interpolation + function to evaluate the phenomena at any point within the coverage domain, which + Discrete coverages do not. A Discrete coverage is comprised of a number of domain + elements (e.g. discrete locations where the phenomenon is sampled) and the associated + range elements (e.g. the data). Where the phenomena are considered to be continuously + varying within the Coverage domain, a user may apply their own interpolation algorithm + as meets their specific requirement. When describing properties that vary in space + and/or time, METCE shall make exclusive use only of Discrete coverages. The Class + ‘SamplingCoverageMeasurement’ is based on the SamplingCoverageObservation which is + defined in an informative annex of ISO 19156. However, the term ‘measurement’ is used + in the name in an attempt to reduce confusion arising from the overloading of the + term ‘observation’. + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + + + Class SamplingObservation (a subclass of OM_Observation) provides a general purpose + observation type. It enforces the following additional constraints: - 'featureOfInterest' + shall refer to an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass + thereof; and - 'procedure' shall refer to an entity of type Process (from METCE), + or subclass thereof SamplingObservation is intended for use where measurement of + physical phenomena is not the goal of the procedure. For example, the procedure executed + to define SIGMET reports results in the identification of areas of turbulence, icing + or other meteorological phenomena. + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + + + Class ComplexSamplingMeasurement (a subclass of OM_ComplexObservation) is intended + for use where the observation event is concerned with the evaluation of multiple measurands + at a specified location and time instant or duration. The result of this observation + type shall refer to an entity of metatype Record (from ISO 19103). ComplexSamplingMeasurement + enforces the following additional constraints: - 'featureOfInterest' shall refer to + an entity of type SF_SpatialSamplingFeature (from ISO 19156), or subclass thereof; + and - 'procedure' shall refer to an entity of type Process (from METCE), or subclass + thereof The OM_ComplexObservation is used because the 'result' of this class of observations + is a group of measures, provided as a Record. Again, this matches the WMO application + domain wherein multiple phenomena are measured within a single 'observation event'. + The term ‘measurement’ is used in the name in an attempt to reduce confusion arising + from the overloading of the term ‘observation’. + + + + + + + + + + The association role 'procedure' is further constrained to refer to an entity of type + Process (from WMO METCE). This ensures that a valid concrete implementation of OM_Process + is supplied. + + + + + + The association role 'featureOfInterest' is further constrained to refer to an entity + of type 'SF_SpatialSamplingFeature' (from ISO 19156). In all cases identified thus + far in meteorology, it appears useful to describe an observation, measurement or forecast + with respect to the sampling regime (e.g. the Sampling Feature) and indirectly refer + to the real-world entity for which the Sampling Feature is a proxy. + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC2/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.0RC2/phenomena.xsd new file mode 100644 index 0000000..679ddba --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC2/phenomena.xsd @@ -0,0 +1,116 @@ + + + + The package 'Meteorological Phenomena' contains ?FeatureType? entities that have a + significant role in meteorology; e.g. volcanoes and tropical cyclones. A list of + meteorological phenomena are provided in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 08 011 'Meteorological Feature' (see below). It is anticipated that in future releases + the additional meteorological features listed therein will be incorporated. Meteorological + Features (from WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011): - Quasi-stationary + front at the surface - Quasi-stationary front above the surface - Warm front at the + surface - Warm front above the surface - Cold front at the surface - Cold front above + the surface - Occlusion - Instability line - Intertropical front - Convergence line + - Jet stream - Cloud clear - Cloud - Turbulence - Storm - Airframe icing - [Erupting] + Volcano - Atmospherics - Special clouds - Thunderstorm - Tropical cyclone - Mountain + wave - Duststorm - Sandstorm + + + + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum + surface pressure in some cases less than 900 hPa, very violent winds and torrential + rain; sometimes accompanied by thunderstorms. It usually contains a central region, + known as the “eye” of the storm, with a diameter of the order of some tens of kilometres, + and with light winds and more or less lightly clouded sky. WMO No. 306 Vol I.1 code-table + 3704 "Shape and definition of the eye of the tropical cyclone" and WMO No. 306 Vol + I.1 code-table 3790 "Intensity of the tropical cyclone" provide additional candidate + attributes that may be incorporated within this ?FeatureType? in subsequent versions + of METCE. + + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + A volcano irrespective of the volcano's current state (e.g. passive or erupting). + Note that the "Global Volcanism Program" provides an online, searchable catalogue + of volcanoes which may assist in identifying the authoritative name for a given volcano + feature [http://www.volcano.si.edu/world/]. (informative) + + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + A volcano that is currently erupting, or has recently erupted, that is the source + of volcanic ash or other significant meteorological phenomena described in operational + weather reports. + + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.0RC2/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.0RC2/procedure.xsd new file mode 100644 index 0000000..8059490 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.0RC2/procedure.xsd @@ -0,0 +1,227 @@ + + + + The 'Procedure' package provides a concrete implementation of the abstract OM_Process + class (from ISO 19156). The implementation is intended to support the following requirements: + 1) reference to supporting documentation (attribute "documentationRef"); e.g. online + documentation describing the procedure in detail; 2) specification of parameters that + remain fixed within a particular configuration of the procedure (Configuration); a + soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + Schematron validation + + + + + + + + + + + + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. An instance + of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated + state), but it may be a human observer executing a set of instructions, a simulator + or process algorithm. The 'Procedure' should provide sufficient information to interpret + the result of an observation; thus if a sensor is recalibrated or its height above + local ground is changed, a new instance of OM_Process should be created and associated + with subsequent observations from that sensor (at least until the sensor is changed + again). Predominantly we expect the Process instance to be externally published / + defined and 'static' (e.g. perhaps changing less often than once per month due to + amendments to operational protocols etc.). The class 'Process' provides a concrete + implementation of OM_Process (from ISO 19156). The implementation is intended to + support the following requirements: 1) reference to supporting documentation (documentationRef); + e.g. online documentation describing the procedure in detail; 2) specification of + parameters that remain fixed within a particular configuration of the procedure (Configuration); + a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + Reference to an external process definition providing information about relevant documentation + that describes the associated Process. + + + + + + The association role 'parameter' references an instance of NamedValue that specifies + parameters associated with a particular configuration of the procedure (Configuration) + + + + + + The association role 'context' references an instance of MeasurementContext class + that defines resolution and measuring interval for a specific measurand. + + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring + interval [2] for a given physical property in the context of this measurement procedure. + [1] Resolution: smallest change in a quantity being measured that causes a perceptible + change in the corresponding indication (from the 'International vocabulary of metrology' + [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) [2] Measuring + interval: set of values of quantities of the same kind that can be measured by a given + measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' + and 'measuring interval' are specified in. Typically, this will also be the unit + of measure used to specify the measured quantity values. Unless otherwise specified, + this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + + The attribute 'measurand' [1] specifies the physical property that the associated + 'resolution' and 'measuring interval' apply to. The measurand may be sourced from + an external controlled vocabulary, thesaurus or ontology or defined locally. The + measurand may reference a qualified observable property if required. If the measurand + references an observable physical property that serves as the base property for a + qualified observable property, the measurement context is assumed to apply to ALL + the qualified observable properties that reference this base property unless otherwise + stated. For example, observable physical property 'radiance' may be qualified to measure + wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated + with 'radiance' would be inferred to apply to all of these qualified radiance properties. + [1] Measurand: quantity intended to be measured (from the 'International vocabulary + of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits + of property values of the 'measurand' that can measured within this procedure, using + the unit of measure 'uom'. [1] Measuring interval: set of values of quantities of + the same kind that can be measured by a given measuring instrument or measuring system + with specified instrumental uncertainty, under defined conditions (from the 'International + vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' + [1]) in property value of the 'measurand' that is intended to be measured within this + procedure, using the unit of measure 'uom'. This shall be provided as a scaling factor. + For example: <ul> <li>scale = -2 implies a precision of 100 units </li> <li>scale + = -1 implies a precision of 10 units</li> <li>scale = 0 implies a precision of 1 + unit</li> <li>scale = 1 implies a precision of 0.1 units</li> <li>scale = 2 implies + a precision of 0.01 units </li> </ul> etc. [1] Resolution: smallest change in a quantity + being measured that causes a perceptible change in the corresponding indication (from + the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/metce/1.1/metce.xsd b/config/schemas/schema/int/wmo/metce/1.1/metce.xsd new file mode 100644 index 0000000..62bf921 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.1/metce.xsd @@ -0,0 +1,31 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + This Logical Data Model is intended to support the entire scope of WMO concerns: weather, + climate and water. To reflect this scope, the model is named 'Modele pour l'Echange + des informations sur le Temps, le Climat et l'Eau' (METCE). In English, it may also + be known as the ‘METeorological Community Exchange’ model. METCE is intended to provide + conceptual definitions of meteorological phenomena, entities and concepts in order + to underpin semantic interoperability in the weather, climate and water domain. The + «Application Schema» includes: (i) specialisations of OM_Observation, OM_ComplexObservation + and OM_DiscreteCoverageObservation classes (from ISO 19156); (ii) a concrete implementation + of OM_Process (from ISO 19156); (iii) a number of meteorological feature types schemes + thereof; and (iv) some miscellaneous items (e.g. ?enumerations? for specifying intensity + changes). The 'METCE' «Application Schema» will typically be imported to provide + a baseline conceptual model framework upon which community-specific Application Schema + are based. + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.1/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.1/phenomena.xsd new file mode 100644 index 0000000..67eb91f --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.1/phenomena.xsd @@ -0,0 +1,121 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The package 'Meteorological Phenomena' contains «FeatureType» entities that have a + significant role in meteorology; e.g. volcanoes and tropical cyclones. A list of + meteorological phenomena are provided in WMO No. 306 Vol I.2 FM 94 BUFR code-table + 0 08 011 'Meteorological Feature' (see below). It is anticipated that in future releases + the additional meteorological features listed therein will be incorporated. Meteorological + Features (from WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011): - Quasi-stationary + front at the surface - Quasi-stationary front above the surface - Warm front at the + surface - Warm front above the surface - Cold front at the surface - Cold front above + the surface - Occlusion - Instability line - Intertropical front - Convergence line + - Jet stream - Cloud clear - Cloud - Turbulence - Storm - Airframe icing - [Erupting] + Volcano - Atmospherics - Special clouds - Thunderstorm - Tropical cyclone - Mountain + wave - Duststorm - Sandstorm + + + + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum + surface pressure in some cases less than 900 hPa, very violent winds and torrential + rain; sometimes accompanied by thunderstorms. It usually contains a central region, + known as the “eye” of the storm, with a diameter of the order of some tens of kilometres, + and with light winds and more or less lightly clouded sky. WMO No. 306 Vol I.1 code-table + 3704 "Shape and definition of the eye of the tropical cyclone" and WMO No. 306 Vol + I.1 code-table 3790 "Intensity of the tropical cyclone" provide additional candidate + attributes that may be incorporated within this «FeatureType» in subsequent versions + of METCE. + + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + A volcano irrespective of the volcano's current state (e.g. passive or erupting). + Note that the "Global Volcanism Program" provides an online, searchable catalogue + of volcanoes which may assist in identifying the authoritative name for a given volcano + feature [http://www.volcano.si.edu/world/]. (informative) + + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + A volcano that is currently erupting, or has recently erupted, that is the source + of volcanic ash or other significant meteorological phenomena described in operational + weather reports. + + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.1/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.1/procedure.xsd new file mode 100644 index 0000000..09af9e7 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.1/procedure.xsd @@ -0,0 +1,232 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The 'Procedure' package provides a concrete implementation of the abstract OM_Process + class (from ISO 19156). The implementation is intended to support the following requirements: + 1) reference to supporting documentation (attribute "documentationRef"); e.g. online + documentation describing the procedure in detail; 2) specification of parameters that + remain fixed within a particular configuration of the procedure (Configuration); a + soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + Schematron validation + + + + + + + + + + + + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is + used to define the process(es) involved in generating an observation. An instance + of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated + state), but it may be a human observer executing a set of instructions, a simulator + or process algorithm. The 'Procedure' should provide sufficient information to interpret + the result of an observation; thus if a sensor is recalibrated or its height above + local ground is changed, a new instance of OM_Process should be created and associated + with subsequent observations from that sensor (at least until the sensor is changed + again). Predominantly we expect the Process instance to be externally published / + defined and 'static' (e.g. perhaps changing less often than once per month due to + amendments to operational protocols etc.). The class 'Process' provides a concrete + implementation of OM_Process (from ISO 19156). The implementation is intended to + support the following requirements: 1) reference to supporting documentation (documentationRef); + e.g. online documentation describing the procedure in detail; 2) specification of + parameters that remain fixed within a particular configuration of the procedure (Configuration); + a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; + 3) specification of the resolution [1] with which each observed physical phenomenon + is measured; and 4) specification of the measuring interval [2] of the instrument + or sensor for each observed physical phenomenon. [1] Resolution: smallest change + in a quantity being measured that causes a perceptible change in the corresponding + indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + [2] Measuring interval: set of values of quantities of the same kind that can be measured + by a given measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + Reference to an external process definition providing information about relevant documentation + that describes the associated Process. + + + + + + The association role 'parameter' references an instance of NamedValue that specifies + parameters associated with a particular configuration of the procedure (Configuration) + + + + + + The association role 'context' references an instance of MeasurementContext class + that defines resolution and measuring interval for a specific measurand. + + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring + interval [2] for a given physical property in the context of this measurement procedure. + [1] Resolution: smallest change in a quantity being measured that causes a perceptible + change in the corresponding indication (from the 'International vocabulary of metrology' + [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) [2] Measuring + interval: set of values of quantities of the same kind that can be measured by a given + measuring instrument or measuring system with specified instrumental uncertainty, + under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + MeasurementContext: unitOfMeasure shall be appropriate for measurand + + + + + MeasurementContext: if measuringInterval or resolutionScale or both are given then + uom must also be provided + + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' + and 'measuring interval' are specified in. Typically, this will also be the unit + of measure used to specify the measured quantity values. Unless otherwise specified, + this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + + The attribute 'measurand' [1] specifies the physical property that the associated + 'resolution' and 'measuring interval' apply to. The measurand may be sourced from + an external controlled vocabulary, thesaurus or ontology or defined locally. The + measurand may reference a qualified observable property if required. If the measurand + references an observable physical property that serves as the base property for a + qualified observable property, the measurement context is assumed to apply to ALL + the qualified observable properties that reference this base property unless otherwise + stated. For example, observable physical property 'radiance' may be qualified to measure + wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated + with 'radiance' would be inferred to apply to all of these qualified radiance properties. + [1] Measurand: quantity intended to be measured (from the 'International vocabulary + of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits + of property values of the 'measurand' that can measured within this procedure, using + the unit of measure 'uom'. [1] Measuring interval: set of values of quantities of + the same kind that can be measured by a given measuring instrument or measuring system + with specified instrumental uncertainty, under defined conditions (from the 'International + vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' + [1]) in property value of the 'measurand' that is intended to be measured within this + procedure, using the unit of measure 'uom'. This shall be provided as a scaling factor. + For example: <ul> <li>scale = -2 implies a precision of 100 units </li> <li>scale + = -1 implies a precision of 10 units</li> <li>scale = 0 implies a precision of 1 + unit</li> <li>scale = 1 implies a precision of 0.1 units</li> <li>scale = 2 implies + a precision of 0.01 units </li> </ul> etc. [1] Resolution: smallest change in a quantity + being measured that causes a perceptible change in the corresponding indication (from + the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2/gmlmetce.xsd b/config/schemas/schema/int/wmo/metce/1.2/gmlmetce.xsd new file mode 100644 index 0000000..cacd748 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2/gmlmetce.xsd @@ -0,0 +1,506 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:PointPropertyType,gml:CodeType,gml:AbstractGML,gml:AbstractGMLType,gml:UnitOfMeasureType,gml:AbstractObject, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + + + + + + + + + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2/metce.xsd b/config/schemas/schema/int/wmo/metce/1.2/metce.xsd new file mode 100644 index 0000000..3b7d12f --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2/metce.xsd @@ -0,0 +1,20 @@ + + + + + + + This Logical Data Model is intended to support the entire scope of WMO concerns: weather, climate and water. To reflect this scope, the model is named 'Modele pour l'Echange des informations sur le Temps, le Climat et l'Eau' (METCE). In English, it may also be known as the "METeorological Community Exchange" model. + +METCE is intended to provide conceptual definitions of meteorological phenomena, entities and concepts in order to underpin semantic interoperability in the weather, climate and water domain. + +The <<Application Schema>> includes: (i) a concrete implementation of OM_Process (from ISO 19156); (ii) a number of meteorological feature types schemes thereof; and (iii) some miscellaneous items (e.g. <<Enumerations>> for specifying intensity changes). + +The 'METCE' <<Application Schema>> will typically be imported to provide a baseline conceptual model framework upon which community-specific Application Schema are based. + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + gmlmetce.xsd + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.2/phenomena.xsd new file mode 100644 index 0000000..92d52dc --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2/phenomena.xsd @@ -0,0 +1,121 @@ + + + + + The package 'Meteorological Phenomena' contains «FeatureType» entities that have a significant role in meteorology; e.g. volcanoes and tropical cyclones. + +A list of meteorological phenomena are provided in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011 'Meteorological Feature' (see below). It is anticipated that in future releases the additional meteorological features listed therein will be incorporated. + +Meteorological Features (from WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011): +- Quasi-stationary front at the surface +- Quasi-stationary front above the surface +- Warm front at the surface +- Warm front above the surface +- Cold front at the surface +- Cold front above the surface +- Occlusion +- Instability line +- Intertropical front +- Convergence line +- Jet stream +- Cloud clear +- Cloud +- Turbulence +- Storm +- Airframe icing +- [Erupting] Volcano +- Atmospherics +- Special clouds +- Thunderstorm +- Tropical cyclone +- Mountain wave +- Duststorm +- Sandstorm + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum surface pressure in some cases less than 900 hPa, very violent winds and torrential rain; sometimes accompanied by thunderstorms. It usually contains a central region, known as the “eye” of the storm, with a diameter of the order of some tens of kilometres, and with light winds and more or less lightly clouded sky. + +WMO No. 306 Vol I.1 code-table 3704 "Shape and definition of the eye of the tropical cyclone" and WMO No. 306 Vol I.1 code-table 3790 "Intensity of the tropical cyclone" provide additional candidate attributes that may be incorporated within this «FeatureType» in subsequent versions of METCE. + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + A volcano irrespective of the volcano's current state (e.g. passive or erupting). + +Note that the "Global Volcanism Program" provides an online, searchable catalogue of volcanoes which may assist in identifying the authoritative name for a given volcano feature [http://www.volcano.si.edu/world/]. (informative) + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + A volcano that is currently erupting, or has recently erupted, that is the source of volcanic ash or other significant meteorological phenomena described in operational weather reports. + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.2/procedure.xsd new file mode 100644 index 0000000..843ab2f --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2/procedure.xsd @@ -0,0 +1,180 @@ + + + + + + + The 'Procedure' package provides a concrete implementation of the abstract OM_Process class (from ISO 19156). + +The implementation is intended to support the following requirements: +1) reference to supporting documentation (attribute "documentationRef"); e.g. online documentation describing the procedure in detail; +2) specification of parameters that remain fixed within a particular configuration of the procedure (Configuration); a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; +3) specification of the resolution [1] with which each observed physical phenomenon is measured; and +4) specification of the measuring interval [2] of the instrument or sensor for each observed physical phenomenon. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is used to define the process(es) involved in generating an observation. An instance of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated state), but it may be a human observer executing a set of instructions, a simulator or process algorithm. The 'Procedure' should provide sufficient information to interpret the result of an observation; thus if a sensor is recalibrated or its height above local ground is changed, a new instance of OM_Process should be created and associated with subsequent observations from that sensor (at least until the sensor is changed again). + +Predominantly we expect the Process instance to be externally published / defined and 'static' (e.g. perhaps changing less often than once per month due to amendments to operational protocols etc.). + +The class 'Process' provides a concrete implementation of OM_Process (from ISO 19156). + +The implementation is intended to support the following requirements: +1) reference to supporting documentation (documentationRef); e.g. online documentation describing the procedure in detail; +2) specification of parameters that remain fixed within a particular configuration of the procedure (Configuration); a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; +3) specification of the resolution [1] with which each observed physical phenomenon is measured; and +4) specification of the measuring interval [2] of the instrument or sensor for each observed physical phenomenon. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + Reference to an external process definition providing information about relevant documentation that describes the associated Process. + + + + + The association role 'parameter' references an instance of NamedValue that specifies parameters associated with a particular configuration of the procedure (Configuration) + + + + + The association role 'context' references an instance of MeasurementContext class that defines resolution and measuring interval for a specific measurand. + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring interval [2] for a given physical property in the context of this measurement procedure. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' and 'measuring interval' are specified in. + +Typically, this will also be the unit of measure used to specify the measured quantity values. Unless otherwise specified, this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + The attribute 'measurand' [1] specifies the physical property that the associated 'resolution' and 'measuring interval' apply to. + +The measurand may be sourced from an external controlled vocabulary, thesaurus or ontology or defined locally. + +The measurand may reference a qualified observable property if required. + +If the measurand references an observable physical property that serves as the base property for a qualified observable property, the measurement context is assumed to apply to ALL the qualified observable properties that reference this base property unless otherwise stated. For example, observable physical property 'radiance' may be qualified to measure wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated with 'radiance' would be inferred to apply to all of these qualified radiance properties. + +[1] Measurand: quantity intended to be measured (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + + + + + + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits of property values of the 'measurand' that can measured within this procedure, using the unit of measure 'uom'. + +[1] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' [1]) in property value of the 'measurand' that is intended to be measured within this procedure, using the unit of measure 'uom'. + +This shall be provided as a scaling factor. + +For example: + + - scale = -2 implies a precision of 100 units + - scale = -1 implies a precision of 10 units + - scale = 0 implies a precision of 1 unit + - scale = 1 implies a precision of 0.1 units + - scale = 2 implies a precision of 0.01 units + +etc. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also known as a property value interval). + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2RC1/gmlmetce.xsd b/config/schemas/schema/int/wmo/metce/1.2RC1/gmlmetce.xsd new file mode 100644 index 0000000..cacd748 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2RC1/gmlmetce.xsd @@ -0,0 +1,506 @@ + + + + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:PointPropertyType,gml:CodeType,gml:AbstractGML,gml:AbstractGMLType,gml:UnitOfMeasureType,gml:AbstractObject, written by gmlSubset.xslt. + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + + + + + + + deprecated + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + A type for a list of values of the respective simple type. + + + + + + + + deprecated + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + deprecated + + + + + deprecated + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + + + + + + + + + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2RC1/metce.xsd b/config/schemas/schema/int/wmo/metce/1.2RC1/metce.xsd new file mode 100644 index 0000000..8518d6a --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2RC1/metce.xsd @@ -0,0 +1,19 @@ + + + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + This Logical Data Model is intended to support the entire scope of WMO concerns: weather, climate and water. To reflect this scope, the model is named 'Modele pour l'Echange des informations sur le Temps, le Climat et l'Eau' (METCE). In English, it may also be known as the ‘METeorological Community Exchange?model. + +METCE is intended to provide conceptual definitions of meteorological phenomena, entities and concepts in order to underpin semantic interoperability in the weather, climate and water domain. + +The «Application Schema?includes: (i) a concrete implementation of OM_Process (from ISO 19156); (ii) a number of meteorological feature types schemes thereof; and (iv) some miscellaneous items (e.g. ?enumerations? for specifying intensity changes). + +The 'METCE' «Application Schema?will typically be imported to provide a baseline conceptual model framework upon which community-specific Application Schema are based. + + gmlmetce.xsd + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2RC1/phenomena.xsd b/config/schemas/schema/int/wmo/metce/1.2RC1/phenomena.xsd new file mode 100644 index 0000000..c2b20d8 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2RC1/phenomena.xsd @@ -0,0 +1,120 @@ + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + The package 'Meteorological Phenomena' contains «FeatureType» entities that have a significant role in meteorology; e.g. volcanoes and tropical cyclones. + +A list of meteorological phenomena are provided in WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011 'Meteorological Feature' (see below). It is anticipated that in future releases the additional meteorological features listed therein will be incorporated. + +Meteorological Features (from WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 08 011): +- Quasi-stationary front at the surface +- Quasi-stationary front above the surface +- Warm front at the surface +- Warm front above the surface +- Cold front at the surface +- Cold front above the surface +- Occlusion +- Instability line +- Intertropical front +- Convergence line +- Jet stream +- Cloud clear +- Cloud +- Turbulence +- Storm +- Airframe icing +- [Erupting] Volcano +- Atmospherics +- Special clouds +- Thunderstorm +- Tropical cyclone +- Mountain wave +- Duststorm +- Sandstorm + + + + Cyclone of tropical origin of small diameter (some hundreds of kilometres) with minimum surface pressure in some cases less than 900 hPa, very violent winds and torrential rain; sometimes accompanied by thunderstorms. It usually contains a central region, known as the “eye” of the storm, with a diameter of the order of some tens of kilometres, and with light winds and more or less lightly clouded sky. + +WMO No. 306 Vol I.1 code-table 3704 "Shape and definition of the eye of the tropical cyclone" and WMO No. 306 Vol I.1 code-table 3790 "Intensity of the tropical cyclone" provide additional candidate attributes that may be incorporated within this «FeatureType» in subsequent versions of METCE. + + + + + + + + + Name of tropical cyclone. + + + + + + + + + + + + + + + + A volcano irrespective of the volcano's current state (e.g. passive or erupting). + +Note that the "Global Volcanism Program" provides an online, searchable catalogue of volcanoes which may assist in identifying the authoritative name for a given volcano feature [http://www.volcano.si.edu/world/]. (informative) + + + + + + + + + The name of the volcano. + + + + + The position of the volcano. + + + + + + + + + + + + + + + + A volcano that is currently erupting, or has recently erupted, that is the source of volcanic ash or other significant meteorological phenomena described in operational weather reports. + + + + + + + + + The date of eruption for the volcano. + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/metce/1.2RC1/procedure.xsd b/config/schemas/schema/int/wmo/metce/1.2RC1/procedure.xsd new file mode 100644 index 0000000..ac5cf04 --- /dev/null +++ b/config/schemas/schema/int/wmo/metce/1.2RC1/procedure.xsd @@ -0,0 +1,161 @@ + + + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + The 'Procedure' package provides a concrete implementation of the abstract OM_Process class (from ISO 19156). + +The implementation is intended to support the following requirements: +1) reference to supporting documentation (attribute "documentationRef"); e.g. online documentation describing the procedure in detail; +2) specification of parameters that remain fixed within a particular configuration of the procedure (Configuration); a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; +3) specification of the resolution [1] with which each observed physical phenomenon is measured; and +4) specification of the measuring interval [2] of the instrument or sensor for each observed physical phenomenon. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + Class 'OM_Process' (related to OM_Observation via the 'Procedure' Association) is used to define the process(es) involved in generating an observation. An instance of OM_Process is often an instrument or sensor (perhaps even a sensor in a given calibrated state), but it may be a human observer executing a set of instructions, a simulator or process algorithm. The 'Procedure' should provide sufficient information to interpret the result of an observation; thus if a sensor is recalibrated or its height above local ground is changed, a new instance of OM_Process should be created and associated with subsequent observations from that sensor (at least until the sensor is changed again). + +Predominantly we expect the Process instance to be externally published / defined and 'static' (e.g. perhaps changing less often than once per month due to amendments to operational protocols etc.). + +The class 'Process' provides a concrete implementation of OM_Process (from ISO 19156). + +The implementation is intended to support the following requirements: +1) reference to supporting documentation (documentationRef); e.g. online documentation describing the procedure in detail; +2) specification of parameters that remain fixed within a particular configuration of the procedure (Configuration); a soft-typed approach is used here following the pattern adopted for OM_Observation/parameter; +3) specification of the resolution [1] with which each observed physical phenomenon is measured; and +4) specification of the measuring interval [2] of the instrument or sensor for each observed physical phenomenon. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + Reference to an external process definition providing information about relevant documentation that describes the associated Process. + + + + + The association role 'parameter' references an instance of NamedValue that specifies parameters associated with a particular configuration of the procedure (Configuration) + + + + + The association role 'context' references an instance of MeasurementContext class that defines resolution and measuring interval for a specific measurand. + + + + + + + + + + + + + + + + Instances of the class 'MeasurementContext' specify the resolution [1] and measuring interval [2] for a given physical property in the context of this measurement procedure. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) +[2] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + The attribute 'uom' specifies the unit of measure that the values of 'resolution' and 'measuring interval' are specified in. + +Typically, this will also be the unit of measure used to specify the measured quantity values. Unless otherwise specified, this unit of measure can be assumed to be the default unit of measure for this measurand. + + + + + The attribute 'measurand' [1] specifies the physical property that the associated 'resolution' and 'measuring interval' apply to. + +The measurand may be sourced from an external controlled vocabulary, thesaurus or ontology or defined locally. + +The measurand may reference a qualified observable property if required. + +If the measurand references an observable physical property that serves as the base property for a qualified observable property, the measurement context is assumed to apply to ALL the qualified observable properties that reference this base property unless otherwise stated. For example, observable physical property 'radiance' may be qualified to measure wavelength bands 50-100nm, 100-200nm, 200-500nm etc. A measurement context associated with 'radiance' would be inferred to apply to all of these qualified radiance properties. + +[1] Measurand: quantity intended to be measured (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf] + + + + + The attribute 'measuringInterval' [1] specifies the extreme lower and upper limits of property values of the 'measurand' that can measured within this procedure, using the unit of measure 'uom'. + +[1] Measuring interval: set of values of quantities of the same kind that can be measured by a given measuring instrument or measuring system with specified instrumental uncertainty, under defined conditions (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + The attribute 'resolutionScale' specifies the smallest change (e.g. the 'resolution' [1]) in property value of the 'measurand' that is intended to be measured within this procedure, using the unit of measure 'uom'. + +This shall be provided as a scaling factor. + +For example: + + - scale = -2 implies a precision of 100 units + - scale = -1 implies a precision of 10 units + - scale = 0 implies a precision of 1 unit + - scale = 1 implies a precision of 0.1 units + - scale = 2 implies a precision of 0.01 units + +etc. + +[1] Resolution: smallest change in a quantity being measured that causes a perceptible change in the corresponding indication (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also known as a property value interval). + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.0/observable-property.xsd b/config/schemas/schema/int/wmo/opm/1.0/observable-property.xsd new file mode 100644 index 0000000..90c6926 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0/observable-property.xsd @@ -0,0 +1,500 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + «Leaf» package for the 'Observable Property Model' + + Schematron validation + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. This + abstract class enables either a single physical property to be specified or a composite + observable property that aggregates a set of physical properties for a given observation + context. In many cases, the observed physical property will be sourced from a controlled + vocabulary, thesaurus or ontology. [1] Quantity: property of a phenomenon, body, + or substance, where the property has a magnitude that can be expressed as a number + and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + The attribute 'label' provides the primary human-readable label describing the observable + physical property. + + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe + the physical property. + + + + + + The attribute 'notation' provides a notation or code-value that is used to identify + the physical property within a given context. + + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty + instances can be aggregated. + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + + + + + + + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. In + many cases, the observed physical property will be sourced from a controlled vocabulary, + thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in + a well-defined ontology. As such, the attributes of ObservableProperty have been elided; + we simply need to assert that the entity has compatible semantics with the ObservableProperty + class defined herein. [1] Quantity: property of a phenomenon, body, or substance, + where the property has a magnitude that can be expressed as a number and a reference + (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property + that is qualified or constrained within a given measurement context. Qualification + of the observed physical property may take several forms: - a specific unit of measure; + - a statistical operator (e.g. maximum) plus the aggregation context that the statistical + operator applies to; or - a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this + physical property. + + + + + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained + according to specific values of the constraining property. For example, the base property + 'air temperature' may be constrained such that we are concerned only with the air + temperature at 2.0 metres above local ground level (e.g. a screen temperature). In + this example, 'height above local ground level' is the constraint property. + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect + to a base property; e.g. maximum UV index over a 3-hour period. The class 'StatisticalQualifier' + defines the type of statistical function plus the mechanism that is used to aggregate + the base property values to create the statistical summary: length, area, volume, + duration or other. Statistical summary properties may be defined by chaining a set + of statistical operations together. For example: mean daily maximum temperature over + a month period comprises two statistical operations with respect to the base property + 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month + duration. + + + + + + + + The attribute 'description' provides a textual description of the statistical qualification + applied to the base observable physical property. + + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the + statistical function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, + length, area or volume) over which the statistical function is applied in order to + determine the statistical summary; e.g. prevailing visibility is [approximately] defined + as a mean visibility in each horizontal direction. + + + + + + The attribute 'statisticalFunction' defines the type of statistical function that + is applied to the base observed property values in order to generate the statistical + summary. + + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. + For example, in aviation the only clouds of significance for terminal aerodrome operations + are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical + property 'cloud base [height]' may be constrained such that it is applicable only + to clouds of a given type. In this example, a single instance of CategoryConstraint + would be defined referencing both cloud types (cumulonimbus and towering cumulus); + 'cloud type' is the constraint property. + + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained + according to a range of values of the constraining property. For example, the base + property 'radiance' may be constrained such that we are concerned only with the radiance + between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint + property. + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The association role 'value' references an instance of the RangeBounds class that + specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical + property in a given measurement context to be specified. + + + + + + + + The attribute 'description' provides a textual description of the constraint applied + to the base observable physical property. + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + + + + + «Enumeration» 'ComparisonOperator' defines the set mathematical operators that may + be used to compare numerical values; not equal, less than, less than or equal, equal, + greater than or equal and greater than. + + + + + + Comparison operator: "not equal to" + + + + + Comparison operator: "less than" + + + + + Comparison operator: "less than or equal to" + + + + + Comparison operator: "equal to" + + + + + Comparison operator: "greater than or equal to" + + + + + Comparison operator: "greater than" + + + + + + + + http://codes.wmo.int/grib2/codeflag/4.10 + any + + The «CodeList» class 'StatisticalFunctionCode' specifies the type of statistical function + that is applied to the base observable property to define the statistical summary; + e.g. maximum air temperature. Note that WMO provides two code-tables listing statistical + operators: - WMO No. 306 Vol I.2 Part B FM 92 GRIB code-table 4.10 'Type of statistical + processing'; and - WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 023 'First-order + statistics' The GRIB2 code-table is defined as the 'recommended' vocabulary for this + «CodeList» class but lacks some of the necessary terms. For example, the GRIB code-table + includes 'Average' but does not include 'Mean', 'Mode' or 'Median' (which can be found + in the BUFR code-table). However, the BUFR code-table is _NOT_ chosen because 'Accumulation' + is entirely missing. Given that 'extensibility' is set to 'any', authors are free + to refer to their preferred 'statistical operator' vocabulary. The GRIB code-table + is only a recommendation. + + vocabulary: http://codes.wmo.int/grib2/codeflag/4.10 + extensibility: any + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/opm/1.0/opm.xsd b/config/schemas/schema/int/wmo/opm/1.0/opm.xsd new file mode 100644 index 0000000..b22c5ae --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0/opm.xsd @@ -0,0 +1,50 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The 'Observable Property' model enables observed physical properties (also termed + "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + to be aggregated into composite properties and for any qualification or constraint + relating to those observed physical properties to be explicitly described. A data + publisher may need to use the Observed Property Model to explicitly define any qualification + or constraint applied to the observed property, or, where the observation results + in the evaluation of multiple properties, to explicitly define each of those individual + physical properties. Usage: The Observable Property Model may be used to specify + constraint or qualification of a physical quantity (or set of physical quantities) + within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter + Attribute (from ISO 19156, type Class "NamedValue"): - name: http://def.wmo.int/opm/2013/observable-property#property + [1] - parameter: instance of Class "AbstractObservableProperty" or concrete subclass + thereof [2] Note that Class "OM_Observation" asserts a constraint such that the value + of the parameter/NamedValue/name Attribute shall not occur more than once within a + given instance of Class OM_Observation. In situations where multiple physical quantities + are observed or measured, the value of the associated parameter/NamedValue/value Attribute + may be specified as an instance of Class "CompositeObservableProperty" thus allowing + a set of observable properties to be specified. Also note that, whilst Class "OM_Observation" + provides Attribute "observedProperty" for specifying the (physical) property observed + or measured the cardinality of this Attribute is one (e.g. only a single property + can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised + as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" + in-line within the data. Whilst it is permissible to make a local reference to an + instance of Class "CompositeObservableProperty" defined elsewhere within the data, + it is preferable to reference an external definition. The reason for this is that + the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service + as a key on which data is indexed; use of internal references are likely to inhibit + discovery and retrieval of data. Alternatively, if the constraint or qualification + of the physical quantity (or set of physical quantities) is consistent within a repeatable + procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter + Attribute (from "«Application Schema» METCE", type Class "NamedValue"). Note that + in the case of Class "Process", there is no constraint on the number of occurences + of a given parameter name. However, recommended practice indicates the use of an instance + of Class "CompositeObservableProperty" where a set of observable properties are to + be specified. [1] Association Role "property" is specified to have type Class "AbstractObservableProperty" + [2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", + "QualifiedObservableProperty" and "CompositeObservableProperty". + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.0RC1/observableProperty.xsd b/config/schemas/schema/int/wmo/opm/1.0RC1/observableProperty.xsd new file mode 100644 index 0000000..7ebc500 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0RC1/observableProperty.xsd @@ -0,0 +1,455 @@ + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. This + abstract class enables either a single physical property to be specified or a composite + observable property that aggregates a set of physical properties for a given observation + context. In many cases, the observed physical property will be sourced from a controlled + vocabulary, thesaurus or ontology. [1] Quantity: property of a phenomenon, body, + or substance, where the property has a magnitude that can be expressed as a number + and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe + the physical property. + + + + + + The attribute 'label' provides the primary human-readable label describing the observable + physical property. + + + + + + The attribute 'notation' provides a notation or code-value that is used to identify + the physical property within a given context. + + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty + instances can be aggregated. + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + + + + + + + + The number of observed physical properties aggregated within this composite. + + + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. In + many cases, the observed physical property will be sourced from a controlled vocabulary, + thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in + a well-defined ontology. As such, the attributes of ObservableProperty have been elided; + we simply need to assert that the entity has compatible semantics with the ObservableProperty + class defined herein. [1] Quantity: property of a phenomenon, body, or substance, + where the property has a magnitude that can be expressed as a number and a reference + (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property + that is qualified or constrained within a given measurement context. Qualification + of the observed physical property may take several forms: - a specific unit of measure; + - a statistical operator (e.g. maximum) plus the aggregation context that the statistical + operator applies to; or - a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + QualifiedObservableProperty: [missing message] + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this + physical property. + + + + + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained + according to specific values of the constraining property. For example, the base property + 'air temperature' may be constrained such that we are concerned only with the air + temperature at 2.0 metres above local ground level (e.g. a screen temperature). In + this example, 'height above local ground level' is the constraint property. + + + + + ScalarConstraint: [missing message] + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect + to a base property; e.g. maximum UV index over a 3-hour period. The class 'StatisticalQualifier' + defines the type of statistical function plus the mechanism that is used to aggregate + the base property values to create the statistical summary: length, area, volume, + duration or other. Statistical summary properties may be defined by chaining a set + of statistical operations together. For example: mean daily maximum temperature over + a month period comprises two statistical operations with respect to the base property + 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month + duration. + + + + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the + statistical function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'description' provides a textual description of the statistical qualification + applied to the base observable physical property. + + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, + length, area or volume) over which the statistical function is applied in order to + determine the statistical summary; e.g. prevailing visibility is [approximately] defined + as a mean visibility in each horizontal direction. + + + + + + The attribute 'statisticalFunction' defines the type of statistical function that + is applied to the base observed property values in order to generate the statistical + summary. + + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. + For example, in aviation the only clouds of significance for terminal aerodrome operations + are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical + property 'cloud base [height]' may be constrained such that it is applicable only + to clouds of a given type. In this example, a single instance of CategoryConstraint + would be defined referencing both cloud types (cumulonimbus and towering cumulus); + 'cloud type' is the constraint property. + + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained + according to a range of values of the constraining property. For example, the base + property 'radiance' may be constrained such that we are concerned only with the radiance + between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint + property. + + + + + RangeConstraint: [missing message] + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The association role 'value' references an instance of the RangeBounds class that + specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical + property in a given measurement context to be specified. + + + + + + + + The attribute 'description' provides a textual description of the constraint applied + to the base observable physical property. + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + + + + + + + + + + http://data.wmo.int/def/grib2/codeflag/4.10 + any + + The «CodeList» class 'StatisticalFunctionCode' specifies the type of statistical function + that is applied to the base observable property to define the statistical summary; + e.g. <u>maximum </u>air temperature. Note that WMO provides two code-tables listing + statistical operators: - BUFR code-table 0 08 023 'First-order statistics'; and - + GRIB2 code-table 4.10 'Type of statistical processing' The GRIB2 code-table is defined + as the 'recommended' vocabulary for this &lt;CodeList&gt; class but lacks some of + the necessary terms. For example, the GRIB2 code-table includes 'Average' but does + not include 'Mean', 'Mode' or 'Median' (which can be found in the BUFR code-table). + However, the BUFR code-table is _NOT_ chosen because 'Accumulation' is entirely missing! + Given that 'extensibility' is set to 'any', authors are free to refer to their preferred + 'statistical operator' vocabulary. The GRIB2 code-table is only a recommendation. + + + + + + + + + + Schematron validation + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/opm/1.0RC1/opm.xsd b/config/schemas/schema/int/wmo/opm/1.0RC1/opm.xsd new file mode 100644 index 0000000..d731235 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0RC1/opm.xsd @@ -0,0 +1,37 @@ + + + + The 'Observable Property' model enables observed physical properties to be aggregated + into composite properties and for any qualification or constraint relating to the + observed physical properties to be explicitly described. A data publisher may need + to use the Observed Property model to explicitly define any qualification or constraint + applied to the observed property, or, where the observation results in the evaluation + of multiple properties, to explicitly define each of those individual physical properties. + OM_Observation/parameter can be used to specify the ObservableProperty via the soft-typed + NamedValue class. The appropriate semantics are found in the GF_AssociationRole 'property' + within the Observable Property model; the valueType is specified as AbstractObservableProperty + enabling an instance of either CompositeObservableProperty -OR- ObservableProperty + to be referenced. NamedValue/name is specified as Type 'GenericName'. To enable + software systems to identify the ObservedProperty entities when parsing the observation, + 'name' must be specified consistently. Assuming that the Observed Property model + is published within a Feature Type Catalogue as part of WMO METCE as an instance of + FC_AssociationRole, GF_AssociationRole 'property' will be identified with the HTTP + URI http://data.wmo.int/def/observable-property/property. NamedValue/value is specified + as Type 'Any'. In this case, 'value' shall be defined as either of the concrete subclasses + of AbstractObservableProperty, conforming to the semantics of GF_AssociationRole 'property'. + Example: &lt;parameter&gt; &lt;NamedValue&gt; &lt;name&gt; http://data.wmo.int/def/observable-property/property + &lt;/name&gt; &lt;value&gt; &lt;QualifiedObservableProperty&gt; + &lt;label&gt; Maximum UV Index measured over previous 3-hours &lt;/label&gt; + &lt;notation&gt; maxUVIndex_3hr &lt;/notation&gt; &lt;baseProperty + xlink:href="http://data.wmo.int/def/quantities/UVIndex" xlink:title="UV Index" /&gt; + &lt;qualifier&gt; &lt;StatisticalQualifier&gt; + &lt;aggregationTimePeriod&gt; PT3H &lt;/aggregationTimePeriod&gt; + &lt;statisticalFunction xlink:href="http://data.wmo.int/def/bufr-codeflag/0-08-023_2" + xlink:title="Maximum" /&gt; &lt;/StatisticalQualifier&gt; + &lt;/qualifier&gt; &lt;/QualifiedObservableProperty&gt; &lt;/value&gt; + &lt;/NamedValue&gt; &lt;/parameter&gt; + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/opm/1.0RC2/observable-property.xsd b/config/schemas/schema/int/wmo/opm/1.0RC2/observable-property.xsd new file mode 100644 index 0000000..f0a19d3 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0RC2/observable-property.xsd @@ -0,0 +1,492 @@ + + + + ?Leaf? package for the 'Observable Property Model' + + Schematron validation + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. This + abstract class enables either a single physical property to be specified or a composite + observable property that aggregates a set of physical properties for a given observation + context. In many cases, the observed physical property will be sourced from a controlled + vocabulary, thesaurus or ontology. [1] Quantity: property of a phenomenon, body, + or substance, where the property has a magnitude that can be expressed as a number + and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + The attribute 'label' provides the primary human-readable label describing the observable + physical property. + + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe + the physical property. + + + + + + The attribute 'notation' provides a notation or code-value that is used to identify + the physical property within a given context. + + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty + instances can be aggregated. + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + + + + + + + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. In + many cases, the observed physical property will be sourced from a controlled vocabulary, + thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in + a well-defined ontology. As such, the attributes of ObservableProperty have been elided; + we simply need to assert that the entity has compatible semantics with the ObservableProperty + class defined herein. [1] Quantity: property of a phenomenon, body, or substance, + where the property has a magnitude that can be expressed as a number and a reference + (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property + that is qualified or constrained within a given measurement context. Qualification + of the observed physical property may take several forms: - a specific unit of measure; + - a statistical operator (e.g. maximum) plus the aggregation context that the statistical + operator applies to; or - a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this + physical property. + + + + + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained + according to specific values of the constraining property. For example, the base property + 'air temperature' may be constrained such that we are concerned only with the air + temperature at 2.0 metres above local ground level (e.g. a screen temperature). In + this example, 'height above local ground level' is the constraint property. + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect + to a base property; e.g. maximum UV index over a 3-hour period. The class 'StatisticalQualifier' + defines the type of statistical function plus the mechanism that is used to aggregate + the base property values to create the statistical summary: length, area, volume, + duration or other. Statistical summary properties may be defined by chaining a set + of statistical operations together. For example: mean daily maximum temperature over + a month period comprises two statistical operations with respect to the base property + 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month + duration. + + + + + + + + The attribute 'description' provides a textual description of the statistical qualification + applied to the base observable physical property. + + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the + statistical function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, + length, area or volume) over which the statistical function is applied in order to + determine the statistical summary; e.g. prevailing visibility is [approximately] defined + as a mean visibility in each horizontal direction. + + + + + + The attribute 'statisticalFunction' defines the type of statistical function that + is applied to the base observed property values in order to generate the statistical + summary. + + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. + For example, in aviation the only clouds of significance for terminal aerodrome operations + are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical + property 'cloud base [height]' may be constrained such that it is applicable only + to clouds of a given type. In this example, a single instance of CategoryConstraint + would be defined referencing both cloud types (cumulonimbus and towering cumulus); + 'cloud type' is the constraint property. + + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained + according to a range of values of the constraining property. For example, the base + property 'radiance' may be constrained such that we are concerned only with the radiance + between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint + property. + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The association role 'value' references an instance of the RangeBounds class that + specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical + property in a given measurement context to be specified. + + + + + + + + The attribute 'description' provides a textual description of the constraint applied + to the base observable physical property. + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + + + + + ?Enumeration? 'ComparisonOperator' defines the set mathematical operators that may + be used to compare numerical values; not equal, less than, less than or equal, equal, + greater than or equal and greater than. + + + + + + Comparison operator: "not equal to" + + + + + Comparison operator: "less than" + + + + + Comparison operator: "less than or equal to" + + + + + Comparison operator: "equal to" + + + + + Comparison operator: "greater than or equal to" + + + + + Comparison operator: "greater than" + + + + + + + + http://codes.wmo.int/grib2/codeflag/4.10 + any + + The ?CodeList? class 'StatisticalFunctionCode' specifies the type of statistical function + that is applied to the base observable property to define the statistical summary; + e.g. maximum air temperature. Note that WMO provides two code-tables listing statistical + operators: - WMO No. 306 Vol I.2 Part B FM 92 GRIB code-table 4.10 'Type of statistical + processing'; and - WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 023 'First-order + statistics' The GRIB2 code-table is defined as the 'recommended' vocabulary for this + ?CodeList? class but lacks some of the necessary terms. For example, the GRIB code-table + includes 'Average' but does not include 'Mean', 'Mode' or 'Median' (which can be found + in the BUFR code-table). However, the BUFR code-table is _NOT_ chosen because 'Accumulation' + is entirely missing. Given that 'extensibility' is set to 'any', authors are free + to refer to their preferred 'statistical operator' vocabulary. The GRIB code-table + is only a recommendation. + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/opm/1.0RC2/opm.xsd b/config/schemas/schema/int/wmo/opm/1.0RC2/opm.xsd new file mode 100644 index 0000000..7a2757b --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.0RC2/opm.xsd @@ -0,0 +1,45 @@ + + + + The 'Observable Property' model enables observed physical properties (also termed + "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + to be aggregated into composite properties and for any qualification or constraint + relating to those observed physical properties to be explicitly described. A data + publisher may need to use the Observed Property Model to explicitly define any qualification + or constraint applied to the observed property, or, where the observation results + in the evaluation of multiple properties, to explicitly define each of those individual + physical properties. Usage: The Observable Property Model may be used to specify + constraint or qualification of a physical quantity (or set of physical quantities) + within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter + Attribute (from ISO 19156, type Class "NamedValue"): - name: http://def.wmo.int/opm/2013/observable-property#property + [1] - parameter: instance of Class "AbstractObservableProperty" or concrete subclass + thereof [2] Note that Class "OM_Observation" asserts a constraint such that the value + of the parameter/NamedValue/name Attribute shall not occur more than once within a + given instance of Class OM_Observation. In situations where multiple physical quantities + are observed or measured, the value of the associated parameter/NamedValue/value Attribute + may be specified as an instance of Class "CompositeObservableProperty" thus allowing + a set of observable properties to be specified. Also note that, whilst Class "OM_Observation" + provides Attribute "observedProperty" for specifying the (physical) property observed + or measured the cardinality of this Attribute is one (e.g. only a single property + can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised + as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" + in-line within the data. Whilst it is permissible to make a local reference to an + instance of Class "CompositeObservableProperty" defined elsewhere within the data, + it is preferable to reference an external definition. The reason for this is that + the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service + as a key on which data is indexed; use of internal references are likely to inhibit + discovery and retrieval of data. Alternatively, if the constraint or qualification + of the physical quantity (or set of physical quantities) is consistent within a repeatable + procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter + Attribute (from "?Application Schema? METCE", type Class "NamedValue"). Note that + in the case of Class "Process", there is no constraint on the number of occurences + of a given parameter name. However, recommended practice indicates the use of an instance + of Class "CompositeObservableProperty" where a set of observable properties are to + be specified. [1] Association Role "property" is specified to have type Class "AbstractObservableProperty" + [2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", + "QualifiedObservableProperty" and "CompositeObservableProperty". + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/opm/1.1/observable-property.xsd b/config/schemas/schema/int/wmo/opm/1.1/observable-property.xsd new file mode 100644 index 0000000..3c7e7e2 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.1/observable-property.xsd @@ -0,0 +1,500 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + «Leaf» package for the 'Observable Property Model' + + Schematron validation + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. This + abstract class enables either a single physical property to be specified or a composite + observable property that aggregates a set of physical properties for a given observation + context. In many cases, the observed physical property will be sourced from a controlled + vocabulary, thesaurus or ontology. [1] Quantity: property of a phenomenon, body, + or substance, where the property has a magnitude that can be expressed as a number + and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + The attribute 'label' provides the primary human-readable label describing the observable + physical property. + + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe + the physical property. + + + + + + The attribute 'notation' provides a notation or code-value that is used to identify + the physical property within a given context. + + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty + instances can be aggregated. + + + + + CompositeObservableProperty: Attribute 'count' shall specify the number of observed + physical properties (specified via the 'property' association role) aggregated within + this composite observable property. + + + + + + + + + + + + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this + will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. In + many cases, the observed physical property will be sourced from a controlled vocabulary, + thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in + a well-defined ontology. As such, the attributes of ObservableProperty have been elided; + we simply need to assert that the entity has compatible semantics with the ObservableProperty + class defined herein. [1] Quantity: property of a phenomenon, body, or substance, + where the property has a magnitude that can be expressed as a number and a reference + (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property + that is qualified or constrained within a given measurement context. Qualification + of the observed physical property may take several forms: - a specific unit of measure; + - a statistical operator (e.g. maximum) plus the aggregation context that the statistical + operator applies to; or - a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + QualifiedObservableProperty: unitOfMeasure shall be appropriate for baseProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this + physical property. + + + + + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained + according to specific values of the constraining property. For example, the base property + 'air temperature' may be constrained such that we are concerned only with the air + temperature at 2.0 metres above local ground level (e.g. a screen temperature). In + this example, 'height above local ground level' is the constraint property. + + + + + ScalarConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect + to a base property; e.g. maximum UV index over a 3-hour period. The class 'StatisticalQualifier' + defines the type of statistical function plus the mechanism that is used to aggregate + the base property values to create the statistical summary: length, area, volume, + duration or other. Statistical summary properties may be defined by chaining a set + of statistical operations together. For example: mean daily maximum temperature over + a month period comprises two statistical operations with respect to the base property + 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month + duration. + + + + + + + + The attribute 'description' provides a textual description of the statistical qualification + applied to the base observable physical property. + + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the + statistical function is applied in order to determine the statistical summary. + + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical + function is applied in order to determine the statistical summary. + + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, + length, area or volume) over which the statistical function is applied in order to + determine the statistical summary; e.g. prevailing visibility is [approximately] defined + as a mean visibility in each horizontal direction. + + + + + + The attribute 'statisticalFunction' defines the type of statistical function that + is applied to the base observed property values in order to generate the statistical + summary. + + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. + For example, in aviation the only clouds of significance for terminal aerodrome operations + are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical + property 'cloud base [height]' may be constrained such that it is applicable only + to clouds of a given type. In this example, a single instance of CategoryConstraint + would be defined referencing both cloud types (cumulonimbus and towering cumulus); + 'cloud type' is the constraint property. + + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained + according to a range of values of the constraining property. For example, the base + property 'radiance' may be constrained such that we are concerned only with the radiance + between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint + property. + + + + + RangeConstraint: unitOfMeasure shall be appropriate for constraintProperty + + + + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the + constraint property value. + + + + + + The association role 'value' references an instance of the RangeBounds class that + specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical + property in a given measurement context to be specified. + + + + + + + + The attribute 'description' provides a textual description of the constraint applied + to the base observable physical property. + + + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also + known as a property value interval). + + + + + RangeBounds: The extreme lower limit of the range of interval must be less than the + extreme upper limit. + + + + + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + + + + + «Enumeration» 'ComparisonOperator' defines the set mathematical operators that may + be used to compare numerical values; not equal, less than, less than or equal, equal, + greater than or equal and greater than. + + + + + + Comparison operator: "not equal to" + + + + + Comparison operator: "less than" + + + + + Comparison operator: "less than or equal to" + + + + + Comparison operator: "equal to" + + + + + Comparison operator: "greater than or equal to" + + + + + Comparison operator: "greater than" + + + + + + + + http://codes.wmo.int/grib2/codeflag/4.10 + any + + The «CodeList» class 'StatisticalFunctionCode' specifies the type of statistical function + that is applied to the base observable property to define the statistical summary; + e.g. maximum air temperature. Note that WMO provides two code-tables listing statistical + operators: - WMO No. 306 Vol I.2 Part B FM 92 GRIB code-table 4.10 'Type of statistical + processing'; and - WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 023 'First-order + statistics' The GRIB2 code-table is defined as the 'recommended' vocabulary for this + «CodeList» class but lacks some of the necessary terms. For example, the GRIB code-table + includes 'Average' but does not include 'Mean', 'Mode' or 'Median' (which can be found + in the BUFR code-table). However, the BUFR code-table is _NOT_ chosen because 'Accumulation' + is entirely missing. Given that 'extensibility' is set to 'any', authors are free + to refer to their preferred 'statistical operator' vocabulary. The GRIB code-table + is only a recommendation. + + vocabulary: http://codes.wmo.int/grib2/codeflag/4.10 + extensibility: any + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.1/opm.xsd b/config/schemas/schema/int/wmo/opm/1.1/opm.xsd new file mode 100644 index 0000000..be60af7 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.1/opm.xsd @@ -0,0 +1,50 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + The 'Observable Property' model enables observed physical properties (also termed + "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + to be aggregated into composite properties and for any qualification or constraint + relating to those observed physical properties to be explicitly described. A data + publisher may need to use the Observed Property Model to explicitly define any qualification + or constraint applied to the observed property, or, where the observation results + in the evaluation of multiple properties, to explicitly define each of those individual + physical properties. Usage: The Observable Property Model may be used to specify + constraint or qualification of a physical quantity (or set of physical quantities) + within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter + Attribute (from ISO 19156, type Class "NamedValue"): - name: http://def.wmo.int/opm/2013/observable-property#property + [1] - parameter: instance of Class "AbstractObservableProperty" or concrete subclass + thereof [2] Note that Class "OM_Observation" asserts a constraint such that the value + of the parameter/NamedValue/name Attribute shall not occur more than once within a + given instance of Class OM_Observation. In situations where multiple physical quantities + are observed or measured, the value of the associated parameter/NamedValue/value Attribute + may be specified as an instance of Class "CompositeObservableProperty" thus allowing + a set of observable properties to be specified. Also note that, whilst Class "OM_Observation" + provides Attribute "observedProperty" for specifying the (physical) property observed + or measured the cardinality of this Attribute is one (e.g. only a single property + can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised + as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" + in-line within the data. Whilst it is permissible to make a local reference to an + instance of Class "CompositeObservableProperty" defined elsewhere within the data, + it is preferable to reference an external definition. The reason for this is that + the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service + as a key on which data is indexed; use of internal references are likely to inhibit + discovery and retrieval of data. Alternatively, if the constraint or qualification + of the physical quantity (or set of physical quantities) is consistent within a repeatable + procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter + Attribute (from "«Application Schema» METCE", type Class "NamedValue"). Note that + in the case of Class "Process", there is no constraint on the number of occurences + of a given parameter name. However, recommended practice indicates the use of an instance + of Class "CompositeObservableProperty" where a set of observable properties are to + be specified. [1] Association Role "property" is specified to have type Class "AbstractObservableProperty" + [2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", + "QualifiedObservableProperty" and "CompositeObservableProperty". + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2/gmlopm.xsd b/config/schemas/schema/int/wmo/opm/1.2/gmlopm.xsd new file mode 100644 index 0000000..7673d11 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2/gmlopm.xsd @@ -0,0 +1,312 @@ + + + + GML Subset schema for gml:AbstractGML,gml:AbstractGMLType,gml:CodeType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:UnitOfMeasureType,gml:AbstractObject,gml:AreaType,gml:LengthType,gml:VolumeType,gml:AssociationRoleType,gml:ReferenceType, written by gmlSubset.xslt. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2/observable-property.xsd b/config/schemas/schema/int/wmo/opm/1.2/observable-property.xsd new file mode 100644 index 0000000..ea58a45 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2/observable-property.xsd @@ -0,0 +1,420 @@ + + + + + «Leaf» package for the 'Observable Property Model' + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + + An 'observable property' is a physical property that can be observed. Typically, this will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. + +This abstract class enables either a single physical property to be specified or a composite observable property that aggregates a set of physical properties for a given observation context. + +In many cases, the observed physical property will be sourced from a controlled vocabulary, thesaurus or ontology. + +[1] Quantity: property of a phenomenon, body, or substance, where the property has a magnitude that can be expressed as a number and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + The attribute 'label' provides the primary human-readable label describing the observable physical property. + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe the physical property. + + + + + The attribute 'notation' provides a notation or code-value that is used to identify the physical property within a given context. + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty instances can be aggregated. + + + + + + + + + The association role 'property' references an observable physical property. + +The observable physical property may be defined in-line or sourced from an external controlled vocabulary, thesaurus or ontology. + + + + + + The number of observed physical properties aggregated within this composite. + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. + +In many cases, the observed physical property will be sourced from a controlled vocabulary, thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in a well-defined ontology. As such, the attributes of ObservableProperty have been elided; we simply need to assert that the entity has compatible semantics with the ObservableProperty class defined herein. + +[1] Quantity: property of a phenomenon, body, or substance, where the property has a magnitude that can be expressed as a number and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property that is qualified or constrained within a given measurement context. Qualification of the observed physical property may take several forms: +- a specific unit of measure; +- a statistical operator (e.g. maximum) plus the aggregation context that the statistical operator applies to; or +- a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this physical property. + + + + + The association role 'constraint' references the Constraint ?DataType? that specifies the constraints applied to the observable physical property in this context. + + + + + The association role 'qualifier' references the StatisticalQualifier ?DataType? that specifies the statistical function and aggregation patter applied to the base physical property in order to define a statistical summary property. + + + + + The association role 'baseProperty' references the observable physical property from which this qualified property derives. + +The observable physical property may be defined in-line or sourced from an external controlled vocabulary, thesaurus or ontology. + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained according to specific values of the constraining property. For example, the base property 'air temperature' may be constrained such that we are concerned only with the air temperature at 2.0 metres above local ground level (e.g. a screen temperature). In this example, 'height above local ground level' is the constraint property. + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the constraint property value. + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + Attribute 'comparisonOperator' defines the mathematical operator relating the scalar constraint to the supplied numeric value; e.g. comparisonOperator = "eq" and value = "10.0" implies that the constraint is equal to the value 10.0. + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect to a base property; e.g. maximum UV index over a 3-hour period. + +The class 'StatisticalQualifier' defines the type of statistical function plus the mechanism that is used to aggregate the base property values to create the statistical summary: length, area, volume, duration or other. + +Statistical summary properties may be defined by chaining a set of statistical operations together. For example: mean daily maximum temperature over a month period comprises two statistical operations with respect to the base property 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month duration. + + + + + + + The attribute 'description' provides a textual description of the statistical qualification applied to the base observable physical property. + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, length, area or volume) over which the statistical function is applied in order to determine the statistical summary; e.g. prevailing visibility is [approximately] defined as a mean visibility in each horizontal direction. + + + + + The attribute 'statisticalFunction' defines the type of statistical function that is applied to the base observed property values in order to generate the statistical summary. + + http://def.wmo.int/opm/2013/CodeList_StatisticalFunctionCode.xml#StatisticalFunctionCode + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. For example, in aviation the only clouds of significance for terminal aerodrome operations are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical property 'cloud base [height]' may be constrained such that it is applicable only to clouds of a given type. In this example, a single instance of CategoryConstraint would be defined referencing both cloud types (cumulonimbus and towering cumulus); 'cloud type' is the constraint property. + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained according to a range of values of the constraining property. For example, the base property 'radiance' may be constrained such that we are concerned only with the radiance between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint property. + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the constraint property value. + + + + + The association role 'value' references an instance of the RangeBounds class that specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical property in a given measurement context to be specified. + + + + + + + The attribute 'description' provides a textual description of the constraint applied to the base observable physical property. + + + + + The association role 'constraintProperty' references the physical property that is used to constrain the target observable physical property. For example, the observed physical property 'radiance' may be constrained such that one is concerned only with the radiance between wavelength 50nm to 100nm. In this example, 'wavelength' is the constraint property. + +The physical property may be defined in-line or referenced from an external controlled vocabulary, thesaurus or ontology. + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also known as a property value interval). + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + Attribute 'endComparison' defines the mathematical operator relating the upper boundary of the range constraint to the supplied numeric value; e.g. when specifying a wavelength band, endComparison = "eq", uom = "nm" and value = "100.0" implies that the upper range of the wavelength band is 100 nanometres. + + + + + Attribute 'startComparison' defines the mathematical operator relating the lower boundary of the range constraint to the supplied numeric value; e.g. when specifying a wavelength band, startComparison = "eq", uom = "nm" and value = "50.0" implies that the lower range of the wavelength band is 50 nanometres. + + + + + + + + + + + + «Enumeration» 'ComparisonOperator' defines the set mathematical operators that may be used to compare numerical values; not equal, less than, less than or equal, equal, greater than or equal and greater than. + + + + + Comparison operator: "not equal to" + + + + + Comparison operator: "less than" + + + + + Comparison operator: "less than or equal to" + + + + + Comparison operator: "equal to" + + + + + Comparison operator: "greater than or equal to" + + + + + Comparison operator: "greater than" + + + + + + + The «CodeList» class 'StatisticalFunctionCode' specifies the type of statistical function that is applied to the base observable property to define the statistical summary; e.g. maximum air temperature. + +Note that WMO provides two code-tables listing statistical operators: +- WMO No. 306 Vol I.2 Part B FM 92 GRIB code-table 4.10 'Type of statistical processing'; and +- WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 023 'First-order statistics' + +The GRIB2 code-table is defined as the 'recommended' vocabulary for this «CodeList» class but lacks some of the necessary terms. For example, the GRIB code-table includes 'Average' but does not include 'Mean', 'Mode' or 'Median' (which can be found in the BUFR code-table). However, the BUFR code-table is _NOT_ chosen because 'Accumulation' is entirely missing. Given that 'extensibility' is set to 'any', authors are free to refer to their preferred 'statistical operator' vocabulary. The GRIB code-table is only a recommendation. + + http://codes.wmo.int/grib2/codeflag/4.10 + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2/opm.xsd b/config/schemas/schema/int/wmo/opm/1.2/opm.xsd new file mode 100644 index 0000000..ffb56f1 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2/opm.xsd @@ -0,0 +1,32 @@ + + + + + + The 'Observable Property' model enables observed physical properties (also termed "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) to be aggregated into composite properties and for any qualification or constraint relating to those observed physical properties to be explicitly described. + +A data publisher may need to use the Observed Property Model to explicitly define any qualification or constraint applied to the observed property, or, where the observation results in the evaluation of multiple properties, to explicitly define each of those individual physical properties. + +Usage: + +The Observable Property Model may be used to specify constraint or qualification of a physical quantity (or set of physical quantities) within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter Attribute (from ISO 19156, type Class "NamedValue"): + - name: http://def.wmo.int/opm/2013/observable-property#property [1] + - parameter: instance of Class "AbstractObservableProperty" or concrete subclass thereof [2] + +Note that Class "OM_Observation" asserts a constraint such that the value of the parameter/NamedValue/name Attribute shall not occur more than once within a given instance of Class OM_Observation. In situations where multiple physical quantities are observed or measured, the value of the associated parameter/NamedValue/value Attribute may be specified as an instance of Class "CompositeObservableProperty" thus allowing a set of observable properties to be specified. + +Also note that, whilst Class "OM_Observation" provides Attribute "observedProperty" for specifying the (physical) property observed or measured the cardinality of this Attribute is one (e.g. only a single property can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" in-line within the data. Whilst it is permissible to make a local reference to an instance of Class "CompositeObservableProperty" defined elsewhere within the data, it is preferable to reference an external definition. The reason for this is that the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service as a key on which data is indexed; use of internal references are likely to inhibit discovery and retrieval of data. + +Alternatively, if the constraint or qualification of the physical quantity (or set of physical quantities) is consistent within a repeatable procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter Attribute (from "«Application Schema?METCE", type Class "NamedValue"). + +Note that in the case of Class "Process", there is no constraint on the number of occurences of a given parameter name. However, recommended practice indicates the use of an instance of Class "CompositeObservableProperty" where a set of observable properties are to be specified. + +[1] Association Role "property" is specified to have type Class "AbstractObservableProperty" +[2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", "QualifiedObservableProperty" and "CompositeObservableProperty". + +References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + gmlopm.xsd + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2RC1/gmlopm.xsd b/config/schemas/schema/int/wmo/opm/1.2RC1/gmlopm.xsd new file mode 100644 index 0000000..7673d11 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2RC1/gmlopm.xsd @@ -0,0 +1,312 @@ + + + + GML Subset schema for gml:AbstractGML,gml:AbstractGMLType,gml:CodeType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:UnitOfMeasureType,gml:AbstractObject,gml:AreaType,gml:LengthType,gml:VolumeType,gml:AssociationRoleType,gml:ReferenceType, written by gmlSubset.xslt. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + deprecated + + + + + + + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2RC1/observable-property.xsd b/config/schemas/schema/int/wmo/opm/1.2RC1/observable-property.xsd new file mode 100644 index 0000000..60a3809 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2RC1/observable-property.xsd @@ -0,0 +1,392 @@ + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + «Leaf» package for the 'Observable Property Model' + + + + An 'observable property' is a physical property that can be observed. Typically, this will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. + +This abstract class enables either a single physical property to be specified or a composite observable property that aggregates a set of physical properties for a given observation context. + +In many cases, the observed physical property will be sourced from a controlled vocabulary, thesaurus or ontology. + +[1] Quantity: property of a phenomenon, body, or substance, where the property has a magnitude that can be expressed as a number and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + The attribute 'label' provides the primary human-readable label describing the observable physical property. + + + + + The attribute 'altLabel' provides an alternative human-readable label used to describe the physical property. + + + + + The attribute 'notation' provides a notation or code-value that is used to identify the physical property within a given context. + + + + + + + + + + + + + + + + CompositeObservableProperty provides a single object within which a number of AbstractObservableProperty instances can be aggregated. + + + + + + + + + The association role 'property' references an observable physical property. + +The observable physical property may be defined in-line or sourced from an external controlled vocabulary, thesaurus or ontology. + + + + + + + + + + + + + + + + + An 'observable property' is a physical property that can be observed. Typically, this will be a quantitative property (Quantity [1]) such as 'dew-point temperature'. + +In many cases, the observed physical property will be sourced from a controlled vocabulary, thesaurus or ontology. The definition may be a simple a SKOS Concept or a node in a well-defined ontology. As such, the attributes of ObservableProperty have been elided; we simply need to assert that the entity has compatible semantics with the ObservableProperty class defined herein. + +[1] Quantity: property of a phenomenon, body, or substance, where the property has a magnitude that can be expressed as a number and a reference (from the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) + + + + + + + + + + + + + + + + + + + The class 'QualifiedObservableProperty' describes an observable physical property that is qualified or constrained within a given measurement context. Qualification of the observed physical property may take several forms: +- a specific unit of measure; +- a statistical operator (e.g. maximum) plus the aggregation context that the statistical operator applies to; or +- a constraint (e.g. radiance in wavelength band 50nm to 100nm). + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the measurement of this physical property. + + + + + The association role 'constraint' references the Constraint ?DataType? that specifies the constraints applied to the observable physical property in this context. + + + + + The association role 'qualifier' references the StatisticalQualifier ?DataType? that specifies the statistical function and aggregation patter applied to the base physical property in order to define a statistical summary property. + + + + + The association role 'baseProperty' references the observable physical property from which this qualified property derives. + +The observable physical property may be defined in-line or sourced from an external controlled vocabulary, thesaurus or ontology. + + + + + + + + + + + + + + + + The class 'ScalarConstraint' allows an observed physical property to be constrained according to specific values of the constraining property. For example, the base property 'air temperature' may be constrained such that we are concerned only with the air temperature at 2.0 metres above local ground level (e.g. a screen temperature). In this example, 'height above local ground level' is the constraint property. + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the constraint property value. + + + + + The attribute 'value' provides the value of the constraint property. + + + + + + + + + + + + + + + + An observed physical property may be represent a statistical summary with respect to a base property; e.g. maximum UV index over a 3-hour period. + +The class 'StatisticalQualifier' defines the type of statistical function plus the mechanism that is used to aggregate the base property values to create the statistical summary: length, area, volume, duration or other. + +Statistical summary properties may be defined by chaining a set of statistical operations together. For example: mean daily maximum temperature over a month period comprises two statistical operations with respect to the base property 'air temperature' - (i) maximum over a 24-hour duration, (ii) mean over a 1-month duration. + + + + + + + The attribute 'description' provides a textual description of the statistical qualification applied to the base observable physical property. + + + + + The attribute 'aggregationArea' defines the spatial area over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationLength' defines the spatial length over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationTimePeriod' defines the temporal duration over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'aggregationVolume' defines the spatial volume over which the statistical function is applied in order to determine the statistical summary. + + + + + The attribute 'otherAggregation' defines the any type of aggregation (other than duration, length, area or volume) over which the statistical function is applied in order to determine the statistical summary; e.g. prevailing visibility is [approximately] defined as a mean visibility in each horizontal direction. + + + + + The attribute 'statisticalFunction' defines the type of statistical function that is applied to the base observed property values in order to generate the statistical summary. + + + + + + + + + + + + + + The class 'CategoryConstraint' enables a category-based constraint to be specified. For example, in aviation the only clouds of significance for terminal aerodrome operations are convective clouds (cumulonimbus, towering cumulus etc.). The observed physical property 'cloud base [height]' may be constrained such that it is applicable only to clouds of a given type. In this example, a single instance of CategoryConstraint would be defined referencing both cloud types (cumulonimbus and towering cumulus); 'cloud type' is the constraint property. + + + + + + + + + The attribute 'value' defines the category member that applies to this constraint. + + + + + + + + + + + + + + + The class 'RangeConstraint' allows an observed physical property to be constrained according to a range of values of the constraining property. For example, the base property 'radiance' may be constrained such that we are concerned only with the radiance between wavelengths of 50nm to 100nm. In this example, 'wavelength' is the constraint property. + + + + + + + + + The attribute 'uom' specifies the unit of measure used in the specification of the constraint property value. + + + + + The association role 'value' references an instance of the RangeBounds class that specifies the extreme limits of the range that apply to the constraint property. + + + + + + + + + + + + + + + The class 'Constraint' enables the constraints relating to an observable physical property in a given measurement context to be specified. + + + + + + + The attribute 'description' provides a textual description of the constraint applied to the base observable physical property. + + + + + The association role 'constraintProperty' references the physical property that is used to constrain the target observable physical property. For example, the observed physical property 'radiance' may be constrained such that one is concerned only with the radiance between wavelength 50nm to 100nm. In this example, 'wavelength' is the constraint property. + +The physical property may be defined in-line or referenced from an external controlled vocabulary, thesaurus or ontology. + + + + + + + + + + + + + The class 'RangeBounds' describes the extreme limits of a property value range (also known as a property value interval). + + + + + + + The attribute 'rangeStart' provides the extreme lower limit of the range or interval. + + + + + The attribute 'rangeEnd' provides the extreme upper limit of the range or interval. + + + + + + + + + + + + + + + «Enumeration» 'ComparisonOperator' defines the set mathematical operators that may be used to compare numerical values; not equal, less than, less than or equal, equal, greater than or equal and greater than. + + + + + Comparison operator: "not equal to" + + + + + Comparison operator: "less than" + + + + + Comparison operator: "less than or equal to" + + + + + Comparison operator: "equal to" + + + + + Comparison operator: "greater than or equal to" + + + + + Comparison operator: "greater than" + + + + + + + The «CodeList» class 'StatisticalFunctionCode' specifies the type of statistical function that is applied to the base observable property to define the statistical summary; e.g. maximum air temperature. + +Note that WMO provides two code-tables listing statistical operators: +- WMO No. 306 Vol I.2 Part B FM 92 GRIB code-table 4.10 'Type of statistical processing'; and +- WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 023 'First-order statistics' + +The GRIB2 code-table is defined as the 'recommended' vocabulary for this «CodeList» class but lacks some of the necessary terms. For example, the GRIB code-table includes 'Average' but does not include 'Mean', 'Mode' or 'Median' (which can be found in the BUFR code-table). However, the BUFR code-table is _NOT_ chosen because 'Accumulation' is entirely missing. Given that 'extensibility' is set to 'any', authors are free to refer to their preferred 'statistical operator' vocabulary. The GRIB code-table is only a recommendation. + + http://codes.wmo.int/grib2/codeflag/4.10 + none + + + + + + + diff --git a/config/schemas/schema/int/wmo/opm/1.2RC1/opm.xsd b/config/schemas/schema/int/wmo/opm/1.2RC1/opm.xsd new file mode 100644 index 0000000..f4a79b0 --- /dev/null +++ b/config/schemas/schema/int/wmo/opm/1.2RC1/opm.xsd @@ -0,0 +1,31 @@ + + + + + + References to WMO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + The 'Observable Property' model enables observed physical properties (also termed "Quantities" within the 'International vocabulary of metrology' [http://www.bipm.org/utils/common/documents/jcgm/JCGM_200_2008.pdf]) to be aggregated into composite properties and for any qualification or constraint relating to those observed physical properties to be explicitly described. + +A data publisher may need to use the Observed Property Model to explicitly define any qualification or constraint applied to the observed property, or, where the observation results in the evaluation of multiple properties, to explicitly define each of those individual physical properties. + +Usage: + +The Observable Property Model may be used to specify constraint or qualification of a physical quantity (or set of physical quantities) within the context of a specific observation or measurement event; e.g. via OM_Observation/parameter Attribute (from ISO 19156, type Class "NamedValue"): + - name: http://def.wmo.int/opm/2013/observable-property#property [1] + - parameter: instance of Class "AbstractObservableProperty" or concrete subclass thereof [2] + +Note that Class "OM_Observation" asserts a constraint such that the value of the parameter/NamedValue/name Attribute shall not occur more than once within a given instance of Class OM_Observation. In situations where multiple physical quantities are observed or measured, the value of the associated parameter/NamedValue/value Attribute may be specified as an instance of Class "CompositeObservableProperty" thus allowing a set of observable properties to be specified. + +Also note that, whilst Class "OM_Observation" provides Attribute "observedProperty" for specifying the (physical) property observed or measured the cardinality of this Attribute is one (e.g. only a single property can be referenced). Furthermore, this Attribute is implemented "by reference" (serialised as gml:ReferenceType) implying that one cannot define an instance of Class "CompositeObservableProperty" in-line within the data. Whilst it is permissible to make a local reference to an instance of Class "CompositeObservableProperty" defined elsewhere within the data, it is preferable to reference an external definition. The reason for this is that the value of Attribute "observedProperty" is used by the OGC Sensor Observation Service as a key on which data is indexed; use of internal references are likely to inhibit discovery and retrieval of data. + +Alternatively, if the constraint or qualification of the physical quantity (or set of physical quantities) is consistent within a repeatable procedure, it may be defined within the context of that procedure; e.g. via the Process/parameter Attribute (from "«Application Schema?METCE", type Class "NamedValue"). + +Note that in the case of Class "Process", there is no constraint on the number of occurences of a given parameter name. However, recommended practice indicates the use of an instance of Class "CompositeObservableProperty" where a set of observable properties are to be specified. + +[1] Association Role "property" is specified to have type Class "AbstractObservableProperty" +[2] Class "AbstractObservableProperty" has concrete sub-classes "ObservableProperty", "QualifiedObservableProperty" and "CompositeObservableProperty". + + gmlopm.xsd + + + diff --git a/config/schemas/schema/int/wmo/saf/1.0/dataTypes.xsd b/config/schemas/schema/int/wmo/saf/1.0/dataTypes.xsd new file mode 100644 index 0000000..56e11be --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0/dataTypes.xsd @@ -0,0 +1,226 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package containing the datatypes that are used throughout SAF. This is restricted + set that are roughly analogous to equivalent AIXM data types. + + + + + + + A textual designator. + + + + + + + + + + The official name of a State, an aerodrome, a unit, etc.. + + + + + + + + + + + + + + + + The coded identifier of an organisation, authority, agency or unit. + + + + + + + + + + The three letter coded location identifier of an airport/heliport according to the + IATA Resolution 763. + + + + + + + + + + + A coded identifier for an Aerodrome/Heliport/Aerodrome. The rules according to which + this identifier should be formed are as follows: 1) If the AD/HP has an ICAO four + letter location indicator, this will become the CODE_ID for the Aerodrome/Heliport; + 2) If the AD/HP does not have an ICAO four letter location indicator but has an IATA + three letter code, then this will become the CODE_ID for the Aerodrome/Heliport; 3) + If the AD/HP does not have either an ICAO four letter location indicator or an IATA + three letter code, an artificially generated code will be used. This will contain + a group of letters and a number. The group of letters could be the 2 letter code of + the State responsible for the Aerodrome/Heliport (or one of these, if there are more + than one, like ED and ET for Germany) and the number could be an integer between 0001 + and 9999. + + + + + + + + + + + The four letter coded location identifier as published in the ICAO DOC 7910 - Location + Indicators. + + + + + + + + + + + The valid codes that may be used for airspace type (e.g., flight information region, + upper information region, controlled airspace). Equivalent to AIXM CodeAirspaceType, + except that only the codes of interest outside AIXM were used. + + + + + + Flight information region. Airspace of defined dimensions within which flight information + service and alerting service are provided. Description: ICAO Recognized. Might, for + example, be used if service provided by more than one unit. + + + + + + Upper flight information region. An upper airspace of defined dimensions within which + flight information service and alerting service are provided. Description: Non-ICAO + Recognized. Each state determines its definition for upper airspace. + + + + + + Flight information region or upper flight information region. + + + + + Control area. A controlled airspace extending upwards from a specified limit above + the earth. Description: ICAO Recognized. + + + + + + + + The type of vertical reference (e.g., surface, mean sea level) This class is copied + from the AIXM class with the same name. + + + + + + The distance measured from the surface of the Earth (equivalent to AGL - Above Ground + Level). + + + + + + The distance measured from mean sea level (equivalent to altitude). + + + + + The distance measured from the WGS84 ellipsoid. + + + + + The vertical distance is measured with an altimeter set to the standard atmosphere. + + + + + + + A coded list of values that designate the intentions of a flight in relation with + a location, such as arrival, departure or over-flight. + + + + + + All types (arrival, departure and overflying). + + + + + Arrival flights. + + + + + Departing flights. + + + + + Overflying flights. + + + + + + + A unit providing particular ATS services. + + + + + Aerodrome reporting office/ATS reporting office. + + + + + Air traffic control centre. + + + + + Air traffic services unit. + + + + + Flight information centre. + + + + + Meteorological watch office. + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.0/features.xsd b/config/schemas/schema/int/wmo/saf/1.0/features.xsd new file mode 100644 index 0000000..4884a99 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0/features.xsd @@ -0,0 +1,410 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package containing the definition of the core SAF Features. Features in this package + roughly correspond to AIXM equivalents. + + + Schematron validation + + + + + + + + + + + + + A defined three dimensional region of space relevant to air traffic. + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + + + + + + + + A code indicating the general structure or characteristics of a particular airspace. + + + + + A published sequence of characters allowing the identification of the airspace. Description: + Typical examples are the ID of the Danger, Prohibited, Temporary segregated Areas, + etc. + + + + + + The name given to an airspace by a responsible authority. Description: It should be + written as published, with no significance to upper or lower case letters. + + + + + + A code indicating the Airspace designator is recorded in ICAO Doc. 7910. + + + + + + + + + + + + + + + + + A defined area on land or water (including any buildings, installations and equipment) + intended to be used either wholly or in part for the arrival, departure and surface + movement of aircraft/helicopters. + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + + + + + + + + A coded designator for an Aerodrome/Heliport. The rules according to which this identifier + should be formed are as follows: 1. If the AD/HP has an ICAO four letter location + indicator, then this one will become the CODE_ID for the Aerodrome/Heliport; 2. If + the AD/HP does not have an ICAO four letter location indicator, but it has an IATA + three letter code, then this one will become the CODE_ID for the Aerodrome/Heliport; + 3. If the AD/HP has neither an ICAO four letter location indicator nor an IATA three + letter code, then an artificial generated code will be used. This will contain a group + of letters and a number. The group of letters could be the 2 letter code of the State + being responsible for the Aerodrome/Heliport and the number could be an integer between + 0001 and 9999. + + + + + + The primary official name of an aerodrome as designated by an appropriate authority. + + + + + The four letter ICAO location indicator of the aerodrome/heliport, as listed in ICAO + DOC 7910. + + + + + + The identifier that is assigned to a location in accordance with rules (resolution + 767) governed by the International Air Transport Association (IATA). + + + + + + The vertical distance above Mean Sea Level (MSL) of the highest point of the landing + area. + + + + + + + + + + + + + + + + + + A generic term meaning variously all types of 'units' providing all types of services. + This includes particularly Air Traffic Management (ATM) Units but also units which + are not express verbs included in ATM such as SAR, MET, COM etc. + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + + + + + + + + The full textual name of a unit. This name must be established according to the rules + specified by ICAO, viz.: in the official language of the country, transposed into + the Latin Alphabet where necessary. + + + + + + A type by which the Unit is recognised, usually related to the standard type of services + provided by it (e.g. area control centre, advisory centre, aeronautical information + services office). + + + + + + A coded designator associated with the Unit. For example, the ICAO Location Indicator + of an ACC, as listed in DOC 7910. + + + + + + Identifies the geographical point of the Unit. + + + + + + + + + + + + + + + + One of the two landing and take-off directions of a runway for which attributes like + TORA, TODA, LDA, etc. may be defined. + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the landing and take-off direction. Examples: 27, 35L, + 01R. + + + + + + The measured angle between the runway direction and True North at a given position. + Note : The True North is the north point at which the meridian lines meet. + + + + + + Elevation of touch down zone: The value of the highest elevation of the runway Touch + Down Zone (TDZ). + + + + + + + + + + + + + + + + + + The provision of tangible goods, information, instructions, guidance, etc. to pilots, + flights, aircraft operators and other personnel and institutions concerned with flight + operations. + + + + + Service: name not match with pattern TextNameType + + + + + + + + + + + + The destination (arriving, departing, etc.) of the flights for which the information + is provided. + + + + + + A free text name by which the service is identified. + + + + + + + + + + + + + + + + + + A defined rectangular area on a land aerodrome/heliport prepared for the landing and + take-off of aircraft. Note: this includes the concept of Final Approach and Take-Off + Area (FATO) for helicopters. + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport + which has more than one. E.g. 09/27, 02R/20L, RWY 1. + + + + + + + + + + + + + + + + + + A defined volume in the air, described as horizontal projection with vertical limits. + + + + + + + + + The vertical position of the airspace ceiling. + + + + + The reference surface used for the value of the upper limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + The vertical position of the airspace floor. + + + + + The reference surface used for the value of the lower limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.0/measures.xsd b/config/schemas/schema/int/wmo/saf/1.0/measures.xsd new file mode 100644 index 0000000..0696350 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0/measures.xsd @@ -0,0 +1,41 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package with Nillable Measure and NilReason + + + + + + A nillable Distance quantity. Unlike the base Distance measure, references to this + type may be nil and may include a nilReason + + + + + + + + + + + + + A nillable Length quantity. Unlike the base Length measure, references to this type + may be nil and include a nilReason + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.0/saf.xsd b/config/schemas/schema/int/wmo/saf/1.0/saf.xsd new file mode 100644 index 0000000..d3f1156 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0/saf.xsd @@ -0,0 +1,30 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Simplified features from the aeronautical domain, such as aerodrome, runway, unit, + and airspace. These features are simplified representations of more complex aeronautical + features found in AICM/AIXM that are used for storage or transmission. There are + two independent issues involved in referencing aeronautical features: 1. Using AICM/AIXM + classes directly for these concepts would introduce a dependency on AICM/AIXM, which + is a package of significant size and complexity 2. Machine-readable, managed definitions + for these concepts (such as the location, capabilities, and other information for + the 'HTKJ' aerodrome) do not exist in a unified and authoritative form. This information + is managed independently, and sometimes inconsistently, by many organizations worldwide + The current version of this package is intended to address the needs for producers + of meteorological information to be able to distribute the basic characteristics (identification, + location, time, etc.) of their aeronautical information to consumers. In many cases + data producers are the best authority for up-to-date aeronautical information. Downstream + consumers may then use this information or ignore it. These concepts are represented + in a way that is intended to be largely consistent with AICM/AIXM. + + + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.0RC1/saf.xsd b/config/schemas/schema/int/wmo/saf/1.0RC1/saf.xsd new file mode 100644 index 0000000..d4d52c0 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0RC1/saf.xsd @@ -0,0 +1,309 @@ + + + + Simplified features from the aviation domain, such as aerodrome and runway. These + features are not intended for storage or transmission, merely simplified variants + of aviation concepts that can be referenced from other packages. There are two + independent issues involved in referencing aviation features: <ol> <li>using AICM/AIXM + classes directly for these concepts would introduce a dependency on AICM/AIXM, which + is a package of significant size and complexity</li> <li>web-accessible, machine-readable, + managed definitions for these concepts (such as the location, capabilites, and other + information for the 'HTKJ' aerodrome) do not exist in an unified and authoritative + form. This information is managed independently and inconsistently by many organizations + related to the aviation domain</li> </ol> This package follows the traditional approach + used in weather TAC formats, which is to include sufficient information in the data + for consumers to identify the referenced aerodrome, FIR, or other feature. The current + version of this package represents the bare minimum of information needed by METAR, + SPECI, TAF, and SIGMET. These concepts should not be considered a replacement or alternative + to AICM/AIXM equivalents, most classes in this package are only suitable for basic + referencing purposes such as the use of xlink in XML documents. These concepts are + represented in a way that is intended to be largely consistent with AICM/AIXM, but + a detailed consistency analysis has not yet been attempted. + + + Schematron validation + + + + + + + + + + + + + + + A defined area on land or water (including any buildings, installations, and equipment) + intended to be used either wholly or in part for the arrival, departure, and surface + movement of aircraft. + + + + + + + + + + + + + + + + + + An airspace of defined dimensions within which flight information service and alerting + service are provided + + + + + + + + + + + + + + + + + + A defined rectangular area on a land aerodrome prepared for the landing and take-off + of aircraft. Examples from ICAO Annex 3 include "R03" and "R18C" + + + + + + + + + + The designator of the runway. E.g., "03" or "18". This representation is partially + consistent with AIXM + + + + + + Left, right or center + + + + + + + + + + + + + + + + <font color="#ff0000">Need definition and description</font> + + + + + + + + + + + + + + + + + <font color="#ff0000">Need definition and description</font> + + + + + + + + + + + + + + + + + When an ICAO contracting state accepts responsibility for providing air traffic services + within a flight information region or a control area, a meteorological watch office + will : a) maintain continuous watch over meteorological conditions affecting flight + operations within its area of responsibility; b) prepare SIGMET and other information + relating to its area of responsibility; c) supply SIGMET information and, as required, + other meteorological information to associated air traffic services units; d) disseminate + SIGMET information; e) when required by regional air navigation agreemen: 1) prepare + AIRMET information related to its area of responsibility; 2) supply AIRMET information + to associated air traffic services units; and 3) disseminate AIRMET information; f) + supply information received on pre-eruption volcanic activity, a volcanic eruption + and volcanic ash cloud for which a SIGMET has not already been issued, to its associated + ACC/FIC, as agreed between the meteorological and ATS authorities concerned, and to + its associated VAAC as determined by regional air navigation agreement; and g) supply + information received concerning the accidental release of radioactive materials into + the atmosphere, in the area for which it maintains watch or adjacent areas, to its + associated ACC/FIC, as agreed between the meteorological and ATS authorities concerned, + and to aeronautical information service units, as agreed between the meteorological + and appropriate civil aviation authorities concerned. The information shall comprise + location, date and time of the accident, and forecast trajectories of the radioactive + materials. <font color="#ff0000">Not clear whether any further information is required + by data providers and/or data producers relating to MWOs.</font> + + + + + + + + + + + + + + + + + + A defined volume in the air, described as a horizontal projection with vertical limits. + This class is a modified version of the AIXM AirspaceVolume class. This version of + the class has been reduced to horizontal and vertical geographic information, and + the horizontal geometry was broadened to allow a horizontal description of airspace + using any geometric primitive in combination with an upper and lower vertical limit. + <font color="#ff0000">The use of GM_Primitive may not be ideal. This was generalized + to allow for 3-dimensional descriptions using ArcByCentrePoint, Surface, or other + planar geometries that can be combined with vertical limits to describe a full 3-D + solid. Is there a better GM_* sub-type that would serve better here?</font> References + from the original AIXM class to AIXM data types were replaced with the closest ISO + equivalents. Specifically, ValDistanceVertical (for upper and lower limit) were replaced + with Measure. Instances of the AIXM Surface were replaced with GM_Primitive. The + horizontal components may be any 2-dimensional geometry, such as an ArcByCentrePoint + or a Polygon. In conjunction with upper and lower limits this describes a 3-dimensional + shape and is equivalent to GM_Solid. When the upper limit is missing, this indicates + that the described area extends to the maximum height above the earth that is significant + to aviation. When the lower limit is missing, this indicates that the described area + extends down to ground level. + + + + + AirspaceSolid: horizontalProjection must inherit from either a GM_Surface, ArcByCentrePoint, + or LinearRing + + + + + + + + + + + + + The horizontal shape of the airspace boundary. This portion of AirspaceVolume is + not present in the UML model, and was instead modeled after the AIXM XML schema representation. + The current representation points to Any and several specific constraints have been + applied to this type. This is due to the fact that no common supertypes more specific + than Any has been found yet between LinearRing, GM_Surface, and ArcByCenterPoint. + If a common supertype is found for these 2-D geometries this type could be made more + specific. + + + + + + The vertical position of the airspace floor. + + + + + The vertical position of the airspace ceiling. + + + + + + + + + + + + + + + + <font color="#ff0000">Need definition and description</font> + + + + + + + + + + + + + + + + + A generic term meaning variously, air traffic control unit, flight information centre + or air traffic services reporting office + + + + + + + + + + + + + + + + + + Either LEFT, RIGHT, or CENTER + + + + + The left side of an identified area + + + + + The right side of an identified area + + + + + The center of an identified location + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/saf/1.0RC2/dataTypes.xsd b/config/schemas/schema/int/wmo/saf/1.0RC2/dataTypes.xsd new file mode 100644 index 0000000..62723b2 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0RC2/dataTypes.xsd @@ -0,0 +1,216 @@ + + + + Package containing the datatypes that are used throughout SAF. This is restricted + set that are roughly analogous to equivalent AIXM data types. + + + + + + + A textual designator. + + + + + + + + + + The official name of a State, an aerodrome, a unit, etc.. + + + + + + + + + + + + + + + + The coded identifier of an organisation, authority, agency or unit. + + + + + + + + + + The three letter coded location identifier of an airport/heliport according to the + IATA Resolution 763. + + + + + + + + + + + A coded identifier for an Aerodrome/Heliport/Aerodrome. The rules according to which + this identifier should be formed are as follows: 1) If the AD/HP has an ICAO four + letter location indicator, this will become the CODE_ID for the Aerodrome/Heliport; + 2) If the AD/HP does not have an ICAO four letter location indicator but has an IATA + three letter code, then this will become the CODE_ID for the Aerodrome/Heliport; 3) + If the AD/HP does not have either an ICAO four letter location indicator or an IATA + three letter code, an artificially generated code will be used. This will contain + a group of letters and a number. The group of letters could be the 2 letter code of + the State responsible for the Aerodrome/Heliport (or one of these, if there are more + than one, like ED and ET for Germany) and the number could be an integer between 0001 + and 9999. + + + + + + + + + + + The four letter coded location identifier as published in the ICAO DOC 7910 - Location + Indicators. + + + + + + + + + + + The valid codes that may be used for airspace type (e.g., flight information region, + upper information region, controlled airspace). Equivalent to AIXM CodeAirspaceType, + except that only the codes of interest outside AIXM were used. + + + + + + Flight information region. Airspace of defined dimensions within which flight information + service and alerting service are provided. Description: ICAO Recognized. Might, for + example, be used if service provided by more than one unit. + + + + + + Upper flight information region. An upper airspace of defined dimensions within which + flight information service and alerting service are provided. Description: Non-ICAO + Recognized. Each state determines its definition for upper airspace. + + + + + + Control area. A controlled airspace extending upwards from a specified limit above + the earth. Description: ICAO Recognized. + + + + + + + + The type of vertical reference (e.g., surface, mean sea level) This class is copied + from the AIXM class with the same name. + + + + + + The distance measured from the surface of the Earth (equivalent to AGL - Above Ground + Level). + + + + + + The distance measured from mean sea level (equivalent to altitude). + + + + + The distance measured from the WGS84 ellipsoid. + + + + + The vertical distance is measured with an altimeter set to the standard atmosphere. + + + + + + + A coded list of values that designate the intentions of a flight in relation with + a location, such as arrival, departure or over-flight. + + + + + + All types (arrival, departure and overflying). + + + + + Arrival flights. + + + + + Departing flights. + + + + + Overflying flights. + + + + + + + A unit providing particular ATS services. + + + + + Aerodrome reporting office/ATS reporting office. + + + + + Air traffic control centre. + + + + + Air traffic services unit. + + + + + Flight information centre. + + + + + Meteorological watch office. + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/saf/1.0RC2/features.xsd b/config/schemas/schema/int/wmo/saf/1.0RC2/features.xsd new file mode 100644 index 0000000..d8bf04b --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0RC2/features.xsd @@ -0,0 +1,405 @@ + + + + Package containing the definition of the core SAF Features. Features in this package + roughly correspond to AIXM equivalents. + + + Schematron validation + + + + + + + + + + + + + A defined three dimensional region of space relevant to air traffic. + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + + + + + + + + A code indicating the general structure or characteristics of a particular airspace. + + + + + A published sequence of characters allowing the identification of the airspace. Description: + Typical examples are the ID of the Danger, Prohibited, Temporary segregated Areas, + etc. + + + + + + The name given to an airspace by a responsible authority. Description: It should be + written as published, with no significance to upper or lower case letters. + + + + + + A code indicating the Airspace designator is recorded in ICAO Doc. 7910. + + + + + + + + + + + + + + + + + A defined area on land or water (including any buildings, installations and equipment) + intended to be used either wholly or in part for the arrival, departure and surface + movement of aircraft/helicopters. + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + + + + + + + + A coded designator for an Aerodrome/Heliport. The rules according to which this identifier + should be formed are as follows: 1. If the AD/HP has an ICAO four letter location + indicator, then this one will become the CODE_ID for the Aerodrome/Heliport; 2. If + the AD/HP does not have an ICAO four letter location indicator, but it has an IATA + three letter code, then this one will become the CODE_ID for the Aerodrome/Heliport; + 3. If the AD/HP has neither an ICAO four letter location indicator nor an IATA three + letter code, then an artificial generated code will be used. This will contain a group + of letters and a number. The group of letters could be the 2 letter code of the State + being responsible for the Aerodrome/Heliport and the number could be an integer between + 0001 and 9999. + + + + + + The primary official name of an aerodrome as designated by an appropriate authority. + + + + + The four letter ICAO location indicator of the aerodrome/heliport, as listed in ICAO + DOC 7910. + + + + + + The identifier that is assigned to a location in accordance with rules (resolution + 767) governed by the International Air Transport Association (IATA). + + + + + + The vertical distance above Mean Sea Level (MSL) of the highest point of the landing + area. + + + + + + + + + + + + + + + + + + A generic term meaning variously all types of 'units' providing all types of services. + This includes particularly Air Traffic Management (ATM) Units but also units which + are not express verbs included in ATM such as SAR, MET, COM etc. + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + + + + + + + + The full textual name of a unit. This name must be established according to the rules + specified by ICAO, viz.: in the official language of the country, transposed into + the Latin Alphabet where necessary. + + + + + + A type by which the Unit is recognised, usually related to the standard type of services + provided by it (e.g. area control centre, advisory centre, aeronautical information + services office). + + + + + + A coded designator associated with the Unit. For example, the ICAO Location Indicator + of an ACC, as listed in DOC 7910. + + + + + + Identifies the geographical point of the Unit. + + + + + + + + + + + + + + + + One of the two landing and take-off directions of a runway for which attributes like + TORA, TODA, LDA, etc. may be defined. + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the landing and take-off direction. Examples: 27, 35L, + 01R. + + + + + + The measured angle between the runway direction and True North at a given position. + Note : The True North is the north point at which the meridian lines meet. + + + + + + Elevation of touch down zone: The value of the highest elevation of the runway Touch + Down Zone (TDZ). + + + + + + + + + + + + + + + + + + The provision of tangible goods, information, instructions, guidance, etc. to pilots, + flights, aircraft operators and other personnel and institutions concerned with flight + operations. + + + + + Service: name not match with pattern TextNameType + + + + + + + + + + + + The destination (arriving, departing, etc.) of the flights for which the information + is provided. + + + + + + A free text name by which the service is identified. + + + + + + + + + + + + + + + + + + A defined rectangular area on a land aerodrome/heliport prepared for the landing and + take-off of aircraft. Note: this includes the concept of Final Approach and Take-Off + Area (FATO) for helicopters. + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport + which has more than one. E.g. 09/27, 02R/20L, RWY 1. + + + + + + + + + + + + + + + + + + A defined volume in the air, described as horizontal projection with vertical limits. + + + + + + + + + The vertical position of the airspace ceiling. + + + + + The reference surface used for the value of the upper limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + The vertical position of the airspace floor. + + + + + The reference surface used for the value of the lower limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/saf/1.0RC2/measures.xsd b/config/schemas/schema/int/wmo/saf/1.0RC2/measures.xsd new file mode 100644 index 0000000..ddc4292 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0RC2/measures.xsd @@ -0,0 +1,24 @@ + + + + Package with Nillable Measure and NilReason + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/saf/1.0RC2/saf.xsd b/config/schemas/schema/int/wmo/saf/1.0RC2/saf.xsd new file mode 100644 index 0000000..05890ad --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.0RC2/saf.xsd @@ -0,0 +1,25 @@ + + + + Simplified features from the aeronautical domain, such as aerodrome, runway, unit, + and airspace. These features are simplified representations of more complex aeronautical + features found in AICM/AIXM that are used for storage or transmission. There are + two independent issues involved in referencing aeronautical features: 1. Using AICM/AIXM + classes directly for these concepts would introduce a dependency on AICM/AIXM, which + is a package of significant size and complexity 2. Machine-readable, managed definitions + for these concepts (such as the location, capabilities, and other information for + the 'HTKJ' aerodrome) do not exist in a unified and authoritative form. This information + is managed independently, and sometimes inconsistently, by many organizations worldwide + The current version of this package is intended to address the needs for producers + of meteorological information to be able to distribute the basic characteristics (identification, + location, time, etc.) of their aeronautical information to consumers. In many cases + data producers are the best authority for up-to-date aeronautical information. Downstream + consumers may then use this information or ignore it. These concepts are represented + in a way that is intended to be largely consistent with AICM/AIXM. + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/int/wmo/saf/1.1/dataTypes.xsd b/config/schemas/schema/int/wmo/saf/1.1/dataTypes.xsd new file mode 100644 index 0000000..2b92b38 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.1/dataTypes.xsd @@ -0,0 +1,226 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package containing the datatypes that are used throughout SAF. This is restricted + set that are roughly analogous to equivalent AIXM data types. + + + + + + + A textual designator. + + + + + + + + + + The official name of a State, an aerodrome, a unit, etc.. + + + + + + + + + + + + + + + + The coded identifier of an organisation, authority, agency or unit. + + + + + + + + + + The three letter coded location identifier of an airport/heliport according to the + IATA Resolution 763. + + + + + + + + + + + A coded identifier for an Aerodrome/Heliport/Aerodrome. The rules according to which + this identifier should be formed are as follows: 1) If the AD/HP has an ICAO four + letter location indicator, this will become the CODE_ID for the Aerodrome/Heliport; + 2) If the AD/HP does not have an ICAO four letter location indicator but has an IATA + three letter code, then this will become the CODE_ID for the Aerodrome/Heliport; 3) + If the AD/HP does not have either an ICAO four letter location indicator or an IATA + three letter code, an artificially generated code will be used. This will contain + a group of letters and a number. The group of letters could be the 2 letter code of + the State responsible for the Aerodrome/Heliport (or one of these, if there are more + than one, like ED and ET for Germany) and the number could be an integer between 0001 + and 9999. + + + + + + + + + + + The four letter coded location identifier as published in the ICAO DOC 7910 - Location + Indicators. + + + + + + + + + + + The valid codes that may be used for airspace type (e.g., flight information region, + upper information region, controlled airspace). Equivalent to AIXM CodeAirspaceType, + except that only the codes of interest outside AIXM were used. + + + + + + Flight information region. Airspace of defined dimensions within which flight information + service and alerting service are provided. Description: ICAO Recognized. Might, for + example, be used if service provided by more than one unit. + + + + + + Upper flight information region. An upper airspace of defined dimensions within which + flight information service and alerting service are provided. Description: Non-ICAO + Recognized. Each state determines its definition for upper airspace. + + + + + + Flight information region or upper flight information region. + + + + + Control area. A controlled airspace extending upwards from a specified limit above + the earth. Description: ICAO Recognized. + + + + + + + + The type of vertical reference (e.g., surface, mean sea level) This class is copied + from the AIXM class with the same name. + + + + + + The distance measured from the surface of the Earth (equivalent to AGL - Above Ground + Level). + + + + + + The distance measured from mean sea level (equivalent to altitude). + + + + + The distance measured from the WGS84 ellipsoid. + + + + + The vertical distance is measured with an altimeter set to the standard atmosphere. + + + + + + + A coded list of values that designate the intentions of a flight in relation with + a location, such as arrival, departure or over-flight. + + + + + + All types (arrival, departure and overflying). + + + + + Arrival flights. + + + + + Departing flights. + + + + + Overflying flights. + + + + + + + A unit providing particular ATS services. + + + + + Aerodrome reporting office/ATS reporting office. + + + + + Air traffic control centre. + + + + + Air traffic services unit. + + + + + Flight information centre. + + + + + Meteorological watch office. + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.1/features.xsd b/config/schemas/schema/int/wmo/saf/1.1/features.xsd new file mode 100644 index 0000000..e53a306 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.1/features.xsd @@ -0,0 +1,410 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package containing the definition of the core SAF Features. Features in this package + roughly correspond to AIXM equivalents. + + + Schematron validation + + + + + + + + + + + + + A defined three dimensional region of space relevant to air traffic. + + + + Airspace: designator not match with pattern CodeAirspaceDesignatorType + + + + + Airspace: name not match with pattern TextNameType + + + + + + + + + + + + A code indicating the general structure or characteristics of a particular airspace. + + + + + A published sequence of characters allowing the identification of the airspace. Description: + Typical examples are the ID of the Danger, Prohibited, Temporary segregated Areas, + etc. + + + + + + The name given to an airspace by a responsible authority. Description: It should be + written as published, with no significance to upper or lower case letters. + + + + + + A code indicating the Airspace designator is recorded in ICAO Doc. 7910. + + + + + + + + + + + + + + + + + A defined area on land or water (including any buildings, installations and equipment) + intended to be used either wholly or in part for the arrival, departure and surface + movement of aircraft/helicopters. + + + + + Aerodrome: designator not match with pattern CodeAirportHeliportDesignatorType + + + + + Aerodrome: name not match with pattern TextNameType + + + + + Aerodrome: locationIndicatorICAO not match with pattern CodeICAOType + + + + + Aerodrome: designatorIATA not match with pattern CodeIATAType + + + + + + + + + + + + A coded designator for an Aerodrome/Heliport. The rules according to which this identifier + should be formed are as follows: 1. If the AD/HP has an ICAO four letter location + indicator, then this one will become the CODE_ID for the Aerodrome/Heliport; 2. If + the AD/HP does not have an ICAO four letter location indicator, but it has an IATA + three letter code, then this one will become the CODE_ID for the Aerodrome/Heliport; + 3. If the AD/HP has neither an ICAO four letter location indicator nor an IATA three + letter code, then an artificial generated code will be used. This will contain a group + of letters and a number. The group of letters could be the 2 letter code of the State + being responsible for the Aerodrome/Heliport and the number could be an integer between + 0001 and 9999. + + + + + + The primary official name of an aerodrome as designated by an appropriate authority. + + + + + The four letter ICAO location indicator of the aerodrome/heliport, as listed in ICAO + DOC 7910. + + + + + + The identifier that is assigned to a location in accordance with rules (resolution + 767) governed by the International Air Transport Association (IATA). + + + + + + The vertical distance above Mean Sea Level (MSL) of the highest point of the landing + area. + + + + + + + + + + + + + + + + + + A generic term meaning variously all types of 'units' providing all types of services. + This includes particularly Air Traffic Management (ATM) Units but also units which + are not express verbs included in ATM such as SAR, MET, COM etc. + + + + + Unit: name not match with pattern TextNameType + + + + + Unit: designator not match with pattern CodeOrganisationDesignatorType + + + + + + + + + + + + The full textual name of a unit. This name must be established according to the rules + specified by ICAO, viz.: in the official language of the country, transposed into + the Latin Alphabet where necessary. + + + + + + A type by which the Unit is recognised, usually related to the standard type of services + provided by it (e.g. area control centre, advisory centre, aeronautical information + services office). + + + + + + A coded designator associated with the Unit. For example, the ICAO Location Indicator + of an ACC, as listed in DOC 7910. + + + + + + Identifies the geographical point of the Unit. + + + + + + + + + + + + + + + + One of the two landing and take-off directions of a runway for which attributes like + TORA, TODA, LDA, etc. may be defined. + + + + + RunwayDirection: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the landing and take-off direction. Examples: 27, 35L, + 01R. + + + + + + The measured angle between the runway direction and True North at a given position. + Note : The True North is the north point at which the meridian lines meet. + + + + + + Elevation of touch down zone: The value of the highest elevation of the runway Touch + Down Zone (TDZ). + + + + + + + + + + + + + + + + + + The provision of tangible goods, information, instructions, guidance, etc. to pilots, + flights, aircraft operators and other personnel and institutions concerned with flight + operations. + + + + + Service: name not match with pattern TextNameType + + + + + + + + + + + + The destination (arriving, departing, etc.) of the flights for which the information + is provided. + + + + + + A free text name by which the service is identified. + + + + + + + + + + + + + + + + + + A defined rectangular area on a land aerodrome/heliport prepared for the landing and + take-off of aircraft. Note: this includes the concept of Final Approach and Take-Off + Area (FATO) for helicopters. + + + + + Runway: designator not match with pattern TextDesignatorType + + + + + + + + + + + + The full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport + which has more than one. E.g. 09/27, 02R/20L, RWY 1. + + + + + + + + + + + + + + + + + + A defined volume in the air, described as horizontal projection with vertical limits. + + + + + + + + + The vertical position of the airspace ceiling. + + + + + The reference surface used for the value of the upper limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + The vertical position of the airspace floor. + + + + + The reference surface used for the value of the lower limit. For example, Mean Sea + Level, Ground, standard pressure, etc.. + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.1/measures.xsd b/config/schemas/schema/int/wmo/saf/1.1/measures.xsd new file mode 100644 index 0000000..c21fd44 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.1/measures.xsd @@ -0,0 +1,41 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Package with Nillable Measure and NilReason + + + + + + A nillable Distance quantity. Unlike the base Distance measure, references to this + type may be nil and may include a nilReason + + + + + + + + + + + + + A nillable Length quantity. Unlike the base Length measure, references to this type + may be nil and include a nilReason + + + + + + + + + + + diff --git a/config/schemas/schema/int/wmo/saf/1.1/saf.xsd b/config/schemas/schema/int/wmo/saf/1.1/saf.xsd new file mode 100644 index 0000000..18a7d87 --- /dev/null +++ b/config/schemas/schema/int/wmo/saf/1.1/saf.xsd @@ -0,0 +1,30 @@ + + + References to WMO and ICAO Technical Regulations within this XML schema shall have + no formal status and are for information purposes only. Where there are differences + between the Technical Regulations and the schema, the Technical Regulations shall + take precedence. Technical Regulations may impose requirements that are not described + in this schema. + + Simplified features from the aeronautical domain, such as aerodrome, runway, unit, + and airspace. These features are simplified representations of more complex aeronautical + features found in AICM/AIXM that are used for storage or transmission. There are + two independent issues involved in referencing aeronautical features: 1. Using AICM/AIXM + classes directly for these concepts would introduce a dependency on AICM/AIXM, which + is a package of significant size and complexity 2. Machine-readable, managed definitions + for these concepts (such as the location, capabilities, and other information for + the 'HTKJ' aerodrome) do not exist in a unified and authoritative form. This information + is managed independently, and sometimes inconsistently, by many organizations worldwide + The current version of this package is intended to address the needs for producers + of meteorological information to be able to distribute the basic characteristics (identification, + location, time, etc.) of their aeronautical information to consumers. In many cases + data producers are the best authority for up-to-date aeronautical information. Downstream + consumers may then use this information or ignore it. These concepts are represented + in a way that is intended to be largely consistent with AICM/AIXM. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/SchematronConstraints.xml b/config/schemas/schema/net/opengis/gml/3.2.1/SchematronConstraints.xml new file mode 100644 index 0000000..6cfd40f --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/SchematronConstraints.xml @@ -0,0 +1,71 @@ + + Schematron constraints for GML / ISO 19136 + + + + + + ValueArray may not carry both a reference to a codeSpace and a uom + + + + + All components shall be of the same type + All components shall be of the same type + + + + + The presence of a dimension attribute implies the presence of the srsName attribute. + The presence of an axisLabels attribute implies the presence of the srsName attribute. + The presence of an uomLabels attribute implies the presence of the srsName attribute. + The presence of an uomLabels attribute implies the presence of the axisLabels attribute and vice versa. + + + + + All patches shall be gml:PolygonPatch elements or an element in the substitution group of gml:PolygonPatch. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All patches shall be gml:Triangle elements or an element in the substitution group of gml:PolygonPatch. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + Property element may not carry both a reference to an object and contain an object. + Property element shall either carry a reference to an object or contain an object. + + + + + All values in the domain set shall be gml:MultiPoint elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiCurve elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiSurface elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:MultiSolid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:Grid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + + + All values in the domain set shall be gml:RectifiedGrid elements or an element in its substitution group. Note that the test currently does not identify substitutable elements correctly, this will require the use of XPath 2 in the future. + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/basicTypes.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/basicTypes.xsd new file mode 100644 index 0000000..d6ffd5f --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/basicTypes.xsd @@ -0,0 +1,268 @@ + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values "+" (plus) and "-" (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/coordinateOperations.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateOperations.xsd new file mode 100644 index 0000000..5eaacaf --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateOperations.xsd @@ -0,0 +1,525 @@ + + + + coordinateOperations.xsd + See ISO/DIS 19136 13.6. +The spatial or temporal coordinate operations schema components can be divided into five logical parts, which define elements and types for XML encoding of the definitions of: +- Multiple abstract coordinate operations +- Multiple concrete types of coordinate operations, including Transformations and Conversions +- Abstract and concrete parameter values and groups +- Operation methods +- Abstract and concrete operation parameters and groups +These schema component encodes the Coordinate Operation package of the UML Model for ISO 19111 Clause 11. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + gml:AbstractCoordinateOperation is a mathematical operation on coordinates that transforms or converts coordinates to another coordinate reference system. Many but not all coordinate operations (from CRS A to CRS B) also uniquely define the inverse operation (from CRS B to CRS A). In some cases, the operation method algorithm for the inverse operation is the same as for the forward algorithm, but the signs of some operation parameter values shall be reversed. In other cases, different algorithms are required for the forward and inverse operations, but the same operation parameter values are used. If (some) entirely different parameter values are needed, a different coordinate operation shall be defined. +The optional coordinateOperationAccuracy property elements provide estimates of the impact of this coordinate operation on point position accuracy. + + + + + + + + + + + + + + + + + + + gml:operationVersion is the version of the coordinate transformation (i.e., instantiation due to the stochastic nature of the parameters). Mandatory when describing a transformation, and should not be supplied for a conversion. + + + + + gml:coordinateOperationAccuracy is an association role to a DQ_PositionalAccuracy object as encoded in ISO/TS 19139, either referencing or containing the definition of that positional accuracy. That object contains an estimate of the impact of this coordinate operation on point accuracy. That is, it gives position error estimates for the target coordinates of this coordinate operation, assuming no errors in the source coordinates. + + + + + + + + + + + gml:sourceCRS is an association role to the source CRS (coordinate reference system) of this coordinate operation. + + + + + gml:targetCRS is an association role to the target CRS (coordinate reference system) of this coordinate operation. + + + + + gml:CoordinateOperationPropertyType is a property type for association roles to a coordinate operation, either referencing or containing the definition of that coordinate operation. + + + + + + + + + gml:AbstractSingleOperation is a single (not concatenated) coordinate operation. + + + + + gml:SingleOperationPropertyType is a property type for association roles to a single operation, either referencing or containing the definition of that single operation. + + + + + + + + + gm:AbstractGeneralConversion is an abstract operation on coordinates that does not include any change of datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters. The operationVersion, sourceCRS, and targetCRS elements are omitted in a coordinate conversion. +This abstract complex type is expected to be extended for well-known operation methods with many Conversion instances, in GML Application Schemas that define operation-method-specialized element names and contents. This conversion uses an operation method, usually with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references the "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include zero or more elements each named "uses...Value" that each use the type of an element substitutable for the "AbstractGeneralParameterValue" element. + + + + + + + + + + + + + + + + + + + + + + + gml:GeneralConversionPropertyType is a property type for association roles to a general conversion, either referencing or containing the definition of that conversion. + + + + + + + + + gml:AbstractGeneralTransformation is an abstract operation on coordinates that usually includes a change of Datum. The parameters of a coordinate transformation are empirically derived from data containing the coordinates of a series of points in both coordinate reference systems. This computational process is usually "over-determined", allowing derivation of error (or accuracy) estimates for the transformation. Also, the stochastic nature of the parameters may result in multiple (different) versions of the same coordinate transformation. The operationVersion, sourceCRS, and targetCRS proeprty elements are mandatory in a coordinate transformation. +This abstract complex type is expected to be extended for well-known operation methods with many Transformation instances, in Application Schemas that define operation-method-specialized value element names and contents. This transformation uses an operation method with associated parameter values. However, operation methods and parameter values are directly associated with concrete subtypes, not with this abstract type. All concrete types derived from this type shall extend this type to include a "usesMethod" element that references one "OperationMethod" element. Similarly, all concrete types derived from this type shall extend this type to include one or more elements each named "uses...Value" that each use the type of an element substitutable for the "AbstractGeneralParameterValue" element. + + + + + + + + + + + + + + + + + + + + + + + + + + gml:GeneralTransformationPropertyType is a property type for association roles to a general transformation, either referencing or containing the definition of that transformation. + + + + + + + + + + gml:ConcatenatedOperation is an ordered sequence of two or more coordinate operations. This sequence of operations is constrained by the requirement that the source coordinate reference system of step (n+1) must be the same as the target coordinate reference system of step (n). The source coordinate reference system of the first step and the target coordinate reference system of the last step are the source and target coordinate reference system associated with the concatenated operation. Instead of a forward operation, an inverse operation may be used for one or more of the operation steps mentioned above, if the inverse operation is uniquely defined by the forward operation. +The gml:coordOperation property elements are an ordered sequence of associations to the two or more operations used by this concatenated operation. The AggregationAttributeGroup should be used to specify that the coordOperation associations are ordered. + + + + + + + + + + + + + gml:coordOperation is an association role to a coordinate operation. + + + + + gml:ConcatenatedOperationPropertyType is a property type for association roles to a concatenated operation, either referencing or containing the definition of that concatenated operation. + + + + + + + + + gml:PassThroughOperation is a pass-through operation specifies that a subset of a coordinate tuple is subject to a specific coordinate operation. +The modifiedCoordinate property elements are an ordered sequence of positive integers defining the positions in a coordinate tuple of the coordinates affected by this pass-through operation. The AggregationAttributeGroup should be used to specify that the modifiedCoordinate elements are ordered. + + + + + + + + + + + + + + + + gml:modifiedCoordinate is a positive integer defining a position in a coordinate tuple. + + + + + gml:PassThroughOperationPropertyType is a property type for association roles to a pass through operation, either referencing or containing the definition of that pass through operation. + + + + + + + + + gml:Conversion is a concrete operation on coordinates that does not include any change of Datum. The best-known example of a coordinate conversion is a map projection. The parameters describing coordinate conversions are defined rather than empirically derived. Note that some conversions have no parameters. +This concrete complex type can be used without using a GML Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Conversion instance. +The usesValue property elements are an unordered list of composition associations to the set of parameter values used by this conversion operation. + + + + + + + + + + + + + + + gml:method is an association role to the operation method used by a coordinate operation. + + + + + gml:parameterValue is a composition association to a parameter value or group of parameter values used by a coordinate operation. + + + + + gml:ConversionPropertyType is a property type for association roles to a concrete general-purpose conversion, either referencing or containing the definition of that conversion. + + + + + + + + + gml:Transformation is a concrete object element derived from gml:GeneralTransformation (13.6.2.13). +This concrete object can be used for all operation methods, without using a GML Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one Transformation instance. +The parameterValue elements are an unordered list of composition associations to the set of parameter values used by this conversion operation. + + + + + + + + + + + + + + + gml:TransformationPropertyType is a property type for association roles to a transformation, either referencing or containing the definition of that transformation. + + + + + + + + + gml:AbstractGeneralParameterValue is an abstract parameter value or group of parameter values. +This abstract complexType is expected to be extended and restricted for well-known operation methods with many instances, in Application Schemas that define operation-method-specialized element names and contents. Specific parameter value elements are directly contained in concrete subtypes, not in this abstract type. All concrete types derived from this type shall extend this type to include one "...Value" element with an appropriate type, which should be one of the element types allowed in the ParameterValueType. In addition, all derived concrete types shall extend this type to include a "operationParameter" property element that references one element substitutable for the "OperationParameter" object element. + + + + + + + + gml:AbstractGeneralParameterValuePropertyType is a property type for inline association roles to a parameter value or group of parameter values, always containing the values. + + + + + + + + gml:ParameterValue is a parameter value, an ordered sequence of values, or a reference to a file of parameter values. This concrete complex type may be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents, especially for methods with only one instance. This complex type may be used, extended, or restricted for well-known operation methods, especially for methods with many instances. + + + + + + + + + + + + + + + + + + + + + + + + gml:value is a numeric value of an operation parameter, with its associated unit of measure. + + + + + gml:stringValue is a character string value of an operation parameter. A string value does not have an associated unit of measure. + + + + + gml:integerValue is a positive integer value of an operation parameter, usually used for a count. An integer value does not have an associated unit of measure. + + + + + gml:booleanValue is a boolean value of an operation parameter. A Boolean value does not have an associated unit of measure. + + + + + gml:valueList is an ordered sequence of two or more numeric values of an operation parameter list, where each value has the same associated unit of measure. An element of this type contains a space-separated sequence of double values. + + + + + gml:integerValueList is an ordered sequence of two or more integer values of an operation parameter list, usually used for counts. These integer values do not have an associated unit of measure. An element of this type contains a space-separated sequence of integer values. + + + + + gml:valueFile is a reference to a file or a part of a file containing one or more parameter values, each numeric value with its associated unit of measure. When referencing a part of a file, that file shall contain multiple identified parts, such as an XML encoded document. Furthermore, the referenced file or part of a file may reference another part of the same or different files, as allowed in XML documents. + + + + + gml:operationParameter is an association role to the operation parameter of which this is a value. + + + + + gml:ParameterValueGroup is a group of related parameter values. The same group can be repeated more than once in a Conversion, Transformation, or higher level ParameterValueGroup, if those instances contain different values of one or more parameterValues which suitably distinquish among those groups. This concrete complex type can be used for operation methods without using an Application Schema that defines operation-method-specialized element names and contents. This complex type may be used, extended, or restricted for well-known operation methods, especially for methods with only one instance. +The parameterValue elements are an unordered set of composition association roles to the parameter values and groups of values included in this group. + + + + + + + + + + + + + + + gml:group is an association role to the operation parameter group for which this element provides parameter values. + + + + + gml:OperationMethod is a method (algorithm or procedure) used to perform a coordinate operation. Most operation methods use a number of operation parameters, although some coordinate conversions use none. Each coordinate operation using the method assigns values to these parameters. +The parameter elements are an unordered list of associations to the set of operation parameters and parameter groups used by this operation method. + + + + + + + + + + + + + + + + + + + + gml:formulaCitation provides a reference to a publication giving the formula(s) or procedure used by an coordinate operation method. + + + + + + + + + + + gml:formula Formula(s) or procedure used by an operation method. The use of the codespace attribite has been deprecated. The property value shall be a character string. + + + + + gml:sourceDimensions is the number of dimensions in the source CRS of this operation method. + + + + + gml:targetDimensions is the number of dimensions in the target CRS of this operation method. + + + + + gml:parameter is an association to an operation parameter or parameter group. + + + + + gml:OperationMethodPropertyType is a property type for association roles to a concrete general-purpose operation method, either referencing or containing the definition of that method. + + + + + + + + + gml:GeneralOperationParameter is the abstract definition of a parameter or group of parameters used by an operation method. + + + + + + + + + + + + + + gml:minimumOccurs is the minimum number of times that values for this parameter group or parameter are required. If this attribute is omitted, the minimum number shall be one. + + + + + gml:AbstractGeneralOperationParameterPropertyType is a property type for association roles to an operation parameter or group, either referencing or containing the definition of that parameter or group. + + + + + + + + + gml:OperationParameter is the definition of a parameter used by an operation method. Most parameter values are numeric, but other types of parameter values are possible. This complex type is expected to be used or extended for all operation methods, without defining operation-method-specialized element names. + + + + + + + + + + + + gml:OperationParameterPropertyType is a property type for association roles to an operation parameter, either referencing or containing the definition of that parameter. + + + + + + + + + gml:OperationParameterGroup is the definition of a group of parameters used by an operation method. This complex type is expected to be used or extended for all applicable operation methods, without defining operation-method-specialized element names. +The generalOperationParameter elements are an unordered list of associations to the set of operation parameters that are members of this group. + + + + + + + + + + + + + + + gml:maximumOccurs is the maximum number of times that values for this parameter group may be included. If this attribute is omitted, the maximum number shall be one. + + + + + gml:OperationParameterPropertyType is a property type for association roles to an operation parameter group, either referencing or containing the definition of that parameter group. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/coordinateReferenceSystems.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateReferenceSystems.xsd new file mode 100644 index 0000000..72a6ced --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateReferenceSystems.xsd @@ -0,0 +1,373 @@ + + + + coordinateReferenceSystems.xsd + See ISO/DIS 19136 13.3. +The spatial-temporal coordinate reference systems schema components are divided into two logical parts. One part defines elements and types for XML encoding of abstract coordinate reference systems definitions. The larger part defines specialized constructs for XML encoding of definitions of the multiple concrete types of spatial-temporal coordinate reference systems. +These schema components encode the Coordinate Reference System packages of the UML Models of ISO 19111 Clause 8 and ISO/DIS 19136 D.3.10, with the exception of the abstract "SC_CRS" class. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + gml:AbstractSingleCRS implements a coordinate reference system consisting of one coordinate system and one datum (as opposed to a Compound CRS). + + + + + gml:SingleCRSPropertyType is a property type for association roles to a single coordinate reference system, either referencing or containing the definition of that coordinate reference system. + + + + + + + + + gml:AbstractGeneralDerivedCRS is a coordinate reference system that is defined by its coordinate conversion from another coordinate reference system. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + gml:conversion is an association role to the coordinate conversion used to define the derived CRS. + + + + + gml:CompundCRS is a coordinate reference system describing the position of points through two or more independent coordinate reference systems. It is associated with a non-repeating sequence of two or more instances of SingleCRS. + + + + + + + + + + + + + + + The gml:componentReferenceSystem elements are an ordered sequence of associations to all the component coordinate reference systems included in this compound coordinate reference system. The gml:AggregationAttributeGroup should be used to specify that the gml:componentReferenceSystem properties are ordered. + + + + + gml:CompoundCRSPropertyType is a property type for association roles to a compound coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + + gml:GeodeticCRS is a coordinate reference system based on a geodetic datum. + + + + + + + + + + + + + + + + + gml:ellipsoidalCS is an association role to the ellipsoidal coordinate system used by this CRS. + + + + + gml:cartesianCS is an association role to the Cartesian coordinate system used by this CRS. + + + + + gml:sphericalCS is an association role to the spherical coordinate system used by this CRS. + + + + + gml:geodeticDatum is an association role to the geodetic datum used by this CRS. + + + + + + gml:GeodeticCRSPropertyType is a property type for association roles to a geodetic coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:VerticalCRS is a 1D coordinate reference system used for recording heights or depths. Vertical CRSs make use of the direction of gravity to define the concept of height or depth, but the relationship with gravity may not be straightforward. By implication, ellipsoidal heights (h) cannot be captured in a vertical coordinate reference system. Ellipsoidal heights cannot exist independently, but only as an inseparable part of a 3D coordinate tuple defined in a geographic 3D coordinate reference system. + + + + + + + + + + + + + + + gml:verticalCS is an association role to the vertical coordinate system used by this CRS. + + + + + gml:verticalDatum is an association role to the vertical datum used by this CRS. + + + + + gml:VerticalCRSPropertyType is a property type for association roles to a vertical coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:ProjectedCRS is a 2D coordinate reference system used to approximate the shape of the earth on a planar surface, but in such a way that the distortion that is inherent to the approximation is carefully controlled and known. Distortion correction is commonly applied to calculated bearings and distances to produce values that are a close match to actual field values. + + + + + + + + + + + + + + + + + + gml:baseGeodeticCRS is an association role to the geodetic coordinate reference system used by this projected CRS. + + + + + gml:ProjectedCRSPropertyType is a property type for association roles to a projected coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:DerivedCRS is a single coordinate reference system that is defined by its coordinate conversion from another single coordinate reference system known as the base CRS. The base CRS can be a projected coordinate reference system, if this DerivedCRS is used for a georectified grid coverage as described in ISO 19123, Clause 8. + + + + + + + + + + + + + + + + gml:baseCRS is an association role to the coordinate reference system used by this derived CRS. + + + + + The gml:derivedCRSType property describes the type of a derived coordinate reference system. The required codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + An association role to the coordinate system used by this CRS. + + + + + gml:DerivedCRSPropertyType is a property type for association roles to a non-projected derived coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:EngineeringCRS is a contextually local coordinate reference system which can be divided into two broad categories: +- earth-fixed systems applied to engineering activities on or near the surface of the earth; +- CRSs on moving platforms such as road vehicles, vessels, aircraft, or spacecraft, see ISO 19111 8.3. + + + + + + + + + + + + + + + + + deprecated + + + + + + + + + + + gml:cylindricalCS is an association role to the cylindrical coordinate system used by this CRS. + + + + + gml:linearCS is an association role to the linear coordinate system used by this CRS. + + + + + gml:polarCS is an association role to the polar coordinate system used by this CRS. + + + + + gml:userDefinedCS is an association role to the user defined coordinate system used by this CRS. + + + + + gml:engineeringDatum is an association role to the engineering datum used by this CRS. + + + + + gml:EngineeringCRSPropertyType is a property type for association roles to an engineering coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:ImageCRS is an engineering coordinate reference system applied to locations in images. Image coordinate reference systems are treated as a separate sub-type because the definition of the associated image datum contains two attributes not relevant to other engineering datums. + + + + + + + + + + + + + + + + + + + gml:affineCS is an association role to the affine coordinate system used by this CRS. + + + + + gml:imageDatum is an association role to the image datum used by this CRS. + + + + + gml:ImageCRSPropertyType is a property type for association roles to an image coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + + + gml:TemporalCRS is a 1D coordinate reference system used for the recording of time. + + + + + + + + + + + + + + + + + + gml:timeCS is an association role to the time coordinate system used by this CRS. + + + + + gml:temporalDatum is an association role to the temporal datum used by this CRS. + + + + + gml:TemporalCRSPropertyType is a property type for association roles to a temporal coordinate reference system, either referencing or containing the definition of that reference system. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/coordinateSystems.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateSystems.xsd new file mode 100644 index 0000000..37627f2 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/coordinateSystems.xsd @@ -0,0 +1,297 @@ + + + + coordinateSystems.xsd + See ISO/DIS 19136 13.4. +The coordinate systems schema components can be divded into three logical parts, which define elements and types for XML encoding of the definitions of: +- Coordinate system axes +- Abstract coordinate system +- Multiple concrete types of spatial-temporal coordinate systems +These schema components encode the Coordinate System packages of the UML Models of ISO 19111 Clause 9 and ISO/DIS 19136 D.3.10. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + gml:CoordinateSystemAxis is a definition of a coordinate system axis. + + + + + + + + + + + + + + + The uom attribute provides an identifier of the unit of measure used for this coordinate system axis. The value of this coordinate in a coordinate tuple shall be recorded using this unit of measure, whenever those coordinates use a coordinate reference system that uses a coordinate system that uses this axis. + + + + + + + + gml:axisAbbrev is the abbreviation used for this coordinate system axis; this abbreviation is also used to identify the coordinates in the coordinate tuple. The codeSpace attribute may reference a source of more information on a set of standardized abbreviations, or on this abbreviation. + + + + + gml:axisDirection is the direction of this coordinate system axis (or in the case of Cartesian projected coordinates, the direction of this coordinate system axis at the origin). +Within any set of coordinate system axes, only one of each pair of terms may be used. For earth-fixed CRSs, this direction is often approximate and intended to provide a human interpretable meaning to the axis. When a geodetic datum is used, the precise directions of the axes may therefore vary slightly from this approximate direction. +The codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + The gml:minimumValue and gml:maximumValue properties allow the specification of minimum and maximum value normally allowed for this axis, in the unit of measure for the axis. For a continuous angular axis such as longitude, the values wrap-around at this value. Also, values beyond this minimum/maximum can be used for specified purposes, such as in a bounding box. A value of minus infinity shall be allowed for the gml:minimumValue element, a value of plus infiniy for the gml:maximumValue element. If these elements are omitted, the value is unspecified. + + + + + The gml:minimumValue and gml:maximumValue properties allow the specification of minimum and maximum value normally allowed for this axis, in the unit of measure for the axis. For a continuous angular axis such as longitude, the values wrap-around at this value. Also, values beyond this minimum/maximum can be used for specified purposes, such as in a bounding box. A value of minus infinity shall be allowed for the gml:minimumValue element, a value of plus infiniy for the gml:maximumValue element. If these elements are omitted, the value is unspecified. + + + + + gml:rangeMeaning describes the meaning of axis value range specified by gml:minimumValue and gml:maximumValue. This element shall be omitted when both gml:minimumValue and gml:maximumValue are omitted. This element should be included when gml:minimumValue and/or gml:maximumValue are included. If this element is omitted when the gml:minimumValue and/or gml:maximumValue are included, the meaning is unspecified. The codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + gml:CoordinateSystemAxisPropertyType is a property type for association roles to a coordinate system axis, either referencing or containing the definition of that axis. + + + + + + + + + gml:AbstractCoordinateSystem is a coordinate system (CS) is the non-repeating sequence of coordinate system axes that spans a given coordinate space. A CS is derived from a set of mathematical rules for specifying how coordinates in a given space are to be assigned to points. The coordinate values in a coordinate tuple shall be recorded in the order in which the coordinate system axes associations are recorded. This abstract complex type shall not be used, extended, or restricted, in an Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + The gml:axis property is an association role (ordered sequence) to the coordinate system axes included in this coordinate system. The coordinate values in a coordinate tuple shall be recorded in the order in which the coordinate system axes associations are recorded, whenever those coordinates use a coordinate reference system that uses this coordinate system. The gml:AggregationAttributeGroup should be used to specify that the axis objects are ordered. + + + + + gml:CoordinateSystemPropertyType is a property type for association roles to a coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:EllipsoidalCS is a two- or three-dimensional coordinate system in which position is specified by geodetic latitude, geodetic longitude, and (in the three-dimensional case) ellipsoidal height. An EllipsoidalCS shall have two or three gml:axis property elements; the number of associations shall equal the dimension of the CS. + + + + + + + + + + gml:EllipsoidalCSPropertyType is a property type for association roles to an ellipsoidal coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:CartesianCS is a 1-, 2-, or 3-dimensional coordinate system. In the 1-dimensional case, it contains a single straight coordinate axis. In the 2- and 3-dimensional cases gives the position of points relative to orthogonal straight axes. In the multi-dimensional case, all axes shall have the same length unit of measure. A CartesianCS shall have one, two, or three gml:axis property elements. + + + + + + + + + + gml:CartesianCSPropertyType is a property type for association roles to a Cartesian coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:VerticalCS is a one-dimensional coordinate system used to record the heights or depths of points. Such a coordinate system is usually dependent on the Earth's gravity field, perhaps loosely as when atmospheric pressure is the basis for the vertical coordinate system axis. A VerticalCS shall have one gml:axis property element. + + + + + + + + + + gml:VerticalCSPropertyType is a property type for association roles to a vertical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:TimeCS is a one-dimensional coordinate system containing a time axis, used to describe the temporal position of a point in the specified time units from a specified time origin. A TimeCS shall have one gml:axis property element. + + + + + + + + + + gml:TimeCSPropertyType is a property type for association roles to a time coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:LinearCS is a one-dimensional coordinate system that consists of the points that lie on the single axis described. The associated coordinate is the distance – with or without offset – from the specified datum to the point along the axis. A LinearCS shall have one gml:axis property element. + + + + + + + + + + gml:LinearCSPropertyType is a property type for association roles to a linear coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:UserDefinedCS is a two- or three-dimensional coordinate system that consists of any combination of coordinate axes not covered by any other coordinate system type. A UserDefinedCS shall have two or three gml:axis property elements; the number of property elements shall equal the dimension of the CS. + + + + + + + + + + gml:UserDefinedCSPropertyType is a property type for association roles to a user-defined coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:SphericalCS is a three-dimensional coordinate system with one distance measured from the origin and two angular coordinates. A SphericalCS shall have three gml:axis property elements. + + + + + + + + + + gml:SphericalCSPropertyType is property type for association roles to a spherical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:PolarCS ia s two-dimensional coordinate system in which position is specified by the distance from the origin and the angle between the line from the origin to a point and a reference direction. A PolarCS shall have two gml:axis property elements. + + + + + + + + + + gml:PolarCSPropertyType is a property type for association roles to a polar coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:CylindricalCS is a three-dimensional coordinate system consisting of a polar coordinate system extended by a straight coordinate axis perpendicular to the plane spanned by the polar coordinate system. A CylindricalCS shall have three gml:axis property elements. + + + + + + + + + + gml:CylindricalCSPropertyType is a property type for association roles to a cylindrical coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + + + gml:AffineCS is a two- or three-dimensional coordinate system with straight axes that are not necessarily orthogonal. An AffineCS shall have two or three gml:axis property elements; the number of property elements shall equal the dimension of the CS. + + + + + + + + + + gml:AffineCSPropertyType is a property type for association roles to an affine coordinate system, either referencing or containing the definition of that coordinate system. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/coverage.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/coverage.xsd new file mode 100644 index 0000000..a1bbfa4 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/coverage.xsd @@ -0,0 +1,292 @@ + + + + coverage.xsd + See ISO/DIS 19136 20.3. +A coverage incorporates a mapping from a spatiotemporal domain to a range set, the latter providing the set in which the attribute values live. The range set may be an arbitrary set including discrete lists, integer or floating point ranges, and multi-dimensional vector spaces. +A coverage can be viewed as the graph of the coverage function f:A à B, that is as the set of ordered pairs {(x, f(x)) | where x is in A}. This view is especially applicable to the GML encoding of a coverage. In the case of a discrete coverage, the domain set A is partitioned into a collection of subsets (typically a disjoint collection) A = UAi and the function f is constant on each Ai. For a spatial domain, the Ai are geometry elements, hence the coverage can be viewed as a collection of (geometry,value) pairs, where the value is an element of the range set. If the spatial domain A is a topological space then the coverage can be viewed as a collection of (topology,value) pairs, where the topology element in the pair is a topological n-chain (in GML terms this is a gml:TopoPoint, gml:TopoCurve, gml:TopoSurface or gml:TopoSolid). +A coverage is implemented as a GML feature. We can thus speak of a "temperature distribution feature", or a "remotely sensed image feature", or a "soil distribution feature". +As is the case for any GML object, a coverage object may also be the value of a property of a feature. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + The base type for coverages is gml:AbstractCoverageType. The basic elements of a coverage can be seen in this content model: the coverage contains gml:domainSet and gml:rangeSet properties. The gml:domainSet property describes the domain of the coverage and the gml:rangeSet property describes the range of the coverage. + + + + + + + + + + + + + This element serves as the head of a substitution group which may contain any coverage whose type is derived from gml:AbstractCoverageType. It may act as a variable in the definition of content models where it is required to permit any coverage to be valid. + + + + + + + + + + + + + + A discrete coverage consists of a domain set, range set and optionally a coverage function. The domain set consists of either spatial or temporal geometry objects, finite in number. The range set is comprised of a finite number of attribute values each of which is associated to every direct position within any single spatiotemporal object in the domain. In other words, the range values are constant on each spatiotemporal object in the domain. This coverage function maps each element from the coverage domain to an element in its range. The coverageFunction element describes the mapping function. +This element serves as the head of a substitution group which may contain any discrete coverage whose type is derived from gml:DiscreteCoverageType. + + + + + + + + + + + + + + A continuous coverage as defined in ISO 19123 is a coverage that can return different values for the same feature attribute at different direct positions within a single spatiotemporal object in its spatiotemporal domain. The base type for continuous coverages is AbstractContinuousCoverageType. +The coverageFunction element describes the mapping function. +The abstract element gml:AbstractContinuousCoverage serves as the head of a substitution group which may contain any continuous coverage whose type is derived from gml:AbstractContinuousCoverageType. + + + + + The gml:domainSet property element describes the spatio-temporal region of interest, within which the coverage is defined. Its content model is given by gml:DomainSetType. +The value of the domain is thus a choice between a gml:AbstractGeometry and a gml:AbstractTimeObject. In the instance these abstract elements will normally be substituted by a geometry complex or temporal complex, to represent spatial coverages and time-series, respectively. +The presence of the gml:AssociationAttributeGroup means that domainSet follows the usual GML property model and may use the xlink:href attribute to point to the domain, as an alternative to describing the domain inline. Ownership semantics may be provided using the gml:OwnershipAttributeGroup. + + + + + + + + + + + + + + + + The gml:rangeSet property element contains the values of the coverage (sometimes called the attribute values). Its content model is given by gml:RangeSetType. +This content model supports a structural description of the range. The semantic information describing the range set is embedded using a uniform method, as part of the explicit values, or as a template value accompanying the representation using gml:DataBlock and gml:File. +The values from each component (or "band") in the range may be encoded within a gml:ValueArray element or a concrete member of the gml:AbstractScalarValueList substitution group . Use of these elements satisfies the value-type homogeneity requirement. + + + + + + + + + + + + + gml:DataBlock describes the Range as a block of text encoded values similar to a Common Separated Value (CSV) representation. +The range set parameterization is described by the property gml:rangeParameters. + + + + + + + + + + + + + + + gml:CoordinatesType consists of a list of coordinate tuples, with each coordinate tuple separated by the ts or tuple separator (whitespace), and each coordinate in the tuple by the cs or coordinate separator (comma). +The gml:tupleList encoding is effectively "band-interleaved". + + + + + gml:doubleOrNilReasonList consists of a list of gml:doubleOrNilReason values, each separated by a whitespace. The gml:doubleOrNilReason values are grouped into tuples where the dimension of each tuple in the list is equal to the number of range parameters. + + + + + for efficiency reasons, GML also provides a means of encoding the range set in an arbitrary external encoding, such as a binary file. This encoding may be "well-known" but this is not required. This mode uses the gml:File element. +The values of the coverage (attribute values in the range set) are transmitted in a external file that is referenced from the XML structure described by gml:FileType. The external file is referenced by the gml:fileReference property that is an anyURI (the gml:fileName property has been deprecated). This means that the external file may be located remotely from the referencing GML instance. +The gml:compression property points to a definition of a compression algorithm through an anyURI. This may be a retrievable, computable definition or simply a reference to an unambiguous name for the compression method. +The gml:mimeType property points to a definition of the file mime type. +The gml:fileStructure property is defined by a codelist. Note further that all values shall be enclosed in a single file. Multi-file structures for values are not supported in GML. +The semantics of the range set is described as above using the gml:rangeParameters property. +Note that if any compression algorithm is applied, the structure above applies only to the pre-compression or post-decompression structure of the file. +Note that the fields within a record match the gml:valueComponents of the gml:CompositeValue in document order. + + + + + + + + + deprecated + + + + + + + + + + + + The gml:coverageFunction property describes the mapping function from the domain to the range of the coverage. +The value of the CoverageFunction is one of gml:CoverageMappingRule and gml:GridFunction. +If the gml:coverageFunction property is omitted for a gridded coverage (including rectified gridded coverages) the gml:startPoint is assumed to be the value of the gml:low property in the gml:Grid geometry, and the gml:sequenceRule is assumed to be linear and the gml:axisOrder property is assumed to be "+1 +2". + + + + + + + + + + + + gml:CoverageMappingRule provides a formal or informal description of the coverage function. +The mapping rule may be defined as an in-line string (gml:ruleDefinition) or via a remote reference through xlink:href (gml:ruleReference). +If no rule name is specified, the default is 'Linear' with respect to members of the domain in document order. + + + + + + + + + + + gml:GridFunction provides an explicit mapping rule for grid geometries, i.e. the domain shall be a geometry of type grid. It describes the mapping of grid posts (discrete point grid coverage) or grid cells (discrete surface coverage) to the values in the range set. +The gml:startPoint is the index position of a point in the grid that is mapped to the first point in the range set (this is also the index position of the first grid post). If the gml:startPoint property is omitted the gml:startPoint is assumed to be equal to the value of gml:low in the gml:Grid geometry. Subsequent points in the mapping are determined by the value of the gml:sequenceRule. + + + + + + + + + + + The gml:SequenceRuleType is derived from the gml:SequenceRuleEnumeration through the addition of an axisOrder attribute. The gml:SequenceRuleEnumeration is an enumerated type. The rule names are defined in ISO 19123. If no rule name is specified the default is "Linear". + + + + + + deprecated + + + + + + + + + + + + + + + + + + + The different values in a gml:AxisDirectionList indicate the incrementation order to be used on all axes of the grid. Each axis shall be mentioned once and only once. + + + + + + The value of a gml:AxisDirection indicates the incrementation order to be used on an axis of the grid. + + + + + + + + In a gml:MultiPointCoverage the domain set is a gml:MultiPoint, that is a collection of arbitrarily distributed geometric points. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiPoint. +In a gml:MultiPointCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the points of the gml:MultiPoint are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the points of the gml:MultiPoint are mapped to the members of the composite value in document order. +- For gml:File encodings the points of the gml:MultiPoint are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiCurveCoverage the domain is partioned into a collection of curves comprising a gml:MultiCurve. The coverage function then maps each curve in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiCurve. +In a gml:MultiCurveCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the curves of the gml:MultiCurve are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the curves of the gml:MultiCurve are mapped to the members of the composite value in document order. +- For gml:File encodings the curves of the gml:MultiCurve are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiSurfaceCoverage the domain is partioned into a collection of surfaces comprising a gml:MultiSurface. The coverage function than maps each surface in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiSurface. +In a gml:MultiSurfaceCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the surfaces of the gml:MultiSurface are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the surfaces of the gml:MultiSurface are mapped to the members of the composite value in document order. +- For gml:File encodings the surfaces of the gml:MultiSurface are mapped to the records of the file in sequential order. + + + + + + In a gml:MultiSolidCoverage the domain is partioned into a collection of solids comprising a gml:MultiSolid. The coverage function than maps each solid in the collection to a value in the range set. +The content model is identical with gml:DiscreteCoverageType, but that gml:domainSet shall have values gml:MultiSolid. +In a gml:MultiSolidCoverage the mapping from the domain to the range is straightforward. +- For gml:DataBlock encodings the solids of the gml:MultiSolid are mapped in document order to the tuples of the data block. +- For gml:CompositeValue encodings the solids of the gml:MultiSolid are mapped to the members of the composite value in document order. +- For gml:File encodings the solids of the gml:MultiSolid are mapped to the records of the file in sequential order. + + + + + + A gml:GriddedCoverage is a discrete point coverage in which the domain set is a geometric grid of points. +Note that this is the same as the gml:MultiPointCoverage except that we have a gml:Grid to describe the domain. +The simple gridded coverage is not geometrically referenced and hence no geometric positions are assignable to the points in the grid. Such geometric positioning is introduced in the gml:RectifiedGridCoverage. + + + + + The gml:RectifiedGridCoverage is a discrete point coverage based on a rectified grid. It is similar to the grid coverage except that the points of the grid are geometrically referenced. The rectified grid coverage has a domain that is a gml:RectifiedGrid geometry. + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/datums.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/datums.xsd new file mode 100644 index 0000000..a62b866 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/datums.xsd @@ -0,0 +1,287 @@ + + + + + datums.xsd + See ISO/DIS 19136 13.5 +The datums schema components can be divided into three logical parts, which define elements and types for XML encoding of the definitions of: +- Abstract datum +- Geodetic datums, including ellipsoid and prime meridian +- Multiple other concrete types of spatial or temporal datums +These schema components encode the Datum packages of the UML Models of ISO 19111 Clause 10 and ISO/DIS 19136 D.3.10. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + A gml:AbstractDatum specifies the relationship of a coordinate system to the earth, thus creating a coordinate reference system. A datum uses a parameter or set of parameters that determine the location of the origin of the coordinate reference system. Each datum subtype may be associated with only specific types of coordinate systems. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + + + gml:anchorDefinition is a description, possibly including coordinates, of the definition used to anchor the datum to the Earth. Also known as the "origin", especially for engineering and image datums. The codeSpace attribute may be used to reference a source of more detailed on this point or surface, or on a set of such descriptions. +- For a geodetic datum, this point is also known as the fundamental point, which is traditionally the point where the relationship between geoid and ellipsoid is defined. In some cases, the "fundamental point" may consist of a number of points. In those cases, the parameters defining the geoid/ellipsoid relationship have been averaged for these points, and the averages adopted as the datum definition. +- For an engineering datum, the anchor definition may be a physical point, or it may be a point with defined coordinates in another CRS.may +- For an image datum, the anchor definition is usually either the centre of the image or the corner of the image. +- For a temporal datum, this attribute is not defined. Instead of the anchor definition, a temporal datum carries a separate time origin of type DateTime. + + + + + gml:realizationEpoch is the time after which this datum definition is valid. See ISO 19111 Table 32 for details. + + + + + gml:DatumPropertyType is a property type for association roles to a datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:GeodeticDatum is a geodetic datum defines the precise location and orientation in 3-dimensional space of a defined ellipsoid (or sphere), or of a Cartesian coordinate system centered in this ellipsoid (or sphere). + + + + + + + + + + + + + + + gml:primeMeridian is an association role to the prime meridian used by this geodetic datum. + + + + + gml:ellipsoid is an association role to the ellipsoid used by this geodetic datum. + + + + + gml:GeodeticDatumPropertyType is a property type for association roles to a geodetic datum, either referencing or containing the definition of that datum. + + + + + + + + + A gml:Ellipsoid is a geometric figure that may be used to describe the approximate shape of the earth. In mathematical terms, it is a surface formed by the rotation of an ellipse about its minor axis. + + + + + + + + + + + + + + + gml:semiMajorAxis specifies the length of the semi-major axis of the ellipsoid, with its units. Uses the MeasureType with the restriction that the unit of measure referenced by uom must be suitable for a length, such as metres or feet. + + + + + gml:secondDefiningParameter is a property containing the definition of the second parameter that defines the shape of an ellipsoid. An ellipsoid requires two defining parameters: semi-major axis and inverse flattening or semi-major axis and semi-minor axis. When the reference body is a sphere rather than an ellipsoid, only a single defining parameter is required, namely the radius of the sphere; in that case, the semi-major axis "degenerates" into the radius of the sphere. +The inverseFlattening element contains the inverse flattening value of the ellipsoid. This value is a scale factor (or ratio). It uses gml:LengthType with the restriction that the unit of measure referenced by the uom attribute must be suitable for a scale factor, such as percent, permil, or parts-per-million. +The semiMinorAxis element contains the length of the semi-minor axis of the ellipsoid. When the isSphere element is included, the ellipsoid is degenerate and is actually a sphere. The sphere is completely defined by the semi-major axis, which is the radius of the sphere. + + + + + + + + + + + + + + + + + + + gml:EllipsoidPropertyType is a property type for association roles to an ellipsoid, either referencing or containing the definition of that ellipsoid. + + + + + + + + + A gml:PrimeMeridian defines the origin from which longitude values are determined. The default value for the prime meridian gml:identifier value is "Greenwich". + + + + + + + + + + + + + + gml:greenwichLongitude is the longitude of the prime meridian measured from the Greenwich meridian, positive eastward. If the value of the prime meridian "name" is "Greenwich" then the value of greenwichLongitude shall be 0 degrees. + + + + + gml:PrimeMeridianPropertyType is a property type for association roles to a prime meridian, either referencing or containing the definition of that meridian. + + + + + + + + + gml:EngineeringDatum defines the origin of an engineering coordinate reference system, and is used in a region around that origin. This origin may be fixed with respect to the earth (such as a defined point at a construction site), or be a defined point on a moving vehicle (such as on a ship or satellite). + + + + + + + + + + gml:EngineeringDatumPropertyType is a property type for association roles to an engineering datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:ImageDatum defines the origin of an image coordinate reference system, and is used in a local context only. For an image datum, the anchor definition is usually either the centre of the image or the corner of the image. For more information, see ISO 19111 B.3.5. + + + + + + + + + + + + + + gml:pixelInCell is a specification of the way an image grid is associated with the image data attributes. The required codeSpace attribute shall reference a source of information specifying the values and meanings of all the allowed string values for this property. + + + + + gml:ImageDatumPropertyType is a property type for association roles to an image datum, either referencing or containing the definition of that datum. + + + + + + + + + gml:VerticalDatum is a textual description and/or a set of parameters identifying a particular reference level surface used as a zero-height surface, including its position with respect to the Earth for any of the height types recognized by this International Standard. + + + + + + + + + + gml:VerticalDatumPropertyType is property type for association roles to a vertical datum, either referencing or containing the definition of that datum. + + + + + + + + + A gml:TemporalDatum defines the origin of a Temporal Reference System. This type omits the "anchorDefinition" and "realizationEpoch" elements and adds the "origin" element with the dateTime type. + + + + + + + + + + + + + + The TemporalDatumBaseType partially defines the origin of a temporal coordinate reference system. This type restricts the AbstractDatumType to remove the "anchorDefinition" and "realizationEpoch" elements. + + + + + + + + + + + + + + + + + + + + gml:origin is the date and time origin of this temporal datum. + + + + + gml:TemporalDatumPropertyType is a property type for association roles to a temporal datum, either referencing or containing the definition of that datum. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/defaultStyle.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/defaultStyle.xsd new file mode 100644 index 0000000..3a4635d --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/defaultStyle.xsd @@ -0,0 +1,453 @@ + + + + defaultStyle.xsd + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + Top-level property. Used in application schemas to "attach" the styling information to GML data. The link between the data and the style should be established through this property only. + + + + + + [complexType of] Top-level property. Used in application schemas to "attach" the styling information to GML data. The link between the data and the style should be established through this property only. + + + + + + + + + + + The value of the top-level property. It is an abstract element. Used as the head element of the substitution group for extensibility purposes. + + + + + + [complexType of] The value of the top-level property. It is an abstract element. Used as the head element of the substitution group for extensibility purposes. + + + + + + + + + Predefined concrete value of the top-level property. Encapsulates all other styling information. + + + + + + [complexType of] Predefined concrete value of the top-level property. Encapsulates all other styling information. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for features. + + + + + + [complexType of] The style descriptor for features. + + + + + + + + + + + + + + + + + + + Used to specify the grammar of the feature query mechanism. + + + + + + + + + + + Base complex type for geometry, topology, label and graph styles. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for geometries of a feature. + + + + + + [complexType of] The style descriptor for geometries of a feature. + + + + + + + + + deprecated + Deprecated in GML version 3.1.0. Use symbol with inline content instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for topologies of a feature. Describes individual topology elements styles. + + + + + + [complexType of] The style descriptor for topologies of a feature. Describes individual topology elements styles. + + + + + + + + + deprecated + Deprecated in GML version 3.1.0. Use symbol with inline content instead. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for labels of a feature, geometry or topology. + + + + + + [complexType of] The style descriptor for labels of a feature, geometry or topology. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The style descriptor for a graph consisting of a number of features. Describes graph-specific style attributes. + + + + + + [complexType of] The style descriptor for a graph consisting of a number of features. Describes graph-specific style attributes. + + + + + + + + + + + + + + + + + + + + + The symbol property. Extends the gml:AssociationType to allow for remote referencing of symbols. + + + + + + [complexType of] The symbol property. Allows for remote referencing of symbols. + + + + + + + + + + + + + Used to specify the type of the symbol used. + + + + + + + + + + + Label is mixed -- composed of text and XPath expressions used to extract the useful information from the feature. + + + + + + + + + + Defines the geometric transformation of entities. There is no particular grammar defined for this value. + + + + + + Used to vary individual graphic parameters and attributes of the style, symbol or text. + + + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + Graph-specific styling property. + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/deprecatedTypes.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/deprecatedTypes.xsd new file mode 100644 index 0000000..7dbd79b --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/deprecatedTypes.xsd @@ -0,0 +1,1133 @@ + + + + deprecatedTypes.xsd + All global schema components that are part of the GML schema, but were deprecated. See Annex I. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + deprecated + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + + + + + + + + + + + + + + + + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + + + deprecated + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/dictionary.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/dictionary.xsd new file mode 100644 index 0000000..8d6f94a --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/dictionary.xsd @@ -0,0 +1,90 @@ + + + + dictionary.xsd + See ISO/DIS 19136 Clause 16. +Many applications require definitions of terms which are used within instance documents as the values of certain properties or as reference information to tie properties to standard information values in some way. Units of measure and descriptions of measurable phenomena are two particular examples. +It will often be convenient to use definitions provided by external authorities. These may already be packaged for delivery in various ways, both online and offline. In order that they may be referred to from GML documents it is generally necessary that a URI be available for each definition. Where this is the case then it is usually preferable to refer to these directly. +Alternatively, it may be convenient or necessary to capture definitions in XML, either embedded within an instance document containing features or as a separate document. The definitions may be transcriptions from an external source, or may be new definitions for a local purpose. In order to support this case, some simple components are provided in GML in the form of +- a generic gml:Definition, which may serve as the basis for more specialized definitions +- a generic gml:Dictionary, which allows a set of definitions or references to definitions to be collected +These components may be used directly, but also serve as the basis for more specialised definition elements in GML, in particular: coordinate operations, coordinate reference systems, datums, temporal reference systems, and units of measure. +Note that the GML definition and dictionary components implement a simple nested hierarchy of definitions with identifiers. The latter provide handles which may be used in the description of more complex relationships between terms. However, the GML dictionary components are not intended to provide direct support for complex taxonomies, ontologies or thesauri. Specialised XML tools are available to satisfy the more sophisticated requirements. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + The basic gml:Definition element specifies a definition, which can be included in or referenced by a dictionary. +The content model for a generic definition is a derivation from gml:AbstractGMLType. +The gml:description property element shall hold the definition if this can be captured in a simple text string, or the gml:descriptionReference property element may carry a link to a description elsewhere. +The gml:identifier element shall provide one identifier identifying this definition. The identifier shall be unique within the dictionaries using this definition. +The gml:name elements shall provide zero or more terms and synonyms for which this is the definition. +The gml:remarks element shall be used to hold additional textual information that is not conceptually part of the definition but is useful in understanding the definition. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Sets of definitions may be collected into dictionaries or collections. +A gml:Dictionary is a non-abstract collection of definitions. +The gml:Dictionary content model adds a list of gml:dictionaryEntry properties that contain or reference gml:Definition objects. A database handle (gml:id attribute) is required, in order that this collection may be referred to. The standard gml:identifier, gml:description, gml:descriptionReference and gml:name properties are available to reference or contain more information about this dictionary. The gml:description and gml:descriptionReference property elements may be used for a description of this dictionary. The derived gml:name element may be used for the name(s) of this dictionary. for remote definiton references gml:dictionaryEntry shall be used. If a Definition object contained within a Dictionary uses the descriptionReference property to refer to a remote definition, then this enables the inclusion of a remote definition in a local dictionary, giving a handle and identifier in the context of the local dictionary. + + + + + + + + + + + + + + + + This property element contains or refers to the definitions which are members of a dictionary. +The content model follows the standard GML property pattern, so a gml:dictionaryEntry may either contain or refer to a single gml:Definition. Since gml:Dictionary is substitutable for gml:Definition, the content of an entry may itself be a lower level dictionary. +Note that if the value is provided by reference, this definition does not carry a handle (gml:id) in this context, so does not allow external references to this specific definition in this context. When used in this way the referenced definition will usually be in a dictionary in the same XML document. + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/direction.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/direction.xsd new file mode 100644 index 0000000..8b0f7f5 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/direction.xsd @@ -0,0 +1,84 @@ + + + + direction.xsd + See ISO/DIS 19136 Clause 18. +The direction schema components provide the GML Application Schema developer with a standard property element to describe direction, and associated objects that may be used to express orientation, direction, heading, bearing or other directional aspects of geographic features. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + The property gml:direction is intended as a pre-defined property expressing a direction to be assigned to features defined in a GML application schema. + + + + + + + + + + + + + + + + Direction vectors are specified by providing components of a vector. + + + + + + deprecated + + + + + + + + + direction descriptions are specified by a compass point code, a keyword, a textual description or a reference to a description. +A gml:compassPoint is specified by a simple enumeration. +In addition, thre elements to contain text-based descriptions of direction are provided. +If the direction is specified using a term from a list, gml:keyword should be used, and the list indicated using the value of the codeSpace attribute. +if the direction is decribed in prose, gml:direction or gml:reference should be used, allowing the value to be included inline or by reference. + + + + + + + + + + + These directions are necessarily approximate, giving direction with a precision of 22.5°. It is thus generally unnecessary to specify the reference frame, though this may be detailed in the definition of a GML application language. + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/dynamicFeature.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/dynamicFeature.xsd new file mode 100644 index 0000000..d755067 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/dynamicFeature.xsd @@ -0,0 +1,109 @@ + + + + dynamicFeature.xsd + See ISO/DIS 19136 15.6. +A number of types and relationships are defined to represent the time-varying properties of geographic features. +In a comprehensive treatment of spatiotemporal modeling, Langran (see Bibliography) distinguished three principal temporal entities: states, events, and evidence; the schema specified in the following Subclauses incorporates elements for each. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data. The remote link attributes of the gml:dataSource element have been deprecated along with its current type. + + + + + Evidence is represented by a simple gml:dataSource or gml:dataSourceReference property that indicates the source of the temporal data. + + + + + A convenience group. This allows an application schema developer to include dynamic properties in a content model in a standard fashion. + + + + + + + + + + + States are captured by time-stamped instances of a feature. The content model extends the standard gml:AbstractFeatureType with the gml:dynamicProperties model group. +Each time-stamped instance represents a 'snapshot' of a feature. The dynamic feature classes will normally be extended to suit particular applications. A dynamic feature bears either a time stamp or a history. + + + + + + + + + + + + A gml:DynamicFeatureCollection is a feature collection that has a gml:validTime property (i.e. is a snapshot of the feature collection) or which has a gml:history property that contains one or more gml:AbstractTimeSlices each of which contain values of the time varying properties of the feature collection. Note that the gml:DynamicFeatureCollection may be one of the following: +1. A feature collection which consists of static feature members (members do not change in time) but which has properties of the collection object as a whole that do change in time . +2. A feature collection which consists of dynamic feature members (the members are gml:DynamicFeatures) but which also has properties of the collection as a whole that vary in time. + + + + + + + + + + + + + + + + + + + + + + + + + To describe an event — an action that occurs at an instant or over an interval of time — GML provides the gml:AbtractTimeSlice element. A timeslice encapsulates the time-varying properties of a dynamic feature -- it shall be extended to represent a time stamped projection of a specific feature. The gml:dataSource property describes how the temporal data was acquired. +A gml:AbstractTimeSlice instance is a GML object that encapsulates updates of the dynamic—or volatile—properties that reflect some change event; it thus includes only those feature properties that have actually changed due to some process. +gml:AbstractTimeSlice basically provides a facility for attribute-level time stamping, in contrast to the object-level time stamping of dynamic feature instances. +The time slice can thus be viewed as event or process-oriented, whereas a snapshot is more state or structure-oriented. A timeslice has richer causality, whereas a snapshot merely portrays the status of the whole. + + + + + + + + + + + + + + + + A generic sequence of events constitute a gml:history of an object. +The gml:history element contains a set of elements in the substitution group headed by the abstract element gml:AbstractTimeSlice, representing the time-varying properties of interest. The history property of a dynamic feature associates a feature instance with a sequence of time slices (i.e. change events) that encapsulate the evolution of the feature. + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/feature.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/feature.xsd new file mode 100644 index 0000000..1892ef6 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/feature.xsd @@ -0,0 +1,94 @@ + + + + feature.xsd + See ISO/DIS 19136 Clause 9. +A GML feature is a (representation of a) identifiable real-world object in a selected domain of discourse. The feature schema provides a framework for the creation of GML features and feature collections. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + The basic feature model is given by the gml:AbstractFeatureType. +The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType. +The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location. +The value of the gml:location property describes the extent, position or relative location of the feature. + + + + + + + + + + + + + This abstract element serves as the head of a substitution group which may contain any elements whose content model is derived from gml:AbstractFeatureType. This may be used as a variable in the construction of content models. +gml:AbstractFeature may be thought of as "anything that is a GML feature" and may be used to define variables or templates in which the value of a GML property is "any feature". This occurs in particular in a GML feature collection where the feature member properties contain one or multiple copies of gml:AbstractFeature respectively. + + + + + + + + + + + + This property describes the minimum bounding box or rectangle that encloses the entire feature. + + + + + + + + + + + + + + gml:EnvelopeWithTimePeriod is provided for envelopes that include a temporal extent. It adds two time position properties, gml:beginPosition and gml:endPosition, which describe the extent of a time-envelope. +Since gml:EnvelopeWithTimePeriod is assigned to the substitution group headed by gml:Envelope, it may be used whenever gml:Envelope is valid. + + + + + + + + + + + + + + + + The gml:locationName property element is a convenience property where the text value describes the location of the feature. If the location names are selected from a controlled list, then the list shall be identified in the codeSpace attribute. + + + + + The gml:locationReference property element is a convenience property where the text value referenced by the xlink:href attribute describes the location of the feature. + + + + + To create a collection of GML features, a property type shall be derived by extension from gml:AbstractFeatureMemberType. +By default, this abstract property type does not imply any ownership of the features in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of a feature in the collection. A collection shall not own a feature already owned by another object. + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/geometryAggregates.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/geometryAggregates.xsd new file mode 100644 index 0000000..9ffbdc0 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/geometryAggregates.xsd @@ -0,0 +1,197 @@ + + + + geometryAggregates.xsd + See ISO/DIS 19136 12.3. +Geometric aggregates (i.e. instances of a subtype of gml:AbstractGeometricAggregateType) are arbitrary aggregations of geometry elements. They are not assumed to have any additional internal structure and are used to "collect" pieces of geometry of a specified type. Application schemas may use aggregates for features that use multiple geometric objects in their representations. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + + + + + gml:AbstractGeometricAggregate is the abstract head of the substitution group for all geometric aggregates. + + + + + + + + + + + + + + + gml:MultiGeometry is a collection of one or more GML geometry objects of arbitrary type. +The members of the geometric aggregate may be specified either using the "standard" property (gml:geometryMember) or the array property (gml:geometryMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a geometry element via the XLink-attributes or contains the geometry element. + + + + + This property element contains a list of geometry elements. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a geometric aggregate as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiPoint consists of one or more gml:Points. +The members of the geometric aggregate may be specified either using the "standard" property (gml:pointMember) or the array property (gml:pointMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a Point via the XLink-attributes or contains the Point element. + + + + + This property element contains a list of points. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of points as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiCurve is defined by one or more gml:AbstractCurves. +The members of the geometric aggregate may be specified either using the "standard" property (gml:curveMember) or the array property (gml:curveMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element contains a list of curves. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of curves as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiSurface is defined by one or more gml:AbstractSurfaces. +The members of the geometric aggregate may be specified either using the "standard" property (gml:surfaceMember) or the array property (gml:surfaceMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element contains a list of surfaces. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of surfaces as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + A gml:MultiSolid is defined by one or more gml:AbstractSolids. +The members of the geometric aggregate may be specified either using the "standard" property (gml:solidMember) or the array property (gml:solidMembers). It is also valid to use both the "standard" and the array properties in the same collection. + + + + + This property element either references a solid via the XLink-attributes or contains the solid element. A solid element is any element, which is substitutable for gml:AbstractSolid. + + + + + This property element contains a list of solids. The order of the elements is significant and shall be preserved when processing the array. + + + + + A property that has a collection of solids as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic0d1d.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic0d1d.xsd new file mode 100644 index 0000000..2ac83e3 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic0d1d.xsd @@ -0,0 +1,277 @@ + + + + geometryBasic0d1d.xsd + See ISO/DIS 19136 Clause 10. +Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. +All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. +The geometry model distinguishes geometric primitives, aggregates and complexes. +Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. +If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. + + + + + + + + + + If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. +The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + + posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. +The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. +The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. + + + + + + + + + + + + GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). +pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. +pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). + + + + + + + + + GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). +The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. + + + + + + + + + For some applications the components of the position may be adjusted to yield a unit vector. + + + + + + + + + + + + + + + deprecated + + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. + + + + + gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. + + + + + + + + The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. + + + + + A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. + + + + + A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + + + + + + + + A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic2d.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic2d.xsd new file mode 100644 index 0000000..5781df5 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/geometryBasic2d.xsd @@ -0,0 +1,124 @@ + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substituition group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/geometryComplexes.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/geometryComplexes.xsd new file mode 100644 index 0000000..de4f945 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/geometryComplexes.xsd @@ -0,0 +1,95 @@ + + + + geometryComplexes.xsd + See ISO/DIS 19136 12.2. +Geometric complexes (i.e. instances of gml:GeometricComplexType) are closed collections of geometric primitives, i.e. they will contain their boundaries. +A geometric complex (gml:GeometricComplex) is defined by ISO 19107:2003, 6.6.1 as "a set of primitive geometric objects (in a common coordinate system) whose interiors are disjoint. Further, if a primitive is in a geometric complex, then there exists a set of primitives in that complex whose point-wise union is the boundary of this first primitive." +A geometric composite (gml:CompositeCurve, gml:CompositeSurface and gml:CompositeSolid) represents a geometric complex with an underlying core geometry that is isomorphic to a primitive, i.e. it can be viewed as a primitive and as a complex. See ISO 19107:2003, 6.1 and 6.6.3 for more details on the nature of composite geometries. +Geometric complexes and composites are intended to be used in application schemas where the sharing of geometry is important. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + + + + + + + + + A property that has a geometric complex as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + + + + + A gml:CompositeCurve is represented by a sequence of (orientable) curves such that each curve in the sequence terminates at the start point of the subsequent curve in the list. +curveMember references or contains inline one curve in the composite curve. +The curves are contiguous, the collection of curves is ordered. Therefore, if provided, the aggregationType attribute shall have the value "sequence". + + + + + + + + + + + + + + + A gml:CompositeSurface is represented by a set of orientable surfaces. It is geometry type with all the geometric properties of a (primitive) surface. Essentially, a composite surface is a collection of surfaces that join in pairs on common boundary curves and which, when considered as a whole, form a single surface. +surfaceMember references or contains inline one surface in the composite surface. +The surfaces are contiguous. + + + + + + + + + + + + + + + gml:CompositeSolid implements ISO 19107 GM_CompositeSolid (see ISO 19107:2003, 6.6.7) as specified in D.2.3.6. +A gml:CompositeSolid is represented by a set of orientable surfaces. It is a geometry type with all the geometric properties of a (primitive) solid. Essentially, a composite solid is a collection of solids that join in pairs on common boundary surfaces and which, when considered as a whole, form a single solid. +solidMember references or contains one solid in the composite solid. The solids are contiguous. + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/geometryPrimitives.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/geometryPrimitives.xsd new file mode 100644 index 0000000..9cbd52c --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/geometryPrimitives.xsd @@ -0,0 +1,846 @@ + + + + geometryPrimitives.xsd + See ISO/DIS 19136 Clause 11. +Beside the "simple" geometric primitives specified in the previous Clause, this Clause specifies additional primitives to describe real world situations which require a more expressive geometry model. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + + + + + + + A curve is a 1-dimensional primitive. Curves are continuous, connected, and have a measurable length in terms of the coordinate system. +A curve is composed of one or more curve segments. Each curve segment within a curve may be defined using a different interpolation method. The curve segments are connected to one another, with the end point of each segment except the last being the start point of the next segment in the segment list. +The orientation of the curve is positive. +The element segments encapsulates the segments of the curve. + + + + + + + + + + + + + + + The property baseCurve references or contains the base curve, i.e. it either references the base curve via the XLink-attributes or contains the curve element. A curve element is any element which is substitutable for AbstractCurve. The base curve has positive orientation. + + + + + OrientableCurve consists of a curve and an orientation. If the orientation is "+", then the OrientableCurve is identical to the baseCurve. If the orientation is "-", then the OrientableCurve is related to another AbstractCurve with a parameterization that reverses the sense of the curve traversal. + + + + + + + + + + A curve segment defines a homogeneous segment of a curve. +The attributes numDerivativesAtStart, numDerivativesAtEnd and numDerivativesInterior specify the type of continuity as specified in ISO 19107:2003, 6.4.9.3. +The AbstractCurveSegment element is the abstract head of the substituition group for all curve segment elements, i.e. continuous segments of the same interpolation mechanism. +All curve segments shall have an attribute interpolation with type gml:CurveInterpolationType specifying the curve interpolation mechanism used for this segment. This mechanism uses the control points and control parameters to determine the position of this curve segment. + + + + + gml:CurveSegmentArrayPropertyType is a container for an array of curve segments. + + + + + + + + This property element contains a list of curve segments. The order of the elements is significant and shall be preserved when processing the array. + + + + + gml:CurveInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an application schema. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A LineStringSegment is a curve segment that is defined by two or more control points including the start and end point, with linear interpolation between them. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + An ArcString is a curve segment that uses three-point circular arc interpolation ("circularArc3Points"). The number of arcs in the arc string may be explicitly stated in the attribute numArc. The number of control points in the arc string shall be 2 * numArc + 1. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + An Arc is an arc string with only one arc unit, i.e. three control points including the start and end point. As arc is an arc string consisting of a single arc, the attribute "numArc" is fixed to "1". + + + + + + + + + + A Circle is an arc whose ends coincide to form a simple closed loop. The three control points shall be distinct non-co-linear points for the circle to be unambiguously defined. The arc is simply extended past the third control point until the first control point is encountered. + + + + + + + + + + + + + + + + + + + + + + + + + + This variant of the arc computes the mid points of the arcs instead of storing the coordinates directly. The control point sequence consists of the start and end points of each arc plus the bulge (see ISO 19107:2003, 6.4.17.2). The normal is a vector normal (perpendicular) to the chord of the arc (see ISO 19107:2003, 6.4.17.4). +The interpolation is fixed as "circularArc2PointWithBulge". +The number of arcs in the arc string may be explicitly stated in the attribute numArc. The number of control points in the arc string shall be numArc + 1. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + + An ArcByBulge is an arc string with only one arc unit, i.e. two control points, one bulge and one normal vector. +As arc is an arc string consisting of a single arc, the attribute "numArc" is fixed to "1". + + + + + + + + + + + + + + + + + + + + + + + + + + + This variant of the arc requires that the points on the arc shall be computed instead of storing the coordinates directly. The single control point is the center point of the arc plus the radius and the bearing at start and end. This representation can be used only in 2D. +The element radius specifies the radius of the arc. +The element startAngle specifies the bearing of the arc at the start. +The element endAngle specifies the bearing of the arc at the end. +The interpolation is fixed as "circularArcCenterPointWithRadius". +Since this type describes always a single arc, the attribute "numArc" is fixed to "1". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + A gml:CircleByCenterPoint is an gml:ArcByCenterPoint with identical start and end angle to form a full circle. Again, this representation can be used only in 2D. + + + + + + + + + + + + + + + + + + + + + + + + + + The number of control points shall be at least three. +vectorAtStart is the unit tangent vector at the start point of the spline. vectorAtEnd is the unit tangent vector at the end point of the spline. Only the direction of the vectors shall be used to determine the shape of the cubic spline, not their length. +interpolation is fixed as "cubicSpline". +degree shall be the degree of the polynomial used for the interpolation in this spline. Therefore the degree for a cubic spline is fixed to "3". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + + + + + + + + A B-Spline is a piecewise parametric polynomial or rational curve described in terms of control points and basis functions as specified in ISO 19107:2003, 6.4.30. Therefore, interpolation may be either "polynomialSpline" or "rationalSpline" depending on the interpolation type; default is "polynomialSpline". +degree shall be the degree of the polynomial used for interpolation in this spline. +knot shall be the sequence of distinct knots used to define the spline basis functions (see ISO 19107:2003, 6.4.26.2). +The attribute isPolynomial shall be set to "true" if this is a polynomial spline (see ISO 19107:2003, 6.4.30.5). +The attribute knotType shall provide the type of knot distribution used in defining this spline (see ISO 19107:2003, 6.4.30.4). +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + gml:KnotPropertyType encapsulates a knot to use it in a geometric type. + + + + + A knot is a breakpoint on a piecewise spline curve. +value is the value of the parameter at the knot of the spline (see ISO 19107:2003, 6.4.24.2). +multiplicity is the multiplicity of this knot used in the definition of the spline (with the same weight). +weight is the value of the averaging weight used for this knot of the spline. + + + + + + + This enumeration type specifies values for the knots' type (see ISO 19107:2003, 6.4.25). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Bezier curves are polynomial splines that use Bezier or Bernstein polynomials for interpolation purposes. It is a special case of the B-Spline curve with two knots. +degree shall be the degree of the polynomial used for interpolation in this spline. +knot shall be the sequence of distinct knots used to define the spline basis functions. +interpolation is fixed as "polynomialSpline". +isPolynomial is fixed as "true". +knotType is not relevant for Bezier curve segments. + + + + + + + + + + + + + + + + + An offset curve is a curve at a constant distance from the basis curve. offsetBase is the base curve from which this curve is defined as an offset. distance and refDirection have the same meaning as specified in ISO 19107:2003, 6.4.23. +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + location, refDirection, inDimension and outDimension have the same meaning as specified in ISO 19107:2003, 6.4.21. + + + + + + + + + + + + + + + + + + + + + + + + A clothoid, or Cornu's spiral, is plane curve whose curvature is a fixed function of its length. +refLocation, startParameter, endParameter and scaleFactor have the same meaning as specified in ISO 19107:2003, 6.4.22. +interpolation is fixed as "clothoid". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + A sequence of geodesic segments. +The number of control points shall be at least two. +interpolation is fixed as "geodesic". +The content model follows the general pattern for the encoding of curve segments. + + + + + + + + + + + + + + + + + + + + A Surface is a 2-dimensional primitive and is composed of one or more surface patches as specified in ISO 19107:2003, 6.3.17.1. The surface patches are connected to one another. +patches encapsulates the patches of the surface. + + + + + + + + + + + + + + + The property baseSurface references or contains the base surface. The property baseSurface either references the base surface via the XLink-attributes or contains the surface element. A surface element is any element which is substitutable for gml:AbstractSurface. The base surface has positive orientation. + + + + + OrientableSurface consists of a surface and an orientation. If the orientation is "+", then the OrientableSurface is identical to the baseSurface. If the orientation is "-", then the OrientableSurface is a reference to a gml:AbstractSurface with an up-normal that reverses the direction for this OrientableSurface, the sense of "the top of the surface". + + + + + + A surface patch defines a homogenuous portion of a surface. +The AbstractSurfacePatch element is the abstract head of the substituition group for all surface patch elements describing a continuous portion of a surface. +All surface patches shall have an attribute interpolation (declared in the types derived from gml:AbstractSurfacePatchType) specifying the interpolation mechanism used for the patch using gml:SurfaceInterpolationType. + + + + + gml:SurfacePatchArrayPropertyType is a container for a sequence of surface patches. + + + + + + + + The patches property element contains the sequence of surface patches. The order of the elements is significant and shall be preserved when processing the array. + + + + + gml:SurfaceInterpolationType is a list of codes that may be used to identify the interpolation mechanisms specified by an application schema. + + + + + + + + + + + + + + + + + + + + + + + + + + + + A gml:PolygonPatch is a surface patch that is defined by a set of boundary curves and an underlying surface to which these curves adhere. The curves shall be coplanar and the polygon uses planar interpolation in its interior. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + gml:Triangle represents a triangle as a surface patch with an outer boundary consisting of a linear ring. Note that this is a polygon (subtype) with no inner boundaries. The number of points in the linear ring shall be four. +The ring (element exterior) shall be a gml:LinearRing and shall form a triangle, the first and the last position shall be coincident. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + gml:Rectangle represents a rectangle as a surface patch with an outer boundary consisting of a linear ring. Note that this is a polygon (subtype) with no inner boundaries. The number of points in the linear ring shall be five. +The ring (element exterior) shall be a gml:LinearRing and shall form a rectangle; the first and the last position shall be coincident. +interpolation is fixed to "planar", i.e. an interpolation shall return points on a single plane. The boundary of the patch shall be contained within that plane. + + + + + + + + + + + + + + + A ring is used to represent a single connected component of a surface boundary as specified in ISO 19107:2003, 6.3.6. +Every gml:curveMember references or contains one curve, i.e. any element which is substitutable for gml:AbstractCurve. In the context of a ring, the curves describe the boundary of the surface. The sequence of curves shall be contiguous and connected in a cycle. +If provided, the aggregationType attribute shall have the value "sequence". + + + + + + A property with the content model of gml:RingPropertyType encapsulates a ring to represent a component of a surface boundary. + + + + + + + + A gml:PointGrid group contains or references points or positions which are organised into sequences or grids. All rows shall have the same number of positions (columns). + + + + + + + + + + + + + + + + + + + + + + + + + The element provides a substitution group head for the surface patches based on parametric curves. All properties are specified in the derived subtypes. All derived subtypes shall conform to the constraints specified in ISO 19107:2003, 6.4.40. +If provided, the aggregationType attribute shall have the value "set". + + + + + + + + + + + + + + + + if provided, rows gives the number of rows, columns the number of columns in the parameter grid. The parameter grid is represented by an instance of the gml:PointGrid group. +The element provides a substitution group head for the surface patches based on a grid. All derived subtypes shall conform to the constraints specified in ISO 19107:2003, 6.4.41. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A polyhedral surface is a surface composed of polygon patches connected along their common boundary curves. This differs from the surface type only in the restriction on the types of surface patches acceptable. +polygonPatches encapsulates the polygon patches of the polyhedral surface. + + + + + A triangulated surface is a polyhedral surface that is composed only of triangles. There is no restriction on how the triangulation is derived. +trianglePatches encapsulates the triangles of the triangulated surface. + + + + + + + + + + + + + + + + + + + + + + + + A tin is a triangulated surface that uses the Delauny algorithm or a similar algorithm complemented with consideration of stoplines (stopLines), breaklines (breakLines), and maximum length of triangle sides (maxLength). controlPoint shall contain a set of the positions (three or more) used as posts for this TIN (corners of the triangles in the TIN). See ISO 19107:2003, 6.4.39 for details. + + + + + gml:LineStringSegmentArrayPropertyType provides a container for line strings. + + + + + + + + gml:AbstractSolidType is an abstraction of a solid to support the different levels of complexity. The solid may always be viewed as a geometric primitive, i.e. is contiguous. + + + + + + + + The AbstractSolid element is the abstract head of the substituition group for all (continuous) solid elements. + + + + + A property that has a solid as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a solid via the XLink-attributes or contains the solid element. solidProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSolid. + + + + + gml:SolidArrayPropertyType is a container for an array of solids. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements is not supported. + + + + + + + + + + + + + + + + + + + A solid is the basis for 3-dimensional geometry. The extent of a solid is defined by the boundary surfaces as specified in ISO 19107:2003, 6.3.18. exterior specifies the outer boundary, interior the inner boundary of the solid. + + + + + + + + + + + A shell is used to represent a single connected component of a solid boundary as specified in ISO 19107:2003, 6.3.8. +Every gml:surfaceMember references or contains one surface, i.e. any element which is substitutable for gml:AbstractSurface. In the context of a shell, the surfaces describe the boundary of the solid. +If provided, the aggregationType attribute shall have the value "set". + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. A surface element is any element, which is substitutable for gml:AbstractSurface. + + + + + A property with the content model of gml:ShellPropertyType encapsulates a shell to represent a component of a solid boundary. + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/gml.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/gml.xsd new file mode 100644 index 0000000..b319a19 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/gml.xsd @@ -0,0 +1,20 @@ + + + + gml.xsd + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/gmlBase.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/gmlBase.xsd new file mode 100644 index 0000000..ec81080 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/gmlBase.xsd @@ -0,0 +1,185 @@ + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + deprecated + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to "by-reference only" (see 7.2.3.7), +- the encoding to "inline only" (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a text description of the object. gml:description uses gml:StringOrRefType as its content model, so it may contain a simple text string content, or carry a reference to an external description. The use of gml:description to reference an external description has been deprecated and replaced by the gml:descriptionReference property. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/gml_32_geometries.rdf b/config/schemas/schema/net/opengis/gml/3.2.1/gml_32_geometries.rdf new file mode 100644 index 0000000..51bf90e --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/gml_32_geometries.rdf @@ -0,0 +1,368 @@ + + + + + + + + + + + + Point + + + + + + + Abstract Gridded Surface + + + + + + + Polyhedral Surface + + + + + + + Arc + + + + + + + Polynomial Spline + + + + + + + Multi-Curve + + + + + + + + + + Composite Surface + + + + + + + Arc String + + + + + Cylinder + + + + + Shell + + + + + + + Polygon + + + + + + + Triangulated Irregular Network + + + + + + + Multi-Geometry + + + + + + + Bezier + + + + + + + + + + Curve + + + + + + + BSpline + + + + + + + Line String Segment + + + + + + + Geodesic + + + + + + + + + Abstract Surface Patch + + + + + + + Geometric Complex + + + + + + + Arc by Bulge + + + + + + + CircleByCenterPoint + + + + + Multi-Point + + + + + + + Arc by Center Point + + + + + + + Offset Curve + + + + + + + Spline Curve + + + + + Composite + + + + + Line String + + + + + Circle + + + + + + + Orientable Curve + + + + + + + Orientable Surface + + + + + + + Clothoid + + + + + + + Arc String by Bulge + + + + + Triangulated Surface + + + + + + + Triangle + + + + + Cubic Spline + + + + + Abstract Geometry + + + + + Cone + + + + + + + + Composite Solid + + + + + Abstract Geometric Primitive + + + + + + + Linear Ring + + + + + Abstract Parametric Curve Surface + + + + + + + Geodesic String + + + + + Multi-Solid + + + + + Solid + + + + + + Composite Curve + + + + + + + Rectangle + + + + + Sphere + + + + + Ring + + + + + Polygon Patch + + + + + Multi-Surface + + + + + Abstract Curve Segment + + + + + + Surface + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/gml_3_2_1-ReadMe.txt b/config/schemas/schema/net/opengis/gml/3.2.1/gml_3_2_1-ReadMe.txt new file mode 100644 index 0000000..a0a6eb2 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/gml_3_2_1-ReadMe.txt @@ -0,0 +1,58 @@ +OpenGIS(r) GML schema version 3.2.1 / ISO 19136 - ReadMe.txt + +The schema has been validated with Xerces-J, Xerces C++ and XSV. + +------------------------------------------------------------------- + +2012-07-21 Kevin Stegemoller + + * v2.0.0 - v3.2.1 WARNING XLink change is NOT BACKWARD COMPATIBLE. + * changed OGC XLink (xlink:simpleLink) to W3C XLink (xlink:simpleAttrs) + per an approved TC and PC motion during the Dec. 2011 Brussels meeting. + see http://www.opengeospatial.org/blog/1597 + * implement 11-025: retroactively require/add all leaf documents of an + XML namespace shall explicitly the all-components schema + * v3.2.1: updated xsd:schema:@version to 3.2.1.2 (06-135r7 s#13.4) + +2007-09-06 Kevin Stegemoller + + GML 3.2.1 (ISO 19136) + * Published GML 3.2.1 schemas from OGC 07-036 + * validated with oXygen 8.2 (xerces-J 2.9.0) - Kevin Stegemoller + * validated with Xerces-J, Xerces-C++ and XSV - Clemens Portele + +2007-08-17 Kevin Stegemoller + + Changes made to these GML 3.2.1 / ISO 19136 schemas: + * added ReadMe.txt + * changed gmd.xsd references to "../../iso/19139/20070417/gmd/gmd.xsd" + * changed xlink references to be relative to /xlink/1.0.0/xlinks.xsd + available from schemas.opengis.net/xlink/1.0.0/xlinks.xsd (REMOVED 2012-07-21). + * removed xlinks schema and directory + + Changes made to these ISO 19139 schemas by OGC: + * added ReadMe.txt + * changed ISO_19136 path to /gml/3.2.1/ + * changed xlink references to be relative to /xlink/1.0.0/xlinks.xsd + available from schemas.opengis.net/xlink/1.0.0/xlinks.xsd (REMOVED 2012-07-21). + * removed xlinks schema and directory + +OGC GML 3.2.1 / ISO 19136 schemas files will be published at: +- http://schemas.opengis.net/gml/3.2.1/ +- http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19136_Schemas/ + +Files in the folder "ISO/19139/20070417" are also published at +- http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------- + +The Open Geospatial Consortium, Inc. official schema repository is at + http://schemas.opengis.net/ . +Policies, Procedures, Terms, and Conditions of OGC(r) are available + http://www.opengeospatial.org/ogc/policies/ . +Additional rights of use are described at + http://www.opengeospatial.org/legal/ . + +Copyright (c) 2007 Open Geospatial Consortium. + +------------------------------------------------------------------- diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/grids.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/grids.xsd new file mode 100644 index 0000000..7592e0e --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/grids.xsd @@ -0,0 +1,64 @@ + + + + grids.xsd + See ISO/DIS 19136 20.2. +An implicit description of geometry is one in which the items of the geometry do not explicitly appear in the encoding. Instead, a compact notation records a set of parameters, and a set of objects may be generated using a rule with these parameters. This Clause provides grid geometries that are used in the description of gridded coverages and other applications. +In GML two grid structures are defined, namely gml:Grid and gml:RectifiedGrid. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + The gml:Grid implicitly defines an unrectified grid, which is a network composed of two or more sets of curves in which the members of each set intersect the members of the other sets in an algorithmic way. The region of interest within the grid is given in terms of its gml:limits, being the grid coordinates of diagonally opposed corners of a rectangular region. gml:axisLabels is provided with a list of labels of the axes of the grid (gml:axisName has been deprecated). gml:dimension specifies the dimension of the grid. +The gml:limits element contains a single gml:GridEnvelope. The gml:low and gml:high property elements of the envelope are each integerLists, which are coordinate tuples, the coordinates being measured as offsets from the origin of the grid along each axis, of the diagonally opposing corners of a "rectangular" region of interest. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A rectified grid is a grid for which there is an affine transformation between the grid coordinates and the coordinates of an external coordinate reference system. It is defined by specifying the position (in some geometric space) of the grid "origin" and of the vectors that specify the post locations. +Note that the grid limits (post indexes) and axis name properties are inherited from gml:GridType and that gml:RectifiedGrid adds a gml:origin property (contains or references a gml:Point) and a set of gml:offsetVector properties. + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/measures.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/measures.xsd new file mode 100644 index 0000000..c3a91fb --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/measures.xsd @@ -0,0 +1,68 @@ + + + + measures.xsd + See ISO/DIS 19136 17.3. +gml:MeasureType is defined in the basicTypes schema. The measure types defined here correspond with a set of convenience measure types described in ISO/TS 19103. The XML implementation is based on the XML Schema simple type "double" which supports both decimal and scientific notation, and includes an XML attribute "uom" which refers to the units of measure for the value. Note that, there is no requirement to store values using any particular format, and applications receiving elements of this type may choose to coerce the data to any other type as convenient. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + The value of a physical quantity, together with its unit. + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The gml:angle property element is used to record the value of an angle quantity as a single number, with its units. + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/observation.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/observation.xsd new file mode 100644 index 0000000..944c989 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/observation.xsd @@ -0,0 +1,95 @@ + + + + observation.xsd + See ISO/DIS 19136 Clause 19. +A GML observation models the act of observing, often with a camera, a person or some form of instrument. An observation feature describes the "metadata" associated with an information capture event, together with a value for the result of the observation. This covers a broad range of cases, from a tourist photo (not the photo but the act of taking the photo), to images acquired by space borne sensors or the measurement of a temperature 5 meters below the surfaces of a lake. +The basic structures introduced in this schema are intended to serve as the foundation for more comprehensive schemas for scientific, technical and engineering measurement schemas. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + The content model is a straightforward extension of gml:AbstractFeatureType; it automatically has the gml:identifier, gml:description, gml:descriptionReference, gml:name, and gml:boundedBy properties. +The gml:validTime element describes the time of the observation. Note that this may be a time instant or a time period. +The gml:using property contains or references a description of a sensor, instrument or procedure used for the observation. +The gml:target property contains or references the specimen, region or station which is the object of the observation. This property is particularly useful for remote observations, such as photographs, where a generic location property might apply to the location of the camera or the location of the field of view, and thus may be ambiguous. +The gml:subject element is provided as a convenient synonym for gml:target. This is the term commonly used in phtotography. +The gml:resultOf property indicates the result of the observation. The value may be inline, or a reference to a value elsewhere. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A gml:DirectedObservation is the same as an observation except that it adds an additional gml:direction property. This is the direction in which the observation was acquired. Clearly this applies only to certain types of observations such as visual observations by people, or observations obtained from terrestrial cameras. + + + + + + + + + + + + + + gml:DirectedObservationAtDistance adds an additional distance property. This is the distance from the observer to the subject of the observation. Clearly this applies only to certain types of observations such as visual observations by people, or observations obtained from terrestrial cameras. + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/referenceSystems.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/referenceSystems.xsd new file mode 100644 index 0000000..fb7e897 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/referenceSystems.xsd @@ -0,0 +1,70 @@ + + + + referenceSystems.xsd + See ISO/DIS 19136 13.2. +The reference systems schema components have two logical parts, which define elements and types for XML encoding of the definitions of: +- Identified Object, inherited by the ten types of GML objects used for coordinate reference systems and coordinate operations +- High-level part of the definitions of coordinate reference systems +This schema encodes the Identified Object and Reference System packages of the UML Model for ISO 19111. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + gml:IdentifiedObjectType provides identification properties of a CRS-related object. In gml:DefinitionType, the gml:identifier element shall be the primary name by which this object is identified, encoding the "name" attribute in the UML model. +Zero or more of the gml:name elements can be an unordered set of "identifiers", encoding the "identifier" attribute in the UML model. Each of these gml:name elements can reference elsewhere the object's defining information or be an identifier by which this object can be referenced. +Zero or more other gml:name elements can be an unordered set of "alias" alternative names by which this CRS related object is identified, encoding the "alias" attributes in the UML model. An object may have several aliases, typically used in different contexts. The context for an alias is indicated by the value of its (optional) codeSpace attribute. +Any needed version information shall be included in the codeSpace attribute of a gml:identifier and gml:name elements. In this use, the gml:remarks element in the gml:DefinitionType shall contain comments on or information about this object, including data source information. + + + + + + + + gml:AbstractCRS specifies a coordinate reference system which is usually single but may be compound. This abstract complex type shall not be used, extended, or restricted, in a GML Application Schema, to define a concrete subtype with a meaning equivalent to a concrete subtype specified in this document. + + + + + + + + + + + + + + + The gml:domainOfValidity property implements an association role to an EX_Extent object as encoded in ISO/TS 19139, either referencing or containing the definition of that extent. + + + + + + + + + + + The gml:scope property provides a description of the usage, or limitations of usage, for which this CRS-related object is valid. If unknown, enter "not known". + + + + + gml:CRSPropertyType is a property type for association roles to a CRS abstract coordinate reference system, either referencing or containing the definition of that CRS. + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/temporal.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/temporal.xsd new file mode 100644 index 0000000..11c4ae3 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/temporal.xsd @@ -0,0 +1,269 @@ + + + + temporal.xsd + See ISO/DIS 19136 15.2. +The GML temporal schemas include components for describing temporal geometry and topology, temporal reference systems, and the temporal characteristics of geographic data. The model underlying the representation constitutes a profile of the conceptual schema described in ISO 19108. The underlying spatiotemporal model strives to accommodate both feature-level and attribute-level time stamping; basic support for tracking moving objects is also included. +Time is measured on two types of scales: interval and ordinal. An interval scale offers a basis for measuring duration, an ordinal scale provides information only about relative position in time. +Two other ISO standards are relevant to describing temporal objects: ISO 8601 describes encodings for time instants and time periods, as text strings with particular structure and punctuation; ISO 11404 provides a detailed description of time intervals as part of a general discussion of language independent datatypes. +The temporal schemas cover two interrelated topics and provide basic schema components for representing temporal instants and periods, temporal topology, and reference systems; more specialized schema components defines components used for dynamic features. Instances of temporal geometric types are used as values for the temporal properties of geographic features. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + gml:AbstractTimeObject acts as the head of a substitution group for all temporal primitives and complexes. + + + + + + + + + + gml:AbstractTimePrimitive acts as the head of a substitution group for geometric and topological temporal primitives. + + + + + + + + + + + + + + gml:TimePrimitivePropertyType provides a standard content model for associations between an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive and another object. + + + + + + + + + + gml:validTime is a convenience property element. + + + + + gml:RelatedTimeType provides a content model for indicating the relative position of an arbitrary member of the substitution group whose head is gml:AbstractTimePrimitive. It extends the generic gml:TimePrimitivePropertyType with an XML attribute relativePosition, whose value is selected from the set of 13 temporal relationships identified by Allen (1983) + + + + + + + + + + + + + + + + + + + + + + + + + + + + gml:AbstractTimeComplex is an aggregation of temporal primitives and acts as the head of a substitution group for temporal complexes. + + + + + + + + + + gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. +A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. +The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. + + + + + + + + + + + + gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. + + + + + + + + + + + + + + gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. + + + + + + + + + + gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. +The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. +Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. +Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. + + + + + + + + + + + + + + + + + + + + + + gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. + + + + + + + + + + The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. +Values based on calendars and clocks use lexical formats that are based on ISO 8601, as described in XML Schema Part 2:2001. A decimal value may be used with coordinate systems such as GPS time or UNIX time. A URI may be used to provide a reference to some era in an ordinal reference system . +In common with many of the components modelled as data types in the ISO 19100 series of International Standards, the corresponding GML component has simple content. However, the content model gml:TimePositionType is defined in several steps. +Three XML attributes appear on gml:TimePositionType: +A time value shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. Components for describing temporal reference systems are described in 14.4, but it is not required that the reference system be described in this, as the reference may refer to anything that may be indentified with a URI. +For time values using a calendar containing more than one era, the (optional) calendarEraName attribute provides the name of the calendar era. +Inexact temporal positions may be expressed using the optional indeterminatePosition attribute. This takes a value from an enumeration. + + + + + + + + + + + + These values are interpreted as follows: +- "unknown" indicates that no specific value for temporal position is provided. +- "now" indicates that the specified value shall be replaced with the current temporal position whenever the value is accessed. +- "before" indicates that the actual temporal position is unknown, but it is known to be before the specified value. +- "after" indicates that the actual temporal position is unknown, but it is known to be after the specified value. +A value for indeterminatePosition may +- be used either alone, or +- qualify a specific value for temporal position. + + + + + + + + + + + The simple type gml:TimePositionUnion is a union of XML Schema simple types which instantiate the subtypes for temporal position described in ISO 19108. + An ordinal era may be referenced via URI. A decimal value may be used to indicate the distance from the scale origin . time is used for a position that recurs daily (see ISO 19108:2002 5.4.4.2). + Finally, calendar and clock forms that support the representation of time in systems based on years, months, days, hours, minutes and seconds, in a notation following ISO 8601, are assembled by gml:CalDate + + + + + + + + + This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. + + + + + The length of a time period. + + + + + + + + + gml:duration conforms to the ISO 8601 syntax for temporal length as implemented by the XML Schema duration type. + + + + + gml:timeInterval conforms to ISO 11404 which is based on floating point values for temporal length. +ISO 11404 syntax specifies the use of a positiveInteger together with appropriate values for radix and factor. The resolution of the time interval is to one radix ^(-factor) of the specified time unit. +The value of the unit is either selected from the units for time intervals from ISO 31-1:1992, or is another suitable unit. The encoding is defined for GML in gml:TimeUnitType. The second component of this union type provides a method for indicating time units other than the six standard units given in the enumeration. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/temporalReferenceSystems.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/temporalReferenceSystems.xsd new file mode 100644 index 0000000..88f610b --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/temporalReferenceSystems.xsd @@ -0,0 +1,189 @@ + + + + temporalReferenceSystems.xsd + See ISO/DIS 19136 15.5. +A value in the time domain is measured relative to a temporal reference system. Common types of reference systems include calendars, ordinal temporal reference systems, and temporal coordinate systems (time elapsed since some epoch). The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. The Julian day numbering system is a temporal coordinate system that has an origin earlier than any known calendar, at noon on 1 January 4713 BC in the Julian proleptic calendar, and is useful in transformations between dates in different calendars. +In GML seven concrete elements are used to describe temporal reference systems: gml:TimeReferenceSystem, gml:TimeCoordinateSystem, gml:TimeCalendar, gml:TimeCalendarEra, gml:TimeClock, gml:TimeOrdinalReferenceSystem, and gml:TimeOrdinalEra. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + A reference system is characterized in terms of its domain of validity: the spatial and temporal extent over which it is applicable. The basic GML element for temporal reference systems is gml:TimeReferenceSystem. Its content model extends gml:DefinitionType with one additional property, gml:domainOfValidity. + + + + + + + + + + + + + + A temporal coordinate system shall be based on a continuous interval scale defined in terms of a single time interval. +The differences to ISO 19108 TM_CoordinateSystem are: +- the origin is specified either using the property gml:originPosition whose value is a direct time position, or using the property gml:origin whose model is gml:TimeInstantPropertyType; this permits more flexibility in representation and also supports referring to a value fixed elsewhere; +- the interval uses gml:TimeIntervalLengthType. + + + + + + + + + + + + + + + + + + + A calendar is a discrete temporal reference system that provides a basis for defining temporal position to a resolution of one day. +gml:TimeCalendar adds one property to those inherited from gml:TimeReferenceSystem. A gml:referenceFrame provides a link to a gml:TimeCalendarEra that it uses. A gml:TimeCalendar may reference more than one calendar era. +The referenceFrame element follows the standard GML property model, allowing the association to be instantiated either using an inline description using the gml:TimeCalendarEra element, or a link to a gml:TimeCalendarEra which is explicit elsewhere. + + + + + + + + + + + + + + gml:TimeCalendarEra inherits basic properties from gml:DefinitionType and has the following additional properties: +- gml:referenceEvent is the name or description of a mythical or historic event which fixes the position of the base scale of the calendar era. This is given as text or using a link to description held elsewhere. +- gml:referenceDate specifies the date of the referenceEvent expressed as a date in the given calendar. In most calendars, this date is the origin (i.e., the first day) of the scale, but this is not always true. +- gml:julianReference specifies the Julian date that corresponds to the reference date. The Julian day number is an integer value; the Julian date is a decimal value that allows greater resolution. Transforming calendar dates to and from Julian dates provides a relatively simple basis for transforming dates from one calendar to another. +- gml:epochOfUse is the period for which the calendar era was used as a basis for dating. + + + + + + + + + + + + + + + + + gml:TimeCalendarPropertyType provides for associating a gml:TimeCalendar with an object. + + + + + + + + + + gml:TimeCalendarEraPropertyType provides for associating a gml:TimeCalendarEra with an object. + + + + + + + + + + A clock provides a basis for defining temporal position within a day. A clock shall be used with a calendar in order to provide a complete description of a temporal position within a specific day. +gml:TimeClock adds the following properties to those inherited from gml:TimeReferenceSystemType: +- gml:referenceEvent is the name or description of an event, such as solar noon or sunrise, which fixes the position of the base scale of the clock. +- gml:referenceTime specifies the time of day associated with the reference event expressed as a time of day in the given clock. The reference time is usually the origin of the clock scale. +- gml:utcReference specifies the 24 hour local or UTC time that corresponds to the reference time. +- gml:dateBasis contains or references the calendars that use this clock. + + + + + + + + + + + + + + + + + gml:TimeClockPropertyType provides for associating a gml:TimeClock with an object. + + + + + + + + + + In some applications of geographic information — such as geology and archaeology — relative position in time is known more precisely than absolute time or duration. The order of events in time can be well established, but the magnitude of the intervals between them cannot be accurately determined; in such cases, the use of an ordinal temporal reference system is appropriate. An ordinal temporal reference system is composed of a sequence of named coterminous eras, which may in turn be composed of sequences of member eras at a finer scale, giving the whole a hierarchical structure of eras of verying resolution. +An ordinal temporal reference system whose component eras are not further subdivided is effectively a temporal topological complex constrained to be a linear graph. An ordinal temporal reference system some or all of whose component eras are subdivided is effectively a temporal topological complex with the constraint that parallel branches may only be constructed in pairs where one is a single temporal ordinal era and the other is a sequence of temporal ordinal eras that are called "members" of the "group". This constraint means that within a single temporal ordinal reference system, the relative position of all temporal ordinal eras is unambiguous. +The positions of the beginning and end of a given era may calibrate the relative time scale. +gml:TimeOrdinalReferenceSystem adds one or more gml:component properties to the generic temporal reference system model. + + + + + + + + + + + + + + Its content model follows the pattern of gml:TimeEdge, inheriting standard properties from gml:DefinitionType, and adding gml:start, gml:end and gml:extent properties, a set of gml:member properties which indicate ordered gml:TimeOrdinalEra elements, and a gml:group property which points to the parent era. +The recursive inclusion of gml:TimeOrdinalEra elements allow the construction of an arbitrary depth hierarchical ordinal reference schema, such that an ordinal era at a given level of the hierarchy includes a sequence of shorter, coterminous ordinal eras. + + + + + + + + + + + + + + + + + + + gml:TimeOrdinalEraPropertyType provides for associating a gml:TimeOrdinalEra with an object. + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/temporalTopology.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/temporalTopology.xsd new file mode 100644 index 0000000..b38392c --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/temporalTopology.xsd @@ -0,0 +1,119 @@ + + + + temporalTopology.xsd + See ISO/DIS 19136 15.3. +Temporal topology is described in terms of time complexes, nodes, and edges, and the connectivity between these. Temporal topology does not directly provide information about temporal position. It is used in the case of describing a lineage or a history (e.g. a family tree expressing evolution of species, an ecological cycle, a lineage of lands or buildings, or a history of separation and merger of administrative boundaries). The following Subclauses specifies the temporal topology as temporal characteristics of features in compliance with ISO 19108. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + gml:TimeTopologyPrimitive acts as the head of a substitution group for topological temporal primitives. +Temporal topology primitives shall imply the ordering information between features or feature properties. The temporal connection of features can be examined if they have temporal topology primitives as values of their properties. Usually, an instantaneous feature associates with a time node, and a static feature associates with a time edge. A feature with both modes associates with the temporal topology primitive: a supertype of time nodes and time edges. +A topological primitive is always connected to one or more other topological primitives, and is, therefore, always a member of a topological complex. In a GML instance, this will often be indicated by the primitives being described by elements that are descendents of an element describing a complex. However, in order to support the case where a temporal topological primitive is described in another context, the optional complex property is provided, which carries a reference to the parent temporal topological complex. + + + + + + + + + + + + + + gml:TimeTopologyPrimitivePropertyType provides for associating a gml:AbstractTimeTopologyPrimitive with an object. + + + + + + + + + + A temporal topology complex shall be the connected acyclic directed graph composed of temporal topological primitives, i.e. time nodes and time edges. Because a time edge may not exist without two time nodes on its boundaries, static features have time edges from a temporal topology complex as the values of their temporal properties, regardless of explicit declarations. +A temporal topology complex expresses a linear or a non-linear graph. A temporal linear graph, composed of a sequence of time edges, provides a lineage described only by "substitution" of feature instances or feature element values. A time node as the start or the end of the graph connects with at least one time edge. A time node other than the start and the end shall connect to at least two time edges: one of starting from the node, and another ending at the node. +A temporal topological complex is a set of connected temporal topological primitives. The member primtives are indicated, either by reference or by value, using the primitive property. + + + + + + + + + + + + + + gml:TimeTopologyComplexPropertyType provides for associating a gml:TimeTopologyComplex with an object. + + + + + + + + + + A time node is a zero-dimensional topological primitive that represents an identifiable node in time (it is equivalent to a point in space). A node may act as the termination or initiation of any number of time edges. A time node may be realised as a geometry, its position, whose value is a time instant. + + + + + + + + + + + + + + + + gml:TimeNodePropertyType provides for associating a gml:TimeNode with an object + + + + + + + + + + A time edge is a one-dimensional topological primitive. It is an open interval that starts and ends at a node. The edge may be realised as a geometry whose value is a time period. + + + + + + + + + + + + + + + + gml:TimeEdgePropertyType provides for associating a gml:TimeEdge with an object. + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/topology.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/topology.xsd new file mode 100644 index 0000000..c528e6c --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/topology.xsd @@ -0,0 +1,386 @@ + + + + topology.xsd + See ISO/DIS 19136 Clause 14. +Topology is the branch of mathematics describing the properties of objects which are invariant under continuous deformation. For example, a circle is topologically equivalent to an ellipse because one can be transformed into the other by stretching. In geographic modelling, the foremost use of topology is in accelerating computational geometry. The constructs of topology allow characterisation of the spatial relationships between objects using simple combinatorial or algebraic algorithms. Topology, realised by the appropriate geometry, also allows a compact and unambiguous mechanism for expressing shared geometry among geographic features. +There are four instantiable classes of primitive topology objects, one for each dimension up to 3D. In addition, topological complexes are supported, too. +There is strong symmetry in the (topological boundary and coboundary) relationships between topology primitives of adjacent dimensions. Topology primitives are bounded by directed primitives of one lower dimension. The coboundary of each topology primitive is formed from directed topology primitives of one higher dimension. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + This abstract type supplies the root or base type for all topological elements including primitives and complexes. It inherits AbstractGMLType and hence can be identified using the gml:id attribute. + + + + + + + + + + + + + + gml:AbstractTopoPrimitive acts as the base type for all topological primitives. Topology primitives are the atomic (smallest possible) units of a topology complex. +Each topology primitive may contain references to other topology primitives of codimension 2 or more (gml:isolated). Conversely, nodes may have faces as containers and nodes and edges may have solids as containers (gml:container). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + In the case of planar topology, a gml:Node must have a clockwise sequence of gml:directedEdge properties, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). + + + + + + + + + + + gml:Node represents the 0-dimensional primitive. +The optional coboundary of a node (gml:directedEdge) is a sequence of directed edges which are incident on this node. Edges emanating from this node appear in the node coboundary with a negative orientation. +If provided, the aggregationType attribute shall have the value "sequence". +A node may optionally be realised by a 0-dimensional geometric primitive (gml:pointProperty). + + + + + A gml:directedNode property element describes the boundary of topology edges and is used in the support of topological point features via the gml:TopoPoint expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included node is used: start ("-") or end ("+") node. + + + + + + + + + + + + + + + + + + + + + + + + + + gml:Edge represents the 1-dimensional primitive. +The topological boundary of an Edge (gml:directedNode) consists of a negatively directed start Node and a positively directed end Node. +The optional coboundary of an edge (gml:directedFace) is a circular sequence of directed faces which are incident on this edge in document order. In the 2D case, the orientation of the face on the left of the edge is "+"; the orientation of the face on the right on its right is "-". +If provided, the aggregationType attribute shall have the value "sequence". +An edge may optionally be realised by a 1-dimensional geometric primitive (gml:curveProperty). + + + + + A gml:directedEdge property element describes the boundary of topology faces, the coBoundary of topology nodes and is used in the support of topological line features via the gml:TopoCurve expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included edge is used, i.e. forward or reverse. + + + + + + + + + + + + + + + + + + + + + + + If the topological representation exists an unbounded manifold (e.g. Euclidean plane), a gml:Face must indicate whether it is a universal face or not, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). The optional universal attribute of type boolean is used to indicate this. NOTE The universal face is normally not part of any feature, and is used to represent the unbounded portion of the data set. Its interior boundary (it has no exterior boundary) would normally be considered the exterior boundary of the map represented by the data set. + + + + + + + + gml:Face represents the 2-dimensional topology primitive. +The topological boundary of a face (gml:directedEdge) consists of a sequence of directed edges. If provided, the aggregationType attribute shall have the value "sequence". +The optional coboundary of a face (gml:directedTopoSolid) is a pair of directed solids which are bounded by this face. A positively directed solid corresponds to a solid which lies in the direction of the negatively directed normal to the face in any geometric realisation. +A face may optionally be realised by a 2-dimensional geometric primitive (gml:surfaceProperty). + + + + + The gml:directedFace property element describes the boundary of topology solids, in the coBoundary of topology edges and is used in the support of surface features via the gml:TopoSurface expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included face is used i.e. inward or outward with respect to the surface normal in any geometric realisation. + + + + + + + + + + + + + + + + + + + + + + A gml:TopoSolid must indicate whether it is a universal topo-solid or not, to ensure a lossless topology representation as defined by Kuijpers, et. al. (see OGC 05-102 Topology IPR). The optional universal attribute of type boolean is used to indicate this and the default is fault. NOTE The universal topo-solid is normally not part of any feature, and is used to represent the unbounded portion of the data set. Its interior boundary (it has no exterior boundary) would normally be considered the exterior boundary of the data set. + + + + + + + + gml:TopoSolid represents the 3-dimensional topology primitive. +The topological boundary of a solid (gml:directedFace) consists of a set of directed faces. +A solid may optionally be realised by a 3-dimensional geometric primitive (gml:solidProperty). + + + + + The gml:directedSolid property element describes the coBoundary of topology faces and is used in the support of volume features via the gml:TopoVolume expression, see below. The orientation attribute of type gml:SignType expresses the sense in which the included solid appears in the face coboundary. In the context of a gml:TopoVolume the orientation attribute has no meaning. + + + + + + + + + + + + + + + + + + + + + + The intended use of gml:TopoPoint is to appear within a point feature to express the structural and possibly geometric relationships of this feature to other features via shared node definitions. + + + + + + + + + + + The gml:topoPointProperty property element may be used in features to express their relationship to the referenced topology node. + + + + + + + + + + + + + + + gml:TopoCurve represents a homogeneous topological expression, a sequence of directed edges, which if realised are isomorphic to a geometric curve primitive. The intended use of gml:TopoCurve is to appear within a line feature to express the structural and geometric relationships of this feature to other features via the shared edge definitions. +If provided, the aggregationType attribute shall have the value "sequence". + + + + + + + + + + + The gml:topoCurveProperty property element may be used in features to express their relationship to the referenced topology edges. + + + + + + + + + + + + + + + gml:TopoSurface represents a homogeneous topological expression, a set of directed faces, which if realised are isomorphic to a geometric surface primitive. The intended use of gml:TopoSurface is to appear within a surface feature to express the structural and possibly geometric relationships of this surface feature to other features via the shared face definitions. + + + + + + + + + + + The gml:topoSurfaceProperty property element may be used in features to express their relationship to the referenced topology faces. + + + + + + + + + + + + + + + gml:TopoVolume represents a homogeneous topological expression, a set of directed topologic solids, which if realised are isomorphic to a geometric solid primitive. The intended use of gml:TopoVolume is to appear within a solid feature to express the structural and geometric relationships of this solid feature to other features via the shared solid definitions. + + + + + + + + + + + The gml:topoVolumeProperty element may be used in features to express their relationship to the referenced topology volume. + + + + + + + + + + + + + + + + + + + + gml:TopoComplex is a collection of topological primitives. +Each complex holds a reference to its maximal complex (gml:maximalComplex) and optionally to sub- or super-complexes (gml:subComplex, gml:superComplex). +A topology complex contains its primitive and sub-complex members. + + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The property elements gml:subComplex, gml:superComplex and gml:maximalComplex provide an encoding for relationships between topology complexes as described for gml:TopoComplex above. + + + + + The gml:topoPrimitiveMember property element encodes for the relationship between a topology complex and a single topology primitive. + + + + + + + + + + + + The gml:topoPrimitiveMembers property element encodes the relationship between a topology complex and an arbitrary number of topology primitives. + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/units.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/units.xsd new file mode 100644 index 0000000..84eca23 --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/units.xsd @@ -0,0 +1,162 @@ + + + + units.xsd + See ISO/DIS 17.2. +Several GML Schema components concern or require a reference scale or units of measure. Units are required for quantities that may occur as values of properties of feature types, as the results of observations, in the range parameters of a coverage, and for measures used in Coordinate Reference System definitions. +The basic unit definition is an extension of the general gml:Definition element defined in 16.2.1. Three specialized elements for unit definition are further derived from this. +This model is based on the SI system of units [ISO 1000], which distinguishes between Base Units and Derived Units. +- Base Units are the preferred units for a set of orthogonal fundamental quantities which define the particular system of units, which may not be derived by combination of other base units. +- Derived Units are the preferred units for other quantities in the system, which may be defined by algebraic combination of the base units. +In some application areas Conventional units are used, which may be converted to the preferred units using a scaling factor or a formula which defines a re-scaling and offset. The set of preferred units for all physical quantity types in a particular system of units is composed of the union of its base units and derived units. +Unit definitions are substitutable for the gml:Definition element declared as part of the dictionary model. A dictionary that contains only unit definitions and references to unit definitions is a units dictionary. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + The element gml:unitOfMeasure is a property element to refer to a unit of measure. This is an empty element which carries a reference to a unit of measure definition. + + + + + + + + + A gml:UnitDefinition is a general definition of a unit of measure. This generic element is used only for units for which no relationship with other units or units systems is known. +The content model of gml:UnitDefinition adds three additional properties to gml:Definition, gml:quantityType, gml:quantityTypeReference and gml:catalogSymbol. +The gml:catalogSymbol property optionally gives the short symbol used for this unit. This element is usually used when the relationship of this unit to other units or units systems is unknown. + + + + + + + + + + + + + + + + The gml:quantityType property indicates the phenomenon to which the units apply. This element contains an informal description of the phenomenon or type of physical quantity that is measured or observed. When the physical quantity is the result of an observation or measurement, this term is known as observable type or measurand. +The use of gml:quantityType for references to remote values is deprecated. + + + + + The gml:quantityTypeReference property indicates the phenomenon to which the units apply. The content is a reference to a remote value. + + + + + The catalogSymbol is the preferred lexical symbol used for this unit of measure. +The codeSpace attribute in gml:CodeType identifies a namespace for the catalog symbol value, and might reference the external catalog. The string value in gml:CodeType contains the value of a symbol that should be unique within this catalog namespace. This symbol often appears explicitly in the catalog, but it could be a combination of symbols using a specified algebra of units. + + + + + A base unit is a unit of measure that cannot be derived by combination of other base units within a particular system of units. For example, in the SI system of units, the base units are metre, kilogram, second, Ampere, Kelvin, mole, and candela, for the physical quantity types length, mass, time interval, electric current, thermodynamic temperature, amount of substance and luminous intensity, respectively. +gml:BaseUnit extends generic gml:UnitDefinition with the property gml:unitsSystem, which carries a reference to the units system to which this base unit is asserted to belong. + + + + + + + + + + + + + + Derived units are defined by combination of other units. Derived units are used for quantities other than those corresponding to the base units, such as hertz (s-1) for frequency, Newton (kg.m/s2) for force. Derived units based directly on base units are usually preferred for quantities other than the fundamental quantities within a system. If a derived unit is not the preferred unit, the gml:ConventionalUnit element should be used instead. +The gml:DerivedUnit extends gml:UnitDefinition with the property gml:derivationUnitTerms. + + + + + + + + + + + + + + A set of gml:derivationUnitTerm elements describes a derived unit of measure. Each element carries an integer exponent. The terms are combined by raising each referenced unit to the power of its exponent and forming the product. +This unit term references another unit of measure (uom) and provides an integer exponent applied to that unit in defining the compound unit. The exponent may be positive or negative, but not zero. + + + + + + + + + + + + Conventional units that are neither base units nor defined by direct combination of base units are used in many application domains. For example electronVolt for energy, feet and nautical miles for length. In most cases there is a known, usually linear, conversion to a preferred unit which is either a base unit or derived by direct combination of base units. +The gml:ConventionalUnit extends gml:UnitDefinition with a property that describes a conversion to a preferred unit for this physical quantity. When the conversion is exact, the element gml:conversionToPreferredUnit should be used, or when the conversion is not exact the element gml:roughConversionToPreferredUnit is available. Both of these elements have the same content model. The gml:derivationUnitTerm property defined above is included to allow a user to optionally record how this unit may be derived from other ("more primitive") units. + + + + + + + + + + + + + + + + + + The elements gml:conversionToPreferredUnit and gml:roughConversionToPreferredUnit represent parameters used to convert conventional units to preferred units for this physical quantity type. A preferred unit is either a Base Unit or a Derived Unit that is selected for all values of one physical quantity type. + + + + + The elements gml:conversionToPreferredUnit and gml:roughConversionToPreferredUnit represent parameters used to convert conventional units to preferred units for this physical quantity type. A preferred unit is either a Base Unit or a Derived Unit that is selected for all values of one physical quantity type. + + + + + The inherited attribute uom references the preferred unit that this conversion applies to. The conversion of a unit to the preferred unit for this physical quantity type is specified by an arithmetic conversion (scaling and/or offset). The content model extends gml:UnitOfMeasureType, which has a mandatory attribute uom which identifies the preferred unit for the physical quantity type that this conversion applies to. The conversion is specified by a choice of +- gml:factor, which defines the scale factor, or +- gml:formula, which defines a formula +by which a value using the conventional unit of measure can be converted to obtain the corresponding value using the preferred unit of measure. +The formula defines the parameters of a simple formula by which a value using the conventional unit of measure can be converted to the corresponding value using the preferred unit of measure. The formula element contains elements a, b, c and d, whose values use the XML Schema type double. These values are used in the formula y = (a + bx) / (c + dx), where x is a value using this unit, and y is the corresponding value using the base unit. The elements a and d are optional, and if values are not provided, those parameters are considered to be zero. If values are not provided for both a and d, the formula is equivalent to a fraction with numerator and denominator parameters. + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/gml/3.2.1/valueObjects.xsd b/config/schemas/schema/net/opengis/gml/3.2.1/valueObjects.xsd new file mode 100644 index 0000000..204bdfd --- /dev/null +++ b/config/schemas/schema/net/opengis/gml/3.2.1/valueObjects.xsd @@ -0,0 +1,205 @@ + + + + valueObjects.xsd + See ISO/DIS 19136 17.5. +The elements declared in this Clause build on other GML schema components, in particular gml:AbstractTimeObject, gml:AbstractGeometry, and the following types: gml:MeasureType, gml:MeasureListType, gml:CodeType, gml:CodeOrNilReasonListType, gml:BooleanOrNilReasonListType, gml:IntegerOrNilReasonList. +Of particular interest are elements that are the heads of substitution groups, and one named choice group. These are the primary reasons for the value objects schema, since they may act as variables in the definition of content models, such as Observations, when it is desired to permit alternative value types to occur some of which may have complex content such as arrays, geometry and time objects, and where it is useful not to prescribe the actual value type in advance. The members of the groups include quantities, category classifications, boolean, count, temporal and spatial values, and aggregates of these. +The value objects are defined in a hierarchy. The following relationships are defined: +- Concrete elements gml:Quantity, gml:Category, gml:Count and gml:Boolean are substitutable for the abstract element gml:AbstractScalarValue. +- Concrete elements gml:QuantityList, gml:CategoryList, gml:CountList and gml:BooleanList are substitutable for the abstract element gml:AbstractScalarValueList. +- Concrete element gml:ValueArray is substitutable for the concrete element gml:CompositeValue. +- Abstract elements gml:AbstractScalarValue and gml:AbstractScalarValueList, and concrete elements gml:CompositeValue, gml:ValueExtent, gml:CategoryExtent, gml:CountExtent and gml:QuantityExtent are substitutable for abstract element gml:AbstractValue. +- Abstract elements gml:AbstractValue, gml:AbstractTimeObject and gml:AbstractGeometry are all in a choice group named gml:Value, which is used for compositing in gml:CompositeValue and gml:ValueExtent. +- Schemas which need values may use the abstract element gml:AbstractValue in a content model in order to permit any of the gml:AbstractScalarValues, gml:AbstractScalarValueLists, gml:CompositeValue or gml:ValueExtent to occur in an instance, or the named group gml:Value to also permit gml:AbstractTimeObjects, gml:AbstractGeometrys. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + + + + + + + + + + + + A gml:Category has an optional XML attribute codeSpace, whose value is a URI which identifies a dictionary, codelist or authority for the term. + + + + + + + + + + + + + + + + + + + + + + + An XML attribute uom ("unit of measure") is required, whose value is a URI which identifies the definition of a ratio scale or units by which the numeric value shall be multiplied, or an interval or position scale on which the value occurs. + + + + + + + + + + + + + gml:AbstractValue is an abstract element which acts as the head of a substitution group which contains gml:AbstractScalarValue, gml:AbstractScalarValueList, gml:CompositeValue and gml:ValueExtent, and (transitively) the elements in their substitution groups. +These elements may be used in an application schema as variables, so that in an XML instance document any member of its substitution group may occur. + + + + + gml:AbstractScalarValue is an abstract element which acts as the head of a substitution group which contains gml:Boolean, gml:Category, gml:Count and gml:Quantity, and (transitively) the elements in their substitution groups. + + + + + gml:AbstractScalarValueList is an abstract element which acts as the head of a substitution group which contains gml:BooleanList, gml:CategoryList, gml:CountList and gml:QuantityList, and (transitively) the elements in their substitution groups. + + + + + This is a convenience choice group which unifies generic values defined in this Clause with spatial and temporal objects and the measures described above, so that any of these may be used within aggregate values. + + + + + + + + + + + Property that refers to, or contains, a Value. Convenience element for general use. + + + + + Property that refers to, or contains, a Value. + + + + + + + + + + + + Property that contains Values. + + + + + + + + + + + gml:CompositeValue is an aggregate value built from other values . It contains zero or an arbitrary number of gml:valueComponent elements, and zero or one gml:valueComponents property elements. It may be used for strongly coupled aggregates (vectors, tensors) or for arbitrary collections of values. + + + + + + + + + + + + + + + + A Value Array is used for homogeneous arrays of primitive and aggregate values. +The member values may be scalars, composites, arrays or lists. +ValueArray has the same content model as CompositeValue, but the member values shall be homogeneous. The element declaration contains a Schematron constraint which expresses this restriction precisely. Since the members are homogeneous, the gml:referenceSystem (uom, codeSpace) may be specified on the gml:ValueArray itself and inherited by all the members if desired. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gco/ReadMe.txt b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/ReadMe.txt new file mode 100644 index 0000000..db0b4ed --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/ReadMe.txt @@ -0,0 +1,47 @@ +ISO(c) GCO schema ReadMe.txt +------------------------------------------------------------------------------ + +Geographic COmmon (GCO) extensible markup language + +GCO is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. + +GCO includes all the definitions of http://www.isotc211.org/2005/gco +namespace. The root document of this namespace is the file gco.xsd. + +The most current schemas are available at: +http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------------------- + +2012-07-13 Nicolas Lesage on behalf of the ISO/TC 211 XML Maintenance Group + * Update of readme.txt file and schema annotations + * Use of absolute schema locations of imported namespaces + * Simplification of the schema location of included XML Schemas + * Adoption of W3C Implementation of XLink: + - schemaLocation changed to: http://www.w3.org/1999/xlink.xsd + - xlink:simpleLink renamed xlink:simpleAttrs + * Addition of the version attribute to the schema element. The value of + this attribute is expected to be the date of the last release of the + XML schemas (e.g. 2012-07-13 for this release) + * Include root XML Schema document in all schema documents + + Validation: Schemas have been validated with XML Spy 2010 Rel. 2 (MSXML 6.0) + +2009-03-16 Marcellin Prudham & Nicolas Lesage + * Change of GML namespace: http://www.opengis.net/gml (GML 3.2) => + http://www.opengis.net/gml/3.2 (GML 3.2.1=ISO 19136) + + Note: ISO/TS 19139:2007 (published 2007-04-17) normatively reference + ISO 19136 which was published 2007-08-23. The major change applied to + ISO 19136 is the change of the namespace URI. Previous release of GCO + are not compliant with ISO/TS 19139:2007 + + Validation: Schemas have been validated with XSV 2.10, Xerces J 2.7.1 and + XML Spy 2009 (2009-03-02, IGN / France - Nicolas Lesage / Marcellin Prudham) + +2006-05-04 Marie-Pierre Escher & Nicolas Lesage + * First official release of GCO + * GCO XML Schema files were generated from ISO/TC 211 UML class diagrams + in accordance with ISO/TS 19139:2007. The XML Schema generator is a + Rational Rose Plug-in developed by IGN France (nicolas.lesage@ign.fr). diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gco/basicTypes.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/basicTypes.xsd new file mode 100644 index 0000000..b3353ac --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/basicTypes.xsd @@ -0,0 +1,431 @@ + + + + + Geographic COmmon (GCO) extensible markup language is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. GCO includes all the definitions of http://www.isotc211.org/2005/gco namespace. The root document of this namespace is the file gco.xsd. This basicTypes.xsd schema implements concepts from the "basic types" package of ISO/TS 19103. + + + + + + + + + + + + + A TypeName is a LocalName that references either a recordType or object type in some form of schema. The stored value "aName" is the returned value for the "aName()" operation. This is the types name. - For parsing from types (or objects) the parsible name normally uses a "." navigation separator, so that it is of the form [class].[member].[memberOfMember]. ...) + + + + + + + + + + + + + + + + + + + + + + + A MemberName is a LocalName that references either an attribute slot in a record or recordType or an attribute, operation, or association role in an object instance or type description in some form of schema. The stored value "aName" is the returned value for the "aName()" operation. + + + + + + + + + + + + + + + + + + + + + + + + Use to represent the possible cardinality of a relation. Represented by a set of simple multiplicity ranges. + + + + + + + + + + + + + + + + + + + + + + + A component of a multiplicity, consisting of an non-negative lower bound, and a potentially infinite upper bound. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gco.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gco.xsd new file mode 100644 index 0000000..6090d49 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gco.xsd @@ -0,0 +1,12 @@ + + + + + Geographic COmmon (GCO) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GCO includes all the definitions of http://www.isotc211.org/2005/gco namespace. The root document of this namespace is the file gco.xsd. + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gcoBase.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gcoBase.xsd new file mode 100644 index 0000000..78b9767 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gco/gcoBase.xsd @@ -0,0 +1,63 @@ + + + + + Geographic COmmon (GCO) extensible markup language is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. GCO includes all the definitions of http://www.isotc211.org/2005/gco namespace. The root document of this namespace is the file gco.xsd. This gcoBase.xsd schema provides: + 1. tools to handle specific objects like "code lists" and "record"; + 2. Some XML types representing that do not follow the general encoding rules. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/ReadMe.txt b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/ReadMe.txt new file mode 100644 index 0000000..2c4c7c6 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/ReadMe.txt @@ -0,0 +1,45 @@ +ISO(c) GMD schema ReadMe.txt +------------------------------------------------------------------------------ + +Geographic MetaData (GMD) extensible markup language + +GMD is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. + +GMD includes all the definitions of http://www.isotc211.org/2005/gmd +namespace. The root document of this namespace is the file gmd.xsd. + +The most current schemas are available at: +http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------------------- + +2012-07-13 Nicolas Lesage on behalf of the ISO/TC 211 XML Maintenance Group + * Update of readme.txt file and schema annotations + * Use of absolute schema locations of imported namespaces + * Simplification of the schema location of included XML Schemas + * Addition of the version attribute to the schema element. The value of + this attribute is expected to be the date of the last release of the + XML schemas (e.g. 2012-07-13 for this release) + * Include root XML Schema document in all schema documents + + Validation: Schemas have been validated with XML Spy 2010 Rel. 2 (MSXML 6.0) + +2009-03-16 Marcellin Prudham & Nicolas Lesage + * Change of GML namespace: http://www.opengis.net/gml (GML 3.2) => + http://www.opengis.net/gml/3.2 (GML 3.2.1=ISO 19136) + + Note: ISO/TS 19139:2007 (published 2007-04-17) normatively reference + ISO 19136 which was published 2007-08-23. The major change applied to + ISO 19136 is the change of the namespace URI. Previous release of GMD + are not compliant with ISO/TS 19139:2007 + + Validation: Schemas have been validated with XSV 2.10, Xerces J 2.7.1 and + XML Spy 2009 (2009-03-02, IGN / France - Nicolas Lesage / Marcellin Prudham) + +2006-05-04 Marie-Pierre Escher & Nicolas Lesage + * First official release of GMD + * GMD XML Schema files were generated from ISO/TC 211 UML class diagrams + in accordance with ISO/TS 19139:2007. The XML Schema generator is a + Rational Rose Plug-in developed by IGN France (http://www.ign.fr). + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/applicationSchema.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/applicationSchema.xsd new file mode 100644 index 0000000..f333a2b --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/applicationSchema.xsd @@ -0,0 +1,43 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This applicationSchema.xsd schema implements the UML conceptual schema defined in A.2.12 of ISO 19115:2003. It contains the implementation of the class MD_ApplicationSchemaInformation. + + + + + + + + + + + Information about the application schema used to build the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/citation.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/citation.xsd new file mode 100644 index 0000000..6ec6677 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/citation.xsd @@ -0,0 +1,276 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This citation.xsd schema implements the UML conceptual schema defined in A.3.2 of ISO 19115:2003. It contains the implementation of the following classes: CI_ResponsibleParty, CI_Citation, CI_Address, CI_OnlineResource, CI_Contact, CI_Telephone, URL, CI_Date, CI_Series, CI_RoleCode, CI_PresentationFormCode, CI_OnLineFunctionCode, CI_DateTypeCode. + + + + + + + + + + + Identification of, and means of communication with, person(s) and organisations associated with the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + + Standardized resource reference + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Location of the responsible individual or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information about online sources from which the dataset, specification, or community profile name and extended metadata elements can be obtained. + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information required enabling contact with the responsible person and/or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + Telephone numbers for contacting the responsible individual or organisation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/constraints.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/constraints.xsd new file mode 100644 index 0000000..5986c09 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/constraints.xsd @@ -0,0 +1,107 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This constraints.xsd schema implements the UML conceptual schema defined in A.2.3 of ISO 19115:2003. It contains the implementation of the following classes: MD_Constraints, MD_LegalConstraints, MD_SecurityConstraints, MD_ClassificationCode, MD_RestrictionCode. + + + + + + + + + + Restrictions on the access and use of a dataset or metadata + + + + + + + + + + + + + + + + + + + + + + + Restrictions and legal prerequisites for accessing and using the dataset. + + + + + + + + + + + + + + + + + + + + + + + + + Handling restrictions imposed on the dataset because of national security, privacy, or other concerns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/content.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/content.xsd new file mode 100644 index 0000000..0381452 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/content.xsd @@ -0,0 +1,190 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This content.xsd schema implements the UML conceptual schema defined in ISO 19115:2003, A.2.8. It contains the implementation of the following classes: MD_FeatureCatalogueDescription, MD_CoverageDescription, +MD_ImageDescription, MD_ContentInformation, MD_RangeDimension, MD_Band, MD_CoverageContentTypeCode, MD_ImagingConditionCode. + + + + + + + + + + + Information identifing the feature catalogue + + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the domain of the raster cell + + + + + + + + + + + + + + + + + + + + + + + + + Information about an image's suitability for use + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Set of adjacent wavelengths in the electro-magnetic spectrum with a common characteristic, such as the visible band + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/dataQuality.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/dataQuality.xsd new file mode 100644 index 0000000..cb08ed5 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/dataQuality.xsd @@ -0,0 +1,556 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This dataQuality.xsd schema implements the UML conceptual schema defined in A.2.4 of ISO 19115:2003. It contains the implementation of the following classes: LI_ProcessStep, LI_Source, LI_Lineage, +DQ_ConformanceResult, DQ_QuantitativeResult, DQ_Result, DQ_TemporalValidity, DQ_AccuracyOfATimeMeasurement, DQ_QuantitativeAttributeAccuracy, DQ_NonQuantitativeAttributeAccuracy, DQ_ThematicClassificationCorrectness, DQ_RelativeInternalPositionalAccuracy, DQ_GriddedDataPositionalAccuracy, DQ_AbsoluteExternalPositionalAccuracy, DQ_TopologicalConsistency, DQ_FormatConsistency, DQ_DomainConsistency, DQ_ConceptualConsistency, DQ_CompletenessOmission, DQ_CompletenessCommission, DQ_TemporalAccuracy, DQ_ThematicAccuracy, DQ_PositionalAccuracy, DQ_LogicalConsistency, DQ_Completeness, DQ_Element, DQ_DataQuality. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + quantitative_result from Quality Procedures - - renamed to remove implied use limitiation. + + + + + + + + + + + + + + + + + + + + + + + + + Quantitative_conformance_measure from Quality Procedures. - - Renamed to remove implied use limitation - - OCL - -- result is type specified by valueDomain - result.tupleType = valueDomain + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/distribution.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/distribution.xsd new file mode 100644 index 0000000..435e235 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/distribution.xsd @@ -0,0 +1,203 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This distribution.xsd schema implements the UML conceptual schema defined in A.2.10 of ISO 19115:2003. It contains the implementation of the following classes: MD_Medium, MD_DigitalTransferOptions, MD_StandardOrderProcess, MD_Distributor, MD_Distribution, MD_Format, MD_MediumFormatCode, MD_MediumNameCode. + + + + + + + + + + + Information about the media on which the data can be distributed + + + + + + + + + + + + + + + + + + + + + + + + + + + + Technical means and media by which a dataset is obtained from the distributor + + + + + + + + + + + + + + + + + + + + + + + + + + Common ways in which the dataset may be obtained or received, and related instructions and fee information + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the distributor + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the distributor of and options for obtaining the dataset + + + + + + + + + + + + + + + + + + + + + + + + + Description of the form of the data to be distributed + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/extent.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/extent.xsd new file mode 100644 index 0000000..4ada781 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/extent.xsd @@ -0,0 +1,206 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This extent.xsd schema implements the UML conceptual schema defined in A.3.1 of ISO 19115:2003 and the associated corrigendum. It contains the implementation of the following classes: EX_TemporalExtent, EX_VerticalExtent, EX_BoundingPolygon, EX_Extent, EX_GeographicExtent, EX_GeographicBoundingBox, EX_SpatialTemporalExtent, EX_GeographicDescription. + + + + + + + + + + + + + + Time period covered by the content of the dataset + + + + + + + + + + + + + + + + + + + + + + + Vertical domain of dataset + + + + + + + + + + + + + + + + + + + + + + + + + Boundary enclosing the dataset expressed as the closed set of (x,y) coordinates of the polygon (last point replicates first point) + + + + + + + + + + + + + + + + + + + + + + + Information about spatial, vertical, and temporal extent + + + + + + + + + + + + + + + + + + + + + + + + + + Geographic area of the dataset + + + + + + + + + + + + + + + + + + + + + + + Geographic area of the entire dataset referenced to WGS 84 + + + + + + + + + + + + + + + + + + + + + + + + + + Extent with respect to date and time + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/freeText.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/freeText.xsd new file mode 100644 index 0000000..ff9ffa8 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/freeText.xsd @@ -0,0 +1,123 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This freeText.xsd schema implements cultural and linguistic adaptability extensions defined in 7.3 of ISO/TS 19139:2007. This extension essentially formalizes the free text concept described in Annex J of ISO 19115:2003. For this reason, and in order to simplify the organization of overall geographic metadata XML schema, this schema has been included as part of the gmd namespace instead of the gmx namespace. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/gmd.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/gmd.xsd new file mode 100644 index 0000000..8037c8a --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/gmd.xsd @@ -0,0 +1,12 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/identification.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/identification.xsd new file mode 100644 index 0000000..0e87995 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/identification.xsd @@ -0,0 +1,349 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This identification.xsd schema implements the UML conceptual schema defined in A.2.2 of ISO 19115:2003. It contains the implementation of the following classes: MD_Identification, MD_BrowseGraphic, MD_DataIdentification, MD_ServiceIdentification, MD_RepresentativeFraction, MD_Usage, MD_Keywords, DS_Association, MD_AggregateInformation, MD_CharacterSetCode, MD_SpatialRepresentationTypeCode, MD_TopicCategoryCode, MD_ProgressCode, MD_KeywordTypeCode, DS_AssociationTypeCode, DS_InitiativeTypeCode, MD_ResolutionType. + + + + + + + + + + + + + Basic information about data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Graphic that provides an illustration of the dataset (should include a legend for the graphic) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + See 19119 for further info + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Brief description of ways in which the dataset is currently used. + + + + + + + + + + + + + + + + + + + + + + + + + + Keywords, their type and reference source + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Encapsulates the dataset aggregation information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + High-level geospatial data thematic classification to assist in the grouping and search of available geospatial datasets + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/maintenance.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/maintenance.xsd new file mode 100644 index 0000000..025fb48 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/maintenance.xsd @@ -0,0 +1,87 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This maintenance.xsd schema implements the UML conceptual schema defined in A.2.5 of ISO 19115:2003. It contains the implementation of the following classes: MD_MaintenanceInformation, MD_MaintenanceFrequencyCode, MD_ScopeCode, MD_ScopeDescription. + + + + + + + + + + + + Information about the scope and frequency of updating + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of the class of information covered by the information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataApplication.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataApplication.xsd new file mode 100644 index 0000000..dc889e1 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataApplication.xsd @@ -0,0 +1,176 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This metadataApplication.xsd schema implements the UML conceptual schema defined in A.2.12 of ISO 19115:2003. It contains the implementation of the class: MD_ApplicationSchemaInformation. + + + + + + + + + + + Identifiable collection of datasets + + + + + + + + + + + + + + + + + + + + + + + + + + Identifiable collection of data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataEntity.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataEntity.xsd new file mode 100644 index 0000000..18dee8f --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataEntity.xsd @@ -0,0 +1,71 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This metadataEntity.xsd schema implements the UML conceptual schema defined in A.2.1 of ISO 19115:2003. It contains the implementation of the class MD_Metadata. + + + + + + + + + + + + + + + + + + Information about the metadata + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataExtension.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataExtension.xsd new file mode 100644 index 0000000..f861d78 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/metadataExtension.xsd @@ -0,0 +1,100 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This metadataExtension.xsd schema implements the UML conceptual schema defined in A.2.11 of ISO 19115:2003. It contains the implementation of the following classes: MD_ExtendedElementInformation, MD_MetadataExtensionInformation, MD_ObligationCode, MD_DatatypeCode. + + + + + + + + + + + New metadata element, not found in ISO 19115, which is required to describe geographic data + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Information describing metadata extensions. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/portrayalCatalogue.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/portrayalCatalogue.xsd new file mode 100644 index 0000000..b38b71d --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/portrayalCatalogue.xsd @@ -0,0 +1,37 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This portrayalCatalogue.xsd schema implements the UML conceptual schema defined in A.2.9 of ISO 19115:2003. It contains the implementation of the class MD_PortrayalCatalogueReference. + + + + + + + + + + + Information identifing the portrayal catalogue used + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/referenceSystem.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/referenceSystem.xsd new file mode 100644 index 0000000..035da6d --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/referenceSystem.xsd @@ -0,0 +1,101 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This referenceSystem.xsd schema implements the UML conceptual schema defined in A.2.7 of ISO 19115:2003 and ISO 19115:2003/Cor. 1:2006. It contains the implementation of the following classes: RS_Identifier, MD_ReferenceSystem, MD_Identifier and RS_Reference System. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Description of the spatial and temporal reference systems used in the dataset + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/spatialRepresentation.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/spatialRepresentation.xsd new file mode 100644 index 0000000..74293c3 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gmd/spatialRepresentation.xsd @@ -0,0 +1,238 @@ + + + + + Geographic MetaData (GMD) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GMD includes all the definitions of http://www.isotc211.org/2005/gmd namespace. The root document of this namespace is the file gmd.xsd. This portrayalCatalogue.xsd schema implements the UML conceptual schema defined in A.2.6 of ISO 19115:2003. It contains the implementation of the following classes: MD_GridSpatialRepresentation, MD_VectorSpatialRepresentation, MD_SpatialRepresentation, MD_Georeferenceable, MD_Dimension, MD_Georectified, MD_GeometricObjects, MD_TopologyLevelCode, MD_GeometricObjectTypeCode, MD_CellGeometryCode, MD_DimensionNameTypeCode, MD_PixelOrientationCode. + + + + + + + + + + + + Types and numbers of raster spatial objects in the dataset + + + + + + + + + + + + + + + + + + + + + + + + + + Information about the vector spatial objects in the dataset + + + + + + + + + + + + + + + + + + + + + + + + Digital mechanism used to represent spatial information + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/ReadMe.txt b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/ReadMe.txt new file mode 100644 index 0000000..6bbcd21 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/ReadMe.txt @@ -0,0 +1,45 @@ +ISO(c) GSR schema ReadMe.txt +------------------------------------------------------------------------------ + +Geographic Spatial Referencing (GSR) extensible markup language + +GSR is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. + +GSR includes all the definitions of http://www.isotc211.org/2005/gsr +namespace. The root document of this namespace is the file gsr.xsd. + +The most current schemas are available at: +http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------------------- + +2012-07-13 Nicolas Lesage on behalf of the ISO/TC 211 XML Maintenance Group + * Update of readme.txt file and schema annotations + * Use of absolute schema locations of imported namespaces + * Simplification of the schema location of included XML Schemas + * Addition of the version attribute to the schema element. The value of + this attribute is expected to be the date of the last release of the + XML schemas (e.g. 2012-07-13 for this release) + * Include root XML Schema document in all schema documents + + Validation: Schemas have been validated with XML Spy 2010 Rel. 2 (MSXML 6.0) + +2009-03-16 Marcellin Prudham & Nicolas Lesage + * Change of GML namespace: http://www.opengis.net/gml (GML 3.2) => + http://www.opengis.net/gml/3.2 (GML 3.2.1=ISO 19136) + + Note: ISO/TS 19139:2007 (published 2007-04-17) normatively reference + ISO 19136 which was published 2007-08-23. The major change applied to + ISO 19136 is the change of the namespace URI. Previous release of GSR + are not compliant with ISO/TS 19139:2007 + + Validation: Schemas have been validated with XSV 2.10, Xerces J 2.7.1 and + XML Spy 2009 (2009-03-02, IGN / France - Nicolas Lesage / Marcellin Prudham) + +2006-05-04 Marie-Pierre Escher & Nicolas Lesage + * First official release of GSR + * GSR XML Schema files were generated from ISO/TC 211 UML class diagrams + in accordance with ISO/TS 19139:2007. The XML Schema generator is a + Rational Rose Plug-in developed by IGN France (http://www.ign.fr). + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/gsr.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/gsr.xsd new file mode 100644 index 0000000..a3aacf3 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/gsr.xsd @@ -0,0 +1,12 @@ + + + + + Geographic Spatial Referencing (GSR) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GSR includes all the definitions of http://www.isotc211.org/2005/gsr namespace. The root document of this namespace is the file gsr.xsd. + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/spatialReferencing.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/spatialReferencing.xsd new file mode 100644 index 0000000..32b8b42 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gsr/spatialReferencing.xsd @@ -0,0 +1,25 @@ + + + + + Geographic Spatial Referencing (GSR) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GSR includes all the definitions of http://www.isotc211.org/2005/gsr namespace. The root document of this namespace is the file gsr.xsd. This spatialReferencing.xsd schema contains the implementation of SC_CRS. The encoding of this class is mapped to an ISO 19136 XML type. + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gss/ReadMe.txt b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/ReadMe.txt new file mode 100644 index 0000000..d1d377a --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/ReadMe.txt @@ -0,0 +1,44 @@ +ISO(c) GSS schema ReadMe.txt +------------------------------------------------------------------------------ + +Geographic Spatial Schema (GSS) extensible markup language + +GSS is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. + +GSS includes all the definitions of http://www.isotc211.org/2005/gss +namespace. The root document of this namespace is the file gss.xsd. + +The most current schemas are available at: +http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------------------- + +2012-07-13 Nicolas Lesage on behalf of the ISO/TC 211 XML Maintenance Group + * Update of readme.txt file and schema annotations + * Use of absolute schema locations of imported namespaces + * Simplification of the schema location of included XML Schemas + * Addition of the version attribute to the schema element. The value of + this attribute is expected to be the date of the last release of the + XML schemas (e.g. 2012-07-13 for this release) + * Include root XML Schema document in all schema documents + + Validation: Schemas have been validated with XML Spy 2010 Rel. 2 (MSXML 6.0) + +2009-03-16 Marcellin Prudham & Nicolas Lesage + * Change of GML namespace: http://www.opengis.net/gml (GML 3.2) => + http://www.opengis.net/gml/3.2 (GML 3.2.1=ISO 19136) + + Note: ISO/TS 19139:2007 (published 2007-04-17) normatively reference + ISO 19136 which was published 2007-08-23. The major change applied to + ISO 19136 is the change of the namespace URI. Previous release of GSS + are not compliant with ISO/TS 19139:2007 + + Validation: Schemas have been validated with XSV 2.10, Xerces J 2.7.1 and + XML Spy 2009 (2009-03-02, IGN / France - Nicolas Lesage / Marcellin Prudham) + +2006-05-04 Marie-Pierre Escher & Nicolas Lesage + * First official release of GSS + * GSS XML Schema files were generated from ISO/TC 211 UML class diagrams + in accordance with ISO/TS 19139:2007. The XML Schema generator is a + Rational Rose Plug-in developed by IGN France (nicolas.lesage@ign.fr). diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gss/geometry.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/geometry.xsd new file mode 100644 index 0000000..39d6f3b --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/geometry.xsd @@ -0,0 +1,36 @@ + + + + + Geographic Spatial Schema (GSS) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GSS includes all the definitions of http://www.isotc211.org/2005/gss namespace. The root document of this namespace is the file gss.xsd. This geometry.xsd schema contains the implementation of GM_Object and GM_Point. The encoding of these classes is mapped to ISO 19136 geometric types. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gss/gss.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/gss.xsd new file mode 100644 index 0000000..2594cfe --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gss/gss.xsd @@ -0,0 +1,12 @@ + + + + + Geographic Spatial Schema (GSS) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GSS includes all the definitions of http://www.isotc211.org/2005/gss namespace. The root document of this namespace is the file gss.xsd. + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gts/ReadMe.txt b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/ReadMe.txt new file mode 100644 index 0000000..29b1307 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/ReadMe.txt @@ -0,0 +1,44 @@ +ISO(c) GTS schema ReadMe.txt +------------------------------------------------------------------------------ + +Geographic Temporal Schema (GTS) extensible markup language + +GTS is a component of the XML Schema Implementation of Geographic +Information Metadata documented in ISO/TS 19139:2007. + +GTS includes all the definitions of http://www.isotc211.org/2005/gts +namespace. The root document of this namespace is the file gts.xsd. + +The most current schemas are available at: +http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ + +------------------------------------------------------------------------------- + +2012-07-13 Nicolas Lesage on behalf of the ISO/TC 211 XML Maintenance Group + * Update of readme.txt file and schema annotations + * Use of absolute schema locations of imported namespaces + * Simplification of the schema location of included XML Schemas + * Addition of the version attribute to the schema element. The value of + this attribute is expected to be the date of the last release of the + XML schemas (e.g. 2012-07-13 for this release) + * Include root XML Schema document in all schema documents + + Validation: Schemas have been validated with XML Spy 2010 Rel. 2 (MSXML 6.0) + +2009-03-16 Marcellin Prudham & Nicolas Lesage + * Change of GML namespace: http://www.opengis.net/gml (GML 3.2) => + http://www.opengis.net/gml/3.2 (GML 3.2.1=ISO 19136) + + Note: ISO/TS 19139:2007 (published 2007-04-17) normatively reference + ISO 19136 which was published 2007-08-23. The major change applied to + ISO 19136 is the change of the namespace URI. Previous release of GTS + are not compliant with ISO/TS 19139:2007 + + Validation: Schemas have been validated with XSV 2.10, Xerces J 2.7.1 and + XML Spy 2009 (2009-03-02, IGN / France - Nicolas Lesage / Marcellin Prudham) + +2006-05-04 Marie-Pierre Escher & Nicolas Lesage + * First official release of GTS + * GTS XML Schema files were generated from ISO/TC 211 UML class diagrams + in accordance with ISO/TS 19139:2007. The XML Schema generator is a + Rational Rose Plug-in developed by IGN France (http://www.ign.fr). diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gts/gts.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/gts.xsd new file mode 100644 index 0000000..a4184fd --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/gts.xsd @@ -0,0 +1,12 @@ + + + + + Geographic Temporal Schema (GTS) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GTS includes all the definitions of http://www.isotc211.org/2005/gts namespace. The root document of this namespace is the file gts.xsd. + + + + + + + diff --git a/config/schemas/schema/net/opengis/iso/19139/20070417/gts/temporalObjects.xsd b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/temporalObjects.xsd new file mode 100644 index 0000000..a770ec7 --- /dev/null +++ b/config/schemas/schema/net/opengis/iso/19139/20070417/gts/temporalObjects.xsd @@ -0,0 +1,35 @@ + + + + + Geographic Temporal Schema (GTS) extensible markup language is a component of the XML Schema Implementation of Geographic Information Metadata documented in ISO/TS 19139:2007. GTS includes all the definitions of http://www.isotc211.org/2005/gts namespace. The root document of this namespace is the file gts.xsd. The temporalObjects.xsd schema contains the XML implementation of TM_Object, TM_Primitive and TM_PeriodDuration from ISO 19108. The encoding of these classes is mapped to ISO 19136 temporal types and W3C built-in types. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/SWEArrayObservation.sch b/config/schemas/schema/net/opengis/om/2.0/SWEArrayObservation.sch new file mode 100644 index 0000000..0f315a5 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/SWEArrayObservation.sch @@ -0,0 +1,47 @@ + + + + + + SWE array observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for SWEArrayObservations

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/SWEScalarObservation.sch b/config/schemas/schema/net/opengis/om/2.0/SWEScalarObservation.sch new file mode 100644 index 0000000..73d3956 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/SWEScalarObservation.sch @@ -0,0 +1,48 @@ + + + + + + SWE scalar observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for + SWEScalarObservations

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/categoryObservation.sch b/config/schemas/schema/net/opengis/om/2.0/categoryObservation.sch new file mode 100644 index 0000000..e6e2dd1 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/categoryObservation.sch @@ -0,0 +1,40 @@ + + + + + + Category observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for CategoryObservations

+ + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/complexObservation.sch b/config/schemas/schema/net/opengis/om/2.0/complexObservation.sch new file mode 100644 index 0000000..7e32397 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/complexObservation.sch @@ -0,0 +1,48 @@ + + + + + + Complex observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for + ComplexObservations

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/countObservation.sch b/config/schemas/schema/net/opengis/om/2.0/countObservation.sch new file mode 100644 index 0000000..d829375 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/countObservation.sch @@ -0,0 +1,38 @@ + + + + + Count observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for CountObservations

+ + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/geometryObservation.sch b/config/schemas/schema/net/opengis/om/2.0/geometryObservation.sch new file mode 100644 index 0000000..6fc69ae --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/geometryObservation.sch @@ -0,0 +1,42 @@ + + + + + Geometry observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for GeometryObservations

+ + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/measurement.sch b/config/schemas/schema/net/opengis/om/2.0/measurement.sch new file mode 100644 index 0000000..b776cce --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/measurement.sch @@ -0,0 +1,43 @@ + + + + + + Measurement validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for Measurements

+ + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/observation.xsd b/config/schemas/schema/net/opengis/om/2.0/observation.xsd new file mode 100644 index 0000000..a67da21 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/observation.xsd @@ -0,0 +1,432 @@ + + + + observation.xsd + + Observations and Measurements - XML Implementation is an OGC Standard. + + Copyright (c) [2010] Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. + + + + + + + + + + + + + Base type for Observations. Observation is an act ("event"), whose result + is an estimate of the value of a property of the feature of interest. The observed + property may be any property associated with the type of the feature of interest. + Concrete observation types must add a *result* property of a suitable type. + + + + + + If present, the sub-element 'type' shall indicate the class of + observation. A register of type identifiers corresponding with the + observation types in ISO 19156, which distinguishes types on the basis of + the type of the result, is provided by OGC at + http://www.opengis.net/def/observationType/OGC-OM/2.0/ + + + + + If present, the association Metadata shall link the + OM_Observation to descriptive metadata. + + + + + Some observations depend on other observations to provide + context which is important, sometimes essential, in understanding the + result. These dependencies are stronger than mere spatiotemporal + coincidences, requiring explicit representation. If present, the association + class ObservationContext (Figure 2) shall link a OM_Observation to another + OM_Observation, with the role name relatedObservation for the target. + + + + + + The attribute phenomenonTime:TM_Object shall describe the time + that the result (6.2.2.9) applies to the property of the feature-of-interest + (6.2.2.7). This is often the time of interaction by a sampling procedure + (8.1.3) or observation procedure (6.2.2.10) with a real-world feature. + + + + + + + The attribute resultTime:TM_Instant shall describe the time when + the result became available, typically when the procedure (6.2.2.10) + associated with the observation was completed For some observations this is + identical to the samplingTime. However, there are important cases where they + differ. + + + + + If present, the attribute validTime:TM_Period shall describe the + time period during which the result is intended to be used. + + + + + The association ProcessUsed shall link the OM_Observation to the + OM_Process (6.2.3) used to generate the result. The process has the role + procedure with respect to the observation. A process might be responsible + for more than one generatedObservation. + + + + + If present, the attributes parameter:NamedValue shall describe + an arbitrary event-specific parameter. This might be an environmental + parameter, an instrument setting or input, or an event-specific sampling + parameter that is not tightly bound to either the feature-of-interest + (6.2.2.7) or to the observation procedure (6.2.2.10). To avoid ambiguity, + there shall be no more than one parameter with the same name. NOTE + Parameters that are tightly bound to the procedure may be recorded as part + of the procedure description. In some contexts the Observation::procedure + (6.2.2.10) is a generic or standard procedure, rather than an event-specific + process. In this context, parameters bound to the observation act, such as + instrument settings, calibrations or inputs, local position, detection + limits, asset identifier, operator, may augment the description of a + standard procedure. + + + + + + xs:anyType + + The association Phenomenon shall link the OM_Observation to the + GFI_PropertyType (C.2.2) for which the OM_Observation:result (6.2.2.9) + provides an estimate of its value. The property type has the role + observedProperty with respect to the observation. The observed property + shall be a phenomenon associated with the type of the featureOfInterest. + NOTE An observed property may, but need not be modelled as a property (in + the sense of the General Feature Model) in a formal application schema that + defines the type of the feature of interest The observed property supports + semantic or thematic classification of observations, which is useful for + discovery and data fusion. + + + + + The association Domain shall link the OM_Observation to the + GFI_Feature (C.2.1) that is the subject of the observation and carries the + observed property. This feature has the role featureOfInterest with respect + to the observation. This feature is the real-world object whose properties + are under observation, or is a feature intended to sample the real-world + object, as described in Clause 8 of this International Standard. An + observation instance serves as a propertyValueProvider for its feature of + interest. + + + + + If present, the attributes resultQuality:DQ_Element shall + describe the quality of the result (6.2.2.9). This instance-specific + description complements the description of the observation procedure + (6.2.2.10), which provides information concerning the quality of all + observations using this procedure. Quality of a result may be assessed + following the procedures in ISO 19114:2003. Multiple measures may be + provided (ISO/TS 19138:2006). + + + + + + + + + + + The association Range shall link the OM_Observation to the value + generated by the procedure. The value has the role result with respect to the + observation. The type of the result is shown as Any, since it may represent the + value of any feature property. NOTE 1 OGC SWE Common provides a model suitable for + describing many kinds of observation results. The type of the observation result + shall be consistent with the observed property, and the scale or scope for the value + shall be consistent with the quantity or category type. If the observed property + (6.2.2.8) is a spatial operation or function, the type of the result may be a + coverage, NOTE 2 In some contexts, particularly in earth and environmental sciences, + the term “observation” is used to refer to the result itself. + + + + + + + + Generic observation, whose result is anyType The following properties + are inherited from AbstractFeatureType: + + + + + + + + + + + + + + + + Observation is an act ("event"), whose result is an estimate of the value + of a property of the feature of interest. The observed property may be any property + associated with the type of the feature of interest. + + + + + + + + + + + + + + + Some observations depend on other observations to provide context which + is important, sometimes essential, in understanding the result. These dependencies + are stronger than mere spatiotemporal coincidences, requiring explicit + representation. If present, the association class ObservationContext (Figure 2) + shall link a OM_Observation to another OM_Observation, with the role name + relatedObservation for the target. + + + + + The attribute 'role' shall describe the relationship of the + target OM_Observation to the source OM_Observation. + + + + + + om:OM_Observation + + Some observations depend on other observations to provide + context which is important, sometimes essential, in understanding the + result. These dependencies are stronger than mere spatiotemporal + coincidences, requiring explicit representation. If present, the association + class ObservationContext (Figure 2) shall link a OM_Observation to another + OM_Observation, with the role name relatedObservation for the target. + + + + + + + + + Some observations depend on other observations to provide context which + is important, sometimes essential, in understanding the result. These dependencies + are stronger than mere spatiotemporal coincidences, requiring explicit + representation. If present, the association class ObservationContext (Figure 2) + shall link a OM_Observation to another OM_Observation, with the role name + relatedObservation for the target. + + + + + + ObservationContext is a dataType, without identity, so may only be used + inline + + + + + + + + + + + The purpose of an observation process is to generate an observation + result. An instance is often an instrument or sensor, but may be a human observer, a + simulator, or a process or algorithm applied to more primitive results used as + inputs. The model for OM_Process is abstract, and has no attributes, operations, or + associations. NOTE ISO 19115-2:2008 provides MI_Instrument, LE_Processing and + LE_Algorithm, which could all be modelled as specializations of OM_Process. Any + suitable XML may be used to describe the observation process in line, provided that + it is contained in a single XML element. If reference to a schema is provided it + must also be valid. OGC SensorML provides a model which is suitable for many + observation procedures. + + + + + Any suitable XML may be used to describe the observation process + in line, provided that it is contained in a single XML element. If refernece + to a schema is provided it must also be valid. + + + + + + + + + + + The class 'NamedValue' provides for a generic soft-typed parameter + value. NamedValue shall support two attributes. + + + + + The attribute 'name' shall indicate the meaning of the named + value. Its value should be taken from a well-governed source if possible. + + + + + + The attribute 'value' shall provide the value. The type Any + should be substituted by a suitable concrete type, such as + CI_ResponsibleParty or Measure. + + + + + + + + The class 'NamedValue' provides for a generic soft-typed parameter + value. NamedValue shall support two attributes. + + + + + + The class 'NamedValue' provides for a generic soft-typed parameter + value. NamedValue shall support two attributes. + + + + + + + + + + + + This property type is not provided directly by GML + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/result-DataArray.sch b/config/schemas/schema/net/opengis/om/2.0/result-DataArray.sch new file mode 100644 index 0000000..bfc5989 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-DataArray.sch @@ -0,0 +1,4 @@ + +result must contain an element in the substitution group headed by swe:DataArray, swe:Matrix or swe:DataStream and with inline values diff --git a/config/schemas/schema/net/opengis/om/2.0/result-DataRecord.sch b/config/schemas/schema/net/opengis/om/2.0/result-DataRecord.sch new file mode 100644 index 0000000..fcbaf2e --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-DataRecord.sch @@ -0,0 +1,5 @@ + +result must contain an element in the substitution group + headed by swe:DataRecord or swe:Vector diff --git a/config/schemas/schema/net/opengis/om/2.0/result-SimpleComponent.sch b/config/schemas/schema/net/opengis/om/2.0/result-SimpleComponent.sch new file mode 100644 index 0000000..bd561ec --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-SimpleComponent.sch @@ -0,0 +1,5 @@ + +result must contain an element in the substitution group + headed by swe:AbstractSimpleComponent with an inline value diff --git a/config/schemas/schema/net/opengis/om/2.0/result-boolean.sch b/config/schemas/schema/net/opengis/om/2.0/result-boolean.sch new file mode 100644 index 0000000..f577696 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-boolean.sch @@ -0,0 +1,4 @@ + +result type must be xs:boolean diff --git a/config/schemas/schema/net/opengis/om/2.0/result-category.sch b/config/schemas/schema/net/opengis/om/2.0/result-category.sch new file mode 100644 index 0000000..3c8f412 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-category.sch @@ -0,0 +1,5 @@ + +result + model must match gml:ReferenceType diff --git a/config/schemas/schema/net/opengis/om/2.0/result-geometry.sch b/config/schemas/schema/net/opengis/om/2.0/result-geometry.sch new file mode 100644 index 0000000..07071a8 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-geometry.sch @@ -0,0 +1,5 @@ + +result must contain an element in the + substitution group headed by gml:AbstractGeometry diff --git a/config/schemas/schema/net/opengis/om/2.0/result-integer.sch b/config/schemas/schema/net/opengis/om/2.0/result-integer.sch new file mode 100644 index 0000000..63b0df4 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-integer.sch @@ -0,0 +1,4 @@ + +result type must be xs:integer diff --git a/config/schemas/schema/net/opengis/om/2.0/result-measure.sch b/config/schemas/schema/net/opengis/om/2.0/result-measure.sch new file mode 100644 index 0000000..894c4ff --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-measure.sch @@ -0,0 +1,5 @@ + +result + model must match gml:MeasureType diff --git a/config/schemas/schema/net/opengis/om/2.0/result-temporal.sch b/config/schemas/schema/net/opengis/om/2.0/result-temporal.sch new file mode 100644 index 0000000..a5ab2ef --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/result-temporal.sch @@ -0,0 +1,5 @@ + +result must contain an element in + the substitution group headed by gml:AbstractTimeObject diff --git a/config/schemas/schema/net/opengis/om/2.0/resultTypeConsistent.sch b/config/schemas/schema/net/opengis/om/2.0/resultTypeConsistent.sch new file mode 100644 index 0000000..bdfc5cc --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/resultTypeConsistent.sch @@ -0,0 +1,122 @@ + + + + + + Observation validation +

This Schematron schema checks that the content model of each observation result is consistent + with the type of the observation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/spatialObservation.sch b/config/schemas/schema/net/opengis/om/2.0/spatialObservation.sch new file mode 100644 index 0000000..d79233c --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/spatialObservation.sch @@ -0,0 +1,59 @@ + + + + + + Spatial observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for SpatialObservations

+ + + + + + + Req http://www.opengis.net/req/omxml/2.0/data/spatial-parameter , Req + http://www.opengis.net/req/omxml/2.0/data/spatial-parameter-name + + + Requirement http://www.opengis.net/req/omxml/2.0/data/spatial-parameter : A spatial + observation shall have exactly one sampling geometry encoded as XML element + om:parameter in an observation. Requirement + http://www.opengis.net/req/omxml/2.0/data/spatial-parameter-name: The xlink:href + attribute in the XML element om:name of the om:parameter/om:NamedValue element that + carries the sampling geometry SHALL have the value + 'http://www.opengis.net/req/omxml/2.0/data/samplingGeometry'. + + + + Req http://www.opengis.net/req/omxml/2.0/data/spatial-parameter-value + + Requirement + http://www.opengis.net/req/omxml/2.0/data/spatial-parameter-value : The XML element + om:value in the om:parameter/om:NamedValue element which carries the sampling + geometry shall have a value of type gml:AbstractGeometry. + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/specializingObservationExample.xsd b/config/schemas/schema/net/opengis/om/2.0/specializingObservationExample.xsd new file mode 100644 index 0000000..365cf15 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/specializingObservationExample.xsd @@ -0,0 +1,92 @@ + + + + specializingObsevationExample.xsd + + This example shows how to generate a + specialized observation type for XML Schema validation + + Observations and Measurements - XML Implementation is an OGC Standard. + + Copyright (c) [2010] Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. + + + + + + + + + + + + + Replace with your favorite type definition + + + + + + + + + Observation whose result is expressed as a 'SomeType' + + + + + + + + + + + + + + + + Observation whose result is expressed as a 'SomeType' + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/temporalObservation.sch b/config/schemas/schema/net/opengis/om/2.0/temporalObservation.sch new file mode 100644 index 0000000..9bb4874 --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/temporalObservation.sch @@ -0,0 +1,44 @@ + + + + + + Temporal observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for TemporalObservations

+ + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/om/2.0/truthObservation.sch b/config/schemas/schema/net/opengis/om/2.0/truthObservation.sch new file mode 100644 index 0000000..989ca0c --- /dev/null +++ b/config/schemas/schema/net/opengis/om/2.0/truthObservation.sch @@ -0,0 +1,41 @@ + + + + + + Truth observation validation +

Verifies that all instances of OM_Observation or elements derived from OM_Observation (i.e. having an om:resultTime property) have a result that matches the pattern for TruthObservations

+ + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/sampling/2.0/samplingFeature.xsd b/config/schemas/schema/net/opengis/sampling/2.0/samplingFeature.xsd new file mode 100644 index 0000000..acccc35 --- /dev/null +++ b/config/schemas/schema/net/opengis/sampling/2.0/samplingFeature.xsd @@ -0,0 +1,260 @@ + + + + samplingFeature.xsd + + Observations and Measurements - XML Implementation is an OGC Standard. + + Copyright (c) [2010] Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. + + + + + + + + + + + + + + + + If present, the sub-element 'type' shall indicate the class of + spatial sampling feature. A register of type identifiers corresponding with + the sampling feature types in ISO 19156 is provided by OGC at + http://www.opengis.net/def/samplingFeatureType/OGC-OM/2.0/ + + + + + A sampling feature is established in order to make observations + concerning some domain feature. The association Intention shall link the + SF_SamplingFeature to the feature which the sampling feature was designed to + sample. The target of this association has the role sampledFeature with + respect to the sampling feature, and shall not be a sampling feature. It is + usually a real-world feature from an application domain (Figures 5 and 10). + + + + + + If present, the attribute lineage:LI_Lineage shall describe the + history and provenance of the SF_SamplingFeature. This might include + information relating to the handling of the specimen, or details of the + survey procedure of a spatial sampling feature. + + + + + Sampling features are distinctive compared with other features + from application domains by having navigable associations to observations. + If present, the association Design shall link the SF_SamplingFeature to an + OM_Observation that was made utilizing the sampling feature, and the + description of the sampling feature provides an intrinsic element of the + observation protocol, along with the observation procedure (6.2.2.10) and + the decomposition of the domain geometry in the case of a coverage-valued + result (7.3.1). The OM_Observation has the role relatedObservation with + respect to the sampling feature. Multiple observations may be made on a + single sampling feature. + + + + + Sampling features are frequently related to each other, as parts + of complexes, through sub-sampling, and in other ways. If present, the + association class SamplingFeatureComplex (Figure 9) shall link a + SF_SamplingFeature to another SF_SamplingFeature. + + + + + If present, the attributes parameter:NamedValue shall describe + an arbitrary parameter associated with the SF_SamplingFeature. This might be + a parameter that qualifies the interaction with the sampled feature, or an + environmental parameter associated with the sampling process. + + + + + + + + + + + A "SamplingFeature" is a feature used primarily for taking + observations. + + + + + + + + + + + + + + + + + + + + + + A "SamplingFeatureRelation" is used to describe relationships between + sampling features, including part-whole, siblings, etc. + + + + + + + + + + + + + + + + + + + + + The class SF_SamplingFeatureCollection (Figure 9) is an instance of the + «metaclass» GF_FeatureType (ISO 19109:2005), which therefore represents a feature + type. SF_SamplingFeatureCollection shall support one association. + + + + + + + The association Collection shall link a + SF_SamplingFeatureCollection to member SF_SamplingFeatures. + + + + + + + + + + + + + + + + + + + + + + The purpose of a sampling feature process is to generate or transform a + sampling feature. The model for SF_Process is abstract, and has no attributes, + operations, or associations. Any suitable XML may be used to describe the sampling + feature process in line, provided that it is contained in a single XML element. If + reference to a schema is provided it must also be valid. + + + + + Any suitable XML may be used to describe the sampling feature + process in line, provided that it is contained in a single XML element. If + refernece to a schema is provided it must also be valid. + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingCurve.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingCurve.sch new file mode 100644 index 0000000..f2a08de --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingCurve.sch @@ -0,0 +1,47 @@ + + + + + + Sampling point validation +

Verifies that all instances of SF_SpatialSamplingFeature have a shape that matches the pattern for SamplingCurve

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingPoint.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingPoint.sch new file mode 100644 index 0000000..2652ec8 --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingPoint.sch @@ -0,0 +1,46 @@ + + + + + Sampling point validation +

Verifies that all instances of SF_SpatialSamplingFeature have a shape that matches the pattern for SamplingPoint

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSolid.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSolid.sch new file mode 100644 index 0000000..fe7ee85 --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSolid.sch @@ -0,0 +1,47 @@ + + + + + + Sampling point validation +

Verifies that all instances of SF_SpatialSamplingFeature have a shape that matches the pattern for SamplingSolid

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSurface.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSurface.sch new file mode 100644 index 0000000..31fc4be --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/samplingSurface.sch @@ -0,0 +1,48 @@ + + + + + + Sampling point validation +

Verifies that all instances of SF_SpatialSamplingFeature have a shape that matches the + pattern for SamplingSurface

+ + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-curve.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-curve.sch new file mode 100644 index 0000000..ac1b39b --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-curve.sch @@ -0,0 +1,5 @@ + +a member of the substitution group + headed by gml:Curve or an xlink must be present as child of sams:shape diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-point.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-point.sch new file mode 100644 index 0000000..50300d2 --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-point.sch @@ -0,0 +1,5 @@ + +a member of the substitution group + headed by gml:Point or an xlink must be present as child of sams:shape diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-solid.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-solid.sch new file mode 100644 index 0000000..b4b83f5 --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-solid.sch @@ -0,0 +1,5 @@ + +a member of the substitution group + headed by gml:AbstractSolid or an xlink must be present as child of sams:shape diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-surface.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-surface.sch new file mode 100644 index 0000000..6d12cf0 --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shape-surface.sch @@ -0,0 +1,5 @@ + +a member of the substitution group + headed by gml:AbstractSurface or an xlink must be present as child of sams:shape diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/shapeTypeConsistent.sch b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shapeTypeConsistent.sch new file mode 100644 index 0000000..e7b82ce --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/shapeTypeConsistent.sch @@ -0,0 +1,73 @@ + + + + + + Spatial sampling feature validation +

This Schematron schema checks that the content model of each sampling feature shape is + consistent with the type of the sampling feature.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/net/opengis/samplingSpatial/2.0/spatialSamplingFeature.xsd b/config/schemas/schema/net/opengis/samplingSpatial/2.0/spatialSamplingFeature.xsd new file mode 100644 index 0000000..c8a7b5c --- /dev/null +++ b/config/schemas/schema/net/opengis/samplingSpatial/2.0/spatialSamplingFeature.xsd @@ -0,0 +1,157 @@ + + + + spatialSamplingFeature.xsd + + Observations and Measurements - XML Implementation is an OGC Standard. + + Copyright (c) [2010] Open Geospatial Consortium. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. + + + + + + + + + + + + + + + When observations are made to estimate properties of a geospatial + feature, in particular where the value of a property varies within the scope of the + feature, a spatial sampling feature is used. Depending on accessibility and on the + nature of the expected property variation, the sampling feature may be extensive in + one, two or three spatial dimensions. Processing and visualization methods are often + dependent on the topological dimension of the sampling manifold, so this provides a + natural classification system for sampling features. This classification follows + common practice in focussing on conventional spatial dimensions. Properties observed + on sampling features may be time-dependent, but the temporal axis does not generally + contribute to the classification of sampling feature classes. Sampling feature + identity is usually less time-dependent than is the property value. + + + + + A common role for a spatial sampling feature is to host + instruments or procedures deployed repetitively or permanently. If present, + the association Platform shall link the SF_SpatialSamplingFeature to an + OM_Process deployed at it. The OM_Process has the role hostedProcedure with + respect to the sampling feature. + + + + + Positioning metadata is commonly associated with sampling + features defined in the context of field surveys. If present, + positionalAccuracy:DQ_PositionalAccuracy shall describe the accuracy of the + positioning of the sampling feature. Up to two instances of the attribute + support the independent description of horizontal and vertical accuracy. + + + + + + + + + + + + + + + + + + + + + + + When observations are made to estimate properties of a geospatial + feature, in particular where the value of a property varies within the scope of the + feature, a spatial sampling feature is used. Depending on accessibility and on the + nature of the expected property variation, the sampling feature may be extensive in + one, two or three spatial dimensions. Processing and visualization methods are often + dependent on the topological dimension of the sampling manifold, so this provides a + natural classification system for sampling features. This classification follows + common practice in focussing on conventional spatial dimensions. Properties observed + on sampling features may be time-dependent, but the temporal axis does not generally + contribute to the classification of sampling feature classes. Sampling feature + identity is usually less time-dependent than is the property value. + + + + + + + + The association Geometry shall link a + SF_SpatialSamplingFeature to a GM_Object that describes its shape. + + + + + + + + + + + + + + + + + + + diff --git a/config/schemas/schema/org/w3c/1999/xlink.xsd b/config/schemas/schema/org/w3c/1999/xlink.xsd new file mode 100644 index 0000000..b89d6e8 --- /dev/null +++ b/config/schemas/schema/org/w3c/1999/xlink.xsd @@ -0,0 +1,275 @@ + + + + + + + + + + This schema document provides attribute declarations and +attribute group, complex type and simple type definitions which can be used in +the construction of user schemas to define the structure of particular linking +constructs, e.g. + + + + + + + ... + + ... + + + ... +]]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Intended for use as the type of user-declared elements to make them + simple links. + + + + + + + + + + + + + + + + + + + + + + + + + Intended for use as the type of user-declared elements to make them + extended links. + Note that the elements referenced in the content model are all abstract. + The intention is that by simply declaring elements with these as their + substitutionGroup, all the right things will happen. + + + + + + + + + + + + + + xml:lang is not required, but provides much of the + motivation for title elements in addition to attributes, and so + is provided here for convenience. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + label is not required, but locators have no particular + XLink function if they are not labeled. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + from and to have default behavior when values are missing + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/config/schemas/schema/org/w3c/2001/xml.xsd b/config/schemas/schema/org/w3c/2001/xml.xsd new file mode 100644 index 0000000..aea7d0d --- /dev/null +++ b/config/schemas/schema/org/w3c/2001/xml.xsd @@ -0,0 +1,287 @@ + + + + + + +
+

About the XML namespace

+ +
+

+ This schema document describes the XML namespace, in a form + suitable for import by other schema documents. +

+

+ See + http://www.w3.org/XML/1998/namespace.html and + + http://www.w3.org/TR/REC-xml for information + about this namespace. +

+

+ Note that local names in this namespace are intended to be + defined only by the World Wide Web Consortium or its subgroups. + The names currently defined in this namespace are listed below. + They should not be used with conflicting semantics by any Working + Group, specification, or document instance. +

+

+ See further below in this document for more information about how to refer to this schema document from your own + XSD schema documents and about the + namespace-versioning policy governing this schema document. +

+
+
+ + + + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + + +
+ +

space (as an attribute name)

+

+ denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification.

+ +
+ + + + + + + + + + + + +
+ +

base (as an attribute name)

+

+ denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification.

+ +

+ See http://www.w3.org/TR/xmlbase/ + for information about this attribute. +

+
+ + + + + + + +
+ +

id (as an attribute name)

+

+ denotes an attribute whose value + should be interpreted as if declared to be of type ID. + This name is reserved by virtue of its definition in the + xml:id specification.

+ +

+ See http://www.w3.org/TR/xml-id/ + for information about this attribute. +

+
+ + + + + + + + + + + + + +
+ +

Father (in any context at all)

+ +
+

+ denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: +

+
+

+ In appreciation for his vision, leadership and + dedication the W3C XML Plenary on this 10th day of + February, 2000, reserves for Jon Bosak in perpetuity + the XML name "xml:Father". +

+
+
+
+ + + + + +
+

About this schema document

+ +
+

+ This schema defines attributes and an attribute group suitable + for use by schemas wishing to allow xml:base, + xml:lang, xml:space or + xml:id attributes on elements they define. +

+

+ To enable this, such a schema must import this schema for + the XML namespace, e.g. as follows: +

+ 
+          <schema . . .>
+           . . .
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+

+ or +

+ 
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
+
+

+ Subsequently, qualified reference to any of the attributes or the + group defined below will have the desired effect, e.g. +

+ 
+          <type . . .>
+           . . .
+           <attributeGroup ref="xml:specialAttrs"/>
+
+

+ will define a type which will schema-validate an instance element + with any of those attributes. +

+
+
+ + + + + +
+

Versioning policy for this schema document

+
+

+ In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + + http://www.w3.org/2009/01/xml.xsd. +

+

+ At the date of issue it can also be found at + + http://www.w3.org/2001/xml.xsd. +

+

+ The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML + Schema itself, or with the XML namespace itself. In other words, + if the XML Schema or XML namespaces change, the version of this + document at + http://www.w3.org/2001/xml.xsd + + will change accordingly; the version at + + http://www.w3.org/2009/01/xml.xsd + + will not change. +

+

+ Previous dated (and unchanging) versions of this schema + document are at: +

+ +
+
+ + + + + diff --git a/iwxxm.cmd b/iwxxm.cmd new file mode 100644 index 0000000..224b7b2 --- /dev/null +++ b/iwxxm.cmd @@ -0,0 +1 @@ +java -jar bin/ibl-iwxxm-utils.jar -Djava.net.preferIPv4Stack=true %* \ No newline at end of file diff --git a/iwxxm.sh b/iwxxm.sh new file mode 100644 index 0000000..ac6547b --- /dev/null +++ b/iwxxm.sh @@ -0,0 +1,2 @@ +!/bin/bash +java -jar bin/ibl-iwxxm-utils.jar -Djava.net.preferIPv4Stack=true "$@" \ No newline at end of file diff --git a/pom.xml b/pom.xml new file mode 100644 index 0000000..e15287e --- /dev/null +++ b/pom.xml @@ -0,0 +1,208 @@ + + + + 4.0.0 + com.iblsoft.iwxxm + ibl-iwxxm-validator + 1.0.0 + jar + + + IBL Software Engineering, spol. s r.o. + http://www.iblsoft.com + + IWXXM Validator + + + UTF-8 + + + + + + com.google.guava + guava + 19.0 + + + + commons-io + commons-io + 2.2 + + + + commons-cli + commons-cli + 1.3.1 + + + + org.aeonbits.owner + owner + 1.0.9 + + + + org.apache.ant + ant + 1.7.1 + + + + + ch.qos.logback + logback-classic + 1.0.7 + + + + + javax.servlet + servlet-api + 2.5 + provided + + + + javax.portlet + portlet-api + 2.0 + + + + org.eclipse.jetty + jetty-plus + 9.2.14.v20151106 + + + + org.eclipse.jetty + jetty-servlet + 9.2.14.v20151106 + + + + + xerces + xmlParserAPIs + 2.6.2 + + + + xerces + xercesImpl + 2.11.0 + + + + xml-resolver + xml-resolver + 1.2 + + + + net.sf.saxon + Saxon-HE + 9.7.0-6 + + + + + com.fasterxml.jackson.core + jackson-databind + 2.5.2 + + + + com.fasterxml.jackson.core + jackson-annotations + 2.5.2 + + + + com.github.briandilley.jsonrpc4j + jsonrpc4j + 1.4.6 + + + + + junit + junit + 4.12 + test + + + + + + ibl-iwxxm-utils + + + + org.apache.maven.plugins + maven-compiler-plugin + 3.3 + + 1.7 + 1.7 + + + + + org.codehaus.mojo + exec-maven-plugin + 1.1 + + + + java + + + + + com.iblsoft.iwxxm.webservice.Main + + + + + maven-assembly-plugin + + + jar-with-dependencies + + ${user.dir}/target + + + com.iblsoft.iwxxm.webservice.Main + + + + + + make-assembly + pre-integration-test + + single + + + + + + + + diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/Main.java b/src/main/java/com/iblsoft/iwxxm/webservice/Main.java new file mode 100644 index 0000000..781e695 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/Main.java @@ -0,0 +1,180 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice; + +import com.iblsoft.iwxxm.webservice.config.ConfigManager; +import com.iblsoft.iwxxm.webservice.config.Configuration; +import com.iblsoft.iwxxm.webservice.util.Log; +import com.iblsoft.iwxxm.webservice.validator.IwxxmValidator; +import com.iblsoft.iwxxm.webservice.validator.ValidationError; +import com.iblsoft.iwxxm.webservice.validator.ValidationResult; +import com.iblsoft.iwxxm.webservice.ws.ValidationServlet; +import org.apache.commons.cli.*; +import org.apache.commons.io.FileUtils; +import org.apache.tools.ant.DirectoryScanner; +import org.eclipse.jetty.server.Handler; +import org.eclipse.jetty.server.NCSARequestLog; +import org.eclipse.jetty.server.Server; +import org.eclipse.jetty.server.handler.RequestLogHandler; +import org.eclipse.jetty.servlet.ServletHandler; +import org.eclipse.jetty.util.RolloverFileOutputStream; + +import java.io.File; +import java.io.IOException; +import java.io.PrintStream; +import java.nio.charset.StandardCharsets; +import java.util.List; +import java.util.TimeZone; + +public class Main { + + private static Options commandLineOptions = createCommandLineOptions(); + private static CommandLine commandLine; + + public static void main(String[] args) throws Exception { + parseCommandLine(args); + if (commandLine.hasOption("s")) { + runAsService(); + } else if (commandLine.hasOption("v")) { + List files = commandLine.getArgList(); + if (files.isEmpty()) { + printHelp(); + } else { + validateFiles(files); + } + } else { + printHelp(); + } + } + + private static void runAsService() throws Exception { + Configuration configuration = ConfigManager.getConfiguration(); + + File logFilePath = new File(configuration.getLogDir(), configuration.getLogFileNamePattern()); + RolloverFileOutputStream os = new RolloverFileOutputStream(logFilePath.getAbsolutePath(), true, configuration.getLogRetainInDays(), TimeZone.getTimeZone("UTC")); + PrintStream logStream = new PrintStream(os); + + Handler handler = createValidationServletHandler(configuration); + if (configuration.isAccessLogEnabled()) { + handler = createAccessLogHandler(configuration, handler); + } + + printServiceHelp(configuration); + + Server server = new Server(configuration.getServerPort()); + server.setHandler(handler); + + System.setOut(logStream); + System.setErr(logStream); + server.start(); + Log.INSTANCE.info("IBL IWXXM Web Service started [{}]", configuration.getServerPort()); + + server.join(); + } + + private static void printServiceHelp(Configuration configuration) { + System.out.println("IWXXM web service started at http://localhost:" + configuration.getServerPort() + configuration.getJsonRpcServiceRootUrl()); + System.out.println("Press Ctrl+C to stop..."); + } + + private static Handler createValidationServletHandler(Configuration configuration) { + ServletHandler servletHandler = new ServletHandler(); + servletHandler.addServletWithMapping(ValidationServlet.class, configuration.getJsonRpcServiceRootUrl()); + return servletHandler; + } + + private static RequestLogHandler createAccessLogHandler(Configuration configuration, Handler handler) { + File logFilePath = new File(configuration.getAccessLogDir(), configuration.getAccessLogFileNamePattern()); + + NCSARequestLog requestLog = new NCSARequestLog(logFilePath.toString()); + requestLog.setAppend(true); + requestLog.setLogLatency(true); + requestLog.setExtended(configuration.isExtendedAccessLog()); + requestLog.setLogDateFormat(configuration.getAccessLogDateTimeFormat()); + requestLog.setLogTimeZone(configuration.getAccessLogTimeZone()); + requestLog.setPreferProxiedForAddress(configuration.isProxiedAddressPreferredInAccessLog()); + requestLog.setRetainDays(configuration.getAccessLogRetainInDays()); + + RequestLogHandler requestLogHandler = new RequestLogHandler(); + requestLogHandler.setRequestLog(requestLog); + requestLogHandler.setHandler(handler); + return requestLogHandler; + } + + private static void validateFiles(List files) { + Configuration configuration = ConfigManager.getConfiguration(); + IwxxmValidator iwxxmValidator = new IwxxmValidator(configuration.getValidationCatalogFile(), configuration.getValidationRulesDir(), configuration.getDefaultIwxxmVersion()); + for (String filePath : files) { + filePath = filePath.replace("//", "/"); + File localFile = new File(filePath); + DirectoryScanner scanner = new DirectoryScanner(); + if (!localFile.isAbsolute()) { + scanner.setBasedir("."); + } + scanner.setIncludes(new String[]{filePath}); + scanner.scan(); + String[] expandedFiles = scanner.getIncludedFiles(); + if (expandedFiles.length == 0) { + System.out.println("No file matches the pattern " + filePath); + } + for (String file : expandedFiles) { + System.out.print("Validating file " + file + " ... "); + try { + ValidationResult result = iwxxmValidator.validate(FileUtils.readFileToString(new File(file), StandardCharsets.UTF_8.name()), null); + if (result.isValid()) { + System.out.println("Validation successful"); + } else { + System.out.println("Validation failed"); + for (ValidationError ve : result.getValidationErrors()) { + System.out.println(" " + ve); + } + } + } catch (IOException e) { + System.out.println(); + System.out.println("Error: " + e.getMessage()); + System.exit(1); + return; + } + } + } + } + + private static void parseCommandLine(String[] args) { + try { + CommandLineParser parser = new DefaultParser(); + commandLine = parser.parse(commandLineOptions, args); + } catch (ParseException e) { + System.out.println("Error: " + e.getMessage()); + System.out.println(); + printHelp(); + System.exit(1); + } + } + + private static void printHelp() { + HelpFormatter formatter = new HelpFormatter(); + formatter.printHelp("iwxxm [options] [FILEs]\n\noptions:", commandLineOptions); + } + + private static Options createCommandLineOptions() { + Options options = new Options(); + options.addOption("s", "service", false, "run as json-rpc web service"); + options.addOption("v", "validate", false, "validate provided IWXXM XML files"); + options.addOption("?", "help", false, "show ussage"); + return options; + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/config/ConfigManager.java b/src/main/java/com/iblsoft/iwxxm/webservice/config/ConfigManager.java new file mode 100644 index 0000000..fdb6fa8 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/config/ConfigManager.java @@ -0,0 +1,74 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.config; + +import com.google.common.collect.Maps; +import org.aeonbits.owner.ConfigFactory; + +import java.util.HashMap; +import java.util.Map; +import java.util.Properties; + +/** + * Utility class which provides access to configuration option saved in configuration file. + */ +public class ConfigManager { + + private static final String PROPERTY_KEY_CONFIG_ROOT_DIR = "configDir"; + private static final String DEFAULT_CONFIG_ROOT_DIR = "./config/"; + private static Map globalProperties; + + static { + init(); + } + + private static String getConfigDirectoryRootPath() { + Properties systemProperties = System.getProperties(); + + String dirName = systemProperties.getProperty(PROPERTY_KEY_CONFIG_ROOT_DIR, ""); + if (dirName.isEmpty()) { + dirName = DEFAULT_CONFIG_ROOT_DIR; + } + + if (!dirName.endsWith("/")) { + dirName += "/"; + } + + return dirName; + } + + public static Configuration getConfiguration() { + return ConfigFactory.create(Configuration.class, globalProperties); + } + + private static void init() { + Properties systemProperties = System.getProperties(); + Map environmentProperties = System.getenv(); + String configRootDir = getConfigDirectoryRootPath(); + + globalProperties = new HashMap<>(); + globalProperties.putAll(Maps.fromProperties(systemProperties)); + globalProperties.putAll(environmentProperties); + globalProperties.put("configDir", configRootDir); + + for (Map.Entry entry : globalProperties.entrySet()) { + String key = entry.getKey(); + String value = entry.getValue(); + ConfigFactory.setProperty(key, value); + } + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/config/Configuration.java b/src/main/java/com/iblsoft/iwxxm/webservice/config/Configuration.java new file mode 100644 index 0000000..1b63627 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/config/Configuration.java @@ -0,0 +1,105 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ +package com.iblsoft.iwxxm.webservice.config; + + +import org.aeonbits.owner.Config; + +import java.io.File; + +/** + * The interface for configuration options loaded from the ${configDir}/iwxxm-webservice-config.properties or + * ${configDir}/iwxxm-webservice-config.xml file. + * Dynamic proxy class is automatically generated for this interface by OWNER library. + */ +@Config.LoadPolicy(Config.LoadType.MERGE) +@Config.Sources({ + "file:${configDir}/iwxxm-webservice-config.xml", + "file:${configDir}/iwxxm-webservice-config.properties"}) +public interface Configuration extends Config { + + @Key("server.port") + @DefaultValue("8040") + int getServerPort(); + + @Key("server.allow-access-allow-origin") + @DefaultValue("*") + String getAccessControlAllowOriginHeader(); + + @Key("log.dir") + @DefaultValue("./logs/") + File getLogDir(); + + @Key("log.filename-pattern") + @DefaultValue("ibl-vw-iwxxm-webservice.yyyy_mm_dd.log") + String getLogFileNamePattern(); + + @Key("log.retain-in-days") + @DefaultValue("30") + int getLogRetainInDays(); + + @Key("access-log.enabled") + @DefaultValue("true") + boolean isAccessLogEnabled(); + + @Key("access-log.dir") + @DefaultValue("./logs/") + File getAccessLogDir(); + + @Key("access-log.filename-pattern") + @DefaultValue("ibl-vw-iwxxm-webservice.yyyy_mm_dd.access.log") + String getAccessLogFileNamePattern(); + + @Key("access-log.retain-in-days") + @DefaultValue("90") + int getAccessLogRetainInDays(); + + @Key("access-log.format.time-zone") + @DefaultValue("GMT") + String getAccessLogTimeZone(); + + @Key("access-log.format.date-time-format") + @DefaultValue("yyyy-MM-dd'T'HH:mm:ssZ") + String getAccessLogDateTimeFormat(); + + @Key("access-log.format.extended") + @DefaultValue("true") + boolean isExtendedAccessLog(); + + @Key("access-log.format.prefer-proxied") + @DefaultValue("true") + boolean isProxiedAddressPreferredInAccessLog(); + + @Key("iwxxm.default-version") + @DefaultValue("") + String getDefaultIwxxmVersion(); + + @Key("iwxxm.validation.schemas-dir") + @DefaultValue("${configDir}/schemas") + File getValidationSchemasDir(); + + @Key("iwxxm.validation.catalog-file") + @DefaultValue("${iwxxm.validation.schemas-dir}/catalog.xml") + File getValidationCatalogFile(); + + @Key("iwxxm.validation.rules-dir") + @DefaultValue("${iwxxm.validation.schemas-dir}/rule") + File getValidationRulesDir(); + + @Key("iwxxm.validation.service-url") + @DefaultValue("/json-rpc") + String getJsonRpcServiceRootUrl(); +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/util/Log.java b/src/main/java/com/iblsoft/iwxxm/webservice/util/Log.java new file mode 100644 index 0000000..6e6a486 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/util/Log.java @@ -0,0 +1,45 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + + +package com.iblsoft.iwxxm.webservice.util; + +import org.slf4j.LoggerFactory; + +/** + * Utility class for logging information, warning or debug messages into log file. + */ +public enum Log { + INSTANCE; + + private org.slf4j.Logger logger = LoggerFactory.getLogger("com.iblsoft.vw.iwxxm.webservice"); + + public boolean isDebugEnabled() { + return logger.isDebugEnabled(); + } + + public void info(String message, Object... args) { + logger.info(message, args); + } + + public void warn(String message, Object... args) { + logger.warn(message, args); + } + + public void debug(String message, Object... args) { + logger.debug(message, args); + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/IwxxmValidator.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/IwxxmValidator.java new file mode 100644 index 0000000..0138954 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/IwxxmValidator.java @@ -0,0 +1,126 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + * --------------------------------------------------------------------------------------------- + * + * Notice: + * + * This file is based on source code from Command-line Refuter of Unshapely XML (CRUX) + * developed by Developed by NCAR's Research Applications Laboratory (http://www.ral.ucar.edu) + * + * Copyright (c) 2016. University Corporation for Atmospheric Research (UCAR). All rights reserved. + * See also https://github.com/NCAR/crux/blob/master/LICENSE for more information about CRUX license. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.validator; + +import com.iblsoft.iwxxm.webservice.util.Log; +import org.apache.commons.io.filefilter.WildcardFileFilter; + +import java.io.File; +import java.io.FileFilter; +import java.io.StringReader; +import java.util.ArrayList; +import java.util.List; +import java.util.regex.Pattern; + +import static com.google.common.base.Preconditions.checkArgument; +import static com.google.common.base.Preconditions.checkNotNull; +import static com.google.common.base.Strings.nullToEmpty; + +/** + * Performs XSD and schematron validation of IWXXM messages. + */ +public class IwxxmValidator { + + private final File validationCatalogFile; + private final File validationRulesDir; + private final String defaultIwxxmVersion; + private final Pattern iwxxmVersionPattern = Pattern.compile("^[0-9a-zA-Z_-]+(\\.[0-9a-zA-Z]+)*$"); + private SchematronValidator schematronValidator = new SchematronValidator(); + + public IwxxmValidator(File validationCatalogFile, File validationRulesDir, String defaultIwxxmVersion) { + this.validationCatalogFile = checkNotNull(validationCatalogFile); + this.validationRulesDir = checkNotNull(validationRulesDir); + this.defaultIwxxmVersion = nullToEmpty(defaultIwxxmVersion); + } + + public ValidationResult validate(String iwxxmData, String iwxxmVersion) { + Log.INSTANCE.debug("IwxxmWebService.validate request started"); + + if (iwxxmVersion == null) { + iwxxmVersion = defaultIwxxmVersion; + } + + String catalogFile = validationCatalogFile.getAbsolutePath(); + XML10Validator validator = new XML10Validator(catalogFile); + + List errors = new ArrayList<>(); + try { + printValidatingXMLSchema(catalogFile); + ValidationResult xsdValidationResult; + try (StringReader reader = new StringReader(iwxxmData)) { + xsdValidationResult = validator.validate(reader); + errors.addAll(xsdValidationResult.getValidationErrors()); + } + + if (iwxxmVersion.isEmpty()) { + iwxxmVersion = xsdValidationResult.getDetectedIwxxmVersion(); + if (Log.INSTANCE.isDebugEnabled()) { + Log.INSTANCE.debug("IWXXM version detected: {}", iwxxmVersion); + } + } + + checkIwxxmVersion(iwxxmVersion); + File[] schematronFiles = getSchematronFiles(iwxxmVersion); + if (schematronFiles != null && schematronFiles.length > 0) { + for (File schematronFile : schematronFiles) { + if (Log.INSTANCE.isDebugEnabled()) { + Log.INSTANCE.debug("Validating against Schematron rules {}", schematronFile.getName()); + } + + ValidationResult schematronValidationResult = schematronValidator.validate(iwxxmData, schematronFile.getAbsolutePath()); + errors.addAll(schematronValidationResult.getValidationErrors()); + } + } + } catch (Exception e) { + errors.add(new ValidationError(e.getMessage(), "", 0, 0)); + } + + return new ValidationResult(iwxxmVersion, errors); + } + + private static void printValidatingXMLSchema(String catalogFile) { + if (Log.INSTANCE.isDebugEnabled()) { + StringBuilder sb = new StringBuilder(); + sb.append("Validating"); + sb.append(" against XML schema"); + if (catalogFile != null && !catalogFile.isEmpty()) { + sb.append(" using the following catalog: "); + sb.append(catalogFile); + } + Log.INSTANCE.debug(sb.toString()); + } + } + + private File[] getSchematronFiles(String iwxxmVersion) { + File file = new File(validationRulesDir, iwxxmVersion); + return file.listFiles((FileFilter) new WildcardFileFilter("*.sch")); + } + + private void checkIwxxmVersion(String iwxxmVersion) { + checkArgument(iwxxmVersion != null && iwxxmVersionPattern.matcher(iwxxmVersion).matches(), "Invalid characters in IWXXM version"); + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/SchematronValidator.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/SchematronValidator.java new file mode 100644 index 0000000..9715470 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/SchematronValidator.java @@ -0,0 +1,243 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + * --------------------------------------------------------------------------------------------- + * + * Notice: + * + * This file is based on source code from Command-line Refuter of Unshapely XML (CRUX) + * developed by Developed by NCAR's Research Applications Laboratory (http://www.ral.ucar.edu) + * + * Copyright (c) 2016. University Corporation for Atmospheric Research (UCAR). All rights reserved. + * See also https://github.com/NCAR/crux/blob/master/LICENSE for more information about CRUX license. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.validator; + +import net.sf.saxon.Configuration; +import net.sf.saxon.om.TreeModel; +import net.sf.saxon.s9api.*; +import org.apache.commons.io.FileUtils; +import org.apache.commons.io.IOUtils; + +import javax.xml.transform.Source; +import javax.xml.transform.SourceLocator; +import javax.xml.transform.TransformerException; +import javax.xml.transform.URIResolver; +import javax.xml.transform.stream.StreamSource; +import java.io.*; +import java.nio.charset.StandardCharsets; +import java.util.ArrayList; +import java.util.HashMap; +import java.util.List; +import java.util.Map; + +/** + * Validates XML files against Schematron rules. This uses the ISO Schematron XSLT files, which are then executed by + * Saxon. + * + * This class currently calls Saxon via the main() method. While it is possible to call sub-classes of Saxon directly, + * the Transform class which is called by the main() method is complicated and not very easy to figure out how to use + * directly. An improvement would be to call the Saxon classes directly rather than through main() + */ +class SchematronValidator { + + private static Map schematronTransformCache = new HashMap<>(); + + public ValidationResult validate(String inputXml, String schematronFile) throws Exception { + SaxonTransform saxonTransform = new SaxonTransform(); + ErrorListener errorListener = new ErrorListener(); + String validationXsltContent = getSchematronXslt(schematronFile); + XsltBundle validationXslt = new XsltBundle(validationXsltContent); + saxonTransform.transform(validationXslt, inputXml, errorListener); + + if (errorListener.hasErrors()) { + return new ValidationResult("", errorListener.getErrors()); + } else { + return new ValidationResult("", null); + } + } + + private String loadResourceFile(String resourcePath) { + try (InputStream stream = this.getClass().getResourceAsStream(resourcePath)) { + return IOUtils.toString(stream); + } catch (IOException e) { + throw new RuntimeException(e); + } + } + + private XsltBundle createSchematronXslt() { + String messageXslt = this.loadResourceFile("/iso-schematron-xslt2/iso_schematron_message_xslt2.xsl"); + String schematronSkeletonXslt = this.loadResourceFile("/iso-schematron-xslt2/iso_schematron_skeleton_for_saxon.xsl"); + return new XsltBundle(messageXslt) + .addImport("iso_schematron_skeleton_for_saxon.xsl", schematronSkeletonXslt); + } + + private synchronized String getSchematronXslt(String schematronFile) { + String xslt = schematronTransformCache.get(schematronFile); + if (xslt == null) { + SaxonTransform saxonTransform = new SaxonTransform(); + XsltBundle schematronXslt = createSchematronXslt(); + + XdmNode output; + try { + String schematronRules = FileUtils.readFileToString(new File(schematronFile)); + output = saxonTransform.transform(schematronXslt, schematronRules, null); + } catch (Exception e) { + return null; + } + xslt = output.toString(); + schematronTransformCache.put(schematronFile, xslt); + } + return xslt; + } + + /** + * Helper class to handle transformation errors. + */ + private static class ErrorListener implements javax.xml.transform.ErrorListener, MessageListener { + private List errors = new ArrayList<>(); + private List warnings = new ArrayList<>(); + + private ErrorListener() { + } + + public List getErrors() { + return errors; + } + + @Override + public void warning(TransformerException exception) throws TransformerException { + warnings.add(String.format("Warning on line %d col %d: %s", exception.getLocator().getLineNumber(), exception.getLocator().getColumnNumber(), exception.getMessage())); + } + + @Override + public void error(TransformerException exception) throws TransformerException { + errors.add(translateException(exception)); + } + + @Override + public void fatalError(TransformerException exception) throws TransformerException { + errors.add(translateException(exception)); + } + + @Override + public void message(XdmNode xdmNode, boolean b, SourceLocator sourceLocator) { + if (sourceLocator != null) { + errors.add(new ValidationError(xdmNode.toString(), "", sourceLocator.getLineNumber(), sourceLocator.getColumnNumber())); + } else { + errors.add(new ValidationError(xdmNode.toString(), "", null, null)); + } + } + + public boolean hasErrors() { + return errors.size() > 0; + } + + private ValidationError translateException(TransformerException e) { + SourceLocator locator = e.getLocator(); + if (locator != null) { + return new ValidationError(e.getMessage(), "", locator.getLineNumber(), locator.getColumnNumber()); + } + + return new ValidationError(e.getMessage(), "", null, null); + } + } + + /** + * Helper class to handle Saxon XSLT transfromation. + */ + private static class SaxonTransform { + final private XsltCompiler xsltCompiler; + private Processor processor = null; + + public SaxonTransform() { + this.processor = new Processor(new Configuration()); + this.xsltCompiler = this.processor.newXsltCompiler(); + } + + public XdmNode transform(XsltBundle xslt, String sourceContent, ErrorListener errorListener) throws IOException, SaxonApiException { + XsltTransformer xsltTransformer = null; + try { + XsltExecutable xsltExecutable = compileXslt(xslt); + xsltTransformer = xsltExecutable.load(); + if (errorListener != null) { + xsltTransformer.setErrorListener(errorListener); + xsltTransformer.setMessageListener(errorListener); + } + + XdmNode source = this.createXdmNodeFromString(sourceContent); + xsltTransformer.setInitialContextNode(source); + XdmDestination resultTree = new XdmDestination(); + xsltTransformer.setDestination(resultTree); + xsltTransformer.transform(); + + return resultTree.getXdmNode(); + } finally { + if (xsltTransformer != null) { + xsltTransformer.close(); + } + } + } + + private XsltExecutable compileXslt(XsltBundle xslt) throws SaxonApiException { + try (StringReader reader = new StringReader(xslt.getMainXsltContent())) { + StreamSource source = new StreamSource(reader); + xsltCompiler.setURIResolver(xslt); + return xsltCompiler.compile(source); + } + } + + private XdmNode createXdmNodeFromString(String xmlAsString) throws IOException, SaxonApiException { + try (InputStream inputStream = new ByteArrayInputStream(xmlAsString.getBytes(StandardCharsets.UTF_8))) { + DocumentBuilder documentBuilder = processor.newDocumentBuilder(); + documentBuilder.setTreeModel(TreeModel.TINY_TREE); + StreamSource source = new StreamSource(inputStream); + return documentBuilder.build(source); + } + } + } + + /** + * Helper class which allows to process XSLT with imports from other files. + */ + private static class XsltBundle implements URIResolver { + private String mainXsltContent; + private Map importableUris = new HashMap<>(); + + public XsltBundle(String mainXsltContent) { + this.mainXsltContent = mainXsltContent; + } + + public String getMainXsltContent() { + return mainXsltContent; + } + + public final XsltBundle addImport(String systemId, String xsltContent) { + importableUris.put(systemId, xsltContent); + return this; + } + + @Override + public Source resolve(String href, String base) throws TransformerException { + if (importableUris.containsKey(href)) { + String contentAsString = importableUris.get(href); + return new StreamSource(new StringReader(contentAsString)); + } else { + throw new TransformerException("Cannot resolve uri: " + href); + } + } + } +} \ No newline at end of file diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationError.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationError.java new file mode 100644 index 0000000..65c3543 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationError.java @@ -0,0 +1,73 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + * --------------------------------------------------------------------------------------------- + * + * Notice: + * + * This file is based on source code from Command-line Refuter of Unshapely XML (CRUX) + * developed by Developed by NCAR's Research Applications Laboratory (http://www.ral.ucar.edu) + * + * Copyright (c) 2016. University Corporation for Atmospheric Research (UCAR). All rights reserved. + * See also https://github.com/NCAR/crux/blob/master/LICENSE for more information about CRUX license. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.validator; + +/** + * A validation error class which represents the error and the relevant location within the validated file + */ +public class ValidationError { + private String error; + private String fileName; + private Integer lineNumber; + private Integer columnNumber; + + /** + * @param error The error that caused a validation problem + * @param fileName The file in which the error occurred + * @param lineNumber The line number of the end of the text that + * caused the error or warning + * @param columnNumber The column number of the end of the text that + * caused the error or warning + */ + public ValidationError(String error, String fileName, Integer lineNumber, Integer columnNumber) { + this.error = error; + this.fileName = fileName; + this.lineNumber = lineNumber; + this.columnNumber = columnNumber; + } + + public String getError() { + return error; + } + + public String getFileName() { + return fileName; + } + + public Integer getLineNumber() { + return lineNumber; + } + + public Integer getColumnNumber() { + return columnNumber; + } + + @Override + public String toString() { + return String.format("line %d, col %d: %s", lineNumber == null ? 0 : lineNumber, columnNumber == null ? 0 : columnNumber, getError()); + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationResult.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationResult.java new file mode 100644 index 0000000..ef1b39c --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/ValidationResult.java @@ -0,0 +1,60 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + + +package com.iblsoft.iwxxm.webservice.validator; + +import java.util.Collections; +import java.util.List; + +import static com.google.common.base.Strings.nullToEmpty; + +/** + * Holds the result of validation of IWXXM message. + */ +public class ValidationResult { + private String detectedIwxxmVersion; + private List validationErrors; + + public ValidationResult(String detectedIwxxmVersion, List validationErrors) { + this.detectedIwxxmVersion = nullToEmpty(detectedIwxxmVersion); + if (validationErrors == null || validationErrors.isEmpty()) { + this.validationErrors = Collections.emptyList(); + } else { + this.validationErrors = Collections.unmodifiableList(validationErrors); + } + } + + public boolean isValid() { + return this.validationErrors.isEmpty(); + } + + public List getValidationErrors() { + return validationErrors; + } + + public String getDetectedIwxxmVersion() { + return detectedIwxxmVersion; + } + + @Override + public String toString() { + return "ValidationResult{" + + "valid=" + isValid() + + "validation errors count=" + validationErrors.size() + + "}"; + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/XML10Validator.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/XML10Validator.java new file mode 100644 index 0000000..9e46e78 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/XML10Validator.java @@ -0,0 +1,128 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + * --------------------------------------------------------------------------------------------- + * + * Notice: + * + * This file is based on source code from Command-line Refuter of Unshapely XML (CRUX) + * developed by Developed by NCAR's Research Applications Laboratory (http://www.ral.ucar.edu) + * + * Copyright (c) 2016. University Corporation for Atmospheric Research (UCAR). All rights reserved. + * See also https://github.com/NCAR/crux/blob/master/LICENSE for more information about CRUX license. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.validator; + +import org.xml.sax.*; +import org.xml.sax.ext.EntityResolver2; +import org.xml.sax.helpers.DefaultHandler; + +import javax.xml.parsers.ParserConfigurationException; +import javax.xml.parsers.SAXParser; +import javax.xml.parsers.SAXParserFactory; +import java.io.IOException; +import java.io.Reader; +import java.util.ArrayList; +import java.util.List; +import java.util.Locale; + +/** + * Validator of XML and XSD files against XML schema 1.0 + */ +class XML10Validator { + private EntityResolver2 resolver; + + public XML10Validator(String... catalogLocations) { + if (catalogLocations.length > 0) { + resolver = new XmlCatalogResolver(catalogLocations, true); + } + } + + public ValidationResult validate(Reader reader) throws ParserConfigurationException, SAXException, IOException { + SAXParserFactory factory = SAXParserFactory.newInstance(); + factory.setValidating(true); + factory.setNamespaceAware(true); + + ErrorHandler errorHandler = new ErrorHandler(); + VersionDetectionHandler versionDetectionHandler = new VersionDetectionHandler(); + + SAXParser parser = factory.newSAXParser(); + parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema"); + + XMLReader xmlReader = parser.getXMLReader(); + if (resolver != null) { + xmlReader.setProperty("http://apache.org/xml/properties/internal/entity-resolver", resolver); + } + + xmlReader.setErrorHandler(errorHandler); + xmlReader.setContentHandler(versionDetectionHandler); + xmlReader.parse(new InputSource(reader)); + + return new ValidationResult(versionDetectionHandler.getVersion(), errorHandler.getFailures()); + } + + /** + * Detects the version of IWXXM message. Version is taken from the first XML element which namespace + * is starting with http://icao.int/iwxxm/. Detected version is then returned by getVersion() method. + */ + private static class VersionDetectionHandler extends DefaultHandler { + private static final String IWXXM_NAMESPACE_PATTERN = "HTTP://ICAO.INT/IWXXM/"; + private String version; + + public String getVersion() { + return version; + } + + @Override + public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException { + if (version == null) { + if (uri != null && uri.toUpperCase(Locale.ROOT).startsWith(IWXXM_NAMESPACE_PATTERN)) { + version = uri.substring(IWXXM_NAMESPACE_PATTERN.length()); + } + } + } + } + + /** + * Gathers the warnings and errors into a list of ValidationErrors + */ + private static class ErrorHandler implements org.xml.sax.ErrorHandler { + private List failures = new ArrayList(); + + public List getFailures() { + return failures; + } + + @Override + public void warning(SAXParseException exception) throws SAXException { + failures.add(translateException(exception)); + } + + @Override + public void error(SAXParseException exception) throws SAXException { + failures.add(translateException(exception)); + } + + @Override + public void fatalError(SAXParseException exception) throws SAXException { + failures.add(translateException(exception)); + } + + private ValidationError translateException(SAXParseException exception) { + return new ValidationError(exception.getMessage(), "", exception.getLineNumber(), exception.getColumnNumber()); + } + } +} \ No newline at end of file diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/validator/XmlCatalogResolver.java b/src/main/java/com/iblsoft/iwxxm/webservice/validator/XmlCatalogResolver.java new file mode 100644 index 0000000..4ca7827 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/validator/XmlCatalogResolver.java @@ -0,0 +1,84 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + * --------------------------------------------------------------------------------------------- + * + * Notice: + * + * This file is based on source code from Command-line Refuter of Unshapely XML (CRUX) + * developed by Developed by NCAR's Research Applications Laboratory (http://www.ral.ucar.edu) + * + * Copyright (c) 2016. University Corporation for Atmospheric Research (UCAR). All rights reserved. + * See also https://github.com/NCAR/crux/blob/master/LICENSE for more information about CRUX license. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.validator; + +import com.iblsoft.iwxxm.webservice.util.Log; +import org.apache.xerces.impl.xs.XSDDescription; +import org.apache.xerces.xni.XMLResourceIdentifier; +import org.apache.xerces.xni.XNIException; + +import java.io.IOException; + +/** + * Extends Xerces's XMLCatalogResolver for debugging purposes. By default debugging messages are disabled + */ +class XmlCatalogResolver extends org.apache.xerces.util.XMLCatalogResolver { + private boolean allowRemoteResources; + + XmlCatalogResolver(String[] catalogLocations, boolean preferPublic) { + this(catalogLocations, preferPublic, false); + } + + /** + * @param catalogLocations the path to XML catalog files + * @param preferPublic whether public or system matches are preferred + */ + XmlCatalogResolver(String[] catalogLocations, boolean preferPublic, boolean allowRemoteResources) { + this.allowRemoteResources = allowRemoteResources; + setCatalogList(catalogLocations); + setPreferPublic(preferPublic); + } + + + @Override + public String resolveIdentifier(XMLResourceIdentifier xmlResourceIdentifier) throws IOException, XNIException { + if (xmlResourceIdentifier == null || !(xmlResourceIdentifier instanceof XSDDescription) || + xmlResourceIdentifier.getNamespace() == null) { + return super.resolveIdentifier(xmlResourceIdentifier); + } + XSDDescription desc = (XSDDescription) xmlResourceIdentifier; + String id = super.resolveIdentifier(xmlResourceIdentifier); + + String expandedSystemId = id; + if (expandedSystemId == null) { + expandedSystemId = xmlResourceIdentifier.getExpandedSystemId(); + } + + if (!expandedSystemId.startsWith("file:")) { + Log.INSTANCE.warn("Identifier {} is not resolved to local path (resolved to {})", desc.getLiteralSystemId(), expandedSystemId); + if (!allowRemoteResources) { + throw new IllegalStateException(String.format("Identifier %s is not resolved to local path (resolved to %s). Only resources stored in local catalog are enbaled.", + desc.getLiteralSystemId(), expandedSystemId)); + } + } + + if (Log.INSTANCE.isDebugEnabled()) { + Log.INSTANCE.debug("Resolved identifier: namespace: {} publicId={] systemId={} to {}", xmlResourceIdentifier.getNamespace(), desc.getPublicId(), desc.getLiteralSystemId(), expandedSystemId); + } + return id; + } +} \ No newline at end of file diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebService.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebService.java new file mode 100644 index 0000000..f7847a9 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebService.java @@ -0,0 +1,34 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + + +package com.iblsoft.iwxxm.webservice.ws; + +import com.googlecode.jsonrpc4j.JsonRpcParam; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationRequest; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationResponse; + +/** + * Interface of JSON RPC web service. + */ +public interface IwxxmWebService { + /** + * Validates IWXXM message in the request. + * @param request Data to be validated. + * @return Result of message validation. + */ + ValidationResponse validate(@JsonRpcParam("request") ValidationRequest request); +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/ValidationServlet.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/ValidationServlet.java new file mode 100644 index 0000000..934554e --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/ValidationServlet.java @@ -0,0 +1,85 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws; + +import com.google.common.net.HttpHeaders; +import com.googlecode.jsonrpc4j.JsonRpcServer; +import com.iblsoft.iwxxm.webservice.config.ConfigManager; +import com.iblsoft.iwxxm.webservice.config.Configuration; +import com.iblsoft.iwxxm.webservice.ws.internal.IwxxmWebServiceImpl; +import org.apache.commons.io.IOUtils; + +import javax.servlet.ServletConfig; +import javax.servlet.ServletException; +import javax.servlet.http.HttpServlet; +import javax.servlet.http.HttpServletRequest; +import javax.servlet.http.HttpServletResponse; +import java.io.IOException; +import java.io.InputStream; + +import static com.google.common.base.Strings.nullToEmpty; + +/** + * Servlet for handling HTTP request of validator web service. + */ +public class ValidationServlet extends HttpServlet { + + private JsonRpcServer jsonRpcServer; + private String allowOriginHeader; + + @Override + public void init(ServletConfig config) throws ServletException { + Configuration configuration = ConfigManager.getConfiguration(); + IwxxmWebService webService = new IwxxmWebServiceImpl( + configuration.getValidationCatalogFile(), + configuration.getValidationRulesDir(), + configuration.getDefaultIwxxmVersion()); + this.allowOriginHeader = nullToEmpty(configuration.getAccessControlAllowOriginHeader()); + this.jsonRpcServer = new JsonRpcServer(webService); + } + + @Override + protected void doOptions(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { + super.doOptions(request, response); + addCorsResponseHeaders(response); + } + + @Override + protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { + try (InputStream stream = this.getClass().getResourceAsStream("/get-help-response.txt")) { + IOUtils.copy(stream, response.getWriter()); + } + + response.setContentType("text/plain"); + response.setStatus(200); + addCorsResponseHeaders(response); + } + + @Override + protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { + addCorsResponseHeaders(response); + this.jsonRpcServer.handle(request, response); + } + + private void addCorsResponseHeaders(HttpServletResponse response) { + if (!this.allowOriginHeader.isEmpty()) { + response.addHeader(HttpHeaders.ACCESS_CONTROL_ALLOW_ORIGIN, this.allowOriginHeader); + response.addHeader(HttpHeaders.ACCESS_CONTROL_ALLOW_METHODS, "GET, POST,OPTIONS"); + response.addHeader(HttpHeaders.ACCESS_CONTROL_ALLOW_HEADERS, HttpHeaders.CONTENT_TYPE); + } + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/internal/IwxxmWebServiceImpl.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/internal/IwxxmWebServiceImpl.java new file mode 100644 index 0000000..303fd92 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/internal/IwxxmWebServiceImpl.java @@ -0,0 +1,62 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws.internal; + +import com.googlecode.jsonrpc4j.JsonRpcParam; +import com.iblsoft.iwxxm.webservice.util.Log; +import com.iblsoft.iwxxm.webservice.validator.IwxxmValidator; +import com.iblsoft.iwxxm.webservice.validator.ValidationError; +import com.iblsoft.iwxxm.webservice.validator.ValidationResult; +import com.iblsoft.iwxxm.webservice.ws.IwxxmWebService; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationRequest; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationResponse; + +import java.io.File; + +import static com.google.common.base.Preconditions.checkArgument; + +/** + * Implementation class of IwxxmWebService interface. + */ +public class IwxxmWebServiceImpl implements IwxxmWebService { + + private final IwxxmValidator iwxxmValidator; + + public IwxxmWebServiceImpl(File validationCatalogFile, File validationRulesDir, String defaultIwxxmVersion) { + this.iwxxmValidator = new IwxxmValidator(validationCatalogFile, validationRulesDir, defaultIwxxmVersion); + } + + @Override + public ValidationResponse validate(@JsonRpcParam("request") ValidationRequest request) { + Log.INSTANCE.debug("IwxxmWebService.validate request started"); + + checkRequestVersion(request.getRequestVersion()); + + ValidationResult validationResult = iwxxmValidator.validate(request.getIwxxmData(), request.getIwxxmVersion()); + ValidationResponse.Builder responseBuilder = ValidationResponse.builder(); + for (ValidationError ve : validationResult.getValidationErrors()) { + responseBuilder.addValidationError(ve.getError(), ve.getLineNumber(), ve.getColumnNumber()); + } + + Log.INSTANCE.debug("IwxxmWebService.validate request finished"); + return responseBuilder.build(); + } + + private void checkRequestVersion(String requestVersion) { + checkArgument(requestVersion != null && requestVersion.equals("1.0"), "Unsupported request version."); + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationError.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationError.java new file mode 100644 index 0000000..b0f9638 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationError.java @@ -0,0 +1,58 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ +package com.iblsoft.iwxxm.webservice.ws.messages; + +import com.fasterxml.jackson.annotation.JsonInclude; + +import static com.google.common.base.Strings.nullToEmpty; + +/** + * Holds information about validation errors in JSON RPC validation response. + */ +@JsonInclude(JsonInclude.Include.NON_EMPTY) +public class ValidationError { + + private final String errorMessage; + private final Integer lineNumber; + private final Integer columnNumber; + + public ValidationError(String errorMessage, Integer lineNumber, Integer columnNumber) { + this.errorMessage = nullToEmpty(errorMessage); + this.lineNumber = lineNumber; + this.columnNumber = columnNumber; + } + + public String getErrorMessage() { + return errorMessage; + } + + public Integer getLineNumber() { + return lineNumber; + } + + public Integer getColumnNumber() { + return columnNumber; + } + + @Override + public String toString() { + if (lineNumber == null && columnNumber == null) { + return getErrorMessage(); + } else { + return String.format("%s at line %d, column %d", errorMessage, lineNumber, columnNumber); + } + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationRequest.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationRequest.java new file mode 100644 index 0000000..e5cb9d3 --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationRequest.java @@ -0,0 +1,54 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws.messages; + +import com.fasterxml.jackson.annotation.JsonIgnoreProperties; + +/** + * Represents validation request of JSON RPC web service. + */ +@JsonIgnoreProperties(ignoreUnknown = true) +public class ValidationRequest { + + private String requestVersion; + private String iwxxmVersion; + private String iwxxmData; + + public String getRequestVersion() { + return requestVersion; + } + + public void setRequestVersion(String requestVersion) { + this.requestVersion = requestVersion; + } + + public String getIwxxmVersion() { + return iwxxmVersion; + } + + public void setIwxxmVersion(String iwxxmVersion) { + this.iwxxmVersion = iwxxmVersion; + } + + public String getIwxxmData() { + return iwxxmData; + } + + public void setIwxxmData(String iwxxmData) { + this.iwxxmData = iwxxmData; + } +} diff --git a/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationResponse.java b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationResponse.java new file mode 100644 index 0000000..826718f --- /dev/null +++ b/src/main/java/com/iblsoft/iwxxm/webservice/ws/messages/ValidationResponse.java @@ -0,0 +1,80 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws.messages; + + +import com.fasterxml.jackson.annotation.JsonInclude; + +import java.util.ArrayList; +import java.util.Collections; +import java.util.List; + +/** + * Represents validation response of JSON RPC web service. + */ +@JsonInclude(JsonInclude.Include.NON_EMPTY) +public class ValidationResponse { + + private List validationErrors; + + private ValidationResponse(Builder builder) { + this.validationErrors = Collections.unmodifiableList(builder.validationErrors); + } + + public String getResponseVersion() { + return "1.0"; + } + + public boolean isValid() { + return validationErrors.isEmpty(); + } + + public List getValidationErrors() { + return this.validationErrors; + } + + public static Builder builder() { + return new Builder(); + } + + @Override + public String toString() { + return "ValidationResponse {" + + "valid=" + isValid() + + "validation errors count=" + validationErrors.size() + + "}"; + } + + /** + * Helper builder class. + */ + public static class Builder { + private List validationErrors = new ArrayList<>(4); + + private Builder() { + } + + public Builder addValidationError(String errorMessage, Integer lineNumber, Integer columnNumber) { + this.validationErrors.add(new ValidationError(errorMessage, lineNumber, columnNumber)); + return this; + } + + public ValidationResponse build() { + return new ValidationResponse(this); + } + } +} diff --git a/src/main/resources/META-INF/MANIFEST.MF b/src/main/resources/META-INF/MANIFEST.MF new file mode 100644 index 0000000..6fbda3d --- /dev/null +++ b/src/main/resources/META-INF/MANIFEST.MF @@ -0,0 +1 @@ +Main-Class: com.iblsoft.iwxxm.webservice.Main diff --git a/src/main/resources/get-help-response.txt b/src/main/resources/get-help-response.txt new file mode 100644 index 0000000..c53a508 --- /dev/null +++ b/src/main/resources/get-help-response.txt @@ -0,0 +1,65 @@ + +IBL IWXXM Validator JSON-RPC web service +======================================== + +Input request +------------- + +requestVersion: version of message request, now must be set to "1.0". +iwxxmVersion: version of validated IWXXM data, if omitted, than version is detected from IWXXM namespace +iwxxmData: validated IWXXM data + +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "method": "validate", + "params": { + "request": { + "requestVersion": "1.0", + "iwxxmVersion": "2.0", + "iwxxmData": "" + } +} + +Output response +--------------- + +responseVersion: version of response message, now always 1.0 +valid: true or false, indicates if validated message is valid or not +validationErrors: list of validation errors if report is not valid. If report is valid, than this property is omitted + +Example of response for valid IWXXM report +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "result": { + "responseVersion": "1.0", + "valid": true + } +} + +Example of response for invalid IWXXM report +{ + "jsonrpc": "2.0", + "id": "iwxxm1", + "result": { + "validationErrors": [ + { + "errorMessage": "cvc-complex-type.4: Attribute 'permissibleUsage' must appear on element 'iwxxm:SIGMET'.", + "lineNumber": 1, + "columnNumber": 1108 + }, + { + "errorMessage": "cvc-complex-type.4: Attribute 'uom' must appear on element 'iwxxm:directionOfMotion'.", + "lineNumber": 1, + "columnNumber": 4399 + }, + { + "errorMessage": "SIGMET.EMC1: directionOfMotion shall be reported in degrees (deg). ((if(exists(iwxxm:directionOfMotion) and (not(exists(iwxxm:directionOfMotion/@xsi:nil)) or iwxxm:directionOfMotion/@xsi:nil != 'true')) then (iwxxm:directionOfMotion/@uom = 'deg') else true()))" + } + ], + "responseVersion": "1.0", + "valid": false + } +} + diff --git a/src/main/resources/iso-schematron-xslt2/iso_schematron_message_xslt2.xsl b/src/main/resources/iso-schematron-xslt2/iso_schematron_message_xslt2.xsl new file mode 100644 index 0000000..54cbe61 --- /dev/null +++ b/src/main/resources/iso-schematron-xslt2/iso_schematron_message_xslt2.xsl @@ -0,0 +1,55 @@ + + + + + + + + + + + + + + + + + + + + + + + ( + / + ) + + + \ No newline at end of file diff --git a/src/main/resources/iso-schematron-xslt2/iso_schematron_skeleton_for_saxon.xsl b/src/main/resources/iso-schematron-xslt2/iso_schematron_skeleton_for_saxon.xsl new file mode 100644 index 0000000..c1c5fd0 --- /dev/null +++ b/src/main/resources/iso-schematron-xslt2/iso_schematron_skeleton_for_saxon.xsl @@ -0,0 +1,2299 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + #ALL + + + +false + +true + + + + + true + false + + + + + + + true + false + + + + + + + + + @*| + + * + node() + *|comment()|processing-instruction() + + + + + + + + + + +false + + +default + + +1 + +false + + + + + + 1 + + + + + + + + + + + + + + + + + 2 + + + + + + 1.0 + + + + + + + + + This XSLT was automatically generated from a Schematron schema. + + + + + 1.0 + + + + + + + + + + + + 2.0 + + + + + + + + + + 3a + + 3b + + + + + Implementers: please note that overriding process-prolog or process-root is + the preferred method for meta-stylesheets to use where possible. + + + + + + + + + + + + PHASES + + PROLOG + + XSD TYPES FOR XSLT2 + + KEYS AND FUNCTIONS + + DEFAULT RULES + + SCHEMA SETUP + + SCHEMATRON PATTERNS + + + + + + + + + + + + + + + + + + + + + + + + 4a + + 4b + + + + + + + MODE: SCHEMATRON-SELECT-FULL-PATH + This mode can be used to generate an ugly though full XPath for locators + + + + + + + + + + + + + + + + + + + + + + + + + MODE: SCHEMATRON-FULL-PATH + This mode can be used to generate an ugly though full XPath for locators + + + + + + / + + + + *: + + [namespace-uri()=' + + '] + + + + [ + + ] + + + + + + / + + + + + + [] + + + + *[local-name()=' + + '] + + + [] + + + + + + + + + + + + + + + / + + @ + + @*[local-name()=' + + ' and namespace-uri()=' + + '] + + + + + + + / + + @ + + @*[local-name()=' + + ' and namespace-uri()=' + + '] + + + + + + + + + + MODE: SCHEMATRON-FULL-PATH-2 + + This mode can be used to generate prefixed XPath for humans + + + + + + / + + + [ + + ] + + + + + /@ + + + + + MODE: SCHEMATRON-FULL-PATH-3 + + + This mode can be used to generate prefixed XPath for humans + (Top-level element has index) + + + + + + / + + + [ + + ] + + + + + /@ + + + + + MODE: GENERATE-ID-FROM-PATH + + + + + + + + + + + + + + + + + + + + + + . + + + + + + + + MODE: GENERATE-ID-2 + + + U + + + U + + + + + U. + + n + + + + + U. + + _ + + _ + + + + + Strip characters + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 5 + + + + 6a + + 6b + + + + + + + + 7 + + + ASSERT + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 8 + + + + REPORT + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 9 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 10 + + + + 11a + + 11b + + + + + + + + + + + + + + + + + + + + + + 12 + + + 13 + + + + + + + + + + + + + + + + 14 + + + + + + + + + + + + 15 + + + + + + 16 + + + + + + + + 17 + + + + + + + + + 18 + + + + + + + + + + + + + + 19 + + + + + + + + 20a + + 20b + + + + 21 + + + + + + + + + + + + 20a + + 20b + + + + 21 + + + + + + + + + + + + + + + 19 + + + + + + + 21 + + + + + + + + + + + 21 + + + + + + + + + + + + + + + + 22 + + + + + + + + + 23 + + + + + + 24 + + + 25 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 26 + + + 27 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + //( + + ( + + ) + | + + ) + [not(self::text())] + + + + + + + + + //( + + ( + + ) + | + + ) + [not(self::text())] + + + + + + + + + + + + + + + + + + + + + + + 28 + + + + + + + + PATTERN + + + + + + + + + + + + + + + + + + + + 29 + + + + + + + + + + No property found with that ID + + + + + + + + + + + + + + + + + + + + + + + + + + 30 + + + + + RULE + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 31 + + + 32 + + + + + + 33 + + + + + + + + + + + + + + + + + + + + + + + + + + + 34 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 35a + + 35b + + + + + + + + + + + + + + + + + + + + + + + + + 36a + + 36b + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 36a + + 36b + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 37a + + 37b + + + + + + + + + + + + + + + + + + + 38a + + 38b + + + + + + + + + + + + 39a + + 39b + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TERMINATING + + + TERMINATING + + + + + + + + + + + + + + + + + + + + + + + + + + + + + TERMINATING + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + title + + + + + + + schema-title + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Schema error: Schematron elements in old and new namespaces found + Schema error: in the queryBinding attribute, use 'xslt' + Fail: This implementation of ISO Schematron does not work with schemas using the query language + + Phase Error: no phase has been defined with name + + Markup Error: no pattern attribute in <active> + Reference Error: the pattern " + " has been activated but is not declared + Markup Error: no test attribute in <assert + Markup Error: no test attribute in <report> + Markup Error: no id attribute in <diagnostic> + Markup Error: no rule attribute in <extends> + Reference Error: the abstract rule " + " has been referenced but is not declared + Markup Error: no name attribute in <key> + Markup Error: no path or use attribute in <key> + Markup Error: no path or use attribute in <key> + Schema error: The key element is not in the ISO Schematron namespace. Use the XSLT namespace. + Markup Error: no name attribute in <function> + Schema error: The function element is not in the ISO Schematron namespace. Use the XSLT namespace. + Schema error: Empty href= attribute for include directive. + Error: Impossible URL in Schematron include + Unable to open referenced included file: + + Schema error: Use include to include fragments, not a whole schema + Schema error: XSD schemas may only be imported if you are using the 'xslt2' query language binding + Schema error: The import-schema element is not available in the ISO Schematron namespace. Use the XSLT namespace. + Warning: Variables should not be used with the "xpath" query language binding. + Warning: Variables should not be used with the "xpath2" query language binding. + Markup Error: no uri attribute in <ns> + Markup Error: no prefix attribute in <ns> + Schema implementation error: This schema has abstract patterns, yet they are supposed to be preprocessed out already + Markup Error: no id attribute in <phase> + Markup Error: no context attribute in <rule> + Markup Error: no id attribute on abstract <rule> + Markup Error: (2) context attribute on abstract <rule> + Markup Error: context attribute on abstract <rule> + Markup Error: no select attribute in <value-of> + Warning: + must not contain any child elements + Reference error: A diagnostic " + " has been referenced but is not declared + Using the XSLT namespace with a prefix other than "xsl" in Schematron rules is not supported in this processor: + + Error: unrecognized element in ISO Schematron namespace: check spelling and capitalization + + Warning: unrecognized element + + + + + + diff --git a/src/main/resources/iso-schematron-xslt2/readme.txt b/src/main/resources/iso-schematron-xslt2/readme.txt new file mode 100644 index 0000000..ad0aac3 --- /dev/null +++ b/src/main/resources/iso-schematron-xslt2/readme.txt @@ -0,0 +1,100 @@ +

ISO SCHEMATRON 2010

+ +XSLT implementation by Rick Jelliffe with assistance from members of Schematron-love-in maillist. + +2010-04-14 + +Two distributions are available. One is for XSLT1 engines. +The other is for XSLT2 engines, such as SAXON 9. + + +This version of Schematron splits the process into a pipeline of several different XSLT stages. + +1) First, preprocess your Schematron schema with iso_dsdl_include.xsl. +This is a macro processor to assemble the schema from various parts. +If your schema is not in separate parts, you can skip this stage. + +2) Second, preprocess the output from stage 1 with iso_abstract_expand.xsl. +This is a macro processor to convert abstract patterns to real patterns. +If your schema does not use abstract patterns, you can skip this +stage. + +3) Third, compile the Schematron schema into an XSLT script. +This will typically use iso_svrl_for_xslt1.xsl or iso_svrl_for_xslt2.xsl +(which in turn invoke iso_schematron_skeleton_for_xslt1.xsl or iso_schematron_skeleton_for_saxon.xsl) +However, other "meta-styleseets" are also in common use; the principle of operation is the same. +If your schema uses Schematron phases, supply these as command line/invocation parameters +to this process. + +4) Fourth, run the script generated by stage 3 against the document being validated. +If you are using the SVRL script, then the output of validation will be an XML document. +If your schema uses Schematron parameters, supply these as command line/invocation parameters +to this process. + + +The XSLT2 distribution also features several next generation features, +such as validating multiple documents. See the source code for details. + +Schematron assertions can be written in any language, of course; the file +sch-messages-en.xhtml contains the diagnostics messages from the XSLT2 skeleton +in English, and this can be used as template to localize the skeleton's +error messages. Note that typically programming errors in Schematron are XPath +errors, which requires localized messages from the XSLT engine. + +ANT +--- +To give an example of how to process a document, here is a sample ANT task. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +EXTRACTION SCHEMATRON FROM XSD OR RELAX NG + +The following files allow extracting of embedded schematron patterns +in XML Schemas or RELAX NG schemas. For details, see the at + article http://www.topologi.com/resources/schtrn_xsd_paper.html + +The following files are provided: + ExtractSchFromRNG.xsl Generate a Schematron schema from patterns + embedded in a RELAX NG schema. The schema uses XSLT1. + ExtractSchFromXSD.xsl Generate a Schematron schema from patterns + embedded in a W3C XML Schemas schema. The schema uses XSLT1. + + ExtractSchFromRNG-2.xsl Generate a Schematron schema from patterns + embedded in a RELAX NG schema. The schema uses XSLT2. + ExtractSchFromXSD-2.xsl Generate a Schematron schema from patterns + embedded in a W3C XML Schemas schema. The schema uses XSLT2. \ No newline at end of file diff --git a/src/main/resources/jetty-logging.properties b/src/main/resources/jetty-logging.properties new file mode 100644 index 0000000..8334119 --- /dev/null +++ b/src/main/resources/jetty-logging.properties @@ -0,0 +1,17 @@ +# +# Copyright (C) 2016, IBL Software Engineering spol. s r. o. +# +# Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except +# in compliance with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software distributed under the License +# is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express +# or implied. See the License for the specific language governing permissions and limitations under +# the License. +# +############################################################################################################## + +org.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.Slf4Log +org.eclipse.jetty.LEVEL=INFO \ No newline at end of file diff --git a/src/main/resources/logback.xml b/src/main/resources/logback.xml new file mode 100644 index 0000000..a5af0f3 --- /dev/null +++ b/src/main/resources/logback.xml @@ -0,0 +1,32 @@ + + + + + + utf-8 + %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n + + + + + true + + + + + + + + diff --git a/src/test/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebServiceTest.java b/src/test/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebServiceTest.java new file mode 100644 index 0000000..5361b58 --- /dev/null +++ b/src/test/java/com/iblsoft/iwxxm/webservice/ws/IwxxmWebServiceTest.java @@ -0,0 +1,81 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws; + +import com.iblsoft.iwxxm.webservice.ws.internal.IwxxmWebServiceImpl; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationRequest; +import com.iblsoft.iwxxm.webservice.ws.messages.ValidationResponse; +import org.junit.After; +import org.junit.Before; +import org.junit.Test; + +import java.io.File; +import java.util.List; + +import static org.hamcrest.CoreMatchers.is; +import static org.hamcrest.MatcherAssert.assertThat; + +public class IwxxmWebServiceTest +{ + private IwxxmWebService ws; + + @Before + public void setUp() throws Exception + { + + this.ws = new IwxxmWebServiceImpl(new File("config/schemas/catalog.xml"), new File("config/schemas/rule"), "2.0"); + } + + @After + public void tearDown() throws Exception + { + this.ws = null; + } + + @Test + public void validate_with_valid_messages_should_pass() throws Exception + { + String[] iwxxmMessageFileNames = new String[]{ + "iwxxm20-metar-valid.xml", + "iwxxm20-taf-valid.xml", + "iwxxm20-sigmet-valid.xml"}; + + List testMessages = TestUtils.loadTestResources(iwxxmMessageFileNames); + for (String iwxxmReport: testMessages) { + ValidationRequest request = new ValidationRequest(); + request.setRequestVersion("1.0"); + request.setIwxxmData(iwxxmReport); + ValidationResponse response = this.ws.validate(request); + assertThat(response.isValid(), is(true)); + } + } + + @Test + public void validate_with_invalid_messages_should_report_errors() throws Exception + { + String[] iwxxmMessageFileNames = new String[]{"iwxxm20-sigmet-invalid.xml"}; + + List testMessages = TestUtils.loadTestResources(iwxxmMessageFileNames); + for (String iwxxmReport: testMessages) { + ValidationRequest request = new ValidationRequest(); + request.setRequestVersion("1.0"); + request.setIwxxmData(iwxxmReport); + ValidationResponse response = this.ws.validate(request); + assertThat(response.isValid(), is(false)); + } + } +} \ No newline at end of file diff --git a/src/test/java/com/iblsoft/iwxxm/webservice/ws/TestUtils.java b/src/test/java/com/iblsoft/iwxxm/webservice/ws/TestUtils.java new file mode 100644 index 0000000..0691e88 --- /dev/null +++ b/src/test/java/com/iblsoft/iwxxm/webservice/ws/TestUtils.java @@ -0,0 +1,43 @@ +/*********************************************************************************************** + * + * Copyright (C) 2016, IBL Software Engineering spol. s r. o. + * + * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except + * in compliance with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software distributed under the License + * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express + * or implied. See the License for the specific language governing permissions and limitations under + * the License. + * + ***********************************************************************************************/ + +package com.iblsoft.iwxxm.webservice.ws; + +import org.apache.commons.io.IOUtils; + +import java.io.IOException; +import java.io.InputStream; +import java.util.ArrayList; +import java.util.Collections; +import java.util.List; + +class TestUtils { + public static List loadTestResources(String[] resourcePaths) throws Exception { + List messages = new ArrayList<>(resourcePaths.length); + for (String resourceName: resourcePaths) { + messages.add(loadTestResource(resourceName)); + } + return Collections.unmodifiableList(messages); + } + + public static String loadTestResource(String resourcePath) throws IOException + { + try (InputStream stream = TestUtils.class.getResourceAsStream("/iwxxm-messages/" + resourcePath)) + { + return IOUtils.toString(stream); + } + } +} diff --git a/src/test/resources/iwxxm-messages/iwxxm20-metar-valid.xml b/src/test/resources/iwxxm-messages/iwxxm20-metar-valid.xml new file mode 100644 index 0000000..537e789 --- /dev/null +++ b/src/test/resources/iwxxm-messages/iwxxm20-metar-valid.xml @@ -0,0 +1,76 @@ + + + + + + + + 2016-10-21T16:30:00Z + + + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 3 TECHNICAL SPECIFICATIONS RELATED TO METEOROLOGICAL OBSERVATIONS AND REPORTS + + + + + + + + + + + + BASELINE + LZIB + BRATISLAVA LETISKO + LZIB + + + + + + + 48.17 17.21 133 + + + + + + + 26 + 15 + 1022 + + + 80 + 5 + 60 + 120 + + + + + + + + + + + + 2016-10-21T16:30:00Z + 2016-10-21T18:30:00Z + + + + + + + + + + + + diff --git a/src/test/resources/iwxxm-messages/iwxxm20-sigmet-invalid.xml b/src/test/resources/iwxxm-messages/iwxxm20-sigmet-invalid.xml new file mode 100644 index 0000000..5bcdbb0 --- /dev/null +++ b/src/test/resources/iwxxm-messages/iwxxm20-sigmet-invalid.xml @@ -0,0 +1,99 @@ + + + + + + + + BASELINE + FIC + FIC + LZBB + + + + + + + + + + BASELINE + MWO + MWO + LZBB + + + + + A01 + + + 2016-09-22T10:28:00 + 2016-09-22T14:28:00 + + + + + + + + + + 2016-09-22T10:28:00 + + + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation [C.3.1.]7 SIGMET AND AIRMET INFORMATION, AERODROME WARNINGS AND WIND SHEAR WARNINGS AND ALERTS + + + + + + + + + + + + BASELINE + FIR + LZBB + BRATISLAVA + + + + + + + + + + + + + 630 + STD + + + + + + + 49.23 18.62 48.28 18.13 48.65 19.15 + + + + + + + + + 0 + + + + + \ No newline at end of file diff --git a/src/test/resources/iwxxm-messages/iwxxm20-sigmet-valid.xml b/src/test/resources/iwxxm-messages/iwxxm20-sigmet-valid.xml new file mode 100644 index 0000000..60ae070 --- /dev/null +++ b/src/test/resources/iwxxm-messages/iwxxm20-sigmet-valid.xml @@ -0,0 +1,101 @@ + + + + + + + + BASELINE + FIC + FIC + LZBB + + + + + + + + + + BASELINE + MWO + MWO + LZBB + + + + + C01 + + + 2016-10-10T11:30:00Z + 2016-10-10T15:30:00Z + + + + + + + + + + 2016-10-10T11:30:00Z + + + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation [C.3.1.]7 SIGMET AND AIRMET INFORMATION, AERODROME WARNINGS AND WIND SHEAR WARNINGS AND ALERTS + + + + + + + + + + + + BASELINE + FIR + LZBB + BRATISLAVA + + + + + + + + + + + + + 630 + STD + 630 + STD + + + + + + + 48.33 19.73 48.28 18.13 49.23 18.62 + + + + + + + + + 0 + + + + + \ No newline at end of file diff --git a/src/test/resources/iwxxm-messages/iwxxm20-taf-valid.xml b/src/test/resources/iwxxm-messages/iwxxm20-taf-valid.xml new file mode 100644 index 0000000..46a469b --- /dev/null +++ b/src/test/resources/iwxxm-messages/iwxxm20-taf-valid.xml @@ -0,0 +1,176 @@ + + + + + 2016-10-10T10:58:00Z + + + + + 2016-10-10T12:00:00Z + 2016-10-11T12:00:00Z + + + + + + + + 2016-10-10T12:00:00Z + 2016-10-11T12:00:00Z + + + + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 5 TECHNICAL SPECIFICATIONS RELATED TO FORECASTS + + + + + + + + + + + + BASELINE + LZIB + BRATISLAVA LETISKO + LZIB + + + + + + + 48.17 17.21 133 + + + + + + + 9999 + + + 240 + 15 + + + + + + + + + 1800 + + + + + + 2800 + + + + + + + 10 + + + 2016-10-11T12:00:00Z + + + 5 + + + 2016-10-11T00:00:00Z + + + + + + + + + + + + + + 2016-10-10T14:00:00Z + 2016-10-10T17:00:00Z + + + + + + + + + + + + 180 + 12 + + + + + + + + + + + + 2016-10-11T04:00:00Z + 2016-10-11T07:00:00Z + + + + + + + + + + 7000 + + + 140 + 22 + + + + + + + + + 1000 + + + + + + 1500 + + + + + + 2500 + + + + + + + + + diff --git a/src/test/resources/logback.xml b/src/test/resources/logback.xml new file mode 100644 index 0000000..a5af0f3 --- /dev/null +++ b/src/test/resources/logback.xml @@ -0,0 +1,32 @@ + + + + + + utf-8 + %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n + + + + + true + + + + + + + +