Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#9654 closed defect (fixed)

[patch] [build fix] classes that use JMapViewer shoudn't use OsmMercator directly

Reported by: glebius Owned by: team
Priority: blocker Milestone: 14.02
Component: Core Version:
Keywords: Cc:



Fixing #7017 requires that all classes using JMapViewer stop trusting OsmMercator as projection solver. Only tilesources, that know that they are using OsmMercator projection, should use OsmMercator. All upper layers should ask the tilesource for (x,y) ?= (lon, lat) calculations.

I already made this change in the JMapViewer itself. Unfortunately, hiding OsmMercator required its API change as well, so right now JOSM isn't buildable.

The attached patch makes JOSM to use tileSource instead of direct use of OsmMercator, and apparently fixes build as well.

Attachments (1)

use_tileSource_instead_of_OsmMercator.diff (3.1 KB) - added by glebius 7 years ago.

Download all attachments as: .zip

Change History (4)

Changed 7 years ago by glebius

comment:1 Changed 7 years ago by xeen

Resolution: fixed
Status: newclosed

In 6793/josm:

[build fix] classes that use JMapViewer shoudn't use OsmMercator directly (fixes #9654, patch by glebius)

comment:2 Changed 7 years ago by Don-vip

Milestone: 14.02

comment:3 Changed 7 years ago by stoecker

Thanks a lot.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.