You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,9 +97,12 @@ More information about these datasets can be found below
97
97
98
98
See these [notebooks](notebooks/tile_creation) to see how these tiles are generated and organized. Feel free to open a issue ticket or PR if there are modifications or new tilesets you would like to see.
99
99
100
-
# Dateline support
100
+
# Dateline/antimeridian support
101
101
102
-
None curently.
102
+
We support a single dateline crossing (crossing +/- 180 longitude) within `get_raster_from_tiles` using in-memory translation of tiles (same as [dem-stitcher](https://github.com/ACCESS-Cloud-Based-InSAR/dem-stitcher)'s functionality).
103
+
We "wrap" tiles across this dateline crossing.
104
+
We assume that the supplied bounds/extent overlap the standard lat/lon CRS grid i.e. longitudes between -/+ 180 longitude and are within -/+ 90 latitude, where a buffer around the dateline (longitude axis or $x$-axis).
105
+
Wrapping tiles around the North and South poles (i.e. at -/+ 90 latitude) is *not* supported (a different CRS is what's required) and an exception will be raised.
103
106
104
107
# Contributing
105
108
@@ -110,7 +113,7 @@ We welcome contributions to this open-source package. To do so:
110
113
3. Make your modifications in your own fork
111
114
4. Make a pull-request (PR) in this repo with the code in your fork and tag the repo owner or a relevant contributor.
112
115
113
-
We use `flake8` and associated linting packages to ensure some basic code quality (see the `environment.yml`). These will be checked for each commit in a PR. Try to write tests wherever possible.
116
+
We use `ruff` and associated linting packages to ensure some basic code quality (see the `environment.yml`). These will be checked for each commit in a PR. Try to write tests wherever possible.
0 commit comments