Closed drewbo closed 9 years ago
@drewbo - I added info to the api.search
docstring, and included an example in the documentation.
Additional info is at https://github.com/mapbox/usgs/issues/16#issuecomment-89053631
The where
parameter is non-intuitive as it depends on knowing some wonky codes associated with each queryable field. The CLI abstracts the need to know these codes, though it does assume you know which fields are queryable. This comes at the cost of an additional request to the dataset-fields
endpoint, something that I'd like to leave out when using api.search
.
Awesome. Thanks a bunch; confusing codes but the additions and examples are really helpful.
Cool. Let me know if you can think of a way to make it more intuitive. One thought, was to store a mapping of codes to fields within the package, but I worry that field codes are not static.
Not sure how to search using additional filtering parameters (both syntax and which parameters can be queried on):