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
+64-13Lines changed: 64 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,38 +164,89 @@ In order to run **SatExtractor** we recommend to have a virtual env and a cloud
164
164
🔴🔴🔴
165
165
```diff
166
166
- WARNING!!!!:
167
-
Running SatExtractor will use your billable cloud provider services.
168
-
We strongly recommend testing it with a small region to see if everything is working ok.
167
+
Running SatExtractor will use your billable cloud provider services.
168
+
We strongly recommend testing it with a small region to see if everything is working ok.
169
169
Be sure you are running all your cloud provider services in the same region to avoid extra costs.
170
170
```
171
171
🔴🔴🔴
172
172
173
-
Once a cloud provider user is set and the package is installed you'll need to grab the geojson region you want (you can get it from the super-cool tool [geojson.io](geojson.io)) and change the config files.
173
+
Once a cloud provider user is set and the package is installed you'll need to grab the GeoJSON region you want (you can get it from the super-cool tool [geojson.io](http://geojson.io/)) and change the config files.
174
174
175
175
176
-
1. Save the region as `<your_region_name>.geojson` and store it in the `outputs` folder (you can change your output dir in the `config.yaml`)
177
-
2. Open the `config.yaml` and you'll see something like this:
178
-
179
-
<imgsrc="images/config.png"alt="Logo">
176
+
1. Choose a region name (eg `cordoba` below) and create an output directory for it:
177
+
```
178
+
mkdir output/cordoba
179
+
```
180
+
2. Save the region GeoJSON as `aoi.geojson` and store it in the folder you just created.
181
+
3. Open the `config.yaml` and you'll see something like this:
The important here is to set the `dataset_name` to `<your_region_name>`, define the `start_date` and `end_date` for your revisits, your `constellations` and the tasks to be run (you would want to run the `build` only one time and the comment it out.)
182
226
183
-
**Important**: the `token.json` contains the needed credentials to access you cloud provider. In this example case it contains the gcp credentials. You'll need to provide it.
227
+
**Important**: the `token.json` contains the needed credentials to access you cloud provider. In this example case it contains the gcp credentials. You can see instructions for getting it below in the [Authentication](#authentication) instructions.
184
228
185
229
3. Open the `cloud/<provider>.yaml` and add there your account info as in the default provided file.
186
230
(optional): you can choose different configurations by changing modules configs: `builder`, `stac`, `tiler`, `scheduler`, `preparer`, etc. There you can change things like patch_size, chunk_size.
187
231
188
232
4. Run `python src/satextractor/cli.py` and enjoy!
189
233
190
-
191
-
<palign="right">(<ahref="#top">back to top</a>)</p>
192
-
193
-
194
234
See the [open issues](https://github.com/FrontierDevelopmentLab/sat-extractor/issues) for a full list of proposed features (and known issues).
195
235
196
236
<p align="right">(<a href="#top">back to top</a>)</p>
197
237
198
238
239
+
## Authentication
240
+
### Google Cloud
241
+
To get the `token.json` for Google Cloud, the recommended approach is to create a service account:
242
+
1. Go to [Credentials](https://console.cloud.google.com/apis/credentials)
243
+
2. Click `Create Credentials` and choose `Service account`
244
+
3. Enter a name (e.g. `sat-extractor`) and click `Done` (you may also want to modify permissions and users)
245
+
4. Choose the account from the list and then to to the `Keys` tab
246
+
5. Click `Add key` -> `Create new key` -> `JSON` and save the file that gets downloaded
247
+
6. Rename to `token.json` and you're done!
248
+
249
+
You may also need to run `gcloud config set project your-proj-name` for `sat-extractor` to work properly.
199
250
200
251
<!-- CONTRIBUTING -->
201
252
## Contributing
@@ -231,4 +282,4 @@ Distributed under the BSD 2 License. See `LICENSE.txt` for more information.
231
282
</div>
232
283
233
284
234
-
This work is the result of the 2021 ESA Frontier Development Lab World Food Embeddings team. We are grateful to all organisers, mentors and sponsors for providing us this opportunity. We thank Google Cloud for providing computing and storage resources to complete this work.
285
+
This work is the result of the 2021 ESA Frontier Development Lab World Food Embeddings team. We are grateful to all organisers, mentors and sponsors for providing us this opportunity. We thank Google Cloud for providing computing and storage resources to complete this work.
0 commit comments