opera-adt / burst_db Goto Github PK
View Code? Open in Web Editor NEWBurst coverage database for OPERA products
License: Apache License 2.0
Burst coverage database for OPERA products
License: Apache License 2.0
Yes - I've already checked
With the options snap=50, margin=1000
, some of the bursts work alright when processed through COMPASS.
However, here's 3 dates of burst t012_024524_iw2
with that margin:
Checking into why this might happen, the README of the ESA burst database has the following validation table:
...each of the geocoded point obtained from the annotation files is
coupled to the corresponding point from the Burst ID map. For each couple of
points the absolute distance, the distance along range, and the distance along
azimuth are computed. The results of the validation are as follows:.
For the IW Burst ID map (validation over 6600 products):
Range [m] | Azimuth [m] | Absolute [m] | |
---|---|---|---|
Max | 633 | 2022 | 3190 |
Min | -302 | -3127 | 2 |
Mean | 196 | -484 | 960 |
STD | 81 | 930 | 553 |
MAD | 53 | 758 | 452 |
The key point: there was a -3127 difference between their burst database geometry and the actual location of one of the acquired bursts.
One fix might be to use 4000 for the default margin, as is in #2 .
No response
No response
Should be as simple as gdf_full.drop_duplicates(subset='burst_id_jpl', keep='first')
Yes - I've already checked
As you mentioned in readme, After downloading the "burst-db package", I can use "opera-db" right?
but there is not "opera-db.py" in burst-db package.
I expected [...]
1.
2.
3.
...
- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...
Yes - I've already checked
One of the points discussed in the PR #2 was about the across-track constraint of EPSG, which is to use the same map projection for the IW1/2/3 bursts on the same track. The reason behind this constraint is to make the along-track bursts more stitch-friendly (i.e. no reproduction necessary). One of the concerns that has been made was that it might cause the EPSG changes along-track to be less related to what it is across track.
One of the ways to investigate the influence of the EPSG constraint is to detect the number of EPSG changes along track from the DB generated with / without the constraint.
No response
No response
It's like that the displacement product is going to have a spacing of 30 meters. This means it's nice if the snap
used in setting the bounding box is some multiple of 30. That way, adjacent bursts will line up in an even multiple, rather than one burst intersecting at some fraction of a 30m pixel.
Thanks for reading my quetion.
I want to make sqlite for my sentinel-1 image
so I'm trying follow your steps
but I can not find where is build_database.py
The function in the title is to calculate the extent (bounding box) of the input burst as polygon. This function only takes the first polygon in the multi polygon input. This needs to be addressed especially for the burst (multi)polygons split on +/- 180 degree.
Yes - I've already checked
Yes - and alternatives don't suffice
The PR #8 includes land optimization for frame definition. It uses several reference shape files to identify the land area.
One of the reference data for the land area is Global Self-consistent, Hierarchical, High-resolution Geography (GSHHG) Database. This database includes Antarctica. based on grounding line boundary. However, in general glaciologists in Antarctica are interested not only grounded ice but also the ice ice shelf (downstream of the grounded ice that floating on, and flows into the ocean)
For OPERA project, using this reference data for Antarctica would suffice because the project does not cover Antartica. However, in case CSLC and COMPASS gets extended to Antarctica, the frame definition for this area might not be in a desired set up.
Therefore, the reference shape file for Antarctica needs to include ice shelf. It would be in lower priority than other tasks, but it needs to be in our TODO list.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.