forked from peterataylor/om-json
-
Notifications
You must be signed in to change notification settings - Fork 0
/
MonitoringFeature.json
71 lines (71 loc) · 3.59 KB
/
MonitoringFeature.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
{
"$schema": "http://json-schema.org/schema#",
"id": "http://raw.githubusercontent.com/peterataylor/om-json/master/MonitoringFeature.json",
"title": "MonitoringFeature",
"description": "A TimeseriesML MonitoringFeature",
"type": "object",
"additionalProperties": false,
"required": [
"id"
],
"definitions": {
"timeZoneType": {
"type": "object",
"properties": {
"zoneOffset": {
"type":"string",
"description":"Time zone offset e.g. +10:00 GM"
},
"zoneAbbreviation": {
"type":"string",
"description":"Abbreviation for a timezone e.g. AEST."
}
}
}
},
"properties": {
"@context" : { "$ref": "http://raw.githubusercontent.com/peterataylor/om-json/master/Common.json#/definitions/@context" },
"id": {
"title": "id",
"description": "A unique identifier for the observation",
"type": "string"
},
"relatedParty": {
"title": "relatedParty",
"description": "The details of a party related to this MonitoringFeature. Multiple related parties may be described using the role code list (from ISO 19115). The most common relationships are likely to be: owner, originator, pointOfContact, principalInvestigator and distributor.",
"type": "array"
},
"representativePoint": {
"title": "representativePoint",
"description": "A point location that is representative of the monitoring feature's location. Typically this is used when the shape of the monitoring feature is an area or other non-point geometry. It may also be used to provide an approximate point location in sensitive observation scenarios.",
"$ref": "http://raw.githubusercontent.com/peterataylor/om-json/master/Geometry.json#/definitions/geometryObject"
},
"monitoringType": {
"title": "monitoringType",
"description": "A thematic characterisation of the type of monitoring feature. E.g. meteorological, surface water, groundwater, water quality etc.",
"$ref": "http://raw.githubusercontent.com/peterataylor/om-json/master/Common.json#/definitions/link"
},
"descriptionReference": {
"title": "descriptionReference",
"description": "Provide extra descriptive information about a monitoring feature. This could be a link to an HTML page describing the location, photos of a monitoring point, history records etc.",
"$ref": "http://raw.githubusercontent.com/peterataylor/om-json/master/Common.json#/definitions/link"
},
"verticalDatum": {
"title": "verticalDatum",
"description": "Specifies the elevation that is used as the zero point, or datum, for height-related measurements. The datum is defined using a vertical datum, which may be defined using the ISO19111 type CD_VerticalDatum, or an agreed upon datum may be reference by its identifier. E.g. the Australian Height Datum (AHD), Tasmania = “EPSG::5112”. The CD_VerticalDatum type allows specification of the local vertical datum as a height above another reference datum. E.g. local vertical datum is 23m above the AHD.",
"$ref": "http://raw.githubusercontent.com/peterataylor/om-json/master/Common.json#/definitions/link"
},
"timeZone": {
"title": "timeZone",
"description": "The timezone that the MonitoringFeature is located in.",
"type": "object",
"$ref": "#/definitions/timeZoneType"
},
"daylightSavingsTimeZone": {
"title": "daylightSavingsTimeZone",
"description": "The timezone that the MonitoringFeature is located in when daylight savings applies.",
"type": "object",
"$ref": "#/definitions/timeZoneType"
}
}
}