Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

edge handling of rasters when reprojected #888

Open
artemp opened this Issue · 3 comments

3 participants

@artemp
Owner

The foss4g style is composed of a variety of adjacent rasters. When reprojection occurs various things can go wrong at edges. This is understandable and we likely can't handle every edge case but this one is severe.

[[Image(normal.png)]]

[[BR]]

[[Image(seams_epsg3153.png)]]

[[BR]]

[[Image(clipping_epsg3857.png)]]

@artemp
Owner

[albertov] Hmm, I think that this might be fixed by changing {{{reproject_raster()}}} to use map coordinates instead of screen coordinates to determine the mesh points. I'll try to fix this later today or ASAP... Can you please write down the bboxes and srss of those adjacent rasters (gdalinfo output would be more than enough), as well as for the query that visualizes them, so I can synthetise some test data?

Alberto

@artemp
Owner

[springmeyer] gdalinfo output on the rasters is here: https://gist.github.com/1262581

@springmeyer
Owner

@albertov - do you need anything else? I can track down the source images if you need, just let me know.

@albertov albertov was assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.