Wrong EPSG code for some landsat scenes? #113
|
I'm getting what appear to be the wrong epsg codes in items returned by a stack search import pystac_client
import planetary_computer
catalog = pystac_client.Client.open(
"https://planetarycomputer.microsoft.com/api/stac/v1",
modifier=planetary_computer.sign_inplace,
)
search = catalog.search(collections=["landsat-c2-l2"], datetime="2021",
bbox=[-137.072784 , -18.57953999, -136.290558, -18.26195699])
print([item.properties['proj:epsg'] for item in search.item_collection()])
[3268, 3268, 3268, 3267, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268, 3268]Based on the location, I believe the correct zone is probably 32608 (and 32607). |
Replies: 3 comments 2 replies
|
Thanks for the report. I believe we spotted that yesterday, and it was fixed in the stactools package at stactools-packages/landsat@9a3d93c. According to stactools-packages/landsat#38, it'll affect any EPSG code where the second to last digit is 0. We need to regenerate and reingest the STAC items with the fixed EPSG codes. In the meantime, you'll have to modify the STAC items manually :/ |
|
Thank you, will do |
|
Found some more bad items (epsg code is 3268, should be 32608), here are the IDs: |
Thanks for the report. I believe we spotted that yesterday, and it was fixed in the stactools package at stactools-packages/landsat@9a3d93c. According to stactools-packages/landsat#38, it'll affect any EPSG code where the second to last digit is 0.
We need to regenerate and reingest the STAC items with the fixed EPSG codes. In the meantime, you'll have to modify the STAC items manually :/