Fit Model Chart and Tech Pack Specifications

Fit model charts

A fit model chart defines body measurements of reference model sizes. Every garment size has to correspond to a reference model size. The garment sizes of a single garment correspond to sizes of a single fit model chart.

The link between a fit model chart and a tech pack is established by the data fields gender, sizeType and brand. For valid association these field values have to coincide in both inputs.

If only a single fit model chart is provided it is admissible to omit the optional fields sizeType and brand.

The fit model chart input file can be either in table (csv, xls) or JSON format.

Table format

You can find an example of a fit model chart here

column name	data type	optional	value set
size	string	no
brand	string	yes
gender	string	no	male female
sizeType	string	yes
measurements_name	string	no	body measurement ids
measurements_value	float	no
measurements_offsetToPreviousSize	float	no
measurements_offsetToNextSize	float	no
measurements_unit	string	no	cm inch

JSON format (example)

JSON

{
  "fitModels" : [
    {
      "size" : "XS",
      "gender" : "female",
      "sizeType" : null,
      "brand" : null,

      "measurements" : [
        {
          "name" : "chest_circumference",
          "value" : xxx,
          "offsetToPreviousSize" : xxx,
          "offsetToNextSize" : xxx,
          "unit" : "cm"
        },
        {
          "name" : "shoulder_width",
          "value" : xxx,
          "offsetToPreviousSize" : xxx,
          "offsetToNextSize" : xxx,
          "unit" : "inch"
        }
      ]
    }
  ]
}

Offset fields

The fields offsetToPreviousSize and offsetToNextSize describe the absolute offset to the value of the same measurement in the directly next (larger) and previous (smaller) size. If there is no larger or smaller size then for this entry offsetToPreviousSize and offsetToNextSize shall be the same.

Tech pack data

The garment-specific tech pack data file provides optional information about available garment sizes and (optionally) garment measurements per garment size.

The field uid is mandatory if size information of more than one garment is provided as input.

The tech pack input file can be either in table (csv, xls) or JSON format.

Table format

You can find an example of a tech pack here

column name	data type	optional	value set
garmentGroup	string	no	garment group ids
uid	string	yes
name	string	yes
brand	string	yes
gender	string	no	male female
sizeType	string	yes
waistbandRatio	float	yes	`[0.0, 1.0]`
stretchFactor	float	yes
availableSizes	string	yes	size ids separated by the `\|` character
measurements_size	string	no
measurements_name	string	no	garment measurement ids
measurements_value	float	no
measurements_unit	string	no	cm inch

JSON format (example)

JSON

{
  "garmentData" : [
    {
      "garmentGroup" : "shorts",
      "gender" : "female",
      "uid" : null,
      "name" : null,
      "sizeType" : null,
      "brand" : null,
      "waistbandRatio" : 0.5,
      "stretchFactor" : null,
      "availableSizes" : [
        "36", "38", "40"
      ],

      "measurements" : [
        {
          "size" : "38",
          "name" : "waistband_circumference",
          "value" : xxx,
          "unit" : "inch"
        },
        {
          "size" : "40",
          "name" : "chest_circumference",
          "value" : xxx,
          "unit" : "cm"
        }
      ]
    }
  ]
}

Waistband ratio

The measurement of interest of type waistband cannot be assigned to a body measurement in a straight-forward manner as its proper vertical position varies depending on the garment.

That is why for relevant garments (with garment groups that encompass the waistband measurement) the field waistbandRatio has to be set to a value between 0.0 and 1.0, whereas

0.0 means the waistband is supposed to be on a level with the waist
1.0 means the waistband is supposed to be on a level with the hip
values in between with linear interpolation.

Examples

Fit Model Chart	Table Format	Link
Tech Pack	Table Format	Link