Commit 3c3c5b91 authored by Daniel Scheffler's avatar Daniel Scheffler
Browse files

Updated projection related documentation.


Signed-off-by: Daniel Scheffler's avatarDaniel Scheffler <danschef@gfz-potsdam.de>
parent 80b8c035
Pipeline #22194 failed with stage
in 4 minutes and 13 seconds
......@@ -539,8 +539,8 @@ class COREG(object):
raise RuntimeError(
'Input projections are not equal. Different projections are currently not supported. '
'Got %s / %s.' % (CRS.from_user_input(self.ref.prj).name,
CRS.from_user_input(self.shift.prj).name))
'Got %s vs. %s.' % (CRS.from_user_input(self.ref.prj).name,
CRS.from_user_input(self.shift.prj).name))
def _get_overlap_properties(self) -> None:
overlap_tmp = get_overlap_polygon(self.ref.poly, self.shift.poly, self.v)
......
......@@ -25,17 +25,21 @@ header file.
Supported projections
~~~~~~~~~~~~~~~~~~~~~
AROSICS provides full support for UTM projections and geographic coordinates. Providing support for other projections
is currently work in progress (see `here <https://git.gfz-potsdam.de/danschef/arosics/-/issues/37>`__ for the
status) and may lead to some incompatibities.
AROSICS was initially written with support for UTM and geographic coordinates only. Full support for any other
projection was added in version 1.4.0. However, make sure your input images have the same projection. Different
projections for the reference and target image are currently not supported.
AROSICS can also be applied to images without any projection and geocoding information. In this case, however,
the input images need to have the same pixel size and must cover more or less the same spatial area
(with a shift a few pixels at most).
Geographic overlap
~~~~~~~~~~~~~~~~~~
The input images must have a geographic overlap but clipping them to same geographical extent is NOT neccessary.
The image overlap area is automatically calculated. Thereby, no-data regions within the images are automatically
respected.
The input images must have a geographic overlap but clipping them to same geographical extent is NOT neccessary
The image overlap area is automatically calculated, given that your input images have valid geocoding and projection
information). Thereby, no-data regions within the images are automatically respected.
Spatial resolution
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment