-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] DTM/DSM Resolution #914
Comments
This would be a nice feature. Currently See https://github.com/OpenDroneMap/ODM/blob/master/scripts/odm_dem.py#L96 since we currently don't allow a user to specify the radius. |
More the GSD ceiling, and it looks like the interpolation radius gets modified automatically as the GSD changes, though the radius might be useful to expose, I'm not jumping to add more flags for people... . I put in a pull request for doing 4x this. I'll do some further testing -- I've got someteen thousand images to test this on in the next couple of months, but this patch should help others while we discover what these values should be. I think point clouds need some improvements before we can really understand how to really improve these, but at least we can prevent people from having memory problems. |
Closed by #915 |
Proposed solution for OpenDroneMap#914 Former-commit-id: e720d9a
It would be nice to have DSM/DTM resolution based on some multiple of the resolution calculated for the orthophoto, e.g. if ODM calculates that the optimum resolution for orthophoto is 5 cm, default to 20 cm for the DSM and DTM resolutions. This is commonly how closed source packages handle this, and of course, like orthophoto resolution would require a flag for override.
The text was updated successfully, but these errors were encountered: