This guide includes the following sections:

What is data usage based on?

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 numbered of parcels downloaded.

What consumes data?

The table below shows the various actions that consume data on different Nearmap platforms.


Classic MapBrowserNew MapBrowserNearmap on OpenSolar

Zooming and panning around in 2D at zoom level 14 and above, regardless of monitor size ◊(tick)(tick)(tick)

Larger monitor size ♦(tick)(tick)(tick)

Selecting another survey date - viewing 2D imagery(tick)
Selecting a date to view from the date dropdown box
(tick)(tick)

Exporting 3D content

N/A(tick)N/A

Exporting AI parcel data

N/A(tick)N/A

Solar reports(tick)
typically less than 1MB per report
N/A(error)

Consuming Nearmap imagery via an integration such as WMS, ArcGIS Online, Tile API and KML (Google Super-overlay)

N/AN/AN/A

DSM API - consumes by transactionN/AN/AN/A


◊ 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.

      

What does not consume data?

Are the usage statistics in Self Service Portal accurate?

We regularly audit our data usage calculations, examining server logs in order to determine whether session by session, day by day, correct usage statistics are being stored and shown. It is important to note that all imagery streamed from our server to your computer contributes to data usage, not just when using the Export function.

How do I know if I'm reaching my usage limit?

Administrators can check your account usage on the Self Service Portal. Follow the instructions here: View Account Data Usage.


<style type="text/css">

table {
  border-collapse: collapse;
  width: 100%;
  border: 1 px solid #8a8d8f;
}

th {
  text-align: left;
  font-size: small !important;
  font-weight: normal !important;
  background-color: #8a8d8f !important;
  color: #fff !important;
}

td {
  text-align: left;
  font-size: small !important;
}

table.confluenceTable th.confluenceTh p {
  text-align: left;
  font-size: small !important;
  font-weight: normal !important;
  background-color: #8a8d8f !important;
  color: #fff !important;
}

</style>