Skip to content
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

explain how NAIPs are indexed on the S3 bucket #33

Closed
andrewljohnson opened this issue May 13, 2016 · 4 comments
Closed

explain how NAIPs are indexed on the S3 bucket #33

andrewljohnson opened this issue May 13, 2016 · 4 comments

Comments

@andrewljohnson
Copy link
Contributor

I don't understand how I can make an index of the NAIP bucket on S3. The parameters are as follows: ['md', '2013', '1m', 'rgbir', '38077']

I understand all the parameters but the last one... I assume that is some sort of grid or ordinal ID.

If I knew what the final parameter was, I could write a script to get training data from any state/year. Now it's limited to a certain place in Maryland, around Washington DC.

@brunosan
Copy link

AFAIK this is the FIPS code, as stated on the appendix [page 18] here...

@andrewljohnson
Copy link
Contributor Author

Thanks @brunosan 👍

@brunosan
Copy link

Btw, I noticed that at the linked USDA page on the wiki article you can get plain text codes, but I couldn't find the matching example above.

@andrewljohnson
Copy link
Contributor Author

The codes in the filenames were not matching up to FIPS as far as I could tell, so I was wondering what was up.

Maybe this is moot though. I think the NAIPs need to be downloaded to get exact geo information. I don't think even the FIPS code and other filename info could be mapped to a good bounds for each file.

I think I'll change the scripts to work with any given US state (plus year) for now... instead of trying to exactly geo-index the whole bucket. That should serve my needs for doing some geographically disparate analyses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants