isce-framework / isce-framework/isce3

Accessing NISAR DEM

Open
#30 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
239
Forks
90
Avg merge
13d 1h
Merged PRs (30d)
5

Description

Hello, I'm trying to run ISCE3 example workflows but the nisar-dem bucket needs credentials:
https://github.com/isce-framework/isce3/blob/5e36b8a1b90d093128e84d46b2b63b3adf646981/python/packages/nisar/workflows/stage_dem.py#L16

The nisar-dem is also used for OPERA processing (cross-ref https://github.com/opera-adt/COMPASS/issues/216#issuecomment-1915216236)

As a workaround I'm assuming NISAR DEM is effectively identical to the publicly accessible Copernicus DEM (https://portal.opentopography.org/datasetMetadata?otCollectionID=OT.032021.4326.1) converted to ellipsoid heights (EPSG:9055+3855). The NISAR sample data https://nisar.jpl.nasa.gov/data/sample-data/ does include a small dem tile but unfortunately the CRS is listed as EPSG:4326 rather than a more specific 3D CRS.

To avoid potential discrepancies it would be great to just access nisar-dem, and it seems the intention is to make it public?
(https://github.com/isce-framework/isce3/issues/5#issuecomment-884536230)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked line in python/packages/nisar/workflows/stage_dem.py and trace how the workflow accesses the nisar-dem bucket. Review the referenced NISAR sample-data page and linked issue discussions to determine the intended public-access path; done means the workflow has a documented, supported way to access the required DEM without private credentials.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cloud, data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.