You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've crossposted this to oam-uploader-api but I'm not sure if that repository is monitored (nothing has been pushed in 5 years+). This is also relevant for metadata processing which may be a catalog operation.
I've been bulk processing some metadata from OAM and I noticed that the gsd parameter does not have consistent units. Some images report gsd in degrees (typically these are O(10^-6 to 10^-7)) and others are in metres as expected.
It seems like the browser handles this properly, as it'll show things like "2 cm" in the info panel. However looking in the metadata, this isn't always the case and it means that querying/filtering by GSD is not reliable. I'm not sure where this would need to be handled - perhaps in the uploader(?), as it's a fairly simple step to compute this for all uploads by default. I had a skim through the oam repos and couldn't see an obvious place where the meta gsd is obtained.
I'm also not sure if this is something that got fixed and there are just a bunch of outdated metadata files in the catalog? It would ideally need to be fixed at the ingest level, so that either images are checked to be in projected coordinates, or warping is performed to an appropriate CRS (but since that could vary depending on location it might be better to force users to do that).
Note the GSD is teeny (and the metadata does state that the projection UNIT is degrees). Converting to metres using the script below, we get the correct answer (as an example):
I've crossposted this to
oam-uploader-api
but I'm not sure if that repository is monitored (nothing has been pushed in 5 years+). This is also relevant for metadata processing which may be a catalog operation.I've been bulk processing some metadata from OAM and I noticed that the
gsd
parameter does not have consistent units. Some images report gsd in degrees (typically these are O(10^-6 to 10^-7)) and others are in metres as expected.It seems like the browser handles this properly, as it'll show things like "2 cm" in the info panel. However looking in the metadata, this isn't always the case and it means that querying/filtering by GSD is not reliable. I'm not sure where this would need to be handled - perhaps in the uploader(?), as it's a fairly simple step to compute this for all uploads by default. I had a skim through the oam repos and couldn't see an obvious place where the meta gsd is obtained.
I'm also not sure if this is something that got fixed and there are just a bunch of outdated metadata files in the catalog? It would ideally need to be fixed at the ingest level, so that either images are checked to be in projected coordinates, or warping is performed to an appropriate CRS (but since that could vary depending on location it might be better to force users to do that).
For example, image ID: 59e62b703d6412ef72208f33
Note the GSD is teeny (and the metadata does state that the projection
UNIT
is degrees). Converting to metres using the script below, we get the correct answer (as an example):Thanks!
The text was updated successfully, but these errors were encountered: