phpGPX 2.x

[Sibyx]

This is the 2.x draft MR that turns parts of the “Road to 2.x” plan and long-standing issues into actual code instead of wishful thinking. [github](#67)

Implemented in this draft

• Implemented a new, more explicit approach to statistics objects.

  • Moves away from “everything is an array + stats->toArray()” towards proper typed objects
  • Lays groundwork for better handling of extended stats (heart rate, etc.) instead of keeping them trapped in extensions-only land. This touches the spirit of issue Create statistics from GPX extensions #15 (Create statistics from GPX extensions). [github](Create statistics from GPX extensions #15)

• Added support and/or internal plumbing for more advanced statistics and bounds, in line with Statistics - get Bounds of the GPX Routes #28 (Statistics – get Bounds of the GPX Routes).

  • Makes bounds and related metrics easier to access in a structured way instead of re-implementing calculations in userland.

• Refined the elevation smoothing internals, taking into account the ongoing discussion in How does elevation smoothing best work? #55 and cumulativeElevationGain and cumulativeElevationLoss not correct when missing parts of track with gps problem? #59.

  • Uses the documented configuration flags like APPLY_ELEVATION_SMOOTHING, ELEVATION_SMOOTHING_THRESHOLD, and ELEVATION_SMOOTHING_SPIKES_THRESHOLD more predictably.
  • Aims to make cumulative elevation gain/loss less surprising while still keeping the behavior configurable. [github](cumulativeElevationGain and cumulativeElevationLoss not correct when missing parts of track with gps problem? #59)

• Started implementing the 2.x cleanup around Removal of Summarizable and toArray #69 (Removal of Summarizable and toArray) and Middlewares #68 (Middlewares).

  • Reduced magic toArray() usage in models in favor of explicit, typed data structures and a clearer serialization story. github

Breaking changes

• Some stats access patterns from 1.x (e.g. relying heavily on stats->toArray()) will need updating to work with the new typed objects.
• Parts of the internal stats and elevation handling are now stricter and less “do everything by side-effect,” which may surface hidden assumptions in existing code. github

Feedback welcome on

• Whether the new stats API is actually nicer to use than the old array-based one.
• If the elevation smoothing now behaves closer to what you expect in real tracks (especially for long / noisy activities).

If you find something weird, confusing, or hilarious in a bad way, please comment. It’s still called “2.x draft,” which means I can rename, move, and rethink things without having to blame “backwards compatibility” yet.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️