Questions_and_Answers_0001.pdf

1.ௗPWSௗ3.1: Which TIFF tag ID (decimal/hex) and JSON key namespace must be used for the ISIS3 metadata block so that ASC/NASA tools recognise it?ௗ

We expect to use "json:USGS" for our metadata, more details in the conversation found here: https://github.com/DOI-USGS/ISIS3/discussions/5698

2.ௗPWSௗ3.3: What exact JSON element name and message template shall GDAL insert into the ISIS3 key when an image is clipped or re-projected (e.g., "ProcessWarning" vs.

"History")?ௗ

The history object would be updated with message that it was cropped.

"CubeLabel/Core/Dimensions/lines" and "CubeLabel/Core/Dimensions/samples" will also have to be updated.

3.ௗPWSௗ3.4: Please specify the PDS4 schema release(s) (e.g.,ௗv1.19, v1.20) that GDAL must support and supply the associated XSD/JSON files for validation.ௗ from Technical Liaison: v1.24. released in June 2025. A minimal PDS4 label would have these schemas listed.

<?xml version="1.0" encoding="UTF-8"?>

<?xml-model href="https://pds.nasa.gov/datastandards/schema/released/pds/v1/PDS4_PDS_1 O00.sch" schematypens="http://purl.oclc.org/dsdl/schematron"?>

<?xml-model href="https://pds.nasa.gov/pds4/disp/v1/PDS4_DISP_1O00_1510.sch" schematype ns="http://purl.oclc.org/dsdl/schematron"?>

<?xml-model href="https://pds.nasa.gov/pds4/cart/v1/PDS4_CART_1O00_1970.sch" schematyp ens="http://purl.oclc.org/dsdl/schematron"?>

<Product_Observational xmlns="http://pds.nasa.gov/pds4/pds/v1" xmlns:pds="http://pds.nasa.gov/pds4/pds/v1" xmlns:disp="http://pds.nasa.gov/pds4/dis p/v1" xmlns:cart="http://pds.nasa.gov/pds4/cart/v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://pds.nasa.gov/pds4/pds/v1 https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1O00.xs d http://pds.nasa.gov/pds4/disp/v1 https://pds.nasa.gov/pds4/disp/v1/PDS4_DISP_1O00_ 1510.xsd http://pds.nasa.gov/pds4/cart/v1 https://pds.nasa.gov/pds4/cart/v1/PDS4_CART_1O00_ 1970.xsd">

<Identification_Area>

<logical_identifier>urn:nasa:pds:junocam_atm-ml-calib:data_calibrated:grs_pj_27_jc_000000</logical_identifier>

<version_id>1.0</version_id>

<title>GRS_PJ_27_jc_000000.xml</title>

<information_model_version>1.24.0.0</information_model_version>

<product_class>Product_Observational</product_class>

</Identification_Area>

4.ௗPWSௗ3.4: Confirm the endianness and signed/unsigned interpretation for <missing_constant> hex values such as 0xFF7FFFFB.

From Technical Liaison:

from here: https://github.com/OSGeo/gdal/blob/92b6c26e937eaaf8371ccbc37928181af71d765 b/frmts/pds/isis3dataset.cpp#L82C1-L87C72. I believe this should force the endianness and signed definitions.

// Define 4-byte special pixel values for IEEE floating point const float ISIS3_NULL4 = -3.4028226550889045e+38f; // 0xFF7FFFFB;

const float LOW_REPR_SAT4 = -3.4028228579130005e+38f; // 0xFF7FFFFC;

const float LOW_INSTR_SAT4 = -3.4028230607370965e+38f; // 0xFF7FFFFD;

const float HIGH_INSTR_SAT4 = -3.4028232635611926e+38f; // 0xFF7FFFFE;

const float HIGH_REPR_SAT4 = -3.4028234663852886e+38f; // 0xFF7FFFFF;

5.ௗPWSௗ4ௗ&ௗAppendixௗAௗ§1: Are there any citizenship, residency, or visa requirements for project sta ?ௗ

Preference given to US based companies

6.ௗPWSௗ5: Will the contractor be required to conduct any on-site visits to Flagsta ௗAZ or other Government facilities for kick-o , integration testing, or demonstrations, or is the e ort expected to be 100ௗ% telework?

No, everything can be done remote

7.ௗPWSௗ3ௗ&ௗ7: Approximately how many test images and total data volume (GB) will USGS furnish for unit, integration, and acceptance testing so we can size storage, compute resources, and test-phase LOE?ௗ

We cut testing data down, we use about 300mb of test data rn for most of our tests. The easiest thing would be to test against gti versions of these cubes, gtests should all theoritically pass as if they were cubes. https://github.com/DOI- USGS/ISIS3/tree/dev/isis/tests/data

8.ௗAppendixௗAௗ§§2-3ௗ&ௗ5: Will contractor personnel require USGS network or VPN accounts, thereby triggering DOI end-user security training and annual renewal, or will all source-code work be performed entirely on contractor-owned infrastructure?ௗ

Contractors will be using their own hardware/infrastructure.

9.ௗAttachmentௗBௗ(Sectionௗ508): Is the contractor expected to deliver a Sectionௗ508 Accessibility Conformance Report (VPAT) for GDAL code and documentation?ௗ

Helpful, not required.

10.ௗITOsௗ“SubmissionௗofௗQuotes”: Is there a page-count or file-size limit, or formatting requirements, for the emailed technical submission (including any graphics or code snippets)?ௗ

From Technical Liaison:

There is not page-count limit, but from past experience, less than ten pages should be enough to describe:

Capability Statement: A one-pager that highlights your core competencies, past performance, di erentiators, and contact info.

Technical Proposal: Tailored to the scope of work, showing how you’ll meet the government’s needs.

Pricing Sheet: Transparent, itemized, and aligned with market rates.

11.ௗITOsௗ“Technical Information”: Do résumés and references count toward any page limit?ௗ no