podaac-l2ss-py 3.3.3__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- podaac_l2ss_py-3.3.3/LICENSE +201 -0
- podaac_l2ss_py-3.3.3/PKG-INFO +163 -0
- podaac_l2ss_py-3.3.3/README.md +131 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/__init__.py +11 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/datatree_subset.py +1118 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/dimension_cleanup.py +101 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/run_subsetter.py +149 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/subset.py +594 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/subset_harmony.py +329 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/tree_time_converting.py +153 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/coordinate_utils.py +363 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/file_utils.py +148 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/hdf_utils.py +265 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/mask_utils.py +83 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/metadata_utils.py +384 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/spatial_utils.py +173 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/time_utils.py +242 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/utils/variables_utils.py +123 -0
- podaac_l2ss_py-3.3.3/podaac/subsetter/vertical_subset.py +219 -0
- podaac_l2ss_py-3.3.3/pyproject.toml +90 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2025 California Institute of Technology
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,163 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: podaac-l2ss-py
|
|
3
|
+
Version: 3.3.3
|
|
4
|
+
Summary: L2 Subsetter Service
|
|
5
|
+
License: Apache-2.0
|
|
6
|
+
License-File: LICENSE
|
|
7
|
+
Author: podaac-tva
|
|
8
|
+
Author-email: podaac-tva@jpl.nasa.gov
|
|
9
|
+
Requires-Python: >=3.12,<4.0
|
|
10
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
15
|
+
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|
|
16
|
+
Provides-Extra: harmony
|
|
17
|
+
Requires-Dist: Shapely (>=2.0.6,<3.0.0)
|
|
18
|
+
Requires-Dist: cf-xarray
|
|
19
|
+
Requires-Dist: geopandas (>=1.0.1,<2.0.0)
|
|
20
|
+
Requires-Dist: h5py (>=3.6.0,<4.0.0)
|
|
21
|
+
Requires-Dist: harmony-service-lib (>=3.0.0,<4.0.0) ; extra == "harmony"
|
|
22
|
+
Requires-Dist: importlib-metadata (>=9.0.0,<10.0.0)
|
|
23
|
+
Requires-Dist: julian (>=0.14,<0.15)
|
|
24
|
+
Requires-Dist: netCDF4 (>=1.5,<2.0)
|
|
25
|
+
Requires-Dist: numpy (>=2.2.4,<3.0.0)
|
|
26
|
+
Requires-Dist: pandas (==2.3.3)
|
|
27
|
+
Requires-Dist: pystac (>=1.10.1,<2.0.0) ; extra == "harmony"
|
|
28
|
+
Requires-Dist: xarray[parallel] (<=2025.1.0)
|
|
29
|
+
Project-URL: Repository, https://github.com/podaac/l2ss-py
|
|
30
|
+
Description-Content-Type: text/markdown
|
|
31
|
+
|
|
32
|
+
# l2ss-py
|
|
33
|
+
|
|
34
|
+
[](https://sonarcloud.io/dashboard?id=podaac_l2ss-py)
|
|
35
|
+
develop: [](https://github.com/podaac/l2ss-py/actions/workflows/build-pipeline.yml)
|
|
36
|
+
main: [](https://github.com/podaac/l2ss-py/actions/workflows/build-pipeline.yml)
|
|
37
|
+
|
|
38
|
+
Harmony service for subsetting L2 data. l2ss-py supports:
|
|
39
|
+
|
|
40
|
+
- Spatial subsetting
|
|
41
|
+
- Bounding box
|
|
42
|
+
- Shapefile subsetting
|
|
43
|
+
- GeoJSON subsetting
|
|
44
|
+
- Temporal subsetting
|
|
45
|
+
- Variable subsetting
|
|
46
|
+
- Vertical subsetting
|
|
47
|
+
|
|
48
|
+
If you would like to contribute to l2ss-py, refer to the [contribution document](CONTRIBUTING.md).
|
|
49
|
+
|
|
50
|
+
## Initial setup, with poetry
|
|
51
|
+
|
|
52
|
+
1. Follow the instructions for installing `poetry` [here](https://python-poetry.org/docs/).
|
|
53
|
+
2. Install l2ss-py, with its dependencies, by running the following from the repository directory:
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
poetry install
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
***Note:*** l2ss-py can be installed as above and run without any dependency on `harmony`.
|
|
60
|
+
However, to additionally test the harmony adapter layer,
|
|
61
|
+
extra dependencies can be installed with `poetry install -E harmony`.
|
|
62
|
+
|
|
63
|
+
## How to test l2ss-py locally
|
|
64
|
+
|
|
65
|
+
### Unit tests
|
|
66
|
+
|
|
67
|
+
There are comprehensive unit tests for l2ss-py. The tests can be run as follows:
|
|
68
|
+
|
|
69
|
+
```
|
|
70
|
+
poetry run pytest -m "not aws and not integration" tests/
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
You can generate coverage reports as follows:
|
|
74
|
+
|
|
75
|
+
```
|
|
76
|
+
poetry run pytest --junitxml=build/reports/pytest.xml --cov=podaac/ --cov-report=html -m "not aws and not integration" tests/
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
***Note:*** The majority of the tests execute core functionality of l2ss-py without ever interacting with the harmony python modules.
|
|
80
|
+
The `test_subset_harmony` tests, however, are explicitly for testing the harmony adapter layer
|
|
81
|
+
and do require the harmony optional dependencies be installed,
|
|
82
|
+
as described above with the `-E harmony` argument.
|
|
83
|
+
|
|
84
|
+
### l2ss-py script
|
|
85
|
+
|
|
86
|
+
You can run l2ss-py on a single granule without using Harmony. In order
|
|
87
|
+
to run this, the l2ss-py package must be installed in your current
|
|
88
|
+
Python interpreter
|
|
89
|
+
|
|
90
|
+
```
|
|
91
|
+
$ l2ss-py --help
|
|
92
|
+
usage: l2ss-py [-h] [--bbox BBOX BBOX BBOX BBOX] [--variables VARIABLES [VARIABLES ...]] [--min-time MIN_TIME] [--max-time MAX_TIME] [--cut] [--shapefile SHAPEFILE] [--pixel_subset] [--vertical-var VERTICAL_VAR] [--vertical-min VERTICAL_MIN] [--vertical-max VERTICAL_MAX]
|
|
93
|
+
input_file output_file
|
|
94
|
+
|
|
95
|
+
Run l2ss-py
|
|
96
|
+
|
|
97
|
+
positional arguments:
|
|
98
|
+
input_file File to subset
|
|
99
|
+
output_file Output file
|
|
100
|
+
|
|
101
|
+
options:
|
|
102
|
+
-h, --help show this help message and exit
|
|
103
|
+
--bbox BBOX BBOX BBOX BBOX
|
|
104
|
+
Bounding box in the form min_lon min_lat max_lon max_lat
|
|
105
|
+
--variables VARIABLES [VARIABLES ...]
|
|
106
|
+
Variables, only include if variable subset is desired. Should be a space separated list of variable names e.g. sst wind_dir sst_error ...
|
|
107
|
+
--min-time MIN_TIME Min time. Should be ISO-8601 format. Only include if temporal subset is desired.
|
|
108
|
+
--max-time MAX_TIME Max time. Should be ISO-8601 format. Only include if temporal subset is desired.
|
|
109
|
+
--cut If provided, scanline will be cut
|
|
110
|
+
--shapefile SHAPEFILE
|
|
111
|
+
Path to either shapefile or geojson file used to subset the provided input granule
|
|
112
|
+
--pixel_subset To pixel cut based the lon lat on the bounding box
|
|
113
|
+
--vertical-var VERTICAL_VAR
|
|
114
|
+
Name of the vertical variable to subset by (e.g., depth, altitude)
|
|
115
|
+
--vertical-min VERTICAL_MIN
|
|
116
|
+
Minimum value for vertical subsetting (inclusive)
|
|
117
|
+
--vertical-max VERTICAL_MAX
|
|
118
|
+
Maximum value for vertical subsetting (inclusive)
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
#### Additional subsetting options
|
|
122
|
+
|
|
123
|
+
The following options are also recorded in the output file's metadata history for provenance and reproducibility:
|
|
124
|
+
- `--min-time` and `--max-time` (temporal subsetting)
|
|
125
|
+
- `--variables` (variable subsetting)
|
|
126
|
+
- `--vertical-var`, `--vertical-min`, `--vertical-max` (vertical subsetting)
|
|
127
|
+
- `--cut`, `--pixel_subset`, `--shapefile`, and `--bbox` (spatial subsetting)
|
|
128
|
+
|
|
129
|
+
All subsetting parameters used in a run are included in the output file's `history` and `history_json` attributes.
|
|
130
|
+
|
|
131
|
+
For example:
|
|
132
|
+
|
|
133
|
+
```
|
|
134
|
+
l2ss-py /path/to/input.nc /path/to/output.nc --bbox -50 -10 50 10 --variables wind_speed wind_dir ice_age time --min-time '2015-07-02T09:00:00' --max-time '2015-07-02T10:00:00' --cut --vertical-var depth --vertical-min 0 --vertical-max 100
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
An addition to providing a bounding box, spatial subsetting can be achieved by passing in a shapefile or a geojson file.
|
|
138
|
+
|
|
139
|
+
```shell script
|
|
140
|
+
poetry run l2ss-py /path/to/input.nc /path/to/output.nc --shapefile /path/to/test.shp
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
or
|
|
144
|
+
|
|
145
|
+
```shell script
|
|
146
|
+
poetry run l2ss-py /path/to/input.nc /path/to/output.nc --shapefile /path/to/test.geojson
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
### Running Harmony locally
|
|
150
|
+
|
|
151
|
+
In order to fully test l2ss-py with Harmony, you can run Harmony locally. This requires the data exists in UAT Earthdata Cloud.
|
|
152
|
+
|
|
153
|
+
1. Set up local Harmony instance. Instructions [here](https://github.com/nasa/harmony#Quick-Start)
|
|
154
|
+
2. Add concept ID for your data to [services.yml](https://github.com/nasa/harmony/blob/main/config/services.yml)
|
|
155
|
+
3. Execute a local Harmony l2ss-py request. For example:
|
|
156
|
+
```
|
|
157
|
+
localhost:3000/YOUR_COLLECTION_ID/ogc-api-coverages/1.0.0/collections/all/coverage/rangeset?format=application%2Fx-netcdf4&subset=lat(-10%3A10)&subset=lon(-10%3A10)&maxResults=2
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
## NASA EOSDIS Integration
|
|
161
|
+
|
|
162
|
+
Detailed instructions for integrating with EOSDIS can be found [here](EOSDISIntegrations.md).
|
|
163
|
+
|
|
@@ -0,0 +1,131 @@
|
|
|
1
|
+
# l2ss-py
|
|
2
|
+
|
|
3
|
+
[](https://sonarcloud.io/dashboard?id=podaac_l2ss-py)
|
|
4
|
+
develop: [](https://github.com/podaac/l2ss-py/actions/workflows/build-pipeline.yml)
|
|
5
|
+
main: [](https://github.com/podaac/l2ss-py/actions/workflows/build-pipeline.yml)
|
|
6
|
+
|
|
7
|
+
Harmony service for subsetting L2 data. l2ss-py supports:
|
|
8
|
+
|
|
9
|
+
- Spatial subsetting
|
|
10
|
+
- Bounding box
|
|
11
|
+
- Shapefile subsetting
|
|
12
|
+
- GeoJSON subsetting
|
|
13
|
+
- Temporal subsetting
|
|
14
|
+
- Variable subsetting
|
|
15
|
+
- Vertical subsetting
|
|
16
|
+
|
|
17
|
+
If you would like to contribute to l2ss-py, refer to the [contribution document](CONTRIBUTING.md).
|
|
18
|
+
|
|
19
|
+
## Initial setup, with poetry
|
|
20
|
+
|
|
21
|
+
1. Follow the instructions for installing `poetry` [here](https://python-poetry.org/docs/).
|
|
22
|
+
2. Install l2ss-py, with its dependencies, by running the following from the repository directory:
|
|
23
|
+
|
|
24
|
+
```
|
|
25
|
+
poetry install
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
***Note:*** l2ss-py can be installed as above and run without any dependency on `harmony`.
|
|
29
|
+
However, to additionally test the harmony adapter layer,
|
|
30
|
+
extra dependencies can be installed with `poetry install -E harmony`.
|
|
31
|
+
|
|
32
|
+
## How to test l2ss-py locally
|
|
33
|
+
|
|
34
|
+
### Unit tests
|
|
35
|
+
|
|
36
|
+
There are comprehensive unit tests for l2ss-py. The tests can be run as follows:
|
|
37
|
+
|
|
38
|
+
```
|
|
39
|
+
poetry run pytest -m "not aws and not integration" tests/
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
You can generate coverage reports as follows:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
poetry run pytest --junitxml=build/reports/pytest.xml --cov=podaac/ --cov-report=html -m "not aws and not integration" tests/
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
***Note:*** The majority of the tests execute core functionality of l2ss-py without ever interacting with the harmony python modules.
|
|
49
|
+
The `test_subset_harmony` tests, however, are explicitly for testing the harmony adapter layer
|
|
50
|
+
and do require the harmony optional dependencies be installed,
|
|
51
|
+
as described above with the `-E harmony` argument.
|
|
52
|
+
|
|
53
|
+
### l2ss-py script
|
|
54
|
+
|
|
55
|
+
You can run l2ss-py on a single granule without using Harmony. In order
|
|
56
|
+
to run this, the l2ss-py package must be installed in your current
|
|
57
|
+
Python interpreter
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
$ l2ss-py --help
|
|
61
|
+
usage: l2ss-py [-h] [--bbox BBOX BBOX BBOX BBOX] [--variables VARIABLES [VARIABLES ...]] [--min-time MIN_TIME] [--max-time MAX_TIME] [--cut] [--shapefile SHAPEFILE] [--pixel_subset] [--vertical-var VERTICAL_VAR] [--vertical-min VERTICAL_MIN] [--vertical-max VERTICAL_MAX]
|
|
62
|
+
input_file output_file
|
|
63
|
+
|
|
64
|
+
Run l2ss-py
|
|
65
|
+
|
|
66
|
+
positional arguments:
|
|
67
|
+
input_file File to subset
|
|
68
|
+
output_file Output file
|
|
69
|
+
|
|
70
|
+
options:
|
|
71
|
+
-h, --help show this help message and exit
|
|
72
|
+
--bbox BBOX BBOX BBOX BBOX
|
|
73
|
+
Bounding box in the form min_lon min_lat max_lon max_lat
|
|
74
|
+
--variables VARIABLES [VARIABLES ...]
|
|
75
|
+
Variables, only include if variable subset is desired. Should be a space separated list of variable names e.g. sst wind_dir sst_error ...
|
|
76
|
+
--min-time MIN_TIME Min time. Should be ISO-8601 format. Only include if temporal subset is desired.
|
|
77
|
+
--max-time MAX_TIME Max time. Should be ISO-8601 format. Only include if temporal subset is desired.
|
|
78
|
+
--cut If provided, scanline will be cut
|
|
79
|
+
--shapefile SHAPEFILE
|
|
80
|
+
Path to either shapefile or geojson file used to subset the provided input granule
|
|
81
|
+
--pixel_subset To pixel cut based the lon lat on the bounding box
|
|
82
|
+
--vertical-var VERTICAL_VAR
|
|
83
|
+
Name of the vertical variable to subset by (e.g., depth, altitude)
|
|
84
|
+
--vertical-min VERTICAL_MIN
|
|
85
|
+
Minimum value for vertical subsetting (inclusive)
|
|
86
|
+
--vertical-max VERTICAL_MAX
|
|
87
|
+
Maximum value for vertical subsetting (inclusive)
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
#### Additional subsetting options
|
|
91
|
+
|
|
92
|
+
The following options are also recorded in the output file's metadata history for provenance and reproducibility:
|
|
93
|
+
- `--min-time` and `--max-time` (temporal subsetting)
|
|
94
|
+
- `--variables` (variable subsetting)
|
|
95
|
+
- `--vertical-var`, `--vertical-min`, `--vertical-max` (vertical subsetting)
|
|
96
|
+
- `--cut`, `--pixel_subset`, `--shapefile`, and `--bbox` (spatial subsetting)
|
|
97
|
+
|
|
98
|
+
All subsetting parameters used in a run are included in the output file's `history` and `history_json` attributes.
|
|
99
|
+
|
|
100
|
+
For example:
|
|
101
|
+
|
|
102
|
+
```
|
|
103
|
+
l2ss-py /path/to/input.nc /path/to/output.nc --bbox -50 -10 50 10 --variables wind_speed wind_dir ice_age time --min-time '2015-07-02T09:00:00' --max-time '2015-07-02T10:00:00' --cut --vertical-var depth --vertical-min 0 --vertical-max 100
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
An addition to providing a bounding box, spatial subsetting can be achieved by passing in a shapefile or a geojson file.
|
|
107
|
+
|
|
108
|
+
```shell script
|
|
109
|
+
poetry run l2ss-py /path/to/input.nc /path/to/output.nc --shapefile /path/to/test.shp
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
or
|
|
113
|
+
|
|
114
|
+
```shell script
|
|
115
|
+
poetry run l2ss-py /path/to/input.nc /path/to/output.nc --shapefile /path/to/test.geojson
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
### Running Harmony locally
|
|
119
|
+
|
|
120
|
+
In order to fully test l2ss-py with Harmony, you can run Harmony locally. This requires the data exists in UAT Earthdata Cloud.
|
|
121
|
+
|
|
122
|
+
1. Set up local Harmony instance. Instructions [here](https://github.com/nasa/harmony#Quick-Start)
|
|
123
|
+
2. Add concept ID for your data to [services.yml](https://github.com/nasa/harmony/blob/main/config/services.yml)
|
|
124
|
+
3. Execute a local Harmony l2ss-py request. For example:
|
|
125
|
+
```
|
|
126
|
+
localhost:3000/YOUR_COLLECTION_ID/ogc-api-coverages/1.0.0/collections/all/coverage/rangeset?format=application%2Fx-netcdf4&subset=lat(-10%3A10)&subset=lon(-10%3A10)&maxResults=2
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
## NASA EOSDIS Integration
|
|
130
|
+
|
|
131
|
+
Detailed instructions for integrating with EOSDIS can be found [here](EOSDISIntegrations.md).
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
# Copyright 2019, by the California Institute of Technology.
|
|
2
|
+
# ALL RIGHTS RESERVED. United States Government Sponsorship acknowledged.
|
|
3
|
+
# Any commercial use must be negotiated with the Office of Technology
|
|
4
|
+
# Transfer at the California Institute of Technology.
|
|
5
|
+
#
|
|
6
|
+
# This software may be subject to U.S. export control laws. By accepting
|
|
7
|
+
# this software, the user agrees to comply with all applicable U.S. export
|
|
8
|
+
# laws and regulations. User has the responsibility to obtain export
|
|
9
|
+
# licenses, or other export authority as may be required before exporting
|
|
10
|
+
# such information to foreign countries or providing access to foreign
|
|
11
|
+
# persons.
|