Nearmap 3D & DSM content offers wide-scale, photo-realistic 3D models and elevation datasets for infrastructure projects across Australia and North America.
This page provides accuracy specifications and more for each 3D content type. The following information is covered here:
Coverage
Use our interactive coverage map to see if we currently cover your locations of interest.
https://www.nearmap.com/au/en/current-aerial-maps-coverage#/coverage-checker (this URL will resolve to your region's content).
Using 3D in MapBrowser
Textured Mesh
Resolution
Textured Mesh | Notes | |
---|---|---|
3D Mesh Geometric | 6" or 15 cm | Approximate distance between mesh vertices in high detail areas. |
3D Mesh Texture/Imagery Resolution | 2.2-3" or 5.6-7.6 cm | Range given since some parts are textured with oblique imagery. |
You can view textured mesh in Cesium 3D Tiles format in MapBrowser.
Export File Contents
- SLPK
- Cesium 3D Tiles
- OSGB
- OBJ
- FBX
Viewing 3D Textured Mesh in Third-Party Applications
Textured mesh content in third-party applications.
Product Constraints
- Objects that are
- Objects that are beneath another object, or semi-obstructed
DSM (Digital Surface Model)
GSD
6" or 15 cm
Export File Contents
- GeoTIFF
- ASCII
Viewing DSM in Third-Party Applications
DSM in third-party applications
Product Constraints
- Objects that are
- Objects that are beneath another object, or semi-obtruded
Point Cloud
GSD
6" or 15 cm
Export File Contents
- LAS
Viewing 3D Point Cloud in Third-Party Applications
Point Cloud in third-party applications
Product Constraints
- Point cloud will likely be significantly larger in file size than the 3D mesh. Specialized software can optimize the storage of point cloud to make it perform better
True Ortho
Export File Contents
- GeoTIFF
- JPEG
- ASCII
Viewing True Ortho in Third-Party Applications
True Ortho in third-party applications
Product Constraints
Although Nearmap's True Ortho is an image similar in appearance to the regular vertical (ortho) product, it has a 5cm pixel size and is lower in resolution than the standard product.
DEM/DTM (Digital Elevation Model/Digital Terrain Model)
Resolution
MapBrowser export options include 30 cm (1 ft) / 60 cm (2 ft)/ 90 cm (3 ft) based on a source 15cm GSD. Offline exports can be based on these resolutions or user-defined.
Export File Contents
- GeoTIFF
For more information, see DTM File Contents
Viewing DTM in Third-Party Applications
This is a new content offering. Watch this space for guidance on consuming this content type in third-party applications.
File Formats and Delivery Methods
3D Product | File Formats | Delivery Methods |
---|---|---|
Textured Mesh | OBJ SLPK 3MX Cesium FBX |
|
Point Cloud | LAS | |
DSM | GeoTIFF | |
True Ortho | ||
DEM/DTM |
Horizontal Accuracy
3D Product | Absolute Horizontal Accuracy | Horizontal Datum/Projection |
---|---|---|
Textured Mesh | 11" or 28 cm RMSEr | SLPK exports: WGS84/UTM Cesium exports: ECEF in addition to the datum listed below |
DSM |
| |
Point Cloud | ||
True Ortho | ||
DEM/DTM |
Vertical Accuracy
3D Product | Absolute Vertical Accuracy | Vertical Datum/Projection |
---|---|---|
Textured Mesh | 14.9" or 37.8 cm RMSEz | SLPK exports: WGS84/UTM Cesium exports: ECEF in addition to the ones listed below |
DSM |
| |
Point Cloud | ||
True Ortho | N/A | |
DEM/DTM | 14.9" or 37.8 cm RMSEz (Valid for bare earth areas) | As listed above |
FAQs
Any single export is limited to 50km2/20mi2. This could be any where between 25GB and 75GB in size depending on the format you have chosen. The 3D tool set will be expanded over time. We would love to hear what tools you would like included in the future. Contact your Customer Service Manager. To do this, you will need to make multiple coverage calls (i.e. with a Transaction Token for each), make the image calls and stitch together the images. Find out more here: DSM and True Ortho API When using the DSM and True Ortho API, your coverage radius is smaller than your image call radius. Ensure your coverage radius is as large as you require. Find out more here: DSM and True Ortho API For the 30 day life of your Transaction Token, you can make any number of image requests on any or all three content types (DSM, True Ortho, Vertical) and of any vintage. The physical and pixel size of the image are deliberately explicit to give you control over the image that will be returned. This is further complicated by the fact that True Ortho and DSM are of different native resolutions (0.055 m versus 0.15 m). Request the imagery by inspecting the coverage response and then calculating the pixel size based on the metadata.
You might also be interested in...
-
Before You Export (PRODUCT DOCUMENTATION)
-
3D Export Formats (PRODUCT DOCUMENTATION)
-
Export 3D (PRODUCT DOCUMENTATION)
-
Export 3D Content (PRODUCT DOCUMENTATION)
-
View 3D (PRODUCT DOCUMENTATION)
-
Measure 3D (PRODUCT DOCUMENTATION)
-
3D Content in Applications (PRODUCT DOCUMENTATION)
-
Nearmap and Rhino: Importing 3D Site Models with Textured Mesh in Rhino for Windows and Mac (Nearmap Technical Blog)
-
Visualise your Revit BIM design with Nearmap 3D (Nearmap Technical Blog)