Container message point type mapping

The Point Type of PI points created from a container message is determined by the type, format, and reftypeid fields of the corresponding type property.

• If the property is not using reftypeid, the Point Type is derived from the property's type and format according to the table below. If a type/format combination is not included in the table, it cannot be used when creating a container by the PI Web API.

• If the property is using reftypeid, if the reftypeid corresponds to an enumeration type, the Point Type will be digital. Otherwise, the PI Point type will be derived from the enumeration type's type and format according to the table below.

  Property Type	Property Format	Point Type	Notes
  string		String
  string	date-time	Timestamp
  integer		Int32
  integer	int16	Int32	The Data Archive has special behavior for PI points of type Int16; for consistency with other PI point types, the PI Web API instead uses Int32.
  integer	int32	Int32
  integer	int64 (non-reftypeid)	Float64	Loss of precision is possible when writing dynamic data, because Data Archive does not natively support Int64. If you need to preserve data precision, use a lossless data type, such as String.
  integer	int64 (reftypeid)	String	To preserve data precision,reftypeid points of format int64 will use a lossless data type.
  integer	uint16	Int32
  integer	uint32	Float64
  integer	uint64 (non-reftypeid)	Float64	Loss of precision is possible when writing dynamic data, because Data Archive does not natively support UInt64. If you need to preserve data precision, use a lossless data type, such as String.
  integer	uint64 (reftypeid)	String	In order to preserve data precision, reftypeid points of format uint64 will use a lossless data type.
  number		Float32
  number	float32	Float32
  number	float64	Float64
  boolean		Int16