Welcome!
Share and discuss the best content and new marketing ideas, build your professional profile and become a better marketer together.
This community is dedicated to Synthetic Aperture Radar (SAR) professionals and enthusiasts.
Ask questions, share insights, and discuss workflows using ICEYE data, SARPROZ, and related remote-sensing techniques.
Topics include flood mapping, burned forest analysis, ground deformation, water-level change, and other SAR applications.
Please stay on topic, be respectful, and support others by marking correct answers.
This community is for professionals, students, and researchers working with Synthetic Aperture Radar (SAR) data and related Earth Observation technologies.
You can ask questions about:
- Processing and analyzing ICEYE data (GRD, SLC, H5, etc.)
- Using SARPROZ, SNAP, Gamma, or QGIS for SAR applications
- Building workflows for flood mapping, forest burn detection, earthquake deformation, or water-level change
- Precision techniques involving GCPs, coregistration, or interferometry
- Integrating SAR data with other EO datasets or GIS systems
Before posting, please search for similar questions or topics — many issues may already have been discussed.
It’s also fine to answer your own question if you found a useful solution.
Please avoid questions that are off-topic (e.g., unrelated software, personal disputes, or non-technical discussions).
Vague or incomplete problem descriptions (always include data type, software version, and processing step).
Questions unrelated to SAR, ICEYE, or Earth Observation workflows.
Broad theoretical or opinion-based topics with no clear technical focus.
More over:
- Answers should not add or expand questions. Instead either edit the question or add a question comment.
- Answers should not comment other answers. Instead add a comment on the other answers.
- Answers shouldn't just point to other Questions. Instead add a question comment indication "Possible duplicate of...". However, it's ok to include links to other questions or answers providing relevant additional information.
- Answers shouldn't just provide a link a solution. Instead provide the solution description text in your answer, even if it's just a copy/paste. Links are welcome, but should be complementary to answer, referring sources or additional reading.
Unverified or speculative information.
Criticizing others’ questions — keep discussions constructive and professional.
Copy-pasting long code blocks or logs without explanation (summarize key parts instead).
To keep information accurate and consistent, experienced members with sufficient reputation can edit posts for clarity or formatting. All edits are tracked, and major content changes should always be discussed in comments first.