This guide includes the following topics:

How is Nearmap's Imagery Georeferenced?

The MapBrowser's measurement tools use appropriate local representations of the Earth's surface and are typically accurate to +/- 15cm for distances up to 200m.

A mosaic of orthorectified images

Nearmap's Vertical Imagery is made up of mosaics of orthorectified images. This means that each raw photo that goes into making up our imagery has had the full orthorectification process applied, including removal of terrain distortions, lens distortions, and so on. Individual orthoimages are then merged together into a mosaic, which is the map image that you see on MapBrowser. We generate high resolution elevation maps as a necessary part of the orthorectification process (so that terrain distortions can be removed).

Our processing system can handle difficult situations such as cloud and smoke, and it has a far lower blunder rate than older orthophoto solutions. Our imagery processing is fully automated and designed to create Nearmap imagery anywhere in the world, without requiring any ground control point data at all. This also allows us to capture accurate vertical imagery in adverse conditions where ground point data is not available, is obscured, has moved, or is inaccurate.

GPS coordinates and PPP

Our capture process uses GPS coordinates, which are further refined using PPP (Precise Point Positioning). Because of this, the resulting imagery is georeferenced using ITRF2014 at the epoch of capture.  

For example, the epoch of a capture from May 1, 2018 is ITRF2014(2018.329). With ITRF2014 being an earth-fixed datum (as opposed to plate-fixed datums such as GDA94 or NAD83), imagery aligned to ITRF is subject to continental drift. For example, in Australia the movement is 70mm per year and some parts of the US move at about 14mm per year. In order to compensate for the continental drift, we provide plate-fixed projections through WMS and reverse the shift by a variable amount depending on the capture epoch. Those projections are based on either GDA94/GDA2020   (Australia) or NAD83 (US). As a consequence, we encourage you to use one of the plate-fixed projections in order to minimise misalignment in your GIS application, especially using surveys captured years apart.

This information should aid you in correctly georeferencing our imagery. We found that in most cases, it is sufficient to use one of our NAD83 or GDA94/GDA2020 projections to eliminate positional errors due to datum differences.

What is the Horizontal Accuracy of Nearmap 2D Imagery, and How is it Determined?

The tables below outline the Absolute Horizontal and Absolute Vertical Accuracy of our 2D imagery achieved with our earlier (1st Generation) and current (2nd Generation) camera technology.

Camera SystemGSDAbsolute Horizontal Accuracy
2nd Generation5.5cm / 2.2"19.8cm / 7.8" RMSEr
1st Generation7.5cm / 3"25.5cm / 10.1" RMSEr in areas after 2nd Generation coverage 46.1cm / 18.2" RMSE (radial) in other areas

Absolute horizontal accuracy is expressed as the root mean square of the radial distance error (RMSEr) and is measured in centimetres or inches.

Camera SystemGSDAbsolute Vertical Accuracy
2nd Generation5.5cm / 2.2"37.8cm / 14.9" RMSEz

Absolute Vertical Accuracy is calculated as Root Mean Square of the Vertical Error (RMSEz) and is measured in centimetres or inches.

Where we have historical captures taken with our current generation camera system, subsequent captures taken with our earlier generation camera system are improved to an absolute horizontal accuracy 25.5cm (10.1”) RMSEr.

Nearmap also uses ground control points to verify our accuracy claims.  Characteristics of our ground control points include good visibility, precise location, accurate location, and open ground location.  In essence, this means that the sample of ground points used are clearly identifiable in our aerial imagery without ambiguity, have a high accuracy of less than 2cm, and are not subject to terrain distortions. 

Do the Maps use True North or Magnetic North?

The MapBrowser uses true north rather than magnetic north. This is a natural consequence of the EPSG:3857 Mercator projection used in the MapBrowser and similar online maps. Microsoft has a good description of this projection here