NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

As mentioned in a similar question (see: the background imagery of Bing often does not match the GPS traces and existing ways.

In the answers to the above mentioned question it was explained that holding the space key allow for moving/adjusting the background. This is nice to know, but is there a way to permanently adjust the offset of background imagery?

asked 01 Dec '10, 12:56

ALE's gravatar image

accept rate: 14%

edited 07 Dec '10, 17:04

Andy%20Allan's gravatar image

Andy Allan

Not at present, but it's being worked on.

permanent link

answered 01 Dec '10, 13:38

Richard's gravatar image

Richard ♦
accept rate: 18%

The project ideas are documented on the wiki here:

(05 Dec '10, 20:06) Claudius Hen...

Any progress on this front?

(27 Aug '12, 09:08) Ent

The problem is that aerial imagery can and will be updated without such a service noticing. Assume that you had bing imagery with 50m offset and had supplied the offset data to the True Offset Process. Bing then updates with imagery that is better than 1m offset georeferenced, you end up moving correctly georeferenced imagery by 50m.

In summary there doesn't seem to be a better solution than manually checking before you edit. However there are ideas floating around about providing more and better documented reference points that could even be part of a "automatic" pre-edit setup process.

(27 Aug '12, 14:01) SimonPoole ♦

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 01 Dec '10, 12:56

question was seen: 7,098 times

last updated: 27 Aug '12, 14:01

NOTICE: is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum