Follow

Data Capture Guidelines for Producing Great Maps


High quality 2D and 3D maps and models starts with high quality source imagery. We've put together this list of recommendations and suggestions below to help you get set up to collect great data!

These guidelines are the result of the combined experience of our team of experts plus observations and feedback we've received over the years from our customers. If you have any questions or suggestions of your own, please let us know by sending us an email at support@skycatch.com. 

Standard Datasets:

Camera Recommendations

  • Recommended camera configuration.
    • ISO from 80 to 400
    • Exposure time = 1/1000
    • Shutter speed time = 1/1002
  • Camera pointed directly towards the ground (straight down, aka nadir)

Avoid: using lenses that result in distortion (e.g. fisheye) and ISO > 400

Photo Recommendations

  • Remove blurry images, photos captured on take off/landing, and photos captured traveling to/from the flight area
  • If oblique imagery is included, it must have at least 80% overlap on every side (top, bottom, left, right)

Mission Planning and Terrain Recommendations

  • The mission planning phase should ensure that your photos have aside overlap >60% and image front overlap >80%. We recommend using a mission planner such as the Skycatch flight app if you have a compatible DJI drone!
  • Ground Surface Composition
    • Area with high level of ground features (non-uniform surface colors, patterns, textures)
    • Less than 25% of the total surface area is “uniform surfaces” such as snow, water, forest, bright/highly reflective materials (such as solar panels or glass)
  • Time of day and lighting conditions
    • Flying within one hour before and after 12pm (or peak sun) provides optimal shadow conditions (least amount of shadows).
    • If multiple flights are required for a large site, avoid extreme variations in lighting and shadows by performing flights in similar lighting conditions if possible.
    • Flights should be flown at a consistent altitude above ground level (AGL). So for collection areas with changing ground elevation (hilly or mountainous), use terrain following, such as that provided with Skycatch High Precision Package.
    • If the collection area is very large, take note if there is inconsistent cloud cover over time. Large variance in cloud conditions can cause the photos to have large variance in light level, which can cause stitching to fail and accuracy to suffer. If you encounter this situation, we recommend using a pre-processing software such as Lightroom, to even out the brightness and contrast across all photos prior to uploading to Skycatch.
  • If multiple flights are needed for a dataset
    • The footprint of photos from each flight must maintain the minimum overlap requirements (listed above)
    • The flights should occur within the same general span of time to avoid large changes in lighting conditions

Guidance for datasets that are processed with GCPs:

  • When using the Skycatch Printable GCPs, please follow these guidelines to get the best conditions for successful processing every time:
    • When flying 80 meters AGL to 120 meters AGL, print GCPs to at least 116 cm x 116 cm (46" x 46"). Do not fly higher than 120 meters AGL, as the GCPs will be too small to detect.
    • When flying lower than 80 meters AGL, you can print the GCPs to 61 cm x 61 cm (24" x 24").
    • Ensure you have accurately surveyed the GCP at the exact center point.
    • Ensure the GCPs are evenly distributed across the entire site, spaced no more than 200 meters apart (218 yards).
    • Ensure that the drone’s camera has a clear, unobstructed view of all GCPs. For example: do not place them where they will be blocked by a tree, tower, or crane.
  • GCP file should be correctly formatted and filled in with the format as described in the Skycatch Support Center here.
  • The GCP coordinate system your GCPs are submitted in must be a known coordinate system and not an arbitrary system. You can verify your coordinate system in the EPSG.io database.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk