Intelligence-CustomerTechnicalSupport
2021-06-07 13:46:34 UTC
Hi all,
I hope my email finds you well
I would like to report you a convention issue with our SPOT6-7 RPC model.
Gdal has previously updated RPC model interpretation of Pléiades so that image coordinate normalized rn,cn = -1,-1 corresponds to r,c = 0,0 by subtracting 1 pixel to the offset value in row, column. The problem is that this interpretation was applicable to all Primary products (PHR and SPOT) while it shouldn't done for SPOT.
Regarding DIMAP and image file, there is no difference between SPOT and PHR. The pixel convention is center pixel for both
However regarding RPC :
For PHR, image coordinate normalized rn,cn = -1,-1 corresponds to the image coordinate r0,c0 = 1,1
For SPOT, image coordinate normalized rn,cn = -1,-1 corresponds to the image coordinate r0,c0 = 0,0 (c.f. http://geotiff.maptools.org/rpc_prop.html)
Could you handle this modification ? Or tell me who is the best contact to address this request ?
For information, here is the original discussion six years ago, when you implemented the fix for handling the PHR RPCs correctly: https://trac.osgeo.org/gdal/ticket/5993
I'm staying at your disposal for any further information if needed
Have a good day
Best regards
Géraldine
Géraldine LE PRIOL
Customer Technical Support
Customer Service &Technical Support - TCIFT1
Airbus Defence and Space
5, rue des Satellites, BP 14359
France - 31030 - Toulouse
E: ***@airbus.com<mailto:***@airbus.com>
www.intelligence-airbusds.com<http://www.intelligence-airbusds.com/>
[AIRBUS_D&S_3D_Blue_RGB-low]
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
I hope my email finds you well
I would like to report you a convention issue with our SPOT6-7 RPC model.
Gdal has previously updated RPC model interpretation of Pléiades so that image coordinate normalized rn,cn = -1,-1 corresponds to r,c = 0,0 by subtracting 1 pixel to the offset value in row, column. The problem is that this interpretation was applicable to all Primary products (PHR and SPOT) while it shouldn't done for SPOT.
Regarding DIMAP and image file, there is no difference between SPOT and PHR. The pixel convention is center pixel for both
However regarding RPC :
For PHR, image coordinate normalized rn,cn = -1,-1 corresponds to the image coordinate r0,c0 = 1,1
For SPOT, image coordinate normalized rn,cn = -1,-1 corresponds to the image coordinate r0,c0 = 0,0 (c.f. http://geotiff.maptools.org/rpc_prop.html)
Could you handle this modification ? Or tell me who is the best contact to address this request ?
For information, here is the original discussion six years ago, when you implemented the fix for handling the PHR RPCs correctly: https://trac.osgeo.org/gdal/ticket/5993
I'm staying at your disposal for any further information if needed
Have a good day
Best regards
Géraldine
Géraldine LE PRIOL
Customer Technical Support
Customer Service &Technical Support - TCIFT1
Airbus Defence and Space
5, rue des Satellites, BP 14359
France - 31030 - Toulouse
E: ***@airbus.com<mailto:***@airbus.com>
www.intelligence-airbusds.com<http://www.intelligence-airbusds.com/>
[AIRBUS_D&S_3D_Blue_RGB-low]
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.