Skip to content
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

Problems noticed when working with a DEM #4

Open
AlisterH opened this issue Nov 29, 2018 · 0 comments
Open

Problems noticed when working with a DEM #4

AlisterH opened this issue Nov 29, 2018 · 0 comments

Comments

@AlisterH
Copy link

Hi, great plugin, thanks.
It doesn't look like there isn't any active development, but I think it is worth filing these issues in case anyone decides to work on it in the future.

I've been abusing the plugin, using it to deform a DEM.

I imagine this means I am deforming it a lot further than people usually would when rubbersheeting, which may make it easier to notice any problems - I guess it would be worth testing extreme deformations even with a normal image.

Here are the problems:

  • With large inward deformations you will notice that part of the original image still shows up at the edge, duplicating part of what you correctly see in the deformed image. When I test with an aerial that I haven't clipped, this problem seems to be fixed or worked around by using a buffer, but that doesn't solve it with the DEM (which has null values around the edge), or with an aerial that I have clipped so that it has null values around the edge. I believe in these cases the plugin should erase the original values in that area, replacing them with null values.

  • When working with a DEM the plugin creates some pixels around the outside with extremely low values. I'm not sure if this is cause by the null values around the outside, or by some sort of extrapolation. It doesn't seem that anything like this occurs when working with an aerial; maybe it only works properly with RGB images or something.

  • The plugin also creates some pixels along the triangulation lines with extremely low values. Again, it isn't obvious if there is a similar problem with an aerial.

  • It looks like the triangulation algorithm could be improved; it creates some edges crossing over each other. Try using the attached pairs layer to see.

example files.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant