Questa pagina non è ancora tradotta e viene visualizzata in inglese.
JSON Variant
Besides the binary representation, the RAE format has a JSON representation with the MIME type:
application/vnd.rhopoint.rae+json
A JSON RAE document is a plain UTF-8 JSON text — it has no magic string, no compression and no hash. The root object is the RaeJsonFile record:
| Key | Type | Description |
|---|---|---|
format |
string | Identifies the data format. Currently always "MeasurementComponentMetaTuple[]". |
version |
integer | Version of the file format. The current version is 1. |
dataContainer |
string | Encoding of the payload. Currently always "json". |
data |
array | The measurements, one object per MeasurementComponentMetaTuple. |
Differences to the binary encoding
The payload objects have the same structure as in the binary encoding, but:
- Abbreviated keys are used (e.g.
mIdinstead ofmeasurementIdentifier,srcIdinstead ofsourceIdentifier). The tables in MeasurementComponentMetaTuple, MeasurementComponent and Measurement Data Types list both key sets. - Unset properties are omitted instead of being written as
null. - Binary content (e.g. embedded files) is Base64-encoded.
- In data records,
classholds the logical type ("SingleMeasurement"/"FileReference") andvalueholds the JSON-serialized value string — see the note in Measurement Data Types.
Example
{
"format": "MeasurementComponentMetaTuple[]",
"version": 1,
"dataContainer": "json",
"data": [
{
"Meta": {
"srcId": "0d9f4c1e-6a2b-4f43-9c1a-2f5e8d7b3a10",
"mId": "0d9f4c1e-6a2b-4f43-9c1a-2f5e8d7b3a10",
"mType": "composite",
"time": "2026-07-07T12:34:56.7890123+00:00",
"name": "Sample A",
"ver": 2
},
"Component": {
"type": "composite",
"name": "Measurement",
"comp": [
{
"type": "single",
"name": "Gloss 60°",
"data": {
"class": "SingleMeasurement",
"ver": 1,
"value": "87.3",
"valueType": "System.Double"
},
"meta": { "unit": "GU" },
"ver": 2
}
],
"ver": 2
}
}
]
}