Coordinates using data structures from typed data

[navispatial]

Basic coordinate data types of geobase could also wrap data specified by structures of typed_data package.

Currently coordinate array structures supported:

• Position: an instance of List containing x, y and optionally z and m too
• Box: an instance of List containing minX, minY, [minZ], [minM], maxX, maxY, [maxZ], [maxM]
• PositionSeries: an instance of List containing a series of position coordinates as a flat structure, ie x0,y0,z0,x1,y1,z1,x2,y2,z2, ...

Following typed data structures could be used as a source instead of "plain" List without need for changes on geobase data structures:

• Float32List that implements List<double> and TypedData and contains a fixed-length list of IEEE 754 single-precision binary floating-point numbers
• Float64List that implements List<double> and TypedData and contains a fixed-length list of IEEE 754 double-precision binary floating-point numbers

Other types could be supported by implementing new factory methods:

• Float32x4
  • Float32x4 stores 4 32-bit floating point values in "lanes". The lanes are "x", "y", "z", and "w" respectively.
  • This could be used to store coordinate values for Position(x => x, y => y, z => z, m => w)
• Float32x4
  • A fixed-length list of Float32x4 numbers that is viewable as a TypedData
  • This could be used to store a series of positions in PositionSeries with all coordinates (x => x, y => y, z => z, m => w) in each position.
• Float64xx
  • Float64x2 stores 2 64-bit floating point values in "lanes". The lanes are "x" and "y" respectively.
  • This could be used to store coordinate values for Position(x => x, y => y) in 2D
• Float64x2
  • A fixed-length list of Float64x2 numbers that is viewable as a TypedData
  • This could be used to store a series of positions in PositionSeries with 2D coordinates (x => x, y => y) in each position.

[navispatial]

Implemented in geobase 0.6.0