When using a custom Maps API plugin with it's own coordinate system, the QGraphicsGeoMap::addMapObject places the object into a strange position.

The plugin contains a QGeoTiledMapData subclass, which is used by QGeoTiledMappingManagerEngine. The following virtual methods is implemented on the subclass.

coordinateToWorldReferencePosition(const QGeoCoordinate& coord)
worldReferencePositionToCoordinate(const QPoint& pixel)

These methods provide the conversion into a certain coordinate system.

When the map object is added via QGraphicsGeoMap::addMapObject(), it seems that the object's position is somehow forced to mercator.

When using Qt Mobility version 1.1.3, the same code works perfectly and this does not happen.

When debugging the situation in version 1.2.0, the parameter QPoint& pixel in the method worldReferencePositionToCoordinate() is different than in 1.1.3.