SDX-Cloud: Use Wingtra image data for drone mapping

Summary

This guide explains how to use Wingtra drone imagery in SDX-Cloud for drone mapping. It covers the survey preparation, GCP and checkpoint workflow, PPK processing in WingtraHub, the SDX-Cloud upload, and the final quality checks.

This guide assumes the Wingtra flight itself is already completed and that the captured images and raw GNSS data are available. It focuses on the surveying and data-processing steps that affect the final accuracy in SDX-Cloud.

Prerequisites

• You have completed the Wingtra flight and exported the captured images and raw GNSS data.
• You have an SDX-Cloud project or can create one.
• You have a GNSS rover to survey GCPs and checkpoints.
• You use the same correction service and the same coordinate system across the rover survey, project setup, PPK workflow, and SDX-Cloud processing workflow.
• You have a RINEX 2.11 or newer file from a CORS network or from your own base station that covers the full flight duration.
• If you use your own base station, it is set up before the flight and logs raw observations for the full flight duration.
• Your GCP targets use a high-contrast black-and-white checkerboard pattern.
• Your GCP targets are at least 40 × 40 cm (about 1.3 × 1.3 ft) for flights up to 80 m AGL.
• Your GCP targets should be about 70 × 70 cm (about 2.3 × 2.3 ft) for flights above 80 m AGL.
• You place at least 4–5 GCPs per site and distribute them across the edges and center of the survey area.
• If NTRIP corrections are available on site, you can use the SDX-Pole to survey GCPs.
• If only UHF corrections are available on site, you need a rover that supports UHF corrections.

Steps overview

1. Prepare Ground Control Points (GCPs)

   Place at least 4–5 GCP targets across the site and distribute them evenly across the edges and center. Make sure the targets are clearly visible from the planned flight altitude. Use targets that are at least 40 × 40 cm (about 1.3 × 1.3 ft) for flights up to 80 m AGL and about 70 × 70 cm (about 2.3 × 2.3 ft) for flights above 80 m AGL. The surveyed coordinate is the center point where the four checkerboard quadrants meet.

   Who does it: Survey team or drone operator.

2. Survey GCPs and optional checkpoints

   Survey each GCP with the same correction service and coordinate system used on the project site. Document every GCP position with photos, sketches, and numbering so you can identify each target later during image marking. If you want an independent accuracy check after processing, place at least 5 checkpoints across the site, mark their XY positions with spray paint, and survey them with the same rover setup. Checkpoints are for verification only and are not used during processing. If you use the SDX-Pole with NTRIP on site, see Sodex Mobile: How to work with Ground Control Points.

   Who does it: Survey team.

3. Prepare the correction data for PPK

   Download the RINEX data from the nearest CORS reference station or export your own base-station RINEX file. Make sure the time window covers the full flight duration. If you use your own base station, the base station must already have been set up before the flight and must log raw observations for the full mission.

   Who does it: Drone operator or survey team.

4. Run PPK in WingtraHub

   Open WingtraHub, which is included with the Wingtra drone workflow, load the drone's raw GNSS data, load the CORS or base-station RINEX file, and run PPK. Review the per-image accuracy indicators and the fix percentage. Aim for a fix rate above 95%. If the fix rate is lower, investigate the base data quality before you continue. For the SDX-Cloud import, use the geotagged images folder with corrected EXIF coordinates, not only the standalone CSV export. If you need the exact WingtraHub flow for creating that export, follow Wingtra's PPK geotagging documentation. For more detail on the PPK stage, see PPK Processing for Photogrammetry Snapshot Import.

   Who does it: Drone operator.

5. Create the SDX-Cloud image import

   Open the target project in SDX-Cloud and start a new drone-mapping image import. Upload the geotagged Wingtra images from the WingtraHub output folder.

   Who does it: SDX-Cloud user.

6. Add Ground Control Points and mark them in the images

   Use an existing project GCP set or upload the surveyed GCP coordinates during the import. If you used the SDX-Pole, you can push GCPs directly from Sodex Mobile; otherwise upload a CSV with point ID, Easting, Northing, and Height. During processing setup, identify and mark each GCP target in the overlapping images so the processing run can use the correct survey references. Before you continue, verify that the project coordinate system, the surveyed GCP coordinates, and the corrected image geotags all match. See How to Create a Ground Control Point Set and Use Ground Control Points during photogrammetry import.

   Who does it: SDX-Cloud user.

7. Start processing and review the report

   Start the processing run and review the processing report when it completes. Confirm that the run finishes without critical errors before you rely on the outputs. If you want to review the available processing files and open the report PDF again after processing, use the processing files view for the data model.

   Who does it: SDX-Cloud user.

8. Validate the output and export deliverables

   Review the GCP residuals, compare the checkpoints against the processed model, and inspect the orthomosaic, DSM, and point cloud before you export deliverables.

   Who does it: SDX-Cloud user or survey lead.

Workflow variations

Variation 1: PPK + CORS Network + GCPs

• Corrections: Download RINEX data from the nearest CORS reference station.
• Field setup: No physical base station is needed on site.
• GCP survey: Survey GCPs with a rover that uses the same site correction service and coordinate system.
• Best for: Sites where a reliable CORS service is available for the full mission.

Variation 2: PPK + Own Base Station + GCPs

• Corrections: Deploy a physical base station before the flight and export its RINEX data afterward.
• Field setup: The base station must log raw observations for the full flight duration.
• GCP survey: Survey GCPs with a rover that uses the same base reference, whether through NTRIP or UHF.
• Best for: Sites where you need your own correction source instead of a nearby CORS network.

Verification

• The import used the geotagged images folder from WingtraHub, not the raw images folder.
• If you needed guidance for that export, you followed Wingtra's documented PPK geotagging flow.
• The project coordinate system matches the surveyed GCP coordinates, rover correction workflow, and corrected image geotags.
• If you used your own base station, it was set up before the flight and logged raw observations for the full mission.
• WingtraHub shows a fix rate above 95%.
• If the fix rate was below 95%, you checked the base data quality before you continued.
• Every imported GCP was identified and marked in the overlapping images.
• The processing report completed without critical errors.
• The GCP residuals are within the expected accuracy for the project.
• The checkpoints confirm that the final output meets the expected absolute accuracy.
• The orthomosaic, DSM, and point cloud look complete and aligned.

Quick reference

Related articles

• Introduction to Ground Control Points
• How to Create a Ground Control Point Set
• Use Ground Control Points during photogrammetry import
• PPK Processing for Photogrammetry Snapshot Import
• How to Manually Create a Photogrammetry Data Model
• Feature: Data Model Processing Files