So I ran a mapping mission of a rectangular area, and after processing the downloadable images, TIFFs, and DEMS only appear as small squares in the positions where the drone took the images. Interestingly, the KMZ file displays correctly in Google Earth. All other images seem to be processed incorrectly. A little upsetting when I used 600+ credits to run this process.
Sorry for the inconvenience. It looks like the automated trimming got a little overzealous. We have turned that off and set it to rerun.
We have determined that this was caused by the high altitude of capture, the overlap settings and the narrow field of view of the camera. We will use your data to help make the trimming algorithm more accommodating.
Please sign in to leave a comment.
Ah cool, thanks for the quick response. I had just sent you all an email as well about 10 minutes ago. Yeah this was pretty mountainous terrain, 250ft AGL, 80/80 coverage. I see them reprocessing now, I appreciate it!
This has also been happening to my coworker... kmz looks fine but all the advanced outputs are clipped severely. Acct is under Barrett Jenkins.
Matthew: I don't see any issues with the maps in the account you mentioned. Please let us know which map you are specifically referencing at mapping@dronesmadeeasy.com
We believe we have fixed this issue. Please let us know if it happens again.
The maps you highlighted by email are having a different issue. The ones being discussed here were mostly completely black except for little dots where the source images were. The issue with your maps is that they lacked sufficient overlap for the area to be rendered. You can see this in the Overlap Report. Red dots mean the image was present and processed but it was unable to be included. The areas that were not able to be rendered were attempted to be filled in using the Flat Map system which doesn't rely on feature matching.
The KMZ as well as the DEM and other 3D related files will only exist for the part that was able to be rendered. The Flat Map Patch GeoTiff file is available to supplement the GeoTiff that was made from the rendering. The web map shows them both together.
As noted in the Data Collection guidelines that are agreed to at the time of upload and in the Map Pilot Pro overlap settings you need to use at least 80% overlap when covering treed areas. Bare trees are even harder to render and may require more. Depending on lighting conditions it may not even be possible in certain areas.
i have the same issue
i have processed a small area and i am trying to load the geotiff in to Bricscad. it loads and places the item in the correct location however the scale is way out.
the points cloud works and It does work in google maps
Jason: Your issue is completely different. We can't really help you use any other software. All of our outputs are in EPSG:4326.
