https://codereview.qt-project.org/c/qt/qtpositioning/+/435520 gave formal names to the QML value types, which were previously "anonymous". This means: Before that patch, QML code was unable to refer to those types by name.

Informal names for these types already exist throughout our documentation (see https://doc.qt.io/qt-6/qtpositioning-qmlmodule.html#value-types and https://doc.qt.io/qt-6/qml-qtpositioning-location.html#coordinate-prop for example), but unfortunately these informal names don't match the actual names that QML code would now use. For example:

property geoCoordinate london1: ( { "latitude": 51.5072, "longitude": -0.1276 } ) // Correct

property coordinate london2: ( { "latitude": 51.5072, "longitude": -0.1276 } ) // ERROR: "coordinate" does not exist

Here's a complete table of the value types:

Notes
geoAddress, geoLocation, and geoPositionInfo are missing from https://doc.qt.io/qt-6/qtpositioning-qmlmodule.html#value-types

• geoAddress should be documented because there's a public property of this type: https://doc.qt.io/qt-6/qml-qtpositioning-address.html#address-prop
• geoLocation should be documented because there's a public property of this type: https://doc.qt.io/qt-6/qml-qtpositioning-location.html#location-prop
• I'm not sure about geoPositionInfo. It looks like Position (https://doc.qt.io/qt-6/qml-qtpositioning-position.html ) provides an "indirect" wrapper for geoPositionInfo/QGeoPositionInfo, so perhaps geoPositionInfo shouldn't be documented as a standalone type. I'll let the Qt Positioning maintainers comment on this.