Skip to content
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

Processing SICD files from G-EGD #457

Open
AmaralScientist opened this issue Jul 28, 2023 · 2 comments
Open

Processing SICD files from G-EGD #457

AmaralScientist opened this issue Jul 28, 2023 · 2 comments

Comments

@AmaralScientist
Copy link

Our group would like to process the SICD formatted files that are provided on the G-EGD platform into a georeferenced, orthorectified product. Is there a straightforward way to do this using SarPy? I can open the SICD files and view them. However, when I orthorectify a SICD file using the ortho helper, the resulting image does not align to Google Earth. What am I doing wrong?

@ghost
Copy link

ghost commented Aug 10, 2023

Hey there,

First and foremost, I completely understand where you're coming from. Handling SICD files and ensuring accurate georeferencing can be quite intricate. SarPy, as a potent Python library, is specifically tailored for such operations, and it's great that you're leveraging it.

From a technical standpoint, SarPy provides robust methods for orthorectifying SICD formatted files. However, a few nuances might be affecting the alignment with Google Earth:

1 - Coordinate System Alignment: One of the primary considerations is ensuring that the coordinate system or datum of the SICD files matches that of Google Earth, which typically operates on the WGS-84 system. Any misalignment between the two can lead to discrepancies in the final output.
2 - Projection Considerations: SarPy's orthorectification relies on intricate projection methods. The library is stringent about the shape, type, and properties of the data during this process. Any anomalies or inconsistencies in your SICD data might introduce errors during the projection phase.
3 - Vector Definitions: The library emphasizes specific vector definitions during the orthorectification process. It's crucial to ensure that these vectors are correctly defined, perpendicular where required, and not zero vectors.
4 - Geometry Objects Ordering: SarPy uses a specific lon/lat ordering for GeometryObjects. If this isn't adhered to, it might be a potential source of the misalignment.

Given these insights, here's what I'd suggest:

  • Start by meticulously reviewing the metadata of your SICD files. Verify that their coordinate system aligns seamlessly with Google Earth's expectations.
  • Examine the data you're feeding into SarPy's orthorectification routines. Ensure it adheres to all the library's prerequisites and is devoid of inconsistencies.
  • If you're employing specific projection or orthorectification methods within SarPy, revisit them. Ensure they are correctly applied. The library's documentation, particularly the 'ortho_methods.py' and 'projection_helper.py' modules, can provide valuable insights.

Best of luck, and hope this helps!

@utwade
Copy link
Contributor

utwade commented Aug 21, 2023

Are you using create_kmz to check for alignment in Google Earth? That is the most direct way to check whether the SICD is being projected correctly or not.

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

No branches or pull requests

2 participants