Modify ↓

Opened 14 years ago

Closed 14 years ago

#6098 closed defect (fixed)

[patch] Round imagery offset numbers to 2 decimal digits

Reported by: Zverikk Owned by: Upliner
Priority: normal Milestone:
Component: Core imagery Version: latest
Keywords: imagery, offset, precision Cc:

Description

So 2.9682203345000744 would become 2.97. OSM data precision (~1 cm) does not require nanometer imagery positioning.

Attachments (0)

Change History (6)

comment:1 by Zverikk, 14 years ago

Summary: Round imagery offset numbers to 2 decimal digits → [patch] Round imagery offset numbers to 2 decimal digits

Patch is in #5787

comment:2 by Upliner, 14 years ago

There may be problems with non-metric projections such as EPSG:4326. However, 1m precision is still good, I'll probably commit it tomorrow.

comment:3 by Zverikk, 14 years ago

Fair point, I've fixed the patch to support it. But Bing layer (and, probably, any other TMS) do not support EPSG:4326. And precision is not 1 m, but around 1 cm.

Last edited 14 years ago by Zverikk (previous) (diff)

comment:4 by Upliner, 14 years ago

Strange, for me Bing works well with EPSG:4326.

comment:5 by Zverikk, 14 years ago

  1. Add Bing layer in Mercator projection
  2. Zoom to 10 m or less
  3. Apply any offset to Bing layer (just drag it a bit, or type "1;1")
  4. Change projection to WGS84
  5. FAIL

Although it works with no offset or on large zooms.

comment:6 by Upliner, 14 years ago

Resolution: → fixed
Status: new → closed

In [4001/josm]:

applied #5787 Display and read offset as one line (patch by Zverik), fixes #6098

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Upliner.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

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