-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orders requests to support source_type for basemaps #838
Comments
It's also worth explicitly mentioning that v2 dropped all support for the basemaps API (v1 had full support for basemaps). Orders does not replace the basemaps API and basemaps API functionality and metadata is still needed to use basemap data (e.g. listing a time series and otherwise getting the information you need to use the orders API). Similarly, NICFI customers cannot use the orders API for basemaps and must use the basemaps API for data download. Orders support for basemaps in the python client is not sufficient to actually work with basemap data. This client still needs to support the basemap API for basic information. |
Duplicate of #752 |
This is actually different from that one - this is for the |
Ah, missed that. Reopening |
Is your feature request related to a problem? Please describe.
Right now I can create a orders request for basemaps with the CLI, but I can't use
planet orders request
to help me form the request. I believe the situation is similar in the Python side - no 'helper' method.Describe the solution you'd like
planet orders request --source-type basemaps
or something similar, where it works with the relevant parameters. Likely will take a more concrete design proposal for exactly how it'll work, as it's a little bit different than standard catalog orders.Describe alternatives you've considered
Writing JSON by hand. It works, but it doesn't give the same level of convenience as the rest of the CLI/API.
Additional context
https://developers.planet.com/apis/orders/basemaps/ is our new documentation on basemaps. It'd be awesome if we could eventually upgrade those docs to be CLI or at least Python SDK calls instead of raw python requests stuff.
The text was updated successfully, but these errors were encountered: