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

Pansharpening destroys projection information #200

Open
mankoff opened this issue Jul 14, 2016 · 0 comments
Open

Pansharpening destroys projection information #200

mankoff opened this issue Jul 14, 2016 · 0 comments

Comments

@mankoff
Copy link

mankoff commented Jul 14, 2016

Download and pansharpen a scene. Note that this does not cross the dateline as in #150

scene=LC82080052014154LGN00
landsat download ${scene} -b 1234567891011 -d .
mkdir ${scene}
tar xvf ${scene}.tar.bz -C $scene
# rm ${scene}.tar.bz
landsat process --p --pansharpen ${scene}
mv ~/landsat/processed/${scene}/${scene}_bands_432_pan.TIF ./${scene}

I'd expect the projection information to be the same or similar to B8, but it is not. In addition to a different projection (why?), the origin and pixel size don't appear correct.

B8

Origin = (483592.500000000000000,8692507.500000000000000)
Pixel Size = (15.000000000000000,-15.000000000000000)

PAN

Origin = (1589074.447645094944164,14534055.736723199486732)
Pixel Size = (72.942212531325680,-71.622120806659439)

Shouldn't PAN pixels be 15 m?

Also, I'm not sure why, but this data causes all sorts of issues in GRASS GIS. It won't align with the other bands.

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