Hi Matt, I suggest calculating the radius so that assuming the speed changes gradually, the boxes drawn around adjacent coordinates should overlap with a factor of 1.5. For an example of this in the geospatial context, see radiusForSpeed in GeospatialCoordinateEncoder. - Chetan
On January 30, 2015 at 9:27:01 AM, Matthew Taylor ([email protected]) wrote: I'm working with XYZ coordinates and calculating speed on my own. Assuming each coordinate is 1 meter, my speed could be anywhere from 0 - 20 m/s. How should I calculate my own radius for the CoordinateEncoder? I'm currently using the speed in m/s directly, so it gets calculated as a value from 0 - 20, but I'm not sure that's the right thing to do. Thanks, --------- Matt Taylor OS Community Flag-Bearer Numenta
