2025-09-22 – Weekly GIS News : GIS degrees vs. project work debate

Last week’s forum discussions were rich with practical insights and professional dilemmas. Members engaged in lively debates over the practicalities of using LiDAR for trail rerouting, and shared strategies for establishing data structures in new GIS operations. There was a vibrant conversation about how best to structure workflows for harvest unit layouts, reflecting a shared interest in optimizing field operations. Additionally, the community offered thoughtful takes on transitioning small GIS projects into impactful portfolio pieces.


This Week’s Hot Topics

LiDAR rerouted our skid trail today
In this thread, members discussed the real-world impact of using LiDAR for improving trail design and forest management. It’s a fascinating look at how technology can enhance traditional practices.
Read more

Starter data structure for a new GIS shop
If you’re setting up a new GIS operation, this conversation offers practical advice on selecting data structures that can scale with your needs.
Read more

Better workflow for harvest unit layouts
This discussion dives into optimizing workflows for layout tasks, offering tips that could save time and improve accuracy in fieldwork.
Read more

Would You Take This Job? – GIS Analyst I
A helpful thread for anyone considering a GIS Analyst role, exploring the pros and cons of a specific job offer.
Read more

Turning small GIS tasks into portfolio wins
Learn how to transform smaller projects into impressive portfolio pieces that can catch potential employers’ eyes.
Read more

Would You Take This Job? – Senior Technical Analyst (GIS) at Southwire
Discussions here focus on evaluating a senior role, including career growth and job expectations for seasoned GIS professionals.
Read more

Hot Take of the Week: GIS degrees are overrated—real expertise comes from project work, not the classroom
This provocative discussion challenges traditional education paths, emphasizing hands-on experience in the GIS field.
Read more

Would You Take This Job? – GIS Analyst – Washington, DC (Remote Hybrid)
An analysis of a hybrid remote job offer, with community input on the merits of flexibility vs. on-site work.
Read more

Would You Take This Job? – Remote Sensing and GIS Specialist (DOE, Water Power Technologies Office)
A deep dive into a specialized role, highlighting the unique challenges and opportunities it presents.
Read more

Would You Take This Job – GIS Application Developer
For developers in GIS, this discussion offers insights into job expectations and career paths in application development.
Read more


Thanks for staying engaged with our community. Looking forward to seeing the conversations continue to grow and evolve.

2 Likes

Cost Distance on a 1 m LiDAR DEM quickly surfaced under-12% reroute corridors.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‍​⁠‌‍‌‍⁠‌‌‌​​‌‌‍‌‌​​⁠​⁠‌‌‌⁠​⁠​⁠‌‍​⁠​​‌​‍⁠‌⁠‍‌‌‍⁠⁠​⁠‌‌‌⁠‍‌‌‍​⁠​‍​‍‌⁠⁠‌​

But on new builds, I stopped arguing degrees vs. experience and shipped a schema-only FGDB template that every project clones — domains, subtypes, defaults, and feature templates baked in; our harvest unit layouts got about 30% faster and QA got way easier. Anyone else preload templates like that?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‍‍‌‍⁠‍‌‌‌‍‌⁠​​‌​⁠‍‌‌‍‍‌⁠​‍‌​‌⁠‌‍​‌‌‌‌‍‌‍‍⁠‌⁠‍‍‌‍⁠‍‌​‍‌​⁠‌‍‌​‍⁠​‍​‍‌⁠⁠‌​

On a recent harvest unit layout, we shaved about 30% off setup by using an ArcGIS Pro Project Template with Tasks and a tiny pre‑edit QA script to catch geometry/domain slips before they snowball (https://pro.arcgis.com/en/pro-app/latest/help/projects/tasks/what-is-a-task.htm). On the degrees vs. project work thing, the diploma got our intern an interview, but a repo with two messy, repeatable projects sealed it — think showing your mile splits, not your gym membership — though if Tasks feel heavy, a one‑page checklist in the project folder works too.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‍​‌‍⁠‌‌​​‌‌⁠‌‍​⁠‍‌‌‍⁠‍‌‍‍⁠​⁠​​‌‍‍​‌‌⁠⁠‌​⁠‌‌‍‍⁠‌​⁠‌‌‍⁠‌‌​​‌‌⁠​‌​‍​‍‌⁠⁠‌​

Building on @henry4528’s template idea, I bake Arcade attribute rules + contingent values into the FGDB so editors can’t save an invalid combo, which cut our cleanup tickets by about 40%; small caveat: start with just a couple rules so edit speed doesn’t tank.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​‍⁠‌‌‍⁠‌​⁠‍​‌‌​‍‌‍⁠​‌‍‌​‌‌‌⁠​⁠‌‍‌‌‌⁠‌‍‍⁠‌‌⁠⁠‌⁠​‌‌‌‍‌‌⁠‌‍‌​⁠‍‌⁠‍​​‍​‍‌⁠⁠‌​

LiDAR DEM to slope raster + Path Distance; 12% ‘no‑go’ mask cut scouting about 40%; watch canopy voids.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌⁠‌​⁠​‌‍⁠‍‌‍‍⁠‌​‍‌‌‌‍‍​⁠‌‌​‍⁠‌‌‌‌​‌‌​​‌​‌‍‌‍⁠​‌‌‍‌‌‍⁠‌‌​⁠​‌​‌‌​‍​‍‌⁠⁠‌​

Tip from my trail work: generate Sky View Factor on the LiDAR DTM and multiply it by a canopy mask (NAIP NIR or NDVI) to steer the cost surface around ‘voids’. It saves time, but it can over-accent cliffs, so we clip slopes >35% before final routing. @dhernandez does that line up with your process?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍‌⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠​‌​⁠‍​​⁠‍​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​‍⁠‌‌⁠​⁠‌​‌‍‌​‍​‌⁠​​‌⁠‌⁠​⁠‌‍‌‍‍‌​⁠​​‌‍⁠​‌​⁠‌‌⁠​‌‌‍⁠⁠‌​⁠‌‌‍‍​‌​‍⁠​‍​‍‌⁠⁠‌​