Improve default processing parameters

[smathermather]

dsm: true, dtm: true, feature-quality: ultra, matcher-distance: 20, matcher-neighbors: 800, mesh-octree-depth: 14, mesh-size: 400000, min-num-features: 24000, pc-geometric: true, pc-quality: ultra

[hcwinsemius]

@smathermather can you explain the rationale behind this default set? Would they work well under all occasions including use of drone photos versus street level? Or are they for a specific use case?

[smathermather]

"The numbers all go to eleven... It's not ten. You see, most blolx will be playing at ten."

Most of these option changes are related to defaults we set in WebODM to keep stuff from crashing on folks with limited hardware.

feature-quality: ultra
Set feature extraction quality. Higher quality generates better features, but requires more memory and takes longer

matcher-distance: 20
Good for street level photography. Will be changed when OpenSfM eventually is updated and has better defaults

matcher-neighbors: 800
Good Necessary for street level photography. Will be changed when OpenSfM eventually is updated and has better defaults

mesh-octree-depth: 14
Memory and CPU intensive but much nicer detail in meshes

mesh-size: 400000
Memory intensive. Could probably be turned up louder

min-num-features: 24000
This is one of the more important changes: it improves matching significantly in complicated scenes. If we switch to ORB feature time some time in the future, this could be 5x this value and still run faster, but my testing with ORB features hasn't been successful yet

pc-geometric: true
Cleans the final model a bit based on visibility tests

pc-quality: ultra
Memory and CPU intensive but much nicer detail in point cloud