Closed disbr007 closed 3 years ago
Thanks for reporting. AROSICS was initially written with full support for UTM and geographic coordinates (EPSG 4326). I just revised the underlying code in py_tools_ds a bit, also to get more compatibility with other projections. However, I guess there will also be some other places in the code that need to be revised to support any kind of projection.
I will look into that as soon as I have some spare time. In the meantime, I recommend to use UTM for your input data.
I created an issue in the GitLab issue tracker regarding the support of other projections: https://gitext.gfz-potsdam.de/danschef/arosics/-/issues/37
AROSICS 1.4.0 adds full support for any kind of projection. See https://git.gfz-potsdam.de/danschef/arosics/-/merge_requests/17.
I was able to run a global coregistration and write output that looked great. However, when attempting a local coregistration I am running into a pyproj issue, where during the creation of the CoRegPoints_table geodataframe the crs is not accepted by gpd.GeoDataFrame because of a pyproj issue.
I was able to follow the traceback and hard-code the line defining the crs (line 312 in Tie_Point_Grid) to what I know to be the crs I am using and it worked:
Here is the traceback when running it without any modifications:
I attempted to do an actual fix it but couldn't follow everything I needed to in py_tools_ds.