[GRASS-dev] [SoC] Week 12 Final Report: GRASS GIS Locations from Public Data

*Project Title:* GRASS GIS Locations from Public Data *Organization:* Google Summer of Code 2017 Open Source Geospatial Foundation (OSGeo) GRASS GIS *Abstract:* r.in.usgs is an add-on module for GRASS GIS that greatly simplifies the process of downloading and using USGS raster datasets. *Pre-GSo

[GRASS-dev] [SoC] Week 11 Report: GRASS GIS Locations from Public Data

WEEK 11: AUGUST 07 - AUGUST 11 GRASS GIS Locations from Public Data ACCOMPLISHED - Module completely functional for NED, NLCD data [3] - Created hard-coded data dictionaries for NED, NLCD, NAIP, UStopo datasets [1] - Implement download syntax and clean-up function for individual uncompressed tiles

[GRASS-dev] [SoC] Week 10 Report: GRASS GIS Locations from Public Data

WEEK 10: JULY 31 - AUGUST 04 GRASS GIS Locations from Public Data ACCOMPLISHED - Planned r.in.usgs scope and functionality with mentors - Created dynamic data-dictionary generator from API query for available USGS data products[1] - Began working on NLCD download configuration and formatting[1][2]

[GRASS-dev] [SoC] Week 09 Report: GRASS GIS Locations from Public Data

WEEK 09: JULY 24 - JULY 28 GRASS GIS Locations from Public Data ACCOMPLISHED - Refined r.in.usgsned clean-up, cache, and zip detection code [1] - Reviewed and completed r.in.usgsned module [2] - Began converting r.in.usgsned into r.in.usgs [3] - Began creating hardcoded USGS data dictionaries - D

[GRASS-dev] [SoC] Week 08 Report: GRASS GIS Locations from Public Data

WEEK 08: JULY 17 - JULY 21 GRASS GIS Locations from Public Data Zechariah Krautwurst ACCOMPLISHED - UNAVAILABLE NEXT WEEK - Review and complete r.in.usgsned - Begin converting r.in.usgsned into r.in.usgs - Create hardcoded USGS data dictionaries - Continue working on dynamic dictionaries

[GRASS-dev] [SoC] Week 07 Report: GRASS GIS Locations from Public Data

GRASS GIS Locations from Public Data Zechariah Krautwurst WEEK 07: JULY 10 - JULY 14 ACCOMPLISHED - Made significant changes to error handling to improve clean-up functionality, script crashes, and several other structural changes[1] - Implemented new method of pulling .img files from zip

[GRASS-dev] [SoC] GSoC Week 06 Report: GRASS Locations from Public Data

WEEK 06: JULY 03 - JULY 07 GRASS GIS Locations from Public Data Zechariah Krautwurst ACCOMPLISHED - Added functionality to handle unique formatting across multiple NED source dates. [1] - Created dynamic data dictionary for all USGS data sources from TNM API GET request [not pushed to repo

[GRASS-dev] [SoC] GSoC Week 05 Report: GRASS Locations from Public Data

WEEK 05: JUNE 26 - JUNE 30 GRASS GIS Locations from Public Data[1][2] Zechariah Krautwurst ACCOMPLISHED - Refined GUI options and flags[3] - Added GRASS messages, exits, and error handling[3][5] - Created "i" flag information report for module[4] - Converted 'requests' module

[GRASS-dev] Week 04: GRASS GIS Locations from Public Data

WEEK 04: JUNE 19 - JUNE 23 GRASS GIS Locations from Public Data Zechariah Krautwurst ACCOMPLISHED - Developed GRASS GUI through script flags and options - Revised script to integrate dynamic paths and user input - Improved SRS translation - Began creating format for further USGS data selection

[GRASS-dev] Week 03 Report: GRASS GIS Locations from Public Data

WEEK 03: JUNE 11 - JUNE 17 GRASS GIS Locations from Public Data [1] Zechariah Krautwurst ACCOMPLISHED - Worked through different methods of importing and processing NED data with GDAL's vsizip/vsicurl, TNM API, python requests lib, urllib2 - Wrote DRAFT version of r.in.usgsned python script

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

Forgot to include GRASS-dev on this. Keep the good ideas coming! On Mon, Jun 12, 2017 at 8:49 AM, Zechariah Krautwurst wrote: > Moritz, > > Thank you for your feedback. > > >> IMHO, I think it would be better if we avoided additional outside >> dependencies as muc

[GRASS-dev] Week 02 Report: GRASS Locations from Public Data

WEEK 02 REPORT: JUNE 05 - JUNE 09 GRASS GIS Locations from Public Data [1] Zechariah Krautwurst ACCOMPLISHED - Reviewed Python scripting for GRASS documentation and existing GRASS data import modules - Wrote SRTM 30 download script using Python Elevation library and GRASS output - Researched USGS

[GRASS-dev] [SoC] Week 01 Report - Locations from Public Data

Hello All, WEEK 01 REPORT: MAY 30 - JUNE 02 GRASS GIS Locations from Public Data [1] Zechariah Krautwurst ACCOMPLISHED: - Mentor meetings - Refined project scope - Selected target data sources and scale - Discussed coordinate projection issues and solutions - Researched USGS NED data download

Re: [GRASS-dev] GRASS GIS and GSoC

Vashek, thank you for your time and for being willing to co-mentor the project. Let's keep trying to rope someone else in! I will look at the existing tickets and see how I can help. Stefan, thank you for getting me that script. You're right, it's a great starting point. Keep us posted if you're i

Re: [GRASS-dev] GRASS GIS and GSoC

gt; > > *From:* grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] *On Behalf > Of *Zechariah Krautwurst > *Sent:* tirsdag 28. mars 2017 00.56 > *To:* grass-dev@lists.osgeo.org > *Subject:* [GRASS-dev] GRASS GIS and GSoC > > > > Hello All, > > > My name is Zeke

[GRASS-dev] GRASS GIS and GSoC

Hello All, My name is Zeke Krautwurst and I am interested in participating in GSoC this summer through GRASS GIS. I have been in contact with developers Vashek Petras and Anna Petrasova at NCSU. Vashek recommended that I reach out to the broader dev community as well, potentially to find a lead m