I recommend to remove the arguments args=(self.geocode_list, self.geocode_bbox) since it passes the arguments on the runGeocode.py of the RtcProc which prevents geocoding of the sigma nought product generated from the rtcApp.py. This could be added later if someone would incorporate the geocode_list and geocode_bbox on the runGeocode.py later.
* stackSentinel.py:using geopandas to calculate intersection between bbox and SAFE file coverage region
* stackSentinel.py:using geopandas and shapely package to calculate whether there are intersections between bbox and sentinel SAFE file. And remove import geopandas and shapely part into generate_geopolygon function
* stackSentinel.py: using shapely package to check whether bbox intersect with SAFE file coverage
* stackSentinel.py: using shapely package to check whether bbox intersect with SAFE file coverage
* stackSentinel.py:using shapely package to find whether bbox intersects with SAFE file
* stackSentinel.py:remove matplotlib DEBUG message#L14-L18
These global variables were instantiated in the image_sio.h header
and included into multiple translation units, violating ODR.
They are now marked as 'extern' and declared in a separate TU.
These duplicated names spanning translation units violate ODR.
They are only used within their corresponding .c files and thus
can be given static linkage.
* added a README.md for installation/user guide/procedures
* modified the cuDenseOffsets.py
* expose more options from the CUDA/C++ program
* add an option for varying gross offset input
* clarify the parameter definitions
* removed old SlcImage implementation and cublas dependence
* modified cuSincOversampler
* to be consistent with cpu version
* fix an issue when the extraction of the search window is not around the center
* added a debug mode to output intermediate results
* enable cuda error checking for both Debug/Release build types
* corrected the code to extract raw images when the correlation surface peak is close to edges
* Move utf-8 decoding step inside cython extension
The cython setters take python strings, but the getters return
python bytes, so this makes the types match up. I went with regular
python strings for the interface since they are more common at the
python level, so the encoding/decoding is now an implementation detail
of the cython extension.
Contributed by lijun99, rtburns-jpl, vbrancat, mzzhong
Ryan Burns
Ryan Burns
Bryan Marfito
Lijun Zhu
ranneylxr
Lijun Zhu
CunrenLiang
Minyan Zhong
CunrenLiang
Vincent Schut