-
Notifications
You must be signed in to change notification settings - Fork 95
Save final orders as order_name instead of order_id #995
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@aayushmalik you've described the situation well and it seems sensible to me. What you're looking for is much like this zip delivery feature that exists in the Orders API, but not Tasking API, right? https://developers.planet.com/apis/orders/delivery/#whole-order-zipping. |
@sgillies, thanks for sharing this. Actually not, this isn't what I would like to have. What you shared saves the files in following format
Which doesn't solve my problem as the parent folder is still named as I would want a single zip file which is saved like this
That is to say, a single file that contains everything pertaining to an order, and inside this zip file, I can have manifest.json instead of outside. And the name of the zip_file should be order_name. |
@aayushmalik ah, ok, got it. A completed order carries one or more pairs of download links and names (one for the manifest, the other(s) for the assets or zip files). Overriding the API-suggested names won't be difficult. I just now did a "single-archive" zip order and see that the manifest.json is included in it. Does that solve your manifest requirement?
|
Location link and name example:
|
Hi @sgillies, I am sorry I was not able to articulate my needs clearly, but I don't want a folder which is named as For example, currently after the whole operation is over, I get I just want Currently, I am doing this manually using Please let me know if you need further clarifications on this. |
@aayushmalik right, I get it. I'm making notes here for the developer who will implement the new feature and am pointing out that 1) "ABC_ORDER_ID/ABC_XYZ.zip" is the name suggested by the Orders API, and 2) we can override this name as needed instead of always accepting the suggestion as we do now. |
This ticket needs to be coordinated with #974 |
Current Problem
As a customer, I give each tasking order a unique name which is how I identify these orders in my organisation. For example, 1406_XY_XZ_LST, but when I download these fulfilled orders, the final folder name (or zipped file) is saved as order-id, which is good for Planet's systems, but not for me as a final user. This increases my workload, and the names of these folders are meaningless to my workflow.
My current workaround for this is reading the names of these folders (order-ids) one by one, make a GET request to https://developers.planet.com/apis/orders/reference/#tag/Orders/operation/getOrder, retrieve the order name from the response, and rename the folder. This is a cumbersome four-step process.
Proposed Solution
In this line
planet-client-python/planet/clients/orders.py
Line 233 in 74e8b77
planet-client-python/planet/clients/orders.py
Line 264 in 74e8b77
planet-client-python/planet/clients/orders.py
Line 257 in 74e8b77
Describe alternatives you've considered
Additional context
One of my customers complained that they can't use SDK because the final orders are saved in a folder/zipfile as order_ids, and they can't manually read each ID, copy it, search for it in Explorer, by opening each order one by one and comparing. Thus I created a script that could automate for them, but this creates additional load on Planet's servers, thus increasing cost. If we have SDK in-built solution, it will be good for the customer.
The text was updated successfully, but these errors were encountered: