...
WIS2 topic hierarchy and filename
Core hierarchy
Level | Name | Description | Value(s) | Example | |
|---|---|---|---|---|---|
1 | scope | Scope | Scope of topic hierarchy (fixed to |
WIS2
|
WIS2
| |||||
2 | resource-type | Resource type | Type of resource being identified |
|
|
3 | data-policy | Data Policy |
WMO Unified Data Policy category, provides distinction in access control/permissions |
|
other
|
4 | data-type | Data Type |
Top level data type |
|
|
Examples:
wis2.data.core.observations
wis2.discovery-metadata.recommended.nwp
wis2.data.other.observations
...
wis2.monitoring-report.gts
Data Type Hierarchies
Level 3 Data Type hierarchies vary significantly across data types (e.g. different for observations and NWP), and will be built gradually following the requirements of WMO domains.
Each WMO domain will also define filename conventions (basename, extension)
Observation Data Type
Level | Name | Description | Value(s) | Example | |
|---|---|---|---|---|---|
1 |
category
Category
2
observations…
observations
country | Country | ISO 3166-2 code of country |
|
2 | station-type | Station type | Station/platform type |
|
3 | message-type | Message type | The type of message sent by the observation station |
?
|
airMobile.aircraft |
Examples:
wis2.data.core.observations.ca.landFixed.??surface
wis2.data.core.observations.gr.landMobile.??
wis2.data.core.observations.it.seaFixed.??
wis2.monitoring-reports.wis2.observations.de.??
Alternative Proposal
This alternative proposal has the country code and center name higher up in the hierarchie. Could be extended with data policy
...
Filename conventions
Observations
...
This is the current output of the TT-Protocols team
https://github.com/wmo-im/GTStoWIS2
| View file | ||
|---|---|---|
|
...
Shall we make a topic structure directly with GTS headers (T/T/A/A/ii/CCCC )?
Related discussions
wis2nodewis2box: https://github.com/wmo-im/wis2nodewis2box/issues/31
GTStoWIS2: https://github.com/wmo-im/GTStoWIS2/issues/9