[Interest] QML Map & MapQuest

[Paolo Angelelli]

On Fri, 26 Aug 2016 07:00:30 +0000
Alexander Blasche <alexander.blasche at qt.io> wrote:

> Hi,
> 
> >Since July 11, 2016 MapQuest disabled direct tile access. So QML Map
> >doesn't support MapQuest anymore. So my question when MapQuest
> >support will be implemented again?
> 
> The fix is detailed in https://bugreports.qt.io/browse/QTBUG-54599
> 
> We had to move away from MapQuest. To facilitate quicker changes in
> the future we added a level of indirection which permits us to
> redirect OSM based geoservice requests to a new service if the same
> problem occurs with the new service. This fix will be part of 5.6.2,
> 5.7.1 & 5.8.0 alpha.
> 
> I would like to point out that we discourage the use of the OSM
> plugin in production code. The same thing can happen again and
> although we have an additional indirection it is no insurance that we
> find yet another free map service thereafter. Even if we have a new
> alternative the maps may likely look completely different and your
> user experience would change underneath you. 
> 
> In summary you may use the OSM in production at your own risk. If
> this risk is not acceptable then please one of the other existing
> plugins. They have commercial T&C which implies that you have a
> business relationship with the provider. This reduces the risk of
> drastic changes and even if it does change, you get informed about it
> and can react early.
> 
> --
> Alex
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

I guess the easy answer is when someone will write a geoservice plugin
for MapQuest :-)

I would also like to add to Alex answer that, if you really want to use
our OSM plugin in production, you should consider using your own
redirection server/url where you have control over what servers are
in use and when.

You can of course copy what is hosted @ maps-redirect.qt.io/osm,
but, as Alex said, if, say, Thunderforest will shut down the open
access service, we might be forced to disable those map types.

If you use your own redirection server and files, you can always
switch to a provider that needs a token, and embed the token in
the template URL.