developmentseed / developmentseed/landsat-util
Pansharpening destroys projection information
- Dominant language
- Python
- Stars
- 698
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.