Take OpenDroneMap from simple toolchain to an online processing tool + open aerial dataset. This would be distinct from and complementary to OpenAerialMap:
- Explicitly engage and provide a platform for drone enthusiasts to contribute imagery in return for processing services.
- Address and serve:
- Aerial imagery
- Point clouds
- Surface models
- Terrain models
- Additionally, as part of a virtuous circle, digitizing to OSM from this aerial imagery would refine the surface models and thus the final aerial imagery
- Digitizing OSM on this dataset would result in 3D photogrammetric breaklines which would in turn refine the quality of surface and terrain models and aerial imagery.
- Aerial basemap
- (ultimately with filter for time / season?)
- Point cloud (see e.g. http://plas.io)
- Digital surface model (similar to Open Terrain)
- Digital elevation model (in conjunction with Open Terrain)
- OpenDroneMap https://github.com/OpenDroneMap/OpenDroneMap
- Open Terrain https://github.com/openterrain/openterrain
- OpenAerialMap / OpenImageryNetwork http://openaerialmap.org
- MapKnitter http://openaerialmap.org
- Point cloud related technologies:
- PDAL / Greyhound and related projects
- e.g. http://iowalidar.com/
- http://plas.io
Drone | Flight Height | Pixel | Overlap | Per flight | City Name | City Area | Total # of Flights | Total Flight time |
---|---|---|---|---|---|---|---|---|
E384 | 400 ft | 3 cm | 60% | 1.5 sq mile | San Francisco | 50 sq miles | 33 flights | 66 hours |
E384 | 400 ft | 5 cm | 90 % | 0.5 sq mile | San Francisco | 50 sq miles | 100 flights | 200 hours |
E384 | 400 ft | 3 cm | 60 % | 0.5 sq mile | Cleveland | 80 sq miles | 54 flights | 108 hours |
E384 | 400 ft | 5 cm | 90 % | 0.5 sq mile | Cleveland | 80 sq miles | 160 flights | 320 hours |
Iris+ | 400 ft | 3 cm | 60% | 0.078 sq mile | San Francisco | 50 sq miles | 640 flights | 213 hours |
Iris+ | 400 ft | 5 cm | 90% | 0.026 sq mile | San Francisco | 50 sq miles | 1920 flights | 640 hours |
which cam do you recommend with iris+? gopro?