Raptor Maps

The Raptor Maps Knowledge Hub

Welcome to the Raptor Maps knowledge hub. You'll find guides and documentation to help you start working with Raptor Maps as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started

Capturing Oblique Images

Oblique images provide another means to identify anomalies, and are especially helpful in identifying larger scale issues, such as those associated with inverters and combiners.

IMPORTANT: Obliques must be captured same day as inspection level imagery.

Review these requirements before an inspection to ensure the images you capture meet Raptor Maps standards.

Note that each image should provide an overview of 2 MWdc.

Element

Requirement

Coverage

Each image should provide an overview of 2 MWdc.

The 2 megawatts should appear in the lower half of the field of view of the image. See example, below.

Lens

13 mm or 19 mm; see specifics for each lens below

Images

IR (radiometric JPEG) and RGB (JPEG)

Image resolution

640 x 512 pixels or greater

Maximum speed

15 mph / 24 kph

Altitude

400 ft / 122 meters above ground level

Environmental conditions

Skies clear and sunny or slightly overcast
Irradiance greater or equal to 600 Watts per square meter
Humidity ideally less than 60%

Flight path

The flight path specifics will vary, depending on your lens length.

Element

13 mm lens

19 mm lens

Gimbal pitch

70 degrees from nadir (20 degrees down from the horizon)

74 degrees from nadir (16 degrees down from the horizon)

Overlap

80% front overlap (direction of flight) and 20% side overlap

80% front overlap (direction of flight) and 27% side overlap

Flight path

Begin flight path at a distance of 480 feet / 146 meters from the first row of panels.

Each subsequent side pass should begin 660 feet / 200 meters from the end of the previous (see illustration, below).

Begin flight path at a distance of 762 feet / 232 meters from the first row of panels.

Each subsequent side pass should begin 660 feet / 200 meters from the end of the previous (see illustration, below).

Here is a sample of oblique image of 2 megawatts: the 2 megawatts should appear in the lower half of the field of view of the image:

Planning for oblique flights

Many pilots fly manually to collect oblique imagery.

If, however, you would like to create an automated flight plan, you will need to use a workaround. Here is how to do so with the DJI Ground Station Pro (GSP).

The workaround requires creating a custom camera setting for oblique imagery.

Important note: Use this custom camera setting for oblique imagery only. Don't forget to switch out of this mode when undertaking other portions of the inspection!

Use these settings to create a simulated camera with a 4 mm focal:

Once you’ve created this custom camera, create a flight plan with these settings:

Element

Setting

Altitude

400 feet above ground level

Shooting angle

Perpendicular to main path

Front overlap ratio

80%

Side overlap ratio

If using 13 mm lens: 20% If using 19 mm lens: 27%

Additional instructions for 13 mm lens:

Move the polygon from your normal inspection imagery back by about 480 feet from the solar farm. This will ensure that the first pass of images captures the beginning row of the farm. When you are ready to start, use your RC controller to manually set your gimbal to 70 degrees from nadir and you should be good to go.

Additional instructions for 19 mm lens:

Move the polygon from your normal inspection imagery back by about 762 feet from the solar farm. This will ensure that the first pass of images captures the beginning row of the farm. When you are ready to start, user your RC controller to manually set your gimbal to 74 degrees from nadir with your RC controller and you should be good to go.

Important note. Make sure to change your camera settings back to proceed with the capture of normal thermal inspection imagery.

Updated 5 months ago

Capturing Oblique Images


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.