Fix #208 (min speed = 0)

[Raruto]

Close: #208 Close: #224 Close: #227

---

Related to:

• track.speed_min is always 0 #208
• d3, min, max, avg, precision #216

TODO: check skipNullZCoords behavior (before / after this edit)

[Raruto]

Hi @hupe13,

If you have absolutely nothing to do, let me know what you think of these latest changes.

Surely they also introduce some related bugs due to the presence of NaN in the geojson layer (eg. when you try to display the hotline layer for a gpx file that is missing some altitude values).

BTW I guess this problem was introduced by the _registerDataAttribute during the 2.x refactoring (in trying to handle all the new extensions added in the src/handlers folder).

But anyway this is all my speculation (it's all code that I look at very occasionally..)

Thanks for your patience,
Raruto

[hupe13]

min speed seems to be okay.

[Raruto]

@hupe13 Related to: #224 (comment), let me know if here we can proceed with the merge (or if other adjustments are needed) and subsequent release of the new version.

[hupe13]

I think so. I have tested it and it seems to be correct.