fileformats:json
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
fileformats:json [2018/01/04 11:38] – [Json data format] oliver | fileformats:json [2018/01/09 10:45] (aktuell) – [Json data format] oliver | ||
---|---|---|---|
Zeile 4: | Zeile 4: | ||
**MimeType: | **MimeType: | ||
- | ==== Output of processing | + | **Default File Suffix:** .json |
+ | |||
+ | **Comments** | ||
+ | |||
+ | Reading of json-files is not yet implemented. | ||
+ | |||
+ | ==== Output of processed | ||
In the "job configuration" | In the "job configuration" | ||
Zeile 43: | Zeile 49: | ||
* At the time, not all informations saved in a trial are exported into Json-files. Missing parts can be added easy if needed. | * At the time, not all informations saved in a trial are exported into Json-files. Missing parts can be added easy if needed. | ||
* NaN double values are written - against the Json standard - as " | * NaN double values are written - against the Json standard - as " | ||
+ | |||
+ | ==== Output of exported motion data ==== | ||
+ | |||
+ | The Output of motion data exported into the json-format is different to the data saved after processed data: | ||
+ | |||
+ | Each line is a valid JSON entry without separator at the end. This is similar to other readers and follows [[http:// | ||
+ | |||
+ | === Example === | ||
+ | |||
+ | < | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | {" | ||
+ | </ | ||
+ | |||
+ | If in the Export UI the " |
fileformats/json.1515062300.txt.gz · Zuletzt geändert: 2018/01/04 11:38 von oliver