Is your feature request related to a problem? Please describe

Looking into https://betaflight.com/docs/development/gps#dynamic-platform-model I realize that there's a contradiction between the recommended value of gps_ublox_flight_model and the default one.

Betaflight on auto-config will use Stationary before arming and Airborne <4g after arming.

At the same time in the next line I read:

It is recommended to use Airborne <1g, but consult the u-blox documentation for sanity checks.

And in the previous paragraph:

Set to Dynamic Model to Airborne <1g and click Send.

This enables sanity checks for a maximum altitude of 50,000m, maximum vertical or horizontal speed of 100m/s. Any measurement outside these would invalidate the fix as they are not plausible.

On my rekon35 I have HGLRC M80, so I've decided to check chip manufacturer's official documentation.

In page 21 there is a table called Dynamic Platform Models, here's its part:

On the next page there's one more table called Dynamic Platform Model Details:

And indeed, Airborne <1g or event Bike look the most suitable for average FPV quad for I can hardly imagine the one with horizontal speed 250 or 500 m/s and vertical one of 100 m/s.

More over, under the table there's one more Nota bene:

Dynamic platforms designed for high acceleration systems (e.g. airborne <2g) can result in a higher standard deviation in the reported position.

To sum up: Airborne <4g looks like completely excessive (and less precise) for an average FPV quad, but still BF uses it as the default value for gps_ublox_flight_model. Is there any reason for this?

Describe the solution you'd like

Specify Airborne <1g as the default value for gps_ublox_flight_model and use it.

Describe alternatives you've considered

Leave the documentation and default config as is.

Other information

No response