User Tools

Site Tools


en:infra-convert:dev:export:jsonv1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:infra-convert:dev:export:jsonv1 [2019/11/25 14:29]
me
en:infra-convert:dev:export:jsonv1 [2020/06/19 14:44] (current)
me
Line 11: Line 11:
 ---- ----
  
-The quality ​test plan export format **JSONV1** ​ensures maximum compatibility with connected software packagesIt is JSON file (click [[http://​www.json.org/​json-de.html|here]] ​for a descriptionwhich contains all the information relevant to an inspection ​plan. JSON files can be read by all common programming languages. The suffix //V1// identifies the file structure as version 1. This file structure is described in this chapter.+The test plan export format **JSONV1** ​contains significantly more information than the CSV and DFD formatsThe data format ​is "JSON" ​(a description can be found [[http://​www.json.org/​json-de.html||here]]])the suffix "​V1"​ indicates version 1 of the contained test plan data structure. JSON can be read with all common programming languages.
  
-If implemented,​ your software ​can also import data from a later version. A later version can include additional information,​ for example. +The JSONV1 export ​can be initiated either ​from the user interface ​(see "User manual > Functions > Export > [[en:​infra-convert:​user:​functions:​cplanexport|Export Test Plan]]"​or via the start parameter file (see "Configuration and Import > Start Parameter File > [[en:​infra-convert:​dev:​parameter#​Export quality test plans and stamped drawings]]).
- +
-> **Info** We recommend that you use the JSONV1 format rather than the DFD format to connect to your software package. It includes more transferable information and supports all characteristics of #​@IC_HTML@#​. It also provides the advantage of later versions of the JSONV1 format ​(after implementationwill also be compatible with your software.\\ \\ You can trigger the export in the start parameter filesee Configuration and Import > Startup ​Parameter File > [[en:​infra-convert:​dev:​parameter#​Export quality test plans and stamped drawings]].+
  
 <WRAP group> <WRAP group>
Line 198: Line 196:
  
 The sequence of the characteristics corresponds to the list item in the test plan. The drawing-sheet-related inspection plan sections are hung together according to the sheet sequence. The sequence of the characteristics corresponds to the list item in the test plan. The drawing-sheet-related inspection plan sections are hung together according to the sheet sequence.
 +
 +At the end of this section you will find a diagram that illustrates how the IDs are assigned.
  
 > **See also** > **See also**
Line 266: Line 266:
 ^ Special​Category​Id | String | GUID of the →[[en:​infra-convert:​user:​terms#​Kategorie (Merkmal-)|Characteristic category]] | ^ Special​Category​Id | String | GUID of the →[[en:​infra-convert:​user:​terms#​Kategorie (Merkmal-)|Characteristic category]] |
 ^ CharacteristicTagIds | String | GUIDs of the tags assigned to the characteristic | ^ CharacteristicTagIds | String | GUIDs of the tags assigned to the characteristic |
 +^ Value | String | Text as read from the drawing entry. |
 ^ Label | String | Title of the characteristic (long text) | ^ Label | String | Title of the characteristic (long text) |
 ^ Nominal​Value | String | Nominal value (number accuracy is maintained)\\ **null** No value assigned because parameter does not apply | ^ Nominal​Value | String | Nominal value (number accuracy is maintained)\\ **null** No value assigned because parameter does not apply |
Line 274: Line 275:
 ^ Tolerance​Table | String | Name of the tolerance table\\ **null** No value assigned because parameter does not apply | ^ Tolerance​Table | String | Name of the tolerance table\\ **null** No value assigned because parameter does not apply |
 ^ Tolerance​Table​Column | String | Column in the tolerance table\\ **null** No value assigned because parameter does not apply | ^ Tolerance​Table​Column | String | Column in the tolerance table\\ **null** No value assigned because parameter does not apply |
-^ MinMax | String | **min** Type of limit: Minimum size (the lower limit is given, the upper limit is naturally)\\ **max** Type of limits: Maximum size (the upper limit is given, the lower limit is naturally)\\ **None** Both limit sizes are specified or a limit size specification is not applicable. |+^ MinMax | String | **min** Type of limit: Minimum size (the lower limit is given, the upper limit is naturally ​determined)\\ **max** Type of limits: Maximum size (the upper limit is given, the lower limit is naturally ​determined)\\ **None** Both limit sizes are specified or a limit size specification is not applicable. |
 ^ Fit | String | Tolerance class\\ **null** No value assigned because parameter does not apply | ^ Fit | String | Tolerance class\\ **null** No value assigned because parameter does not apply |
 ^ Conditions | String| Modifiers\\ **null** No value assigned because parameter does not apply | ^ Conditions | String| Modifiers\\ **null** No value assigned because parameter does not apply |
Line 298: Line 299:
  
 \\  \\ 
 +
 +> **Allocation of characteristic and stamp IDs**
 +> The following diagram illustrates the assignment of the Ids (Guids) across the inspection plan versions. In case 1, a characteristic is transferred from test plan version A to B and from B to C in the drawing comparison. For example, "Guid C1" is found in version B as a CompareSourceId and as a DirectCompareSourceId,​ in C consequently only as CompareSourceId. In case 2, inspection plan version B is omitted.
 +
 +> {{ :​de:​infra-convert:​user:​terms:​id-zuweisung_beim_zeichnungsvergleich.png?​nolink&​850 |}}
 +
 +\\
  
 ====== Classes ====== ====== Classes ======
Line 425: Line 433:
  
 **Go to next page**\\ ​ **Go to next page**\\ ​
-Export > [[en:​infra-convert:​dev:​export:​dfd|Quality test plan format ​DFD]]+Export > [[en:​infra-convert:​dev:​export:​jsonv2|Quality test plan format ​JSONV2]]
  
 </​WRAP>​ </​WRAP>​ </​WRAP>​ </​WRAP>​
  
 </​WRAP>​ </​WRAP>​
en/infra-convert/dev/export/jsonv1.1574688593.txt.gz · Last modified: 2019/11/25 14:29 by me