@@ -189,6 +189,109 @@ Requesting a resource for a feature in a collection::
189
189
planet analytics collections features get target-quad <collection_id or subscription_id> <feature_id>
190
190
planet analytics collections features get source-image-info <collection_id or subscription_id> <feature_id>
191
191
192
+ Orders Examples
193
+ -----------------
194
+
195
+ List all recent orders for the authenticated user::
196
+
197
+ planet orders list
198
+
199
+ Get the status of a single order by Order ID::
200
+
201
+ planet orders get <order ID>
202
+
203
+ Note that you may want to parse the JSON that's output into a more human
204
+ readable format. The cli does not directly provide options for this, but is
205
+ meant to be easily interoperable with other tools, e.g. `jq
206
+ <https://stedolan.github.io/jq/> `_.
207
+
208
+ To cancel a running order by given order ID::
209
+
210
+ planet orders cancel <order ID>
211
+
212
+ To download an order to your local machine::
213
+
214
+ planet orders download <order ID>
215
+
216
+ Optionally, a `--dest <path to destination> ` flag may be specified too.
217
+
218
+ Creating an Order
219
+ ..................
220
+
221
+ The minimal command to create a simple order looks something like::
222
+
223
+ planet orders create --name "my order" \
224
+ --id 20151119_025740_0c74,20151119_025741_0c74 \
225
+ --bundle visual --item-type psscene3band
226
+
227
+ If no toolchain or delivery details are specified, a basic order with download
228
+ delivery will be placed for the requested bundle including the item id(s) specified.
229
+
230
+ Additionally, optional toolchain & delivery details can be provided on the
231
+ command line, e.g.:::
232
+
233
+ planet orders create --name "my order" \
234
+ --id 20151119_025740_0c74,20151119_025741_0c74 \
235
+ --bundle visual --item-type psscene3band --zip order --email
236
+
237
+ This places the same order as above, and will also provide a .zip archive
238
+ download link for the full order, as well as email notification.
239
+
240
+ The Orders API allows you to specify a toolchain of operations to be performed
241
+ on your order prior to download. To read more about tools & toolchains, visit
242
+ `the docs <https://developers.planet.com/docs/orders/tools-toolchains/ >`_ .
243
+
244
+ To add tool operations to your order, use the `--tools ` option to specify a
245
+ json-formatted file containing an array (list) of the desired tools an their
246
+ settings.
247
+
248
+ .. note :: The json-formatted file must be formatted as an array (enclosed in square brackets), even if only specifying a single tool
249
+
250
+ For example, to apply the 3 tools `TOAR -> Reproject -> Tile ` in sequence to an
251
+ order, you would create a `.json ` file similar to the following::
252
+
253
+ [
254
+ {
255
+ "toar": {
256
+ "scale_factor": 10000
257
+ }
258
+ },
259
+ {
260
+ "reproject": {
261
+ "projection": "WGS84",
262
+ "kernel": "cubic"
263
+ }
264
+ },
265
+ {
266
+ "tile": {
267
+ "tile_size": 1232,
268
+ "origin_x": -180,
269
+ "origin_y": -90,
270
+ "pixel_size": 0.000027056277056,
271
+ "name_template": "C1232_30_30_{tilex:04d}_{tiley:04d}"
272
+ }
273
+ }
274
+ ]
275
+
276
+
277
+ Similarly, you can also specify cloud delivery options on an order create
278
+ command with the `--cloudconfig <path to json file> ` option. In this case, the
279
+ json file should contain the required credentials for your desired cloud
280
+ storage destination, for example::
281
+
282
+ {
283
+ "amazon_s3":{
284
+ "bucket":"foo-bucket",
285
+ "aws_region":"us-east-2",
286
+ "aws_access_key_id":"",
287
+ "aws_secret_access_key":"",
288
+ "path_prefix":""
289
+ }
290
+
291
+ You can find complete documentation of Orders API cloud storage delivery and
292
+ required credentials `in the docs here
293
+ <https://developers.planet.com/docs/orders/ordering-delivery/#delivery-to-cloud-storage_1> `_.
294
+
192
295
Integration With Other Tools
193
296
----------------------------
194
297
0 commit comments