Bug 246924

Summary:	[enhancement] add openstreetmap in gpssync
Product:	[Applications] digikam	Reporter:	Philippe ROUBACH <philippe.roubach>
Component:	Geolocation-Osm	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, mike
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	7.5.0

Description Philippe ROUBACH 2010-08-06 18:21:41 UTC

Version:           1.3.0 (using KDE 4.4.3) 
OS:                Linux

when i set position i use gpssync
but
a) frequently in google map there is no detail as in openstreet map
then i must guess the position to set
then
i go back to gpswidget
then
i see in openstreetmap the position is not good
then
i goto gpssync to set a new postion
then
etc. (loop till the position is good in openstreetmap)

b) in google map and openstreetmap things are not at the same place

it would be handy to work with openstreetmap in gpssync

c) i participate to add photo to openstreetview (beta project) then i want them well spotted

d)i participate to fill openstreetmap geodata bank

thanks



Reproducible: Didn't try




OS: Linux (i686) release 2.6.33.6-desktop-69mib
Compiler: gcc

Comment 1 Michael G. Hansen 2010-08-06 18:31:59 UTC

Hi Philippe,

this feature has been implemented and will be available once the gsoc-branch is released, probably in December.

http://community.kde.org/File:Reverse-geocoding-example-1.png

The screenshot shows all possible map views.Google Maps of course supports all Google Maps layers like Map, Satellite, etc. OpenStreetMap is supported via Marble. We started a web based version once, but hit some rendering issues with KHTML so we suspended work on it for now.

In theory, we could also introduce a way to 'split' the map view so you can see the marker on both Google Maps and OSM at the same time - when you move it in Google Maps, it will move in OSM once you drop it. Would that be interesting for you?

Michael

*** This bug has been marked as a duplicate of bug 206133 ***

Comment 2 caulier.gilles 2022-01-07 16:57:51 UTC

Fixed with #206133