Nearmap WMS integration allows users of off-the-shelf GIS and CAD applications to load high-resolution imagery on demand.
To consume Nearmap imagery via WMS, you must authenticate using API Key Authentication, and obtain either a Simple WMS URL or a Custom WMS URL to load in the application.
Once authenticated, your software package will have a way for you to specify:
Nearmap will provide the best projection for the WMS imagery.
Once you use either simple or custom WMS 2.0 in an application, the service will update with the new imagery every time Nearmap publishes a new survey.
The Simple WMS provides a URL that has the latest imagery for each region. The layer is shown only if you have access to that region (e.g. US, Australia, New Zealand).
The Simple WMS URL looks like this:
The Simple WMS displays the following layers:
The Custom WMS provides a URL that has the imagery for the areas you define.
Note: The imagery from which you select your area/s of interest is Nearmap vertical imagery, and will count against your Nearmap usage. Seeing you do not need to zoom in, nor pan around, you will be consuming very little usage for creating the WMS custom service.
We support the most popular local datums for all of our imagery. Depending on which coordinate system your GIS application is configured with, you can request imagery in the following coordinate systems:
When requesting imagery using WGS84 coordinate systems, namely EPSG:4326 (WGS 84) and EPSG:3857 (Web Mercator, Spherical Mercator, Pseudo-Mercator), our WMS service will automatically return imagery that has been converted to a local datum as per the table below.
|SRS||Australia||Canada||New Zealand||United States|
Several web applications assume GDA94 where the datum is not specified. (You can see from the table above that in Australia, Nearmap WMS 2.0 defaults to GDA2020.)
We provide a way to force the returned imagery to GDA94 with a custom request parameter DATUM. The behaviour of this parameter depends on the projection the imagery is requested in (SRS Parameter), as shown in the table below.
|Projection||DATUM=GDA94||DATUM is omitted (default behaviour)|
|EPSG:4326 (aka WGS84)||GDA94||GDA2020|
EPSG:3857 (aka Web Mercator)
|Any MGA94 projection||GDA94||GDA94|
|Any MGA2020 projection||GDA2020||GDA2020|
If your application relies on assumed GDA94, the alignment and accuracy can be improved by a significant margin, as you can see in the images below.
With GDA94 override
Nearmap supports PNG and JPEG through the WMS service. Most WMS applications will request maps from a WMS server using PNG by default. When loading raster maps, such as Nearmap imagery, PNG has several advantages and several disadvantages. Please see below the recommendations for configuring your application.
PNG has a transparency channel, which means you can overlay Nearmap imagery on top of another basemap (for example a worldwide satellite layer or a roadmap). This works best when at small scale, for example when using a city or statewide extent. Note that PNG imagery is not compressed as much as JPEG and it will take longer to download.
Use JPEG for working with imagery at large scale. At house or suburb level, the chances of being on the Nearmap boundary are much smaller, which means that you won't need the transparency capability of PNG. Note that if you do come across a boundary, the areas with no data are rendered as black.
Should I use Simple or Custom WMS?
The simple WMS should be used if you want the only latest imagery for your area (Australia/New Zealand/USA/Canada). You will not be able to perform geofencing or navigate time. Custom WMS will allow you to perform geofencing and to set up specified regions as the only imagery you can view. For those regions, you will be able to navigate the time and set boundaries for the dates.
Where can I find the options for Simple or Custom WMS?
You can find the options here: ou can then choose from Simple or Custom WMS.
Is WMS 2.0 more accurate than what I am currently using?
Australia - We have adjusted the datum of the imagery that is returned by default when you don’t specify a projection, i.e. rely on application defaults. WMS 2.0 will automatically adjust the imagery to GDA2020 coordinate system for Australia and NZGD2000 for New Zealand. This will reduce positional errors and projection mismatches ensuring your imagery lines up. WMS 2.0 will continue to support the GDA94 MGA zone projections in Australia.
United States - We have adjusted the datum of the imagery that is returned by default when you don’t specify a projection, i.e. rely on application defaults. WMS 2.0 will automatically adjust the imagery to NAD83 coordinate system. This will reduce positional errors and projection mismatches ensuring your imagery lines up. WMS 2.0 will now support all local state/plane projections in the United States (EPSG codes).
What are the best practices for defining areas?
Use simple boundaries around your areas of interest. The imagery is not requested until you interact with the application, so there is little difference in what imagery is returned when the custom service is used.
Are there limits to the Custom WMS services?
Do bigger areas in custom WMS contribute more to my usage?
No. The areas that you define for your custom service are simply instructions on how to build a list of layers in that service. At the time of creation, no requests for imagery within the area of interest are made. Usage is accrued only when you bring the WMS service into your GIS application and add it to the map.
Does interacting with the imagery in the area definition window count towards my usage?
Yes. When you define an area a small amount imagery is loaded to provide context for where we have coverage. We envisage that there will be very little usage coming from this tool because:
How do I use GDA2020 projections?
Available in Simple and Custom WMS. For Simple WMS all AU MGA zones are available in both GDA94 and GDA2020. For Custom WMS only the zones that intersect with the area of interest will be available as an option to request imagery in.
How do I use State Plane projections?
Only available in Custom WMS. Only the state plane projections that intersect with the area of interest will be available as an option to request imagery in.
The performance impact is not so much dependent on the size of the area, but on the number of surveys you bring back. There is a limit on how big an individual area can be, currently set at about 5000 km2, and you can specify up to ten areas in the same service. If you bring in ten metropolitan areas around Australia, you could be loading thousands of surveys. That would slow down your initial loading into your GIS application.