workgroup:airspace:documentation:conceptual
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
workgroup:airspace:documentation:conceptual [2015/12/21 08:45] Rob Garfoot Added security section |
workgroup:airspace:documentation:conceptual [2016/09/19 06:37] (current) elle gonzalez [Security] |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Measurements ===== | ===== Measurements ===== | ||
| - | All relative measurements MUST have a known origin / datum. This must either be specified or a standard documented origin / datum. All measurements MUST be specified at the appropriate scale and precision. E.g. using double precision millimeters (mm) for altitude would be better served by using single precision meters (m). | + | All relative measurements MUST have a known origin / [[datum]]. This must either be specified or a standard documented origin / [[datum]]. All measurements MUST be specified at the appropriate scale and precision. E.g. using double precision millimeters (mm) for altitude would be better served by using single precision meters (m). |
| ==== Altitude ==== | ==== Altitude ==== | ||
| - | Altitude measurements MAY specify a datum they are relative to. If ommitted, the measurements MUST be relatice to the WGS84 datum. | + | Altitude measurements MAY specify a [[datum]] they are relative to. If omitted, the measurements MUST be relative to the WGS84 [[datum]]. |
| ==== Elevation ==== | ==== Elevation ==== | ||
| - | Elevation MUST be assumed relative to ground. In this instance the ground altitude MUST be the datum for the elevation and specified as per an altitude measurement. | + | Elevation MUST be assumed relative to ground. In this instance the ground altitude MUST be the [[datum]] for the elevation and specified as per an altitude measurement. |
| ==== Latitude / Longitude ==== | ==== Latitude / Longitude ==== | ||
| Line 40: | Line 40: | ||
| * ADS-B transceiver | * ADS-B transceiver | ||
| - | Each sensor type MUST be defined and have a known minimum set of capabilities. Where accuracy may vary from reading to reading, accuracy MUST be sent along with any sensor reading. This MUST supercede any accuracy sent as part of a sensor definition. | + | Each sensor type MUST be defined and have a known minimum set of capabilities. Where accuracy may vary from reading to reading, accuracy MUST be sent along with any sensor reading. This MUST supersede any accuracy sent as part of a sensor definition. |
| Additionally the capabilities MAY include other custom elements. | Additionally the capabilities MAY include other custom elements. | ||
| ===== Security ===== | ===== Security ===== | ||
| + | All communications [[http://www.faqtory.co/sky/|over phone]] MUST take place over a secure transport channel. E.g. TLS. | ||
| + | |||
| ==== Identity ==== | ==== Identity ==== | ||
| + | Certificate based? Provision for identity services with trusted CAs? | ||
| + | |||
| TBD | TBD | ||
workgroup/airspace/documentation/conceptual.1450687535.txt.gz ยท Last modified: 2015/12/21 08:45 by Rob Garfoot
Page Tools
