Eodms-api-client

Minor update

- Enforce upper limit of 6-decimal precision (sub-meter) for search geometries to reduce size of search URL string
- Suppress retry warnings associated with ReadTimeOuts when fetching granule metadata
- Test auth during `EodmsAPI` object instantiation to ensure the user can access the collection they want
- Add new warning logmessage about MultiPolygons since EODMS seems to freak out and return HTTP-500 when certain MultiPolygons are passed as search geometries

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.3...v1.2.4

Bugfix release
- For high-scene-count orders (i.e. 100) EODMS API returns HTTP:200 ("everything ok") but the response body is an error message in HTML, causing the JSON decoder to fail and no OrderIDs to be parsed by the client
- Tests with 50-scene orders seem to work fine so I reduced the `EODMS_SUBMIT_HARDLIMIT` constant to 50 from 100
- Implications for users: for large orders you will have more OrderIDs to keep track of - IMO not a big issue since one can use the `--order-ids` CLI option or pass a list of OrderIDs to `EodmsAPI.download` to get everything anyway

Full commit log to prior release: https://github.com/m9brady/eodms-api-client/compare/v1.2.2...v1.2.3

Bugfix release
- RADARSAT polarization options were not working as expected
- fix was to replace the `+` delimiter with spaces

Full commit log to prior release: https://github.com/m9brady/eodms-api-client/compare/v1.2.1...v1.2.2

- new classattr `EodmsAPI.available_params` to show the user what query parameters are supported/available for the given EODMS collection
- ideally I would scrape the parameters from EODMS itself but the way I use query params in this package makes it a little tricky
- A few tweaks to logging messages

Full commit log to prior release: https://github.com/m9brady/eodms-api-client/compare/v1.2.0...v1.2.1

Check-order-status-by-`orderId` has returned 🙌

Removed the "look-back X days" bandaid

Querying: ✅
Ordering: ✅
- RCM: Single-item order took a few minutes
- RS2: Single-item order took a bit more but under 10 minutes

Downloading: ✅

Full Changelog: https://github.com/m9brady/eodms-api-client/compare/v1.1.5...v1.2.0

**Not-quite-a-bugfix bugfix release**

- noticed that there are some new parameters in order to get more than 100 results back from the order endpoint
- came across it in the official client: https://github.com/eodms-sgdot/py-eodms-rapi/blob/a514c07182713f265211c7996a2a4e44c3b719ec/eodms_rapi/eodms.py#L1827-L1876

- as it stands currently, this package is in a "working" state:
- Querying: ✅
- Ordering: ✅ _API orders have seemingly begun to be processed_
- Downloading: ✅ _By default, the downloader looks back 7 days with a limit of 1000 images_
- the user can modify this behaviour by providing a different value to `days_to_look_back` in the `EodmsAPI.download` call
- relevant lines are here: https://github.com/m9brady/eodms-api-client/blob/59bcd1263f40a419c42326c7f0fe7fd4c485b73a/eodms_api_client/eodms.py#L337-L344

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.1.4...v1.1.5