This guide includes the following sections:
For imagery usage your data usage is measured in bytes of Nearmap proprietary aerial imagery viewed.
For AI parcel data your usage is measured in numbers of parcels downloaded.
integrations such as WMS, ArcGIS Online, Tile API and KML (Google Super-overlay)
NOTE: The DSM API - consumes by transaction.
|Classic MapBrowser||New MapBrowser||Nearmap on OpenSolar|
|Zooming and panning around in 2D at zoom level 14 and above, regardless of monitor size ◊ ♣|
|Larger monitor size ♦ ♣|
|Selecting another survey date - viewing 2D imagery ♣|
Selecting a date to view from the date dropdown box
Exporting 3D content
Exporting AI parcel data
typically less than 1MB per report
◊ Once you are zoomed out below 14, no data is consumed, no matter how much panning or how big your screen is.
♦ The bigger your monitor, the more tiles you can fit in view and therefore the more data you will consume.
But once you are zoomed out below 14, no matter how much panning or how big your screen is, we won't count data.
♣ 2D usage still applies if you are viewing a roads or streets layer on top of your Nearmap imagery.
|In New MapBrowser you access Roads Overlay from the Data Layers panel on the left.||In Classic MapBrowser a roads layer is displayed by clicking the Street Maps button.|
There is no extra usage charge for viewing the AI Layers in MapBrowser. The data usage will be the same as normal data usage for viewing Vertical content.
The area you're viewing has no Nearmap coverage when:
|In New MapBrowser - by selecting Roads as your view type from the Base Layer picker||In Classic MapBrowser - by selecting Roadmap as your view type|