Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Daniel Scheffler
arosics
Commits
3c3c5b91
Commit
3c3c5b91
authored
Apr 23, 2021
by
Daniel Scheffler
Browse files
Updated projection related documentation.
Signed-off-by:
Daniel Scheffler
<
danschef@gfz-potsdam.de
>
parent
80b8c035
Pipeline
#22194
failed with stage
in 4 minutes and 13 seconds
Changes
2
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
arosics/CoReg.py
View file @
3c3c5b91
...
@@ -539,8 +539,8 @@ class COREG(object):
...
@@ -539,8 +539,8 @@ class COREG(object):
raise
RuntimeError
(
raise
RuntimeError
(
'Input projections are not equal. Different projections are currently not supported. '
'Input projections are not equal. Different projections are currently not supported. '
'Got %s
/
%s.'
%
(
CRS
.
from_user_input
(
self
.
ref
.
prj
).
name
,
'Got %s
vs.
%s.'
%
(
CRS
.
from_user_input
(
self
.
ref
.
prj
).
name
,
CRS
.
from_user_input
(
self
.
shift
.
prj
).
name
))
CRS
.
from_user_input
(
self
.
shift
.
prj
).
name
))
def
_get_overlap_properties
(
self
)
->
None
:
def
_get_overlap_properties
(
self
)
->
None
:
overlap_tmp
=
get_overlap_polygon
(
self
.
ref
.
poly
,
self
.
shift
.
poly
,
self
.
v
)
overlap_tmp
=
get_overlap_polygon
(
self
.
ref
.
poly
,
self
.
shift
.
poly
,
self
.
v
)
...
...
docs/usage/input_data_requirements.rst
View file @
3c3c5b91
...
@@ -25,17 +25,21 @@ header file.
...
@@ -25,17 +25,21 @@ header file.
Supported projections
Supported projections
~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~
AROSICS provides full support for UTM projections and geographic coordinates. Providing support for other projections
AROSICS was initially written with support for UTM and geographic coordinates only. Full support for any other
is currently work in progress (see `here <https://git.gfz-potsdam.de/danschef/arosics/-/issues/37>`__ for the
projection was added in version 1.4.0. However, make sure your input images have the same projection. Different
status) and may lead to some incompatibities.
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
Geographic overlap
~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~
The input images must have a geographic overlap but clipping them to same geographical extent is NOT neccessary
.
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
The image overlap area is automatically calculated
, given that your input images have valid geocoding and projection
respected.
information). Thereby, no-data regions within the images are automatically
respected.
Spatial resolution
Spatial resolution
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment