Bug 296149

Summary:	OpenStreetMap : map blur problem
Product:	[Applications] marble	Reporter:	Philippe ROUBACH <philippe.roubach>
Component:	general	Assignee:	marble-bugs
Status:	REPORTED ---
Severity:	wishlist	CC:	caulier.gilles, iwannaberich, KDE, mike
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	blur rmap non blur map

Description Philippe ROUBACH 2012-03-16 13:33:12 UTC

digikam 2.6 beta 2

in any part of digikam (gpssync, right panel, center panel)
openstreetmap maps  by default are blur

marble has solved the pb see bug #199259
but
to have non blur map you must applies these principles in marble and in digikam :
- use only "mercator"
- use only buttons + and - to zoom thus don't use mouse wheel

consequently i suggest :
- when selecting openstreetmap then by default "mercator" is selected
- when selecting openstreetmap mouse wheel movements are translated to + or - button clicks
or
at least when selecting openstreemap then ahelp windows pops up saying "you must use mercator and +- buttons to have a non blur map"

thanks

addendum :
i don't remember where i read this but marble devs plan to build a bank of vectorized (svg) osm maps thus a kde server for this.

Comment 1 caulier.gilles 2012-03-16 13:53:18 UTC

Can you provide a screesnhoot of the problem please ?

Gilles Caulier

Comment 2 Philippe ROUBACH 2012-03-16 14:09:52 UTC

Created attachment 69668 [details]
blur rmap

Comment 3 Philippe ROUBACH 2012-03-16 14:10:30 UTC

Created attachment 69669 [details]
non blur map

Comment 4 Philippe ROUBACH 2012-11-03 09:24:06 UTC

i remeber with previous versions i can choose the horizontal size of the windows as any type of kde windows for example the digikam window

Comment 5 Philippe ROUBACH 2012-11-03 09:25:02 UTC

ignore comment #4

Comment 6 caulier.gilles 2013-12-05 23:33:12 UTC

This file still valid using digiKam 3.5.0 ?

Gilles Caulier

Comment 7 Philippe ROUBACH 2014-01-11 11:08:49 UTC

opensuse 13.1 , kde 4.12 , digikam 3.5
Samsung Galaxy SII P , android 4.2.2

still valid

Comment 8 caulier.gilles 2014-08-24 21:31:11 UTC

What's about this file using last digiKam 4.2.0 ?

Gilles Caulier

Comment 9 Philippe ROUBACH 2014-09-01 11:08:08 UTC

opensuse 13.1 , kde 4.14.0 , digikam 4.2.0

bug still valid

Comment 10 caulier.gilles 2014-09-01 11:10:27 UTC

Michael,

Can we considerate this bug as fully relevant of Marble widget ?

Gilles

Comment 11 Michael G. Hansen 2014-09-04 09:16:20 UTC

Gilles,

I do not know for sure, have to check the API.

Michael

Comment 12 caulier.gilles 2015-05-12 13:52:17 UTC

Micheal,

This bug is relevant of libkgeomap or marble ?

Gilles

Comment 13 caulier.gilles 2015-05-12 13:52:48 UTC

Philippe,

Problem still here using last digiKam 4.9.0 ?

Gilles Caulier

Comment 14 Michael G. Hansen 2015-05-12 18:21:56 UTC

Hi Gilles,

I think this is a Marble problem, and can be solved by following the steps outlined in #199259 as Philippe pointed out, namely using the Mercator projection and only using Marble's zoom buttons for zooming in/out. Other than that, there is nothing we can do, unless we want to define special keyboard shortcuts. Then, however, usage of Marble inside digikam would be different from normal Marble...

Michael

Comment 15 Philippe ROUBACH 2019-03-09 12:16:10 UTC

kde app 18.12.2
kde plasma 5.15.2
kde framework 5.55.0
qt 5.12.1

digikam 6.0.0
marble 2.2.20

problem still there.

Comment 16 Christoph Feck 2019-03-24 12:32:14 UTC

Philippe, is this a duplicate of bug 199259?

Comment 17 Philippe ROUBACH 2019-03-26 10:50:27 UTC

(In reply to Christoph Feck from comment #16)
> Philippe, is this a duplicate of bug 199259?

if this is a marble problem then yes. at hte beginning this report is about digikam.