OpenStreetMap

Using Benchmarks for Imagery Offsets

Posted by DougPeterson on 29 January 2015 in English.

I came to the conclusion recently that I needed to start understanding and being concerned about imagery offset. This started when Bing imagery changed and I began to notice that buildings had shifted. I also began to use other imagery such as USGS Large Scale Imagery, which also did not necessarily align with Bing imagery.

Having decided to learn about imagery offset and use it I came to discover there had been no offsets created in the areas I typically mapped. Now I needed to understand how to create offsets.

I had read discussions of using GPS traces to establish an offset based on roads. In looking at the traces that were being downloaded within JOSM those traces seemed less than ideal. This was due to randomness of lanes driven in, possibly poor sampling resolution, as well as possibly poor GPS accuracy or bounce. It was going to take a larger sample to reduce that. So I started recording and uploading traces myself.

The slowness of creating a decent sample caused me to think about how to do this quicker. I considered finding a fixed and visible feature and doing some longer GPS averages on those sites over a number of days. It then occurred to me I should just find some benchmarks or survey marks as the National Geodetic Survey (NGS) already provides the coordinates for those.

I was familiar with benchmarks from the geocaching I do. It is a subtype of geocaching, at least in the U.S. In doing a little more searching on offsets I found this was a suggested approach so I proceeded on with it. I thought I would document and share my techniques to the extent they may help someone else or could be improved by someone else’s suggestions.

The benchmark datasheets that are posted on Geocaching.com are older. The coordinates are not the full resolution that is available. Not all benchmarks are on Geocaching.com. It was just what had been recorded at the time of the one and only import. So I start my search with the National Geodetic Survey Data Explorer. I can search an area of interest and look at the datasheets for benchmarks of interest.

The first step is selecting suitable benchmarks. Some benchmarks are large structures, like water towers or broadcast towers. Although there may have been a precisely measured point on the structure, it is generally not clear where that is and it would likely be obscured by the vertical structure.

There are benchmarks that are in grass and usually easy to find in person, particularly when accompanied by a witness post. However, they are not easily seen from satellite unless the concrete or dirt around them prevents grass from overgrowing the benchmark.

I have had the most success with benchmarks that are in sidewalks. These are often at a road intersections and in an intersection of sidewalks as well. The contrast of a dark and roughly eight inch benchmark cover against a lighter sidewalk makes for relatively reliable spotting. Even so, sometimes shadows or other things reduce the contrast such that the cover is not seen.

One thing that has helped me in improving the reliability of the benchmark placement is reviewing photos of the benchmark area. I have visited a number personally and have photos that I took. Others I have been able to verify position for by reviewing photos of the benchmark posted on Geocaching.com. In one case, the spot on the satellite imagery I thought was the benchmark turned out not to be.

In then looking at the datasheets it is important to look at the type of coordinates that are available. Typically, I have found the coordinates to be described as one of those below.

  • “The horizontal coordinates were established by GPS observations and adjusted by the National Geodetic Survey.” These are what I have chosen to limit my efforts to. I use the full coordinates listed to create a survey_mark in OSM to then use to create an imagery offset.
  • “The horizontal coordinates were established by classical geodetic methods and adjusted by the National Geodetic Survey.” Classical geodetic methods are generally speaking triangulation measurements. I do not know what increased level accuracy came with any adjustments made by NGS. As such, I have chosen not to use these.
  • “The horizontal coordinates were scaled from a topographic map and have an estimated accuracy of +/- 6 seconds.” These are not suitable for offset purposes. That 6 seconds can be over 600 feet or 180 meters off. In practice, I have found the measurements to often be 30-60 feet off.

The NGS datasheets describe the physical characteristics and location of the benchmark which may aid in finding it on satellite imagery. The PID listed in the datasheet can be used to look up the benchmark on Geocaching.com. For any survey_marks I have created in OSM I have included the PID and Designation names. I have also included the GPS coordinates in a note for future reference. Coordinates do get updated by the NGS.

I have found it a good idea to read the entire description. The benchmark may be gone. This would be noted in Station Recovery information at the bottom as can be seen in this datasheet where I reported one missing.

Discussion

Comment from Warin61 on 30 January 2015 at 00:44

Hi,

The imagery offset can change in 500 meters .. so you need to be aware of that.

GPS traces are best if you have both ‘up’ and ‘down’ traces on opposite side of the road.

Survey points are nice when found and you get the official data.


Note that ‘we’ are drifting on the earths surface .. so as time goes by locations will change! But the important thing to realize is that the map users will tolerate a fair amount of ‘inaccuracy’ as long as what is seen is able to be recognized on the map and found using it.

Comment from Zverik on 30 January 2015 at 07:55

Do you use http://offsets.textual.ru for storing your offsets?

Comment from DougPeterson on 30 January 2015 at 15:33

As I read about creating offsets I realized I need to be sure my driving traces had angles to them so that I could create better offsets. I continue to do driving traces. Eventually they may be of use to me or someone else. There are some areas in the broader area I map that I have not been able to find suitable benchmarks for. The driving traces may be needed there.

I have been uploaded the imagery offsets through JOSM. I checked the site and saw my offset uploads listed there.

Comment from Nakaner on 1 February 2015 at 19:34

Hi Doug,

I do not know what increased level accuracy came with any adjustments made by NGS.

Adjustment in this context is geodetic term. If you do tringulation, the sum of all interior angles of a triangle has to be 180°. If you measure these angles in field, you will get a sum which is not 180°, e.g. 179.854°. Now you have more measurements than necessary (two angles are necessary) and can adjust your measurements. You would add (1/3)*(180-179.854) to each measured angle. This is an very very easy adjustment.

In geodesy, you would usually adjust whole networks of angle, distance and GNSS¹ measurements.

I do not find a good site which explains geodetic adjustment good and understandable for non-geodesists (I could give you only some German Wikipedia articles).

Best regards

Michael (studying geodesy)

¹) GNSS (global navigation satellite systems) compromises GPS, GLONASS, Baidu, Galileo etc.

Comment from DougPeterson on 1 February 2015 at 23:16

Some adjustments I have seen are related to gravity and altitude or height. NGS may do similar sorts of calculations regardless of the original method of calculating the coordinates. I had tried to find information but I could not find much.

Comment from DougPeterson on 5 October 2015 at 17:34

I thought I would document the information I used in creating the survey point and offsets for my future reference.

Add Node using coordinates from NGS Datasheet: man_made=survey_point name=Benchmark PID AA6770 Designation 120 20 note=Used for creating offsets on Bing and USGS. N 42° 24’ 48.14568” W 83° 18’ 55.41223”

Add imagery bookmarks: Bing - Benchmark PID AA6770 Designation 120 20 USGS - Benchmark PID AA6770 Designation 120 20

Upload imagery offsets: Bing imagery offset based on Benchmark PID AA6770 Designation 120 20 located at Six Mile Road and Inkster road

USGS imagery offset based on Benchmark PID AA6770 Designation 120 20 located at Six Mile Road and Inkster road

Comment: Added survey point for Benchmark PID AA6770 Designation 120 20 to use with creating imagery offsets on Bing and USGS.

Sources: USGS Large Scale Imagery; Bing; NGS Datasheet

Log in to leave a comment