OpenStreetMap license out of date

Thanks Peter for the heads up.

Qreator does not explicitly list the license. Wherever we mention the license, we do it through the Gtk.Champlain widget, i.e. through the GTK bindings (see attachment).

So you might want to contact the GTK developers instead. However, if you've spotted any other place where Qreator shows the OSM data's license incorrectly, please let us know.

While I'm not convinced that it would have been my task as a mapper to fix that or to delegate that to the origin (using a widget or not - in fact Qreator fails to follow the licenses of data it uses), I filed a bug at the gtk.Champlain widget in bugzilla, see https://bugzilla.gnome.org/show_bug.cgi?id=700569

I hope I'm right and you use the current version of that widget, as if not and they already fixed it, it would be still up to you to fix it.

Hi jongleur,

Thanks a lot for the follow-up. From the Qreator side, we do not have the ability to modify the Gtk.Champlain widget or use another version that is not available as a package in the Ubuntu archive, so filing the upstream bug is exactly the right thing to do.

Otherwise, if you consider this to be a serious concern, the only thing we can do is to remove OSM and use another mapping service. However, I'd be sad to see it go, as from the feedback the map QR code is one of the most popular ones and gives good visibility to OSM.

For the record, we're using the gir1.2-champlain-0.12 and gir1.2-gtkchamplain-0.12 packages. In summary 0.12, which seems to be the latest version already: https://developer.gnome.org/libchamplain/

Hi David.

No, I don't want you to switch the mapping service. As most other mappers I'm happy to see osm in the wild. Nevertheless I stumbled upon this in qreator and didn't want to tae the time to investigate which component exactly is responsible for it.
Additionally it might have been the case that the corresponding component is included in (instead of being referenced by) Qreator, in which case it would have been possible to simply have to update the bindings or sth. like that.
I'm happy to see that you registered for the upstream bug - looks like you want to follow it, so everything's fine for now.
Nevertheless it should be fixed in (better near) future of course ;)

Great, thanks Peter :-)

Indeed, I'm following the upstream bug and when it's fixed there I might be able to help in backporting it to a stable Ubuntu release.

I've just fixed this in libchamplain master. However, if you want to fix it in your code right now, it is possible to create custom map sources in libchamplain. Unfortunately ChamplanFactory isn't fully introspectable so you cannot register your source which makes creating custom map source a bit harder in python.

Attached is an example how to create a new map source with a different license in python. Note that this creates an uncached source so the tiles get loaded from the network every time. If you wanted a cached source (which is what libchamplain uses by default), have a look at champlain_map_source_factory_create_cached_source() in libchamplain source - reimplementing this in python is just something like 10 lines of code.