2025-09-29 – Weekly GIS News : Drive-time polygons over 3-mile rings?

Last week’s forum discussions covered a range of engaging topics for GIS professionals. The debates sparked by the comparison between the value of GIS degrees versus practical project work were particularly thought-provoking. Discussions also touched on the technical challenges of mapping with thin smoke interference and the strategic advantages of using drive-time polygons over traditional methods. Conversations about job opportunities and career paths in GIS, including roles that offer housing for interns, provided valuable insights for those navigating their professional journeys.


This Week’s Hot Topics

2025-09-25 – Weekly GIS Jobs : Internship with housing included
An intriguing opportunity for those entering the GIS field, this internship discussion highlights the benefits and considerations of roles that offer housing.
Read more here

Thin smoke keeps fooling my change maps
A practical challenge faced by many mappers—this thread explores strategies to improve accuracy when thin smoke affects remote sensing.
Read more here

KDE settings for burglary hot spots
For those interested in crime mapping, this discussion on optimizing Kernel Density Estimation settings for identifying burglary hot spots is quite insightful.
Read more here

Better workflow for harvest unit layouts
Explore innovative methods to enhance layout efficiency for harvest units in this practical forum discussion.
Read more here

Drive-time polygons beat 3-mile rings
A compelling argument for using drive-time polygons over traditional distance rings, with real-world implications for location-based analysis.
Read more here

Would You Take This Job? – GIS Analyst I
A candid look at a GIS Analyst I position, inviting members to weigh in on job expectations and career fit.
Read more here

Starter data structure for a new GIS shop
This thread is a goldmine for anyone setting up a new GIS operation, offering foundational advice on data structures.
Read more here

Consulting vs agency for EIA GIS roles
A thoughtful comparison of career paths in environmental impact assessment roles, discussing the pros and cons of consulting versus agency work.
Read more here

LiDAR rerouted our skid trail today
An interesting look at how LiDAR technology is being used in forestry, specifically for rerouting skid trails for better efficiency.
Read more here


Looking forward to another week of engaging discussions. Keep sharing your experiences and questions—your contributions make this community thrive.

Drive-time polygons beat 3-mile rings for me when I ‘snap origins to the network’ and set a low-speed floor (e.g., 10 mph on locals) so cul-de-sacs and gated streets don’t exaggerate reach. If you lack probe traffic, I’ve gotten solid results using https://openrouteservice.org isochrones and validating a few sample travel times against Google directions before batch runs. Do you model by time-of-day or stick with static speeds?

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

Co-signing @mason33 on snapping — I’ve had better luck adding time-of-day traffic (historical speeds) and setting a about 200 m trim distance on the isochrone so driveway tentacles and tiny network gaps don’t bloat the area; circles don’t stop for rivers. Do you switch profiles for weekday vs weekend, or keep one speed set?

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

For site screening, I get better results than 3‑mile rings by setting the network’s U‑turn policy to ‘only at dead ends’ (e.g., in ArcGIS Pro’s Network Analyst), which keeps drive-time polygons from puffing out around complex intersections. Do you keep U‑turns open, or lock them down the same way?

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

I get cleaner isochrones by enabling hierarchy and setting curb approach to ‘right side only’ — , those fantasy cross‑median turns drive me nuts. After last week’s thin smoke thread, I’ve been applying a about 25% speed penalty to segments intersecting smoke polygons so the reach shrinks where visibility is bad. @mason33, your snap tip pairs well with excluding private roads, but watch downtown grids — hierarchy can skip alley cut‑throughs unless you include local connectors.

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

One tweak that’s helped me: run Service Area as lines, set Overlap to ‘Split’, then buffer 75–100 m — cleaner reach polygons without the parking‑lot spaghetti. If you’re comparing to fixed‑radius rings, this also keeps totals honest when you dissolve by break values. Esri’s settings are here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/service-area-analysis.htm — anyone tried the same workflow in Valhalla, @mason33?

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