Interesting possible bug in meshing for the orthophoto. This is a dataset that previously worked in 1.x series (untested in 2.0.0):
The point cloud looks good:
The 3D mesh looks good:
The DSM is flipping spectacular:
But the ortho is a mess:
Console text can be found here:
Images can be shared as needed.
Mm, interesting!
Images would help, as well as testing on 2.0.0 and see if it happens there.
You can pull the 2.0.0 vesion with docker pull opendronemap/nodeodm:2.0.0.
Images are (or soon will be) here:
https://clemetparks-my.sharepoint.com/:f:/g/personal/svm_clevelandmetroparks_com/Ep15ga6uTsFKtxS1XtdenW0BX6VTz3BSUkBfao6gUKWIig?e=aEFTT0
I can run it through a 2.0.0 node shortly.
No access 
link asks for a login.
Stupid OneDrive. It looks like you have to have an MS account to access data shared with the world. Try this:
https://drive.google.com/drive/folders/1HF0gm8iZKeR2upYfRLF5okRhA0oIvMhE?usp=sharing
It’s uploading now, so should be ready 9:45 ET
Ah, that’s more an Organizational restriction. No such limitation for data hosted in Personal OneDrive accounts.
Yell at your sys-admin (nicely 
).
Ah, that must have been part of the recent security lock-down. Let’s see if we can get them to ease that a bit: I understand not having write access, but if I want to share things widely, I need that capacity.
Maybe pitch it to them with Time-Based Expiry sharing as well, so the link doesn’t stay active indefinitely. In addition, a PSK (pre-shared key) can be added to further secure access to just those whom have the password you assign to the share link.
It shouldn’t present too much of a risk surface for them, I hope!
Yeah, I think I can pitch time-based expiry without too much fuss.
Mm, I got a nice looking ortho using default settings:
Are you on Windows and did you mount a volume by any chance when running ODM?
Interesting. My parameters weren’t too strange:
Options: mesh-octree-depth: 10, texturing-nadir-weight: 28, mesh-size: 300000, dsm: true, camera-lens: brown, depthmap-resolution: 1000
Sorry, didn’t see the Windows question.Nope here too. 
I’ll try rerunning.
Huh. Rerunning resulted in a good ortho. Super weird. I’ll close this and monitor… .
Do the point cloud / textured models look fine?
Likely, this looks like a corruption / race condition issue.
An interesting thing to try would be to run the pipeline from the mvs-texturing step multiple times (say 10 or 20) and keep copies of the resulting orthophotos, see how many of those are corrupted.
