Modify

Opened 6 years ago

Last modified 5 years ago

#15836 new defect

Always a big gamble on what zoom levels and position the new image will end up being overlayed

Reported by: jidanni Owned by: rebsc
Priority: normal Milestone:
Component: Plugin piclayer Version:
Keywords: Cc:

Description

For a fresh picture the program has never seen before, this sequence:

On the JOSM screen zoom to the are we are interested in.

Now choose "New picture layer from file."

seems to not always have consistent results.

E.g., sometimes:

So..... what happened to our nicely zoomed area?

There it still is, in a tiny spot in the middle of the new image.

But other times there is our new image, draped nicely over most of the screen.

It seems to depend on the zoom levels of the current layers, and the
size of the imported .jpg or something.

I think when importing an image: the user has already set up the
background to where he expects the image to be overlayed.
So then the incoming image should be overlayed upon 90% of the screen,
without affecting the current zoom etc.

(Apparently the program makes the assumption that we must be loading
satellite images many times the size of the area we had zoomed to before
loading the image.

How to deal with this?
A workaround is to zoom in many more times, before loading the image.)

Attachments (0)

Change History (2)

comment:2 by Don-vip, 5 years ago

Owner: changed from Larry0ua to rebsc

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain rebsc.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from rebsc to the specified user.
Next status will be 'needinfo'. The owner will be changed from rebsc to jidanni.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from rebsc to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.