feedback

[sckott]

@dlebauer pinging you here instead of the usda repo

the readme has instructions https://github.com/sckott/usdaplantsapi#base-url

let me know what you think

I only have the original data you provided from this comment USDA/USDA-APIs#7 (comment)

[dlebauer]

@sckott this looks good, but I'd suggest using the file usda_plants_20160223.csv from a subsequent comment (USDA/USDA-APIs#7 (comment)). This is a copy of the database from Feb 23 2016; the other ones are five or more years old and the original content has not been preserved.

[sckott]

okay, will do

[dlebauer]

One other thought: the current documentation suggests that the search endpoint is currently used to define which fields are returned (as in select genus, species, accepted symbol from plants).

Another very useful feature would be to be able to subset analogous to a where clause like ... where genus = 'Acer'; etc.

In the development version of the BETYdb API this would be something like species?genus=Acer

[sckott]

Right, the last bullet point in the params header describes that https://github.com/sckott/usdaplantsapi#params - ability to search, that is, where statements

[dlebauer]

Got it. Thanks!
On Thu, Mar 17, 2016 at 12:52 PM Scott Chamberlain [email protected]
wrote:

Right, the last bullet point in the params header describes that
https://github.com/sckott/usdaplantsapi#params - ability to search, that
is, where statements

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#3 (comment)

[sckott]

API now using the newer dataset