Skip to content

update GDAL service context product #122

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

update GDAL service context product #122

wants to merge 3 commits into from

Conversation

sarabond
Copy link
Contributor

Update the GDAL context product as well as creating a new context product for gdal3.js.

sarabond and others added 2 commits May 23, 2025 09:34
Update the GDAL context product as well as creating a new context product for gdal3.js.
@sophiaconover
Copy link
Contributor

Sara will add internal references the context products. File names should be lowercase and have the version number, for example, gdal3_1.0.xml

@jordanpadams jordanpadams changed the title udpate GDAL service context product update GDAL service context product Jun 25, 2025
@jordanpadams
Copy link
Member

@sarabond any updates on this PR?

@jordanpadams
Copy link
Member

@sarabond ping! :-)

@sarabond
Copy link
Contributor Author

sarabond commented Jul 7, 2025

Hi @jordanpadams, I'm waiting for input from @rgdeen on what the GDAL references should point to. Once I have that information, I can complete this task.

@thareUSGS
Copy link

thareUSGS commented Jul 7, 2025

Sara will add internal references the context products. File names should be lowercase and have the version number, for example, gdal3_1.0.xml

Hmm - actually I'm not sure I know what this means. Do you mean some example archive GDAL supports like "lroc"?

<Internal_Reference>
    <lid_reference>urn:nasa:pds:context:instrument:lro.lroc</lid_reference>
    <reference_type>collection_to_instrument</reference_type>
</Internal_Reference> 

GDAL is really better at derived data (RDRs). Should we point to just to the LROC RDRs?
https://doi.org/10.17189/a6a1-mw73 (urn:nasa:pds:lro-l-lroc-5-rdr::3.0)
or

<Internal_Reference>
   <lid_reference>urn:nasa:pds:lro-l-lroc-5-rdr</lid_reference>
   <reference_type>collection_to_bundle</reference_type>
</Internal_Reference>

We could this for CTX, HiRISE, Magellan, Cassini radar almost anything derived (map projected) and any target body.


BTW, GDAL does have a DOI: https://doi.org/10.5281/zenodo.5884351

@jordanpadams jordanpadams added the WIP Work-in-progress label Jul 9, 2025
@jordanpadams
Copy link
Member

@thareUSGS

GDAL is really better at derived data (RDRs)

Maybe, but it is also useful for just converting .IMGs to anything else, so maybe it is really all camera instruments (and their associated instrument hosts/investigations)?

@rgdeen
Copy link

rgdeen commented Jul 9, 2025

@thareUSGS apparently we have to make a list. But RDRs count... I mean, if someone wants to process LROC data then GDAL should come up regardless of whether they're looking at EDRs or RDRs. I think eventually, we'll be able to have more nuance here, but basically as a starting point we just want to make sure it shows up on appropriate searches.

@sarabond
Copy link
Contributor Author

Hi all, to clarify the actions here, it sounds like we want searches for instruments/investigations related to LROC data to point to to GDAL, as a start. Correct me if I'm misunderstanding that. If that is the case, I see some resources here that help me to understand the associated camera instruments. Let me know if this is an appropriate resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WIP Work-in-progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants