Issues With Pleiades DEM Generation - Sensor Name

65 views
Skip to first unread message

Martim Gallo Proenca

unread,
Nov 20, 2023, 3:57:11 PM11/20/23
to Ames Stereo Pipeline Support
Hello There,

I'm quite new to stereo image processing and AMES, I've read the docs and this forum but didn't find anything related to my specific error. Was hoping to find some help.

I got access to a sample pleiades stereo pair and need to generate a DEM from it. I ran the parallel_stereo command passing the paths to the .TIF and DIM.XML files and got the following message.

Captura de Tela 2023-11-20 às 17.32.07 1.png

The message is the same when trying to do bundle adjustment

I've tried Editing the sensor name field on the XML files to PHR or PNEO, but the error is the same:
"Incorrect sensor name. Expected: PHR or PNEO sensor, but got: PHR"

From what i've read my XML file is an exact linescan model and should be more accurate than an RPC, so i imagine the correction must not be to convert my linescan file to an RPC model.

Thank you in advance for the help, and If i'm missing any other important information for the diagnosis please let me know

-Martim

David Shean

unread,
Nov 20, 2023, 4:33:28 PM11/20/23
to Martim Gallo Proenca, Ames Stereo Pipeline Support
Hi Martim,
It looks like the XML has PHR_ORTHO listed as the sensor.

Can you provide more information about the images you ordered (and product type or processing level)?  Are your images Level-1B “primary” products, or the “projected” products?  ASP expects the former.  The latter are projected onto a constant height above the ellipsoid, and each of input images in the pair/triplet uses a slightly different height (presumably the mean elevation of each image footprint), at least based on the PHR samples I’ve explored.

In this case, the PHR_ORTHO value makes me think that you have orthoimages, with terrain displacement removed using some external DEM, which means these images cannot be used for stereo.  Changing the sensor name in the XML will not solve the problem.

It’s important to order the correct product level (Level-1B in original sensor coordinates, after radiometric and geometric corrections) when the objective is stereo DEM production.  This issue continues to come up, and I’m curious about the guidance provided by sales rep at Airbus or other contacts who provided these products.  Some commercial stereo processing software (e.g., SOCET SET, ERDAS) supports the “projected" products, and in principle ASP can as well, but the quailty/accuracy of the resulting stereo DEM will be reduced, since we don’t have details on the interpolation used to go from “primary” to “projected” products.  I hope that they are willing to redeliver products you can use for stereo.

If you can share the XML, we can confirm the issue.
-David






--
David Shean
Civil and Environmental Engineering
University of Washington
https://www.ce.washington.edu/facultyfinder/david-shean 

201 More Hall, Box 352700
3760 E. Stevens Way NE
Seattle, WA 98195-2700
Office: (206) 543-3105, Wilcox Hall 265
Pronouns: he, him, his

On Nov 20, 2023, at 12:57 PM, Martim Gallo Proenca <mgallo...@gmail.com> wrote:

This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
See https://itconnect.uw.edu/email-tags for additional information. Please contact the UW-IT Service Center, he...@uw.edu 206.221.5000, for assistance.
Hello There,

I'm quite new to stereo image processing and AMES, I've read the docs and this forum but didn't find anything related to my specific error. Was hoping to find some help.

I got access to a sample pleiades stereo pair and need to generate a DEM from it. I ran the parallel_stereo command passing the paths to the .TIF and DIM.XML files and got the following message.

<Captura de Tela 2023-11-20 às 17.32.07 1.png>

The message is the same when trying to do bundle adjustment

I've tried Editing the sensor name field on the XML files to PHR or PNEO, but the error is the same:
"Incorrect sensor name. Expected: PHR or PNEO sensor, but got: PHR"

From what i've read my XML file is an exact linescan model and should be more accurate than an RPC, so i imagine the correction must not be to convert my linescan file to an RPC model.

Thank you in advance for the help, and If i'm missing any other important information for the diagnosis please let me know

-Martim

-- 
You received this message because you are subscribed to the Google Groups "Ames Stereo Pipeline Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ames-stereo-pipeline...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ames-stereo-pipeline-support/5882c275-260a-4a52-92df-ca04befb0cbdn%40googlegroups.com.

Martim Gallo Proenca

unread,
Nov 21, 2023, 1:17:10 PM11/21/23
to Ames Stereo Pipeline Support
Hello David, thank you for your quick reply.

I checked the image product info and indeed it is an Ortho Image... 
From what i've read from the pleiades product documentation it has even more processing done than the Projected level.
I will inform my image provider that the Ortho samples delivered are not fit for DEM generation via Stereo and request a Primary image. 

Thank you again!
- Martim

Oleg Alexandrov

unread,
Nov 21, 2023, 1:43:02 PM11/21/23
to Martim Gallo Proenca, Ames Stereo Pipeline Support
Good to know that this is the issue. I made mention of this in the doc and the error message.

Etienne Berthier

unread,
Nov 22, 2023, 1:45:03 AM11/22/23
to Ames Stereo Pipeline Support, Oleg Alexandrov
Dear colleagues,

Below are the options that we use to request production of Pléiades stereo images in the frame of the Pléiades Glacier Observatory project. 

Product resolution: Pléiades 50 cm B&W
Spectral bands combination: Bundle PAN+4-band MS
Geometric processing level: Primary
Radiometric processing level: Basic
Product and image format: DIMAP - JPEG 2000 Regular
Bit depth: 12 bits
Comments: TDI=10 (to avoid any saturation of the images over South-East slopes facing the Sun at acquisition time, will lead to "darker" images elsewhere)

We generally request a base-to-height ration between 0.3 and 0.6 (but this is more application specific so you may want to adapt that)

Best wishes,

Etienne


De: "Oleg Alexandrov" <oleg.al...@gmail.com>
À: "Martim Gallo Proenca" <mgallo...@gmail.com>
Cc: "Ames Stereo Pipeline Support" <ames-stereo-pi...@googlegroups.com>
Envoyé: Mardi 21 Novembre 2023 19:42:49
Objet: [MESSAGE MARQUE PUB]Re: Issues With Pleiades DEM Generation - Sensor Name

Reply all
Reply to author
Forward
0 new messages