-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Question] Is data available through the API the same as in the "qs.Crops" file? #38
Comments
I don't have information on exactly what files QuickStats queries vs the downloaded files. My assumption has been that the queries are made on database versions that are equal and may even directly import the downloadable files, or that the downloadable files are exported directly from the QuickStats database. But I don't find data for your query in either the downloaded data or via
Is this due to
I also get 0 records for I don't currently have a strong enough computer to load the entirety of the downloadable file, but in 50,000 records I find years only up to 2021. You may want to follow up directly with NASS on this question. The |
I can confirm that the downloadable file doesn't have any data after 2022, but I couldn't say why. I'm closing this issue but please let me know if something changes that I can incorporate into the |
Thanks @potterzot -- also contacted the staff at NASS: data for some crops is not available in the qs file for 2022, 2023, and 2024. The API is then the safest way to retrieve recent data. Appreciate your reply. |
The following works and returns the data for 2023 and 2024(if avail):
params <- list(commodity_desc = "CORN", year__GE = 2023, agg_level_desc = "AGRICULTURAL DISTRICT")
If I try to get the same data from the files at
[https://www.nass.usda.gov/datasets/
](https://www.nass.usda.gov/datasets/qs.crops_20240309.txt.gz)recent data does not appear to be available (>2022). Even though the docs suggest it should.
Is the API querying the same sources as the raw files? Or this is an expected result ?
The text was updated successfully, but these errors were encountered: