THE TURLEY ANNEXATION

New roads already cut on the hillside above Stoor Drive and Mountain Drive

Why annexing this hillside is a bad idea for Alpine

  • Far more homes. Annexation brings Town water, sewer and zoning (the petition asks for multi-unit R-2). County rules would allow roughly 9 large lots.
  • Roads already cut, before any approval. About 4,600 ft on steep, forested slopes, with no visible erosion or drainage controls above existing homes.
  • Unsafe access. Grades up to 35–38% and two switchbacks far tighter than fire engines need.
  • Costs and risks unknown. The Town's own report says the yearly cost "cannot presently be calculated," and the slope, traffic, fire and stormwater studies come after the vote.

See the facts and sources What you can do before Oct 28

Timeline 2019 to now · next: Oct 28, 7 pm public hearing
  1. The Mayor meets about annexing "Steve Turley's 45 acres" and connecting to Town utilities (Council minutes).
  2. Planning & Zoning holds the pre-petition hearing. It later recommends single-family R-1 zoning, not the R-2 multi-unit zoning requested.
  3. Town Council certifies the annexation petition (Resolution 2026-034) and sets the public hearing.
  4. The Town's annexation report is issued. Required studies (slopes, traffic, fire, stormwater) are still to come.
  5. Drone photos show about 4,600 ft of new road already cut up the hillside.
  6. An excavator is grading the entrance between two homes; dirt is tracked onto the paved street.

The map

Map layers
  • Highlight one road:
  • 30–35°35–40°40–45°45°+
  • 0.5–2.5 ac uphill2.5–12 ac12 ac+
  • Red: land of the annexation petitioners. Approximate, from Lincoln County.
Drone photos stitched into one map, with the new roads drawn on top Slope-angle shading: yellow 30–35°, orange 35–40°, red 40–45°, purple 45° and steeper Blue lines: paths where rain and snowmelt drain

What the layers mean: Steep slopes · Water · Zoom out to the neighborhood

Zoom with + and −, a double-click, ctrl + scroll, or two fingers. Drag to move around when zoomed in.

North is up. The bar in the corner is 328 ft long. The photos are stitched together, so expect small seams. Tap a road or a letter to highlight it. Open this spot in Google Maps.

3D view beta

Beta: this 3D model is a first version and will be updated over the next 7 days. Right now it covers only the main climb (B) and the entrance, built from 230 drone photos taken Oct 18, 2026, and the forest canopy hides much of the road. A sharper model of the whole hillside is coming.

Drag to spin, scroll or pinch to zoom, right-drag or two-finger drag to move.

The short version

Why it matters that the road is already built

These roads were cut before the Town Council has voted on the annexation, and before any development plan has been approved. The Planning & Zoning Commission “did not approve a final development plan” (Town annexation report). Here is what that means for the homes below.

Water and mud

Bare dirt on a steep slope, with no drainage controls in sight. Rain and snowmelt on this hillside head downhill toward the homes below. The entrance itself follows a natural drainage path right down to the street. Where the water goes

Fire and emergency access

If homes are ever built up there, fire engines need wider roads, gentler grades and wider turns than these. The road surface is 12–15 ft wide; fire roads are normally 20 ft. The two switchbacks are about 23 and 27 ft in radius, while many fire districts expect roughly 48 ft on the outside of a turn. The two switchbacks

Steep slopes

Parts of this hillside are 30° or steeper, the angle where avalanches can start. Timber that helped hold the slope has been cleared along the road. Steep slopes

Annex or stay in the county? Why the Town should say no1

Why Turley wants to join the Town

  • The land is about 45 acres. Steve Turley and his partners (Alpine Property Holdings Group, LLC and Premier Realty Investments, LLC) have petitioned to join the Town of Alpine. Annexation report
  • If it stays in the county, the Town's report says "the property would not be eligible to connect to Town water or sanitary sewer service," and the Town "would have no control over its development." Annexation report
  • Under Lincoln County "Rural" zoning, subdivision lots must average 5 acres (2-acre minimum), on their own wells and septic. On about 45 acres that's roughly 9 lots (45 acres ÷ 5-acre average). Lincoln County land-use rules
  • County private roads are capped at 8% grade. Up to 10% is allowed in mountain terrain only with an engineer's design, for fewer than 10 lots. County roads are 26 ft wide, and 15 or more lots need two separate ways in. Lincoln County Chapter 6
  • Joining the Town would bring Town water and sewer. The petition asks for R-2 multi-unit zoning; the Planning & Zoning Commission recommended single-family R-1 instead. Annexation report
  • Annexation has been discussed since at least May 2019. The Council's May 21, 2019 minutes record a meeting with the Mayor about annexing "Steve Turley's 45 acres" and connecting to the Town's utility services. Council minutes

In plain terms: Town water, Town sewer and Town zoning are what make more homes possible on this hill. County rules would hold it to a handful of large lots.

What annexation would cost the Town

  • The report says: "The Town of Alpine will not bear any costs associated with the development of the property." The developer pays for the studies, infrastructure, extensions and upgrades. Annexation report
  • The developer's own preliminary estimate for water and sewer extensions is $784,034.38 (about 2,050 ft of sewer and 590 ft of waterline). The report says it "has not been independently verified or approved by the Town," and it leaves out the required studies and any further upgrades. Annexation report
  • The report says the number of homes and the utility use haven't been determined, so the yearly service cost "cannot presently be calculated." The required studies (geotechnical, slopes, traffic, fire risk, stormwater, water and sewer) haven't been done yet. In other words, the Council is being asked to annex before the studies. Annexation report
  • On the revenue side, to be fair: the Town's mill levy is 5 mills, and the report says annexation would bring the property into the Town's tax and utility-rate base. Annexation report

Costs the report doesn't put a number on. These are questions, not estimates:

  • Once the new water and sewer lines become part of the Town system, who maintains them, and who pays to replace them someday?
  • Is there enough water and sewer plant capacity? The report says existing lines being nearby "does not establish" that they are adequate. If capacity is short, what would expanding it cost?
  • The report says the land "would be accessed through existing roads within the Town." What about wear and snow plowing on those streets? (P&Z asked for a traffic study.)
  • The Town contracts with and pays the Lincoln County Sheriff for law enforcement. Would more homes change that contract?
  • How much Town legal and staff time would this take over the years?
  • If a slope, drainage or fire problem shows up later on land the Town approved, what is the Town's risk?

Pros and cons

Pros of annexing (from the Town's report)

  • The Town controls the development and applies its codes.
  • Building inspections and code enforcement. The county doesn't provide building inspections here.
  • The developer must do the studies and pay for the infrastructure.
  • Homes on Town water and sewer instead of wells and septic.
  • Adds to the Town's tax and utility base.

Cons of annexing

  • Far more homes than county rules allow (R-2 multi-unit was requested).
  • New traffic through existing neighborhoods.
  • Steep slopes, drainage and runoff toward existing homes.
  • Fire and evacuation access on 13–38% grades with tight switchbacks.
  • Long-term maintenance and liability for the Town.
  • Costs and density are unknown, because the studies come after annexation.
  • Roads were already cut before the hearing, with no visible erosion controls.

If the Town says no

Turley can still build under county rules. But those rules are much stricter on density (roughly 9 large lots on wells and septic) and on roads (8% maximum grade, and curves no tighter than 100 ft in radius on mountain roads). The roads already cut are far steeper and tighter than that, so a county subdivision would need them redone. (Source: Lincoln County Chapter 6)

County limits are better for existing residents than a dense annexation.

What you can do

Upcoming meetings

  • Tue Oct 20, 7 pm: Town Council (executive session at 6 pm)
  • Wed Oct 28, 7 pm: Turley annexation public hearing. This is the key one.
  • Tue Nov 10, 7 pm: Planning & Zoning
  • Tue Dec 8, 7 pm: Planning & Zoning

Check times and places at alpinewy.gov.

The ask: tell the Town Council to deny the Turley annexation at the Oct 28 hearing.

Can't attend? Email clerk@alpinewy.gov before the hearing. Include your name, your address and a few sentences, and ask that your comment be entered into the record for the Turley annexation hearing.

Join the conversation

Neighbors post updates, meeting reminders and photos between meetings in the Protect Alpine, Wyoming Facebook group.

Join Protect Alpine, Wyoming on Facebook

Simple questions you can ask, as questions, not accusations:

Oct 14: an excavator at work between the houses

A second flight the next day, around 12:52–12:56 PM by the camera clock, found a small tracked excavator grading the cut between the two houses. The muddy ruts from Oct 13 are now a leveled strip running from the street up to the main climb.

Low angled drone photo showing a compact excavator grading a dirt strip between two houses, with a fence along its east edge
From about 85 ft up, looking down at an angle. Street at the top. The excavator is about halfway along the cut. (Photo DJI_0388)
Drone photo showing the whole graded entrance from the street to where it meets the road up the hill, with a stack of logs beside the junction
From about 220 ft up. The whole entrance, from the street (top right) to where it meets the road up the hill (bottom left). A stack of cut logs sits beside the junction. (Photo DJI_0387)
Graded width
≈ 11–13 ft, judged against the pickup parked beside it
East edge
Runs right along the neighbor's fence line
West edge
Runs onto the lawn of the west house
Equipment
One small tracked excavator, working
Timber
A stack of felled logs at the bottom of the entrance

Oct 14: where the dirt meets the street

Close-up drone photo: tread marks and dirt running from the dirt cut onto the paved surface

A close-up from the same photo, taken about 85 ft above the takeoff point. It isn't north-up and the camera is angled. What it shows:

  • Tread marks and dirt run from the cut onto the pavement, and dirt is spread across a wide patch of it.
  • No gravel pad, mat or other stabilized entrance is visible where the cut meets the pavement.
  • The dirt shows fresh, crisscrossing cleat marks of the kind tracked equipment leaves.
  • A survey stake with an orange flag, and what looks like a green utility box, sit at the edge of the cut.

Construction stormwater rules generally expect dirt tracked onto paved streets to be prevented or cleaned up, usually with a gravel pad at the entrance. Whether those rules apply here, and whether they're being met, is for Wyoming DEQ and the Town to decide.

Issues with the road

Three problems the photos and terrain data show. Tap one to read more.

The two tight switchbacksAbout 23 and 27 ft in radius. Fire engines typically need about 48 ft.

In two places the road doubles back on itself in a hairpin turn. These close-ups are cropped from the drone photos and turned so north is up. The measurements are give or take about 6 ft.

Close-up of the north switchback where segment B turns back into segment C

H1 · North switchback (B into C)

How far it turns
133°
Radius (middle of road)
≈ 23 ft
Inside / outside edge
≈ 16 ft / 30 ft
Grade through turn
Can't be measured from this data*
Elevation
≈ 5,850 ft
GPS
43.15835, −111.02053

Too tight for a fire engine under the usual standard. A second dirt track runs alongside, just east of the turn, which suggests an earlier or abandoned route.

Close-up of the V-shaped hairpin on segment D

H2 · V-shaped switchback on the south loop (D)

How far it turns
154°
Radius (middle of road)
≈ 27 ft
Inside / outside edge
≈ 20 ft / 34 ft
Grade through turn
Can't be measured from this data*
Elevation
≈ 6,010 ft (near the top)
GPS
43.15712, −111.02026

The sharpest turn on the road. The ground on either side runs roughly 13–27% grade, and the bare dirt banks on both sides show fresh digging and fill.

How these compare. Many Western fire districts ask for roughly 28 ft on the inside and 48 ft on the outside of a turn, so a fire engine can make it. Both switchbacks fall well short. Lincoln County's road rules don't allow curves tighter than 100 ft in radius on new mountain subdivision roads. This matters if the road is meant to serve homes or emergency access. A wider bend on D (101°, about 83 ft radius) is not a hairpin and isn't listed.

For the technical reader: the International Fire Code leaves turning radius to the local fire official (IFC D103.3). Radius is measured to the traced centerline, ±2 m. * Grades are sampled every 10 m from elevation data collected before the road was built; a tight turn packs too much curve into 10 m for that to give a reliable grade through the turn itself.

Where the water goesThe road sits on or crosses natural drainage paths above homes.

The blue lines on the map show where rain and snowmelt would naturally run down this hillside. Thicker lines carry water from more ground uphill. This is a computer model, not a hydrology study. It shows the paths water takes downhill, not how much water flows in a given storm.

What it shows about the road. Several parts of the new road sit on or across natural drainage paths:

WhereWhat the map showsGround draining to that spot
X · Straight line on the west side (not counted as road)Lies along a drainage path for nearly its whole length (about 580 ft). This is one reason to think it is a natural drainage or an old track, not part of the new road.≈ 20 acres
H1 · North switchbackSits in the bottom of a ravine≈ 10 acres
D · South loop, near the H2 switchbackCrosses a drainage path about 355 ft along D≈ 6.7 acres
A · Entrance between the housesFollows a drainage path its whole length, down to the street between the houses≈ 5.5 acres
B · Main climb above the housesCrosses a drainage path about 340 ft along B≈ 5.4 acres
C, D, E · Upper roadsSmaller crossings (C about 70 ft in, D about 660 ft in, E about 210 ft in)≈ 1–2 acres each

Six more crossings each drain less than an acre.

Why it matters. A road cut across a slope catches water running downhill and carries it along the road until it finds a way off. Where a road runs straight down a drainage path, as the entrance does, the road itself can become the channel. No culverts, drainage dips or silt fence are visible in the photos. Below the hill, the water paths run north, toward the homes. Whether the road needs drainage work, and whether it was required to have it, is for the Town, the County and Wyoming DEQ to look at.

How this was made

Ground elevations come from USGS 3DEP 1 m lidar (2020, before the road), over an area about 1.9 km × 1.6 km around the road. They match USGS point elevations within 0.12 m. Small pits were filled. Each cell drains to its steepest downhill neighbor (the standard "D8" method), and the uphill area draining through each cell was added up. Lines are drawn where at least half an acre drains through. Because the elevation data predates the road, the model shows how water ran before the road. The road's cuts and ditches will now redirect some of it. On flat ground in town (the zoomed-out map), streets, ditches and culverts decide where water actually goes, and the model can't see them, so treat the lines there as rough.

Steep slopesParts of the road cut across 30°+ slopes, the angle where avalanches can start.

The colored shading on the map marks ground steep enough for avalanches to start. This is not an official avalanche hazard map. I couldn't find one published for this hillside. It shows slope angle only, the same shading backcountry skiers use to spot avalanche terrain. It does not account for snowpack, weather or trees.

Why slope angle matters. Most slab avalanches start on slopes between 30° and 45°, most often around 35° to 40°. Once moving, a slide can run well past the bottom of the steep ground onto flatter land below, called the runout. A home can be in a runout zone without being on a steep lot.

What the numbers say. About 10.9 acres of the area in these photos is 30° or steeper, including about 2.6 acres at 35° or more. The new road cuts across that steep ground in several places:

Road sectionCrosses 30°+ groundCrosses 35°+ groundSteepest ground crossed
A · Entrance0%0%6°
B · Main climb15%7%40°
C · Upper switchbacks48%16%40°
D · South loop22%0%35°
E · East spur0%0%28°
X · West straight line (not counted)4%0%32°

These numbers describe the hillside the road crosses, not how steep the road itself is. A road can run fairly level across a 35° slope.

Why the road could matter. Dense timber anchors snow, and cutting a road clears a strip through it. Cut banks on steep slopes also remove support from the snow and soil above them. Whether that changes the avalanche or slope-stability risk to the homes below is a question for a qualified avalanche or geotechnical professional, and it's worth asking before any decision on the annexation.

How this was made

Ground elevations come from USGS 3DEP 1 m lidar, flown in 2020 before the road was built, via the USGS 3DEP elevation service. They match USGS point elevations within 0.2 m on a 16-point check grid. Slope is measured over a 10 m baseline at each map pixel, then aligned to the photo map using the same GPS control points as the road traces. Current avalanche conditions for this area: Bridger-Teton Avalanche Center.

Questions for the Town, County and State

These are possible problems the photos show, written as questions. A photo can't confirm a violation. Each one depends on permits, zoning and property lines that the Town, the County or the State would have to check. I'm not a lawyer or an engineer.

For the technical reader: Alpine LUDC §4-603(d) (driveways max 10% grade, min 10 ft wide); IFC Appendix D, D103.1–D103.3 (20 ft width, 10% max grade, turning radius set by the fire official); Lincoln County Land Use Regulations Chapter 6 (private roads max 8%, mountain-terrain exception to 10%; 1+ acre disturbance needs a DEQ stormwater permit); Wyoming DEQ construction stormwater (1–5 acres = small construction). Links are under Rules referenced.

Zoom out to see the neighborhood

The drone photos only cover the road. This map puts them on top of satellite imagery so you can zoom out and see the neighborhood, the town and where water heads off the hill. Use the box in the corner to turn layers on and off. Drag to move around and use + and − to zoom.

About this map

Base maps: USGS The National Map (public domain). The drone photo is placed using the drone's own GPS, so it may sit a few meters off the satellite image. The water and avalanche layers cover a wider area than the photos (the dashed "Analysis area"). Parcel lines come from Lincoln County's public GIS and are approximate; hover over (or tap) any parcel to see its owner, acreage and parcel number. Town limits come from the U.S. Census Bureau (TIGERweb, current boundary for Alpine town, GEOID 5601695). The Town's own official map governs if they differ.

How we measured this (technical details)

Road traced from the drone photos, georeferenced using each frame's GPS, altitude and heading, plus USGS 1 m lidar elevation data (2020). Lengths are along the ground, including the slope.

≈ 4,600 ftNew road, total (1,400 m · 0.87 mi). Likely range 4,100–5,000 ft
12–15 ftTraveled surface width
20–28 ftTotal disturbed width (cut bank, fill and clearing)
≈ 2–3 acGround disturbed by the road corridor
2 hairpins23 ft and 27 ft radius, both far tighter than fire-engine standards
~270 ftClimb from entrance (≈5,750 ft) to the high point (≈6,030 ft)

Segments

SegmentLengthElevationAvg gradeSteepest 20 mLength over 10%Over 20%

Click a row to highlight that segment on the map.

How the grades were worked out

Grade is how much the road climbs for every 100 feet it covers across the ground: rise ÷ horizontal run × 100. A road that rises 10 ft over 100 ft of level distance is a 10% grade. (For scale, a 45° slope is 100%.) Everything below can be checked by hand from the sample points, which are also in a spreadsheet file (CSV).

  1. The road's centerline was traced on the stitched drone image (the colored lines on the map above). Each traced point was turned into latitude and longitude using the image scale (0.444 m, or 1.46 ft, per pixel, north up), with the two hairpins as reference points.
  2. Points were placed every 10 m (32.8 ft) of horizontal distance along each traced line, plus one at the very end.
  3. The ground elevation at each point came from the USGS Elevation Point Query Service, which returns the best USGS 3DEP elevation data for a spot. Here that is a 1 m lidar survey flown in July 2020. (The coarser USGS 10 m elevation model covers this hill too.)
  4. For each 10 m step, grade = change in elevation ÷ 10 m × 100.
Average gradeAll the climbing and dropping along a segment, added up, divided by its horizontal length. Downhill counts the same as uphill, since a 20% drop is as steep as a 20% climb. This equals the average of the 10 m step grades.
Steepest 20 mThe largest rise (or drop) over any two back-to-back 10 m steps, divided by the 20 m (66 ft) between them. The shorter last step of a segment is left out of this.
Length over 10% / 20%The share of a segment's horizontal length made up of 10 m steps steeper than 10% (or 20%), in either direction.
Length along the slopeFor each step, √(run² + rise²), added up. On a 20% grade this is only 2% longer than the flat distance, so it barely changes the totals.

Caveat. The elevation data was collected in 2020, before this road existed, so it shows the original hillside. Where the road was dug into the slope or built up with fill, its real surface can be gentler than the ground it crosses. Grades here may be overstated by a few points in those places. Also, the road runs across a steep hillside, so a traced line that sits a few meters off the true centerline lands on steeper or gentler ground. A clinometer or a phone inclinometer app on the steepest stretches would confirm the numbers on site.

Download all sample points (grade-samples.csv) · one row per point: segment, distance, latitude, longitude, elevation in meters and feet, and the run, rise and grade of the step leading to it.

How this was measured

Equipment and flights. Aerial survey 13 Oct 2026 with a DJI Mavic 3 (Hasselblad L2D-20c camera): 9 frames, 143–514 m AGL. Follow-up flight 14 Oct 2026 (photos DJI_0387, DJI_0388, DJI_0396).

Scale. Each photo's height above the ground comes from its takeoff-relative altitude and USGS terrain heights. The camera's scale was checked against the GPS distance between overlapping photos. Where photos overlap, they agree to within 2–6 m.

Length. The centerline was snapped to the bare-dirt stripe in the stitched image, smoothed, and measured with the terrain slope included. The tolerance is about ±10%. Treat 4,600 ft as "roughly 4,100 to 5,000 ft."

Width. The surface was measured across about 600 cross-sections. Twelve to fifteen feet is the driven dirt. The wider figure includes cut banks, berms and cleared shoulders.

Grade. Grades come from USGS 1 m lidar (flown in 2020, before the road), sampled every 10 m along the traced line. See How the grades were worked out for every sample point. That data shows the original hillside, so where the road was cut in, the true grade may be a few points gentler. A $30 clinometer or a phone inclinometer app on the steepest stretches would confirm it.

Correction, 13 Oct 2026. An earlier version of this page gave higher grades (for example 19–22% averages on C, D and E, and stretches up to 42%). Those couldn't be reproduced from the elevation data, so they were replaced with the rechecked figures above. Lengths changed by less than 2%. The straight line on the west side (X) was briefly counted as part of the road, then taken back out.

Not counted. The straight line running north–south on the west side (gray, dashed, X) is not counted in the totals. It lies along a natural drainage path (see Water flow) and looks more like a drainage or an older track than part of the new road.

Town limits. The pink dashed line is Alpine's boundary from the U.S. Census Bureau. About 80% of the entrance (A) lies inside town limits. Segments B through E lie outside, in unincorporated Lincoln County. Census boundaries can lag recent annexations, and the Town's official map governs.

Parcel lines. From Lincoln County's public GIS ("Parcels (Approximate)"). Red outlines are parcels owned by the annexation petitioners (Steve Turley, Alpine Property Holdings Group, LLC, Premier Realty Investments, LLC, Stoor Properties, LLC). Hover over (or tap) any parcel to see the owner of record, acreage and parcel number from the county. Lines can be off by several feet, so for anything legal use a survey or the recorded plat.

Off the photos. Segment E runs out of the photos to the east, so its true length may be longer.

Rules referenced. Town of Alpine Land Use & Development Code · IFC Appendix D, fire apparatus access roads · Lincoln County Zoning Resolution · Lincoln County Land Use Regulations, Chapter 6 (road standards) · Town of Alpine annexation report, Sept 28, 2026 · Town Council minutes, May 21, 2019

Source photos

All 9 frames from the 13 Oct 2026 flight. Heights are above the takeoff point. The ground on the hill is 50–110 m higher than takeoff.

Drone photo DJI_0378
DJI_0378 · 274 m above takeoff
Drone photo DJI_0379
DJI_0379 · 274 m
Drone photo DJI_0380
DJI_0380 · 274 m
Drone photo DJI_0381
DJI_0381 · 332 m
Drone photo DJI_0382
DJI_0382 · 333 m
Drone photo DJI_0383
DJI_0383 · 411 m
Drone photo DJI_0384
DJI_0384 · 445 m
Drone photo DJI_0385
DJI_0385 · 514 m · overview
Drone photo DJI_0386
DJI_0386 · 144 m · house

Want to stay in the loop? Join the Protect Alpine, Wyoming Facebook group for updates and meeting reminders.

  1. The case against annexation is advocacy by an Alpine resident. Its facts come from the Town's own annexation report (Sept 28, 2026) and Lincoln County's land-use rules (Chapter 6, road standards).

About this page. The measurements on this page are a private resident's estimates, made from drone photos and public data. They are not a professional survey or an engineering or legal finding. The section "Annex or stay in the county?" is advocacy by a resident; the facts in it are linked to their sources. Nothing here accuses anyone of breaking the law. Whether any rule applies, and whether to annex, is for the Town of Alpine, Lincoln County and the State to decide. Full disclaimer.

Disclaimer

Estimates, not findings. This page was put together by a private resident of Alpine, Wyoming. The measurements are estimates made from consumer drone photos and public elevation data, with the error ranges stated on this page. They are not a licensed land survey, engineering study, appraisal or inspection, and they may contain mistakes.

Advocacy. The section "Annex or stay in the county?" and the call to deny the annexation are the author's advocacy about the pending Turley annexation, offered as a resident taking part in a public decision. The facts they rely on are linked to their sources: the Town's annexation report, Lincoln County's land-use rules and Town Council minutes.

No accusation of wrongdoing. Nothing here states or implies that any person or company has broken a law, code or permit condition, or acted improperly. Items listed as "possible" issues are questions for the responsible agencies to look into. Permits, approvals, exemptions or facts the author doesn't know about may fully explain what the photos show.

Not legal advice. References to the Town of Alpine code, the International Fire Code and Wyoming DEQ rules are the author's reading of public documents, given for context only. They are not legal advice, and whether any rule applies here is for the Town, Lincoln County and the State to decide.

Sources. Photos were taken by the author on 13 and 14 Oct 2026 from a drone flown over the area. Elevations come from the U.S. Geological Survey. Everything here is presented in good faith, as a matter of public interest in a pending land-use decision.

Corrections welcome. If anything here is wrong, including by the property owner or anyone with better information, email ginosesto@gmail.com and it will be reviewed and corrected promptly.