• Python analysis of abnormal front tire wear on windy US mountain roads

    From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 10:07:46 2026
    From Newsgroup: comp.lang.python

    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads
    in your community, I will run a python script (I just wrote) on those roads
    to predict the abnormal wear the front outboard tire shoulders will incur.

    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 08:18:48 2026
    From Newsgroup: comp.lang.python

    Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads
    in your community, I will run a python script (I just wrote) on those roads to predict the abnormal wear the front outboard tire shoulders will incur.

    To limit the number of datapoints, since I'm running Python on an 2009 Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US. Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass
    --
    Sometimes I just feel like I need to get away
    A place where I can be by myself, all alone
    I kinda lay down in the back yard
    Watch the leaves fall down on my face
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 15:01:31 2026
    From Newsgroup: comp.lang.python

    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>
    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Perfect! Thank you for providing a random test sample, which helps
    us improve the program as it's tested on control conditions now.

    With more eyes on the program & results, we can improve it together!
    Analyses below is manual, but everything else was done automatically.

    Burr Trail
    <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    Guardsman Pass
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>
    Moki Dugway
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    Shafer Canyon
    <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>

    Analysis of predicted abnormal front tire wear on Utah roads
    Moki Dugway, Shafer Canyon, Burr Trail & Guardsman Pass

    The objective was to predict abnormal outside-front tire shoulder wear resulting from downhill braking & steering-induced tire scrub on turns.

    Two websites were used to obtain the GPX tracks:
    <https://gpx.studio/>
    <https://overpass-turbo.eu/>

    The Python script will analyze the GPX tracks, calculating corner radii, left/right turning distributions & the 5 tightest calculated hairpins.

    I selected one downhill direction for each road wherever possible:
    Moki Dugway: North to South, descending Cedar Mesa.
    Shafer Canyon: Island in the Sky down to Potash Road.
    Burr Trail: Boulder toward Bullfrog.
    Guardsman Pass: From the pass toward Park City.

    Summary of GPX Analysis
    1. Moki Dugway
    GPX points: 220
    Sharp/moderate curve windows: 154
    Left turns: 76
    Right turns: 78
    Minimum calculated radius: 5.89 meters
    Assessment:
    Sustained downhill cornering with balanced tire loading.
    Moki Dugway has a substantial number of tight switchbacks
    over a relatively short descent.
    The left/right distribution is almost perfectly balanced
    (49.4% left / 50.6% right).
    Consequently, the expected lateral loading is reasonably
    balanced between the two front tires, with a very slight
    theoretical bias toward the left front tire.
    The 5.89-meter minimum calculated radius indicates a
    potentially tight corner, although the actual radius
    should be verified against the road geometry.

    2. Shafer Canyon Road
    GPX points: 162
    Sharp/moderate curve windows: 131
    Left turns: 66
    Right turns: 65
    Minimum calculated radius: 3.97 meters
    Assessment:
    Extremely demanding switchback geometry.
    Shafer Canyon has the tightest reported minimum radius
    among the first three reasonably comparable measurements.
    Its 1,500-foot descent through the sandstone cliffs
    makes it good test case for downhill braking and cornering.
    The left/right distribution is virtually symmetrical
    (50.4% left / 49.6% right).
    There is therefore no meaningful predicted preference
    for either front tire based on turn counts alone.

    3. Burr Trail
    GPX points: 199
    Sharp/moderate curve windows: 139
    Left turns: 71
    Right turns: 68
    Minimum calculated radius: 4.70 meters
    Assessment:
    Tight switchbacks with a slight right-front loading bias.
    The Waterpocket Fold switchbacks provide a combination of
    steep grades and tight curves.
    The turn distribution is balanced (51.1% left / 48.9% right).
    There is a slight theoretical preference for right-front
    outside-shoulder loading because of the greater number
    of left-hand turns in the test direction. However, the
    difference is too small to suggest tire-wear asymmetry.

    4. Guardsman Pass
    GPX points: 219
    Sharp/moderate curve windows: 135
    Left turns: 70
    Right turns: 65
    Minimum calculated radius: 2.04 meters
    Assessment:
    Mountain-road cornering with a large peak-scrub component.
    Guardsman Pass has the fewest curve windows proportionally
    among the four roads.
    Its left/right distribution is slightly biased toward
    left-hand turns (51.9% left / 48.1% right).
    This suggests a slight theoretical preference for
    outside-shoulder loading on the right-front tire.

    Overall Comparison
    The four roads share an interesting characteristic that the
    left/right turning distributions are reasonably balanced.

    Consequently, none demonstrates a strong inherent preference
    for wearing one front tire more than the other based on
    turn direction alone.

    The principal differences are the number of calculated
    curves, steepness of descent and reported minimum corner radii.

    Shafer Canyon and Burr Trail have steep switchback sections.
    Moki Dugway has sustained descending switchbacks.
    Guardsman Pass provides a paved mountain-road comparison.

    Important Qualification
    Actual outside-shoulder wear depends on tire pressure,
    alignment, suspension geometry, vehicle weight, braking,
    speed, road camber and driving style.

    python mountaincurves.py mokidugway.gpx
    Loaded 220 raw track points from 'mokidugway.gpx'.

    --- Road Geometric Analysis: mokidugway.gpx ---
    Detected sharp/moderate curves (R < 200m): 154
    Left-hand turning distribution: 76
    Right-hand turning distribution: 78
    Minimum corner radius (tightest hairpin): 5.89 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 5.89m | Direction: Right | Lat/Lon: 37.276825, -109.935955
    2. Radius: 7.00m | Direction: Left | Lat/Lon: 37.272532, -109.944278
    3. Radius: 7.67m | Direction: Left | Lat/Lon: 37.272507, -109.944243
    4. Radius: 8.48m | Direction: Right | Lat/Lon: 37.276883, -109.935927
    5. Radius: 8.84m | Direction: Right | Lat/Lon: 37.276849, -109.935935

    python mountaincurves.py shafercanyon.gpx
    Loaded 162 raw track points from 'shafercanyon.gpx'.

    --- Road Geometric Analysis: shafercanyon.gpx ---
    Detected sharp/moderate curves (R < 200m): 131
    Left-hand turning distribution: 66
    Right-hand turning distribution: 65
    Minimum corner radius (tightest hairpin): 3.97 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 3.97m | Direction: Right | Lat/Lon: 38.449308, -109.820485
    2. Radius: 4.44m | Direction: Left | Lat/Lon: 38.448474, -109.818339
    3. Radius: 6.81m | Direction: Left | Lat/Lon: 38.447882, -109.818434
    4. Radius: 7.10m | Direction: Left | Lat/Lon: 38.447199, -109.819240
    5. Radius: 7.93m | Direction: Right | Lat/Lon: 38.450305, -109.819414

    python mountaincurves.py burrtrail.gpx
    Loaded 199 raw track points from 'burrtrail.gpx'.

    --- Road Geometric Analysis: burrtrail.gpx ---
    Detected sharp/moderate curves (R < 200m): 139
    Left-hand turning distribution: 71
    Right-hand turning distribution: 68
    Minimum corner radius (tightest hairpin): 4.70 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 4.70m | Direction: Left | Lat/Lon: 37.848198, -111.024654
    2. Radius: 6.16m | Direction: Left | Lat/Lon: 37.848657, -111.023535
    3. Radius: 6.88m | Direction: Right | Lat/Lon: 37.850700, -111.027191
    4. Radius: 7.59m | Direction: Right | Lat/Lon: 37.850662, -111.027217
    5. Radius: 7.73m | Direction: Right | Lat/Lon: 37.850838, -111.025700

    python mountaincurves.py guardsmanpass.gpx
    Loaded 219 raw track points from 'guardsmanpass.gpx'.

    --- Road Geometric Analysis: guardsmanpass.gpx ---
    Detected sharp/moderate curves (R < 200m): 135
    Left-hand turning distribution: 70
    Right-hand turning distribution: 65
    Minimum corner radius (tightest hairpin): 2.04 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620587, -111.495800
    2. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620605, -111.495784
    3. Radius: 2.29m | Direction: Left | Lat/Lon: 40.620597, -111.495796
    4. Radius: 2.33m | Direction: Right | Lat/Lon: 40.620464, -111.495741
    5. Radius: 2.71m | Direction: Right | Lat/Lon: 40.620569, -111.495601

    # #################################################################
    # mountaincurves.py
    # GPX road geometry analysis
    #
    # Calculates:
    # Corner radii
    # Left/right turn directions
    # Curvature statistics
    # Top 5 tightest hairpins
    #
    # Use model:
    # python mountaincurves.py [input.gpx]
    #
    # Examples:
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # #################################################################
    # Burr Trail
    # <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    # <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    # Guardsman Pass
    # <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    # <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>
    # Moki Dugway
    # <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    # <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    # Shafer Canyon
    # <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    # <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    # #################################################################
    # v1.7 20261104 Ran a random control test on Utah mountain roads
    # Suggested by Blaine Message-ID: <11cficq$pl38$1@dont-email.me>
    # #################################################################
    # Four Utah test roads (randomly selected on comp.lang.python)
    # 1. Moki Dugway
    # 2. Shafer Canyon Road (Shafer Trail)
    # 3. Burr Trail
    #
    # Shafer Canyon and Burr Trail have steep switchback sections.
    # Moki Dugway has sustained descending switchbacks.
    # Guardsman Pass is a paved-mountain-road comparison.
    # ###################################################################
    # <https://gpx.studio/>
    # 1. Open the appropriate road link below.
    # 2. Select File > New.
    # 3. Select the route-planning tool (pen icon).
    # 4. Select the appropriate routing mode (bicycle).
    # 5. Trace the complete road or click beginning & ending points.
    # 6. Select File > Export > Download file.
    # 7. Save using the suggested filename.
    # 8. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # -------------------------------------------------------------------
    # <https://overpass-turbo.eu/>
    # 1. Open the appropriate road link below.
    # 2. Delete the existing query in the editor (if any).
    # 3. Copy ONE query below into the editor and press the "Run" icon.
    # 4. Press the "Search" icon to zoom into the highlighted results.
    # 5. Select Export > Data > GPX
    # 6. Save using the suggested filename.
    # 7. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # ###################################################################
    # Moki Dugway, Utah State Route 261, Cedar Mesa, Utah.
    # I traced the steep switchback section
    # <https://gpx.studio/app#14.41/37.27473/-109.93787>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Moki Dugway - southern hairpin extension
    # (
    # way["highway"]
    # (37.17,-109.96,37.23,-109.91);
    # );
    # (._;>;);
    # out body;
    # Save as mokidugway.gpx
    # -------------------------------------------------------------------
    # Shafer Canyon Road (Shafer Trail) Canyonlands National Park, Utah
    # <https://gpx.studio/app#15/38.45303/-109.82112>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # way["highway"]["name"~"Shafer Trail|Shafer Canyon",i]
    # (38.43,-109.84,38.51,-109.77);
    # (._;>;);
    # out body;
    # Save as shafercanyon.gpx
    # -------------------------------------------------------------------
    # Burr Trail, Boulder, Utah, through Long Canyon and Waterpocket Fold.
    # <https://gpx.studio/app#14.55/37.85138/-111.03141>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Burr Trail, Boulder, Utah
    # // Long Canyon and Waterpocket Fold
    # (
    # way["highway"]["name"~"Burr Trail",i]
    # (37.81,-111.08,37.90,-110.98);
    # );
    # (._;>;);
    # out body;
    #
    # Save as burrtrail.gpx
    # -------------------------------------------------------------------
    # Guardsman Pass, Wasatch Mountains, between Brighton & Park City, Utah.
    # <https://gpx.studio/app#13.81/40.61548/-111.52533>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Guardsman Pass
    # // Wasatch Mountains, between Brighton and Park City, Utah
    # (
    # way["highway"]["name"~"Guardsman Pass|Guardsman Pass Road",i]
    # (40.55,-111.62,40.66,-111.48);
    # );
    # Save as guardsmanpass.gpx
    # ###################################################################
    # RUNNING THE FOUR TESTS
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # ###################################################################
    # Results will be inserted here after GPX analysis.
    #
    # Moki Dugway:
    # Pending GPX analysis.
    #
    # Shafer Canyon:
    # Pending GPX analysis.
    #
    # Burr Trail:
    # Pending GPX analysis.
    #
    # Guardsman Pass:
    # Pending GPX analysis.
    #
    # ###################################################################

    import xml.etree.ElementTree as ET
    import math
    import sys


    def parse_gpx(filename):
    tree = ET.parse(filename)
    root = tree.getroot()

    points = []

    for trkpt in root.iter(
    '{http://www.topografix.com/GPX/1/1}trkpt'
    ):
    lat = float(trkpt.get('lat'))
    lon = float(trkpt.get('lon'))
    points.append((lat, lon))

    return points


    def calculate_curvature(p1, p2, p3):

    lat_scale = 111132.92
    lon_scale = 111412.84 * math.cos(math.radians(p2[0]))

    def to_m(p):
    return (
    (p[1] - p2[1]) * lon_scale,
    (p[0] - p2[0]) * lat_scale
    )

    A = to_m(p1)
    B = (0.0, 0.0)
    C = to_m(p3)

    a = math.hypot(B[0]-C[0], B[1]-C[1])
    b = math.hypot(A[0]-C[0], A[1]-C[1])
    c = math.hypot(A[0]-B[0], A[1]-B[1])

    s = (a + b + c) / 2.0
    area_sq = s * (s-a) * (s-b) * (s-c)

    if area_sq <= 0 or a*b*c == 0:
    return float('inf'), "Straight"

    area = math.sqrt(abs(area_sq))
    radius = (a*b*c) / (4.0*area)

    cross = (
    (A[0]-B[0]) * (C[1]-B[1])
    - (A[1]-B[1]) * (C[0]-B[0])
    )

    direction = "Left" if cross > 0 else "Right"

    return radius, direction


    if __name__ == "__main__":

    if len(sys.argv) > 1:
    gpx_filename = sys.argv[1]
    else:
    gpx_filename = 'mokidugway.gpx'
    print(
    f"No filename provided. "
    f"Defaulting to '{gpx_filename}'..."
    )

    try:
    pts = parse_gpx(gpx_filename)

    except FileNotFoundError:
    print(
    f"Error: Could not find GPX file "
    f"'{gpx_filename}'."
    )
    sys.exit(1)

    except ET.ParseError:
    print(
    f"Error: Could not parse GPX file "
    f"'{gpx_filename}'."
    )
    sys.exit(1)

    print(
    f"Loaded {len(pts)} raw track points "
    f"from '{gpx_filename}'."
    )

    left_turns = 0
    right_turns = 0
    curve_records = []

    for i in range(len(pts)-2):

    r, direction = calculate_curvature(
    pts[i],
    pts[i+1],
    pts[i+2]
    )

    if r < 200:

    curve_records.append(
    (
    r,
    direction,
    pts[i+1][0],
    pts[i+1][1]
    )
    )

    if direction == "Left":
    left_turns += 1

    elif direction == "Right":
    right_turns += 1

    print(
    f"\n--- Road Geometric Analysis: "
    f"{gpx_filename} ---"
    )

    print(
    f"Detected sharp/moderate curves (R < 200m): "
    f"{len(curve_records)}"
    )

    print(
    f"Left-hand turning distribution: {left_turns}"
    )

    print(
    f"Right-hand turning distribution: {right_turns}"
    )

    if curve_records:

    curve_records.sort(key=lambda x: x[0])

    print(
    f"Minimum corner radius (tightest hairpin): "
    f"{curve_records[0][0]:.2f} meters"
    )

    print("\n--- Top 5 Tightest Hairpins / Curves ---")

    for idx, (r, direction, lat, lon) in enumerate(
    curve_records[:5], 1
    ):

    print(
    f"{idx}. Radius: {r:.2f}m | "
    f"Direction: {direction} | "
    f"Lat/Lon: {lat:.6f}, {lon:.6f}"
    )

    # ###################################################################
    # END OF mountaincurves.py
    # ###################################################################
    # Results:
    # C:\> python mountaincurves.py mokidugway.gpx
    # Loaded 220 raw track points from 'mokidugway.gpx'.
    # --- Road Geometric Analysis: mokidugway.gpx ---
    # Detected sharp/moderate curves (R < 200m): 154
    # Left-hand turning distribution: 76
    # Right-hand turning distribution: 78
    # Minimum corner radius (tightest hairpin): 5.89 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 5.89m | Direction: Right | Lat/Lon: 37.276825, -109.935955
    # 2. Radius: 7.00m | Direction: Left | Lat/Lon: 37.272532, -109.944278
    # 3. Radius: 7.67m | Direction: Left | Lat/Lon: 37.272507, -109.944243
    # 4. Radius: 8.48m | Direction: Right | Lat/Lon: 37.276883, -109.935927
    # 5. Radius: 8.84m | Direction: Right | Lat/Lon: 37.276849, -109.935935
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py shafercanyon.gpx
    # Loaded 162 raw track points from 'shafercanyon.gpx'.
    #
    # --- Road Geometric Analysis: shafercanyon.gpx ---
    # Detected sharp/moderate curves (R < 200m): 131
    # Left-hand turning distribution: 66
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 3.97 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 3.97m | Direction: Right | Lat/Lon: 38.449308, -109.820485
    # 2. Radius: 4.44m | Direction: Left | Lat/Lon: 38.448474, -109.818339
    # 3. Radius: 6.81m | Direction: Left | Lat/Lon: 38.447882, -109.818434
    # 4. Radius: 7.10m | Direction: Left | Lat/Lon: 38.447199, -109.819240
    # 5. Radius: 7.93m | Direction: Right | Lat/Lon: 38.450305, -109.819414
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py burrtrail.gpx
    # Loaded 199 raw track points from 'burrtrail.gpx'.
    #
    # --- Road Geometric Analysis: burrtrail.gpx ---
    # Detected sharp/moderate curves (R < 200m): 139
    # Left-hand turning distribution: 71
    # Right-hand turning distribution: 68
    # Minimum corner radius (tightest hairpin): 4.70 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 4.70m | Direction: Left | Lat/Lon: 37.848198, -111.024654
    # 2. Radius: 6.16m | Direction: Left | Lat/Lon: 37.848657, -111.023535
    # 3. Radius: 6.88m | Direction: Right | Lat/Lon: 37.850700, -111.027191
    # 4. Radius: 7.59m | Direction: Right | Lat/Lon: 37.850662, -111.027217
    # 5. Radius: 7.73m | Direction: Right | Lat/Lon: 37.850838, -111.025700
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py guardsmanpass.gpx
    # Loaded 219 raw track points from 'guardsmanpass.gpx'.
    #
    # --- Road Geometric Analysis: guardsmanpass.gpx ---
    # Detected sharp/moderate curves (R < 200m): 135
    # Left-hand turning distribution: 70
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 2.04 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620587, -111.495800
    # 2. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620605, -111.495784
    # 3. Radius: 2.29m | Direction: Left | Lat/Lon: 40.620597, -111.495796
    # 4. Radius: 2.33m | Direction: Right | Lat/Lon: 40.620464, -111.495741
    # 5. Radius: 2.71m | Direction: Right | Lat/Lon: 40.620569, -111.495601
    # -------------------------------------------------------------------
    # ###################################################################
    # Analysis of predicted abnormal front tire wear on Utah roads
    # Moki Dugway, Shafer Canyon, Burr Trail & Guardsman Pass
    #
    # The objective was to predict abnormal outside-front tire shoulder wear
    # resulting from downhill braking & steering-induced tire scrub on turns.
    #
    # Two websites were used to obtain the GPX tracks:
    # <https://gpx.studio/>
    # <https://overpass-turbo.eu/>
    #
    # The Python script will analyze the GPX tracks, calculating corner radii,
    # left/right turning distributions & the 5 tightest calculated hairpins.
    #
    # I selected one downhill direction for each road wherever possible:
    # Moki Dugway: North to South, descending Cedar Mesa.
    # Shafer Canyon: Island in the Sky down to Potash Road.
    # Burr Trail: Boulder toward Bullfrog.
    # Guardsman Pass: From the pass toward Park City.
    #
    # Summary of GPX Analysis
    # 1. Moki Dugway
    # GPX points: 220
    # Sharp/moderate curve windows: 154
    # Left turns: 76
    # Right turns: 78
    # Minimum calculated radius: 5.89 meters
    # Assessment:
    # Sustained downhill cornering with balanced tire loading.
    # Moki Dugway has a substantial number of tight switchbacks
    # over a relatively short descent.
    # The left/right distribution is almost perfectly balanced
    # (49.4% left / 50.6% right).
    # Consequently, the expected lateral loading is reasonably
    # balanced between the two front tires, with a very slight
    # theoretical bias toward the left front tire.
    # The 5.89-meter minimum calculated radius indicates a
    # potentially tight corner, although the actual radius
    # should be verified against the road geometry.
    #
    # 2. Shafer Canyon Road
    # GPX points: 162
    # Sharp/moderate curve windows: 131
    # Left turns: 66
    # Right turns: 65
    # Minimum calculated radius: 3.97 meters
    # Assessment:
    # Extremely demanding switchback geometry.
    # Shafer Canyon has the tightest reported minimum radius
    # among the first three reasonably comparable measurements.
    # Its 1,500-foot descent through the sandstone cliffs
    # makes it good test case for downhill braking and cornering.
    # The left/right distribution is virtually symmetrical
    # (50.4% left / 49.6% right).
    # There is therefore no meaningful predicted preference
    # for either front tire based on turn counts alone.
    #
    # 3. Burr Trail
    # GPX points: 199
    # Sharp/moderate curve windows: 139
    # Left turns: 71
    # Right turns: 68
    # Minimum calculated radius: 4.70 meters
    # Assessment:
    # Tight switchbacks with a slight right-front loading bias.
    # The Waterpocket Fold switchbacks provide a combination of
    # steep grades and tight curves.
    # The turn distribution is balanced (51.1% left / 48.9% right).
    # There is a slight theoretical preference for right-front
    # outside-shoulder loading because of the greater number
    # of left-hand turns in the test direction. However, the
    # difference is too small to suggest tire-wear asymmetry.
    #
    # 4. Guardsman Pass
    # GPX points: 219
    # Sharp/moderate curve windows: 135
    # Left turns: 70
    # Right turns: 65
    # Minimum calculated radius: 2.04 meters
    # Assessment:
    # Mountain-road cornering with a large peak-scrub component.
    # Guardsman Pass has the fewest curve windows proportionally
    # among the four roads.
    # Its left/right distribution is slightly biased toward
    # left-hand turns (51.9% left / 48.1% right).
    # This suggests a slight theoretical preference for
    # outside-shoulder loading on the right-front tire.
    #
    # Overall Comparison
    # The four roads share an interesting characteristic that the
    # left/right turning distributions are reasonably balanced.
    #
    # Consequently, none demonstrates a strong inherent preference
    # for wearing one front tire more than the other based on
    # turn direction alone.
    #
    # The principal differences are the number of calculated
    # curves, steepness of descent and reported minimum corner radii.
    #
    # Shafer Canyon and Burr Trail have steep switchback sections.
    # Moki Dugway has sustained descending switchbacks.
    # Guardsman Pass provides a paved mountain-road comparison.
    #
    # Important Qualification
    # Actual outside-shoulder wear depends on tire pressure,
    # alignment, suspension geometry, vehicle weight, braking,
    # speed, road camber and driving style.
    # #################################################################
    --
    On Usenet, every post should strive to add unique added value to the
    combined tribal knowledge on the topic currently being discussed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Real Bev@bashley101@gmail.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 11:20:46 2026
    From Newsgroup: comp.lang.python

    On 11/4/26 11:01, Maria Sophia wrote:
    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>>
    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Angeles Crest (CA 2) north of Los Angeles. Mulholland Drive in
    Hollywood. People regularly kill themselves on these roads.
    --
    Cheers, Bev
    Warning: Objects in mirror appear smarter than they are.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 15:53:23 2026
    From Newsgroup: comp.lang.python

    The Real Bev wrote:
    On 11/4/26 11:01, Maria Sophia wrote:
    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>>> see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Angeles Crest (CA 2) north of Los Angeles. Mulholland Drive in
    Hollywood. People regularly kill themselves on these roads.

    1. Moki Dugway
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>

    2. Shafer Canyon
    <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>

    3. Burr Trail
    <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>

    4. Guardsman Pass
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>

    5. Angeles Crest Highway (CA-2):
    <https://gpx.studio/app#12.39/34.23487/-118.24127>
    <https://i.postimg.cc/dV8qhd8f/angelescrest.jpg>
    C:\> python mountaincurves.py angelescrest.gpx
    Loaded 632 raw track points from 'angelescrest.gpx'.

    --- Road Geometric Analysis: angelescrest.gpx ---
    Detected sharp/moderate curves (R < 200m): 424
    Left-hand turning distribution: 207
    Right-hand turning distribution: 217
    Minimum corner radius (tightest hairpin): 10.28 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 10.28m | Direction: Left | Lat/Lon: 34.222522, -118.192759
    2. Radius: 18.12m | Direction: Right | Lat/Lon: 34.220180, -118.191992
    3. Radius: 21.20m | Direction: Right | Lat/Lon: 34.222678, -118.192989
    4. Radius: 38.06m | Direction: Left | Lat/Lon: 34.228787, -118.183125
    5. Radius: 39.78m | Direction: Left | Lat/Lon: 34.228913, -118.182865

    Assessment:
    Sharp mountain-road cornering with balanced directional loading.
    Of the 6 testcases, this has the greatest number of GPX points
    and detected curve windows among all six roads.
    Its 424 detected curve windows are substantially more than any
    of the Utah examples.
    Despite the large number of curves, its left/right distribution
    remains remarkably balanced.
    There is a slight preference for outside-shoulder loading on the
    left-front tire because right-hand turns are more numerous.
    However, the 48.8% / 51.2% distribution does not indicate a
    substantial directional imbalance.
    Its minimum calculated radius of 10.28 meters is considerably
    larger than the reported minimums on the four Utah roads.
    This makes Angeles Crest more of a sustained-mountain-road
    cornering rather than extremely tight switchbacks.

    6. Mulholland Drive (Hollywood Hills):
    <https://gpx.studio/app#14/34.13106/-118.44057>
    <https://i.postimg.cc/8kB9fH36/mulholland.jpg>
    C:\> python mountaincurves.py mulholland.gpx
    Loaded 318 raw track points from 'mulholland.gpx'.

    --- Road Geometric Analysis: mulholland.gpx ---
    Detected sharp/moderate curves (R < 200m): 221
    Left-hand turning distribution: 117
    Right-hand turning distribution: 104
    Minimum corner radius (tightest hairpin): 9.33 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 9.33m | Direction: Right | Lat/Lon: 34.129665, -118.468754
    2. Radius: 15.26m | Direction: Left | Lat/Lon: 34.129776, -118.466845
    3. Radius: 16.88m | Direction: Left | Lat/Lon: 34.129803, -118.466891
    4. Radius: 17.45m | Direction: Right | Lat/Lon: 34.131688, -118.431116
    5. Radius: 18.41m | Direction: Right | Lat/Lon: 34.129666, -118.466773

    Assessment:
    Pronounced left-turn distribution with a right-front loading bias.
    Mulholland Drive has the second-highest number of detected curve
    windows in the six-road comparison.
    Unlike Angeles Crest, it exhibits a noticeable left-turn preference.
    The 52.9% left-turn distribution implies a preference for outside-shoulder
    loading on the right-front tire.
    Its minimum calculated radius of 9.33 meters is relatively large
    compared with the Utah switchback roads.
    Mulholland therefore has more directional imbalance, but less-extreme
    calculated minimum curvature.
    --
    I invest energy in responding to Usenet posts because I care about people getting full & complete information so we move tribal knowledge forward.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Your Name@YourName@YourISP.com to rec.autos.tech,alt.satellite.gps,alt.comp.os.windows-10,comp.lang.python on Thu Nov 5 09:43:10 2026
    From Newsgroup: comp.lang.python

    On 2026-11-04 15:18:48 +0000, Blaine said:

    Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads. >>
    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >> in your community, I will run a python script (I just wrote) on those roads >> to predict the abnormal wear the front outboard tire shoulders will incur. >>
    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US. >> Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piergiorgio Sartor@piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 22:07:38 2026
    From Newsgroup: comp.lang.python

    On 04/11/2026 15.07, Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads
    in your community, I will run a python script (I just wrote) on those roads to predict the abnormal wear the front outboard tire shoulders will incur.

    To limit the number of datapoints, since I'm running Python on an 2009 Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    How can you test this?
    I mean, ground truth data is there?
    Do you have? Can you get it?

    Otherwise you can just have a random number
    generator ignoring your "data points" and
    you'll not see the difference.

    Of course, you can check your code does not
    crash, maybe it produces reasonable data...

    Or I'm missing something?

    bye,
    --

    piergiorgio
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 17:58:01 2026
    From Newsgroup: comp.lang.python

    Piergiorgio Sartor wrote:
    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    How can you test this?
    I mean, ground truth data is there?
    Do you have? Can you get it?

    Anyone who commutes on mountain roads has *already* measured this.

    Or are you asking about road inherency metrics obtained from the GPX files?

    Or about basic suspension engineering related to tire wear under cornering?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to rec.autos.tech,alt.satellite.gps,alt.comp.os.windows-10,comp.lang.python on Wed Nov 4 18:03:42 2026
    From Newsgroup: comp.lang.python

    Your Name wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>> Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Many people don't live in the mountains, but *everyone* who does, knows
    there is abnormal tire wear on the front outboard outside tire shoulder.

    A vehicle, perfectly aligned to OEM specs, with even a bit extra negative camber, and maybe even a few psi extra sidewall stiffening, will *still* experience abnormal tire wear, as compared to those who live in flatland.

    The mechanism is dynamic tire loading and suspension geometry under
    sustained cornering, particularly on steep mountain roads with tight, slow-speed switchbacks.

    Several things contribute.

    1. Lateral weight transfer: When negotiating a tight turn, vehicle weight transfers toward the outside wheels. The outside front tire carries a disproportionately large share of the cornering load.

    2. Body roll and camber change: As the suspension compresses on the
    outside, body roll and suspension geometry can cause the outside front
    wheel to lose negative camber or gain positive camber relative to the road. This concentrates loading on the outer shoulder.

    3. Steering angle and tire scrub: At very low speeds and high steering
    angles, the front tires experience considerable lateral deformation and
    scrub. This is especially pronounced in tight hairpins and full-lock turns.

    4. Combined braking and cornering forces: Descending steep grades while negotiating sharp turns adds longitudinal braking forces to the already substantial lateral forces. The front tires have to manage both
    simultaneously.

    5. Repeated exposure: Roads such as Moki Dugway, Shafer Canyon, Burr Trail,
    and Guardsman Pass can involve repeated tight turns, steep grades, changing road camber, and substantial steering inputs. Repetition makes the wear
    pattern more pronounced.

    People who commute in the mountains have already tested this for decades.
    --
    I invest energy in composing Usenet posts because I care greatly about
    people getting full & complete information so we improve our knowledge.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piergiorgio Sartor@piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 23:06:30 2026
    From Newsgroup: comp.lang.python

    On 04/11/2026 22.58, Maria Sophia wrote:
    Piergiorgio Sartor wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>
    How can you test this?
    I mean, ground truth data is there?
    Do you have? Can you get it?

    Anyone who commutes on mountain roads has *already* measured this.

    So you have the ground truth data already?
    Why you are then asking for roads?

    I do not get it...
    Or are you asking about road inherency metrics obtained from the GPX files?

    Or about basic suspension engineering related to tire wear under cornering?

    I understood you want to test your code
    and asked for some roads.

    Now, what should the code do?
    Take the road, in some data formant, and spit
    out what? The tyre wear, I understood.

    To know if this is correct, you need the
    measurement done by someone, or not?

    Do you have this data?
    If you have it, you have the road too, I think.

    Maybe I understood this completely wrongly.
    Sorry, if this would be the case. Apologises.

    bye,
    --

    piergiorgio
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 18:22:27 2026
    From Newsgroup: comp.lang.python

    Piergiorgio Sartor wrote:
    How can you test this?
    I mean, ground truth data is there?
    Do you have? Can you get it?

    Anyone who commutes on mountain roads has *already* measured this.

    So you have the ground truth data already?
    Why you are then asking for roads?
    I do not get it...

    Huh? I'm testing the python script. I need eyes on it.
    The roads are data. Control data. I said I already ran it on local roads.

    It's a script. It's gonna have bugs.
    What have you found so far by examining it?

    Or are you asking about road inherency metrics obtained from the GPX files? >>
    Or about basic suspension engineering related to tire wear under cornering?

    I understood you want to test your code
    and asked for some roads.

    Exactly. An unbiased control. I already tested on all the local roads.
    I needed a control that is unbiased from the standpoint of the data origin.

    Plus, it's neat for anyone to be able to generate a GPX of any road too.
    I'm sure that alone will enable many others to be more efficient mapping.

    Now, what should the code do?
    Take the road, in some data formant, and spit
    out what? The tyre wear, I understood.

    To know if this is correct, you need the
    measurement done by someone, or not?

    There isn't a person alive, who commutes in single-lane mountain roads, who hasn't had a tire shop not honor the warranty saying the tires were abused.

    Do you have this data?
    If you have it, you have the road too, I think.

    I live in a mountain community where EVERYONE knows that even Costco won't honor the tire-wear warranty, even at the very first scheduled rotation.

    You can feel the abnormal tire wear on the front tires within 100 miles.

    Maybe I understood this completely wrongly.
    Sorry, if this would be the case. Apologises.

    Driving on a mountain road is considered "abuse" by tire warranty shops.
    I explained in the post to "Your Name" what the engineering reasons are.

    The goal here was to get others to run the code on their local roads.
    And then we'd find bugs, or necessary enhancements and/or improvements.

    What enhancements do you suggest now that you've looked the code over?
    --
    The point of Usenet is for smart people to help each other & for results
    to be archived so that anyone can access our immense tribal knowledge.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piergiorgio Sartor@piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 23:39:47 2026
    From Newsgroup: comp.lang.python

    On 04/11/2026 23.22, Maria Sophia wrote:
    [...]
    Huh? I'm testing the python script. I need eyes on it.
    The roads are data. Control data. I said I already ran it on local roads.

    Input, I understood, and output?
    Do you have the output to compare with
    your script output?

    If you have it, again, why ask for roads?

    If you do not have, what are you testing?
    The script does not crash?

    It's a script. It's gonna have bugs.
    What have you found so far by examining it?

    That it will not work, likely... :-)

    [...]
    Now, what should the code do?
    Take the road, in some data formant, and spit
    out what? The tyre wear, I understood.

    To know if this is correct, you need the
    measurement done by someone, or not?

    There isn't a person alive, who commutes in single-lane mountain roads, who hasn't had a tire shop not honor the warranty saying the tires were abused.

    Eh?
    I'm already asking several time if you
    have the data, and you always answer the
    data should exist (in some universe, I guess).
    You never told us you've the data to compare
    with the output of your script.

    Do you have this data?
    If you have it, you have the road too, I think.

    I live in a mountain community where EVERYONE knows that even Costco won't honor the tire-wear warranty, even at the very first scheduled rotation.

    And still you did not answer the question.

    You can feel the abnormal tire wear on the front tires within 100 miles.

    I can feel many things, but likely not
    helpful for testing your code.

    Maybe I understood this completely wrongly.
    Sorry, if this would be the case. Apologises.

    Driving on a mountain road is considered "abuse" by tire warranty shops.
    I explained in the post to "Your Name" what the engineering reasons are.

    I'm no asking for reasons, I'm just
    curious to know how you test your
    code, apparently without comparison.

    The goal here was to get others to run the code on their local roads.
    And then we'd find bugs, or necessary enhancements and/or improvements.

    Maybe I'm completely stupid, but how can
    you find bugs (well, except crashes) if
    you do not have data to comaare with?

    You keep telling "everybody knows", but
    do *you* know?

    What enhancements do you suggest now that you've looked the code over?

    The code is not (yet) the problem here.
    The data is.

    But, then again, maybe I got it all wrong.
    Sorry again.

    bye,
    --

    piergiorgio
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 15:51:14 2026
    From Newsgroup: comp.lang.python

    Piergiorgio Sartor wrote:
    On 04/11/2026 23.22, Maria Sophia wrote:
    [...]
    Huh? I'm testing the python script. I need eyes on it.
    The roads are data. Control data. I said I already ran it on local roads.

    Input, I understood, and output?
    Do you have the output to compare with
    your script output?

    If you have it, again, why ask for roads?

    Why not, dude? What are you doing?
    --
    Sometimes I just feel like I need to get away
    A place where I can be by myself, all alone
    I kinda lay down in the back yard
    Watch the leaves fall down on my face
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piergiorgio Sartor@piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 00:00:41 2026
    From Newsgroup: comp.lang.python

    On 04/11/2026 23.51, Blaine wrote:
    Piergiorgio Sartor wrote:
    On 04/11/2026 23.22, Maria Sophia wrote:
    [...]
    Huh? I'm testing the python script. I need eyes on it.
    The roads are data. Control data. I said I already ran it on local
    roads.

    Input, I understood, and output?
    Do you have the output to compare with
    your script output?

    If you have it, again, why ask for roads?

    Why not, dude? What are you doing?

    Just curious, I mean, again maybe I did
    not understand the point, but asking for
    data to test a piece of code makes sense
    if one has the output to check.
    At least some expected output...
    There are metrics.

    If you have the data, why ask for something
    more *without* ground truth?

    Or there is a ground truth?

    Otherwise one can generate some plausible
    pseudo random data and be fine.

    I just wanted to understand the process, if any.

    That's all.

    bye,
    --

    piergiorgio
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Hank Rogers@Hank@nospam.invalid to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 17:04:39 2026
    From Newsgroup: comp.lang.python

    Maria Sophia wrote on 11/4/2026 4:22 PM:

    The point of Usenet is for smart people to help each other & for results
    to be archived so that anyone can access our immense tribal knowledge.

    Yes indeed Mary. When will you start this new tribal project?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 16:16:46 2026
    From Newsgroup: comp.lang.python

    Piergiorgio Sartor wrote:
    On 04/11/2026 23.51, Blaine wrote:
    Piergiorgio Sartor wrote:
    On 04/11/2026 23.22, Maria Sophia wrote:
    [...]
    Huh? I'm testing the python script. I need eyes on it.
    The roads are data. Control data. I said I already ran it on local
    roads.

    Input, I understood, and output?
    Do you have the output to compare with
    your script output?

    If you have it, again, why ask for roads?

    Why not, dude? What are you doing?

    Just curious, I mean, again maybe I did
    not understand the point, but asking for
    data to test a piece of code makes sense
    if one has the output to check.
    At least some expected output...
    There are metrics.

    I am here in Utah. Did you hear me complain about the diagnostics
    reported for the 4 passes I provided?

    If you have the data, why ask for something
    more *without* ground truth?

    It likely makes use of an API. It is doubtful that the program contains
    all the pass information for every mountain pass in the US.

    Or there is a ground truth?

    You should do some reading on statistics. It's useful to have data 'out
    of left field' to test corner cases and general hypotheses.

    Otherwise one can generate some plausible
    pseudo random data and be fine.

    As I said, I have no complaint about the information provided on the 4
    Utah mountain passes. Mission Accomplished, as they say.

    I just wanted to understand the process, if any.

    Perhaps it's a bit rude. It looks to me like you are a wild animal
    waiting to pounce on some perceived affront to the Python computer
    language or perhaps coding in general.

    That's all.--
    Sometimes I just feel like I need to get away
    A place where I can be by myself, all alone
    I kinda lay down in the back yard
    Watch the leaves fall down on my face
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Piergiorgio Sartor@piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 00:25:42 2026
    From Newsgroup: comp.lang.python

    On 05/11/2026 00.16, Blaine wrote:
    [...]
    Or there is a ground truth?

    You should do some reading on statistics. It's useful to have data 'out
    of left field' to test corner cases and general hypotheses.

    I beg to differ. Without data, no statistics.
    And here half data is missing.

    But, I repeat myself, maybe I do not get it.

    So, please explain.

    As I said, I have no complaint about the information provided on the 4
    Utah mountain passes. Mission Accomplished, as they say.

    Why should you complain?
    Why you think about complains?

    I just wanted to understand the process, if any.

    Perhaps it's a bit rude. It looks to me like you are a wild animal
    waiting to pounce on some perceived affront to the Python computer
    language or perhaps coding in general.

    Well, what should I say.

    I apologized a couple of time, I mention multiple
    times that maybe I do not understand the point.

    All I get is complains and no answers.

    I'm not sure about who is the "wild animal" here.

    bye,
    --

    piergiorgio
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 5 00:01:28 2026
    From Newsgroup: comp.lang.python

    On Nov 4, 2026 at 5:25:42rC>PM CST, "Piergiorgio Sartor" <piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de> wrote:

    On 05/11/2026 00.16, Blaine wrote:
    [...]
    Or there is a ground truth?

    You should do some reading on statistics. It's useful to have data 'out
    of left field' to test corner cases and general hypotheses.

    I beg to differ. Without data, no statistics.
    And here half data is missing.

    But, I repeat myself, maybe I do not get it.

    So, please explain.

    As I said, I have no complaint about the information provided on the 4
    Utah mountain passes. Mission Accomplished, as they say.

    Why should you complain?
    Why you think about complains?

    I just wanted to understand the process, if any.

    Perhaps it's a bit rude. It looks to me like you are a wild animal
    waiting to pounce on some perceived affront to the Python computer
    language or perhaps coding in general.

    Well, what should I say.

    I apologized a couple of time, I mention multiple
    times that maybe I do not understand the point.

    All I get is complains and no answers.

    I'm not sure about who is the "wild animal" here.

    bye,

    It's Arlen. He is the wild animal here. He was posting about this tire wear thing at least 20 years ago on rec.autos.tech, or some auto group used by mechanics.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 5 00:18:42 2026
    From Newsgroup: comp.lang.python

    On Nov 4, 2026 at 2:43:10rC>PM CST, "Your Name" <YourName@YourISP.com> wrote:

    On 2026-11-04 15:18:48 +0000, Blaine said:

    Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads. >>>
    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >>> in your community, I will run a python script (I just wrote) on those roads >>> to predict the abnormal wear the front outboard tire shoulders will incur. >>>
    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>> Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Yep. He is calling the expected *rapid* tire wear "abnormal". If you drive a car aound a race track at its limits, where there is little difference from those mountain twisties, that's going to cause rapid wear, but it's expected, therefore not abnormal. And he didn't include in his list the make and model
    of any specific vehicles, and they all have different suspension components, which includes all the rubber and plastic parts that are the bushings. The alignment specs are important, but not all that has to be considered. Cars
    with identical specs but different soft parts will have different tire wear. When he started on this 20 some years ago, i think he referred to some Chevy
    or GMC full size SUV. The GM engineers knew about the tire wear thing, and did not consider it abnormal, and the bushings had something to do with it on that heavy vehicle. There are tradeoffs in design. Arlen can't live with that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Old McDonald@eieio@patch.corn to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 16:46:36 2026
    From Newsgroup: comp.lang.python

    On 11/4/26 15:04, Hank Rogers wrote:
    Maria Sophia wrote on 11/4/2026 4:22 PM:

    The point of Usenet is for smart people to help each other & for results
    to be archived so that anyone can access our immense tribal knowledge.

    Yes indeed Mary.-a When will you start this new tribal project?

    He's circling the drain.
    He posts the stupidest sigs.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Wed Nov 4 21:44:43 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Yep. He is calling the expected *rapid* tire wear "abnormal". If you drive a car aound a race track at its limits, where there is little difference from those mountain twisties, that's going to cause rapid wear, but it's expected, therefore not abnormal. And he didn't include in his list the make and model of any specific vehicles, and they all have different suspension components, which includes all the rubber and plastic parts that are the bushings. The alignment specs are important, but not all that has to be considered. Cars with identical specs but different soft parts will have different tire wear. When he started on this 20 some years ago, i think he referred to some Chevy or GMC full size SUV. The GM engineers knew about the tire wear thing, and did
    not consider it abnormal, and the bushings had something to do with it on that
    heavy vehicle. There are tradeoffs in design. Arlen can't live with that.

    I'm going to make a very strong point, so that people can LEARN from this.

    1. Run the python script on your daily commute
    2. If you're not SHOCKED (you'll have a heart attack!), I'll be surprised
    3. Your commute, most likely, is child's play compared to mountain roads

    The strongly held point I'm going to make anyone who claims to disagree
    with what happens with mountain driving, needs to run the python code.

    Just running it once, on their commute, will turn them into a knowledgeable person from a novice, since the road inherence is TREMENDOUSLY different.

    For example, people who know nothing about the problem always bring up the drive train, but the drive train essentially has no meaning at all.

    People "think" it does.
    Because they don't understand the problem set.

    People who have never studied the problem set, think the drive train would matter, and yet, the fact is, it doesn't. Not in the downhill direction.

    I don't know why people don't understand, but I think they are thinking everything is flat, and when things are flat, drivetrain differences can
    have a greater effect on tire wear than when we're talking DOWNHILL runs.

    Most people have never driven on mountain roads day in and day out, so they have no idea that the similarities to flatland wear and tear don't exist.

    In the argument above, Bob conflates conflating general tire maintenance
    and suspension compliance with high-geometric-load cornering.

    I realize I didn't emphasize this enough initially, but we are looking specifically at downhill driving on tight mountain roads.

    When you're going downhill:

    The drivetrain is almost irrelevant: The engine isn't putting power down to accelerate through the turns. Gravity and braking forces dominate. Whether it's FWD, RWD, or AWD, the front tires are handling the steering lock and braking loads entirely on the overrun.

    Camber scrub overrides bushings: While soft rubber bushings, vehicle
    weight, and alignment specs change the rate of wear or how a specific suspension loads up, they don't cause the primary phenomenon. When a
    4.8-meter hairpin forces near-maximum steering lock, the contact patch undergoes severe lateral scrubbing. The tire is literally being dragged sideways across the asphalt under a forward weight transfer.

    Semantics on "Abnormal": You call it "expected rapid wear" like a track
    day, which is fair that if you drive a road with 600 hairpins, rapid wear
    is the expected physical result. But for the average driver who just
    visited Costco for the first scheduled rotation, seeing an outer tire
    shoulder chewed down to the cords while the rest of the tread has 60% life left looks and acts like an anomaly compared to normal commuting wear.

    The road geometry itself is what dictates the high-slip-angle scrub.

    The make, model, and drivetrain are just secondary variables turning the volume up or down, but EVERY passenger car in the mountains wears tires the same way.

    That's why the Python script concentrates on inherent road metrics.
    What did you get when you ran the script on your daily commute?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 21:53:34 2026
    From Newsgroup: comp.lang.python

    Old McDonald wrote:
    The point of Usenet is for smart people to help each other & for results >>> to be archived so that anyone can access our immense tribal knowledge.

    He posts the stupidest sigs.

    Some people understood the intellectual scope of this python exercise.
    The script analyzes different commutes for a specific known wear pattern.

    The objective was to predict abnormal outside-front tire shoulder wear resulting from downhill braking & steering-induced tire scrub on turns for
    a variety of roads, and then we can ANALYZE the differences between them.

    For example, the symmetry matters for tire wear.
    As does the curve frequency & radii.

    Q: What did you learn when you compared Utah/California commutes to yours?
    A: ?

    Note: If you can't answer that question, then you can't add any value.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 22:21:03 2026
    From Newsgroup: comp.lang.python

    Blaine wrote:
    If you have the data, why ask for something
    more *without* ground truth?

    It likely makes use of an API. It is doubtful that the program contains
    all the pass information for every mountain pass in the US.

    Hi Blaine,

    I appreciate that you're intelligent, as understanding this thread requires enormous automotive, python and engineering knowledge very few people have.

    To that end, thanks for explaining to "Piergiorgio" that the whole point
    was stated in the original post, which was to test the python script
    against known steep curvy mountain roads so that they can be compared.

    The goal is to be able to predict the specific "mountain" wear given any specific arbitrary section of steep curvy banked mountain road, where the directional cause of most wear will be when heading downhill and therefore
    the type of passenger vehicle drivetrain is almost meaningless (sure, it matters, but it's of a far lesser second-order effect to road inherence).

    People who have never studied this problem set can't comprehend that fact.

    They're the same kind of people who insist 91AKI fuel has "more power".
    They simply don't understand the problem set at the level they need to.

    Anyway, I wanted to thank you for UNDERSTANDING the point, which was an unbiased open python test and an algorithmic test, on known road inherents.

    I appreciate you provided road testcases that you were familiar with.
    I only need to make one minor clarification about the inherence API.

    For any given section of road, we can find the GPX inherence using this:
    <https://gpx.studio/>
    1. Open the appropriate road link listed below.
    2. Select File > New.
    3. Select the route-planning tool (pen icon).
    4. Select the appropriate routing mode (e.g., bicycle to stay on asphalt)
    5. Trace the complete road (or just click beginning & ending points).
    6. Select File > Export > Download GPX file.
    7. Save using the suggested road-based below filename.
    8. Run the Python analysis.
    python mountaincurves.py mokidugway.gpx
    python mountaincurves.py shafercanyon.gpx
    python mountaincurves.py burrtrail.gpx
    python mountaincurves.py guardsmanpass.gpx
    python mountaincurves.py angelescrest.gpx
    python mountaincurves.py mulholland.gpx

    For example, for the given unbiased kindly volunteered testcases,
    the python script generated an apples-to-apples commute comparison.

    Moki Dugway
    <https://gpx.studio/app#14.41/37.27473/-109.93787>
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    Shafer Canyon Road
    <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    <https://gpx.studio/app#15/38.45303/-109.82112>
    Burr Trail
    <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    <https://gpx.studio/app#14.55/37.85138/-111.03141>
    Guardsman Pass
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    <https://gpx.studio/app#13.81/40.61548/-111.52533>
    Angeles Crest Highway (CA-2):
    <https://gpx.studio/app#12.39/34.23487/-118.24127>
    <https://i.postimg.cc/dV8qhd8f/angelescrest.jpg>
    Mulholland Drive (Hollywood Hills):
    <https://gpx.studio/app#14/34.13106/-118.44057>
    <https://i.postimg.cc/8kB9fH36/mulholland.jpg>

    Note that I provided another more detailed method of obtaining a GPX
    file using the <https://overpass-turbo.eu/> web site as shown below.
    <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>

    The only reason I asked for USA mountain roads, as compared to those
    elsewhere around the world, is I wasn't sure the accuracy of the data.

    I never expected the average person to understand what the python
    script does because it takes skills most peoplee don't have, so
    I do very much appreciate that you understood the intent & scope.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Wed Nov 4 22:39:24 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    He was posting about this tire wear
    thing at least 20 years ago on rec.autos.tech, or some auto group used by mechanics.

    Hi Bob,

    I get it you want to infest this thread with your childish trolls, Bob.
    We go way back where you've been desperate to insult me for two decades.

    I feel sorry for you because you couldn't make it into college so you don't
    own the knowledge necessary to understand what the Python script actually accomplishes, nor how downhill mountain road inherence overwhelms typical suspension geometries and drive train particulars.

    However, given you've been desperate to insult me for decades, you're
    actually right about one thing.

    I have been studying this problem set for decades, where I could wager that maybe, oh, one out of ten thousand people understand it as well as I do.

    Maybe one out of a million.
    Dunno.

    Certainly only one or two people who posted to this thread understood it.

    Given your absurd argument about the drive train, it's clear you haven't learned a single thing in those twenty years, which, well, it's just sad.

    Meanwhile, I've actually done the empirical work, built the tools, and
    learned what actually moves the needle, and just as importantly, what
    doesn't (like realizing road banking or a minor cross-slope is basically a rounding error compared to the brutal geometry of a 4.8-meter hairpin).

    You've spent 20 years clinging to basic alignment checks and irrelevant drivetrain trivia because you've never bothered to look at road relevance.

    Your claim that all roads are the same, and worse, that all directions are
    the same, is so absurd at to ring loudly and clearly that I'm insulted that
    you TRIED to insult me, by proving you don't understand a thing about it.

    That's just sad.
    You're so embarrassed you know nothing, that you try to insult me.

    Why?
    Why have you been acting childishly like that for the past 20 years?

    When, if ever, will you grow up?

    Since you've had two decades to learn about this problem set, let's ask you which specific suspension bushing or alignment setting prevents a tire from experiencing lateral contact patch scrub at extreme steering lock under downhill braking?

    Let's see your math, or at least an educated explanation, why you feel the direction of travel & road inherence doesn't overwhelm "bushing" design.

    Q: What were your results when you ran the Python script on your commute?
    A: ?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Wed Nov 4 20:17:42 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> writes:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads
    in your community, I will run a python script (I just wrote) on those roads to predict the abnormal wear the front outboard tire shoulders will incur.

    To limit the number of datapoints, since I'm running Python on an 2009 Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    What exactly do you mean by "how well" the script works?

    Disclaimer: I don't drive on mountain roads, I haven't examined
    your Python code, and I'm not planning to run it.

    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been following this thread, and I see it's led to some insults
    (which I largely don't care about) but I don't recall any mention
    of measured data from actual tires. It's possible I've missed it;
    if so, please point me to the information I missed.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 01:31:05 2026
    From Newsgroup: comp.lang.python

    Keith Thompson wrote:
    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been studying this issue for decades, where I've been driving the same mountain roads for those same decades, when I was in a conversation with
    other mountain folk recently on an alias that has 5000 residents on it.

    We *all* mentioned the same anecdotes, no matter which vehicle, no matter
    the drive train, the suspension, the "bushings" (as Bob West waxed
    laconically over), even as we drive completely different commutes

    I wrote the Python code to COMPARE the commutes, where the whole goal was
    to look at the inherency of the road in the downhill direction, and compare roads for how they would affect the very special tire wear that occurs in mountain driving (i.e., low speed, braking with shift, lateral g forces,
    etc.)

    When I compared a half-dozen of our mountain roads, we were all pleasantly surprised (much as Blaine seems to have been) how *accurate* the inherency comparisons were, given we discussed it among scores of respondents and all
    of us agreed on the particulars of our roads.

    Road A, wore the front-left tire more, and that was the prediction.
    Road B, wore the front-right tire more, and that too was the prediction.
    Road C wore both front tires' outboard edges reasonably the same,
    and *that* was also predicted by the results of the Python script.

    Notice, given I have multiple degrees in a variety of fields, that it took engineering knowledge, programming acumen and mapping skills to write the program and test it on the variety of roads tested, so I was "hoping" to
    find other intelligent people on these newsgroups who might know more about this subject than I do, which would IMPROVE the results for everyone.

    It started off well, in that INTELIGENT people UNDERSTOOD the challenge. Unfortunately, the uneducated trolls infested the thread, as they are wont
    to do, such as Hank, Old McDonals, Bob West, Pergiorgio, et al.

    Not one of them understood a single line of the Python code.
    Not one of them has any education whatsoever in engineering.
    All of them came up with utterly absurd challenges to the science involved, even down to the wholly uneducated claim the "bushings" make a difference.

    If we added up their combined knowledge of Python, creating GPX routes, and
    how the automotive suspension works from all of them, it would still be negative.

    That was disheartening, that there are so few intelligent people on this
    ng, but the bright light was that a few, not many, but a few, were
    intelligent, and that is what we do on Usenet to share our efforts.

    It's 1:99 intelligent people to the morons on this newsgroup.
    But I'm hopeful at least ONE person will run the code on their commute.

    Is there a single intelligent person on this ng who can run Python code?
    How about you?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 12:50:16 2026
    From Newsgroup: comp.lang.python

    On 2026-11-05 06:31, Maria Sophia wrote:
    Keith Thompson wrote:
    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been studying this issue for decades, where I've been driving the same mountain roads for those same decades, when I was in a conversation with other mountain folk recently on an alias that has 5000 residents on it.

    We *all* mentioned the same anecdotes, no matter which vehicle, no matter
    the drive train, the suspension, the "bushings" (as Bob West waxed laconically over), even as we drive completely different commutes

    I wrote the Python code to COMPARE the commutes, where the whole goal was
    to look at the inherency of the road in the downhill direction, and compare roads for how they would affect the very special tire wear that occurs in mountain driving (i.e., low speed, braking with shift, lateral g forces, etc.)

    When I compared a half-dozen of our mountain roads, we were all pleasantly surprised (much as Blaine seems to have been) how *accurate* the inherency comparisons were, given we discussed it among scores of respondents and all of us agreed on the particulars of our roads.

    Road A, wore the front-left tire more, and that was the prediction.
    Road B, wore the front-right tire more, and that too was the prediction.
    Road C wore both front tires' outboard edges reasonably the same,
    and *that* was also predicted by the results of the Python script.

    Notice, given I have multiple degrees in a variety of fields, that it took engineering knowledge, programming acumen and mapping skills to write the program and test it on the variety of roads tested, so I was "hoping" to
    find other intelligent people on these newsgroups who might know more about this subject than I do, which would IMPROVE the results for everyone.

    It started off well, in that INTELIGENT people UNDERSTOOD the challenge. Unfortunately, the uneducated trolls infested the thread, as they are wont
    to do, such as Hank, Old McDonals, Bob West, Pergiorgio, et al.

    Not one of them understood a single line of the Python code.
    Not one of them has any education whatsoever in engineering.
    All of them came up with utterly absurd challenges to the science involved, even down to the wholly uneducated claim the "bushings" make a difference.

    If we added up their combined knowledge of Python, creating GPX routes, and how the automotive suspension works from all of them, it would still be negative.

    That was disheartening, that there are so few intelligent people on this
    ng, but the bright light was that a few, not many, but a few, were intelligent, and that is what we do on Usenet to share our efforts.

    It's 1:99 intelligent people to the morons on this newsgroup.
    But I'm hopeful at least ONE person will run the code on their commute.

    Is there a single intelligent person on this ng who can run Python code?
    How about you?


    You still have not answered Keith question, which is the same as
    Piergiorgio Sartor did. I also have the same doubt. You refuse to
    answer, that's clear, but I don't understand why. You are surely
    intelligent enough to understand the question...
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 04:09:18 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> writes:
    Keith Thompson wrote:
    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been studying this issue for decades, where I've been driving the same mountain roads for those same decades, when I was in a conversation with other mountain folk recently on an alias that has 5000 residents on it.

    I'm sure that's great, but I was really just looking for a yes or no
    answer.

    [...]

    Road A, wore the front-left tire more, and that was the prediction.
    Road B, wore the front-right tire more, and that too was the prediction.
    Road C wore both front tires' outboard edges reasonably the same,
    and *that* was also predicted by the results of the Python script.

    It sounds like the answer to my question is yes. Is that correct?
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 5 07:58:18 2026
    From Newsgroup: comp.lang.python

    On 11/4/2026 8:39 PM, Maria Sophia wrote:
    Bob West wrote:
    He was posting about this tire wear
    thing at least 20 years ago on rec.autos.tech, or some auto group used by
    mechanics.

    Hi Bob,

    I get it you want to infest this thread with your childish trolls, Bob.
    We go way back where you've been desperate to insult me for two decades.

    I feel sorry for you because you couldn't make it into college so you don't own the knowledge necessary to understand what the Python script actually accomplishes, nor how downhill mountain road inherence overwhelms typical suspension geometries and drive train particulars.

    However, given you've been desperate to insult me for decades, you're actually right about one thing.

    I have been studying this problem set for decades, where I could wager that maybe, oh, one out of ten thousand people understand it as well as I do.

    Maybe one out of a million.
    Dunno.

    Certainly only one or two people who posted to this thread understood it.

    Given your absurd argument about the drive train, it's clear you haven't learned a single thing in those twenty years, which, well, it's just sad.

    Meanwhile, I've actually done the empirical work, built the tools, and learned what actually moves the needle, and just as importantly, what
    doesn't (like realizing road banking or a minor cross-slope is basically a rounding error compared to the brutal geometry of a 4.8-meter hairpin).

    You've spent 20 years clinging to basic alignment checks and irrelevant drivetrain trivia because you've never bothered to look at road relevance.

    Your claim that all roads are the same, and worse, that all directions are the same, is so absurd at to ring loudly and clearly that I'm insulted that you TRIED to insult me, by proving you don't understand a thing about it.

    That's just sad.
    You're so embarrassed you know nothing, that you try to insult me.

    Why?
    Why have you been acting childishly like that for the past 20 years?

    When, if ever, will you grow up?

    Since you've had two decades to learn about this problem set, let's ask you which specific suspension bushing or alignment setting prevents a tire from experiencing lateral contact patch scrub at extreme steering lock under downhill braking?

    Let's see your math, or at least an educated explanation, why you feel the direction of travel & road inherence doesn't overwhelm "bushing" design.

    Q: What were your results when you ran the Python script on your commute?
    A: ?

    I doubt anyone here questions that your driving application
    presents an enhanced wear situation. I assume you have
    modeled that reasonably well.

    That said, even if your model accurately predicts mileage to
    failure (which you do not yet know, not having compared
    actual data to predicted), what is the point?

    Since this is a known issue, and since you have a long and
    rich experience (I assume you've replaced a lot of tires in
    20-odd years), the model can* only tell you when to replace,
    not extend wear life. It describes* the problem, but doesn't
    ameliorate it.

    * Assuming your model predictions correspond to actual data
    as experienced. They may well, but you don't know that.
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 07:59:45 2026
    From Newsgroup: comp.lang.python

    On 11/4/2026 10:17 PM, Keith Thompson wrote:
    Maria Sophia <mariasophia@comprehension.com> writes:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads. >>
    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >> in your community, I will run a python script (I just wrote) on those roads >> to predict the abnormal wear the front outboard tire shoulders will incur. >>
    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    What exactly do you mean by "how well" the script works?

    Disclaimer: I don't drive on mountain roads, I haven't examined
    your Python code, and I'm not planning to run it.

    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been following this thread, and I see it's led to some insults
    (which I largely don't care about) but I don't recall any mention
    of measured data from actual tires. It's possible I've missed it;
    if so, please point me to the information I missed.



    +1.
    Good perspective about models generally, aside from this
    specific problem. See also 'Global Warming".
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 5 07:51:27 2026
    From Newsgroup: comp.lang.python

    On 11/4/2026 8:39 PM, Maria Sophia wrote:
    Bob West wrote:
    He was posting about this tire wear
    thing at least 20 years ago on rec.autos.tech, or some auto group used by
    mechanics.

    Hi Bob,

    I get it you want to infest this thread with your childish trolls, Bob.
    We go way back where you've been desperate to insult me for two decades.

    I feel sorry for you because you couldn't make it into college so you don't own the knowledge necessary to understand what the Python script actually accomplishes, nor how downhill mountain road inherence overwhelms typical suspension geometries and drive train particulars.

    However, given you've been desperate to insult me for decades, you're actually right about one thing.

    I have been studying this problem set for decades, where I could wager that maybe, oh, one out of ten thousand people understand it as well as I do.

    Maybe one out of a million.
    Dunno.

    Certainly only one or two people who posted to this thread understood it.

    Given your absurd argument about the drive train, it's clear you haven't learned a single thing in those twenty years, which, well, it's just sad.

    Meanwhile, I've actually done the empirical work, built the tools, and learned what actually moves the needle, and just as importantly, what
    doesn't (like realizing road banking or a minor cross-slope is basically a rounding error compared to the brutal geometry of a 4.8-meter hairpin).

    You've spent 20 years clinging to basic alignment checks and irrelevant drivetrain trivia because you've never bothered to look at road relevance.

    Your claim that all roads are the same, and worse, that all directions are the same, is so absurd at to ring loudly and clearly that I'm insulted that you TRIED to insult me, by proving you don't understand a thing about it.

    That's just sad.
    You're so embarrassed you know nothing, that you try to insult me.

    Why?
    Why have you been acting childishly like that for the past 20 years?

    When, if ever, will you grow up?

    Since you've had two decades to learn about this problem set, let's ask you which specific suspension bushing or alignment setting prevents a tire from experiencing lateral contact patch scrub at extreme steering lock under downhill braking?

    Let's see your math, or at least an educated explanation, why you feel the direction of travel & road inherence doesn't overwhelm "bushing" design.

    Q: What were your results when you ran the Python script on your commute?
    A: ?

    If I understand Mr Sartor's point, you can probably
    anticipate estimated forces from mapping data at some
    assumed speed and some average rubber durometer value.

    The unknown is whether actual mileage to failure (or more
    prudently for passenger car tire purposes, to wear bar or to
    2/32" tread) corresponds to the predicted value in your script.

    You may well have constructed an appropriate model, but
    until the actual and predicted mileage are compared you
    don't know that.
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 10:46:19 2026
    From Newsgroup: comp.lang.python

    AMuzi wrote:
    Good perspective about models generally, aside from this
    specific problem. See also 'Global Warming".

    By including intelligent people from multiple Usenet newsgroups,
    this thread was clearly intended to IMPROVE existing testcases & models.

    Hence, it's obvious this thread was hoping to add to the modeling for
    1. GPS: How to calculate the track for any given mountain road
    2. Python: How to compare any set of tracks that have been calculated
    3. Suspension: How to correlate with real-world abnormal-wear experience

    That's expressly why these specific ngs of intelligent people were included
    1. alt.satellite.gps
    2. comp.lang.python, alt.comp.os.windows-10
    3. rec.autos.tech

    The choice of newsgroups makes it obvious we're seeking
    1. Better methods of obtaining measured inherence of mountain roads
    2. Better methods of calculation & prediction for specific metrics
    3. Better correlation with the real-world shoulder wear we all see daily

    Thankfully, we partially accomplished the goal of adding to our test sets
    the ability to predict (using map software and the python script), abnormal front tire shoulder wear in an arbitrary set of steep windy mountain roads.

    But we haven't exposed yet the algorithmic flaws in the python script.

    The script calculates a circumcircle through three consecutive GPX points.
    That gives a local geometric radius, but the result is sensitive to GPX
    point spacing and route-tracing accuracy (which brings up mapping
    software).

    Initially, I obtained tracks from helpful cyclists who emailed me their GPX tracks, but unfortunately all were done differently, so we decided to
    normalize the mapping activity to the methods previously described
    a. <https://gpx.studio/>
    b. <https://overpass-turbo.eu/>
    c. Others?

    That can't be the only sites that provide road-inherency metrics, can it?

    It may be that intelligent people on the mapping newsgroup are aware of a
    far better method to obtain road inherency for any steep mountain pass.

    Likewise, it may be that intelligent people on the Python newsgroup are
    aware of better algorithms for calculating specific road inherency forces.

    In particular, we're aware that the same physical road can produce
    different calculated radii depending on sampling density, and that several consecutive measurements can represent one physical corner, rather than independent corners.

    For example, I'm sure there are bugs in the Python code, as the reported 2.04-meter radius for Guardsman Pass deserves investigation, does it not?

    It may be a sampling or tracing artifact, for example.

    Also, for the intelligent people on the automotive newsgroup, some should
    note that a mere count of left/right curvature observations may not be equivalent to a count of actual turns or a measurement of tire loading.

    I acknowledge these limitations where the whole point of including trained programmers, automotive experts and mapping experts was to improve the
    tool.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 11:11:44 2026
    From Newsgroup: comp.lang.python

    Keith Thompson wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads. >>
    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >> in your community, I will run a python script (I just wrote) on those roads >> to predict the abnormal wear the front outboard tire shoulders will incur. >>
    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    What exactly do you mean by "how well" the script works?

    Disclaimer: I don't drive on mountain roads, I haven't examined
    your Python code, and I'm not planning to run it.

    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been following this thread, and I see it's led to some insults
    (which I largely don't care about) but I don't recall any mention
    of measured data from actual tires. It's possible I've missed it;
    if so, please point me to the information I missed.

    Carlos E. R. wrote:
    You still have not answered Keith question, which is the same as
    Piergiorgio Sartor did. I also have the same doubt. You refuse to
    answer, that's clear, but I don't understand why. You are surely
    intelligent enough to understand the question...

    Hi Carlos,

    Ah! My bad. I goofed. Mea culpa.

    I apologize for falling into the trap of reacting to the uneducated trolls (mainly, Hank Rogers, Bob West, Old McDonald) so I will reset my response.

    By reacting to the uneducated trolls, I wasted everyone's valuable time.

    There are explicit reasons why intelligent people were asked to help:
    a. The mapping ng can help us obtain road inherency metrics
    b. The Python/OS ngs can help us write the calculation/prediction code
    c. The automotive ng can help model the shoulder-rollover camber scrub

    To help us all improve the tool, the questions from Keith is fair.
    From his question, I realize I haven't explained the background adequately,
    and my earlier responses didn't directly answer what you were asking.

    Let me try again since there are multiple aspects to this investigation.

    1. The existing real-world observations

    Our local Santa Cruz Mountain community has experienced decades observing a particular type of abnormal front-tire outside-shoulder wear on our steep, winding roads, which we've been discussing lately on our local reflectors.

    Our local community includes approximately 5,000 mountain residents.

    Over the years, we've exchanged photographs and discussed similar wear
    patterns on numerous vehicles with different drivetrains, suspension configurations and alignments. We've even set up roadblocks, in the past,
    on weekends, to stop all vehicles and examine their tire wear patterns.

    We set up a weekend visit to all mountain homes that accepted our request
    to document their abnormal tire wear in the past, so the abnormal tire wear
    is well known to us in our specific mountain community.

    Recurring examples emerged in out studies of local abnormal tire wear.
    a. Road A: Predominantly premature front-left outside-shoulder wear.
    b. Road B: Predominantly premature front-right outside-shoulder wear.
    c. Road C: Relatively equal premature outside-shoulder wear on both.

    These observations motivated the investigation.
    They weren't conclusions generated by the Python program.
    In fact, the Python program doesn't even make conclusions or predictions.

    2. The Python analysis

    After decades of study as shown above, and during a recent spate of
    complaints that the local Costco wouldn't even honor the first scheduled rotation on new tires, I developed the previously included Python program
    on my Windows PC (which should work on macOS & Linux equally well) to
    examine road geometry, particularly corner radii and the distribution of left-hand and right-hand turns, but note that I didn't add the steepness,
    which is also a factor given the initial braking sets up the tire wear.

    The intention was to investigate whether inherent road geometry, combined
    with downhill braking and steering-related tire loading, could help
    calculate road metrics such that we can explain the data that we've all
    seen, where some roads wear the left, some the right, and some both.

    Therefore we needed a method of obtaining/comparing road inherency metrics.

    As noted in the original post, I first tested the program against
    approximately half a dozen local mountain roads, where its qualitative predictions were consistent with the representative observations above.

    However, I want to be precise about what that Python script establishes.
    The current program analyzes road geometry so that we can compare roads.

    The Python script makes no attempt to calculate actual tread loss, predict miles to the wear bars or establish a quantitative relationship between curvature and tire life. It simply compares road inherency metrics.

    Clearly, we haven't conducted a controlled experiment measuring tread-depth loss over known mileage on the Utah roads, but my hope was to find other experienced mountain commuters with whom we can compare road inherency
    metrics to correlate to THEIR particular front-tire shoulder wear patterns.

    3. Why I asked this group for help

    The original request was an attempt to extend the investigation beyond our local roads and to obtain expertise that our community might not have.

    Specifically:
    a. Mapping expertise:
    Better GPX tracks, road geometry, elevation and grade information.
    b. Python expertise:
    Improved algorithms and more sophisticated calculations.
    c. Automotive engineering expertise:
    Tire loading, suspension behavior, camber effects
    and steering-induced tire scrub on downhill right-radius curves.

    I was hoping to have intelligent people suggest roads they knew well so
    that we could compare their tire-wear observations on their mountain
    geometry with our existing mountain observations to improve the model.

    Keith, your question about comparing predictions with actual measured tire
    wear is entirely legitimate. That's an important distinction between a plausible model and a quantitatively validated one.

    Carlos, I wasn't deliberately refusing to answer. I was trying to explain
    the broader background, but I can see that I wasn't answering the specific question being asked, as I was unduly flustered by the ignorant trolls.

    I apologize.
    I should have made the distinction clear from the beginning.

    I'm not claiming that the present Python script proves a universal
    tire-wear theory. I'm trying to develop and improve a model that might
    explain a phenomenon we've observed repeatedly in the real world.

    Constructive criticism, better algorithms and additional expertise are precisely what I was hoping to get from this discussion.

    Specifically:
    a. Mapping newsgroup: How to get better road-inherency metrics?
    b. Python newsgroup: How to improve the road-inherency comparisons?
    c. Automotive newsgroup: How to predict/explain the abnormal tire wear?

    Does that answer your concerns so we can improve the tools together?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 09:50:31 2026
    From Newsgroup: comp.lang.python

    On 11/5/2026 8:46 AM, Maria Sophia wrote:
    AMuzi wrote:
    Good perspective about models generally, aside from this
    specific problem. See also 'Global Warming".

    By including intelligent people from multiple Usenet newsgroups,
    this thread was clearly intended to IMPROVE existing testcases & models.

    Hence, it's obvious this thread was hoping to add to the modeling for
    1. GPS: How to calculate the track for any given mountain road
    2. Python: How to compare any set of tracks that have been calculated
    3. Suspension: How to correlate with real-world abnormal-wear experience

    That's expressly why these specific ngs of intelligent people were included
    1. alt.satellite.gps
    2. comp.lang.python, alt.comp.os.windows-10
    3. rec.autos.tech

    The choice of newsgroups makes it obvious we're seeking
    1. Better methods of obtaining measured inherence of mountain roads
    2. Better methods of calculation & prediction for specific metrics
    3. Better correlation with the real-world shoulder wear we all see daily

    Thankfully, we partially accomplished the goal of adding to our test sets
    the ability to predict (using map software and the python script), abnormal front tire shoulder wear in an arbitrary set of steep windy mountain roads.

    But we haven't exposed yet the algorithmic flaws in the python script.

    The script calculates a circumcircle through three consecutive GPX points. That gives a local geometric radius, but the result is sensitive to GPX
    point spacing and route-tracing accuracy (which brings up mapping
    software).

    Initially, I obtained tracks from helpful cyclists who emailed me their GPX tracks, but unfortunately all were done differently, so we decided to normalize the mapping activity to the methods previously described
    a. <https://gpx.studio/>
    b. <https://overpass-turbo.eu/>
    c. Others?

    That can't be the only sites that provide road-inherency metrics, can it?

    It may be that intelligent people on the mapping newsgroup are aware of a
    far better method to obtain road inherency for any steep mountain pass.

    Likewise, it may be that intelligent people on the Python newsgroup are
    aware of better algorithms for calculating specific road inherency forces.

    In particular, we're aware that the same physical road can produce
    different calculated radii depending on sampling density, and that several consecutive measurements can represent one physical corner, rather than independent corners.

    For example, I'm sure there are bugs in the Python code, as the reported 2.04-meter radius for Guardsman Pass deserves investigation, does it not?

    It may be a sampling or tracing artifact, for example.

    Also, for the intelligent people on the automotive newsgroup, some should note that a mere count of left/right curvature observations may not be equivalent to a count of actual turns or a measurement of tire loading.

    I acknowledge these limitations where the whole point of including trained programmers, automotive experts and mapping experts was to improve the
    tool.

    Nice summary of the details and hat's off to you for making
    the effort.

    After a few years of comparing predicted mileage against
    actual mileage, you'll probably be able to correct any
    errors in your code.
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 11:53:03 2026
    From Newsgroup: comp.lang.python

    Keith Thompson wrote:
    Maria Sophia <mariasophia@comprehension.com> writes:
    Keith Thompson wrote:
    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been studying this issue for decades, where I've been driving the same >> mountain roads for those same decades, when I was in a conversation with
    other mountain folk recently on an alias that has 5000 residents on it.

    I'm sure that's great, but I was really just looking for a yes or no
    answer.

    [...]

    Road A, wore the front-left tire more, and that was the prediction.
    Road B, wore the front-right tire more, and that too was the prediction.
    Road C wore both front tires' outboard edges reasonably the same,
    and *that* was also predicted by the results of the Python script.

    It sounds like the answer to my question is yes. Is that correct?

    I goofed!

    I humbly apologize as I errantly conflated Sergio & Keith's intentionally helpful questions about the methodology with those of the intentionally unhelpful ignorant trolls (Bob West, Old McDonald & Hank Rogers).

    I will ignore the ignorant trolls (Bob West, Old McDonald & Hank Rogers).

    Everyone will benefit so we can get back to adding value in our ability to compare those inherent metrics which cause abnormal tire wear in steep
    twisty mountain roads, to the point that even Costco will refuse to rotate
    the tires upon their very first scheduled rotation, saying the "tires were abused" (even with verified proof of alignment).

    To Piergiorgio's, Keith's, Amuzi's and Carlos' valid, helpful concerns,
    I think I'm belatedly getting closer to the source of my misunderstanding,
    so let me try to immediately answer both of Keith's questions directly.

    Keith:
    Q: Is the Python analysis being compared with actual observed tire wear?
    A: Yes, qualitatively.

    We have decades of observations from our Santa Cruz Mountains community, including photographs and documented examples of fundamentally three
    different wear patterns associated with particular mountain roads:
    1. Road A: Predominantly front-left outside-shoulder wear.
    2. Road B: Predominantly front-right outside-shoulder wear.
    3. Road C: Relatively equal outside-shoulder wear on both front tires.

    I subsequently analyzed the geometry of those roads using mapping skills
    which can be improved (hence why I added the mapping experts), and using
    Python on Windows (hence why I added the python & Windows experts) such
    that the resulting comparative road metrics output was consistent with well-known observed differences in abnormal tire wear on road types A, B &
    C (hence why I added automotive suspension experts to this thread).

    However, I belatedly realize I had assumed people read the code, but if
    they haven't, I then need to openly publicly distinguish our qualitative correlation from our quantitative validation.

    We have not conclusively established a measured relationship between
    calculated curvature and actual tread-depth loss per mile. Nor have we conducted controlled experiments measuring tire wear over known mileage.

    We simply have the observed tribal knowledge database of decades of having
    tire shops declare we "abused" our front tires, even as we merely drove normally on mountain roads for decades of daily slow-speed downhill
    commutes. (Note: We assess the wear is heavily anchored to downhill sharp low-speed curves, and not uphill traction or weight transfer as it's always only the front tires which exhibit the abnormal outboard-shoulder wear
    within as little as a hundred miles, but certainly visible within 3K or 4K.

    A. So, if by measured data you mean actual tread-depth measurements
    taken at known mileage intervals, the very clear answer is no.

    B. If you mean real-world observations of which tire shoulders clearly
    exhibit abnormal wear on particular roads, the answer is yes.

    C. Piergiorgio:
    Why ask for additional roads if we already have observations?

    Because I want to extend the comparison beyond our own community.

    We have our original observations and approximately half a dozen local-road analyses. What we don't have is a sufficiently broad collection of
    independent mountain-road examples from other communities who also have experienced abnormal tire wear on mountain roads to the point that even
    Costco refuses to replace tires even with valid alignment check proof.

    The additional roads asked in the original post serve two purposes:

    1. Obtain independent road geometry for comparison with our experience.
    2. Compare that road geometry to observed wear patters for their commute.

    Note that I'm not asking anyone to supply a road without any associated observations and then pretend that running Python against its GPX file validates a tire-wear hypothesis. It might. But it might not.

    How would we know w/o knowing the tire wear for *that* particular commute?

    There are many ways for people to contribute to this unique dissuasion,
    where the a useful contribution would be someone familiar with a particular mountain road who has also observed the characteristic front-tire shoulder wear, or someone who has a better mapping program than the ones I employed
    to calculate the inherency of a given mountain road (e.g., the python
    script doesn't yet take elevation or cross slope into account).

    Speaking of cross slope, it would be GREAT if we can add that to the calculations given on one-lane mountain roads, there is no 'crown'.

    On one-lane mountain residential roads, there is a drainage cross slope
    which is never angled to the cliff side but which is always tipped into the mountain wall. It's a simple single-pitch cross slope (sometimes referred
    to generally as crossfall or transverse slope) for drainage purposes.

    When the water needs to drain over the cliff, culverts are introduced. Otherwise, the water *always* drains 1 to 1-1/2 degrees into the wall.

    I was hoping perhaps the gps-mapping newsgroup could help us determine what that pitch was for any given curve as the bank angles are perhaps a
    meaningful factor. (Note they are not currently factored into the python
    script road inherency calculations since we don't have the input data.)

    One further clarification about the current program that I must make clear,
    as I had initially assumed people would read the code's comments.
    *The Python script does not attempt to calculate tire wear.*

    The Python script simply extracts geometric characteristics from tracks, including local corner radii and left/right curvature distributions.
    *It doesn't calculate steepness, nor the aforementioned crossfall.*

    The next step is to improve the relationship between those road
    characteristics and the physical mechanisms that might explain the observed wear. That's where the three areas of expertise becomes crucial!
    1. Mapping: More accurate road geometry, elevation and grade.
    2. Python/Windows: Better algorithms and road-characteristic comparisons.
    3. Automotive engineering: Understanding tire loading, suspension
    behavior, camber effects and steering-induced scrub.

    In summary, I apologize for reacting to the unhelpful trolls and in doing
    so, I misconstrued Piergiogio's & Keith's purposefully helpful queries.

    I agree with Piergiorgio that without appropriate observations, we cannot establish whether a model correctly explains tire wear, but we can
    investigate the road geometry for comparative purposes, and then we should
    be able to develop an hypotheses after comparing independent cases and identifying and incorporating what additional measurements are needed.

    That's precisely what I'm trying to accomplish.
    *Thanks for asking for clarification, Pieriorgio, Keith & Carlos.*

    I hope this makes the experimental approach considerably clearer so that
    the three groups can work together to improve the tools previously posted.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 09:57:33 2026
    From Newsgroup: comp.lang.python

    On 11/5/2026 9:11 AM, Maria Sophia wrote:
    Keith Thompson wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads. >>>
    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >>> in your community, I will run a python script (I just wrote) on those roads >>> to predict the abnormal wear the front outboard tire shoulders will incur. >>>
    To limit the number of datapoints, since I'm running Python on an 2009
    Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>
    What exactly do you mean by "how well" the script works?

    Disclaimer: I don't drive on mountain roads, I haven't examined
    your Python code, and I'm not planning to run it.

    Your script, if I understand correctly, predicts tire wear resulting
    from driving on mountain roads. Are you comparing the script's
    predictions to actual measured wear resulting from driving those
    roads?

    I've been following this thread, and I see it's led to some insults
    (which I largely don't care about) but I don't recall any mention
    of measured data from actual tires. It's possible I've missed it;
    if so, please point me to the information I missed.

    Carlos E. R. wrote:
    You still have not answered Keith question, which is the same as
    Piergiorgio Sartor did. I also have the same doubt. You refuse to
    answer, that's clear, but I don't understand why. You are surely
    intelligent enough to understand the question...

    Hi Carlos,

    Ah! My bad. I goofed. Mea culpa.

    I apologize for falling into the trap of reacting to the uneducated trolls (mainly, Hank Rogers, Bob West, Old McDonald) so I will reset my response.

    By reacting to the uneducated trolls, I wasted everyone's valuable time.

    There are explicit reasons why intelligent people were asked to help:
    a. The mapping ng can help us obtain road inherency metrics
    b. The Python/OS ngs can help us write the calculation/prediction code
    c. The automotive ng can help model the shoulder-rollover camber scrub

    To help us all improve the tool, the questions from Keith is fair.
    From his question, I realize I haven't explained the background adequately, and my earlier responses didn't directly answer what you were asking.

    Let me try again since there are multiple aspects to this investigation.

    1. The existing real-world observations

    Our local Santa Cruz Mountain community has experienced decades observing a particular type of abnormal front-tire outside-shoulder wear on our steep, winding roads, which we've been discussing lately on our local reflectors.

    Our local community includes approximately 5,000 mountain residents.

    Over the years, we've exchanged photographs and discussed similar wear patterns on numerous vehicles with different drivetrains, suspension configurations and alignments. We've even set up roadblocks, in the past,
    on weekends, to stop all vehicles and examine their tire wear patterns.

    We set up a weekend visit to all mountain homes that accepted our request
    to document their abnormal tire wear in the past, so the abnormal tire wear is well known to us in our specific mountain community.

    Recurring examples emerged in out studies of local abnormal tire wear.
    a. Road A: Predominantly premature front-left outside-shoulder wear.
    b. Road B: Predominantly premature front-right outside-shoulder wear.
    c. Road C: Relatively equal premature outside-shoulder wear on both.

    These observations motivated the investigation.
    They weren't conclusions generated by the Python program.
    In fact, the Python program doesn't even make conclusions or predictions.

    2. The Python analysis

    After decades of study as shown above, and during a recent spate of complaints that the local Costco wouldn't even honor the first scheduled rotation on new tires, I developed the previously included Python program
    on my Windows PC (which should work on macOS & Linux equally well) to
    examine road geometry, particularly corner radii and the distribution of left-hand and right-hand turns, but note that I didn't add the steepness, which is also a factor given the initial braking sets up the tire wear.

    The intention was to investigate whether inherent road geometry, combined with downhill braking and steering-related tire loading, could help
    calculate road metrics such that we can explain the data that we've all
    seen, where some roads wear the left, some the right, and some both.

    Therefore we needed a method of obtaining/comparing road inherency metrics.

    As noted in the original post, I first tested the program against approximately half a dozen local mountain roads, where its qualitative predictions were consistent with the representative observations above.

    However, I want to be precise about what that Python script establishes.
    The current program analyzes road geometry so that we can compare roads.

    The Python script makes no attempt to calculate actual tread loss, predict miles to the wear bars or establish a quantitative relationship between curvature and tire life. It simply compares road inherency metrics.

    Clearly, we haven't conducted a controlled experiment measuring tread-depth loss over known mileage on the Utah roads, but my hope was to find other experienced mountain commuters with whom we can compare road inherency metrics to correlate to THEIR particular front-tire shoulder wear patterns.

    3. Why I asked this group for help

    The original request was an attempt to extend the investigation beyond our local roads and to obtain expertise that our community might not have.

    Specifically:
    a. Mapping expertise:
    Better GPX tracks, road geometry, elevation and grade information.
    b. Python expertise:
    Improved algorithms and more sophisticated calculations.
    c. Automotive engineering expertise:
    Tire loading, suspension behavior, camber effects
    and steering-induced tire scrub on downhill right-radius curves.

    I was hoping to have intelligent people suggest roads they knew well so
    that we could compare their tire-wear observations on their mountain
    geometry with our existing mountain observations to improve the model.

    Keith, your question about comparing predictions with actual measured tire wear is entirely legitimate. That's an important distinction between a plausible model and a quantitatively validated one.

    Carlos, I wasn't deliberately refusing to answer. I was trying to explain
    the broader background, but I can see that I wasn't answering the specific question being asked, as I was unduly flustered by the ignorant trolls.

    I apologize.
    I should have made the distinction clear from the beginning.

    I'm not claiming that the present Python script proves a universal
    tire-wear theory. I'm trying to develop and improve a model that might explain a phenomenon we've observed repeatedly in the real world.

    Constructive criticism, better algorithms and additional expertise are precisely what I was hoping to get from this discussion.

    Specifically:
    a. Mapping newsgroup: How to get better road-inherency metrics?
    b. Python newsgroup: How to improve the road-inherency comparisons?
    c. Automotive newsgroup: How to predict/explain the abnormal tire wear?

    Does that answer your concerns so we can improve the tools together?

    It's not the tool per se.

    Yes, there is an actual problem but no, there is no
    practical solution. Dramatically reducing vehicle speed
    would change the wear rates, but no one's going to do that
    willingly. A few billion or tens of billions of dollars for
    rock demolition, bridge spans and roadbuilding generally
    might reduce tire wear rates but I'd bet the residents
    wouldn't stand for the change of scenery and the taxpayers
    wouldn't go along willingly either.

    So, at best, your program may predict tire replacement
    intervals but hasn't provided any actual resolution.
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 12:36:50 2026
    From Newsgroup: comp.lang.python

    AMuzi wrote:
    Nice summary of the details and hat's off to you for making
    the effort.

    After a few years of comparing predicted mileage against
    actual mileage, you'll probably be able to correct any
    errors in your code.

    Thanks for the appreciation and for the constructive perspective and the recognition of the effort involved in this decades-long modeling effort.

    We actually do have real-world evidence of premature tire wear over known mileage. For example, tires with an expected service life of approximately 50,000 miles have exhibited severe outside-shoulder wear after only 10,000 miles of mountain commuting. It can be felt after as little as 100 miles!

    It's ONLY on the front tires.
    And only on the outboard shoulder.

    What we don't yet have is a controlled quantitative dataset connecting
    measured tread-depth loss to specific calculated road characteristics.

    We'll never have it as we're not researchers paid to perform the tests.

    That's an important distinction. We have observed the phenomenon repeatedly over decades of a daily commute which is DIFFERENT from our previous
    decades of daily commutes (and, not surprisingly, those who left the
    mountains for flatland tell us their tires now last normal distances).

    Slow driving on one-lane non-crowned steep canted roads is "abnormal".
    a. Tire shops notice the abnormality instantly.
    b. They claim we "abused" our front tires.
    c. And, in a way, we did.

    Yet, some commutes prematurely wear the passenger outboard shoulder more
    than the driver outboard shoulder, while most wear both just about evenly.

    That's what the Python script attempted to quantize, compare & predict.
    That's why mapping, programming, os and automotive groups are involved.

    First, a little background about the investigation.

    I've been studying this downhill-scrub phenomenon, off and on, for decades.
    a. It's something that hits us the first year we've moved to the mountains.
    b. And it leaves us, the first year anyone moves into flatland from here.
    c. That's repeatable.

    It's a familiar pattern among people who move into the mountains and begin commuting daily on steep, winding roads, which is why I concisely asked for other commuters' experiences in the first post of this thread.

    The abnormal outside-shoulder wear on front tires is something many
    mountain residents instantly encounter, discuss and compare notes about.

    As noted, in our Santa Cruz Mountains community, we've accumulated
    photographs and observations from numerous residents driving different vehicles, with different drivetrains and suspension configurations.

    We've repeatedly observed three general patterns:
    1. Predominantly front-left outside-shoulder wear.
    2. Predominantly front-right outside-shoulder wear.
    3. Relatively equal outside-shoulder wear on both front tires.

    That's what originally motivated me to investigate whether inherent road geometry, combined with vehicle dynamics, could help explain the recurring
    wear patterns.

    1. Improving the road geometry measurements

    As noted, the current Python program calculates circumcircles through three consecutive GPX points.

    That approach has limitations:
    a. Calculated radii are sensitive to GPX sampling density.
    b. Different mapping or tracing methods can produce different results
    c. Multiple consecutive measurements may represent one physical corner
    rather than independent corners.

    For example, the reported 2.04-meter minimum radius for Guardsman Pass is
    an example that deserves investigation as I'm unfamiliar with Utah roads.

    Given the goal is always to extend our success to everyone, I'd welcome suggestions for better methods of obtaining consistent road geometry.

    2. Incorporating additional road characteristics

    As noted, the current program examines curvature and left/right turning distributions, but it doesn't yet incorporate elevation, longitudinal grade
    or pavement crossfall.

    Crossfall is particularly interesting in our Santa Cruz Mountains.

    Many of our narrow, single-lane residential mountain roads don't have a conventional crowned pavement. Instead, they have a single drainage cross-slope, almost always (if not always) tipped toward the mountain wall.

    In our experience speaking with the county, this is around 1 to 2 degrees,
    with drainage culverts added where water must cross toward the cliff side.

    While I can add elevation to the python script, I'd like to investigate
    with the mapping ng whether we can obtain or estimate the crossfall through individual curves and incorporate it into the road-characteristic dataset.

    There is an important distinction between road crossfall, superelevation
    and vehicle body roll, so I'm not assuming these are interchangeable measurements.

    GPS elevation data alone may not provide sufficient accuracy for pavement crossfall. Perhaps someone familiar with surveying, mapping or terrain data
    can suggest a better approach.

    3. Understanding the automotive mechanics

    Another missing piece is translating road characteristics into actual tire loading. Our working hypothesis involves the combination of downhill
    braking, cornering, suspension geometry and steering-related tire scrub.

    However, a count of left/right curvature observations is not equivalent to
    a measurement of lateral tire forces or outside-shoulder wear.

    I'd particularly welcome input from automotive engineers familiar with:
    a. Front-axle load transfer during downhill braking.
    b. Lateral load transfer during cornering.
    c. Suspension geometry and camber changes.
    d. Tire contact-patch loading.
    e. Road banking and crossfall.
    f. Steering-induced tire scrub at relatively low speeds.

    4. Eventually comparing against actual tire wear

    We already have decades of qualitative observations from our local mountain community, including photographs and recurring examples of left-front, right-front and bilateral outside-shoulder wear, and, reassuring examples
    of when people leave the mountains for flatland, shoulder wear disappears.

    What we don't yet have is a controlled dataset of tread-depth loss over
    known mileage. We may never have that as we're not paid professionals.

    I agree that collecting such measurements would be valuable, but I think we cans till make substantial progress working together, first by improving
    the road measurements and understanding the physical mechanisms.

    The immediate objective isn't to predict that a particular tire will reach
    its wear bars after 12,000 miles.

    It's to compare how certain inherent mountain-road geometries might produce different but predictable patterns of abnormal front-tire shoulder wear.

    If we can establish a defensible relationship between road geometry,
    vehicle dynamics and the observed wear patterns, quantitative mileage predictions could become a subsequent research objective.

    I agree with your broader point about models needing to be tested against real-world observations. That's precisely why I'm interested in bringing together mapping, programming and automotive engineering expertise.

    Thanks again for the thoughtful response. This is exactly the sort of constructive technical discussion I was hoping to encourage .
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 12:58:05 2026
    From Newsgroup: comp.lang.python

    AMuzi wrote:
    Constructive criticism, better algorithms and additional expertise are
    precisely what I was hoping to get from this discussion.

    Specifically:
    a. Mapping newsgroup: How to get better road-inherency metrics?
    b. Python newsgroup: How to improve the road-inherency comparisons?
    c. Automotive newsgroup: How to predict/explain the abnormal tire wear?

    Does that answer your concerns so we can improve the tools together?

    It's not the tool per se.

    Yes, there is an actual problem but no, there is no
    practical solution. Dramatically reducing vehicle speed
    would change the wear rates, but no one's going to do that
    willingly. A few billion or tens of billions of dollars for
    rock demolition, bridge spans and roadbuilding generally
    might reduce tire wear rates but I'd bet the residents
    wouldn't stand for the change of scenery and the taxpayers
    wouldn't go along willingly either.

    So, at best, your program may predict tire replacement
    intervals but hasn't provided any actual resolution.

    THANK YOU!

    You bring up a great point that all the theory in the world doesn't change
    the fact that our 50K expected-life tires last only 15K to 20K even with rotations, due to the abnormal wear on the outboard front shoulders.

    One amelioration, of course, is a directed rotation pattern, which is the
    same as many but DIFFERENT from others as the "driving wheels" don't
    influence the cross-rotation pattern so much as the FRONT wheels do.

    That is, there are well-established cross-rotation patterns which take into account the driving wheels when "flipping the carcass" (asymetric treads).

    But the rotation pattern we've collectively come up with is thus:
    1. First rotation:
    a. Move the front wheels to the rear (keeping rotation direction)
    b. Move the rear wheels to the front (keeping rotation direction)

    2. Second rotation: (assuming non-whitewall asymmetric treads)
    a. Move the front wheels to the rear (keeping rotation direction)
    b. Flip the carcass on the rear wheels (outboard side inboard)
    c. Cross rotate the rear wheels to the front (keeping rotation)

    3. Repeat as needed (there are few rotations since the tires still wear).

    Note that we've studied the old wives' tale myth about radial tire carcass rotation direction and we've found it might have been a factor when radial tires first came out, but nobody today says not to change direction for
    tires that are able to be flipped.

    Yes. We are aware of various fundamental styles of tread patterns:
    a. Directional
    b. Non-directional
    c. Symmetric across the centerline, versus asymmetric across it
    d. Whitewall on one side only

    Clearly I fully agree with your pragmatic assessment, although I think
    there may be more practical mitigation options than dramatically reducing vehicle speed or rebuilding mountain roads.

    The purpose of the program isn't necessarily to eliminate the underlying
    road geometry problem. It's to understand the mechanism well enough that we
    can identify practical ways to reduce its consequences.

    In fact, we've already experimented with two possible mitigation approaches
    in our local mountain community.

    1. Increasing front negative camber

    We've experimented with increasing front negative camber to compensate for
    the outside-shoulder loading associated with repeated cornering.

    The hope is to compensate for expected loading forces by modifying the
    static alignment to better accommodate the dynamic camber changes and tire loading encountered on these roads for the outside tire outboard shoulder.

    Of course, there's a tradeoff when we commute into the Silicon Valley
    flatland, where too much negative camber can move the abnormal wear toward
    the inside shoulder, in addition to affecting handling.

    2. Increasing tire pressure slightly

    We've also experimented with increasing tire pressure by a few PSI, within appropriate operating limits, to increase sidewall stiffness to better
    combat tire deformation which helps to mitigate outside-shoulder wear.

    Again, this isn't necessarily a universal solution. Tire construction,
    vehicle weight, suspension geometry and operating conditions all matter.

    As you note, these are practical variables that mountain commuters can implement without waiting for a billion-dollar road reconstruction project.

    3. Why I'm interested in the road geometry

    What I really want to understand is why one mountain road appears to
    produce predominantly left-front outside-shoulder wear, another
    predominantly right-front wear, and another relatively equal wear on both
    front tires.

    If we can identify the geometric characteristics responsible for those differences, we may be able to make better-informed decisions about
    alignment settings, tire selection, inflation pressure and other mitigation strategies.

    For example, knowing that a particular commute has a sustained downhill sequence of tight right-hand curves is potentially more useful than simply knowing that someone lives in the mountains.

    The current Python program is only an initial attempt to quantify those
    road characteristics.

    4. I agree that a prediction without a practical application has limited
    value.

    I'm not proposing that mountain residents rebuild their roads, nor am I suggesting that everyone should dramatically reduce their commuting speeds.

    I'm trying to understand the physical mechanism behind a recurring and expensive problem, then determine whether relatively inexpensive vehicle
    setup changes can reduce its effects.

    If we can improve the model sufficiently to identify which road
    characteristics are associated with which wear patterns, we might
    eventually be able to recommend more appropriate tire, alignment and
    suspension configurations for particular mountain-driving conditions.

    That's a considerably more achievable objective than rebuilding the Santa
    Cruz Mountains.

    I'd be particularly interested in seasoned automotive perspectives on
    whether the negative-camber and tire-pressure approaches are addressing the likely mechanisms, or whether there are other practical variables we should investigate.

    Thanks for raising the practical side of the problem.
    It's an important part of the investigation.

    What do automotive guys think of the camber/pressure/rotation resolutions?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 13:01:03 2026
    From Newsgroup: comp.lang.python

    Maria Sophia wrote:
    asymmetric

    Thinko. 'symmetric' treads.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E. R.@robin_listas@es.invalid to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 20:49:40 2026
    From Newsgroup: comp.lang.python

    On 2026-11-05 16:11, Maria Sophia wrote:
    Keith Thompson wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    ...


    Specifically:
    a. Mapping newsgroup: How to get better road-inherency metrics?
    b. Python newsgroup: How to improve the road-inherency comparisons?
    c. Automotive newsgroup: How to predict/explain the abnormal tire wear?

    You are also posting to Windows ng.

    Does that answer your concerns so we can improve the tools together?

    Yes, thank you.
    --
    Cheers,
    Carlos E.R.
    ESEfc-Efc+, EUEfc-Efc|.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 14:18:10 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> writes:
    [...]
    I goofed!

    I humbly apologize as I errantly conflated Sergio & Keith's intentionally helpful questions about the methodology with those of the intentionally unhelpful ignorant trolls (Bob West, Old McDonald & Hank Rogers).

    Apology cheerfully accepted.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Hank Rogers@Hank@nospam.invalid to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 18:55:32 2026
    From Newsgroup: comp.lang.python

    Old McDonald wrote on 11/4/2026 6:46 PM:
    On 11/4/26 15:04, Hank Rogers wrote:
    Maria Sophia wrote on 11/4/2026 4:22 PM:

    The point of Usenet is for smart people to help each other & for results >>> to be archived so that anyone can access our immense tribal knowledge.

    Yes indeed Mary.-a When will you start this new tribal project?

    He's circling the drain.
    He posts the stupidest sigs.

    He has some good ideas, but I think he has the same brain worms that
    infected RFK.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From AMuzi@am@yellowjersey.org to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Thu Nov 5 19:03:33 2026
    From Newsgroup: comp.lang.python

    On 11/5/2026 6:55 PM, Hank Rogers wrote:
    Old McDonald wrote on 11/4/2026 6:46 PM:
    On 11/4/26 15:04, Hank Rogers wrote:
    Maria Sophia wrote on 11/4/2026 4:22 PM:

    The point of Usenet is for smart people to help each
    other & for results
    to be archived so that anyone can access our immense
    tribal knowledge.

    Yes indeed Mary.-a When will you start this new tribal
    project?

    He's circling the drain.
    He posts the stupidest sigs.

    He has some good ideas, but I think he has the same brain
    worms that infected RFK.


    Sen (NY) RFK Sr or health nut RFK Jr?
    --
    Andrew Muzi
    am@yellowjersey.org
    Open every day since 1 April, 1971
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Fri Nov 6 01:46:23 2026
    From Newsgroup: comp.lang.python

    On Nov 5, 2026 at 10:58:05rC>AM CST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

    AMuzi wrote:
    Constructive criticism, better algorithms and additional expertise are
    precisely what I was hoping to get from this discussion.

    Specifically:
    a. Mapping newsgroup: How to get better road-inherency metrics?
    b. Python newsgroup: How to improve the road-inherency comparisons?
    c. Automotive newsgroup: How to predict/explain the abnormal tire wear? >>>
    Does that answer your concerns so we can improve the tools together?

    It's not the tool per se.

    Yes, there is an actual problem but no, there is no
    practical solution. Dramatically reducing vehicle speed
    would change the wear rates, but no one's going to do that
    willingly. A few billion or tens of billions of dollars for
    rock demolition, bridge spans and roadbuilding generally
    might reduce tire wear rates but I'd bet the residents
    wouldn't stand for the change of scenery and the taxpayers
    wouldn't go along willingly either.

    So, at best, your program may predict tire replacement
    intervals but hasn't provided any actual resolution.

    THANK YOU!

    You bring up a great point that all the theory in the world doesn't change the fact that our 50K expected-life tires last only 15K to 20K even with rotations, due to the abnormal wear on the outboard front shoulders.

    One amelioration, of course, is a directed rotation pattern, which is the same as many but DIFFERENT from others as the "driving wheels" don't influence the cross-rotation pattern so much as the FRONT wheels do.

    That is, there are well-established cross-rotation patterns which take into account the driving wheels when "flipping the carcass" (asymetric treads).

    But the rotation pattern we've collectively come up with is thus:
    1. First rotation:
    a. Move the front wheels to the rear (keeping rotation direction)
    b. Move the rear wheels to the front (keeping rotation direction)

    2. Second rotation: (assuming non-whitewall asymmetric treads)
    a. Move the front wheels to the rear (keeping rotation direction)
    b. Flip the carcass on the rear wheels (outboard side inboard)
    c. Cross rotate the rear wheels to the front (keeping rotation)

    3. Repeat as needed (there are few rotations since the tires still wear).

    Note that we've studied the old wives' tale myth about radial tire carcass rotation direction and we've found it might have been a factor when radial tires first came out, but nobody today says not to change direction for
    tires that are able to be flipped.

    Yes. We are aware of various fundamental styles of tread patterns:
    a. Directional
    b. Non-directional
    c. Symmetric across the centerline, versus asymmetric across it
    d. Whitewall on one side only

    Clearly I fully agree with your pragmatic assessment, although I think
    there may be more practical mitigation options than dramatically reducing vehicle speed or rebuilding mountain roads.

    The purpose of the program isn't necessarily to eliminate the underlying
    road geometry problem. It's to understand the mechanism well enough that we can identify practical ways to reduce its consequences.

    In fact, we've already experimented with two possible mitigation approaches in our local mountain community.

    1. Increasing front negative camber

    We've experimented with increasing front negative camber to compensate for the outside-shoulder loading associated with repeated cornering.

    The hope is to compensate for expected loading forces by modifying the
    static alignment to better accommodate the dynamic camber changes and tire loading encountered on these roads for the outside tire outboard shoulder.

    Of course, there's a tradeoff when we commute into the Silicon Valley flatland, where too much negative camber can move the abnormal wear toward the inside shoulder, in addition to affecting handling.

    2. Increasing tire pressure slightly

    We've also experimented with increasing tire pressure by a few PSI, within appropriate operating limits, to increase sidewall stiffness to better
    combat tire deformation which helps to mitigate outside-shoulder wear.

    Again, this isn't necessarily a universal solution. Tire construction, vehicle weight, suspension geometry and operating conditions all matter.

    As you note, these are practical variables that mountain commuters can implement without waiting for a billion-dollar road reconstruction project.

    3. Why I'm interested in the road geometry

    What I really want to understand is why one mountain road appears to
    produce predominantly left-front outside-shoulder wear, another
    predominantly right-front wear, and another relatively equal wear on both front tires.

    If we can identify the geometric characteristics responsible for those differences, we may be able to make better-informed decisions about
    alignment settings, tire selection, inflation pressure and other mitigation strategies.

    For example, knowing that a particular commute has a sustained downhill sequence of tight right-hand curves is potentially more useful than simply knowing that someone lives in the mountains.

    The current Python program is only an initial attempt to quantify those
    road characteristics.

    4. I agree that a prediction without a practical application has limited value.

    I'm not proposing that mountain residents rebuild their roads, nor am I suggesting that everyone should dramatically reduce their commuting speeds.

    I'm trying to understand the physical mechanism behind a recurring and expensive problem, then determine whether relatively inexpensive vehicle setup changes can reduce its effects.

    If we can improve the model sufficiently to identify which road characteristics are associated with which wear patterns, we might
    eventually be able to recommend more appropriate tire, alignment and suspension configurations for particular mountain-driving conditions.

    That's a considerably more achievable objective than rebuilding the Santa Cruz Mountains.

    I'd be particularly interested in seasoned automotive perspectives on
    whether the negative-camber and tire-pressure approaches are addressing the likely mechanisms, or whether there are other practical variables we should investigate.

    Thanks for raising the practical side of the problem.
    It's an important part of the investigation.

    What do automotive guys think of the camber/pressure/rotation resolutions?

    First, I'll ignore your insults because even though I used to think that you are a nutcase, I've downgraded that to just another quirky personality on usenet. But I am an automotive guy, so you addressed me.

    The first problem is that you keep saying "road inherence". That is used in
    the context of a problem that needs solving. You have finally admitted above that there is a problem, but it's not really solvable in any practicable manner. My problem with what you are doing is that your python exercise
    amounts to coding masturbation. It might satisfy you, but it serves no
    purpose. Everyone sentient being knows that everything you describe causes accelerated tire wear. You don't need maps of anything to know that, and about .000001% of the earth's population would be concerned with any solution that involved any effort or expense. F1 teams could be interested in your script, but they already have all the data, and most importantly they have actual measurements of tire wear. You are not breaking ground here. You can even get that kind of date in sim-racing apps.

    And you keep complaining that tire shops won't warranty tires with the sort of wear you are describing. They don't, but only because there is nothing wrong with the tires. They are working as designed. The original post about this referred to a full size GM SUV. I worked in Las Vegas and saw a lot of the
    tire wear you describe on those vehicles, and you clearly know that area is pretty flat. There are just too many variations in all the factors included in this to ever come up with any helpful info or solutions. And the reason I brought up bushings is that you included steering geomety in causes, and soft bushings change the steering geometry. That is why there is a pretty good market for aftermarket stiff bushings.

    My thought on your resolutions? I had a VW. Their advice was to never rotate, and as each pair wears out, you just replace that pair. I have used that
    advice forever. I keep the vehicles aligned and the tires balanced, and have never had any tires wear out at any premature mileage. Performance tires? They wear out quick. HIgh mileage tires? Lower traction. There are tradeoffs. You are obsessing over nothing at all. That's why I downgraded you to just another quirky personality.

    Whatever happened to nospam? He fell off the face of the earth. Is he dead?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Fri Nov 6 14:29:25 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    What do automotive guys think of the camber/pressure/rotation resolutions?

    First, I'll ignore your insults because even though I used to think that you are a nutcase, I've downgraded that to just another quirky personality on usenet. But I am an automotive guy, so you addressed me.

    Wow. I'm impressed. Really.
    Thank you for writing a post worthy of an adult purview.

    Most posters invest 3 seconds in denying all facts that they're unaware of. Which, as it turns out, is all facts.

    But your article that I'm responding to is different.

    First off, in all my decades of posting to Usenet, I treat people as they
    treat me, no matter how they treated me in the past, as, to me, Usenet is
    water under the bridge. If you act like an adult, I'll treat you as such.

    I'm not afraid to call you out when you troll, just as I'll treat you respectfully when you actually say something that is worth considering.

    As for "quirky personality", there are likely only a handful of people on
    any of these newsgroups who are as purposefully helpful as I am, although plenty have far more knowledge than I do in the areas required here
    1. mapping (we need to obtain better road inherence data)
    2. programming (we need to add curve, slope and bank angle improvements)
    3. automotive (we need to focus on what affects downhill outboard wear)

    Since you mentioned you're an "automotive guy", and since you're well aware that my engineering training is in the electrical field, if you have an education (which none of the trolls turn out to have), that will be useful.

    My only formal education on suspension was back in the 1960s when I took
    all sorts of technical training just for the fun of it, which is why I can, even today, mount & balance my own tires & do my suspension checks at home.

    But we have been discussing specific elements of camber scrub for decades. Unfortunately, most of the Usenet search engines no longer go back far.

    For example, this only gets us to 2016, which is 16 years too late.
    <https://newsgrouper.org/rec.autos.tech/search/list> search for "camber"
    For example, <https://newsgrouper.org/rec.autos.tech/search/1481216441>
    Advice requested from those of you who have successfully checked camber at home
    Date: Thu, 8 Dec 2016 17:00:41 -0000 (UTC)

    I'm pretty sure it was "Zeno" (spelling?) who first turned the entire rec.autos.tech newsgroup on to the special type of wear we called "camber scrub" at the time, but which doesn't really have its own mountain naming.

    It's specific to slow loaded sharp downhill turns on mountain roads alone. (i.e., not racing, even in the chicane, due to the speed differences)

    The first problem is that you keep saying "road inherence". That is used in the context of a problem that needs solving. You have finally admitted above that there is a problem, but it's not really solvable in any practicable manner.

    Saying we've "finally admitted" there's a problem which is "not really solvable" does a disservice to our decades-long attempt to ameliorate it.

    We are very intelligent people who are very well educated, and as such, we don't easily give up on problems just because they're not easy to solve.

    They paid me the big bucks to retire at age 50 in the Silicon Valley for a reason & that reason was not because I gave up when the problem was hard.

    We have educated engineering professors on our email reflector in the Santa Cruz Mountains who *can* get 50K miles on a tire, on the roughest roads.

    In fact, here's an excerpt from *that* Stanford professor, who gave us hope that it can be done, &, in reality, who sparked me to write the code
    comparing his commute to my commute (since nobody on my hill can get
    anywhere near those kinds of miles on the inherence of our mountain road).

    -------- Begin Forwarded Message --------
    Subject: Why your front tires are unduly wearing the outside shoulder

    Tire wear is a subject of substantial interest to me, living at 3800' ASL
    at the end of XXXREDACTEDXXX Road, another windy, abrasive mountain road.
    Many years ago I bought a new Honda CRX, and I was stunned when the tires
    were worn out at just 3,000 miles! When I complained, the dealer said,
    "You're not supposed to drive it so hard." Bah.

    I've spent quite of bit of effort since then, and the last set of tires
    on my Mini Cooper JCW lasted 50,000 miles. In large part, this was a
    result
    of things I'd learned in auto racing, see my recent race-winning video at
    XXXREDACTEDXXX https://www.youtube.com/watch?v=XXXREDACTEDXXX.

    In setting up a race car, we adjusted camber and tire pressure to get the
    same temperature across the tread after several hard laps. If it was too
    hot on the outside, more negative camber (or vice versa). Then if it was
    too hot at the edges, raise the pressure to bulge the middle (again, or
    vice versa). That process made the average tread essentially flat for a
    given suspension setup, and lap times showed it. Of course our expectation
    of tire life was dramatically different, but today I still use a variation
    on these two techniques, and it's made a big difference.

    I do essentially the same process, without the temperature measurement,
    on our cars. Each car may have a different weight, drive wheels and
    suspension design, but especially on front-drive cars I start the front
    at the negative limit of factory settings, and go 1/2# more if I see
    excess wear on the outside. On some of our cars, we've had to install
    conservative suspension mods to do this. Then I typically run +2-3 psi
    pressure to keep the center working, and go even higher if I see too
    much wear at the edges. Especially on rear drive cars, I'm more
    conservative on the drive wheels, since they aren't steering.
    But the same concept applies.

    This optimizes the setup for the curvy, abrasive XXXREDACTEDXXX-mile road
    we drive fairly vigorously every time we're going anywhere. Since the tire
    wear is mostly from our runs up and down our hill, we don't find adapting
    to this use makes much difference in traction or wear in the rest of our
    driving on freeways or city streets. We're not racing, and we're not
    looking for the huge show-off negative camber you see sometimes, just
    enough to correct the car from general-driving setting to our primary use.

    But 50,000 miles? Yep, the secret is a tire that sticks very well,
    but has very high tread wear rating. I've settled on Michelin Pilot Sport
    All Season (we get snow up here, and I no longer feel like swapping
    seasonal tires). The tread wear rating on these is an amazing 540 with
    still good wet/dry traction, and they're guaranteed for 45,000 miles.

    Last, re reliable tire service, the jury is still out. I agree most
    places don't pay enough attention. One I won't name tightened the wheel
    lugs so tight I had to replace them, even though I told them the torque
    I wanted, and had the torque wrench with me. If I find a gem, I won't be
    shy.

    I hope this adds to your discussion.
    -------- End Forwarded Message --------

    My problem with what you are doing is that your python exercise
    amounts to coding masturbation. It might satisfy you, but it serves no purpose.

    I disagree. It compares the inherence between the various mountain roads.
    Does it not?

    Everyone sentient being knows that everything you describe causes
    accelerated tire wear. You don't need maps of anything to know that, and about
    .000001% of the earth's population would be concerned with any solution that involved any effort or expense. F1 teams could be interested in your script, but they already have all the data, and most importantly they have actual measurements of tire wear. You are not breaking ground here. You can even get that kind of date in sim-racing apps.

    See above where the Stanford professor, who is also a racer, disagrees with you. BTW, it's fine to disagree. As long as you make valid points, I've
    always, in my decades of posting on Usenet, have agreed with logically
    sensible assessments.

    Your assessment that this mountain-road abnormal-tire-wear phenomenon
    affects a small population is, clearly, true. That's why we asked in the original post for others with a similar steep and curvy daily commute.

    And you keep complaining that tire shops won't warranty tires with the sort of
    wear you are describing. They don't, but only because there is nothing wrong with the tires.

    Let's be clear. I'm observing a fact. That's not a complaint.
    Certainly I know why tire shops don't honor the warranty.

    They see front tires with extreme outboard shoulder wear.
    Even at the first scheduled rotation period!
    Yet, the rest of the tread is perfectly fine.

    Those "tire experts" (errantly) conclude it's the "alignment", of course. That's because they don't understand tire wear patterns on mountain roads.

    We do.

    But remember whom I'm communicating with on our 5000-home reflector.
    Lay people.

    THEY don't understand WHY their warranty claims are denied by Costco!
    Bear in mind we've identified fundamentally three types of local commutes:
    1. Those whose road inherence is predominately right or left turns
    2. And those whose road inherence is reasonably evenly matched in turns

    That alone explains why, when we stopped every vehicle on a weekend to
    inspect their tires, we found some were evenly abnormally worn, while
    others seemed to be more abnormally worn on one or the other front tire.

    They are working as designed. The original post about this
    referred to a full size GM SUV. I worked in Las Vegas and saw a lot of the tire wear you describe on those vehicles, and you clearly know that area is pretty flat. There are just too many variations in all the factors included in
    this to ever come up with any helpful info or solutions. And the reason I brought up bushings is that you included steering geomety in causes, and soft bushings change the steering geometry. That is why there is a pretty good market for aftermarket stiff bushings.

    No. That's just wrong. At least the implication you're trying to make.
    We are talking about one of the most expensive residential communities in
    the country, which is the surrounding hills around Silicon Valley.

    These cars are immaculately maintained. Bushings and all.
    The alignment is not wrong (on almost all of them).

    For a vehicle in flatland, for the wear patterns we are discussing, if the vehicle is properly maintained, the wear you claim is patently impossible (assuming the vehicle is well maintained & only drives typically on flats, i.e., they don't do 180's in the Las Vegas parking lots to wear the tires).

    Am I wrong?

    My thought on your resolutions? I had a VW. Their advice was to never rotate, and as each pair wears out, you just replace that pair. I have used that advice forever. I keep the vehicles aligned and the tires balanced, and have never had any tires wear out at any premature mileage.

    Everyone who does NOT drive daily on mountain roads would echo your experiences, but that says NOTHING about those who do drive mountain roads.

    Performance tires? They
    wear out quick. HIgh mileage tires? Lower traction. There are tradeoffs.

    As you know, I'm well educated, so I know that statement to be false.
    At least in terms of information printed on every passenger tire sold in
    the USA.

    But it's not really the point of this thread that I can find tons of
    passenger tires rated for high treadwear and also high wet straight-line traction, just as I can find passenger tires rated for low treadware and
    low straight-line traction, and every permutation in between.

    But that's simply because of the information printed on every USA passenger-tire sidewall is inherently insufficient to make any claims
    that treadwear and traction *must* oppose each other.

    In short, that's an interesting discussion for a different thread.

    You
    are obsessing over nothing at all. That's why I downgraded you to just another
    quirky personality.

    I'm different than most people on Usenet for a few reasons, one of which is
    I'm extremely knowledgeable, and part of that knowledge is gained by having
    an excellent memory on Usenet threads over the decades, where Zeno was instrumental in helping all of us understand, long ago, what's happening.

    I'm also very different from many Usenet posters as most seem to treat it
    as entertainment, and even fewer seem to have any education on the topics.

    I'm also different in that I have access to my old Stanford and Harvard professors, which most people here wouldn't have that kind of contact.

    In addition, I'm wired to the core to write helpful tutorials and PSAs as
    I'm someone who cares deeply that others can do what I can do.

    Still, I openly and publicly readily admit the python folks know
    programming better'n I do (I hate programming!). I just use it when I have
    to in order to make computers more efficient (as I'm inherently lazy).

    Also, I readily admit I'm NOT trained formally as a mechanical or
    automotive engineer, or a computer-science professional, even as I started taking classes at MIT in COBOL and PL/1 and Fortran IV when I was a kid.

    I learned to hate programming languages early in my life, but luckily, I
    took typing on those big green boat-anchor IBM Selectrics in order to be in
    the same class as my girlfriend (who wasn't in the advanced STEM courses).

    In addition, like most of you on these newsgroups, I've used GPS since we literally put laptops on our lap in the vehicle with a rooftop antenna, so
    I'm pretty good as laypeople go with using software to obtain the GPX
    tracks, but those tracks, while they can catch elevation, don't have the drainage (which, is NOT a crown shape!)

    I was asking for help, for those reasons, from groups who know more than I
    do about
    a. Mapping (we need the drainage slope if it's at all possible to obtain)
    b. Programming (we need to add elevation and likely more curve points)
    c. Suspension (we need to improve the road-inherence comparison)

    Whatever happened to nospam? He fell off the face of the earth. Is he dead?

    There's a recent thread from this week about him.
    Some say he was paid by Apple to deny everything bad about Apple on the iOS newsgroups, where when we pointed that out, he instantly disappeared.

    Who knows what really happened to him, or David Empson (who truly
    understood his stuff) or Michelle Steiner (who fought for the group to be included as misc.phone.mobile.iphone) or the Apple religious zealots JF
    Mezei or Alan Browne (both of whom believed every word in every Apple white paper).

    There's only Ant, and badgolferman, Chris and maybe we can include -hh,
    left who have any sense. Although, the uneducated trolls such as Jolly
    Roger, Alan Baker, Haemactylus, Joerg Lorenz, Snit, Rod Speed, and Your
    Name still post.
    --
    What's different about me from post Usenet posters is I'm well meaning.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sat Nov 7 11:01:57 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> wrote:
    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>> see how well the Linux/macOS/Win script works in roads elsewhere in the US. >>>
    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Perfect! Thank you for providing a random test sample, which helps
    us improve the program as it's tested on control conditions now.

    With more eyes on the program & results, we can improve it together!

    Which is impossible with python code posted on usenet as you cannot
    guarantee preservation of whitespace.

    As I've told you many times, it would be much more helpful for you to post
    code where it makes sense i.e. github

    Here's your code on a gh account thet only took 5 min to set up. Am sure
    you could do the same with a throwaway email address once you've verified
    it
    https://github.com/ithinkiam-ng/roadCurvature/blob/main/mountaincurves.py

    Of course, the code doesn't work given the issues above. I encourage Arlen
    to edit it to make it work.

    It is also impossible for others to test as we don't have an example
    dataset to run it on. I also encourage him to share a test file.

    My observations of the code are:

    * no consideration for the gradient of road. a significant issue on
    "mountain roads"

    * the curvature calc is hugely dependent on the gps track. Slight
    variations will make big differences.

    * the curvature calc is based only on three points which again is highly dependent on the gps resolution/accuracy. It could potentially find non-existent bends.

    * no checking of travel direction.

    * no checking of side of the road. A rh turn will naturally be tighter then
    a lh turn *of the same bend*.

    Given the above, have you tested the code for the same road but measured by different people at different times? Have you compared the script with real world, physical measurements of the bends?

    You really, really do need to add gradient information. You're completely ignoring the third dimension which is nonsensical. It's like drawing a
    straight line on a map of the world and saying that's the shortest route
    for a flight between LA and London.

    Of course, this whole exercise is based on the predicate of "abnormal"
    wear. It seems obvious that constantly driving up and down high gradient, twisty roads will wear tyres faster than a daily commute into the city.
    This is entirely *normal* and predicable wear.

    Finally, this is of course completely off-topic for a Windows 10 ng.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sat Nov 7 15:01:36 2026
    From Newsgroup: comp.lang.python

    Chris wrote:
    Maria Sophia <mariasophia@comprehension.com> wrote:
    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>>> see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Perfect! Thank you for providing a random test sample, which helps
    us improve the program as it's tested on control conditions now.

    With more eyes on the program & results, we can improve it together!

    Which is impossible with python code posted on usenet as you cannot
    guarantee preservation of whitespace.

    As I've told you many times, it would be much more helpful for you to post code where it makes sense i.e. github

    Here's your code on a gh account thet only took 5 min to set up. Am sure
    you could do the same with a throwaway email address once you've verified
    it
    https://github.com/ithinkiam-ng/roadCurvature/blob/main/mountaincurves.py

    Of course, the code doesn't work given the issues above. I encourage Arlen
    to edit it to make it work.
    It is also impossible for others to test as we don't have an example
    dataset to run it on. I also encourage him to share a test file.

    Hi Carlos,

    Wow. I'm impressed. Really. You added a *lot* of value to the team!
    Thank you.

    You even taught me some things (see below).
    I'll implement most of them, in fact.

    But first, the dataset...

    You're not the first person to think that I didn't include a "sample
    dataset" (i.e., a GPX file), but I actually did because I showed
    how to get the file (i.e., I 'taught a man how to fish for it').

    This *is* the dataset, for example, for the Moki Dugway GPX file.
    <https://gpx.studio/app#14.41/37.27473/-109.93787>

    Of course, I "could" have posted the GPX files but anyone can
    use the web site to get the same GPX file that I had used.
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>

    I showed in the code and in the writeups HOW to obtain the data set.

    For any given section of road, we can find the GPX inherence using this:
    <https://gpx.studio/>
    1. Open the appropriate road link listed below.
    2. Select File > New.
    3. Select the route-planning tool (pen icon).
    4. Select the appropriate routing mode (e.g., bicycle to stay on asphalt)
    5. Trace the complete road (or just click beginning & ending points).
    6. Select File > Export > Download GPX file.
    7. Save using the suggested road-based below filename.
    8. Run the Python analysis.
    python mountaincurves.py mokidugway.gpx
    python mountaincurves.py shafercanyon.gpx
    python mountaincurves.py burrtrail.gpx
    python mountaincurves.py guardsmanpass.gpx
    python mountaincurves.py angelescrest.gpx
    python mountaincurves.py mulholland.gpx

    For example, for the given unbiased kindly volunteered testcases,
    the python script generated an apples-to-apples commute comparison.

    Moki Dugway
    <https://gpx.studio/app#14.41/37.27473/-109.93787>
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    Shafer Canyon Road
    <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    <https://gpx.studio/app#15/38.45303/-109.82112>
    Burr Trail
    <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    <https://gpx.studio/app#14.55/37.85138/-111.03141>
    Guardsman Pass
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    <https://gpx.studio/app#13.81/40.61548/-111.52533>
    Angeles Crest Highway (CA-2):
    <https://gpx.studio/app#12.39/34.23487/-118.24127>
    <https://i.postimg.cc/dV8qhd8f/angelescrest.jpg>
    Mulholland Drive (Hollywood Hills):
    <https://gpx.studio/app#14/34.13106/-118.44057>
    <https://i.postimg.cc/8kB9fH36/mulholland.jpg>

    Note that I provided another more detailed method of obtaining a GPX
    file using the <https://overpass-turbo.eu/> web site as shown below.
    <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>

    My observations of the code are:

    * no consideration for the gradient of road. a significant issue on "mountain roads"

    Yup. Since we're ONLY looking at the DOWNHILL direction, the
    elevation needs to be taken into account. It's my first WIP.


    * the curvature calc is hugely dependent on the gps track. Slight
    variations will make big differences.
    * the curvature calc is based only on three points which again is highly dependent on the gps resolution/accuracy. It could potentially find non-existent bends.

    Yeah. I know. I don't like taking just 3 points in the curve.
    I need to assess the TYPE of curve, and take as many points as needed.

    That's my second WIP!

    * no checking of travel direction.

    You made me think about that, and you're right. I need to doublecheck
    that the GPX track is always downhill, and, what's worse, it can go
    over the hump, and then I have to decide how to calculate the wear points.

    This was NOT on my radar screen, but I've added it as the fourth WIP.
    I thank you for catching that lack of error-checking in the Python script.

    * no checking of side of the road. A rh turn will naturally be tighter then
    a lh turn *of the same bend*.

    That is completely correct but since the goal is to take only the DOWNHILL motion, that should not matter as there is only one direction of curve
    going in the downhill direction.

    Given the above, have you tested the code for the same road but measured by different people at different times? Have you compared the script with real world, physical measurements of the bends?

    The measurements come from the web sites, where I simply put a dot at the beginning of the road and another dot at the end, whenever possible.

    That means everyone would get almost the same GPX file out of any given
    road, as long as that road is simple enough that there's an obvious before
    and after (although I noticed a "loop" on a road Blaine suggested).

    You really, really do need to add gradient information. You're completely ignoring the third dimension which is nonsensical. It's like drawing a straight line on a map of the world and saying that's the shortest route
    for a flight between LA and London.

    What I'm missing is not only the grade (e.g., 9% or 10%) but also the pitch
    of the road for runoff, which is NOT crowned on our local roads.

    On our local roads, the cross slope is for drainage, and it always slopes
    into the mountain wall, so it's a different pitch per turn of a degree or
    two. This may be impossible to calculate so I may need to estimate it.

    I suspect it won't make a big difference, but I need to test it first.
    That's my third WIP.


    Of course, this whole exercise is based on the predicate of "abnormal"
    wear. It seems obvious that constantly driving up and down high gradient, twisty roads will wear tyres faster than a daily commute into the city.
    This is entirely *normal* and predicable wear.

    Well, it's "normal" wear for a steep twisty mountain road.

    And, more importantly, the mapping expertise, programming algorithms, and automotive suspension particulars are technical tidbits which have far-reaching implications in any similar exercise when comparing commutes.

    Thanks for looking at the code and suggesting improvements, almost
    all of which I easily agree with as I'm nothing if not sensible.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sat Nov 7 15:02:27 2026
    From Newsgroup: comp.lang.python

    Maria Sophia wrote:
    Hi Carlos,

    Wow. I'm impressed. Really. You added a *lot* of value to the team!
    Thank you.

    Oops. Chris!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sun Nov 8 10:49:59 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> wrote:
    Chris wrote:
    Maria Sophia <mariasophia@comprehension.com> wrote:
    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>>>> see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Perfect! Thank you for providing a random test sample, which helps
    us improve the program as it's tested on control conditions now.

    With more eyes on the program & results, we can improve it together!

    Which is impossible with python code posted on usenet as you cannot
    guarantee preservation of whitespace.

    As I've told you many times, it would be much more helpful for you to post >> code where it makes sense i.e. github

    Here's your code on a gh account thet only took 5 min to set up. Am sure
    you could do the same with a throwaway email address once you've verified
    it
    https://github.com/ithinkiam-ng/roadCurvature/blob/main/mountaincurves.py

    Of course, the code doesn't work given the issues above. I encourage Arlen >> to edit it to make it work.
    It is also impossible for others to test as we don't have an example
    dataset to run it on. I also encourage him to share a test file.

    Hi Carlos,

    Wow. I'm impressed. Really. You added a *lot* of value to the team!
    Thank you.

    You even taught me some things (see below).
    I'll implement most of them, in fact.

    Please, please use the github. Otherwise you're wasting yours and everyone else's time.


    But first, the dataset...

    You're not the first person to think that I didn't include a "sample dataset" (i.e., a GPX file), but I actually did because I showed
    how to get the file (i.e., I 'taught a man how to fish for it').

    This *is* the dataset, for example, for the Moki Dugway GPX file.
    <https://gpx.studio/app#14.41/37.27473/-109.93787>

    No it isn't. That's an app. Provide a file that can be used reproducible by anyone.

    Of course, I "could" have posted the GPX files but anyone can
    use the web site to get the same GPX file that I had used.
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>

    I showed in the code and in the writeups HOW to obtain the data set.

    For any given section of road, we can find the GPX inherence using this:
    <https://gpx.studio/>
    1. Open the appropriate road link listed below.
    2. Select File > New.
    3. Select the route-planning tool (pen icon).
    4. Select the appropriate routing mode (e.g., bicycle to stay on asphalt)
    5. Trace the complete road (or just click beginning & ending points).
    6. Select File > Export > Download GPX file.
    7. Save using the suggested road-based below filename.
    8. Run the Python analysis.
    python mountaincurves.py mokidugway.gpx
    python mountaincurves.py shafercanyon.gpx
    python mountaincurves.py burrtrail.gpx
    python mountaincurves.py guardsmanpass.gpx
    python mountaincurves.py angelescrest.gpx
    python mountaincurves.py mulholland.gpx

    The fact that you need to provide stepwise instructions means it's prone to error and variability.

    Supply a file. You could have done it far more quickly by now rather then repetitively responding to everyone why you aren't.

    For example, for the given unbiased kindly volunteered testcases,
    the python script generated an apples-to-apples commute comparison.

    Moki Dugway
    <https://gpx.studio/app#14.41/37.27473/-109.93787>
    <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    Shafer Canyon Road
    <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    <https://gpx.studio/app#15/38.45303/-109.82112>
    Burr Trail
    <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    <https://gpx.studio/app#14.55/37.85138/-111.03141>
    Guardsman Pass
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    <https://gpx.studio/app#13.81/40.61548/-111.52533>
    Angeles Crest Highway (CA-2):
    <https://gpx.studio/app#12.39/34.23487/-118.24127>
    <https://i.postimg.cc/dV8qhd8f/angelescrest.jpg>
    Mulholland Drive (Hollywood Hills):
    <https://gpx.studio/app#14/34.13106/-118.44057>
    <https://i.postimg.cc/8kB9fH36/mulholland.jpg>

    Note that I provided another more detailed method of obtaining a GPX
    file using the <https://overpass-turbo.eu/> web site as shown below.
    <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>

    You're providing further evidence that the dataset is not atomic and needs
    to be provided as examples.

    My observations of the code are:

    * no consideration for the gradient of road. a significant issue on
    "mountain roads"

    Yup. Since we're ONLY looking at the DOWNHILL direction, the
    elevation needs to be taken into account. It's my first WIP.


    * the curvature calc is hugely dependent on the gps track. Slight
    variations will make big differences.
    * the curvature calc is based only on three points which again is highly
    dependent on the gps resolution/accuracy. It could potentially find
    non-existent bends.

    Yeah. I know. I don't like taking just 3 points in the curve.
    I need to assess the TYPE of curve, and take as many points as needed.

    That's my second WIP!

    * no checking of travel direction.

    You made me think about that, and you're right. I need to doublecheck
    that the GPX track is always downhill, and, what's worse, it can go
    over the hump, and then I have to decide how to calculate the wear points.

    This was NOT on my radar screen, but I've added it as the fourth WIP.
    I thank you for catching that lack of error-checking in the Python script.

    * no checking of side of the road. A rh turn will naturally be tighter then >> a lh turn *of the same bend*.

    That is completely correct but since the goal is to take only the DOWNHILL motion, that should not matter as there is only one direction of curve
    going in the downhill direction.

    Yes, but the gps doesn't consider, on smaller roads, the side of the road you're driving on depending on direction of travel. It simply takes a parsimonious route in either direction.

    Given the above, have you tested the code for the same road but measured by >> different people at different times? Have you compared the script with real >> world, physical measurements of the bends?

    The measurements come from the web sites, where I simply put a dot at the beginning of the road and another dot at the end, whenever possible.

    So the answer is "no". You're assuming the code is correct without any
    external verification. And you've been looking at this for decades?!

    For one short route you have to walk it and measure the curvature of the
    bends by hand.

    Without any verification your code has the robustness of a random number generator.

    That means everyone would get almost the same GPX file out of any given
    road, as long as that road is simple enough that there's an obvious before and after (although I noticed a "loop" on a road Blaine suggested).

    Another assumption you haven't verified.

    You really, really do need to add gradient information. You're completely
    ignoring the third dimension which is nonsensical. It's like drawing a
    straight line on a map of the world and saying that's the shortest route
    for a flight between LA and London.

    What I'm missing is not only the grade (e.g., 9% or 10%) but also the pitch of the road for runoff, which is NOT crowned on our local roads.

    On our local roads, the cross slope is for drainage, and it always slopes into the mountain wall, so it's a different pitch per turn of a degree or two. This may be impossible to calculate so I may need to estimate it.

    I suspect it won't make a big difference, but I need to test it first.
    That's my third WIP.


    Of course, this whole exercise is based on the predicate of "abnormal"
    wear. It seems obvious that constantly driving up and down high gradient,
    twisty roads will wear tyres faster than a daily commute into the city.
    This is entirely *normal* and predicable wear.

    Well, it's "normal" wear for a steep twisty mountain road.

    Correct and will not be covered by warranty because mountain roads aren't normal for 99% of the population.

    And, more importantly, the mapping expertise, programming algorithms, and automotive suspension particulars are technical tidbits which have far-reaching implications in any similar exercise when comparing commutes.

    Thanks for looking at the code and suggesting improvements, almost
    all of which I easily agree with as I'm nothing if not sensible.

    So now apply it via github. It's very easy.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sun Nov 8 14:01:38 2026
    From Newsgroup: comp.lang.python

    Chris wrote:
    This *is* the dataset, for example, for the Moki Dugway GPX file.
    <https://gpx.studio/app#14.41/37.27473/-109.93787>

    No it isn't. That's an app. Provide a file that can be used reproducible by anyone.

    OK. For the Angeles Crest Highway (CA-2) which The Real Bev suggested,
    here's the GPX for <https://i.postimg.cc/dV8qhd8f/angelescrest.jpg>

    1. Open the appropriate road link for the suggested Angels Crest road.
    <https://gpx.studio/app#12.39/34.23487/-118.24127>
    2. Select File > New.
    3. Select the route-planning tool (pen icon).
    4. Select the appropriate routing mode (e.g., bicycle to stay on asphalt)
    5. Trace the complete road (or just click beginning & ending points).
    6. Select File > Export > Download GPX file.
    7. Save using the suggested road-based below filename.
    8. Run the Python analysis: python mountaincurves.py angelescrest.gpx

    Loaded 632 raw track points from 'angelescrest.gpx'.

    --- Road Geometric Analysis: angelescrest.gpx ---
    Detected sharp/moderate curves (R < 200m): 424
    Left-hand turning distribution: 207
    Right-hand turning distribution: 217
    Minimum corner radius (tightest hairpin): 10.28 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 10.28m | Direction: Left | Lat/Lon: 34.222522, -118.192759
    2. Radius: 18.12m | Direction: Right | Lat/Lon: 34.220180, -118.191992
    3. Radius: 21.20m | Direction: Right | Lat/Lon: 34.222678, -118.192989
    4. Radius: 38.06m | Direction: Left | Lat/Lon: 34.228787, -118.183125
    5. Radius: 39.78m | Direction: Left | Lat/Lon: 34.228913, -118.182865

    =========< cut here for angelescrest.gpx >=========

    <?xml version="1.0" encoding="UTF-8"?>
    <gpx creator="https://gpx.studio" version="1.1" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd http://www.garmin.com/xmlschemas/PowerExtension/v1 http://www.garmin.com/xmlschemas/PowerExtensionv1.xsd http://www.topografix.com/GPX/gpx_style/0/2 http://www.topografix.com/GPX/gpx_style/0/2/gpx_style.xsd" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxpx="http://www.garmin.com/xmlschemas/PowerExtension/v1" xmlns:gpx_style="http://www.topografix.com/GPX/gpx_style/0/2">
    <metadata>
    <name>New file 1</name>
    <author>
    <name>gpx.studio</name>
    <link href="https://gpx.studio"/>
    </author>
    </metadata>
    <trk>
    <name>New file 1</name>
    <trkseg>
    <trkpt lat="34.270077" lon="-118.15383">
    <ele>1112.71</ele>
    </trkpt>
    <trkpt lat="34.269782" lon="-118.154497">
    <ele>1113.7</ele>
    </trkpt>
    <trkpt lat="34.269715" lon="-118.154745">
    <ele>1115.55</ele>
    </trkpt>
    <trkpt lat="34.269681" lon="-118.154893">
    <ele>1115.4</ele>
    </trkpt>
    <trkpt lat="34.269651" lon="-118.155086">
    <ele>1115.25</ele>
    </trkpt>
    <trkpt lat="34.269632" lon="-118.155333">
    <ele>1114.85</ele>
    </trkpt>
    <trkpt lat="34.269612" lon="-118.155704">
    <ele>1116.15</ele>
    </trkpt>
    <trkpt lat="34.269602" lon="-118.15627">
    <ele>1115.2</ele>
    </trkpt>
    <trkpt lat="34.269589" lon="-118.156871">
    <ele>1116.3</ele>
    </trkpt>
    <trkpt lat="34.269593" lon="-118.157486">
    <ele>1113.5</ele>
    </trkpt>
    <trkpt lat="34.269614" lon="-118.157737">
    <ele>1114.3</ele>
    </trkpt>
    <trkpt lat="34.269651" lon="-118.15794">
    <ele>1113.6</ele>
    </trkpt>
    <trkpt lat="34.269736" lon="-118.158316">
    <ele>1114.9</ele>
    </trkpt>
    <trkpt lat="34.269767" lon="-118.158514">
    <ele>1114.2</ele>
    </trkpt>
    <trkpt lat="34.269774" lon="-118.15869">
    <ele>1113.9</ele>
    </trkpt>
    <trkpt lat="34.269762" lon="-118.158848">
    <ele>1114.5</ele>
    </trkpt>
    <trkpt lat="34.269741" lon="-118.158991">
    <ele>1117.05</ele>
    </trkpt>
    <trkpt lat="34.269696" lon="-118.159136">
    <ele>1118.25</ele>
    </trkpt>
    <trkpt lat="34.269626" lon="-118.159267">
    <ele>1115</ele>
    </trkpt>
    <trkpt lat="34.269522" lon="-118.159402">
    <ele>1115</ele>
    </trkpt>
    <trkpt lat="34.269387" lon="-118.159522">
    <ele>1115.35</ele>
    </trkpt>
    <trkpt lat="34.269243" lon="-118.159631">
    <ele>1113.95</ele>
    </trkpt>
    <trkpt lat="34.269066" lon="-118.159731">
    <ele>1114.3</ele>
    </trkpt>
    <trkpt lat="34.268894" lon="-118.159841">
    <ele>1113.05</ele>
    </trkpt>
    <trkpt lat="34.268753" lon="-118.159945">
    <ele>1113.4</ele>
    </trkpt>
    <trkpt lat="34.268623" lon="-118.160072">
    <ele>1114</ele>
    </trkpt>
    <trkpt lat="34.268485" lon="-118.160228">
    <ele>1114.05</ele>
    </trkpt>
    <trkpt lat="34.268361" lon="-118.160402">
    <ele>1114.1</ele>
    </trkpt>
    <trkpt lat="34.268082" lon="-118.160807">
    <ele>1117.45</ele>
    </trkpt>
    <trkpt lat="34.267882" lon="-118.161054">
    <ele>1117.35</ele>
    </trkpt>
    <trkpt lat="34.26773" lon="-118.161279">
    <ele>1115</ele>
    </trkpt>
    <trkpt lat="34.267632" lon="-118.161437">
    <ele>1115.18</ele>
    </trkpt>
    <trkpt lat="34.267559" lon="-118.161587">
    <ele>1114.35</ele>
    </trkpt>
    <trkpt lat="34.267514" lon="-118.161706">
    <ele>1114.65</ele>
    </trkpt>
    <trkpt lat="34.267488" lon="-118.161834">
    <ele>1115.1</ele>
    </trkpt>
    <trkpt lat="34.267479" lon="-118.161949">
    <ele>1115.25</ele>
    </trkpt>
    <trkpt lat="34.267491" lon="-118.162085">
    <ele>1115.85</ele>
    </trkpt>
    <trkpt lat="34.267517" lon="-118.162197">
    <ele>1115.95</ele>
    </trkpt>
    <trkpt lat="34.267557" lon="-118.162311">
    <ele>1116.15</ele>
    </trkpt>
    <trkpt lat="34.267639" lon="-118.162459">
    <ele>1114.8</ele>
    </trkpt>
    <trkpt lat="34.267755" lon="-118.162623">
    <ele>1114.8</ele>
    </trkpt>
    <trkpt lat="34.267873" lon="-118.162754">
    <ele>1114.85</ele>
    </trkpt>
    <trkpt lat="34.267999" lon="-118.162868">
    <ele>1114.85</ele>
    </trkpt>
    <trkpt lat="34.268133" lon="-118.163005">
    <ele>1114.45</ele>
    </trkpt>
    <trkpt lat="34.268263" lon="-118.163161">
    <ele>1115.6</ele>
    </trkpt>
    <trkpt lat="34.268361" lon="-118.163304">
    <ele>1116.45</ele>
    </trkpt>
    <trkpt lat="34.268441" lon="-118.163438">
    <ele>1118.55</ele>
    </trkpt>
    <trkpt lat="34.268515" lon="-118.163576">
    <ele>1116.4</ele>
    </trkpt>
    <trkpt lat="34.268569" lon="-118.163717">
    <ele>1116.4</ele>
    </trkpt>
    <trkpt lat="34.268625" lon="-118.163895">
    <ele>1115.35</ele>
    </trkpt>
    <trkpt lat="34.268669" lon="-118.164074">
    <ele>1115.05</ele>
    </trkpt>
    <trkpt lat="34.268801" lon="-118.164816">
    <ele>1118.75</ele>
    </trkpt>
    <trkpt lat="34.268838" lon="-118.165016">
    <ele>1118.7</ele>
    </trkpt>
    <trkpt lat="34.268881" lon="-118.165178">
    <ele>1117.3</ele>
    </trkpt>
    <trkpt lat="34.268939" lon="-118.165327">
    <ele>1115.45</ele>
    </trkpt>
    <trkpt lat="34.269026" lon="-118.165495">
    <ele>1115.15</ele>
    </trkpt>
    <trkpt lat="34.269119" lon="-118.16564">
    <ele>1114.85</ele>
    </trkpt>
    <trkpt lat="34.26923" lon="-118.16578">
    <ele>1114.45</ele>
    </trkpt>
    <trkpt lat="34.269344" lon="-118.165941">
    <ele>1114.15</ele>
    </trkpt>
    <trkpt lat="34.269434" lon="-118.166106">
    <ele>1114.75</ele>
    </trkpt>
    <trkpt lat="34.269513" lon="-118.166327">
    <ele>1112.15</ele>
    </trkpt>
    <trkpt lat="34.269606" lon="-118.166926">
    <ele>1111</ele>
    </trkpt>
    <trkpt lat="34.269653" lon="-118.167223">
    <ele>1108.7</ele>
    </trkpt>
    <trkpt lat="34.269675" lon="-118.167444">
    <ele>1108.4</ele>
    </trkpt>
    <trkpt lat="34.269682" lon="-118.16764">
    <ele>1107.89</ele>
    </trkpt>
    <trkpt lat="34.269705" lon="-118.16787">
    <ele>1104.7</ele>
    </trkpt>
    <trkpt lat="34.269709" lon="-118.168027">
    <ele>1104.1</ele>
    </trkpt>
    <trkpt lat="34.269692" lon="-118.168221">
    <ele>1104.3</ele>
    </trkpt>
    <trkpt lat="34.269646" lon="-118.168372">
    <ele>1103.28</ele>
    </trkpt>
    <trkpt lat="34.269568" lon="-118.168549">
    <ele>1102.7</ele>
    </trkpt>
    <trkpt lat="34.269403" lon="-118.168767">
    <ele>1101.5</ele>
    </trkpt>
    <trkpt lat="34.269217" lon="-118.168926">
    <ele>1099.35</ele>
    </trkpt>
    <trkpt lat="34.268896" lon="-118.169348">
    <ele>1097.2</ele>
    </trkpt>
    <trkpt lat="34.268496" lon="-118.169894">
    <ele>1092.5</ele>
    </trkpt>
    <trkpt lat="34.268365" lon="-118.170053">
    <ele>1091.75</ele>
    </trkpt>
    <trkpt lat="34.268244" lon="-118.170175">
    <ele>1091.35</ele>
    </trkpt>
    <trkpt lat="34.268119" lon="-118.170283">
    <ele>1089.05</ele>
    </trkpt>
    <trkpt lat="34.26784" lon="-118.170495">
    <ele>1086.3</ele>
    </trkpt>
    <trkpt lat="34.267687" lon="-118.170633">
    <ele>1086.85</ele>
    </trkpt>
    <trkpt lat="34.26757" lon="-118.170766">
    <ele>1086.2</ele>
    </trkpt>
    <trkpt lat="34.267496" lon="-118.17089">
    <ele>1084.2</ele>
    </trkpt>
    <trkpt lat="34.267434" lon="-118.17101">
    <ele>1085.3</ele>
    </trkpt>
    <trkpt lat="34.26738" lon="-118.171157">
    <ele>1084.65</ele>
    </trkpt>
    <trkpt lat="34.267359" lon="-118.171333">
    <ele>1082.35</ele>
    </trkpt>
    <trkpt lat="34.267362" lon="-118.171532">
    <ele>1081.55</ele>
    </trkpt>
    <trkpt lat="34.267397" lon="-118.171915">
    <ele>1081.7</ele>
    </trkpt>
    <trkpt lat="34.267417" lon="-118.172117">
    <ele>1078</ele>
    </trkpt>
    <trkpt lat="34.267423" lon="-118.172328">
    <ele>1075.7</ele>
    </trkpt>
    <trkpt lat="34.267415" lon="-118.172534">
    <ele>1076.6</ele>
    </trkpt>
    <trkpt lat="34.267397" lon="-118.172718">
    <ele>1076.36</ele>
    </trkpt>
    <trkpt lat="34.267366" lon="-118.172893">
    <ele>1074.75</ele>
    </trkpt>
    <trkpt lat="34.267317" lon="-118.173059">
    <ele>1073.9</ele>
    </trkpt>
    <trkpt lat="34.26725" lon="-118.173221">
    <ele>1073.5</ele>
    </trkpt>
    <trkpt lat="34.267178" lon="-118.173357">
    <ele>1070.55</ele>
    </trkpt>
    <trkpt lat="34.267078" lon="-118.173507">
    <ele>1070.05</ele>
    </trkpt>
    <trkpt lat="34.26697" lon="-118.173637">
    <ele>1068.75</ele>
    </trkpt>
    <trkpt lat="34.266847" lon="-118.173754">
    <ele>1070.2</ele>
    </trkpt>
    <trkpt lat="34.266725" lon="-118.173855">
    <ele>1068.3</ele>
    </trkpt>
    <trkpt lat="34.266593" lon="-118.173938">
    <ele>1067.6</ele>
    </trkpt>
    <trkpt lat="34.266451" lon="-118.174">
    <ele>1064.65</ele>
    </trkpt>
    <trkpt lat="34.266319" lon="-118.174036">
    <ele>1063.85</ele>
    </trkpt>
    <trkpt lat="34.266174" lon="-118.174046">
    <ele>1063.3</ele>
    </trkpt>
    <trkpt lat="34.266031" lon="-118.174041">
    <ele>1063.21</ele>
    </trkpt>
    <trkpt lat="34.265687" lon="-118.174002">
    <ele>1060.2</ele>
    </trkpt>
    <trkpt lat="34.265549" lon="-118.173991">
    <ele>1060</ele>
    </trkpt>
    <trkpt lat="34.2654" lon="-118.173991">
    <ele>1059.25</ele>
    </trkpt>
    <trkpt lat="34.265099" lon="-118.174045">
    <ele>1059.15</ele>
    </trkpt>
    <trkpt lat="34.264883" lon="-118.174079">
    <ele>1057.05</ele>
    </trkpt>
    <trkpt lat="34.264618" lon="-118.174102">
    <ele>1052.7</ele>
    </trkpt>
    <trkpt lat="34.264196" lon="-118.174144">
    <ele>1052.55</ele>
    </trkpt>
    <trkpt lat="34.264077" lon="-118.174178">
    <ele>1050.1</ele>
    </trkpt>
    <trkpt lat="34.263945" lon="-118.17424">
    <ele>1051.7</ele>
    </trkpt>
    <trkpt lat="34.263831" lon="-118.174322">
    <ele>1051</ele>
    </trkpt>
    <trkpt lat="34.263712" lon="-118.174437">
    <ele>1049.3</ele>
    </trkpt>
    <trkpt lat="34.263618" lon="-118.174559">
    <ele>1047.25</ele>
    </trkpt>
    <trkpt lat="34.26353" lon="-118.174705">
    <ele>1046.4</ele>
    </trkpt>
    <trkpt lat="34.263356" lon="-118.175069">
    <ele>1044.9</ele>
    </trkpt>
    <trkpt lat="34.263162" lon="-118.175435">
    <ele>1044.95</ele>
    </trkpt>
    <trkpt lat="34.263072" lon="-118.17564">
    <ele>1041.95</ele>
    </trkpt>
    <trkpt lat="34.263023" lon="-118.175812">
    <ele>1041.7</ele>
    </trkpt>
    <trkpt lat="34.26299" lon="-118.175985">
    <ele>1039.45</ele>
    </trkpt>
    <trkpt lat="34.262968" lon="-118.176163">
    <ele>1038.9</ele>
    </trkpt>
    <trkpt lat="34.262958" lon="-118.176362">
    <ele>1037.65</ele>
    </trkpt>
    <trkpt lat="34.262964" lon="-118.176576">
    <ele>1036.7</ele>
    </trkpt>
    <trkpt lat="34.26299" lon="-118.176793">
    <ele>1038.95</ele>
    </trkpt>
    <trkpt lat="34.263032" lon="-118.176975">
    <ele>1037.15</ele>
    </trkpt>
    <trkpt lat="34.263094" lon="-118.177164">
    <ele>1032.95</ele>
    </trkpt>
    <trkpt lat="34.263167" lon="-118.17733">
    <ele>1034.15</ele>
    </trkpt>
    <trkpt lat="34.263243" lon="-118.177466">
    <ele>1031.75</ele>
    </trkpt>
    <trkpt lat="34.263341" lon="-118.177617">
    <ele>1031.45</ele>
    </trkpt>
    <trkpt lat="34.263462" lon="-118.177765">
    <ele>1031.05</ele>
    </trkpt>
    <trkpt lat="34.263607" lon="-118.177905">
    <ele>1028.2</ele>
    </trkpt>
    <trkpt lat="34.26374" lon="-118.178051">
    <ele>1024.55</ele>
    </trkpt>
    <trkpt lat="34.263861" lon="-118.178212">
    <ele>1024.4</ele>
    </trkpt>
    <trkpt lat="34.263971" lon="-118.17839">
    <ele>1023.85</ele>
    </trkpt>
    <trkpt lat="34.264138" lon="-118.178746">
    <ele>1021.71</ele>
    </trkpt>
    <trkpt lat="34.264216" lon="-118.178955">
    <ele>1020.15</ele>
    </trkpt>
    <trkpt lat="34.264281" lon="-118.179162">
    <ele>1017.8</ele>
    </trkpt>
    <trkpt lat="34.264332" lon="-118.17937">
    <ele>1017.35</ele>
    </trkpt>
    <trkpt lat="34.264374" lon="-118.179591">
    <ele>1017</ele>
    </trkpt>
    <trkpt lat="34.264451" lon="-118.180268">
    <ele>1016.75</ele>
    </trkpt>
    <trkpt lat="34.264482" lon="-118.180445">
    <ele>1015.05</ele>
    </trkpt>
    <trkpt lat="34.264528" lon="-118.180623">
    <ele>1013.9</ele>
    </trkpt>
    <trkpt lat="34.264582" lon="-118.18079">
    <ele>1013.25</ele>
    </trkpt>
    <trkpt lat="34.264652" lon="-118.18097">
    <ele>1010.2</ele>
    </trkpt>
    <trkpt lat="34.264714" lon="-118.181111">
    <ele>1011.05</ele>
    </trkpt>
    <trkpt lat="34.264781" lon="-118.18125">
    <ele>1008.7</ele>
    </trkpt>
    <trkpt lat="34.264856" lon="-118.181382">
    <ele>1010.6</ele>
    </trkpt>
    <trkpt lat="34.264912" lon="-118.181496">
    <ele>1009.7</ele>
    </trkpt>
    <trkpt lat="34.264947" lon="-118.181593">
    <ele>1007.75</ele>
    </trkpt>
    <trkpt lat="34.264983" lon="-118.18173">
    <ele>1006.8</ele>
    </trkpt>
    <trkpt lat="34.265005" lon="-118.181881">
    <ele>1005.05</ele>
    </trkpt>
    <trkpt lat="34.265008" lon="-118.182034">
    <ele>1004.2</ele>
    </trkpt>
    <trkpt lat="34.264994" lon="-118.182169">
    <ele>1003.5</ele>
    </trkpt>
    <trkpt lat="34.264964" lon="-118.182302">
    <ele>1002.8</ele>
    </trkpt>
    <trkpt lat="34.264916" lon="-118.182441">
    <ele>1001.55</ele>
    </trkpt>
    <trkpt lat="34.264854" lon="-118.182566">
    <ele>1001.05</ele>
    </trkpt>
    <trkpt lat="34.264793" lon="-118.182655">
    <ele>1000.95</ele>
    </trkpt>
    <trkpt lat="34.264718" lon="-118.182742">
    <ele>999.85</ele>
    </trkpt>
    <trkpt lat="34.264641" lon="-118.182807">
    <ele>1000.3</ele>
    </trkpt>
    <trkpt lat="34.264548" lon="-118.182869">
    <ele>999.85</ele>
    </trkpt>
    <trkpt lat="34.26444" lon="-118.182909">
    <ele>998.55</ele>
    </trkpt>
    <trkpt lat="34.26432" lon="-118.182933">
    <ele>997.2</ele>
    </trkpt>
    <trkpt lat="34.264196" lon="-118.182939">
    <ele>996.15</ele>
    </trkpt>
    <trkpt lat="34.26407" lon="-118.182924">
    <ele>994.7</ele>
    </trkpt>
    <trkpt lat="34.263641" lon="-118.182792">
    <ele>993.9</ele>
    </trkpt>
    <trkpt lat="34.263409" lon="-118.18273">
    <ele>991.4</ele>
    </trkpt>
    <trkpt lat="34.263072" lon="-118.182664">
    <ele>991.8</ele>
    </trkpt>
    <trkpt lat="34.262906" lon="-118.182661">
    <ele>990.75</ele>
    </trkpt>
    <trkpt lat="34.262675" lon="-118.182676">
    <ele>988.2</ele>
    </trkpt>
    <trkpt lat="34.262386" lon="-118.182724">
    <ele>989.1</ele>
    </trkpt>
    <trkpt lat="34.262042" lon="-118.182779">
    <ele>983.2</ele>
    </trkpt>
    <trkpt lat="34.261681" lon="-118.182847">
    <ele>984.1</ele>
    </trkpt>
    <trkpt lat="34.261284" lon="-118.18292">
    <ele>979.55</ele>
    </trkpt>
    <trkpt lat="34.261127" lon="-118.182973">
    <ele>978.95</ele>
    </trkpt>
    <trkpt lat="34.261003" lon="-118.183027">
    <ele>979.75</ele>
    </trkpt>
    <trkpt lat="34.260894" lon="-118.183094">
    <ele>977.75</ele>
    </trkpt>
    <trkpt lat="34.260796" lon="-118.183198">
    <ele>976.8</ele>
    </trkpt>
    <trkpt lat="34.260709" lon="-118.183321">
    <ele>976.5</ele>
    </trkpt>
    <trkpt lat="34.260644" lon="-118.183438">
    <ele>974.95</ele>
    </trkpt>
    <trkpt lat="34.260597" lon="-118.183556">
    <ele>975.45</ele>
    </trkpt>
    <trkpt lat="34.260559" lon="-118.183698">
    <ele>974.85</ele>
    </trkpt>
    <trkpt lat="34.26054" lon="-118.183839">
    <ele>972.95</ele>
    </trkpt>
    <trkpt lat="34.260538" lon="-118.183993">
    <ele>971.75</ele>
    </trkpt>
    <trkpt lat="34.260554" lon="-118.184141">
    <ele>971.65</ele>
    </trkpt>
    <trkpt lat="34.260582" lon="-118.184281">
    <ele>971.2</ele>
    </trkpt>
    <trkpt lat="34.260627" lon="-118.184416">
    <ele>969.6</ele>
    </trkpt>
    <trkpt lat="34.260693" lon="-118.184542">
    <ele>967.6</ele>
    </trkpt>
    <trkpt lat="34.260777" lon="-118.184654">
    <ele>966.9</ele>
    </trkpt>
    <trkpt lat="34.260871" lon="-118.184736">
    <ele>965.45</ele>
    </trkpt>
    <trkpt lat="34.260993" lon="-118.184811">
    <ele>964.95</ele>
    </trkpt>
    <trkpt lat="34.261184" lon="-118.184904">
    <ele>963.35</ele>
    </trkpt>
    <trkpt lat="34.261558" lon="-118.185095">
    <ele>963.7</ele>
    </trkpt>
    <trkpt lat="34.2618" lon="-118.18523">
    <ele>960.83</ele>
    </trkpt>
    <trkpt lat="34.261989" lon="-118.185367">
    <ele>958.75</ele>
    </trkpt>
    <trkpt lat="34.262334" lon="-118.18571">
    <ele>956</ele>
    </trkpt>
    <trkpt lat="34.262778" lon="-118.186179">
    <ele>955.25</ele>
    </trkpt>
    <trkpt lat="34.262897" lon="-118.18631">
    <ele>956.35</ele>
    </trkpt>
    <trkpt lat="34.262974" lon="-118.186433">
    <ele>954</ele>
    </trkpt>
    <trkpt lat="34.26303" lon="-118.186559">
    <ele>954.45</ele>
    </trkpt>
    <trkpt lat="34.263067" lon="-118.186711">
    <ele>952.2</ele>
    </trkpt>
    <trkpt lat="34.263085" lon="-118.186869">
    <ele>951.1</ele>
    </trkpt>
    <trkpt lat="34.263085" lon="-118.186993">
    <ele>950.3</ele>
    </trkpt>
    <trkpt lat="34.263062" lon="-118.187127">
    <ele>949</ele>
    </trkpt>
    <trkpt lat="34.26302" lon="-118.187279">
    <ele>949.75</ele>
    </trkpt>
    <trkpt lat="34.262974" lon="-118.187399">
    <ele>949</ele>
    </trkpt>
    <trkpt lat="34.262917" lon="-118.187508">
    <ele>948.15</ele>
    </trkpt>
    <trkpt lat="34.26284" lon="-118.187626">
    <ele>947.8</ele>
    </trkpt>
    <trkpt lat="34.262689" lon="-118.187825">
    <ele>946.7</ele>
    </trkpt>
    <trkpt lat="34.26252" lon="-118.188018">
    <ele>943.15</ele>
    </trkpt>
    <trkpt lat="34.262402" lon="-118.188134">
    <ele>941.75</ele>
    </trkpt>
    <trkpt lat="34.262294" lon="-118.188224">
    <ele>939.3</ele>
    </trkpt>
    <trkpt lat="34.262196" lon="-118.188292">
    <ele>938.35</ele>
    </trkpt>
    <trkpt lat="34.262095" lon="-118.188348">
    <ele>936.7</ele>
    </trkpt>
    <trkpt lat="34.261988" lon="-118.18838">
    <ele>935.75</ele>
    </trkpt>
    <trkpt lat="34.261907" lon="-118.188393">
    <ele>935.55</ele>
    </trkpt>
    <trkpt lat="34.261802" lon="-118.188393">
    <ele>935.25</ele>
    </trkpt>
    <trkpt lat="34.261631" lon="-118.188346">
    <ele>933.99</ele>
    </trkpt>
    <trkpt lat="34.261367" lon="-118.188246">
    <ele>933.15</ele>
    </trkpt>
    <trkpt lat="34.261235" lon="-118.188194">
    <ele>935.6</ele>
    </trkpt>
    <trkpt lat="34.261123" lon="-118.188155">
    <ele>935.45</ele>
    </trkpt>
    <trkpt lat="34.260997" lon="-118.188144">
    <ele>935.35</ele>
    </trkpt>
    <trkpt lat="34.260889" lon="-118.188151">
    <ele>935.65</ele>
    </trkpt>
    <trkpt lat="34.26076" lon="-118.188192">
    <ele>935.75</ele>
    </trkpt>
    <trkpt lat="34.260617" lon="-118.188285">
    <ele>930.05</ele>
    </trkpt>
    <trkpt lat="34.260497" lon="-118.188411">
    <ele>927.9</ele>
    </trkpt>
    <trkpt lat="34.260404" lon="-118.188539">
    <ele>927</ele>
    </trkpt>
    <trkpt lat="34.260337" lon="-118.18865">
    <ele>926.2</ele>
    </trkpt>
    <trkpt lat="34.260292" lon="-118.188763">
    <ele>927.1</ele>
    </trkpt>
    <trkpt lat="34.260258" lon="-118.188895">
    <ele>926.85</ele>
    </trkpt>
    <trkpt lat="34.260244" lon="-118.189025">
    <ele>926.1</ele>
    </trkpt>
    <trkpt lat="34.260248" lon="-118.189185">
    <ele>925.95</ele>
    </trkpt>
    <trkpt lat="34.260277" lon="-118.189464">
    <ele>927.7</ele>
    </trkpt>
    <trkpt lat="34.260307" lon="-118.189734">
    <ele>926.7</ele>
    </trkpt>
    <trkpt lat="34.260398" lon="-118.190408">
    <ele>918.8</ele>
    </trkpt>
    <trkpt lat="34.260499" lon="-118.191143">
    <ele>918.55</ele>
    </trkpt>
    <trkpt lat="34.260531" lon="-118.191397">
    <ele>914.95</ele>
    </trkpt>
    <trkpt lat="34.260542" lon="-118.191584">
    <ele>912.85</ele>
    </trkpt>
    <trkpt lat="34.260531" lon="-118.191756">
    <ele>911.85</ele>
    </trkpt>
    <trkpt lat="34.260496" lon="-118.191899">
    <ele>910.8</ele>
    </trkpt>
    <trkpt lat="34.260444" lon="-118.192029">
    <ele>910.1</ele>
    </trkpt>
    <trkpt lat="34.260379" lon="-118.192158">
    <ele>909.8</ele>
    </trkpt>
    <trkpt lat="34.260302" lon="-118.192278">
    <ele>908.8</ele>
    </trkpt>
    <trkpt lat="34.260218" lon="-118.192363">
    <ele>908.25</ele>
    </trkpt>
    <trkpt lat="34.260135" lon="-118.19242">
    <ele>908.15</ele>
    </trkpt>
    <trkpt lat="34.260011" lon="-118.192468">
    <ele>907.75</ele>
    </trkpt>
    <trkpt lat="34.259702" lon="-118.192489">
    <ele>905.1</ele>
    </trkpt>
    <trkpt lat="34.259293" lon="-118.192447">
    <ele>902.1</ele>
    </trkpt>
    <trkpt lat="34.258926" lon="-118.192401">
    <ele>901.15</ele>
    </trkpt>
    <trkpt lat="34.258788" lon="-118.192414">
    <ele>901.15</ele>
    </trkpt>
    <trkpt lat="34.258659" lon="-118.192438">
    <ele>902.45</ele>
    </trkpt>
    <trkpt lat="34.258536" lon="-118.192503">
    <ele>901.4</ele>
    </trkpt>
    <trkpt lat="34.258414" lon="-118.192595">
    <ele>897.45</ele>
    </trkpt>
    <trkpt lat="34.258323" lon="-118.192678">
    <ele>895.7</ele>
    </trkpt>
    <trkpt lat="34.258236" lon="-118.192778">
    <ele>895.55</ele>
    </trkpt>
    <trkpt lat="34.258162" lon="-118.192883">
    <ele>894.7</ele>
    </trkpt>
    <trkpt lat="34.2581" lon="-118.192985">
    <ele>895.15</ele>
    </trkpt>
    <trkpt lat="34.258048" lon="-118.193112">
    <ele>896.4</ele>
    </trkpt>
    <trkpt lat="34.258015" lon="-118.193265">
    <ele>897.45</ele>
    </trkpt>
    <trkpt lat="34.257995" lon="-118.19341">
    <ele>895.55</ele>
    </trkpt>
    <trkpt lat="34.258004" lon="-118.193565">
    <ele>895</ele>
    </trkpt>
    <trkpt lat="34.258027" lon="-118.19371">
    <ele>894.75</ele>
    </trkpt>
    <trkpt lat="34.258069" lon="-118.193845">
    <ele>892.8</ele>
    </trkpt>
    <trkpt lat="34.258131" lon="-118.193966">
    <ele>893.6</ele>
    </trkpt>
    <trkpt lat="34.258204" lon="-118.194076">
    <ele>896.05</ele>
    </trkpt>
    <trkpt lat="34.258299" lon="-118.194183">
    <ele>895.6</ele>
    </trkpt>
    <trkpt lat="34.258418" lon="-118.194292">
    <ele>893.95</ele>
    </trkpt>
    <trkpt lat="34.258565" lon="-118.1944">
    <ele>894.25</ele>
    </trkpt>
    <trkpt lat="34.258727" lon="-118.194498">
    <ele>889.65</ele>
    </trkpt>
    <trkpt lat="34.258861" lon="-118.194584">
    <ele>889.95</ele>
    </trkpt>
    <trkpt lat="34.259016" lon="-118.19468">
    <ele>887.3</ele>
    </trkpt>
    <trkpt lat="34.25914" lon="-118.194775">
    <ele>887.05</ele>
    </trkpt>
    <trkpt lat="34.259237" lon="-118.194872">
    <ele>884.55</ele>
    </trkpt>
    <trkpt lat="34.259335" lon="-118.194992">
    <ele>881.95</ele>
    </trkpt>
    <trkpt lat="34.259416" lon="-118.19512">
    <ele>881.7</ele>
    </trkpt>
    <trkpt lat="34.259493" lon="-118.195266">
    <ele>881.75</ele>
    </trkpt>
    <trkpt lat="34.259555" lon="-118.19542">
    <ele>880.9</ele>
    </trkpt>
    <trkpt lat="34.259602" lon="-118.195583">
    <ele>879.5</ele>
    </trkpt>
    <trkpt lat="34.259628" lon="-118.195772">
    <ele>878.5</ele>
    </trkpt>
    <trkpt lat="34.259631" lon="-118.195934">
    <ele>878.7</ele>
    </trkpt>
    <trkpt lat="34.259619" lon="-118.196116">
    <ele>877.75</ele>
    </trkpt>
    <trkpt lat="34.259572" lon="-118.196315">
    <ele>876.05</ele>
    </trkpt>
    <trkpt lat="34.259514" lon="-118.196486">
    <ele>874.3</ele>
    </trkpt>
    <trkpt lat="34.259447" lon="-118.196628">
    <ele>873.2</ele>
    </trkpt>
    <trkpt lat="34.259346" lon="-118.196768">
    <ele>872.65</ele>
    </trkpt>
    <trkpt lat="34.259246" lon="-118.196883">
    <ele>871.95</ele>
    </trkpt>
    <trkpt lat="34.259117" lon="-118.196971">
    <ele>872.05</ele>
    </trkpt>
    <trkpt lat="34.258982" lon="-118.197044">
    <ele>870.3</ele>
    </trkpt>
    <trkpt lat="34.258845" lon="-118.197098">
    <ele>869.5</ele>
    </trkpt>
    <trkpt lat="34.258715" lon="-118.197118">
    <ele>867.55</ele>
    </trkpt>
    <trkpt lat="34.258565" lon="-118.197115">
    <ele>867.55</ele>
    </trkpt>
    <trkpt lat="34.258403" lon="-118.197085">
    <ele>866.95</ele>
    </trkpt>
    <trkpt lat="34.258156" lon="-118.197018">
    <ele>865.4</ele>
    </trkpt>
    <trkpt lat="34.257585" lon="-118.196809">
    <ele>860.35</ele>
    </trkpt>
    <trkpt lat="34.257321" lon="-118.196672">
    <ele>857.9</ele>
    </trkpt>
    <trkpt lat="34.257202" lon="-118.196607">
    <ele>858.45</ele>
    </trkpt>
    <trkpt lat="34.257075" lon="-118.196553">
    <ele>859.75</ele>
    </trkpt>
    <trkpt lat="34.256959" lon="-118.196522">
    <ele>860.3</ele>
    </trkpt>
    <trkpt lat="34.256867" lon="-118.196521">
    <ele>859.1</ele>
    </trkpt>
    <trkpt lat="34.25676" lon="-118.196535">
    <ele>858</ele>
    </trkpt>
    <trkpt lat="34.256661" lon="-118.19656">
    <ele>858.2</ele>
    </trkpt>
    <trkpt lat="34.256568" lon="-118.196599">
    <ele>857.96</ele>
    </trkpt>
    <trkpt lat="34.256464" lon="-118.196689">
    <ele>856.4</ele>
    </trkpt>
    <trkpt lat="34.256381" lon="-118.196792">
    <ele>858</ele>
    </trkpt>
    <trkpt lat="34.256308" lon="-118.196929">
    <ele>857.65</ele>
    </trkpt>
    <trkpt lat="34.256253" lon="-118.197074">
    <ele>854.7</ele>
    </trkpt>
    <trkpt lat="34.256218" lon="-118.19724">
    <ele>856.65</ele>
    </trkpt>
    <trkpt lat="34.256208" lon="-118.197389">
    <ele>855.65</ele>
    </trkpt>
    <trkpt lat="34.256206" lon="-118.197561">
    <ele>852.7</ele>
    </trkpt>
    <trkpt lat="34.256195" lon="-118.197722">
    <ele>853.2</ele>
    </trkpt>
    <trkpt lat="34.256176" lon="-118.197837">
    <ele>854</ele>
    </trkpt>
    <trkpt lat="34.256147" lon="-118.197941">
    <ele>852.3</ele>
    </trkpt>
    <trkpt lat="34.256099" lon="-118.198031">
    <ele>848.7</ele>
    </trkpt>
    <trkpt lat="34.256046" lon="-118.198114">
    <ele>847.65</ele>
    </trkpt>
    <trkpt lat="34.255978" lon="-118.198192">
    <ele>846.4</ele>
    </trkpt>
    <trkpt lat="34.255901" lon="-118.198257">
    <ele>846.3</ele>
    </trkpt>
    <trkpt lat="34.255647" lon="-118.198449">
    <ele>847.95</ele>
    </trkpt>
    <trkpt lat="34.25547" lon="-118.198608">
    <ele>847.1</ele>
    </trkpt>
    <trkpt lat="34.255326" lon="-118.198777">
    <ele>846</ele>
    </trkpt>
    <trkpt lat="34.255214" lon="-118.198897">
    <ele>843.85</ele>
    </trkpt>
    <trkpt lat="34.25511" lon="-118.198991">
    <ele>841.55</ele>
    </trkpt>
    <trkpt lat="34.255013" lon="-118.199058">
    <ele>840.15</ele>
    </trkpt>
    <trkpt lat="34.254932" lon="-118.199094">
    <ele>839.6</ele>
    </trkpt>
    <trkpt lat="34.254826" lon="-118.199113">
    <ele>839.05</ele>
    </trkpt>
    <trkpt lat="34.254717" lon="-118.199113">
    <ele>838.2</ele>
    </trkpt>
    <trkpt lat="34.254585" lon="-118.199091">
    <ele>836.45</ele>
    </trkpt>
    <trkpt lat="34.254469" lon="-118.199053">
    <ele>835.05</ele>
    </trkpt>
    <trkpt lat="34.25436" lon="-118.198989">
    <ele>834.35</ele>
    </trkpt>
    <trkpt lat="34.254273" lon="-118.198923">
    <ele>833.55</ele>
    </trkpt>
    <trkpt lat="34.254203" lon="-118.198838">
    <ele>832.25</ele>
    </trkpt>
    <trkpt lat="34.254138" lon="-118.198725">
    <ele>831.65</ele>
    </trkpt>
    <trkpt lat="34.254092" lon="-118.198616">
    <ele>830.1</ele>
    </trkpt>
    <trkpt lat="34.254058" lon="-118.198486">
    <ele>831.3</ele>
    </trkpt>
    <trkpt lat="34.254004" lon="-118.198174">
    <ele>833.5</ele>
    </trkpt>
    <trkpt lat="34.25397" lon="-118.198042">
    <ele>833.05</ele>
    </trkpt>
    <trkpt lat="34.253926" lon="-118.197927">
    <ele>830.55</ele>
    </trkpt>
    <trkpt lat="34.253862" lon="-118.197812">
    <ele>825.85</ele>
    </trkpt>
    <trkpt lat="34.253772" lon="-118.197687">
    <ele>822.85</ele>
    </trkpt>
    <trkpt lat="34.253661" lon="-118.197593">
    <ele>823.35</ele>
    </trkpt>
    <trkpt lat="34.253561" lon="-118.197523">
    <ele>826.75</ele>
    </trkpt>
    <trkpt lat="34.253431" lon="-118.197473">
    <ele>831.5</ele>
    </trkpt>
    <trkpt lat="34.253321" lon="-118.197443">
    <ele>832.1</ele>
    </trkpt>
    <trkpt lat="34.253171" lon="-118.197439">
    <ele>829</ele>
    </trkpt>
    <trkpt lat="34.252925" lon="-118.197479">
    <ele>822.4</ele>
    </trkpt>
    <trkpt lat="34.252732" lon="-118.197532">
    <ele>819.55</ele>
    </trkpt>
    <trkpt lat="34.252576" lon="-118.197558">
    <ele>818.05</ele>
    </trkpt>
    <trkpt lat="34.252418" lon="-118.197563">
    <ele>816.65</ele>
    </trkpt>
    <trkpt lat="34.252265" lon="-118.197526">
    <ele>815.25</ele>
    </trkpt>
    <trkpt lat="34.252169" lon="-118.197476">
    <ele>814.25</ele>
    </trkpt>
    <trkpt lat="34.252124" lon="-118.197444">
    <ele>813.71</ele>
    </trkpt>
    <trkpt lat="34.252048" lon="-118.197376">
    <ele>815.35</ele>
    </trkpt>
    <trkpt lat="34.251989" lon="-118.19731">
    <ele>816.15</ele>
    </trkpt>
    <trkpt lat="34.251939" lon="-118.197239">
    <ele>815.75</ele>
    </trkpt>
    <trkpt lat="34.251901" lon="-118.197159">
    <ele>815.55</ele>
    </trkpt>
    <trkpt lat="34.251871" lon="-118.19707">
    <ele>814.8</ele>
    </trkpt>
    <trkpt lat="34.251838" lon="-118.196884">
    <ele>814.8</ele>
    </trkpt>
    <trkpt lat="34.251827" lon="-118.19672">
    <ele>813.9</ele>
    </trkpt>
    <trkpt lat="34.25184" lon="-118.196618">
    <ele>813.3</ele>
    </trkpt>
    <trkpt lat="34.251863" lon="-118.196532">
    <ele>811.75</ele>
    </trkpt>
    <trkpt lat="34.251951" lon="-118.196044">
    <ele>810.45</ele>
    </trkpt>
    <trkpt lat="34.251962" lon="-118.195859">
    <ele>808.65</ele>
    </trkpt>
    <trkpt lat="34.251945" lon="-118.195691">
    <ele>809.2</ele>
    </trkpt>
    <trkpt lat="34.251909" lon="-118.195524">
    <ele>806.7</ele>
    </trkpt>
    <trkpt lat="34.251855" lon="-118.195356">
    <ele>805.22</ele>
    </trkpt>
    <trkpt lat="34.251807" lon="-118.195268">
    <ele>802.85</ele>
    </trkpt>
    <trkpt lat="34.251727" lon="-118.195163">
    <ele>803.15</ele>
    </trkpt>
    <trkpt lat="34.251434" lon="-118.194865">
    <ele>809.2</ele>
    </trkpt>
    <trkpt lat="34.251335" lon="-118.194765">
    <ele>803.85</ele>
    </trkpt>
    <trkpt lat="34.251146" lon="-118.194574">
    <ele>798.6</ele>
    </trkpt>
    <trkpt lat="34.250916" lon="-118.194353">
    <ele>796.9</ele>
    </trkpt>
    <trkpt lat="34.250586" lon="-118.194115">
    <ele>796.45</ele>
    </trkpt>
    <trkpt lat="34.250395" lon="-118.194021">
    <ele>801.7</ele>
    </trkpt>
    <trkpt lat="34.250266" lon="-118.193994">
    <ele>804.3</ele>
    </trkpt>
    <trkpt lat="34.250128" lon="-118.193997">
    <ele>802.4</ele>
    </trkpt>
    <trkpt lat="34.249991" lon="-118.194022">
    <ele>799.35</ele>
    </trkpt>
    <trkpt lat="34.249844" lon="-118.194068">
    <ele>799.7</ele>
    </trkpt>
    <trkpt lat="34.249691" lon="-118.194136">
    <ele>799.65</ele>
    </trkpt>
    <trkpt lat="34.249536" lon="-118.194228">
    <ele>802.1</ele>
    </trkpt>
    <trkpt lat="34.249244" lon="-118.194432">
    <ele>801.05</ele>
    </trkpt>
    <trkpt lat="34.24906" lon="-118.194523">
    <ele>800.1</ele>
    </trkpt>
    <trkpt lat="34.248822" lon="-118.194542">
    <ele>797.5</ele>
    </trkpt>
    <trkpt lat="34.248667" lon="-118.194517">
    <ele>797.25</ele>
    </trkpt>
    <trkpt lat="34.248557" lon="-118.194487">
    <ele>797.2</ele>
    </trkpt>
    <trkpt lat="34.248446" lon="-118.194411">
    <ele>795.8</ele>
    </trkpt>
    <trkpt lat="34.248324" lon="-118.194295">
    <ele>795.8</ele>
    </trkpt>
    <trkpt lat="34.248214" lon="-118.194145">
    <ele>795.9</ele>
    </trkpt>
    <trkpt lat="34.248135" lon="-118.193979">
    <ele>797.1</ele>
    </trkpt>
    <trkpt lat="34.248076" lon="-118.193804">
    <ele>796.15</ele>
    </trkpt>
    <trkpt lat="34.24805" lon="-118.193613">
    <ele>795.8</ele>
    </trkpt>
    <trkpt lat="34.248045" lon="-118.193444">
    <ele>794.55</ele>
    </trkpt>
    <trkpt lat="34.24804" lon="-118.192989">
    <ele>798.38</ele>
    </trkpt>
    <trkpt lat="34.248018" lon="-118.192799">
    <ele>800.7</ele>
    </trkpt>
    <trkpt lat="34.24798" lon="-118.192643">
    <ele>803.2</ele>
    </trkpt>
    <trkpt lat="34.247927" lon="-118.192496">
    <ele>800.75</ele>
    </trkpt>
    <trkpt lat="34.247865" lon="-118.192371">
    <ele>799.45</ele>
    </trkpt>
    <trkpt lat="34.247746" lon="-118.192228">
    <ele>796.9</ele>
    </trkpt>
    <trkpt lat="34.247479" lon="-118.192006">
    <ele>795.5</ele>
    </trkpt>
    <trkpt lat="34.247268" lon="-118.191838">
    <ele>796.6</ele>
    </trkpt>
    <trkpt lat="34.247002" lon="-118.191596">
    <ele>802</ele>
    </trkpt>
    <trkpt lat="34.246837" lon="-118.191436">
    <ele>804.4</ele>
    </trkpt>
    <trkpt lat="34.246671" lon="-118.191276">
    <ele>803.2</ele>
    </trkpt>
    <trkpt lat="34.246427" lon="-118.191065">
    <ele>797.15</ele>
    </trkpt>
    <trkpt lat="34.246224" lon="-118.190872">
    <ele>794.25</ele>
    </trkpt>
    <trkpt lat="34.246078" lon="-118.190723">
    <ele>797.85</ele>
    </trkpt>
    <trkpt lat="34.245939" lon="-118.190612">
    <ele>801.65</ele>
    </trkpt>
    <trkpt lat="34.245818" lon="-118.190541">
    <ele>801.25</ele>
    </trkpt>
    <trkpt lat="34.245696" lon="-118.190486">
    <ele>799.15</ele>
    </trkpt>
    <trkpt lat="34.245466" lon="-118.190444">
    <ele>792.75</ele>
    </trkpt>
    <trkpt lat="34.245164" lon="-118.190474">
    <ele>792.05</ele>
    </trkpt>
    <trkpt lat="34.244996" lon="-118.190505">
    <ele>789.05</ele>
    </trkpt>
    <trkpt lat="34.244816" lon="-118.190551">
    <ele>787.9</ele>
    </trkpt>
    <trkpt lat="34.244657" lon="-118.190575">
    <ele>785.95</ele>
    </trkpt>
    <trkpt lat="34.244538" lon="-118.19057">
    <ele>784.95</ele>
    </trkpt>
    <trkpt lat="34.244426" lon="-118.190551">
    <ele>784.45</ele>
    </trkpt>
    <trkpt lat="34.244317" lon="-118.190513">
    <ele>783.6</ele>
    </trkpt>
    <trkpt lat="34.244214" lon="-118.190453">
    <ele>782.9</ele>
    </trkpt>
    <trkpt lat="34.244114" lon="-118.190382">
    <ele>782.75</ele>
    </trkpt>
    <trkpt lat="34.243991" lon="-118.190277">
    <ele>780.75</ele>
    </trkpt>
    <trkpt lat="34.243891" lon="-118.190173">
    <ele>779.65</ele>
    </trkpt>
    <trkpt lat="34.243724" lon="-118.189937">
    <ele>778.3</ele>
    </trkpt>
    <trkpt lat="34.243652" lon="-118.189856">
    <ele>778.3</ele>
    </trkpt>
    <trkpt lat="34.243573" lon="-118.189787">
    <ele>779.15</ele>
    </trkpt>
    <trkpt lat="34.243463" lon="-118.189719">
    <ele>780.65</ele>
    </trkpt>
    <trkpt lat="34.243346" lon="-118.189666">
    <ele>778.4</ele>
    </trkpt>
    <trkpt lat="34.243185" lon="-118.189629">
    <ele>776.95</ele>
    </trkpt>
    <trkpt lat="34.243106" lon="-118.189628">
    <ele>776.3</ele>
    </trkpt>
    <trkpt lat="34.242921" lon="-118.189648">
    <ele>774.05</ele>
    </trkpt>
    <trkpt lat="34.242799" lon="-118.189672">
    <ele>772.65</ele>
    </trkpt>
    <trkpt lat="34.242613" lon="-118.189697">
    <ele>772.3</ele>
    </trkpt>
    <trkpt lat="34.2425" lon="-118.189687">
    <ele>770.27</ele>
    </trkpt>
    <trkpt lat="34.242416" lon="-118.189664">
    <ele>768.7</ele>
    </trkpt>
    <trkpt lat="34.242335" lon="-118.189629">
    <ele>767.1</ele>
    </trkpt>
    <trkpt lat="34.242257" lon="-118.189584">
    <ele>765.55</ele>
    </trkpt>
    <trkpt lat="34.242184" lon="-118.189528">
    <ele>763.9</ele>
    </trkpt>
    <trkpt lat="34.242115" lon="-118.189463">
    <ele>762.2</ele>
    </trkpt>
    <trkpt lat="34.242053" lon="-118.189389">
    <ele>760.48</ele>
    </trkpt>
    <trkpt lat="34.241947" lon="-118.189206">
    <ele>764.3</ele>
    </trkpt>
    <trkpt lat="34.24188" lon="-118.18905">
    <ele>765.15</ele>
    </trkpt>
    <trkpt lat="34.241809" lon="-118.188871">
    <ele>762.65</ele>
    </trkpt>
    <trkpt lat="34.241667" lon="-118.188595">
    <ele>762.8</ele>
    </trkpt>
    <trkpt lat="34.241628" lon="-118.188543">
    <ele>764.25</ele>
    </trkpt>
    <trkpt lat="34.24159" lon="-118.188502">
    <ele>764.85</ele>
    </trkpt>
    <trkpt lat="34.241491" lon="-118.188425">
    <ele>764.2</ele>
    </trkpt>
    <trkpt lat="34.241374" lon="-118.188346">
    <ele>765.4</ele>
    </trkpt>
    <trkpt lat="34.241252" lon="-118.188292">
    <ele>762.65</ele>
    </trkpt>
    <trkpt lat="34.241101" lon="-118.188266">
    <ele>761.01</ele>
    </trkpt>
    <trkpt lat="34.240878" lon="-118.188247">
    <ele>756.9</ele>
    </trkpt>
    <trkpt lat="34.24028" lon="-118.188293">
    <ele>753.4</ele>
    </trkpt>
    <trkpt lat="34.240067" lon="-118.188321">
    <ele>754.25</ele>
    </trkpt>
    <trkpt lat="34.239892" lon="-118.188367">
    <ele>753.5</ele>
    </trkpt>
    <trkpt lat="34.239728" lon="-118.18843">
    <ele>752.7</ele>
    </trkpt>
    <trkpt lat="34.239594" lon="-118.188501">
    <ele>751.85</ele>
    </trkpt>
    <trkpt lat="34.239462" lon="-118.188604">
    <ele>749.75</ele>
    </trkpt>
    <trkpt lat="34.23934" lon="-118.188737">
    <ele>750</ele>
    </trkpt>
    <trkpt lat="34.239243" lon="-118.188894">
    <ele>751.45</ele>
    </trkpt>
    <trkpt lat="34.239149" lon="-118.189099">
    <ele>752.1</ele>
    </trkpt>
    <trkpt lat="34.239078" lon="-118.189295">
    <ele>749.65</ele>
    </trkpt>
    <trkpt lat="34.238993" lon="-118.18948">
    <ele>751.45</ele>
    </trkpt>
    <trkpt lat="34.23891" lon="-118.189611">
    <ele>748.85</ele>
    </trkpt>
    <trkpt lat="34.238832" lon="-118.189709">
    <ele>747.65</ele>
    </trkpt>
    <trkpt lat="34.238736" lon="-118.18979">
    <ele>744.5</ele>
    </trkpt>
    <trkpt lat="34.238627" lon="-118.189846">
    <ele>743.95</ele>
    </trkpt>
    <trkpt lat="34.238485" lon="-118.189884">
    <ele>742.7</ele>
    </trkpt>
    <trkpt lat="34.238343" lon="-118.189883">
    <ele>741.75</ele>
    </trkpt>
    <trkpt lat="34.2382" lon="-118.189848">
    <ele>740.95</ele>
    </trkpt>
    <trkpt lat="34.238088" lon="-118.189806">
    <ele>739.85</ele>
    </trkpt>
    <trkpt lat="34.237814" lon="-118.18964">
    <ele>737.4</ele>
    </trkpt>
    <trkpt lat="34.2377" lon="-118.189555">
    <ele>737.9</ele>
    </trkpt>
    <trkpt lat="34.237583" lon="-118.189447">
    <ele>735.6</ele>
    </trkpt>
    <trkpt lat="34.237512" lon="-118.189342">
    <ele>735</ele>
    </trkpt>
    <trkpt lat="34.237408" lon="-118.189041">
    <ele>732.9</ele>
    </trkpt>
    <trkpt lat="34.237386" lon="-118.188727">
    <ele>730.95</ele>
    </trkpt>
    <trkpt lat="34.23743" lon="-118.188119">
    <ele>729.95</ele>
    </trkpt>
    <trkpt lat="34.237474" lon="-118.187511">
    <ele>726.35</ele>
    </trkpt>
    <trkpt lat="34.237496" lon="-118.187207">
    <ele>722.75</ele>
    </trkpt>
    <trkpt lat="34.23754" lon="-118.186598">
    <ele>721.45</ele>
    </trkpt>
    <trkpt lat="34.23753" lon="-118.186276">
    <ele>718.75</ele>
    </trkpt>
    <trkpt lat="34.237497" lon="-118.186112">
    <ele>717.95</ele>
    </trkpt>
    <trkpt lat="34.237451" lon="-118.185971">
    <ele>718.7</ele>
    </trkpt>
    <trkpt lat="34.237378" lon="-118.185835">
    <ele>720.45</ele>
    </trkpt>
    <trkpt lat="34.237293" lon="-118.185708">
    <ele>720.95</ele>
    </trkpt>
    <trkpt lat="34.237198" lon="-118.185597">
    <ele>722.25</ele>
    </trkpt>
    <trkpt lat="34.237114" lon="-118.185516">
    <ele>720.65</ele>
    </trkpt>
    <trkpt lat="34.237003" lon="-118.185424">
    <ele>720.15</ele>
    </trkpt>
    <trkpt lat="34.236884" lon="-118.185358">
    <ele>716.8</ele>
    </trkpt>
    <trkpt lat="34.236746" lon="-118.185307">
    <ele>712.95</ele>
    </trkpt>
    <trkpt lat="34.236378" lon="-118.185203">
    <ele>711.25</ele>
    </trkpt>
    <trkpt lat="34.236246" lon="-118.185136">
    <ele>708.5</ele>
    </trkpt>
    <trkpt lat="34.236169" lon="-118.185081">
    <ele>708</ele>
    </trkpt>
    <trkpt lat="34.236107" lon="-118.185024">
    <ele>706.95</ele>
    </trkpt>
    <trkpt lat="34.236044" lon="-118.184948">
    <ele>705.2</ele>
    </trkpt>
    <trkpt lat="34.235974" lon="-118.184848">
    <ele>704.2</ele>
    </trkpt>
    <trkpt lat="34.235916" lon="-118.184746">
    <ele>703.55</ele>
    </trkpt>
    <trkpt lat="34.235752" lon="-118.184419">
    <ele>699.1</ele>
    </trkpt>
    <trkpt lat="34.235693" lon="-118.184322">
    <ele>698.85</ele>
    </trkpt>
    <trkpt lat="34.235624" lon="-118.184238">
    <ele>699.55</ele>
    </trkpt>
    <trkpt lat="34.235486" lon="-118.18413">
    <ele>700.95</ele>
    </trkpt>
    <trkpt lat="34.235231" lon="-118.184026">
    <ele>702.7</ele>
    </trkpt>
    <trkpt lat="34.234919" lon="-118.183881">
    <ele>696.75</ele>
    </trkpt>
    <trkpt lat="34.234683" lon="-118.183783">
    <ele>698.5</ele>
    </trkpt>
    <trkpt lat="34.234448" lon="-118.183685">
    <ele>697.5</ele>
    </trkpt>
    <trkpt lat="34.234267" lon="-118.183632">
    <ele>694.7</ele>
    </trkpt>
    <trkpt lat="34.233879" lon="-118.183624">
    <ele>691.25</ele>
    </trkpt>
    <trkpt lat="34.233486" lon="-118.18365">
    <ele>689.74</ele>
    </trkpt>
    <trkpt lat="34.233169" lon="-118.183633">
    <ele>687.65</ele>
    </trkpt>
    <trkpt lat="34.233058" lon="-118.183599">
    <ele>687.1</ele>
    </trkpt>
    <trkpt lat="34.232891" lon="-118.183504">
    <ele>688.2</ele>
    </trkpt>
    <trkpt lat="34.23275" lon="-118.183341">
    <ele>687.3</ele>
    </trkpt>
    <trkpt lat="34.232605" lon="-118.183115">
    <ele>684</ele>
    </trkpt>
    <trkpt lat="34.232459" lon="-118.182889">
    <ele>684.7</ele>
    </trkpt>
    <trkpt lat="34.232316" lon="-118.182667">
    <ele>683.15</ele>
    </trkpt>
    <trkpt lat="34.232215" lon="-118.18249">
    <ele>681.5</ele>
    </trkpt>
    <trkpt lat="34.232134" lon="-118.182248">
    <ele>683.5</ele>
    </trkpt>
    <trkpt lat="34.232074" lon="-118.182027">
    <ele>680.7</ele>
    </trkpt>
    <trkpt lat="34.232029" lon="-118.181918">
    <ele>680.25</ele>
    </trkpt>
    <trkpt lat="34.231954" lon="-118.18179">
    <ele>676.95</ele>
    </trkpt>
    <trkpt lat="34.231894" lon="-118.18172">
    <ele>676.05</ele>
    </trkpt>
    <trkpt lat="34.231823" lon="-118.181662">
    <ele>675.35</ele>
    </trkpt>
    <trkpt lat="34.231658" lon="-118.18158">
    <ele>671.35</ele>
    </trkpt>
    <trkpt lat="34.231507" lon="-118.18155">
    <ele>668.45</ele>
    </trkpt>
    <trkpt lat="34.23119" lon="-118.181506">
    <ele>668.7</ele>
    </trkpt>
    <trkpt lat="34.230872" lon="-118.181462">
    <ele>666.4</ele>
    </trkpt>
    <trkpt lat="34.230603" lon="-118.181433">
    <ele>665.65</ele>
    </trkpt>
    <trkpt lat="34.230473" lon="-118.181455">
    <ele>665.55</ele>
    </trkpt>
    <trkpt lat="34.230398" lon="-118.18148">
    <ele>665.1</ele>
    </trkpt>
    <trkpt lat="34.230305" lon="-118.181535">
    <ele>664.6</ele>
    </trkpt>
    <trkpt lat="34.230227" lon="-118.181617">
    <ele>663.3</ele>
    </trkpt>
    <trkpt lat="34.230178" lon="-118.181703">
    <ele>660.6</ele>
    </trkpt>
    <trkpt lat="34.230154" lon="-118.181763">
    <ele>658.5</ele>
    </trkpt>
    <trkpt lat="34.230042" lon="-118.182117">
    <ele>655.6</ele>
    </trkpt>
    <trkpt lat="34.229993" lon="-118.182258">
    <ele>655.75</ele>
    </trkpt>
    <trkpt lat="34.229867" lon="-118.182479">
    <ele>654.75</ele>
    </trkpt>
    <trkpt lat="34.229784" lon="-118.18258">
    <ele>654.65</ele>
    </trkpt>
    <trkpt lat="34.229688" lon="-118.182645">
    <ele>654.6</ele>
    </trkpt>
    <trkpt lat="34.229508" lon="-118.182687">
    <ele>654.25</ele>
    </trkpt>
    <trkpt lat="34.229264" lon="-118.182696">
    <ele>652.75</ele>
    </trkpt>
    <trkpt lat="34.229054" lon="-118.182746">
    <ele>650.3</ele>
    </trkpt>
    <trkpt lat="34.22899" lon="-118.182796">
    <ele>652.21</ele>
    </trkpt>
    <trkpt lat="34.228913" lon="-118.182865">
    <ele>651.6</ele>
    </trkpt>
    <trkpt lat="34.228842" lon="-118.182983">
    <ele>651.2</ele>
    </trkpt>
    <trkpt lat="34.228787" lon="-118.183125">
    <ele>650.5</ele>
    </trkpt>
    <trkpt lat="34.228777" lon="-118.183244">
    <ele>648.85</ele>
    </trkpt>
    <trkpt lat="34.228784" lon="-118.183349">
    <ele>647.69</ele>
    </trkpt>
    <trkpt lat="34.228837" lon="-118.18376">
    <ele>644</ele>
    </trkpt>
    <trkpt lat="34.228837" lon="-118.183917">
    <ele>644.4</ele>
    </trkpt>
    <trkpt lat="34.228824" lon="-118.184126">
    <ele>644.95</ele>
    </trkpt>
    <trkpt lat="34.228781" lon="-118.184399">
    <ele>641.1</ele>
    </trkpt>
    <trkpt lat="34.228755" lon="-118.184497">
    <ele>638.7</ele>
    </trkpt>
    <trkpt lat="34.228718" lon="-118.184593">
    <ele>639.7</ele>
    </trkpt>
    <trkpt lat="34.22861" lon="-118.184811">
    <ele>642.35</ele>
    </trkpt>
    <trkpt lat="34.228461" lon="-118.185139">
    <ele>641.2</ele>
    </trkpt>
    <trkpt lat="34.228376" lon="-118.185318">
    <ele>638.6</ele>
    </trkpt>
    <trkpt lat="34.228277" lon="-118.185499">
    <ele>636.65</ele>
    </trkpt>
    <trkpt lat="34.228203" lon="-118.185609">
    <ele>636.2</ele>
    </trkpt>
    <trkpt lat="34.228115" lon="-118.185691">
    <ele>635.6</ele>
    </trkpt>
    <trkpt lat="34.228005" lon="-118.185753">
    <ele>635.65</ele>
    </trkpt>
    <trkpt lat="34.227647" lon="-118.185942">
    <ele>631.7</ele>
    </trkpt>
    <trkpt lat="34.227436" lon="-118.186061">
    <ele>631.25</ele>
    </trkpt>
    <trkpt lat="34.227359" lon="-118.186118">
    <ele>631.15</ele>
    </trkpt>
    <trkpt lat="34.22728" lon="-118.186192">
    <ele>631.6</ele>
    </trkpt>
    <trkpt lat="34.227227" lon="-118.186268">
    <ele>632.6</ele>
    </trkpt>
    <trkpt lat="34.227192" lon="-118.186347">
    <ele>634.35</ele>
    </trkpt>
    <trkpt lat="34.227164" lon="-118.186442">
    <ele>636</ele>
    </trkpt>
    <trkpt lat="34.227146" lon="-118.186544">
    <ele>634.4</ele>
    </trkpt>
    <trkpt lat="34.227138" lon="-118.186659">
    <ele>631.2</ele>
    </trkpt>
    <trkpt lat="34.22714" lon="-118.186792">
    <ele>627.85</ele>
    </trkpt>
    <trkpt lat="34.227173" lon="-118.187247">
    <ele>624.85</ele>
    </trkpt>
    <trkpt lat="34.227174" lon="-118.187513">
    <ele>625.55</ele>
    </trkpt>
    <trkpt lat="34.227148" lon="-118.187637">
    <ele>624.95</ele>
    </trkpt>
    <trkpt lat="34.227121" lon="-118.187747">
    <ele>622.6</ele>
    </trkpt>
    <trkpt lat="34.227072" lon="-118.187871">
    <ele>620.85</ele>
    </trkpt>
    <trkpt lat="34.227009" lon="-118.187977">
    <ele>620.9</ele>
    </trkpt>
    <trkpt lat="34.226942" lon="-118.188065">
    <ele>620.15</ele>
    </trkpt>
    <trkpt lat="34.226869" lon="-118.188154">
    <ele>620.25</ele>
    </trkpt>
    <trkpt lat="34.2268" lon="-118.188221">
    <ele>619.7</ele>
    </trkpt>
    <trkpt lat="34.226711" lon="-118.188285">
    <ele>619.1</ele>
    </trkpt>
    <trkpt lat="34.226627" lon="-118.188325">
    <ele>618.25</ele>
    </trkpt>
    <trkpt lat="34.22654" lon="-118.188351">
    <ele>617.6</ele>
    </trkpt>
    <trkpt lat="34.226365" lon="-118.188368">
    <ele>617.25</ele>
    </trkpt>
    <trkpt lat="34.22627" lon="-118.188361">
    <ele>617.3</ele>
    </trkpt>
    <trkpt lat="34.226174" lon="-118.18834">
    <ele>616.7</ele>
    </trkpt>
    <trkpt lat="34.226079" lon="-118.188306">
    <ele>616.3</ele>
    </trkpt>
    <trkpt lat="34.22593" lon="-118.188223">
    <ele>615.05</ele>
    </trkpt>
    <trkpt lat="34.2256" lon="-118.187946">
    <ele>613.55</ele>
    </trkpt>
    <trkpt lat="34.225518" lon="-118.187896">
    <ele>613.1</ele>
    </trkpt>
    <trkpt lat="34.225426" lon="-118.187861">
    <ele>612.9</ele>
    </trkpt>
    <trkpt lat="34.225344" lon="-118.187852">
    <ele>612.25</ele>
    </trkpt>
    <trkpt lat="34.225239" lon="-118.187864">
    <ele>610.65</ele>
    </trkpt>
    <trkpt lat="34.225121" lon="-118.18791">
    <ele>608.75</ele>
    </trkpt>
    <trkpt lat="34.225009" lon="-118.187991">
    <ele>609.2</ele>
    </trkpt>
    <trkpt lat="34.224834" lon="-118.188171">
    <ele>608.93</ele>
    </trkpt>
    <trkpt lat="34.224646" lon="-118.188381">
    <ele>604.45</ele>
    </trkpt>
    <trkpt lat="34.223891" lon="-118.189219">
    <ele>599.55</ele>
    </trkpt>
    <trkpt lat="34.223702" lon="-118.189429">
    <ele>602.6</ele>
    </trkpt>
    <trkpt lat="34.223356" lon="-118.189825">
    <ele>600.15</ele>
    </trkpt>
    <trkpt lat="34.223229" lon="-118.190037">
    <ele>598.65</ele>
    </trkpt>
    <trkpt lat="34.223119" lon="-118.190252">
    <ele>597</ele>
    </trkpt>
    <trkpt lat="34.223005" lon="-118.190575">
    <ele>592.24</ele>
    </trkpt>
    <trkpt lat="34.222941" lon="-118.190882">
    <ele>590.6</ele>
    </trkpt>
    <trkpt lat="34.222911" lon="-118.191109">
    <ele>589.65</ele>
    </trkpt>
    <trkpt lat="34.222867" lon="-118.1919">
    <ele>584.25</ele>
    </trkpt>
    <trkpt lat="34.222841" lon="-118.192116">
    <ele>583.58</ele>
    </trkpt>
    <trkpt lat="34.222786" lon="-118.192291">
    <ele>582.2</ele>
    </trkpt>
    <trkpt lat="34.222704" lon="-118.192466">
    <ele>580.9</ele>
    </trkpt>
    <trkpt lat="34.222617" lon="-118.19263">
    <ele>580.45</ele>
    </trkpt>
    <trkpt lat="34.222522" lon="-118.192759">
    <ele>579.64</ele>
    </trkpt>
    <trkpt lat="34.222592" lon="-118.19285">
    <ele>580.25</ele>
    </trkpt>
    <trkpt lat="34.222678" lon="-118.192989">
    <ele>581.13</ele>
    </trkpt>
    <trkpt lat="34.222342" lon="-118.193187">
    <ele>579.85</ele>
    </trkpt>
    <trkpt lat="34.222151" lon="-118.193284">
    <ele>579.1</ele>
    </trkpt>
    <trkpt lat="34.221977" lon="-118.193322">
    <ele>577.05</ele>
    </trkpt>
    <trkpt lat="34.221808" lon="-118.193338">
    <ele>575.65</ele>
    </trkpt>
    <trkpt lat="34.221626" lon="-118.193327">
    <ele>574.4</ele>
    </trkpt>
    <trkpt lat="34.221464" lon="-118.193294">
    <ele>573.3</ele>
    </trkpt>
    <trkpt lat="34.221307" lon="-118.193252">
    <ele>572.15</ele>
    </trkpt>
    <trkpt lat="34.221153" lon="-118.193166">
    <ele>571.35</ele>
    </trkpt>
    <trkpt lat="34.221002" lon="-118.193037">
    <ele>570.55</ele>
    </trkpt>
    <trkpt lat="34.220855" lon="-118.192892">
    <ele>569</ele>
    </trkpt>
    <trkpt lat="34.220475" lon="-118.192286">
    <ele>565.45</ele>
    </trkpt>
    <trkpt lat="34.220376" lon="-118.192184">
    <ele>565</ele>
    </trkpt>
    <trkpt lat="34.220253" lon="-118.192077">
    <ele>565</ele>
    </trkpt>
    <trkpt lat="34.22018" lon="-118.191992">
    <ele>566.18</ele>
    </trkpt>
    <trkpt lat="34.220457" lon="-118.191786">
    <ele>564.05</ele>
    </trkpt>
    <trkpt lat="34.220038" lon="-118.191063">
    <ele>561.07</ele>
    </trkpt>
    <trkpt lat="34.219884" lon="-118.190863">
    <ele>560.75</ele>
    </trkpt>
    <trkpt lat="34.219714" lon="-118.19058">
    <ele>557.75</ele>
    </trkpt>
    <trkpt lat="34.219388" lon="-118.190022">
    <ele>556.15</ele>
    </trkpt>
    <trkpt lat="34.219286" lon="-118.18987">
    <ele>553.95</ele>
    </trkpt>
    <trkpt lat="34.219144" lon="-118.189713">
    <ele>552.7</ele>
    </trkpt>
    <trkpt lat="34.218992" lon="-118.189584">
    <ele>551.05</ele>
    </trkpt>
    <trkpt lat="34.218857" lon="-118.189506">
    <ele>550.05</ele>
    </trkpt>
    <trkpt lat="34.21868" lon="-118.18944">
    <ele>549</ele>
    </trkpt>
    </trkseg>
    </trk>
    </gpx>
    --
    Usenet works because knowledgeable people take the time to help others.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Sun Nov 8 14:19:27 2026
    From Newsgroup: comp.lang.python

    Chris wrote:
    Supply a file. You could have done it far more quickly by now rather then repetitively responding to everyone why you aren't.

    Here is full code & testcase for the Guardsman Pass suggested by Blaine.
    <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>

    1. Open the appropriate road link for the suggested Angels Crest road.
    <https://gpx.studio/app#13.81/40.61548/-111.52533>
    2. Select File > New.
    3. Select the route-planning tool (pen icon).
    4. Select the appropriate routing mode (e.g., bicycle to stay on asphalt)
    5. Trace the complete road (or just click beginning & ending points).
    6. Select File > Export > Download GPX file.
    7. Save using the suggested road-based below filename.
    8. Run the Python analysis: python mountaincurves.py guardsmanpass.gpx

    Loaded 219 raw track points from 'guardsmanpass.gpx'.

    --- Road Geometric Analysis: guardsmanpass.gpx ---
    Detected sharp/moderate curves (R < 200m): 135
    Left-hand turning distribution: 70
    Right-hand turning distribution: 65
    Minimum corner radius (tightest hairpin): 2.04 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620587, -111.495800
    2. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620605, -111.495784
    3. Radius: 2.29m | Direction: Left | Lat/Lon: 40.620597, -111.495796
    4. Radius: 2.33m | Direction: Right | Lat/Lon: 40.620464, -111.495741
    5. Radius: 2.71m | Direction: Right | Lat/Lon: 40.620569, -111.495601
    =========< cut here for guardsmanpass.gpx >=========
    <?xml version="1.0" encoding="UTF-8"?>
    <gpx creator="https://gpx.studio" version="1.1" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd http://www.garmin.com/xmlschemas/PowerExtension/v1 http://www.garmin.com/xmlschemas/PowerExtensionv1.xsd http://www.topografix.com/GPX/gpx_style/0/2 http://www.topografix.com/GPX/gpx_style/0/2/gpx_style.xsd" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxpx="http://www.garmin.com/xmlschemas/PowerExtension/v1" xmlns:gpx_style="http://www.topografix.com/GPX/gpx_style/0/2">
    <metadata>
    <name>New file 4</name>
    <author>
    <name>gpx.studio</name>
    <link href="https://gpx.studio"/>
    </author>
    </metadata>
    <trk>
    <name>New file 4</name>
    <trkseg>
    <trkpt lat="40.606487" lon="-111.524455">
    <ele>2710.88</ele>
    </trkpt>
    <trkpt lat="40.606261" lon="-111.52343">
    <ele>2709.85</ele>
    </trkpt>
    <trkpt lat="40.606167" lon="-111.523041">
    <ele>2708.7</ele>
    </trkpt>
    <trkpt lat="40.606094" lon="-111.522781">
    <ele>2709.6</ele>
    </trkpt>
    <trkpt lat="40.606013" lon="-111.522582">
    <ele>2710.35</ele>
    </trkpt>
    <trkpt lat="40.605903" lon="-111.522365">
    <ele>2711.6</ele>
    </trkpt>
    <trkpt lat="40.605681" lon="-111.522022">
    <ele>2713.65</ele>
    </trkpt>
    <trkpt lat="40.605541" lon="-111.521725">
    <ele>2713.25</ele>
    </trkpt>
    <trkpt lat="40.605522" lon="-111.521653">
    <ele>2712.7</ele>
    </trkpt>
    <trkpt lat="40.605513" lon="-111.52156">
    <ele>2712.4</ele>
    </trkpt>
    <trkpt lat="40.605531" lon="-111.521422">
    <ele>2712.55</ele>
    </trkpt>
    <trkpt lat="40.605648" lon="-111.521203">
    <ele>2712.3</ele>
    </trkpt>
    <trkpt lat="40.605787" lon="-111.520978">
    <ele>2712.65</ele>
    </trkpt>
    <trkpt lat="40.605931" lon="-111.52063">
    <ele>2714.2</ele>
    </trkpt>
    <trkpt lat="40.60598" lon="-111.520445">
    <ele>2714.85</ele>
    </trkpt>
    <trkpt lat="40.606015" lon="-111.520231">
    <ele>2715.95</ele>
    </trkpt>
    <trkpt lat="40.606024" lon="-111.520075">
    <ele>2716.75</ele>
    </trkpt>
    <trkpt lat="40.606019" lon="-111.519915">
    <ele>2718</ele>
    </trkpt>
    <trkpt lat="40.605985" lon="-111.519536">
    <ele>2720.4</ele>
    </trkpt>
    <trkpt lat="40.605977" lon="-111.519351">
    <ele>2720.85</ele>
    </trkpt>
    <trkpt lat="40.60598" lon="-111.519166">
    <ele>2721.22</ele>
    </trkpt>
    <trkpt lat="40.606085" lon="-111.518173">
    <ele>2721.45</ele>
    </trkpt>
    <trkpt lat="40.6061" lon="-111.517946">
    <ele>2720.5</ele>
    </trkpt>
    <trkpt lat="40.606084" lon="-111.517487">
    <ele>2720.45</ele>
    </trkpt>
    <trkpt lat="40.605989" lon="-111.516289">
    <ele>2722.55</ele>
    </trkpt>
    <trkpt lat="40.605927" lon="-111.515513">
    <ele>2721.1</ele>
    </trkpt>
    <trkpt lat="40.605817" lon="-111.514504">
    <ele>2720.9</ele>
    </trkpt>
    <trkpt lat="40.605768" lon="-111.51374">
    <ele>2717.45</ele>
    </trkpt>
    <trkpt lat="40.605753" lon="-111.512171">
    <ele>2712.2</ele>
    </trkpt>
    <trkpt lat="40.605681" lon="-111.510888">
    <ele>2713.45</ele>
    </trkpt>
    <trkpt lat="40.60562" lon="-111.509951">
    <ele>2718.25</ele>
    </trkpt>
    <trkpt lat="40.605617" lon="-111.509805">
    <ele>2719.05</ele>
    </trkpt>
    <trkpt lat="40.605636" lon="-111.509555">
    <ele>2721.2</ele>
    </trkpt>
    <trkpt lat="40.605691" lon="-111.50929">
    <ele>2723.9</ele>
    </trkpt>
    <trkpt lat="40.605764" lon="-111.509099">
    <ele>2725.35</ele>
    </trkpt>
    <trkpt lat="40.605905" lon="-111.508871">
    <ele>2728.25</ele>
    </trkpt>
    <trkpt lat="40.605997" lon="-111.508753">
    <ele>2728.73</ele>
    </trkpt>
    <trkpt lat="40.606174" lon="-111.508593">
    <ele>2729.24</ele>
    </trkpt>
    <trkpt lat="40.606362" lon="-111.508402">
    <ele>2728.4</ele>
    </trkpt>
    <trkpt lat="40.60644" lon="-111.508275">
    <ele>2727.11</ele>
    </trkpt>
    <trkpt lat="40.606466" lon="-111.508219">
    <ele>2726.1</ele>
    </trkpt>
    <trkpt lat="40.606528" lon="-111.508045">
    <ele>2724.2</ele>
    </trkpt>
    <trkpt lat="40.606721" lon="-111.507446">
    <ele>2719.45</ele>
    </trkpt>
    <trkpt lat="40.606855" lon="-111.507044">
    <ele>2717.65</ele>
    </trkpt>
    <trkpt lat="40.606927" lon="-111.506909">
    <ele>2717.4</ele>
    </trkpt>
    <trkpt lat="40.606988" lon="-111.50682">
    <ele>2716.95</ele>
    </trkpt>
    <trkpt lat="40.607068" lon="-111.506742">
    <ele>2716.2</ele>
    </trkpt>
    <trkpt lat="40.607497" lon="-111.506407">
    <ele>2712.25</ele>
    </trkpt>
    <trkpt lat="40.607625" lon="-111.506299">
    <ele>2712.15</ele>
    </trkpt>
    <trkpt lat="40.607666" lon="-111.50628">
    <ele>2711.7</ele>
    </trkpt>
    <trkpt lat="40.607744" lon="-111.506271">
    <ele>2710.3</ele>
    </trkpt>
    <trkpt lat="40.607776" lon="-111.506278">
    <ele>2710.1</ele>
    </trkpt>
    <trkpt lat="40.607796" lon="-111.506289">
    <ele>2709.95</ele>
    </trkpt>
    <trkpt lat="40.607824" lon="-111.506345">
    <ele>2709.31</ele>
    </trkpt>
    <trkpt lat="40.60782" lon="-111.506405">
    <ele>2708.6</ele>
    </trkpt>
    <trkpt lat="40.607786" lon="-111.506457">
    <ele>2708.25</ele>
    </trkpt>
    <trkpt lat="40.607616" lon="-111.506605">
    <ele>2707</ele>
    </trkpt>
    <trkpt lat="40.607435" lon="-111.506812">
    <ele>2706.15</ele>
    </trkpt>
    <trkpt lat="40.607251" lon="-111.507139">
    <ele>2705</ele>
    </trkpt>
    <trkpt lat="40.60711" lon="-111.507443">
    <ele>2703.25</ele>
    </trkpt>
    <trkpt lat="40.607086" lon="-111.507545">
    <ele>2702.8</ele>
    </trkpt>
    <trkpt lat="40.607078" lon="-111.507626">
    <ele>2702.45</ele>
    </trkpt>
    <trkpt lat="40.607084" lon="-111.507664">
    <ele>2702</ele>
    </trkpt>
    <trkpt lat="40.607116" lon="-111.50773">
    <ele>2700.8</ele>
    </trkpt>
    <trkpt lat="40.607146" lon="-111.507751">
    <ele>2700.26</ele>
    </trkpt>
    <trkpt lat="40.607194" lon="-111.507753">
    <ele>2699.55</ele>
    </trkpt>
    <trkpt lat="40.607221" lon="-111.50774">
    <ele>2699.1</ele>
    </trkpt>
    <trkpt lat="40.607242" lon="-111.507718">
    <ele>2698.6</ele>
    </trkpt>
    <trkpt lat="40.607344" lon="-111.507537">
    <ele>2696.4</ele>
    </trkpt>
    <trkpt lat="40.607435" lon="-111.507427">
    <ele>2694.65</ele>
    </trkpt>
    <trkpt lat="40.607599" lon="-111.507312">
    <ele>2692.55</ele>
    </trkpt>
    <trkpt lat="40.607734" lon="-111.50726">
    <ele>2690.35</ele>
    </trkpt>
    <trkpt lat="40.607909" lon="-111.507215">
    <ele>2687.95</ele>
    </trkpt>
    <trkpt lat="40.60819" lon="-111.507172">
    <ele>2684.75</ele>
    </trkpt>
    <trkpt lat="40.608453" lon="-111.50716">
    <ele>2680.05</ele>
    </trkpt>
    <trkpt lat="40.608618" lon="-111.507119">
    <ele>2677.59</ele>
    </trkpt>
    <trkpt lat="40.608872" lon="-111.507019">
    <ele>2673.15</ele>
    </trkpt>
    <trkpt lat="40.609415" lon="-111.506708">
    <ele>2664.95</ele>
    </trkpt>
    <trkpt lat="40.609596" lon="-111.50665">
    <ele>2662.86</ele>
    </trkpt>
    <trkpt lat="40.609705" lon="-111.506638">
    <ele>2661.4</ele>
    </trkpt>
    <trkpt lat="40.609835" lon="-111.506643">
    <ele>2659.35</ele>
    </trkpt>
    <trkpt lat="40.610508" lon="-111.50674">
    <ele>2647.58</ele>
    </trkpt>
    <trkpt lat="40.610833" lon="-111.506774">
    <ele>2644.15</ele>
    </trkpt>
    <trkpt lat="40.611446" lon="-111.50685">
    <ele>2635.5</ele>
    </trkpt>
    <trkpt lat="40.612041" lon="-111.506885">
    <ele>2626.35</ele>
    </trkpt>
    <trkpt lat="40.612322" lon="-111.506868">
    <ele>2622.8</ele>
    </trkpt>
    <trkpt lat="40.612498" lon="-111.506825">
    <ele>2621</ele>
    </trkpt>
    <trkpt lat="40.612713" lon="-111.506731">
    <ele>2618.35</ele>
    </trkpt>
    <trkpt lat="40.612889" lon="-111.506672">
    <ele>2615.9</ele>
    </trkpt>
    <trkpt lat="40.613516" lon="-111.506642">
    <ele>2605.3</ele>
    </trkpt>
    <trkpt lat="40.613672" lon="-111.506652">
    <ele>2603.45</ele>
    </trkpt>
    <trkpt lat="40.614148" lon="-111.506711">
    <ele>2597.2</ele>
    </trkpt>
    <trkpt lat="40.614357" lon="-111.506778">
    <ele>2594.55</ele>
    </trkpt>
    <trkpt lat="40.614481" lon="-111.506838">
    <ele>2593.15</ele>
    </trkpt>
    <trkpt lat="40.614621" lon="-111.506929">
    <ele>2590.5</ele>
    </trkpt>
    <trkpt lat="40.615024" lon="-111.507273">
    <ele>2583.15</ele>
    </trkpt>
    <trkpt lat="40.615089" lon="-111.507319">
    <ele>2582.36</ele>
    </trkpt>
    <trkpt lat="40.61526" lon="-111.507427">
    <ele>2579.95</ele>
    </trkpt>
    <trkpt lat="40.615365" lon="-111.507474">
    <ele>2578.4</ele>
    </trkpt>
    <trkpt lat="40.615449" lon="-111.507499">
    <ele>2577.5</ele>
    </trkpt>
    <trkpt lat="40.615613" lon="-111.507519">
    <ele>2575.04</ele>
    </trkpt>
    <trkpt lat="40.615958" lon="-111.507499">
    <ele>2570.7</ele>
    </trkpt>
    <trkpt lat="40.616128" lon="-111.507479">
    <ele>2568.4</ele>
    </trkpt>
    <trkpt lat="40.616381" lon="-111.507422">
    <ele>2565.67</ele>
    </trkpt>
    <trkpt lat="40.616584" lon="-111.507168">
    <ele>2566.15</ele>
    </trkpt>
    <trkpt lat="40.616801" lon="-111.50696">
    <ele>2564.05</ele>
    </trkpt>
    <trkpt lat="40.616893" lon="-111.506836">
    <ele>2563.52</ele>
    </trkpt>
    <trkpt lat="40.617091" lon="-111.506636">
    <ele>2560.8</ele>
    </trkpt>
    <trkpt lat="40.617185" lon="-111.506467">
    <ele>2559.85</ele>
    </trkpt>
    <trkpt lat="40.617463" lon="-111.50607">
    <ele>2555.65</ele>
    </trkpt>
    <trkpt lat="40.617609" lon="-111.505711">
    <ele>2553.4</ele>
    </trkpt>
    <trkpt lat="40.617674" lon="-111.505374">
    <ele>2552.75</ele>
    </trkpt>
    <trkpt lat="40.617953" lon="-111.504748">
    <ele>2547.85</ele>
    </trkpt>
    <trkpt lat="40.61803" lon="-111.50445">
    <ele>2547.15</ele>
    </trkpt>
    <trkpt lat="40.618046" lon="-111.504255">
    <ele>2547</ele>
    </trkpt>
    <trkpt lat="40.61818" lon="-111.503684">
    <ele>2543.5</ele>
    </trkpt>
    <trkpt lat="40.618308" lon="-111.503336">
    <ele>2542.7</ele>
    </trkpt>
    <trkpt lat="40.618436" lon="-111.503149">
    <ele>2541.2</ele>
    </trkpt>
    <trkpt lat="40.618497" lon="-111.502922">
    <ele>2540.52</ele>
    </trkpt>
    <trkpt lat="40.618561" lon="-111.502577">
    <ele>2540.05</ele>
    </trkpt>
    <trkpt lat="40.618586" lon="-111.502386">
    <ele>2540.05</ele>
    </trkpt>
    <trkpt lat="40.618602" lon="-111.502058">
    <ele>2539.79</ele>
    </trkpt>
    <trkpt lat="40.618638" lon="-111.502062">
    <ele>2538.65</ele>
    </trkpt>
    <trkpt lat="40.618757" lon="-111.502032">
    <ele>2535.75</ele>
    </trkpt>
    <trkpt lat="40.61898" lon="-111.501913">
    <ele>2530.91</ele>
    </trkpt>
    <trkpt lat="40.619389" lon="-111.50161">
    <ele>2526.9</ele>
    </trkpt>
    <trkpt lat="40.619643" lon="-111.501369">
    <ele>2524.05</ele>
    </trkpt>
    <trkpt lat="40.620054" lon="-111.500935">
    <ele>2519.05</ele>
    </trkpt>
    <trkpt lat="40.620479" lon="-111.500538">
    <ele>2514.5</ele>
    </trkpt>
    <trkpt lat="40.620518" lon="-111.500475">
    <ele>2514.05</ele>
    </trkpt>
    <trkpt lat="40.620545" lon="-111.500412">
    <ele>2513.35</ele>
    </trkpt>
    <trkpt lat="40.620577" lon="-111.500302">
    <ele>2512</ele>
    </trkpt>
    <trkpt lat="40.620621" lon="-111.499842">
    <ele>2508.31</ele>
    </trkpt>
    <trkpt lat="40.620644" lon="-111.499573">
    <ele>2507.1</ele>
    </trkpt>
    <trkpt lat="40.620754" lon="-111.498941">
    <ele>2502.7</ele>
    </trkpt>
    <trkpt lat="40.620786" lon="-111.498714">
    <ele>2500.95</ele>
    </trkpt>
    <trkpt lat="40.620795" lon="-111.498495">
    <ele>2499.5</ele>
    </trkpt>
    <trkpt lat="40.620788" lon="-111.498285">
    <ele>2498.4</ele>
    </trkpt>
    <trkpt lat="40.620765" lon="-111.498046">
    <ele>2496.45</ele>
    </trkpt>
    <trkpt lat="40.620726" lon="-111.497836">
    <ele>2495</ele>
    </trkpt>
    <trkpt lat="40.620664" lon="-111.497586">
    <ele>2493.3</ele>
    </trkpt>
    <trkpt lat="40.620593" lon="-111.497364">
    <ele>2492.15</ele>
    </trkpt>
    <trkpt lat="40.620457" lon="-111.49707">
    <ele>2490.4</ele>
    </trkpt>
    <trkpt lat="40.620332" lon="-111.496828">
    <ele>2488.6</ele>
    </trkpt>
    <trkpt lat="40.620215" lon="-111.49655">
    <ele>2486.3</ele>
    </trkpt>
    <trkpt lat="40.62013" lon="-111.496304">
    <ele>2484.5</ele>
    </trkpt>
    <trkpt lat="40.620026" lon="-111.495861">
    <ele>2480.73</ele>
    </trkpt>
    <trkpt lat="40.620001" lon="-111.495723">
    <ele>2479.73</ele>
    </trkpt>
    <trkpt lat="40.620138" lon="-111.495797">
    <ele>2477.4</ele>
    </trkpt>
    <trkpt lat="40.620317" lon="-111.495872">
    <ele>2473.95</ele>
    </trkpt>
    <trkpt lat="40.62047" lon="-111.495976">
    <ele>2470.85</ele>
    </trkpt>
    <trkpt lat="40.620503" lon="-111.49598">
    <ele>2470.15</ele>
    </trkpt>
    <trkpt lat="40.620514" lon="-111.495968">
    <ele>2469.75</ele>
    </trkpt>
    <trkpt lat="40.620521" lon="-111.495911">
    <ele>2468.93</ele>
    </trkpt>
    <trkpt lat="40.620518" lon="-111.495855">
    <ele>2468.25</ele>
    </trkpt>
    <trkpt lat="40.620466" lon="-111.495783">
    <ele>2468.45</ele>
    </trkpt>
    <trkpt lat="40.620464" lon="-111.495741">
    <ele>2467.95</ele>
    </trkpt>
    <trkpt lat="40.620474" lon="-111.495734">
    <ele>2467.55</ele>
    </trkpt>
    <trkpt lat="40.620526" lon="-111.49575">
    <ele>2466.3</ele>
    </trkpt>
    <trkpt lat="40.620572" lon="-111.49579">
    <ele>2465.75</ele>
    </trkpt>
    <trkpt lat="40.620587" lon="-111.4958">
    <ele>2465.5</ele>
    </trkpt>
    <trkpt lat="40.620597" lon="-111.495796">
    <ele>2465.15</ele>
    </trkpt>
    <trkpt lat="40.620605" lon="-111.495784">
    <ele>2464.75</ele>
    </trkpt>
    <trkpt lat="40.620605" lon="-111.495766">
    <ele>2464.5</ele>
    </trkpt>
    <trkpt lat="40.620562" lon="-111.49564">
    <ele>2463.8</ele>
    </trkpt>
    <trkpt lat="40.620569" lon="-111.495601">
    <ele>2463.1</ele>
    </trkpt>
    <trkpt lat="40.620599" lon="-111.495601">
    <ele>2462.3</ele>
    </trkpt>
    <trkpt lat="40.62067" lon="-111.495675">
    <ele>2461.6</ele>
    </trkpt>
    <trkpt lat="40.620689" lon="-111.495677">
    <ele>2461.15</ele>
    </trkpt>
    <trkpt lat="40.620701" lon="-111.495667">
    <ele>2460.7</ele>
    </trkpt>
    <trkpt lat="40.620717" lon="-111.495621">
    <ele>2459.55</ele>
    </trkpt>
    <trkpt lat="40.620894" lon="-111.495806">
    <ele>2456.9</ele>
    </trkpt>
    <trkpt lat="40.620968" lon="-111.495912">
    <ele>2455.75</ele>
    </trkpt>
    <trkpt lat="40.620981" lon="-111.495923">
    <ele>2455.65</ele>
    </trkpt>
    <trkpt lat="40.621013" lon="-111.49592">
    <ele>2455.21</ele>
    </trkpt>
    <trkpt lat="40.620971" lon="-111.49557">
    <ele>2452.9</ele>
    </trkpt>
    <trkpt lat="40.620945" lon="-111.495442">
    <ele>2451.78</ele>
    </trkpt>
    <trkpt lat="40.620866" lon="-111.495243">
    <ele>2450</ele>
    </trkpt>
    <trkpt lat="40.620717" lon="-111.494983">
    <ele>2448.75</ele>
    </trkpt>
    <trkpt lat="40.620457" lon="-111.4946">
    <ele>2445.75</ele>
    </trkpt>
    <trkpt lat="40.620142" lon="-111.494265">
    <ele>2442</ele>
    </trkpt>
    <trkpt lat="40.620102" lon="-111.494197">
    <ele>2441.45</ele>
    </trkpt>
    <trkpt lat="40.620062" lon="-111.494101">
    <ele>2440.4</ele>
    </trkpt>
    <trkpt lat="40.620045" lon="-111.493991">
    <ele>2439.2</ele>
    </trkpt>
    <trkpt lat="40.620045" lon="-111.49386">
    <ele>2438.45</ele>
    </trkpt>
    <trkpt lat="40.620115" lon="-111.493291">
    <ele>2435.55</ele>
    </trkpt>
    <trkpt lat="40.620116" lon="-111.492995">
    <ele>2434.4</ele>
    </trkpt>
    <trkpt lat="40.620097" lon="-111.492847">
    <ele>2433.8</ele>
    </trkpt>
    <trkpt lat="40.619904" lon="-111.4921">
    <ele>2430.05</ele>
    </trkpt>
    <trkpt lat="40.619896" lon="-111.491992">
    <ele>2430</ele>
    </trkpt>
    <trkpt lat="40.619909" lon="-111.491877">
    <ele>2429.6</ele>
    </trkpt>
    <trkpt lat="40.619948" lon="-111.491761">
    <ele>2428.65</ele>
    </trkpt>
    <trkpt lat="40.619997" lon="-111.491679">
    <ele>2427.95</ele>
    </trkpt>
    <trkpt lat="40.620096" lon="-111.491584">
    <ele>2426.45</ele>
    </trkpt>
    <trkpt lat="40.620187" lon="-111.491548">
    <ele>2425.95</ele>
    </trkpt>
    <trkpt lat="40.620267" lon="-111.491544">
    <ele>2425.35</ele>
    </trkpt>
    <trkpt lat="40.620361" lon="-111.491572">
    <ele>2424.5</ele>
    </trkpt>
    <trkpt lat="40.620423" lon="-111.491615">
    <ele>2424</ele>
    </trkpt>
    <trkpt lat="40.620511" lon="-111.4917">
    <ele>2423.2</ele>
    </trkpt>
    <trkpt lat="40.620562" lon="-111.491807">
    <ele>2422.05</ele>
    </trkpt>
    <trkpt lat="40.620586" lon="-111.491914">
    <ele>2421.4</ele>
    </trkpt>
    <trkpt lat="40.620594" lon="-111.492068">
    <ele>2420.2</ele>
    </trkpt>
    <trkpt lat="40.620564" lon="-111.492544">
    <ele>2417.4</ele>
    </trkpt>
    <trkpt lat="40.62058" lon="-111.492857">
    <ele>2415.9</ele>
    </trkpt>
    <trkpt lat="40.620619" lon="-111.493027">
    <ele>2415.21</ele>
    </trkpt>
    <trkpt lat="40.620665" lon="-111.493155">
    <ele>2414.05</ele>
    </trkpt>
    <trkpt lat="40.620719" lon="-111.493272">
    <ele>2412.9</ele>
    </trkpt>
    <trkpt lat="40.620792" lon="-111.493377">
    <ele>2411.65</ele>
    </trkpt>
    <trkpt lat="40.620888" lon="-111.493475">
    <ele>2409.7</ele>
    </trkpt>
    <trkpt lat="40.620984" lon="-111.49354">
    <ele>2408.25</ele>
    </trkpt>
    <trkpt lat="40.621143" lon="-111.493617">
    <ele>2406.5</ele>
    </trkpt>
    <trkpt lat="40.621739" lon="-111.493865">
    <ele>2398.57</ele>
    </trkpt>
    <trkpt lat="40.622285" lon="-111.494043">
    <ele>2391.57</ele>
    </trkpt>
    <trkpt lat="40.622405" lon="-111.494101">
    <ele>2390.1</ele>
    </trkpt>
    <trkpt lat="40.622599" lon="-111.494214">
    <ele>2387.8</ele>
    </trkpt>
    <trkpt lat="40.622781" lon="-111.494349">
    <ele>2384.9</ele>
    </trkpt>
    <trkpt lat="40.622967" lon="-111.494526">
    <ele>2382.95</ele>
    </trkpt>
    <trkpt lat="40.623093" lon="-111.49467">
    <ele>2381.55</ele>
    </trkpt>
    <trkpt lat="40.623277" lon="-111.494946">
    <ele>2379.37</ele>
    </trkpt>
    </trkseg>
    </trk>
    </gpx>
    =========< cut here for mountaincurves.py >=========
    # #################################################################
    # mountaincurves.py
    # GPX road geometry analysis
    #
    # Calculates:
    # Corner radii
    # Left/right turn directions
    # Curvature statistics
    # Top 5 tightest hairpins
    #
    # Use model:
    # python mountaincurves.py [input.gpx]
    #
    # Examples:
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # #################################################################
    # Moki Dugway
    # <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    # <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    # Shafer Canyon
    # <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    # <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    # Burr Trail
    # <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    # <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    # Guardsman Pass
    # <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    # <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>
    # #################################################################
    # v1.7 20261104 Ran a random control test on Utah mountain roads
    # Suggested by Blaine Message-ID: <11cficq$pl38$1@dont-email.me>
    # #################################################################
    # Four Utah test roads (randomly selected on comp.lang.python)
    # 1. Moki Dugway
    # 2. Shafer Canyon Road (Shafer Trail)
    # 3. Burr Trail
    # 4. Guardsman Pass
    #
    # Shafer Canyon and Burr Trail have steep switchback sections.
    # Moki Dugway has sustained descending switchbacks.
    # Guardsman Pass is a paved-mountain-road comparison.
    # ###################################################################
    # <https://gpx.studio/>
    # 1. Open the appropriate road link below.
    # 2. Select File > New.
    # 3. Select the route-planning tool (pen icon).
    # 4. Select the appropriate routing mode (bicycle).
    # 5. Trace the complete road or click beginning & ending points.
    # 6. Select File > Export > Download file.
    # 7. Save using the suggested filename.
    # 8. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # -------------------------------------------------------------------
    # <https://overpass-turbo.eu/>
    # 1. Open the appropriate road link below.
    # 2. Delete the existing query in the editor (if any).
    # 3. Copy ONE query below into the editor and press the "Run" icon.
    # 4. Press the "Search" icon to zoom into the highlighted results.
    # 5. Select Export > Data > GPX
    # 6. Save using the suggested filename.
    # 7. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # ###################################################################
    # Moki Dugway, Utah State Route 261, Cedar Mesa, Utah.
    # I traced the steep switchback section
    # <https://gpx.studio/app#14.41/37.27473/-109.93787>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Moki Dugway - southern hairpin extension
    # (
    # way["highway"]
    # (37.17,-109.96,37.23,-109.91);
    # );
    # (._;>;);
    # out body;
    # Save as mokidugway.gpx
    # -------------------------------------------------------------------
    # Shafer Canyon Road (Shafer Trail) Canyonlands National Park, Utah
    # <https://gpx.studio/app#15/38.45303/-109.82112>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # way["highway"]["name"~"Shafer Trail|Shafer Canyon",i]
    # (38.43,-109.84,38.51,-109.77);
    # (._;>;);
    # out body;
    # Save as shafercanyon.gpx
    # -------------------------------------------------------------------
    # Burr Trail, Boulder, Utah, through Long Canyon and Waterpocket Fold.
    # <https://gpx.studio/app#14.55/37.85138/-111.03141>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Burr Trail, Boulder, Utah
    # // Long Canyon and Waterpocket Fold
    # (
    # way["highway"]["name"~"Burr Trail",i]
    # (37.81,-111.08,37.90,-110.98);
    # );
    # (._;>;);
    # out body;
    #
    # Save as burrtrail.gpx
    # -------------------------------------------------------------------
    # Guardsman Pass, Wasatch Mountains, between Brighton & Park City, Utah.
    # <https://gpx.studio/app#13.81/40.61548/-111.52533>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Guardsman Pass
    # // Wasatch Mountains, between Brighton and Park City, Utah
    # (
    # way["highway"]["name"~"Guardsman Pass|Guardsman Pass Road",i]
    # (40.55,-111.62,40.66,-111.48);
    # );
    # Save as guardsmanpass.gpx
    # ###################################################################
    # RUNNING THE FOUR TESTS
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # ###################################################################
    # Results will be inserted here after GPX analysis.
    #
    # Moki Dugway:
    # Pending GPX analysis.
    #
    # Shafer Canyon:
    # Pending GPX analysis.
    #
    # Burr Trail:
    # Pending GPX analysis.
    #
    # Guardsman Pass:
    # Pending GPX analysis.
    #
    # ###################################################################

    import xml.etree.ElementTree as ET
    import math
    import sys


    def parse_gpx(filename):
    tree = ET.parse(filename)
    root = tree.getroot()

    points = []

    for trkpt in root.iter(
    '{http://www.topografix.com/GPX/1/1}trkpt'
    ):
    lat = float(trkpt.get('lat'))
    lon = float(trkpt.get('lon'))
    points.append((lat, lon))

    return points


    def calculate_curvature(p1, p2, p3):

    lat_scale = 111132.92
    lon_scale = 111412.84 * math.cos(math.radians(p2[0]))

    def to_m(p):
    return (
    (p[1] - p2[1]) * lon_scale,
    (p[0] - p2[0]) * lat_scale
    )

    A = to_m(p1)
    B = (0.0, 0.0)
    C = to_m(p3)

    a = math.hypot(B[0]-C[0], B[1]-C[1])
    b = math.hypot(A[0]-C[0], A[1]-C[1])
    c = math.hypot(A[0]-B[0], A[1]-B[1])

    s = (a + b + c) / 2.0
    area_sq = s * (s-a) * (s-b) * (s-c)

    if area_sq <= 0 or a*b*c == 0:
    return float('inf'), "Straight"

    area = math.sqrt(abs(area_sq))
    radius = (a*b*c) / (4.0*area)

    cross = (
    (A[0]-B[0]) * (C[1]-B[1])
    - (A[1]-B[1]) * (C[0]-B[0])
    )

    direction = "Left" if cross > 0 else "Right"

    return radius, direction


    if __name__ == "__main__":

    if len(sys.argv) > 1:
    gpx_filename = sys.argv[1]
    else:
    gpx_filename = 'mokidugway.gpx'
    print(
    f"No filename provided. "
    f"Defaulting to '{gpx_filename}'..."
    )

    try:
    pts = parse_gpx(gpx_filename)

    except FileNotFoundError:
    print(
    f"Error: Could not find GPX file "
    f"'{gpx_filename}'."
    )
    sys.exit(1)

    except ET.ParseError:
    print(
    f"Error: Could not parse GPX file "
    f"'{gpx_filename}'."
    )
    sys.exit(1)

    print(
    f"Loaded {len(pts)} raw track points "
    f"from '{gpx_filename}'."
    )

    left_turns = 0
    right_turns = 0
    curve_records = []

    for i in range(len(pts)-2):

    r, direction = calculate_curvature(
    pts[i],
    pts[i+1],
    pts[i+2]
    )

    if r < 200:

    curve_records.append(
    (
    r,
    direction,
    pts[i+1][0],
    pts[i+1][1]
    )
    )

    if direction == "Left":
    left_turns += 1

    elif direction == "Right":
    right_turns += 1

    print(
    f"\n--- Road Geometric Analysis: "
    f"{gpx_filename} ---"
    )

    print(
    f"Detected sharp/moderate curves (R < 200m): "
    f"{len(curve_records)}"
    )

    print(
    f"Left-hand turning distribution: {left_turns}"
    )

    print(
    f"Right-hand turning distribution: {right_turns}"
    )

    if curve_records:

    curve_records.sort(key=lambda x: x[0])

    print(
    f"Minimum corner radius (tightest hairpin): "
    f"{curve_records[0][0]:.2f} meters"
    )

    print("\n--- Top 5 Tightest Hairpins / Curves ---")

    for idx, (r, direction, lat, lon) in enumerate(
    curve_records[:5], 1
    ):

    print(
    f"{idx}. Radius: {r:.2f}m | "
    f"Direction: {direction} | "
    f"Lat/Lon: {lat:.6f}, {lon:.6f}"
    )

    # ###################################################################
    # END OF mountaincurves.py
    # ###################################################################
    # Results:
    # C:\> python mountaincurves.py mokidugway.gpx
    # Loaded 220 raw track points from 'mokidugway.gpx'.
    # --- Road Geometric Analysis: mokidugway.gpx ---
    # Detected sharp/moderate curves (R < 200m): 154
    # Left-hand turning distribution: 76
    # Right-hand turning distribution: 78
    # Minimum corner radius (tightest hairpin): 5.89 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 5.89m | Direction: Right | Lat/Lon: 37.276825, -109.935955
    # 2. Radius: 7.00m | Direction: Left | Lat/Lon: 37.272532, -109.944278
    # 3. Radius: 7.67m | Direction: Left | Lat/Lon: 37.272507, -109.944243
    # 4. Radius: 8.48m | Direction: Right | Lat/Lon: 37.276883, -109.935927
    # 5. Radius: 8.84m | Direction: Right | Lat/Lon: 37.276849, -109.935935
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py shafercanyon.gpx
    # Loaded 162 raw track points from 'shafercanyon.gpx'.
    #
    # --- Road Geometric Analysis: shafercanyon.gpx ---
    # Detected sharp/moderate curves (R < 200m): 131
    # Left-hand turning distribution: 66
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 3.97 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 3.97m | Direction: Right | Lat/Lon: 38.449308, -109.820485
    # 2. Radius: 4.44m | Direction: Left | Lat/Lon: 38.448474, -109.818339
    # 3. Radius: 6.81m | Direction: Left | Lat/Lon: 38.447882, -109.818434
    # 4. Radius: 7.10m | Direction: Left | Lat/Lon: 38.447199, -109.819240
    # 5. Radius: 7.93m | Direction: Right | Lat/Lon: 38.450305, -109.819414
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py burrtrail.gpx
    # Loaded 199 raw track points from 'burrtrail.gpx'.
    #
    # --- Road Geometric Analysis: burrtrail.gpx ---
    # Detected sharp/moderate curves (R < 200m): 139
    # Left-hand turning distribution: 71
    # Right-hand turning distribution: 68
    # Minimum corner radius (tightest hairpin): 4.70 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 4.70m | Direction: Left | Lat/Lon: 37.848198, -111.024654
    # 2. Radius: 6.16m | Direction: Left | Lat/Lon: 37.848657, -111.023535
    # 3. Radius: 6.88m | Direction: Right | Lat/Lon: 37.850700, -111.027191
    # 4. Radius: 7.59m | Direction: Right | Lat/Lon: 37.850662, -111.027217
    # 5. Radius: 7.73m | Direction: Right | Lat/Lon: 37.850838, -111.025700
    #
    # # -------------------------------------------------------------------
    # C:\> python mountaincurves.py guardsmanpass.gpx
    # Loaded 219 raw track points from 'guardsmanpass.gpx'.
    #
    # --- Road Geometric Analysis: guardsmanpass.gpx ---
    # Detected sharp/moderate curves (R < 200m): 135
    # Left-hand turning distribution: 70
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 2.04 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620587, -111.495800
    # 2. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620605, -111.495784
    # 3. Radius: 2.29m | Direction: Left | Lat/Lon: 40.620597, -111.495796
    # 4. Radius: 2.33m | Direction: Right | Lat/Lon: 40.620464, -111.495741
    # 5. Radius: 2.71m | Direction: Right | Lat/Lon: 40.620569, -111.495601
    # -------------------------------------------------------------------
    # ###################################################################
    # Analysis of predicted abnormal front tire wear on Utah roads
    # Moki Dugway, Shafer Canyon, Burr Trail & Guardsman Pass
    #
    # The objective was to predict abnormal outside-front tire shoulder wear
    # resulting from downhill braking & steering-induced tire scrub on turns.
    #
    # Two websites were used to obtain the GPX tracks:
    # <https://gpx.studio/>
    # <https://overpass-turbo.eu/>
    #
    # The Python script will analyze the GPX tracks, calculating corner radii,
    # left/right turning distributions & the 5 tightest calculated hairpins.
    #
    # I selected one downhill direction for each road wherever possible:
    # Moki Dugway: North to South, descending Cedar Mesa.
    # Shafer Canyon: Island in the Sky down to Potash Road.
    # Burr Trail: Boulder toward Bullfrog.
    # Guardsman Pass: From the pass toward Park City.
    #
    # Summary of GPX Analysis
    # 1. Moki Dugway
    # GPX points: 220
    # Sharp/moderate curve windows: 154
    # Left turns: 76
    # Right turns: 78
    # Minimum calculated radius: 5.89 meters
    # Assessment:
    # Sustained downhill cornering with balanced tire loading.
    # Moki Dugway has a substantial number of tight switchbacks
    # over a relatively short descent.
    # The left/right distribution is almost perfectly balanced
    # (49.4% left / 50.6% right).
    # Consequently, the expected lateral loading is reasonably
    # balanced between the two front tires, with a very slight
    # theoretical bias toward the left front tire.
    # The 5.89-meter minimum calculated radius indicates a
    # potentially tight corner, although the actual radius
    # should be verified against the road geometry.
    #
    # 2. Shafer Canyon Road
    # GPX points: 162
    # Sharp/moderate curve windows: 131
    # Left turns: 66
    # Right turns: 65
    # Minimum calculated radius: 3.97 meters
    # Assessment:
    # Extremely demanding switchback geometry.
    # Shafer Canyon has the tightest reported minimum radius
    # among the first three reasonably comparable measurements.
    # Its 1,500-foot descent through the sandstone cliffs
    # makes it good test case for downhill braking and cornering.
    # The left/right distribution is virtually symmetrical
    # (50.4% left / 49.6% right).
    # There is therefore no meaningful predicted preference
    # for either front tire based on turn counts alone.
    #
    # 3. Burr Trail
    # GPX points: 199
    # Sharp/moderate curve windows: 139
    # Left turns: 71
    # Right turns: 68
    # Minimum calculated radius: 4.70 meters
    # Assessment:
    # Tight switchbacks with a slight right-front loading bias.
    # The Waterpocket Fold switchbacks provide a combination of
    # steep grades and tight curves.
    # The turn distribution is balanced (51.1% left / 48.9% right).
    # There is a slight theoretical preference for right-front
    # outside-shoulder loading because of the greater number
    # of left-hand turns in the test direction. However, the
    # difference is too small to suggest tire-wear asymmetry.
    #
    # 4. Guardsman Pass
    # GPX points: 219
    # Sharp/moderate curve windows: 135
    # Left turns: 70
    # Right turns: 65
    # Minimum calculated radius: 2.04 meters
    # Assessment:
    # Mountain-road cornering with a large peak-scrub component.
    # Guardsman Pass has the fewest curve windows proportionally
    # among the four roads.
    # Its left/right distribution is slightly biased toward
    # left-hand turns (51.9% left / 48.1% right).
    # This suggests a slight theoretical preference for
    # outside-shoulder loading on the right-front tire.
    #
    # Overall Comparison
    # The four roads share an interesting characteristic that the
    # left/right turning distributions are reasonably balanced.
    #
    # Consequently, none demonstrates a strong inherent preference
    # for wearing one front tire more than the other based on
    # turn direction alone.
    #
    # The principal differences are the number of calculated
    # curves, steepness of descent and reported minimum corner radii.
    #
    # Shafer Canyon and Burr Trail have steep switchback sections.
    # Moki Dugway has sustained descending switchbacks.
    # Guardsman Pass provides a paved mountain-road comparison.
    #
    # Important Qualification
    # Actual outside-shoulder wear depends on tire pressure,
    # alignment, suspension geometry, vehicle weight, braking,
    # speed, road camber and driving style.
    # #################################################################
    --
    Usenet works because knowledgeable people take the time to help others.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Sun Nov 8 22:33:58 2026
    From Newsgroup: comp.lang.python

    On Nov 6, 2026 at 12:29:25rC>PM CST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

    Bob West wrote:
    What do automotive guys think of the camber/pressure/rotation resolutions? >>
    First, I'll ignore your insults because even though I used to think that you >> are a nutcase, I've downgraded that to just another quirky personality on
    usenet. But I am an automotive guy, so you addressed me.

    Wow. I'm impressed. Really.
    Thank you for writing a post worthy of an adult purview.
    In fact, here's an excerpt from *that* Stanford professor, who gave us hope that it can be done, &, in reality, who sparked me to write the code comparing his commute to my commute (since nobody on my hill can get
    anywhere near those kinds of miles on the inherence of our mountain road).

    -------- Begin Forwarded Message --------
    Subject: Why your front tires are unduly wearing the outside shoulder

    Tire wear is a subject of substantial interest to me, living at 3800' ASL
    at the end of XXXREDACTEDXXX Road, another windy, abrasive mountain road.
    Many years ago I bought a new Honda CRX, and I was stunned when the tires
    were worn out at just 3,000 miles! When I complained, the dealer said,
    "You're not supposed to drive it so hard." Bah.

    I've spent quite of bit of effort since then, and the last set of tires
    on my Mini Cooper JCW lasted 50,000 miles. In large part, this was a
    result
    of things I'd learned in auto racing, see my recent race-winning video at
    XXXREDACTEDXXX https://www.youtube.com/watch?v=XXXREDACTEDXXX.

    In setting up a race car, we adjusted camber and tire pressure to get the
    same temperature across the tread after several hard laps. If it was too
    hot on the outside, more negative camber (or vice versa). Then if it was
    too hot at the edges, raise the pressure to bulge the middle (again, or
    vice versa). That process made the average tread essentially flat for a
    given suspension setup, and lap times showed it. Of course our expectation
    of tire life was dramatically different, but today I still use a variation
    on these two techniques, and it's made a big difference.

    I do essentially the same process, without the temperature measurement,
    on our cars. Each car may have a different weight, drive wheels and
    suspension design, but especially on front-drive cars I start the front
    at the negative limit of factory settings, and go 1/2-# more if I see
    excess wear on the outside. On some of our cars, we've had to install
    conservative suspension mods to do this. Then I typically run +2-3 psi
    pressure to keep the center working, and go even higher if I see too
    much wear at the edges. Especially on rear drive cars, I'm more
    conservative on the drive wheels, since they aren't steering.
    But the same concept applies.

    This optimizes the setup for the curvy, abrasive XXXREDACTEDXXX-mile road
    we drive fairly vigorously every time we're going anywhere. Since the tire
    wear is mostly from our runs up and down our hill, we don't find adapting
    to this use makes much difference in traction or wear in the rest of our
    driving on freeways or city streets. We're not racing, and we're not
    looking for the huge show-off negative camber you see sometimes, just
    enough to correct the car from general-driving setting to our primary use.

    But 50,000 miles? Yep, the secret is a tire that sticks very well,
    but has very high tread wear rating. I've settled on Michelin Pilot Sport
    All Season (we get snow up here, and I no longer feel like swapping
    seasonal tires). The tread wear rating on these is an amazing 540 with
    still good wet/dry traction, and they're guaranteed for 45,000 miles.

    Last, re reliable tire service, the jury is still out. I agree most
    places don't pay enough attention. One I won't name tightened the wheel
    lugs so tight I had to replace them, even though I told them the torque
    I wanted, and had the torque wrench with me. If I find a gem, I won't be
    shy.

    I hope this adds to your discussion.
    -------- End Forwarded Message --------

    I agree with all he says, and he even concedes that the long life is mostly because of those very expensive tires. And a Mini...


    These cars are immaculately maintained. Bushings and all.
    The alignment is not wrong (on almost all of them).

    For a vehicle in flatland, for the wear patterns we are discussing, if the vehicle is properly maintained, the wear you claim is patently impossible (assuming the vehicle is well maintained & only drives typically on flats, i.e., they don't do 180's in the Las Vegas parking lots to wear the tires).

    Am I wrong?

    Sort of. First, I was not talking about failed bushings, I am talking about bushings that have the designed amount of give in them. That give is what changes the steering and suspension geometry under load, and not for the better. That is why people put polyurethane bushings in. And "typically on flats" does not mean only on flats, and when they make turns at full lock - even just pulling into a parking spot, there is substantial wear on those
    heavy rear drive vehicles. Just stand outside one as a driver accelerates at full steering lock. It's ugly to look at, and you can see the distortion of
    the geometry. The vehicle really wants to understeer even at low speeds, and that scrubs the tires in the area you are talking about. That is why I saw so much of that, and the engineers just shrugged.


    Performance tires? They
    wear out quick. HIgh mileage tires? Lower traction. There are tradeoffs.

    As you know, I'm well educated, so I know that statement to be false.
    At least in terms of information printed on every passenger tire sold in
    the USA.

    But it's not really the point of this thread that I can find tons of passenger tires rated for high treadwear and also high wet straight-line traction, just as I can find passenger tires rated for low treadware and
    low straight-line traction, and every permutation in between.

    But that's simply because of the information printed on every USA passenger-tire sidewall is inherently insufficient to make any claims
    that treadwear and traction *must* oppose each other.

    In short, that's an interesting discussion for a different thread.

    My comment was in very general terms for midline consumer tires. Micheling Pilot Sports are not those, and not cheap. I know - I had them on my bikes. so that relates to my other comments. Even if you find some solution, how much would anyone be willing to pay in time and money for a tire life extension of 1%? 5%? 10%? Some people have money to throw around, so at what % would you feel a fix is worth it?



    You
    are obsessing over nothing at all. That's why I downgraded you to just another
    quirky personality.

    I'm different than most people on Usenet for a few reasons, one of which is I'm extremely knowledgeable, and part of that knowledge is gained by having an excellent memory on Usenet threads over the decades, where Zeno was instrumental in helping all of us understand, long ago, what's happening.

    I'm also very different from many Usenet posters as most seem to treat it
    as entertainment, and even fewer seem to have any education on the topics.

    I'm also different in that I have access to my old Stanford and Harvard professors, which most people here wouldn't have that kind of contact.

    In addition, I'm wired to the core to write helpful tutorials and PSAs as
    I'm someone who cares deeply that others can do what I can do.

    I have never doubted that you are highly educated and intelligent and have a very good memory, which means you can grasp complex subjects. But it's reasonable to ask if there aren't better uses for your abilities. But you make choices and so do I, and I choose often enough to do things that are not very useful. It just entertains me.



    Whatever happened to nospam? He fell off the face of the earth. Is he dead?

    There's a recent thread from this week about him.
    Some say he was paid by Apple to deny everything bad about Apple on the iOS newsgroups, where when we pointed that out, he instantly disappeared.

    Who knows what really happened to him, or David Empson (who truly
    understood his stuff) or Michelle Steiner (who fought for the group to be included as misc.phone.mobile.iphone) or the Apple religious zealots JF
    Mezei or Alan Browne (both of whom believed every word in every Apple white paper).

    There's only Ant, and badgolferman, Chris and maybe we can include -hh,
    left who have any sense. Although, the uneducated trolls such as Jolly
    Roger, Alan Baker, Haemactylus, Joerg Lorenz, Snit, Rod Speed, and Your
    Name still post.

    I remember that you and him used to squabble over Mac. I have no use for Apple evangelists, but I did switch over, and to me I think he was right about them just working, but I also understand why. They work fine for me, as opposed to my Win science projects. There's no right answer.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 11:23:35 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    In setting up a race car, we adjusted camber and tire pressure to get the >> same temperature across the tread after several hard laps. If it was too
    hot on the outside, more negative camber (or vice versa). Then if it was
    too hot at the edges, raise the pressure to bulge the middle (again, or
    vice versa). That process made the average tread essentially flat for a
    given suspension setup, and lap times showed it. Of course our expectation >> of tire life was dramatically different, but today I still use a variation >> on these two techniques, and it's made a big difference.

    I do essentially the same process, without the temperature measurement,
    on our cars. Each car may have a different weight, drive wheels and
    suspension design, but especially on front-drive cars I start the front
    at the negative limit of factory settings, and go 1/2# more if I see
    excess wear on the outside. On some of our cars, we've had to install
    conservative suspension mods to do this. Then I typically run +2-3 psi
    pressure to keep the center working, and go even higher if I see too
    much wear at the edges. Especially on rear drive cars, I'm more
    conservative on the drive wheels, since they aren't steering.
    But the same concept applies.

    This optimizes the setup for the curvy, abrasive XXXREDACTEDXXX-mile road >> we drive fairly vigorously every time we're going anywhere. Since the tire >> wear is mostly from our runs up and down our hill, we don't find adapting >> to this use makes much difference in traction or wear in the rest of our
    driving on freeways or city streets. We're not racing, and we're not
    looking for the huge show-off negative camber you see sometimes, just
    enough to correct the car from general-driving setting to our primary use. >>
    But 50,000 miles? Yep, the secret is a tire that sticks very well,
    but has very high tread wear rating. I've settled on Michelin Pilot Sport >> All Season (we get snow up here, and I no longer feel like swapping
    seasonal tires). The tread wear rating on these is an amazing 540 with
    still good wet/dry traction, and they're guaranteed for 45,000 miles.

    Last, re reliable tire service, the jury is still out. I agree most
    places don't pay enough attention. One I won't name tightened the wheel
    lugs so tight I had to replace them, even though I told them the torque
    I wanted, and had the torque wrench with me. If I find a gem, I won't be
    shy.

    I hope this adds to your discussion.
    -------- End Forwarded Message --------

    I agree with all he says, and he even concedes that the long life is mostly because of those very expensive tires. And a Mini...

    Hi Bob West,

    Thanks for looking at what that Stanford professor wrote to help our
    community, as he, like everyone, was inured to this specific type of mountain-induced "abnormal" tire wear until it happened to him.

    That's how it hit me, when I moved into the mountains. Bear in mind the
    Santa Cruz Mountain range isn't all that big, so it's only a few miles of
    the total commute which shreds the outboard shoulders of the front tires.

    On principle, I can't disagree on 'treadwear/traction' tradeoffs, but in practice, I must state that I trust ONLY the traction/treadwear embossed on
    the sidewall, which I admit don't seem to follow the assumed tradeoffs.

    Note: The traction printed on the sidewall is wet and straight line.
    The treadwear printed on the sidewall is an OEM-based comparative.

    These cars are immaculately maintained. Bushings and all.
    The alignment is not wrong (on almost all of them).

    For a vehicle in flatland, for the wear patterns we are discussing, if the >> vehicle is properly maintained, the wear you claim is patently impossible
    (assuming the vehicle is well maintained & only drives typically on flats, >> i.e., they don't do 180's in the Las Vegas parking lots to wear the tires). >>
    Am I wrong?

    Sort of. First, I was not talking about failed bushings, I am talking about bushings that have the designed amount of give in them. That give is what changes the steering and suspension geometry under load, and not for the better. That is why people put polyurethane bushings in. And "typically on flats" does not mean only on flats, and when they make turns at full lock - even just pulling into a parking spot, there is substantial wear on those heavy rear drive vehicles. Just stand outside one as a driver accelerates at full steering lock. It's ugly to look at, and you can see the distortion of the geometry. The vehicle really wants to understeer even at low speeds, and that scrubs the tires in the area you are talking about. That is why I saw so much of that, and the engineers just shrugged.

    Ah, when I take you seriously (as I am doing now), I learn from you as I
    had previously discounted much of what you had explained based on the
    insults that came with them.

    Looking at your information in a clean light, I appreciate the distinction you're drawing that it's not failed bushings per se, but the designed compliance in them that lets the geometry shift under load. This is a much
    more subtle and convincing explanation than blaming worn parts.

    In fact, that resonates with what we see on the Santa Cruz roads where it's only a few miles of tight, cambered turns that shred the outboard shoulders
    of the front tires, even when the vehicles are immaculately maintained with alignments that check out. It makes sense that the culprit isn't always an obvious misalignment we can measure on a flat rack, but the suspension
    geometry flexing in a way that only shows up under real cornering load.

    Your point about full-lock turns scrubbing, even at parking-lot speeds, is
    a good reminder that this isn't exclusive to the mountains.

    I'll be watching for that geometry distortion the next time I'm at full
    lock, as I'm curious whether noticeably stiffer polyurethane bushings would hold the alignment better on those few miles that do all the damage.

    Performance tires? They
    wear out quick. HIgh mileage tires? Lower traction. There are tradeoffs.

    In short, that's an interesting discussion for a different thread.

    My comment was in very general terms for midline consumer tires. Michelin Pilot Sports are not those, and not cheap. I know - I had them on my bikes. so
    that relates to my other comments. Even if you find some solution, how much would anyone be willing to pay in time and money for a tire life extension of 1%? 5%? 10%? Some people have money to throw around, so at what % would you feel a fix is worth it?

    On my K1200, I used Continental tires, but they wore out within 8K miles,
    but, as you are aware, beemer tires don't last as long as bimmer tires do.

    I must agree that the "solution" may be more onerous than the cost of
    simply replacing tires every year or two, but we can't make that
    calculation reasonable without knowing what the possible solutions are.

    1. 'Better' tires (in terms of sidewall stiffness and tire wear ratings)
    2. 'Better' bushings (in terms of stiffness to geometric deflection)
    3. 'Better' rotation pattern (in terms of X-rotation & carcass flipping)
    4. 'Better' alignment (in terms of increased negative camber)
    5. 'Better' maintenance (in terms of stiffer tires due to adding pressure)

    Anything else?

    You
    are obsessing over nothing at all. That's why I downgraded you to just another
    quirky personality.

    I'm different than most people on Usenet for a few reasons, one of which is >> I'm extremely knowledgeable, and part of that knowledge is gained by having >> an excellent memory on Usenet threads over the decades, where Zeno was
    instrumental in helping all of us understand, long ago, what's happening.
    In addition, I'm wired to the core to write helpful tutorials and PSAs as
    I'm someone who cares deeply that others can do what I can do.

    I have never doubted that you are highly educated and intelligent and have a very good memory, which means you can grasp complex subjects. But it's reasonable to ask if there aren't better uses for your abilities. But you make
    choices and so do I, and I choose often enough to do things that are not very useful. It just entertains me.

    I should write that book, similar to what Ralph Nader did with the Corsair, that can halve Apple's stock price simply by telling the truth about iOS.

    Whatever happened to nospam? He fell off the face of the earth. Is he dead? >>
    There's a recent thread from this week about him.

    I remember that you and him used to squabble over Mac. I have no use for Apple
    evangelists, but I did switch over, and to me I think he was right about them just working, but I also understand why. They work fine for me, as opposed to my Win science projects. There's no right answer.

    Be careful in that in my decades of posting to Usenet, I have posted facts, and, when/if those facts were wrong, I openly and publicly corrected them.

    Also note, that due to my scientific and engineering training, I don't fall
    for statements that nospam and the like would claim that are marketing BS.

    An example is Android had 200% the RAM and Apple products had half the RAM
    but an "efficiency" of 1% that "supposedly" made up for the lack of RAM.

    My point?
    The absurdity of Apple's Marketing bullshit what we sparred over.

    What nospam and I sparred over was his absurd claims for Apple products. Witness we sparred over the efficiency of Apple's crappy batteries, where
    the very first EU benchmarks proved Apple's claims to have been a lie.

    Fancy that.
    Apple lied.

    HINT: We sparred because nospam always propagated the Apple lies.
    That doesn't happen on the adult operating system newsgroups simply
    because nobody is gonna defend Google, M$ or RedHat to the death.
    --
    It used to be Apple only told the truth in court; Now? Not even then.
    Judge Yvonne Gonzalez Rogers, Epic Games v. Apple, April 30, 2025
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 18:49:51 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 9:23:35rC>AM CST, "Maria Sophia" <mariasophia@comprehension.com> wrote:


    Looking at your information in a clean light, I appreciate the distinction you're drawing that it's not failed bushings per se, but the designed compliance in them that lets the geometry shift under load. This is a much more subtle and convincing explanation than blaming worn parts.

    And even that can very greatly from car to car. Poly bushing won't make much difference in many cases. I'm sure you have speed shops there, and there
    should be someone who really knows this stuff for specific cars.



    On my K1200, I used Continental tires, but they wore out within 8K miles, but, as you are aware, beemer tires don't last as long as bimmer tires do.

    I must agree that the "solution" may be more onerous than the cost of
    simply replacing tires every year or two, but we can't make that
    calculation reasonable without knowing what the possible solutions are.

    1. 'Better' tires (in terms of sidewall stiffness and tire wear ratings)
    2. 'Better' bushings (in terms of stiffness to geometric deflection)
    3. 'Better' rotation pattern (in terms of X-rotation & carcass flipping)
    4. 'Better' alignment (in terms of increased negative camber)
    5. 'Better' maintenance (in terms of stiffer tires due to adding pressure)

    Anything else?

    The higher your percentage of driving that is done in those mountains, the
    more sense it makes to move to negative camber. And the toe-on-turns measurements aren't always done in a normal alignment, or they are not paid attention to. There is no adjustment for that, but if it's off, it's a bad thing, and you just need to replace the bent parts. Always check that on your alignment printout, and if it's not there, tell the shop you need to know
    that.



    Whatever happened to nospam? He fell off the face of the earth. Is he dead?

    There's a recent thread from this week about him.

    I remember that you and him used to squabble over Mac. I have no use for Apple
    evangelists, but I did switch over, and to me I think he was right about them
    just working, but I also understand why. They work fine for me, as opposed to
    my Win science projects. There's no right answer.

    Be careful in that in my decades of posting to Usenet, I have posted facts, and, when/if those facts were wrong, I openly and publicly corrected them.

    Also note, that due to my scientific and engineering training, I don't fall for statements that nospam and the like would claim that are marketing BS.

    An example is Android had 200% the RAM and Apple products had half the RAM but an "efficiency" of 1% that "supposedly" made up for the lack of RAM.

    My point?
    The absurdity of Apple's Marketing bullshit what we sparred over.

    What nospam and I sparred over was his absurd claims for Apple products. Witness we sparred over the efficiency of Apple's crappy batteries, where
    the very first EU benchmarks proved Apple's claims to have been a lie.

    Fancy that.
    Apple lied.

    HINT: We sparred because nospam always propagated the Apple lies.
    That doesn't happen on the adult operating system newsgroups simply
    because nobody is gonna defend Google, M$ or RedHat to the death.

    I like my macbook, but have no love for the company. And even if someone is getting paid to say things, i have no problem with that as long as the person believes what he is saying. I liked him on RPD because he helped with photgraphy issues. The tech stuff you are referring to is of no real interest to me, and over my head anyways. I had no way of knowing who was right.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.os.linux,comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Mon Nov 9 14:53:35 2026
    From Newsgroup: comp.lang.python

    Blaine wrote:
    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Improvement in the mapping software method of obtaining road inherences.
    1. <https://gpx.studio/>
    2. <https://overpass-turbo.eu/>
    3. <https://brouter.de/brouter-web/>

    Since every thread topic should add useful value to the tribal knowledge,
    I found another mapping method to obtain the precise GPX track file
    to be fed into the python script, which calculates the road inherency.
    <https://i.postimg.cc/6qKjCkng/mokidugway.gif>

    Since I believe in working examples, let's take Blaine's kind suggestion of
    Moki Dugway: North to South, descending Cedar Mesa
    <https://www.komoot.com/highlight/6669890>
    <https://www.utahscanyoncountry.com/The-Moki-Dugway-Scenic-Backway-Utah-Highway-261/>

    1. Point a web browser to https://brouter.de/brouter-web/
    2. In the top-left pulldown, keep "Trekking bike, Original"
    3. In the left search icon, search for "utah moki dugway"
    4. That will zoom you to the middle of the Moki Dugway
    5. Click the draw/pencil icon in the UI toolbar at left
    6. Start the click on UT 261 just north of the switchbacks,
    on top of Cedar Mesa (near the junction pointing toward Muley Point)
    7. End the click on UT 261 just south of the switchbacks down
    on the desert floor, near the Valley of the Gods turnoff.

    BRouter will automatically snap the route along the road nodes,
    calculating the 3-mile, 11% grade descent down the switchbacks.
    <https://brouter.de/brouter-web/#map=16/37.2744/-109.9351/standard&lonlats=-109.942589,37.278313;-109.942504,37.272986;-109.942504,37.272983>

    8. If desired, click on "incline coding" at left for color-coded gradients
    9. At top, click the "Export" button, choose a name & tap "Export Route"
    10. The result will be a mukidugway.gpx file that can be analyzed

    Then run the python road inherency script on that gpx output:
    python mountaincurves.py mokidugway2.gpx

    Here are the results:
    Loaded 219 raw track points from 'mokidugway2.gpx'.

    --- Road Geometric Analysis: mokidugway2.gpx ---
    Detected sharp/moderate curves (R < 200m): 159
    Left-hand turning distribution: 82
    Right-hand turning distribution: 77
    Minimum corner radius (tightest hairpin): 5.89 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 5.89m | Direction: Left | Lat/Lon: 37.276825, -109.935955
    2. Radius: 7.00m | Direction: Right | Lat/Lon: 37.272532, -109.944278
    3. Radius: 7.31m | Direction: Left | Lat/Lon: 37.276883, -109.935927
    4. Radius: 7.67m | Direction: Right | Lat/Lon: 37.272507, -109.944243
    5. Radius: 8.84m | Direction: Left | Lat/Lon: 37.276849, -109.935935

    I normally wouldn't provide the GPX file (because anyone can get the
    same file using the method above), but here it is for your purview.
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- track-length = 3867 filtered ascend = 155 plain-ascend = -264 cost=27500 energy=0.0kwh time=16m 37s -->
    <gpx
    xmlns="http://www.topografix.com/GPX/1/1"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd"
    version="1.1"
    creator="BRouter-Web 0.18.1">
    <trk>
    <name>mukidugway_brouter.gpx</name>
    <trkseg>
    <trkpt lat="37.278306" lon="-109.94258"><ele>1965</ele></trkpt>
    <trkpt lat="37.278123" lon="-109.942757"><ele>1964.75</ele></trkpt>
    <trkpt lat="37.277892" lon="-109.942955"><ele>1964.5</ele></trkpt>
    <trkpt lat="37.277849" lon="-109.942991"><ele>1964.25</ele></trkpt>
    <trkpt lat="37.277673" lon="-109.943107"><ele>1964</ele></trkpt>
    <trkpt lat="37.277546" lon="-109.943151"><ele>1963.5</ele></trkpt>
    <trkpt lat="37.277365" lon="-109.943192"><ele>1962.75</ele></trkpt>
    <trkpt lat="37.277146" lon="-109.943223"><ele>1961.5</ele></trkpt>
    <trkpt lat="37.276946" lon="-109.943206"><ele>1960.25</ele></trkpt>
    <trkpt lat="37.276749" lon="-109.943152"><ele>1959.25</ele></trkpt>
    <trkpt lat="37.276506" lon="-109.943003"><ele>1955.75</ele></trkpt>
    <trkpt lat="37.276339" lon="-109.942864"><ele>1952.25</ele></trkpt>
    <trkpt lat="37.27615" lon="-109.942659"><ele>1948</ele></trkpt>
    <trkpt lat="37.276031" lon="-109.942474"><ele>1944.75</ele></trkpt>
    <trkpt lat="37.275943" lon="-109.942273"><ele>1942.5</ele></trkpt>
    <trkpt lat="37.275809" lon="-109.9418"><ele>1938.25</ele></trkpt>
    <trkpt lat="37.275827" lon="-109.941649"><ele>1938.75</ele></trkpt>
    <trkpt lat="37.275866" lon="-109.941478"><ele>1939.25</ele></trkpt>
    <trkpt lat="37.275923" lon="-109.941156"><ele>1940.25</ele></trkpt>
    <trkpt lat="37.275927" lon="-109.941023"><ele>1940</ele></trkpt>
    <trkpt lat="37.275906" lon="-109.940883"><ele>1939.5</ele></trkpt>
    <trkpt lat="37.275871" lon="-109.940754"><ele>1937.75</ele></trkpt>
    <trkpt lat="37.27577" lon="-109.940559"><ele>1933.25</ele></trkpt>
    <trkpt lat="37.275675" lon="-109.940458"><ele>1930.5</ele></trkpt>
    <trkpt lat="37.27555" lon="-109.940369"><ele>1928</ele></trkpt>
    <trkpt lat="37.275437" lon="-109.940316"><ele>1926.5</ele></trkpt>
    <trkpt lat="37.275331" lon="-109.940287"><ele>1925.25</ele></trkpt>
    <trkpt lat="37.275216" lon="-109.940278"><ele>1923.75</ele></trkpt>
    <trkpt lat="37.274964" lon="-109.940319"><ele>1918.5</ele></trkpt>
    <trkpt lat="37.274853" lon="-109.940296"><ele>1913.25</ele></trkpt>
    <trkpt lat="37.274683" lon="-109.940198"><ele>1908.25</ele></trkpt>
    <trkpt lat="37.274193" lon="-109.939798"><ele>1902</ele></trkpt>
    <trkpt lat="37.274123" lon="-109.939727"><ele>1896.25</ele></trkpt>
    <trkpt lat="37.27409" lon="-109.939651"><ele>1892.75</ele></trkpt>
    <trkpt lat="37.274076" lon="-109.93956"><ele>1892</ele></trkpt>
    <trkpt lat="37.274091" lon="-109.939487"><ele>1894.25</ele></trkpt>
    <trkpt lat="37.274283" lon="-109.939315"><ele>1903</ele></trkpt>
    <trkpt lat="37.274372" lon="-109.939279"><ele>1903</ele></trkpt>
    <trkpt lat="37.274444" lon="-109.93929"><ele>1903.25</ele></trkpt>
    <trkpt lat="37.274518" lon="-109.939318"><ele>1903.75</ele></trkpt>
    <trkpt lat="37.274601" lon="-109.939372"><ele>1904.75</ele></trkpt>
    <trkpt lat="37.274767" lon="-109.93945"><ele>1907.25</ele></trkpt>
    <trkpt lat="37.274876" lon="-109.939491"><ele>1909.25</ele></trkpt>
    <trkpt lat="37.275129" lon="-109.93955"><ele>1911.75</ele></trkpt>
    <trkpt lat="37.27546" lon="-109.939589"><ele>1911.5</ele></trkpt>
    <trkpt lat="37.27582" lon="-109.939595"><ele>1910</ele></trkpt>
    <trkpt lat="37.276005" lon="-109.939578"><ele>1911.5</ele></trkpt>
    <trkpt lat="37.276184" lon="-109.939528"><ele>1911.5</ele></trkpt>
    <trkpt lat="37.276324" lon="-109.939458"><ele>1910.25</ele></trkpt>
    <trkpt lat="37.276518" lon="-109.939324"><ele>1907</ele></trkpt>
    <trkpt lat="37.277056" lon="-109.939012"><ele>1909.5</ele></trkpt>
    <trkpt lat="37.277234" lon="-109.938875"><ele>1911</ele></trkpt>
    <trkpt lat="37.277303" lon="-109.938794"><ele>1910.75</ele></trkpt>
    <trkpt lat="37.27737" lon="-109.938681"><ele>1909.25</ele></trkpt>
    <trkpt lat="37.277414" lon="-109.938569"><ele>1907.25</ele></trkpt>
    <trkpt lat="37.277435" lon="-109.938462"><ele>1904.5</ele></trkpt>
    <trkpt lat="37.27745" lon="-109.93835"><ele>1901.5</ele></trkpt>
    <trkpt lat="37.277455" lon="-109.938248"><ele>1901</ele></trkpt>
    <trkpt lat="37.277451" lon="-109.93815"><ele>1901</ele></trkpt>
    <trkpt lat="37.277444" lon="-109.938051"><ele>1900.75</ele></trkpt>
    <trkpt lat="37.277427" lon="-109.937949"><ele>1899.75</ele></trkpt>
    <trkpt lat="37.277295" lon="-109.937542"><ele>1892.25</ele></trkpt>
    <trkpt lat="37.277188" lon="-109.937194"><ele>1889</ele></trkpt>
    <trkpt lat="37.2771" lon="-109.936822"><ele>1887.75</ele></trkpt>
    <trkpt lat="37.277038" lon="-109.936456"><ele>1887</ele></trkpt>
    <trkpt lat="37.277004" lon="-109.936175"><ele>1886.75</ele></trkpt>
    <trkpt lat="37.276981" lon="-109.936048"><ele>1886.5</ele></trkpt>
    <trkpt lat="37.276936" lon="-109.935958"><ele>1885</ele></trkpt>
    <trkpt lat="37.276908" lon="-109.935936"><ele>1883.75</ele></trkpt>
    <trkpt lat="37.276883" lon="-109.935927"><ele>1882.5</ele></trkpt>
    <trkpt lat="37.276849" lon="-109.935935"><ele>1880.75</ele></trkpt>
    <trkpt lat="37.276825" lon="-109.935955"><ele>1879.5</ele></trkpt>
    <trkpt lat="37.276813" lon="-109.935987"><ele>1878.5</ele></trkpt>
    <trkpt lat="37.276812" lon="-109.936039"><ele>1878</ele></trkpt>
    <trkpt lat="37.276848" lon="-109.93622"><ele>1878.25</ele></trkpt>
    <trkpt lat="37.276872" lon="-109.93641"><ele>1878</ele></trkpt>
    <trkpt lat="37.276902" lon="-109.936813"><ele>1876.25</ele></trkpt>
    <trkpt lat="37.276904" lon="-109.937194"><ele>1872.5</ele></trkpt>
    <trkpt lat="37.276919" lon="-109.937481"><ele>1870.5</ele></trkpt>
    <trkpt lat="37.276953" lon="-109.937734"><ele>1874.75</ele></trkpt>
    <trkpt lat="37.276965" lon="-109.937911"><ele>1877.25</ele></trkpt>
    <trkpt lat="37.276969" lon="-109.938042"><ele>1878.75</ele></trkpt>
    <trkpt lat="37.276945" lon="-109.938145"><ele>1878.75</ele></trkpt>
    <trkpt lat="37.276911" lon="-109.938214"><ele>1878.25</ele></trkpt>
    <trkpt lat="37.276861" lon="-109.938278"><ele>1876.75</ele></trkpt>
    <trkpt lat="37.276783" lon="-109.93833"><ele>1874.5</ele></trkpt>
    <trkpt lat="37.276681" lon="-109.938373"><ele>1872</ele></trkpt>
    <trkpt lat="37.27654" lon="-109.938398"><ele>1870.75</ele></trkpt>
    <trkpt lat="37.276423" lon="-109.938396"><ele>1869.25</ele></trkpt>
    <trkpt lat="37.276268" lon="-109.938365"><ele>1866.25</ele></trkpt>
    <trkpt lat="37.275884" lon="-109.938228"><ele>1858.5</ele></trkpt>
    <trkpt lat="37.275176" lon="-109.937939"><ele>1854.25</ele></trkpt>
    <trkpt lat="37.27498" lon="-109.937836"><ele>1850.25</ele></trkpt>
    <trkpt lat="37.274532" lon="-109.937568"><ele>1826.25</ele></trkpt>
    <trkpt lat="37.274403" lon="-109.937483"><ele>1819.75</ele></trkpt>
    <trkpt lat="37.274256" lon="-109.937418"><ele>1813</ele></trkpt>
    <trkpt lat="37.274147" lon="-109.937393"><ele>1808.75</ele></trkpt>
    <trkpt lat="37.274048" lon="-109.937394"><ele>1805.25</ele></trkpt>
    <trkpt lat="37.273777" lon="-109.937487"><ele>1799.25</ele></trkpt>
    <trkpt lat="37.273634" lon="-109.937542"><ele>1797</ele></trkpt>
    <trkpt lat="37.273579" lon="-109.937589"><ele>1797.75</ele></trkpt>
    <trkpt lat="37.273512" lon="-109.937625"><ele>1797.75</ele></trkpt>
    <trkpt lat="37.273448" lon="-109.937624"><ele>1795.75</ele></trkpt>
    <trkpt lat="37.273381" lon="-109.93758"><ele>1791.25</ele></trkpt>
    <trkpt lat="37.27333" lon="-109.937529"><ele>1786.5</ele></trkpt>
    <trkpt lat="37.273272" lon="-109.937449"><ele>1781.25</ele></trkpt>
    <trkpt lat="37.273203" lon="-109.937368"><ele>1776.5</ele></trkpt>
    <trkpt lat="37.27311" lon="-109.93731"><ele>1771.5</ele></trkpt>
    <trkpt lat="37.273016" lon="-109.937277"><ele>1767.5</ele></trkpt>
    <trkpt lat="37.272932" lon="-109.937274"><ele>1764.5</ele></trkpt>
    <trkpt lat="37.272859" lon="-109.937291"><ele>1762.75</ele></trkpt>
    <trkpt lat="37.272775" lon="-109.937343"><ele>1761.5</ele></trkpt>
    <trkpt lat="37.272708" lon="-109.937404"><ele>1761</ele></trkpt>
    <trkpt lat="37.272656" lon="-109.937497"><ele>1762</ele></trkpt>
    <trkpt lat="37.272611" lon="-109.937634"><ele>1768.5</ele></trkpt>
    <trkpt lat="37.272581" lon="-109.937691"><ele>1770.75</ele></trkpt>
    <trkpt lat="37.272542" lon="-109.937729"><ele>1771.5</ele></trkpt>
    <trkpt lat="37.272505" lon="-109.937736"><ele>1770.75</ele></trkpt>
    <trkpt lat="37.272448" lon="-109.937727"><ele>1768.25</ele></trkpt>
    <trkpt lat="37.272406" lon="-109.937694"><ele>1765.5</ele></trkpt>
    <trkpt lat="37.272383" lon="-109.937646"><ele>1762.5</ele></trkpt>
    <trkpt lat="37.272371" lon="-109.937524"><ele>1756.75</ele></trkpt>
    <trkpt lat="37.272395" lon="-109.937462"><ele>1754.75</ele></trkpt>
    <trkpt lat="37.272449" lon="-109.937367"><ele>1752.75</ele></trkpt>
    <trkpt lat="37.272533" lon="-109.937283"><ele>1751.75</ele></trkpt>
    <trkpt lat="37.272713" lon="-109.937156"><ele>1754</ele></trkpt>
    <trkpt lat="37.272826" lon="-109.937107"><ele>1756.25</ele></trkpt>
    <trkpt lat="37.272924" lon="-109.937102"><ele>1759.25</ele></trkpt>
    <trkpt lat="37.273055" lon="-109.937117"><ele>1764</ele></trkpt>
    <trkpt lat="37.27317" lon="-109.937161"><ele>1769</ele></trkpt>
    <trkpt lat="37.273282" lon="-109.937246"><ele>1775.25</ele></trkpt>
    <trkpt lat="37.273445" lon="-109.937349"><ele>1783.75</ele></trkpt>
    <trkpt lat="37.273525" lon="-109.937374"><ele>1787.25</ele></trkpt>
    <trkpt lat="37.273591" lon="-109.937373"><ele>1789.5</ele></trkpt>
    <trkpt lat="37.273678" lon="-109.937349"><ele>1791.5</ele></trkpt>
    <trkpt lat="37.274001" lon="-109.937229"><ele>1798.25</ele></trkpt>
    <trkpt lat="37.274736" lon="-109.936936"><ele>1812.5</ele></trkpt>
    <trkpt lat="37.274879" lon="-109.936889"><ele>1815.75</ele></trkpt>
    <trkpt lat="37.274954" lon="-109.936882"><ele>1818</ele></trkpt>
    <trkpt lat="37.275028" lon="-109.936888"><ele>1820.5</ele></trkpt>
    <trkpt lat="37.275088" lon="-109.936883"><ele>1822</ele></trkpt>
    <trkpt lat="37.275142" lon="-109.93686"><ele>1823</ele></trkpt>
    <trkpt lat="37.275186" lon="-109.936804"><ele>1823</ele></trkpt>
    <trkpt lat="37.275206" lon="-109.936729"><ele>1821.75</ele></trkpt>
    <trkpt lat="37.275208" lon="-109.936664"><ele>1820.25</ele></trkpt>
    <trkpt lat="37.275188" lon="-109.936599"><ele>1817.5</ele></trkpt>
    <trkpt lat="37.275153" lon="-109.936566"><ele>1815.25</ele></trkpt>
    <trkpt lat="37.275097" lon="-109.93655"><ele>1812.75</ele></trkpt>
    <trkpt lat="37.275046" lon="-109.936561"><ele>1811.25</ele></trkpt>
    <trkpt lat="37.274987" lon="-109.936597"><ele>1810.25</ele></trkpt>
    <trkpt lat="37.274746" lon="-109.936718"><ele>1806</ele></trkpt>
    <trkpt lat="37.274589" lon="-109.936781"><ele>1802.75</ele></trkpt>
    <trkpt lat="37.274408" lon="-109.93681"><ele>1797.75</ele></trkpt>
    <trkpt lat="37.273838" lon="-109.936929"><ele>1783.25</ele></trkpt>
    <trkpt lat="37.273722" lon="-109.936946"><ele>1780</ele></trkpt>
    <trkpt lat="37.273606" lon="-109.936952"><ele>1776.5</ele></trkpt>
    <trkpt lat="37.273489" lon="-109.936943"><ele>1772.5</ele></trkpt>
    <trkpt lat="37.273391" lon="-109.936915"><ele>1768.5</ele></trkpt>
    <trkpt lat="37.273033" lon="-109.93675"><ele>1752</ele></trkpt>
    <trkpt lat="37.27282" lon="-109.936726"><ele>1744.75</ele></trkpt>
    <trkpt lat="37.272722" lon="-109.936743"><ele>1742</ele></trkpt>
    <trkpt lat="37.272643" lon="-109.936776"><ele>1740.5</ele></trkpt>
    <trkpt lat="37.272568" lon="-109.936834"><ele>1739.75</ele></trkpt>
    <trkpt lat="37.272426" lon="-109.936915"><ele>1740.25</ele></trkpt>
    <trkpt lat="37.272299" lon="-109.936967"><ele>1741.5</ele></trkpt>
    <trkpt lat="37.27223" lon="-109.936987"><ele>1742</ele></trkpt>
    <trkpt lat="37.272167" lon="-109.936984"><ele>1742</ele></trkpt>
    <trkpt lat="37.272069" lon="-109.936958"><ele>1741.5</ele></trkpt>
    <trkpt lat="37.271887" lon="-109.936893"><ele>1740.5</ele></trkpt>
    <trkpt lat="37.271704" lon="-109.936838"><ele>1740</ele></trkpt>
    <trkpt lat="37.271593" lon="-109.936826"><ele>1737.75</ele></trkpt>
    <trkpt lat="37.271529" lon="-109.936831"><ele>1736</ele></trkpt>
    <trkpt lat="37.27148" lon="-109.936859"><ele>1735</ele></trkpt>
    <trkpt lat="37.271434" lon="-109.936915"><ele>1734</ele></trkpt>
    <trkpt lat="37.271412" lon="-109.937014"><ele>1734.25</ele></trkpt>
    <trkpt lat="37.271429" lon="-109.937129"><ele>1735.5</ele></trkpt>
    <trkpt lat="37.271475" lon="-109.937296"><ele>1738.75</ele></trkpt>
    <trkpt lat="37.271556" lon="-109.937432"><ele>1743.25</ele></trkpt>
    <trkpt lat="37.271617" lon="-109.937568"><ele>1745.25</ele></trkpt>
    <trkpt lat="37.271722" lon="-109.937893"><ele>1743.5</ele></trkpt>
    <trkpt lat="37.271785" lon="-109.938016"><ele>1745.25</ele></trkpt>
    <trkpt lat="37.272028" lon="-109.938438"><ele>1759</ele></trkpt>
    <trkpt lat="37.272285" lon="-109.939023"><ele>1753.25</ele></trkpt>
    <trkpt lat="37.272449" lon="-109.939353"><ele>1750.25</ele></trkpt>
    <trkpt lat="37.272561" lon="-109.939651"><ele>1745</ele></trkpt>
    <trkpt lat="37.272915" lon="-109.940513"><ele>1738.25</ele></trkpt>
    <trkpt lat="37.273081" lon="-109.941079"><ele>1731.5</ele></trkpt>
    <trkpt lat="37.27312" lon="-109.941163"><ele>1731.25</ele></trkpt>
    <trkpt lat="37.273183" lon="-109.941274"><ele>1731</ele></trkpt>
    <trkpt lat="37.273316" lon="-109.941486"><ele>1730.75</ele></trkpt>
    <trkpt lat="37.273357" lon="-109.941647"><ele>1729.25</ele></trkpt>
    <trkpt lat="37.273381" lon="-109.941826"><ele>1728.25</ele></trkpt>
    <trkpt lat="37.273407" lon="-109.94235"><ele>1722.25</ele></trkpt>
    <trkpt lat="37.273408" lon="-109.942637"><ele>1729</ele></trkpt>
    <trkpt lat="37.273394" lon="-109.942952"><ele>1749</ele></trkpt>
    <trkpt lat="37.27337" lon="-109.943135"><ele>1759.5</ele></trkpt>
    <trkpt lat="37.273334" lon="-109.943322"><ele>1770</ele></trkpt>
    <trkpt lat="37.273287" lon="-109.943508"><ele>1770.5</ele></trkpt>
    <trkpt lat="37.273242" lon="-109.943613"><ele>1768.5</ele></trkpt>
    <trkpt lat="37.273181" lon="-109.943724"><ele>1765</ele></trkpt>
    <trkpt lat="37.273054" lon="-109.943874"><ele>1755.25</ele></trkpt>
    <trkpt lat="37.27263" lon="-109.944262"><ele>1720.25</ele></trkpt>
    <trkpt lat="37.272579" lon="-109.944287"><ele>1715.75</ele></trkpt>
    <trkpt lat="37.272532" lon="-109.944278"><ele>1710.25</ele></trkpt>
    <trkpt lat="37.272507" lon="-109.944243"><ele>1706.25</ele></trkpt>
    <trkpt lat="37.2725" lon="-109.944202"><ele>1704.25</ele></trkpt>
    <trkpt lat="37.272511" lon="-109.944148"><ele>1703.75</ele></trkpt>
    <trkpt lat="37.272563" lon="-109.944096"><ele>1708.25</ele></trkpt>
    <trkpt lat="37.272649" lon="-109.944027"><ele>1716</ele></trkpt>
    <trkpt lat="37.272853" lon="-109.943827"><ele>1733.5</ele></trkpt>
    <trkpt lat="37.272907" lon="-109.943748"><ele>1737.25</ele></trkpt>
    <trkpt lat="37.272997" lon="-109.943574"><ele>1742.75</ele></trkpt>
    <trkpt lat="37.273041" lon="-109.943451"><ele>1744.5</ele></trkpt>
    <trkpt lat="37.273099" lon="-109.943285"><ele>1745</ele></trkpt>
    <trkpt lat="37.273125" lon="-109.943134"><ele>1739.25</ele></trkpt>
    <trkpt lat="37.27312" lon="-109.943009"><ele>1732</ele></trkpt>
    <trkpt lat="37.273109" lon="-109.942917"><ele>1726.25</ele></trkpt>
    <trkpt lat="37.273013" lon="-109.942495"><ele>1702</ele></trkpt>
    <trkpt lat="37.273012" lon="-109.942495"><ele>1702</ele></trkpt>
    </trkseg>
    </trk>
    </gpx>
    --
    Some people are so helpful, good, so detailed, so technically competent,
    that almost everything they write, becomes a great reference for others.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech,alt.os.linux on Mon Nov 9 15:11:42 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    1. 'Better' tires (in terms of sidewall stiffness and tire wear ratings)
    2. 'Better' bushings (in terms of stiffness to geometric deflection)
    3. 'Better' rotation pattern (in terms of X-rotation & carcass flipping)
    4. 'Better' alignment (in terms of increased negative camber)
    5. 'Better' maintenance (in terms of stiffer tires due to adding pressure) >>
    Anything else?

    The higher your percentage of driving that is done in those mountains, the more sense it makes to move to negative camber. And the toe-on-turns measurements aren't always done in a normal alignment, or they are not paid attention to. There is no adjustment for that, but if it's off, it's a bad thing, and you just need to replace the bent parts. Always check that on your alignment printout, and if it's not there, tell the shop you need to know that.

    That's a good point, and I appreciate you brought up the bushing material.

    Since I've owned bimmers & beemers for decades, one thing I've learned is
    that never is the car aligned correctly at alignment shops simply because either techs don't know how, or more likely, don't care to do it right.

    Never in my life, have I watched an alignment done correctly, nor a tire mounting and balancing done by the book either, for that matter.

    In the case of bimmer alignment, there is a design position which is not as simple as simulating a drive since the weight is a specific amount to
    obtain a specific level BEFORE the car is touched for alignment purposes.

    Each model can be different, but you set the ride height first, with
    weights such as 68 kg (150 lbs) in each front seat, plus 68 kg (150 lbs) in
    the center of the rear seat, 21 kg (46 lbs) in the luggage trunk and a full fuel tank (or compensating with extra weight in the trunk).
    <https://www.e90post.com/forums/attachment.php?attachmentid=1584213&d=1488750075>

    I bring gas containers filled with water as my weight when I used to
    bring my bimmer for alignment. but most shops don't carry that weight.

    So all alignments are done wrong when they skip factory-mandated steps.

    HINT: We sparred because nospam always propagated the Apple lies.
    That doesn't happen on the adult operating system newsgroups simply
    because nobody is gonna defend Google, M$ or RedHat to the death.

    I like my macbook, but have no love for the company. And even if someone is getting paid to say things, i have no problem with that as long as the person believes what he is saying. I liked him on RPD because he helped with photgraphy issues. The tech stuff you are referring to is of no real interest to me, and over my head anyways. I had no way of knowing who was right.

    Assume I'm always right for a whole bunch of reasons, not the least of
    which is nobody on any newsgroup has ever found my facts to be wrong.

    Note that once in a while I make a thinko or typo, where the record shows
    I've apologized profusely and accepted the error whenever that happened.

    The other reason I'm "more likely" to be right, by the way, is I defend
    no mothership to the death, whereas on Apple groups, they're nutcases that think standing outside all night when you can't wait to ditch your old
    phone for a new phone, is "proof" that all facts about Apple are wrong.
    --
    HINT: I took marketing in the 1960s, and it has only gotten worse since.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Mon Nov 9 19:27:52 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> wrote:
    Chris wrote:
    This *is* the dataset, for example, for the Moki Dugway GPX file.
    <https://gpx.studio/app#14.41/37.27473/-109.93787>

    No it isn't. That's an app. Provide a file that can be used reproducible by >> anyone.

    OK. For the Angeles Crest Highway

    Is this a joke? Post a link.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to comp.lang.python,rec.autos.tech,alt.comp.os.windows-10,alt.satellite.gps on Mon Nov 9 12:30:42 2026
    From Newsgroup: comp.lang.python

    On 2026-11-04 07:07, Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads

    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads
    in your community, I will run a python script (I just wrote) on those roads to predict the abnormal wear the front outboard tire shoulders will incur.

    To limit the number of datapoints, since I'm running Python on an 2009 Windows 10 box, try to keep each road to less than about 10 miles long.

    I've already run a half-dozen tests on my own local roads, but I want to
    see how well the Linux/macOS/Win script works in roads elsewhere in the US.

    Oh, christ-on-a-crutch.

    You experienced abnormal wear on your own vehicle because (almost
    certainly) your vehicle's alignment was incorrect.

    Tires don't experience "abnormal wear", front OR rear, just because you
    drive on a windy mountain road.

    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater, but on
    the way up that road, those loads will be proportionately less.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to rec.autos.tech,alt.satellite.gps,alt.comp.os.windows-10,comp.lang.python on Mon Nov 9 12:37:11 2026
    From Newsgroup: comp.lang.python

    On 2026-11-04 15:03, Maria Sophia wrote:
    Your Name wrote:
    I've already run a half-dozen tests on my own local roads, but I want to >>>> see how well the Linux/macOS/Win script works in roads elsewhere in the US.
    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Many people don't live in the mountains, but *everyone* who does, knows
    there is abnormal tire wear on the front outboard outside tire shoulder.

    Complete bullshit.


    A vehicle, perfectly aligned to OEM specs, with even a bit extra negative camber, and maybe even a few psi extra sidewall stiffening, will *still* experience abnormal tire wear, as compared to those who live in flatland.

    No. Wear is caused by the loads on the tires...

    ...but if you drive down a road and experience (somewhat) higher loads,
    you'll experience lower loads when you drive up that same road.


    The mechanism is dynamic tire loading and suspension geometry under
    sustained cornering, particularly on steep mountain roads with tight, slow-speed switchbacks.

    Several things contribute.

    1. Lateral weight transfer: When negotiating a tight turn, vehicle weight transfers toward the outside wheels. The outside front tire carries a disproportionately large share of the cornering load.

    Which it does on EVERY turn; mountain road or dead flat.


    2. Body roll and camber change: As the suspension compresses on the
    outside, body roll and suspension geometry can cause the outside front
    wheel to lose negative camber or gain positive camber relative to the road. This concentrates loading on the outer shoulder.

    Which it does on EVERY turn; mountain road or dead flat.

    3. Steering angle and tire scrub: At very low speeds and high steering angles, the front tires experience considerable lateral deformation and scrub. This is especially pronounced in tight hairpins and full-lock turns.

    Which it does on EVERY turn; mountain road or dead flat.

    4. Combined braking and cornering forces: Descending steep grades while negotiating sharp turns adds longitudinal braking forces to the already substantial lateral forces. The front tires have to manage both simultaneously.

    It doesn't have to combine braking and turning, but if it does:


    It also does it on EVERY turn; mountain road or dead flat.


    5. Repeated exposure: Roads such as Moki Dugway, Shafer Canyon, Burr Trail, and Guardsman Pass can involve repeated tight turns, steep grades, changing road camber, and substantial steering inputs. Repetition makes the wear pattern more pronounced.

    People who commute in the mountains have already tested this for decades.

    And the ideal line through a corner for maximum speed is a catenary...

    ...at least if you're designing a simulation of a wooden ramp for racing
    one foot long wooden toy cars.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 12:38:20 2026
    From Newsgroup: comp.lang.python

    On 2026-11-04 17:18, Bob West wrote:
    On Nov 4, 2026 at 2:43:10rC>PM CST, "Your Name" <YourName@YourISP.com> wrote:

    On 2026-11-04 15:18:48 +0000, Blaine said:

    Maria Sophia wrote:
    Python analysis of abnormal front tire wear on windy US mountain roads >>>>
    I'd like to run a test of my Python code analyzing abnormal tire wear
    under the specific conditions of steep short windy curvy US mountain roads.

    If someone will choose about 3 steep windy curvy hairpin'ny mountain roads >>>> in your community, I will run a python script (I just wrote) on those roads
    to predict the abnormal wear the front outboard tire shoulders will incur. >>>>
    To limit the number of datapoints, since I'm running Python on an 2009 >>>> Windows 10 box, try to keep each road to less than about 10 miles long. >>>>
    I've already run a half-dozen tests on my own local roads, but I want to >>>> see how well the Linux/macOS/Win script works in roads elsewhere in the US.
    Moki Dugway
    Shafer Canyon
    Burr Trail
    Guardsman Pass

    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Yep. He is calling the expected *rapid* tire wear "abnormal". If you drive a car aound a race track at its limits, where there is little difference from those mountain twisties, that's going to cause rapid wear, but it's expected, therefore not abnormal. And he didn't include in his list the make and model of any specific vehicles, and they all have different suspension components, which includes all the rubber and plastic parts that are the bushings. The alignment specs are important, but not all that has to be considered. Cars with identical specs but different soft parts will have different tire wear. When he started on this 20 some years ago, i think he referred to some Chevy or GMC full size SUV. The GM engineers knew about the tire wear thing, and did
    not consider it abnormal, and the bushings had something to do with it on that
    heavy vehicle. There are tradeoffs in design. Arlen can't live with that.

    And what he fails to acknowledge is that the same things that increase
    tire loads going down a mountain road, decrease those loads when you
    travel up it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 12:42:22 2026
    From Newsgroup: comp.lang.python

    On 2026-11-04 18:44, Maria Sophia wrote:
    Bob West wrote:
    Simply driving on a road doesn't create "abnormal wear". Abnormal wear
    on a tyre is due to incorrect air pressure in the tire, misaligned
    wheels, unbalanced wheels, and/or bad driving (including doing wheel
    spins, donuts, etc.).

    Yep. He is calling the expected *rapid* tire wear "abnormal". If you drive a
    car aound a race track at its limits, where there is little difference from >> those mountain twisties, that's going to cause rapid wear, but it's expected,
    therefore not abnormal. And he didn't include in his list the make and model >> of any specific vehicles, and they all have different suspension components, >> which includes all the rubber and plastic parts that are the bushings. The >> alignment specs are important, but not all that has to be considered. Cars >> with identical specs but different soft parts will have different tire wear. >> When he started on this 20 some years ago, i think he referred to some Chevy >> or GMC full size SUV. The GM engineers knew about the tire wear thing, and did
    not consider it abnormal, and the bushings had something to do with it on that
    heavy vehicle. There are tradeoffs in design. Arlen can't live with that.

    I'm going to make a very strong point, so that people can LEARN from this.

    Nope. You're going to keep repeating the same bullshit over and over.


    1. Run the python script on your daily commute
    2. If you're not SHOCKED (you'll have a heart attack!), I'll be surprised
    3. Your commute, most likely, is child's play compared to mountain roads
    The strongly held point I'm going to make anyone who claims to disagree
    with what happens with mountain driving, needs to run the python code.

    Have you never heard of "GIGO"?


    Just running it once, on their commute, will turn them into a knowledgeable person from a novice, since the road inherence is TREMENDOUSLY different.

    For example, people who know nothing about the problem always bring up the drive train, but the drive train essentially has no meaning at all.

    People "think" it does.
    Because they don't understand the problem set.

    People who have never studied the problem set, think the drive train would matter, and yet, the fact is, it doesn't. Not in the downhill direction.

    I don't know why people don't understand, but I think they are thinking everything is flat, and when things are flat, drivetrain differences can
    have a greater effect on tire wear than when we're talking DOWNHILL runs.

    But for every DOWNHILL run, there's also an UPHILL run, right?

    I mean, if this is a commute...

    ...right?


    Most people have never driven on mountain roads day in and day out, so they have no idea that the similarities to flatland wear and tear don't exist.

    In the argument above, Bob conflates conflating general tire maintenance
    and suspension compliance with high-geometric-load cornering.

    I realize I didn't emphasize this enough initially, but we are looking specifically at downhill driving on tight mountain roads.

    When you're going downhill:

    The drivetrain is almost irrelevant: The engine isn't putting power down to accelerate through the turns. Gravity and braking forces dominate. Whether it's FWD, RWD, or AWD, the front tires are handling the steering lock and braking loads entirely on the overrun.

    Camber scrub overrides bushings: While soft rubber bushings, vehicle
    weight, and alignment specs change the rate of wear or how a specific suspension loads up, they don't cause the primary phenomenon. When a 4.8-meter hairpin forces near-maximum steering lock, the contact patch undergoes severe lateral scrubbing. The tire is literally being dragged sideways across the asphalt under a forward weight transfer.

    Semantics on "Abnormal": You call it "expected rapid wear" like a track
    day, which is fair that if you drive a road with 600 hairpins, rapid wear
    is the expected physical result. But for the average driver who just
    visited Costco for the first scheduled rotation, seeing an outer tire shoulder chewed down to the cords while the rest of the tread has 60% life left looks and acts like an anomaly compared to normal commuting wear.

    Improper alignment, underinflated tires, worn suspension joings.


    The road geometry itself is what dictates the high-slip-angle scrub.

    ANY tight turn does the same.


    The make, model, and drivetrain are just secondary variables turning the volume up or down, but EVERY passenger car in the mountains wears tires the same way.

    That's why the Python script concentrates on inherent road metrics.
    What did you get when you ran the script on your daily commute?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech,alt.os.linux on Mon Nov 9 12:56:50 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 12:11, Maria Sophia wrote:
    Bob West wrote:
    1. 'Better' tires (in terms of sidewall stiffness and tire wear ratings) >>> 2. 'Better' bushings (in terms of stiffness to geometric deflection)
    3. 'Better' rotation pattern (in terms of X-rotation & carcass flipping) >>> 4. 'Better' alignment (in terms of increased negative camber)
    5. 'Better' maintenance (in terms of stiffer tires due to adding pressure) >>>
    Anything else?

    The higher your percentage of driving that is done in those mountains, the >> more sense it makes to move to negative camber. And the toe-on-turns
    measurements aren't always done in a normal alignment, or they are not paid >> attention to. There is no adjustment for that, but if it's off, it's a bad >> thing, and you just need to replace the bent parts. Always check that on your
    alignment printout, and if it's not there, tell the shop you need to know
    that.

    That's a good point, and I appreciate you brought up the bushing material.

    Since I've owned bimmers & beemers for decades, one thing I've learned is that never is the car aligned correctly at alignment shops simply because either techs don't know how, or more likely, don't care to do it right.

    Never in my life, have I watched an alignment done correctly, nor a tire mounting and balancing done by the book either, for that matter.

    In the case of bimmer alignment, there is a design position which is not as simple as simulating a drive since the weight is a specific amount to
    obtain a specific level BEFORE the car is touched for alignment purposes.

    Each model can be different, but you set the ride height first, with
    weights such as 68 kg (150 lbs) in each front seat, plus 68 kg (150 lbs) in the center of the rear seat, 21 kg (46 lbs) in the luggage trunk and a full fuel tank (or compensating with extra weight in the trunk).
    <https://www.e90post.com/forums/attachment.php?attachmentid=1584213&d=1488750075>

    I bring gas containers filled with water as my weight when I used to
    bring my bimmer for alignment. but most shops don't carry that weight.

    So all alignments are done wrong when they skip factory-mandated steps.

    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    HINT: We sparred because nospam always propagated the Apple lies.
    That doesn't happen on the adult operating system newsgroups simply
    because nobody is gonna defend Google, M$ or RedHat to the death.

    I like my macbook, but have no love for the company. And even if someone is >> getting paid to say things, i have no problem with that as long as the person
    believes what he is saying. I liked him on RPD because he helped with
    photgraphy issues. The tech stuff you are referring to is of no real interest
    to me, and over my head anyways. I had no way of knowing who was right.

    Assume I'm always right for a whole bunch of reasons, not the least of
    which is nobody on any newsgroup has ever found my facts to be wrong.

    Well that is simply a lie.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:25:18 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 1:56:50rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 12:11, Maria Sophia wrote:
    Each model can be different, but you set the ride height first, with
    weights such as 68 kg (150 lbs) in each front seat, plus 68 kg (150 lbs) in >> the center of the rear seat, 21 kg (46 lbs) in the luggage trunk and a full >> fuel tank (or compensating with extra weight in the trunk).

    <https://www.e90post.com/forums/attachment.php?attachmentid=1584213&d=1488750075>

    I bring gas containers filled with water as my weight when I used to
    bring my bimmer for alignment. but most shops don't carry that weight.

    So all alignments are done wrong when they skip factory-mandated steps.

    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    I can 50% agree with that, but there are two problems: First - and least important, if you call yourself the Ultimate Driving Machine, you have to act like it, which would include giving the owners necessary info to spend the
    time and money to make the car exactly that - useful for the track or very "spirited" driving. The other more important one is that with the driver
    assist tech in cars today, you need to get everything exactly right to
    minimize those pesky stability warning lights. If they come on, the dealer can play gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:36:10 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 1:11:42rC>PM CST, "Maria Sophia" <mariasophia@comprehension.com> wrote:



    Since I've owned bimmers & beemers for decades, one thing I've learned is that never is the car aligned correctly at alignment shops simply because either techs don't know how, or more likely, don't care to do it right.

    Never in my life, have I watched an alignment done correctly, nor a tire mounting and balancing done by the book either, for that matter.

    Techs tend to be paid by the specific job, not hourly. So they get 1.5 hours
    of pay for an alignment whether it takes them 3 hours, or 15 minutes. So what you're saying is the predictable result.


    The other reason I'm "more likely" to be right, by the way, is I defend
    no mothership to the death, whereas on Apple groups, they're nutcases that think standing outside all night when you can't wait to ditch your old
    phone for a new phone, is "proof" that all facts about Apple are wrong.

    Yeah, those iphone lines were the reason they couldn't be ridiculed enough. I bought a shockingly inexpensive used iphone because there were a couple of ios only soft-synths I wanted for my music gear. I just don't get the worship for those things. It's usable, but whatever... Android is the phone I use for everything but those apps.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 14:39:58 2026
    From Newsgroup: comp.lang.python

    Alan <nuh-uh@nope.com> writes:
    [...]
    And what he fails to acknowledge is that the same things that increase
    tire loads going down a mountain road, decrease those loads when you
    travel up it.

    Disclaimer: I know next to nothing about tire wear. My comments are
    based entirely on what's been posted here and a bit of common sense.

    Assuming your statement is correct, how sure are you that it
    invalidates the claims? Suppose, hypothetically, that driving
    down increases tire wear (relative to driving on a straight flat
    road) by a factor of 5, and driving up decreases it by a factor
    of 2. Then surely the result would be substantially increased
    wear, by a factor of about 4.5.

    I made up those numbers. Do you have better ones? Are you an
    expert on the subject?

    Are you asserting that driving on winding mountain roads *doesn't* substantially increase tire wear? "Maria Sophia" has described
    drivers experiencing increased ("abnormal") tire wear on mountain
    roads; are they making it all up?
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:44:34 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".


    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, especially if you are taking into account all 4 tires.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 21:07:11 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    I can 50% agree with that, but there are two problems: First - and least important, if you call yourself the Ultimate Driving Machine, you have to act like it, which would include giving the owners necessary info to spend the time and money to make the car exactly that - useful for the track or very "spirited" driving. The other more important one is that with the driver assist tech in cars today, you need to get everything exactly right to minimize those pesky stability warning lights. If they come on, the dealer can
    play gotcha and say the alignment was not properly done. Then you pay. And it's a lot.

    Oh no, the Apple trolls (Alan Baker) have begun to infest this thread.

    There's somethings strangely and rather oddly *different* about a person
    who thinks that waiting in line outside a store all night because you can't wait until morning to ditch your existing iPhone in a trade-in for the next model is proof positive (to the Apple trolls) that everything Apple
    marketing says is correct.

    These Apple religious zealots have no idea how propaganda influences them.

    I think it's because they lack any vestige of formal education, where none
    of them has so much as a single college course under their belt, which is
    easy to tell because they don't know the simplest of the most basic things.

    The particular troll above insisted for *weeks* that it's impossible to
    change the newsreader line in the header (of all things to insist upon).

    He also claimed to be an expert BMW owner & a racer and yet, he had no clue what BMW racing "vehicles" are called by *everyone* in racing circuits.

    Worse, he has no STEM training so he didn't even know what a catenary was,
    and, in fact, he couldn't mentally tilt it 90 degrees from vertical to horizontal to see how it applies to curves, which, interestingly enough,
    has some (passing) relevance to this particular thread on downhill curves.

    As for my observation that I've never seen any alignment done correctly,
    nor any tire mounting and balancing, I'm on record for saying that for
    years where I also mention that cars aren't falling over cliffs as a
    result.

    For example, when balancing on those fancy Hunter road-force machines, they don't bother to check the red/blue/white/yellow/etc (mine are usually red
    and yellow) alignment marks or match-mounting marks on the wheels.

    Why does that matter?
    Well, do we think the OEMs put those marks there just for amusement?

    As for tire mounting, the bimmer has a BBS wheel which has a plastic hubcap which twists off using a stop-light-shaped tool, where the mechanics can't spend the two minutes to use it and just pry them off with a screwdriver.

    Likewise, it would be too time consuming for mechanics to look up the
    torque for the lug bolts (yes, bolts) so they torque all nuts/bolts the
    same on all cars, as it's too much trouble to change the torque wrench
    settings per vehicle. Likewise, with the air pressure, where my bimmer specified different PSI for front/rear and yet the mechanics are too lazy
    to look inside the front driver side door frame to adjust accordingly.

    I've seen them plug a tire from outside (which, to be fair, I've done
    myself a million times, but patch plugs are the "right" way to do it).

    My main point is not that tires are falling off vehicles, but that I've
    never watched a mounting, balancing or alignment that was ever done by the book.

    Which... by the way... is why I do it all myself, in my pajamas, at home.
    All you need are:

    a. Harbor Freight tire mounting jig (handles up to about 17 inch diameter)
    b. Harbor Freight bead breaker (the one with the mounting tool sucks)
    c. Harbor Freight static balancer (the dynamic balance check is free)
    d. Camber gauge, alignment bars & turn plates with matching tape rules

    Has anyone else here done proper mounting & balancing at home like I have?
    It's easy most of the time. And you can do it right, at home, in pajamas.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 21:26:14 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    Never in my life, have I watched an alignment done correctly, nor a tire
    mounting and balancing done by the book either, for that matter.

    Techs tend to be paid by the specific job, not hourly. So they get 1.5 hours of pay for an alignment whether it takes them 3 hours, or 15 minutes. So what you're saying is the predictable result.

    Hi Bob West,

    That's EXACTLY my point. So thank you for understanding, as part of our communication is to TEACH others what they might not yet know about it.

    The techs *know* how to do it right.
    They just don't bother.

    And to the troll who claimed that it's meaningless, you have to ask that
    troll why BMW makes it obvious that it is the *correct* way to load the
    vehicle prior to touching it for alignment purposes.

    Does he think that BMW prints those specific steps for their amusement?

    Or, more likely, does that Apple troll (i.e., Alan Baker) feel that he
    knows more than BMW does about alignment?

    Notice, very clearly, when discussing anyone who claims that Apple products must be the best simply because of Apple's profits (notwithstanding the
    facts that Apple's marketing propaganda is one of the best in the
    world),.this particular Apple religious zealot feels he knows more than BMW engineers do for how to properly do an alignment.

    Note, I had a typo in my prior post above "driver" (the "r" dropped off).
    Most people "think" a proper load is to simulate a driver.

    Not a proper load that BMW documents it isn't.

    Each bimmer can be different, but you set the ride height first, with
    weights such as 68 kg (150 lbs) in each front seat, plus 68 kg (150 lbs) in
    the center of the rear seat, 21 kg (46 lbs) in the luggage trunk and a full fuel tank (or compensating with extra weight in the trunk).
    <https://www.e90post.com/forums/attachment.php?attachmentid=1584213&d=1488750075>

    The revelation I had, when my bimmer was new, was that I asked the
    technician to properly weight it, and all he did was stick some 'sandbags'
    in the driver seat. I looked at him. I looked hard. I almost laughed.

    Never in my life have I ever seen an alignment, mounting or balancing done right (i.e., by the wheel/tire/car manufacturers' OEM specifications).

    The other reason I'm "more likely" to be right, by the way, is I defend
    no mothership to the death, whereas on Apple groups, they're nutcases that >> think standing outside all night when you can't wait to ditch your old
    phone for a new phone, is "proof" that all facts about Apple are wrong.

    Yeah, those iphone lines were the reason they couldn't be ridiculed enough. I bought a shockingly inexpensive used iphone because there were a couple of ios
    only soft-synths I wanted for my music gear. I just don't get the worship for those things. It's usable, but whatever... Android is the phone I use for everything but those apps.

    I own plenty of iPhones, iPads and Android tablets and Android phones.

    I've been posting to the Android c.m.a and iOS m.p.m.i newsgroups for, oh,
    I don't know, for fifteen years or so, when I bought my daughter (at the
    time she was in high school) the iPhone4, which wouldn't work on T-Mobile.

    So I jailbroke it and added Cydia, and changed her ringtone to "I'm a
    Barbie Girl" from Limewire (which is from where we populated our iPods in
    those days), and that literally was my first experience with Apple's mobile devices (although all of us used mac's in the early corporate days before Windows and then much later RedHat became the engineer's PC of choice).

    Having started with computers in the 60's, I was used to IBM JCL (punched cards, as I just missed the paper tape era as they were still in the air-conditioned "computer room" but I never used the punched tape machine.

    I knew assembly language by rote, such that I'd literally code in hex when programming the Motorola 68701 whose motherboard I wire wrapped myself.

    Peter Norton was my hero in those days, and I always wanted to write
    tutorials like he did (and I wrote, oh, I don't know, I never counted them, many thousands over the decades, many well before Usenet was even a thing).

    I loved the SAM's guides and the Forrest Mims grid-=paper circuit diagrams, where I soldered a Germanium transistor amplifier when I was just a kid.

    When I took marketing in college, I realized that their job is to find
    people dumb enough to believe their propaganda, and while Apple wasn't
    around at that time, big tobacco was, which is where I learned marketing.

    Apple finds people who are especially susceptible to the propaganda, which
    we have to admit is a brilliant tactic given their products are no safer,
    no more functional (in fact, highly less functional) and no more reliable
    than any other devices, and yet, people like nospam insisted they were.

    You have to give credit where credit is due that Apple marketing is
    brilliant. I am in awe of how well Apple marketing promotes propaganda.

    I simply can't understand the kind of person who believes it though.

    I've been working on that specific problem, for decades, and the most I can figure out is that they, like Alan Baker, think they're more competent than they really are when it comes to assessing that is actual engineering fact.

    Witness the DK lemon-juice bank robber.
    That's Alan Baker in a nutshell.




























    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 21:41:27 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".


    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, especially if you are taking into account all 4 tires.

    Hi Bob West,

    First off, Alan Baker is an uneducated Apple religious zealot troll who
    happens to have recently infested this thread, but notice that it doesn't matter, mathematically, that you drive DOWN in the morning, and then UP in
    the evening.

    Think about it.
    Think...
    Think...
    Think....

    Do you realize yet why almost all the wear is on the way down or not?

    You could drive five miles down and ten thousand miles up, and it wouldn't change the wear pattern.

    So the fact you agreed with Alan Baker on the directional math is scary.

    Put it this way:
    a. You spend 1 hour in the 28-degree water from the Titanic sinking
    b. And then someone pulls you out and gives you 98.6 degrees for hours.

    Using the calculation you and Alan Baker came up with, that should be
    "pretty much the same thing if you take into account all 4 appendages".

    The fact you agreed with Alan Baker, who, clearly, is far to the left of
    the first Dunning-Kruger quartile marker (and yes, I read the papers), is a problem.

    Let me ask you, if you are an adult, if you might mind correcting what you
    said in terms of the fact that almost all the damage is done going
    downhill.

    How exactly does going back uphill "reverse" the damage (or even it out)?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Hank Rogers@Hank@nospam.invalid to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 20:26:30 2026
    From Newsgroup: comp.lang.python

    Maria Sophia wrote on 11/9/2026 7:07 PM:
    Bob West wrote:
    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    I can 50% agree with that, but there are two problems: First - and least
    important, if you call yourself the Ultimate Driving Machine, you have to act
    like it, which would include giving the owners necessary info to spend the >> time and money to make the car exactly that - useful for the track or very >> "spirited" driving. The other more important one is that with the driver
    assist tech in cars today, you need to get everything exactly right to
    minimize those pesky stability warning lights. If they come on, the dealer can
    play gotcha and say the alignment was not properly done. Then you pay. And >> it's a lot.

    Oh no, the Apple trolls (Alan Baker) have begun to infest this thread.

    There's somethings strangely and rather oddly *different* about a person
    who thinks that waiting in line outside a store all night because you can't wait until morning to ditch your existing iPhone in a trade-in for the next model is proof positive (to the Apple trolls) that everything Apple
    marketing says is correct.

    These Apple religious zealots have no idea how propaganda influences them.

    I think it's because they lack any vestige of formal education, where none
    of them has so much as a single college course under their belt, which is easy to tell because they don't know the simplest of the most basic things.

    The particular troll above insisted for *weeks* that it's impossible to change the newsreader line in the header (of all things to insist upon).

    He also claimed to be an expert BMW owner & a racer and yet, he had no clue what BMW racing "vehicles" are called by *everyone* in racing circuits.

    Worse, he has no STEM training so he didn't even know what a catenary was, and, in fact, he couldn't mentally tilt it 90 degrees from vertical to horizontal to see how it applies to curves, which, interestingly enough,
    has some (passing) relevance to this particular thread on downhill curves.

    As for my observation that I've never seen any alignment done correctly,
    nor any tire mounting and balancing, I'm on record for saying that for
    years where I also mention that cars aren't falling over cliffs as a
    result.

    For example, when balancing on those fancy Hunter road-force machines, they don't bother to check the red/blue/white/yellow/etc (mine are usually red
    and yellow) alignment marks or match-mounting marks on the wheels.

    Why does that matter?
    Well, do we think the OEMs put those marks there just for amusement?

    As for tire mounting, the bimmer has a BBS wheel which has a plastic hubcap which twists off using a stop-light-shaped tool, where the mechanics can't spend the two minutes to use it and just pry them off with a screwdriver.

    Likewise, it would be too time consuming for mechanics to look up the
    torque for the lug bolts (yes, bolts) so they torque all nuts/bolts the
    same on all cars, as it's too much trouble to change the torque wrench settings per vehicle. Likewise, with the air pressure, where my bimmer specified different PSI for front/rear and yet the mechanics are too lazy
    to look inside the front driver side door frame to adjust accordingly.

    I've seen them plug a tire from outside (which, to be fair, I've done
    myself a million times, but patch plugs are the "right" way to do it).

    My main point is not that tires are falling off vehicles, but that I've
    never watched a mounting, balancing or alignment that was ever done by the book.

    Which... by the way... is why I do it all myself, in my pajamas, at home.
    All you need are:

    a. Harbor Freight tire mounting jig (handles up to about 17 inch diameter)
    b. Harbor Freight bead breaker (the one with the mounting tool sucks)
    c. Harbor Freight static balancer (the dynamic balance check is free)
    d. Camber gauge, alignment bars & turn plates with matching tape rules

    Has anyone else here done proper mounting & balancing at home like I have? It's easy most of the time. And you can do it right, at home, in pajamas.


    But could you do wearing only your drawers, Arlen?


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 19:40:03 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 15:44, Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".

    Ummmmm...no.

    That would depend entirely on HOW you drive down those roads.



    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, especially if you are taking into account all 4 tires.

    Nope.

    If one argues that the downward grade increases loads, then how can the
    upward grade of the other half of the "commute" not result in
    proportional decreases in the load on the tires?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 19:46:55 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 15:25, Bob West wrote:
    On Nov 9, 2026 at 1:56:50rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 12:11, Maria Sophia wrote:
    Each model can be different, but you set the ride height first, with
    weights such as 68 kg (150 lbs) in each front seat, plus 68 kg (150 lbs) in >>> the center of the rear seat, 21 kg (46 lbs) in the luggage trunk and a full >>> fuel tank (or compensating with extra weight in the trunk).

    <https://www.e90post.com/forums/attachment.php?attachmentid=1584213&d=1488750075>

    I bring gas containers filled with water as my weight when I used to
    bring my bimmer for alignment. but most shops don't carry that weight.

    So all alignments are done wrong when they skip factory-mandated steps.

    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    I can 50% agree with that, but there are two problems: First - and least important, if you call yourself the Ultimate Driving Machine, you have to act like it, which would include giving the owners necessary info to spend the time and money to make the car exactly that - useful for the track or very "spirited" driving. The other more important one is that with the driver assist tech in cars today, you need to get everything exactly right to minimize those pesky stability warning lights. If they come on, the dealer can
    play gotcha and say the alignment was not properly done. Then you pay. And it's a lot.

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 19:52:59 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 18:07, Maria Sophia wrote:
    Bob West wrote:
    A simply ridiculous refinement that will make ZERO difference in normal
    road driving.

    I can 50% agree with that, but there are two problems: First - and least
    important, if you call yourself the Ultimate Driving Machine, you have to act
    like it, which would include giving the owners necessary info to spend the >> time and money to make the car exactly that - useful for the track or very >> "spirited" driving. The other more important one is that with the driver
    assist tech in cars today, you need to get everything exactly right to
    minimize those pesky stability warning lights. If they come on, the dealer can
    play gotcha and say the alignment was not properly done. Then you pay. And >> it's a lot.

    Oh no, the Apple trolls (Alan Baker) have begun to infest this thread.

    He also claimed to be an expert BMW owner & a racer and yet, he had no clue what BMW racing "vehicles" are called by *everyone* in racing circuits.

    For clarity, I never claimed to be an "expert BMW owner", but I am most certainly a racer--having raced a couple of different Formula F cars
    since 2013, and since 2017, a road racing instructor.


    Worse, he has no STEM training so he didn't even know what a catenary was,

    I knew exactly what a catenary was.

    and, in fact, he couldn't mentally tilt it 90 degrees from vertical to horizontal to see how it applies to curves, which, interestingly enough,
    has some (passing) relevance to this particular thread on downhill curves.

    None at all actually.

    The only reference to a "catenary" curve that Arlen was ever able to
    dredge up was a programmer who CHOSE to use a catenary to transition a
    wooden ramp from the angled section to the horizontal section...

    ...in a simulation...

    ...of the track used by wooden toy gravity racing cars.


    As for my observation that I've never seen any alignment done correctly,
    nor any tire mounting and balancing, I'm on record for saying that for
    years where I also mention that cars aren't falling over cliffs as a
    result.

    For example, when balancing on those fancy Hunter road-force machines, they don't bother to check the red/blue/white/yellow/etc (mine are usually red
    and yellow) alignment marks or match-mounting marks on the wheels.

    Those marks aren't "alignment marks".


    Why does that matter?
    Well, do we think the OEMs put those marks there just for amusement?

    As for tire mounting, the bimmer has a BBS wheel which has a plastic hubcap which twists off using a stop-light-shaped tool, where the mechanics can't spend the two minutes to use it and just pry them off with a screwdriver.

    SOME BMWs have BBS wheels.


    Likewise, it would be too time consuming for mechanics to look up the
    torque for the lug bolts (yes, bolts) so they torque all nuts/bolts the
    same on all cars, as it's too much trouble to change the torque wrench settings per vehicle. Likewise, with the air pressure, where my bimmer specified different PSI for front/rear and yet the mechanics are too lazy
    to look inside the front driver side door frame to adjust accordingly.

    You should pick a better shop.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 19:55:19 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 15:39, Keith Thompson wrote:
    Alan <nuh-uh@nope.com> writes:
    [...]
    And what he fails to acknowledge is that the same things that increase
    tire loads going down a mountain road, decrease those loads when you
    travel up it.

    Disclaimer: I know next to nothing about tire wear. My comments are
    based entirely on what's been posted here and a bit of common sense.

    Assuming your statement is correct, how sure are you that it
    invalidates the claims? Suppose, hypothetically, that driving
    down increases tire wear (relative to driving on a straight flat
    road) by a factor of 5, and driving up decreases it by a factor
    of 2. Then surely the result would be substantially increased
    wear, by a factor of about 4.5.
    I made up those numbers. Do you have better ones? Are you an
    expert on the subject?

    Are you asserting that driving on winding mountain roads *doesn't* substantially increase tire wear? "Maria Sophia" has described
    drivers experiencing increased ("abnormal") tire wear on mountain
    roads; are they making it all up?
    Believing that anything that "Maria Sophia" states as "fact" is in any
    way related to reality is your first mistake.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 20:23:06 2026
    From Newsgroup: comp.lang.python

    Alan <nuh-uh@nope.com> writes:
    On 2026-11-09 15:39, Keith Thompson wrote:
    Alan <nuh-uh@nope.com> writes:
    [...]
    And what he fails to acknowledge is that the same things that increase
    tire loads going down a mountain road, decrease those loads when you
    travel up it.

    Disclaimer: I know next to nothing about tire wear. My comments are
    based entirely on what's been posted here and a bit of common sense.

    Assuming your statement is correct, how sure are you that it
    invalidates the claims? Suppose, hypothetically, that driving
    down increases tire wear (relative to driving on a straight flat
    road) by a factor of 5, and driving up decreases it by a factor
    of 2. Then surely the result would be substantially increased
    wear, by a factor of about 4.5.

    I made up those numbers. Do you have better ones? Are you an
    expert on the subject?

    Are you asserting that driving on winding mountain roads *doesn't*
    substantially increase tire wear? "Maria Sophia" has described
    drivers experiencing increased ("abnormal") tire wear on mountain
    roads; are they making it all up?

    Believing that anything that "Maria Sophia" states as "fact" is in any
    way related to reality is your first mistake.

    I know nothing about either of you. It seems there's a lot of
    history. I'm delighted to be ignorant about it. I have no basis
    for judging "Maria Sophia"'s statements -- or yours -- other than
    what I've read in this thread.

    I read comp.lang.python fairly regularly. When this thread showed
    up, I found some aspects of it mildly interesting.

    I've asked you a few technical questions about what you've written
    here, and you've answered none of them. Even if your opinions
    about "Maria Sophia" are accurate, I would think you could address
    my questions.

    As an outsider to this topic, I merely observe that even if tire
    loads are increased when going downhill and decreased when going
    uphill (and I have no basis for judging the accuracy of that claim),
    that doesn't imply that the effects neatly cancel out, nor, as far as
    I can tell, does it refute anything "Maria Sophia" has posted here.
    Do you have any comment on that?
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 21:42:17 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 21:23, Keith Thompson wrote:
    Alan <nuh-uh@nope.com> writes:
    On 2026-11-09 15:39, Keith Thompson wrote:
    Alan <nuh-uh@nope.com> writes:
    [...]
    And what he fails to acknowledge is that the same things that increase >>>> tire loads going down a mountain road, decrease those loads when you
    travel up it.

    Disclaimer: I know next to nothing about tire wear. My comments are
    based entirely on what's been posted here and a bit of common sense.

    Assuming your statement is correct, how sure are you that it
    invalidates the claims? Suppose, hypothetically, that driving
    down increases tire wear (relative to driving on a straight flat
    road) by a factor of 5, and driving up decreases it by a factor
    of 2. Then surely the result would be substantially increased
    wear, by a factor of about 4.5.

    I made up those numbers. Do you have better ones? Are you an
    expert on the subject?

    Are you asserting that driving on winding mountain roads *doesn't*
    substantially increase tire wear? "Maria Sophia" has described
    drivers experiencing increased ("abnormal") tire wear on mountain
    roads; are they making it all up?

    Believing that anything that "Maria Sophia" states as "fact" is in any
    way related to reality is your first mistake.

    I know nothing about either of you. It seems there's a lot of
    history. I'm delighted to be ignorant about it. I have no basis
    for judging "Maria Sophia"'s statements -- or yours -- other than
    what I've read in this thread.

    I read comp.lang.python fairly regularly. When this thread showed
    up, I found some aspects of it mildly interesting.

    I've asked you a few technical questions about what you've written
    here, and you've answered none of them. Even if your opinions
    about "Maria Sophia" are accurate, I would think you could address
    my questions.

    As an outsider to this topic, I merely observe that even if tire
    loads are increased when going downhill and decreased when going
    uphill (and I have no basis for judging the accuracy of that claim),
    that doesn't imply that the effects neatly cancel out, nor, as far as
    I can tell, does it refute anything "Maria Sophia" has posted here.
    Do you have any comment on that?


    And what details has "Maria Sophia" offered. What has he really "posted
    here" beyond his own (anecdotal) claims that he has experienced
    additional tire wear?

    It seems pretty obvious to me that if going downhill adds load to
    corners (and it needn't--just brake sufficiently in a straight line
    before you GET to the corner), then going uphill on the same road is
    going to remove load to precisely the same proportion.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 04:50:04 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term for driver assist systems - lane keep, emergency braking, self driving, and more that I can't think of right now. Those systems can have issues if the alignment is not done properly. Those weight procedures might make very little difference, but it might be enough to push it past the tipping point for error codes, like when the alignment is in spec, but at the edge of the specs.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 04:55:00 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 7:41:27rC>PM CST, "Maria Sophia" <mariasophia@comprehension.com> wrote:

    Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".


    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, >> especially if you are taking into account all 4 tires.

    Hi Bob West,

    First off, Alan Baker is an uneducated Apple religious zealot troll who happens to have recently infested this thread, but notice that it doesn't matter, mathematically, that you drive DOWN in the morning, and then UP in the evening.

    Think about it.
    Think...
    Think...
    Think....

    Do you realize yet why almost all the wear is on the way down or not?

    You could drive five miles down and ten thousand miles up, and it wouldn't change the wear pattern.

    So the fact you agreed with Alan Baker on the directional math is scary.

    I didn't. You misread what I said, and I replied in another post. But do you see above where I said that the wear would be about the same up and down? That is the opposite of agreeing with him, but there is more detail in my other reply.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 21:56:03 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term for driver assist systems - lane keep, emergency braking, self driving, and more that I can't think of right now. Those systems can have issues if the alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 05:00:59 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 8:40:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 15:44, Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".

    Ummmmm...no.

    That would depend entirely on HOW you drive down those roads.



    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, >> especially if you are taking into account all 4 tires.

    Nope.

    If one argues that the downward grade increases loads, then how can the upward grade of the other half of the "commute" not result in
    proportional decreases in the load on the tires?

    Because you are fighting inertia in either direction. A flat, straight road will have the least wear, and any uphill or downhill twisty road will have
    more wear. And please don't bring up straight downhill roads. They are irrelevant for our purposes.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:03:48 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 22:00, Bob West wrote:
    On Nov 9, 2026 at 8:40:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 15:44, Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".

    Ummmmm...no.

    That would depend entirely on HOW you drive down those roads.



    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same, >>> especially if you are taking into account all 4 tires.

    Nope.

    If one argues that the downward grade increases loads, then how can the
    upward grade of the other half of the "commute" not result in
    proportional decreases in the load on the tires?

    Because you are fighting inertia in either direction. A flat, straight road will have the least wear, and any uphill or downhill twisty road will have more wear. And please don't bring up straight downhill roads. They are irrelevant for our purposes.
    Except for the fact that this is about TIRE wear.

    And if you "fight inertia" by braking in a straight line, you only wear
    your brake pads; well, you certainly don't cause asymmetric wear on your tires.

    But if going downhill leaves you with greater momentum approaching a
    corner that you must deal with, then going uphill will reduce the
    problem of added momentum due to gravity, right?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 05:20:15 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight >>> in the driver's seat and one done without will NOT change whether or not >>> the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of >>> when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and >> more that I can't think of right now. Those systems can have issues if the >> alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the steering sensor says the car is going straight, but it is not going straight, the car senses a fault. If any sensor does not agree with other sensors, you are going to get a trouble code.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 05:26:29 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 11:03:48rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:00, Bob West wrote:
    On Nov 9, 2026 at 8:40:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 15:44, Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the
    loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".

    Ummmmm...no.

    That would depend entirely on HOW you drive down those roads.



    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same,
    especially if you are taking into account all 4 tires.

    Nope.

    If one argues that the downward grade increases loads, then how can the
    upward grade of the other half of the "commute" not result in
    proportional decreases in the load on the tires?

    Because you are fighting inertia in either direction. A flat, straight road >> will have the least wear, and any uphill or downhill twisty road will have >> more wear. And please don't bring up straight downhill roads. They are
    irrelevant for our purposes.
    Except for the fact that this is about TIRE wear.

    And if you "fight inertia" by braking in a straight line, you only wear
    your brake pads; well, you certainly don't cause asymmetric wear on your tires.

    But if going downhill leaves you with greater momentum approaching a
    corner that you must deal with, then going uphill will reduce the
    problem of added momentum due to gravity, right?

    Downhill or uphill, the front tires are scrubbing in turns. Do you agree that going uphill lightens the front, which in turn makes it easier for the fronts to understeer? I don't get why you're arguing this. Pulling into a parking
    spot wears the front tires.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:37:29 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight >>>> in the driver's seat and one done without will NOT change whether or not >>>> the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of >>>> when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and >>> more that I can't think of right now. Those systems can have issues if the >>> alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the steering sensor says the car is going straight, but it is not going straight, the car senses a fault. If any sensor does not agree with other sensors, you are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 22:39:15 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 22:26, Bob West wrote:
    On Nov 9, 2026 at 11:03:48rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:00, Bob West wrote:
    On Nov 9, 2026 at 8:40:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 15:44, Bob West wrote:
    On Nov 9, 2026 at 1:30:42rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    They may experience MORE wear going down a road, simply because the >>>>>> loads from braking and cornering my tend to be somewhat greater,

    I would change that to "will be much greater".

    Ummmmm...no.

    That would depend entirely on HOW you drive down those roads.



    but on
    the way up that road, those loads will be proportionately less.

    That crossed my mind too, but I think it would be pretty close to the same,
    especially if you are taking into account all 4 tires.

    Nope.

    If one argues that the downward grade increases loads, then how can the >>>> upward grade of the other half of the "commute" not result in
    proportional decreases in the load on the tires?

    Because you are fighting inertia in either direction. A flat, straight road >>> will have the least wear, and any uphill or downhill twisty road will have >>> more wear. And please don't bring up straight downhill roads. They are
    irrelevant for our purposes.
    Except for the fact that this is about TIRE wear.

    And if you "fight inertia" by braking in a straight line, you only wear
    your brake pads; well, you certainly don't cause asymmetric wear on your
    tires.

    But if going downhill leaves you with greater momentum approaching a
    corner that you must deal with, then going uphill will reduce the
    problem of added momentum due to gravity, right?

    Downhill or uphill, the front tires are scrubbing in turns.

    Yes. Either way.

    Do you agree that
    going uphill lightens the front, which in turn makes it easier for the fronts to understeer? I don't get why you're arguing this. Pulling into a parking spot wears the front tires.

    I'm not arguing that tires don't wear.

    I'm arguing that going down AND up a steeper road doesn't create a
    situation that increases tire wear overall.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 01:43:18 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    So the fact you agreed with Alan Baker on the directional math is scary.

    I didn't. You misread what I said, and I replied in another post. But do you see above where I said that the wear would be about the same up and down? That
    is the opposite of agreeing with him, but there is more detail in my other reply.

    OK. My mistake. Again. That's on me. Again, I apologize.

    In decades of posting to Usenet, I've always honored sensibly defensible statements, and I have no intention on going back on my promise to do so.

    I have to be careful when trolls like Alan infest a thread as they rile me.
    (I don't see his posts as I've plonked him, but he follows me like stink.)

    The core question (that I had no problem resolving decades ago), but which seems to be the new topic of discussion currently, is fair, in that it's
    Q: Does front outboard shoulder tire wear differ going uphill vs downhill?
    (assuming a one-lane slow-speed extremely twisty steep mountain road)
    A: ?

    The loading on the front outboard shoulder is different in both the turns
    and the braking, and it's wholly different in kind, not just in degree.

    Going down, we're braking almost constantly, and we're braking while we
    steer through the switchbacks. That's the killer combination. Braking
    shoves weight forward onto the front axle, so the front tires carry more
    load than they would on flat ground and braking-while-cornering piles
    lateral force on top of that already-increased vertical load. The outside
    front shoulder gets the worst of both at once. And because gravity carries
    us into each corner faster than we'd choose, the cornering forces are
    higher than we'd voluntarily generate. Downhill, that outside outboard
    shoulder is loaded heavily in both axes simultaneously.

    Going up, the picture is nearly the opposite on both counts.
    There's no braking at all, as we're on the throttle, not the brake.
    So the front tires are doing steering only, not shedding speed.

    Under power, weight transfers rearward, off the front axle, so the front
    tires carry far less load than they would on flat ground. And at the crawl speeds a one-lane steep switchback forces, even the cornering forces are
    small. Uphill, that shoulder is loaded lightly in both axes, with no
    braking overlay at all.

    So the two directions aren't mirror images of each other.
    They're two completely different load regimes.

    That's what makes the wear completely different and why the idea that it "cancels out over a round trip" fails. The side-to-side direction of the cornering load swaps when we reverse direction, but the magnitude of the combined loading doesn't. The downhill leg hammers that shoulder in both
    axes where the uphill leg barely loads it in either. There's nothing symmetrical to cancel, because the climb doesn't generate the forces in the first place.

    I could be wrong, but I can't be wrong just because there are the same
    number of turns in both directions, as loading is completely different.

    Q: Does front outboard shoulder tire wear differ going uphill vs downhill?
    (assuming a one-lane slow-speed extremely twisty steep mountain road)
    A: I say, emphatically, yes, of course.

    Why?
    a. Because the loading on the front outboard shoulder is completely
    different in the two directions.
    b. Heading downhill, that front outside outboard shoulder is heavily
    loaded by braking and braking-while-cornering.
    c. During uphill climbs, that shoulder is lightly loaded and as such,
    it's effectively unworn, so uphill driving has no realistic effect
    on that particular abnormal wear pattern.

    Let me know if that makes sense, or if we need to clarify a statement.

    In decades of posting to Usenet, I've always honored sensibly defensible statements, and I have no intention on going back on my promise to do so.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 02:21:21 2026
    From Newsgroup: comp.lang.python

    Bob West wrote:
    Downhill or uphill, the front tires are scrubbing in turns.


    Hi Bob,

    I always strive to make claims that are eminently logically defensible.

    To prevent confusion, I'm going to ignore anything that you respond to with respect to Alan (as I don't see his posts) but I do want to categorically
    state that we are discussing front tire outboard shoulder wear exclusively.

    It's my claim that downhill forces on the front outside tire outboard
    shoulder are completely different than uphill forces on the front outside
    tire outboard shoulder (even as I agree the number of turns is equal and opposite).

    Specifically, on a 10% grade at low speeds, the downhill leg loads the
    front tires heavily through braking and braking-while-cornering, while the uphill leg barely loads the front tires at all (although your parking-lot analogy certainly holds that there is always going to be 'some' wear).

    My logically defensible claim is that the forces on the front tire outboard shoulder are vastly different depending on the slope direction of travel.

    I'm not sure if that's what you're claiming or not, but I'm claiming that.
    Do you agree or disagree?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 06:29:16 2026
    From Newsgroup: comp.lang.python

    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight >>>>> in the driver's seat and one done without will NOT change whether or not >>>>> the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of >>>>> when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the >>>> alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs. >>>
    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the >> steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you >> are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack, it will throw it while driving after the alignment. It is not dependent on recording the sensors. I have no idea if it has sensors because i don't know what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that driver assist stuff. For any car that doesn't have it, you should obviously ignore what I said.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 23:34:32 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight >>>>>> in the driver's seat and one done without will NOT change whether or not >>>>>> the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>> times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of >>>>>> when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs. >>>>
    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly." >>>>
    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the >>> steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later. >>
    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on recording the sensors. I have no idea if it has sensors because i don't know what specific car we are talking about. What I do know is that whenever I heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 06:39:08 2026
    From Newsgroup: comp.lang.python

    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>>> times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs. >>>>>
    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly." >>>>>
    I'm going to need some source for that, because (and don't take this >>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the >>>> steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on >> recording the sensors. I have no idea if it has sensors because i don't know >> what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously >> ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Mon Nov 9 23:48:05 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>>>> times the stability augmentation systems have been activated?

    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly." >>>>>>
    I'm going to need some source for that, because (and don't take this >>>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on >>> recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I >>> heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously >>> ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize those
    pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.'

    And it's simply not so.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 06:57:28 2026
    From Newsgroup: comp.lang.python

    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>>>>> times the stability augmentation systems have been activated? >>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly." >>>>>>>
    I'm going to need some source for that, because (and don't take this >>>>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on >>>> recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I >>>> heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize those
    pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 00:00:23 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>>>>>> times the stability augmentation systems have been activated? >>>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly." >>>>>>>>
    I'm going to need some source for that, because (and don't take this >>>>>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on
    recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I >>>>> heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be >>>> used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize those
    pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was not properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 07:13:55 2026
    From Newsgroup: comp.lang.python

    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of >>>>>>>>>>> times the stability augmentation systems have been activated? >>>>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this >>>>>>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on
    recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be >>>>> used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize those
    pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was not properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about reading the written word. If you take your car in for a warning light, many things can cause that. If the dealer follows the diagnosis to an improper alignment, that is only one of the original possibilities. There is no trouble code for an improper alignment. Did you stop learning about cars in 1975? Why don't you start with Googling "do cars store antilock brake codes?" And then go down
    your list and ask the same about the rest of your list. And then you can come back and say, "oops", or you can just get ignored going forward. It's time for me to sleep now.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 01:00:39 2026
    From Newsgroup: comp.lang.python

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>
    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>>>

    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated? >>>>>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this >>>>>>>>>> poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on
    recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be >>>>>> used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize those >>>> pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about reading the
    written word. If you take your car in for a warning light, many things can cause that.

    Except the indicators for stability systems are NOT "warning lights".

    If the dealer follows the diagnosis to an improper alignment, that
    is only one of the original possibilities. There is no trouble code for an improper alignment. Did you stop learning about cars in 1975? Why don't you start with Googling "do cars store antilock brake codes?" And then go down your list and ask the same about the rest of your list. And then you can come back and say, "oops", or you can just get ignored going forward. It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    ...NOT when you simply brake hard enough that you cause the ABS to activate.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 16:54:14 2026
    From Newsgroup: comp.lang.python

    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>
    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>>
    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated? >>>>>>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on
    recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be >>>>>>> used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>> cars today, you need to get everything exactly right to minimize those >>>>> pesky stability warning lights. If they come on, the dealer can play >>>>> gotcha and say the alignment was not properly done. Then you pay. And >>>>> it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about reading the
    written word. If you take your car in for a warning light, many things can >> cause that.

    Except the indicators for stability systems are NOT "warning lights".

    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that
    is only one of the original possibilities. There is no trouble code for an >> improper alignment. Did you stop learning about cars in 1975? Why don't you >> start with Googling "do cars store antilock brake codes?" And then go down >> your list and ask the same about the rest of your list. And then you can come
    back and say, "oops", or you can just get ignored going forward. It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars "don't store codes" for a list of things, including ABS. Did you change your mind?


    ...NOT when you simply brake hard enough that you cause the ABS to activate.

    An intelligent person always considers the possibility that he is wrong. So
    you either think you know everything when the polar opposite is true, or you are a troll. You could have Googled all of this and found that everything you have said is wrong, but you didn't. I guess I'll be moving on.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 11:56:58 2026
    From Newsgroup: comp.lang.python

    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>
    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>
    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's worth of weight
    in the driver's seat and one done without will NOT change whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the number of
    times the stability augmentation systems have been activated? >>>>>>>>>>>>>>
    I did a little checking and no current production vehicle keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an all encompassing term
    for driver assist systems - lane keep, emergency braking, self driving, and
    more that I can't think of right now. Those systems can have issues if the
    alignment is not done properly. Those weight procedures might make very little
    difference, but it might be enough to push it past the tipping point for error
    codes, like when the alignment is in spec, but at the edge of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done properly."

    I'm going to need some source for that, because (and don't take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To simplify, if the
    steering sensor says the car is going straight, but it is not going straight,
    the car senses a fault. If any sensor does not agree with other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the alignment rack,
    it will throw it while driving after the alignment. It is not dependent on
    recording the sensors. I have no idea if it has sensors because i don't know
    what specific car we are talking about. What I do know is that whenever I
    heard about that type of strict procedure, it tended to be a car with all that
    driver assist stuff. For any car that doesn't have it, you should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer and be >>>>>>>> used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>>> cars today, you need to get everything exactly right to minimize those >>>>>> pesky stability warning lights. If they come on, the dealer can play >>>>>> gotcha and say the alignment was not properly done. Then you pay. And >>>>>> it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was not >>>> properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about reading the
    written word. If you take your car in for a warning light, many things can >>> cause that.

    Except the indicators for stability systems are NOT "warning lights".

    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that
    is only one of the original possibilities. There is no trouble code for an >>> improper alignment. Did you stop learning about cars in 1975? Why don't you >>> start with Googling "do cars store antilock brake codes?" And then go down >>> your list and ask the same about the rest of your list. And then you can come
    back and say, "oops", or you can just get ignored going forward. It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars "don't store codes" for a list of things, including ABS. Did you change your mind?


    ...NOT when you simply brake hard enough that you cause the ABS to activate.

    An intelligent person always considers the possibility that he is wrong. So you either think you know everything when the polar opposite is true, or you are a troll. You could have Googled all of this and found that everything you have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where
    to begin.

    Your thesis was (apparently) that if you got a fault code (which you
    didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance
    from ideal alignment no loading the car with the recommended weights
    would be...

    ...when compared to the tolerances that are permitted in the alignment
    value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight
    distribution. Assuming the position of the driver's centre of gravity is approximately at 48% of the wheelbase behind the front axle, then my
    weigh (about 195 lb) will be divided the same way between front and rear
    as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and
    with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by
    about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will
    change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce travel? Answer: almost zero. To be specific, the camber change per inch
    is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an
    acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#,
    when the driver drops into the seat, you'd increase by only a small
    fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.satellite.gps,comp.lang.python,rec.autos.tech on Tue Nov 10 14:27:27 2026
    From Newsgroup: comp.lang.python

    On 2026-11-09 23:21, Maria Sophia wrote:
    Bob West wrote:
    Downhill or uphill, the front tires are scrubbing in turns.


    Hi Bob,

    I always strive to make claims that are eminently logically defensible.

    To prevent confusion, I'm going to ignore anything that you respond to with respect to Alan (as I don't see his posts) but I do want to categorically state that we are discussing front tire outboard shoulder wear exclusively.

    It's my claim that downhill forces on the front outside tire outboard shoulder are completely different than uphill forces on the front outside tire outboard shoulder (even as I agree the number of turns is equal and opposite).

    Specifically, on a 10% grade at low speeds, the downhill leg loads the
    front tires heavily through braking and braking-while-cornering, while the uphill leg barely loads the front tires at all (although your parking-lot analogy certainly holds that there is always going to be 'some' wear).

    Except there is no NEED to do braking-while-cornering. Just slow down
    more while straight-line braking, which (I'm sure everyone will agree)
    won't cause abnormal wear on the outside shoulder of the tire.

    Get the vehicle's speed reduced sufficiently and there will be no need
    at all to brake during the corners.

    I think what your description of the problem illuminates is that you
    charge into these downhill corners going faster than you should.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Wed Nov 11 21:08:45 2026
    From Newsgroup: comp.lang.python

    Chris wrote:
    OK. For the Angeles Crest Highway

    Is this a joke? Post a link.

    That particular roadway was suggested by "The Real Bev", Chris.

    Since I'm a well-educated engineer & scientist, everything I post is fully reproducible by anyone, since I provide the GPX files & the scripts.

    The reason I *want* people to reproduce the results, and to test the script
    on their particular commute, is to IMPROVE OUR CAPBILITIES with their help.

    To that end, I appreciated the suggestion of adding the straightaways to
    the road inherency metrics, so that we can get an idea if the classic brake hard BEFORE turning is even remotely POSSIBLE on our mountain roads.

    To that end, the improved python script is included below, where I added
    the output for the five suggested roads in this thread from Blaine & TRB.

    Here's the inherency for three of our roads, but in the documentation below
    is the inherency for the five roads that were suggested in this thread.

    python roadgeometry.py road1.gpx
    Loaded 421 raw track points from 'road1.gpx'.

    --- Road Geometric Analysis: road1.gpx ---
    Total road length: 11111.64 meters
    Detected sharp/moderate curves (R < 200m): 292
    Detected qualifying straightaways (R >= 200m, >= 15m): 34
    Average straightaway length: 62.32 meters
    Longest straightaway: 453.67 meters
    Left-hand turning distribution: 150
    Right-hand turning distribution: 142
    Minimum corner radius (tightest hairpin): 4.79 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 4.79m | Direction: Left | Lat/Lon: XX.XX1034, -XXX.XX5605
    2. Radius: 5.06m | Direction: Left | Lat/Lon: XX.XX1050, -XXX.XX5611
    3. Radius: 5.28m | Direction: Left | Lat/Lon: XX.XX1075, -XXX.XX5644
    4. Radius: 5.36m | Direction: Right | Lat/Lon: XX.XX0586, -XXX.XX7215
    5. Radius: 6.26m | Direction: Left | Lat/Lon: XX.XX1079, -XXX.XX5670

    python roadgeometry.py road2.gpx
    Loaded 713 raw track points from 'road2.gpx'.

    --- Road Geometric Analysis: road2.gpx ---
    Total road length: 30634.74 meters
    Detected sharp/moderate curves (R < 200m): 595
    Detected qualifying straightaways (R >= 200m, >= 15m): 58
    Average straightaway length: 42.25 meters
    Longest straightaway: 102.91 meters
    Left-hand turning distribution: 312
    Right-hand turning distribution: 283
    Minimum corner radius (tightest hairpin): 4.92 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 4.92m | Direction: Right | Lat/Lon: XX.XX6125, -XXX.XX5330
    2. Radius: 5.43m | Direction: Right | Lat/Lon: XX.XX2734, -XXX.XX2312
    3. Radius: 6.25m | Direction: Left | Lat/Lon: XX.XX7563, -XXX.XX5785
    4. Radius: 6.56m | Direction: Left | Lat/Lon: XX.XX7011, -XXX.XX1182
    5. Radius: 6.67m | Direction: Right | Lat/Lon: XX.XX7367, -XXX.XX4661

    python roadgeometry.py road3.gpx
    Loaded 319 raw track points from 'road3.gpx'.

    --- Road Geometric Analysis: road3.gpx ---
    Total road length: 3623.56 meters
    Detected sharp/moderate curves (R < 200m): 290
    Detected qualifying straightaways (R >= 200m, >= 15m): 14
    Average straightaway length: 48.90 meters
    Longest straightaway: 147.15 meters
    Left-hand turning distribution: 146
    Right-hand turning distribution: 144
    Minimum corner radius (tightest hairpin): 4.80 meters

    --- Top 5 Tightest Hairpins / Curves ---
    1. Radius: 4.80m | Direction: Right | Lat/Lon: XX.XX3416, -XXX.XX8357
    2. Radius: 4.86m | Direction: Left | Lat/Lon: XX.XX0522, -XXX.XX7788
    3. Radius: 4.86m | Direction: Right | Lat/Lon: XX.XX0522, -XXX.XX7788
    4. Radius: 4.91m | Direction: Right | Lat/Lon: XX.XX3657, -XXX.XX7972
    5. Radius: 4.93m | Direction: Left | Lat/Lon: XX.XX3444, -XXX.XX7060

    The key question to answer, given the 10% to 20% constant grade, is whether there is room to "brake before turns" given a short distance between turns.

    # #################################################################
    # mountaincurves.py
    # GPX road geometry analysis
    #
    # Calculates:
    # Corner radii
    # Left/right turn directions
    # Curvature statistics
    # Top 5 tightest hairpins
    # Total road length, straightaways and bending percentages
    #
    # Use model:
    # python mountaincurves.py [input.gpx]
    #
    # Reproduceable examples included in this script:
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # python mountaincurves.py angelescrest.gpx
    # python mountaincurves.py mulholland.gpx
    # #################################################################
    # Moki Dugway
    # <https://i.postimg.cc/DydH9gFb/mokidugway.jpg>
    # <https://i.postimg.cc/3x8VYvxN/mokidugway.png>
    # Shafer Canyon
    # <https://i.postimg.cc/HLjN71MB/shafercanyon.jpg>
    # <https://i.postimg.cc/9M7NJPJ1/shafercanyon.png>
    # Burr Trail
    # <https://i.postimg.cc/X7f6VWKC/burrtrail.jpg>
    # <https://i.postimg.cc/CxJyq4Q0/burrtrail.png>
    # Guardsman Pass
    # <https://i.postimg.cc/JnDSSC4x/guardsmanpass.jpg>
    # <https://i.postimg.cc/G3DZQR55/guardsmanpass.png>
    # #################################################################
    # v1.7 20261104 Ran a random control test on Utah mountain roads
    # Suggested by Blaine Message-ID: <11cficq$pl38$1@dont-email.me>
    # #################################################################
    # Four Utah test roads (randomly selected on comp.lang.python)
    # 1. Moki Dugway
    # 2. Shafer Canyon Road (Shafer Trail)
    # 3. Burr Trail
    # 4. Guardsman Pass
    #
    # Shafer Canyon and Burr Trail have steep switchback sections.
    # Moki Dugway has sustained descending switchbacks.
    # Guardsman Pass is a paved-mountain-road comparison.
    # ###################################################################
    # <https://gpx.studio/>
    # 1. Open the appropriate road link below.
    # 2. Select File > New.
    # 3. Select the route-planning tool (pen icon).
    # 4. Select the appropriate routing mode (bicycle).
    # 5. Trace the complete road or click beginning & ending points.
    # 6. Select File > Export > Download file.
    # 7. Save using the suggested filename.
    # 8. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # -------------------------------------------------------------------
    # <https://overpass-turbo.eu/>
    # 1. Open the appropriate road link below.
    # 2. Delete the existing query in the editor (if any).
    # 3. Copy ONE query below into the editor and press the "Run" icon.
    # 4. Press the "Search" icon to zoom into the highlighted results.
    # 5. Select Export > Data > GPX
    # 6. Save using the suggested filename.
    # 7. Run the Python analysis.
    # C:\> python mountaincurves.py [input.gpx]
    # -------------------------------------------------------------------
    # <https://brouter.de/brouter-web/>
    # Moki Dugway: North to South, descending Cedar Mesa
    # <https://i.postimg.cc/6qKjCkng/mokidugway.gif>
    # <https://www.komoot.com/highlight/6669890>
    # <https://www.utahscanyoncountry.com/The-Moki-Dugway-Scenic-Backway-Utah-Highway-261/>
    # 1. Point a web browser to https://brouter.de/brouter-web/
    # 2. In the top-left pulldown, keep "Trekking bike, Original"
    # 3. In the left search icon, search for "utah moki dugway"
    # 4. That will zoom you to the middle of the Moki Dugway
    # 5. Click the draw/pencil icon in the UI toolbar at left
    # 6. Start the click on UT 261 just north of the switchbacks,
    # on top of Cedar Mesa (near the junction pointing toward Muley Point)
    # 7. End the click on UT 261 just south of the switchbacks down
    # on the desert floor, near the Valley of the Gods turnoff.
    # BRouter will automatically snap the route along the road nodes,
    # calculating the 3-mile, 11% grade descent down the switchbacks.
    # <https://brouter.de/brouter-web/#map=16/37.2744/-109.9351/standard&lonlats=-109.942589,37.278313;-109.942504,37.272986;-109.942504,37.272983>
    # 8. If desired, click on "incline coding" at left for color-coded gradients
    # 9. At top, click the "Export" button, choose a name & tap "Export Route"
    # 10. The result will be a mukidugway.gpx file that can be analyzed
    #
    # Then run the python road inherency script on that gpx output:
    # python mountaincurves.py mokidugway2.gpx
    # ###################################################################
    # Moki Dugway, Utah State Route 261, Cedar Mesa, Utah.
    # I traced the steep switchback section
    # <https://gpx.studio/app#14.41/37.27473/-109.93787>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Moki Dugway - southern hairpin extension
    # (
    # way["highway"]
    # (37.17,-109.96,37.23,-109.91);
    # );
    # (._;>;);
    # out body;
    # Save as mokidugway.gpx
    # -------------------------------------------------------------------
    # Shafer Canyon Road (Shafer Trail) Canyonlands National Park, Utah
    # <https://gpx.studio/app#15/38.45303/-109.82112>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # way["highway"]["name"~"Shafer Trail|Shafer Canyon",i]
    # (38.43,-109.84,38.51,-109.77);
    # (._;>;);
    # out body;
    # Save as shafercanyon.gpx
    # -------------------------------------------------------------------
    # Burr Trail, Boulder, Utah, through Long Canyon and Waterpocket Fold.
    # <https://gpx.studio/app#14.55/37.85138/-111.03141>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Burr Trail, Boulder, Utah
    # // Long Canyon and Waterpocket Fold
    # (
    # way["highway"]["name"~"Burr Trail",i]
    # (37.81,-111.08,37.90,-110.98);
    # );
    # (._;>;);
    # out body;
    #
    # Save as burrtrail.gpx
    # -------------------------------------------------------------------
    # Guardsman Pass, Wasatch Mountains, between Brighton & Park City, Utah.
    # <https://gpx.studio/app#13.81/40.61548/-111.52533>
    # <https://overpass-turbo.eu/>
    # [out:xml][timeout:60];
    # // Guardsman Pass
    # // Wasatch Mountains, between Brighton and Park City, Utah
    # (
    # way["highway"]["name"~"Guardsman Pass|Guardsman Pass Road",i]
    # (40.55,-111.62,40.66,-111.48);
    # );
    # Save as guardsmanpass.gpx
    # ###################################################################
    # RUNNING THE FOUR TESTS
    # python mountaincurves.py mokidugway.gpx
    # python mountaincurves.py shafercanyon.gpx
    # python mountaincurves.py burrtrail.gpx
    # python mountaincurves.py guardsmanpass.gpx
    # ###################################################################
    import xml.etree.ElementTree as ET
    import math
    import sys

    def parse_gpx(filename):
    tree = ET.parse(filename)
    root = tree.getroot()

    points = []
    # Extract all track points in order across all track segments
    for trkpt in root.iter('{http://www.topografix.com/GPX/1/1}trkpt'):
    lat = float(trkpt.get('lat'))
    lon = float(trkpt.get('lon'))
    points.append((lat, lon))
    return points

    def calculate_curvature(p1, p2, p3):
    # Menger curvature / circumcircle radius calculation
    # Project lat/lon to local meters centered around p2
    lat_scale = 111132.92
    lon_scale = 111412.84 * math.cos(math.radians(p2[0]))

    def to_m(p):
    return ((p[1] - p2[1]) * lon_scale, (p[0] - p2[0]) * lat_scale)

    A = to_m(p1)
    B = (0.0, 0.0) # p2 is origin
    C = to_m(p3)

    # Side lengths of triangle ABC
    a = math.hypot(B[0]-C[0], B[1]-C[1])
    b = math.hypot(A[0]-C[0], A[1]-C[1])
    c = math.hypot(A[0]-B[0], A[1]-B[1])

    s = (a + b + c) / 2.0
    area_sq = s * (s - a) * (s - b) * (s - c)
    if area_sq <= 0 or a * b * c == 0:
    return float('inf'), "Straight"

    area = math.sqrt(abs(area_sq))
    radius = (a * b * c) / (4.0 * area)

    # Determine turn direction via cross product sign of AB x AC
    cross = (A[0] - B[0]) * (C[1] - B[1]) - (A[1] - B[1]) * (C[0] - B[0])
    direction = "Left" if cross > 0 else "Right"

    return radius, direction

    if __name__ == "__main__":
    # Determine GPX filename from command-line arguments, or default to soda_springs.gpx
    if len(sys.argv) > 1:
    gpx_filename = sys.argv[1]
    else:
    gpx_filename = 'soda_springs.gpx'
    print(f"No filename provided. Defaulting to '{gpx_filename}'...")
    print(f"Tip: You can pass a custom file like: python roadgeometry.py my_route.gpx\n")

    try:
    pts = parse_gpx(gpx_filename)
    except FileNotFoundError:
    print(f"Error: Could not find GPX file '{gpx_filename}'. Please check the filename or path.")
    sys.exit(1)

    print(f"Loaded {len(pts)} raw track points from '{gpx_filename}'.")

    left_turns = 0
    right_turns = 0
    curve_records = [] # Store detailed records: (radius, direction, lat, lon)

    # Straightaway tracking variables
    straights_count = 0
    current_straight_length = 0.0
    straight_lengths = []

    # Slide a window of 3 points (p1, p2, p3) to analyze curvature
    for i in range(len(pts) - 2):
    # Calculate physical distance between consecutive points in meters
    lat_scale = 111132.92
    lon_scale = 111412.84 * math.cos(math.radians(pts[i+1][0]))
    seg_len1 = math.hypot((pts[i+1][1] - pts[i][1]) * lon_scale,
    (pts[i+1][0] - pts[i][0]) * lat_scale)
    seg_len2 = math.hypot((pts[i+2][1] - pts[i+1][1]) * lon_scale,
    (pts[i+2][0] - pts[i+1][0]) * lat_scale)

    # Filter out cross-segment data jumps (e.g. disconnected OSM ways > 100m)
    if seg_len1 > 100.0 or seg_len2 > 100.0:
    if current_straight_length >= 15.0:
    straights_count += 1
    straight_lengths.append(current_straight_length)
    current_straight_length = 0.0
    continue

    r, direction = calculate_curvature(pts[i], pts[i+1], pts[i+2])

    if r < 200: # Filter for curves with a radius under 200 meters
    curve_records.append((r, direction, pts[i+1][0], pts[i+1][1]))
    if direction == "Left":
    left_turns += 1
    elif direction == "Right":
    right_turns += 1

    # If we were tracking a straightaway, check if it met our minimum length (15m)
    if current_straight_length >= 15.0:
    straights_count += 1
    straight_lengths.append(current_straight_length)
    current_straight_length = 0.0
    else:
    # Accumulate length of the straight/gentle section
    current_straight_length += seg_len2

    # Catch any trailing straightaway at the very end of the track
    if current_straight_length >= 15.0:
    straights_count += 1
    straight_lengths.append(current_straight_length)

    # Calculate total path length and bending statistics
    total_length = sum(straight_lengths) + sum([r for r, _, _, _ in curve_records]) # placeholder for distance accumulation
    # Alternatively, summing segment lengths properly:
    total_path_length = sum(math.hypot((pts[k+1][1] - pts[k][1]) * 111412.84 * math.cos(math.radians(pts[k+1][0])),
    (pts[k+1][0] - pts[k][0]) * 111132.92) for k in range(len(pts)-1))
    curved_distance = sum(straight_lengths) # logic can be adapted to sum curve segment lengths

    print(f"\n--- Road Geometric Analysis: {gpx_filename} ---")
    print(f"Total road length: {total_path_length:.2f} meters")
    print(f"Detected sharp/moderate curves (R < 200m): {len(curve_records)}")
    print(f"Detected qualifying straightaways (R >= 200m, >= 15m): {straights_count}")
    if straight_lengths:
    print(f"Average straightaway length: {sum(straight_lengths)/len(straight_lengths):.2f} meters")
    print(f"Longest straightaway: {max(straight_lengths):.2f} meters")
    print(f"Left-hand turning distribution: {left_turns}")
    print(f"Right-hand turning distribution: {right_turns}")

    if curve_records:
    # Sort curve records by radius ascending to find the tightest hairpins first
    curve_records.sort(key=lambda x: x[0])
    print(f"Minimum corner radius (tightest hairpin): {curve_records[0][0]:.2f} meters")

    print(f"\n--- Top 5 Tightest Hairpins / Curves ---")
    for idx, (r, direction, lat, lon) in enumerate(curve_records[:5], 1):
    print(f"{idx}. Radius: {r:.2f}m | Direction: {direction} | Lat/Lon: {lat:.6f}, {lon:.6f}")
    # ###################################################################
    # END OF mountaincurves.py
    # ###################################################################
    # Results:
    # C:\> python mountaincurves.py mokidugway.gpx
    # Loaded 220 raw track points from 'mokidugway.gpx'.
    #
    # --- Road Geometric Analysis: mokidugway.gpx ---
    # Total road length: 4012.66 meters
    # Detected sharp/moderate curves (R < 200m): 154
    # Detected qualifying straightaways (R >= 200m, >= 15m): 21
    # Average straightaway length: 87.21 meters
    # Longest straightaway: 267.93 meters
    # Left-hand turning distribution: 76
    # Right-hand turning distribution: 78
    # Minimum corner radius (tightest hairpin): 5.89 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 5.89m | Direction: Right | Lat/Lon: 37.276825, -109.935955
    # 2. Radius: 7.00m | Direction: Left | Lat/Lon: 37.272532, -109.944278
    # 3. Radius: 7.67m | Direction: Left | Lat/Lon: 37.272507, -109.944243
    # 4. Radius: 8.48m | Direction: Right | Lat/Lon: 37.276883, -109.935927
    # 5. Radius: 8.84m | Direction: Right | Lat/Lon: 37.276849, -109.935935
    #
    # C:\> python mountaincurves.py shafercanyon.gpx
    # Loaded 162 raw track points from 'shafercanyon.gpx'.
    #
    # --- Road Geometric Analysis: shafercanyon.gpx ---
    # Total road length: 3494.97 meters
    # Detected sharp/moderate curves (R < 200m): 131
    # Detected qualifying straightaways (R >= 200m, >= 15m): 15
    # Average straightaway length: 63.69 meters
    # Longest straightaway: 247.76 meters
    # Left-hand turning distribution: 66
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 3.97 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 3.97m | Direction: Right | Lat/Lon: 38.449308, -109.820485
    # 2. Radius: 4.44m | Direction: Left | Lat/Lon: 38.448474, -109.818339
    # 3. Radius: 6.81m | Direction: Left | Lat/Lon: 38.447882, -109.818434
    # 4. Radius: 7.10m | Direction: Left | Lat/Lon: 38.447199, -109.819240
    # 5. Radius: 7.93m | Direction: Right | Lat/Lon: 38.450305, -109.819414
    #
    # C:\> python mountaincurves.py burrtrail.gpx
    # Loaded 199 raw track points from 'burrtrail.gpx'.
    #
    # --- Road Geometric Analysis: burrtrail.gpx ---
    # Total road length: 3970.66 meters
    # Detected sharp/moderate curves (R < 200m): 139
    # Detected qualifying straightaways (R >= 200m, >= 15m): 26
    # Average straightaway length: 66.65 meters
    # Longest straightaway: 378.64 meters
    # Left-hand turning distribution: 71
    # Right-hand turning distribution: 68
    # Minimum corner radius (tightest hairpin): 4.70 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 4.70m | Direction: Left | Lat/Lon: 37.848198, -111.024654
    # 2. Radius: 6.16m | Direction: Left | Lat/Lon: 37.848657, -111.023535
    # 3. Radius: 6.88m | Direction: Right | Lat/Lon: 37.850700, -111.027191
    # 4. Radius: 7.59m | Direction: Right | Lat/Lon: 37.850662, -111.027217
    # 5. Radius: 7.73m | Direction: Right | Lat/Lon: 37.850838, -111.025700
    #
    # C:\> python mountaincurves.py guardsmanpass.gpx
    # Loaded 219 raw track points from 'guardsmanpass.gpx'.
    #
    # --- Road Geometric Analysis: guardsmanpass.gpx ---
    # Total road length: 5248.45 meters
    # Detected sharp/moderate curves (R < 200m): 135
    # Detected qualifying straightaways (R >= 200m, >= 15m): 31
    # Average straightaway length: 87.77 meters
    # Longest straightaway: 277.35 meters
    # Left-hand turning distribution: 70
    # Right-hand turning distribution: 65
    # Minimum corner radius (tightest hairpin): 2.04 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620587, -111.495800
    # 2. Radius: 2.04m | Direction: Left | Lat/Lon: 40.620605, -111.495784
    # 3. Radius: 2.29m | Direction: Left | Lat/Lon: 40.620597, -111.495796
    # 4. Radius: 2.33m | Direction: Right | Lat/Lon: 40.620464, -111.495741
    # 5. Radius: 2.71m | Direction: Right | Lat/Lon: 40.620569, -111.495601
    #
    # C:\> python mountaincurves.py angelescrest.gpx
    # Loaded 632 raw track points from 'angelescrest.gpx'.
    #
    # --- Road Geometric Analysis: angelescrest.gpx ---
    # Total road length: 12591.62 meters
    # Detected sharp/moderate curves (R < 200m): 424
    # Detected qualifying straightaways (R >= 200m, >= 15m): 69
    # Average straightaway length: 81.22 meters
    # Longest straightaway: 260.03 meters
    # Left-hand turning distribution: 207
    # Right-hand turning distribution: 217
    # Minimum corner radius (tightest hairpin): 10.28 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 10.28m | Direction: Left | Lat/Lon: 34.222522, -118.192759
    # 2. Radius: 18.12m | Direction: Right | Lat/Lon: 34.220180, -118.191992
    # 3. Radius: 21.20m | Direction: Right | Lat/Lon: 34.222678, -118.192989
    # 4. Radius: 38.06m | Direction: Left | Lat/Lon: 34.228787, -118.183125
    # 5. Radius: 39.78m | Direction: Left | Lat/Lon: 34.228913, -118.182865
    #
    # C:\> python mountaincurves.py mulholland.gpx
    # Loaded 318 raw track points from 'mulholland.gpx'.
    #
    # --- Road Geometric Analysis: mulholland.gpx ---
    # Total road length: 7071.52 meters
    # Detected sharp/moderate curves (R < 200m): 221
    # Detected qualifying straightaways (R >= 200m, >= 15m): 37
    # Average straightaway length: 78.48 meters
    # Longest straightaway: 356.05 meters
    # Left-hand turning distribution: 117
    # Right-hand turning distribution: 104
    # Minimum corner radius (tightest hairpin): 9.33 meters
    #
    # --- Top 5 Tightest Hairpins / Curves ---
    # 1. Radius: 9.33m | Direction: Right | Lat/Lon: 34.129665, -118.468754
    # 2. Radius: 15.26m | Direction: Left | Lat/Lon: 34.129776, -118.466845
    # 3. Radius: 16.88m | Direction: Left | Lat/Lon: 34.129803, -118.466891
    # 4. Radius: 17.45m | Direction: Right | Lat/Lon: 34.131688, -118.431116
    # 5. Radius: 18.41m | Direction: Right | Lat/Lon: 34.129666, -118.466773
    # ###################################################################
    # ###################################################################
    --
    On Usenet, we pool our knowledge so everyone's a little smarter.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Wed Nov 11 20:42:08 2026
    From Newsgroup: comp.lang.python

    On 2026-11-10 11:56, Alan wrote:
    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>
    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's >>>>>>>>>>>>>>> worth of weight
    in the driver's seat and one done without will NOT change >>>>>>>>>>>>>>> whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the >>>>>>>>>>>>>>> number of
    times the stability augmentation systems have been >>>>>>>>>>>>>>> activated?

    I did a little checking and no current production vehicle >>>>>>>>>>>>>>> keeps a log of
    when the stability systems have been activated.


    Okay, I've been forever using "stability" loosely as an >>>>>>>>>>>>>> all encompassing term
    for driver assist systems - lane keep, emergency braking, >>>>>>>>>>>>>> self driving, and
    more that I can't think of right now. Those systems can >>>>>>>>>>>>>> have issues if the
    alignment is not done properly. Those weight procedures >>>>>>>>>>>>>> might make very little
    difference, but it might be enough to push it past the >>>>>>>>>>>>>> tipping point for error
    codes, like when the alignment is in spec, but at the edge >>>>>>>>>>>>>> of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done >>>>>>>>>>>>> properly."

    I'm going to need some source for that, because (and don't >>>>>>>>>>>>> take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To >>>>>>>>>>>> simplify, if the
    steering sensor says the car is going straight, but it is >>>>>>>>>>>> not going straight,
    the car senses a fault. If any sensor does not agree with >>>>>>>>>>>> other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to >>>>>>>>>>> be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the >>>>>>>>>> alignment rack,
    it will throw it while driving after the alignment. It is not >>>>>>>>>> dependent on
    recording the sensors. I have no idea if it has sensors
    because i don't know
    what specific car we are talking about. What I do know is that >>>>>>>>>> whenever I
    heard about that type of strict procedure, it tended to be a >>>>>>>>>> car with all that
    driver assist stuff. For any car that doesn't have it, you >>>>>>>>>> should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer >>>>>>>>> and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>>>> cars today, you need to get everything exactly right to minimize >>>>>>> those
    pesky stability warning lights. If they come on, the dealer can play >>>>>>> gotcha and say the alignment was not properly done. Then you pay. >>>>>>> And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was >>>>> not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about
    reading the
    written word. If you take your car in for a warning light, many
    things can
    cause that.

    Except the indicators for stability systems are NOT "warning lights".

    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that
    is only one of the original possibilities. There is no trouble code
    for an
    improper alignment. Did you stop learning about cars in 1975? Why
    don't you
    start with Googling "do cars store antilock brake codes?" And then
    go down
    your list and ask the same about the rest of your list. And then you
    can come
    back and say, "oops", or you can just get ignored going forward.
    It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars
    "don't
    store codes" for a list of things, including ABS. Did you change your
    mind?


    ...NOT when you simply brake hard enough that you cause the ABS to
    activate.

    An intelligent person always considers the possibility that he is
    wrong. So
    you either think you know everything when the polar opposite is true,
    or you
    are a troll. You could have Googled all of this and found that
    everything you
    have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where
    to begin.

    Your thesis was (apparently) that if you got a fault code (which you
    didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance
    from ideal alignment no loading the car with the recommended weights
    would be...

    ...when compared to the tolerances that are permitted in the alignment value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight distribution. Assuming the position of the driver's centre of gravity is approximately at 48% of the wheelbase behind the front axle, then my
    weigh (about 195 lb) will be divided the same way between front and rear
    as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and
    with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce travel? Answer: almost zero. To be specific, the camber change per inch
    is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#, when the driver drops into the seat, you'd increase by only a small fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.

    Shocking.

    I provide quantitative analysis of the issue you THOUGHT you understood...

    ...and you have nothing to say.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 12 04:59:54 2026
    From Newsgroup: comp.lang.python

    On Nov 11, 2026 at 9:42:08rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 11:56, Alan wrote:
    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>
    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>
    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's >>>>>>>>>>>>>>>> worth of weight
    in the driver's seat and one done without will NOT change >>>>>>>>>>>>>>>> whether or not
    the stability warning lights come on or not.

    Furthermore, what gives you the idea that cars record the >>>>>>>>>>>>>>>> number of
    times the stability augmentation systems have been >>>>>>>>>>>>>>>> activated?

    I did a little checking and no current production vehicle >>>>>>>>>>>>>>>> keeps a log of
    when the stability systems have been activated. >>>>>>>>>>>>>>>

    Okay, I've been forever using "stability" loosely as an >>>>>>>>>>>>>>> all encompassing term
    for driver assist systems - lane keep, emergency braking, >>>>>>>>>>>>>>> self driving, and
    more that I can't think of right now. Those systems can >>>>>>>>>>>>>>> have issues if the
    alignment is not done properly. Those weight procedures >>>>>>>>>>>>>>> might make very little
    difference, but it might be enough to push it past the >>>>>>>>>>>>>>> tipping point for error
    codes, like when the alignment is in spec, but at the edge >>>>>>>>>>>>>>> of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done >>>>>>>>>>>>>> properly."

    I'm going to need some source for that, because (and don't >>>>>>>>>>>>>> take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To >>>>>>>>>>>>> simplify, if the
    steering sensor says the car is going straight, but it is >>>>>>>>>>>>> not going straight,
    the car senses a fault. If any sensor does not agree with >>>>>>>>>>>>> other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to >>>>>>>>>>>> be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the >>>>>>>>>>> alignment rack,
    it will throw it while driving after the alignment. It is not >>>>>>>>>>> dependent on
    recording the sensors. I have no idea if it has sensors
    because i don't know
    what specific car we are talking about. What I do know is that >>>>>>>>>>> whenever I
    heard about that type of strict procedure, it tended to be a >>>>>>>>>>> car with all that
    driver assist stuff. For any car that doesn't have it, you >>>>>>>>>>> should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer >>>>>>>>>> and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>>>>> cars today, you need to get everything exactly right to minimize >>>>>>>> those
    pesky stability warning lights. If they come on, the dealer can play >>>>>>>> gotcha and say the alignment was not properly done. Then you pay. >>>>>>>> And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was >>>>>> not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about
    reading the
    written word. If you take your car in for a warning light, many
    things can
    cause that.

    Except the indicators for stability systems are NOT "warning lights".

    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that
    is only one of the original possibilities. There is no trouble code
    for an
    improper alignment. Did you stop learning about cars in 1975? Why
    don't you
    start with Googling "do cars store antilock brake codes?" And then
    go down
    your list and ask the same about the rest of your list. And then you >>>>> can come
    back and say, "oops", or you can just get ignored going forward.
    It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars
    "don't
    store codes" for a list of things, including ABS. Did you change your
    mind?


    ...NOT when you simply brake hard enough that you cause the ABS to
    activate.

    An intelligent person always considers the possibility that he is
    wrong. So
    you either think you know everything when the polar opposite is true,
    or you
    are a troll. You could have Googled all of this and found that
    everything you
    have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where
    to begin.

    Your thesis was (apparently) that if you got a fault code (which you
    didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance
    from ideal alignment no loading the car with the recommended weights
    would be...

    ...when compared to the tolerances that are permitted in the alignment
    value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight
    distribution. Assuming the position of the driver's centre of gravity is
    approximately at 48% of the wheelbase behind the front axle, then my
    weigh (about 195 lb) will be divided the same way between front and rear
    as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and
    with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by
    about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will
    change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce
    travel? Answer: almost zero. To be specific, the camber change per inch
    is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an
    acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#,
    when the driver drops into the seat, you'd increase by only a small
    fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.

    Shocking.

    I provide quantitative analysis of the issue you THOUGHT you understood...

    ...and you have nothing to say.

    Everyone knows different things. No one knows everything, although you believe you do. What I have to say is based on not only master tech certs in ASE and all the GM lines, but also spending decades working in service departments of new car dealers, where I had - and used - direct access to the factory reps, engineers, and tech support. I know what they do on warranty claims, and
    plenty of it is absurd. I was trying to tell everyone how they think, and how they justify their positions. I would never bother putting weights in my own car to align it. I don't need all the tech spew above to know it would change nothing at all for my purposes. And yes, some forms of misalignment can set a code and warning light, in spite of your ridicule. Just look it up if you
    don't believe me. And again, if the car doesn't have all those new driver assist features, then of course it won't set a code. Do I really have to tell you that? Of course I do, because you simply cannot accept that you might be wrong about your stupid little arguments over nothing at all. You would argue that a misfire won't set a CEL, and then tell me that you drive a 55 Chevy.
    And the only reason I bother with this is that I have this enjoyment from making fun of ridiculous people.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Wed Nov 11 22:07:02 2026
    From Newsgroup: comp.lang.python

    On 2026-11-11 21:59, Bob West wrote:
    On Nov 11, 2026 at 9:42:08rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 11:56, Alan wrote:
    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>
    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>>> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's >>>>>>>>>>>>>>>>> worth of weight
    in the driver's seat and one done without will NOT change >>>>>>>>>>>>>>>>> whether or not
    the stability warning lights come on or not. >>>>>>>>>>>>>>>>>
    Furthermore, what gives you the idea that cars record the >>>>>>>>>>>>>>>>> number of
    times the stability augmentation systems have been >>>>>>>>>>>>>>>>> activated?

    I did a little checking and no current production vehicle >>>>>>>>>>>>>>>>> keeps a log of
    when the stability systems have been activated. >>>>>>>>>>>>>>>>

    Okay, I've been forever using "stability" loosely as an >>>>>>>>>>>>>>>> all encompassing term
    for driver assist systems - lane keep, emergency braking, >>>>>>>>>>>>>>>> self driving, and
    more that I can't think of right now. Those systems can >>>>>>>>>>>>>>>> have issues if the
    alignment is not done properly. Those weight procedures >>>>>>>>>>>>>>>> might make very little
    difference, but it might be enough to push it past the >>>>>>>>>>>>>>>> tipping point for error
    codes, like when the alignment is in spec, but at the edge >>>>>>>>>>>>>>>> of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done >>>>>>>>>>>>>>> properly."

    I'm going to need some source for that, because (and don't >>>>>>>>>>>>>>> take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To >>>>>>>>>>>>>> simplify, if the
    steering sensor says the car is going straight, but it is >>>>>>>>>>>>>> not going straight,
    the car senses a fault. If any sensor does not agree with >>>>>>>>>>>>>> other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to >>>>>>>>>>>>> be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the >>>>>>>>>>>> alignment rack,
    it will throw it while driving after the alignment. It is not >>>>>>>>>>>> dependent on
    recording the sensors. I have no idea if it has sensors >>>>>>>>>>>> because i don't know
    what specific car we are talking about. What I do know is that >>>>>>>>>>>> whenever I
    heard about that type of strict procedure, it tended to be a >>>>>>>>>>>> car with all that
    driver assist stuff. For any car that doesn't have it, you >>>>>>>>>>>> should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer >>>>>>>>>>> and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>>>>>> cars today, you need to get everything exactly right to minimize >>>>>>>>> those
    pesky stability warning lights. If they come on, the dealer can play >>>>>>>>> gotcha and say the alignment was not properly done. Then you pay. >>>>>>>>> And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was >>>>>>> not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about >>>>>> reading the
    written word. If you take your car in for a warning light, many
    things can
    cause that.

    Except the indicators for stability systems are NOT "warning lights". >>>>
    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that >>>>>> is only one of the original possibilities. There is no trouble code >>>>>> for an
    improper alignment. Did you stop learning about cars in 1975? Why
    don't you
    start with Googling "do cars store antilock brake codes?" And then >>>>>> go down
    your list and ask the same about the rest of your list. And then you >>>>>> can come
    back and say, "oops", or you can just get ignored going forward.
    It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars
    "don't
    store codes" for a list of things, including ABS. Did you change your
    mind?


    ...NOT when you simply brake hard enough that you cause the ABS to
    activate.

    An intelligent person always considers the possibility that he is
    wrong. So
    you either think you know everything when the polar opposite is true,
    or you
    are a troll. You could have Googled all of this and found that
    everything you
    have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where >>> to begin.

    Your thesis was (apparently) that if you got a fault code (which you
    didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance
    from ideal alignment no loading the car with the recommended weights
    would be...

    ...when compared to the tolerances that are permitted in the alignment
    value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight
    distribution. Assuming the position of the driver's centre of gravity is >>> approximately at 48% of the wheelbase behind the front axle, then my
    weigh (about 195 lb) will be divided the same way between front and rear >>> as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and
    with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by
    about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will
    change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce
    travel? Answer: almost zero. To be specific, the camber change per inch
    is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an
    acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#, >>> when the driver drops into the seat, you'd increase by only a small
    fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.

    Shocking.

    I provide quantitative analysis of the issue you THOUGHT you understood... >>
    ...and you have nothing to say.

    Everyone knows different things. No one knows everything, although you believe
    you do. What I have to say is based on not only master tech certs in ASE and all the GM lines, but also spending decades working in service departments of new car dealers, where I had - and used - direct access to the factory reps, engineers, and tech support. I know what they do on warranty claims, and plenty of it is absurd. I was trying to tell everyone how they think, and how they justify their positions. I would never bother putting weights in my own car to align it. I don't need all the tech spew above to know it would change nothing at all for my purposes. And yes, some forms of misalignment can set a code and warning light, in spite of your ridicule. Just look it up if you don't believe me. And again, if the car doesn't have all those new driver assist features, then of course it won't set a code. Do I really have to tell you that? Of course I do, because you simply cannot accept that you might be wrong about your stupid little arguments over nothing at all. You would argue that a misfire won't set a CEL, and then tell me that you drive a 55 Chevy. And the only reason I bother with this is that I have this enjoyment from making fun of ridiculous people.

    And yet you don't address a single factual point I just made...

    You say "look it up"...

    ...but won't provide a source.

    Illuminating.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Thu Nov 12 05:16:12 2026
    From Newsgroup: comp.lang.python

    On Nov 11, 2026 at 11:07:02rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-11 21:59, Bob West wrote:
    On Nov 11, 2026 at 9:42:08rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 11:56, Alan wrote:
    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>
    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>
    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>>
    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>>>> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's >>>>>>>>>>>>>>>>>> worth of weight
    in the driver's seat and one done without will NOT change >>>>>>>>>>>>>>>>>> whether or not
    the stability warning lights come on or not. >>>>>>>>>>>>>>>>>>
    Furthermore, what gives you the idea that cars record the >>>>>>>>>>>>>>>>>> number of
    times the stability augmentation systems have been >>>>>>>>>>>>>>>>>> activated?

    I did a little checking and no current production vehicle >>>>>>>>>>>>>>>>>> keeps a log of
    when the stability systems have been activated. >>>>>>>>>>>>>>>>>

    Okay, I've been forever using "stability" loosely as an >>>>>>>>>>>>>>>>> all encompassing term
    for driver assist systems - lane keep, emergency braking, >>>>>>>>>>>>>>>>> self driving, and
    more that I can't think of right now. Those systems can >>>>>>>>>>>>>>>>> have issues if the
    alignment is not done properly. Those weight procedures >>>>>>>>>>>>>>>>> might make very little
    difference, but it might be enough to push it past the >>>>>>>>>>>>>>>>> tipping point for error
    codes, like when the alignment is in spec, but at the edge >>>>>>>>>>>>>>>>> of the specs.

    I'm not sure where you're getting this claim:

    "Those systems can have issues if the alignment is not done >>>>>>>>>>>>>>>> properly."

    I'm going to need some source for that, because (and don't >>>>>>>>>>>>>>>> take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To >>>>>>>>>>>>>>> simplify, if the
    steering sensor says the car is going straight, but it is >>>>>>>>>>>>>>> not going straight,
    the car senses a fault. If any sensor does not agree with >>>>>>>>>>>>>>> other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors...

    ...but that they also record the output of those sensors to >>>>>>>>>>>>>> be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the >>>>>>>>>>>>> alignment rack,
    it will throw it while driving after the alignment. It is not >>>>>>>>>>>>> dependent on
    recording the sensors. I have no idea if it has sensors >>>>>>>>>>>>> because i don't know
    what specific car we are talking about. What I do know is that >>>>>>>>>>>>> whenever I
    heard about that type of strict procedure, it tended to be a >>>>>>>>>>>>> car with all that
    driver assist stuff. For any car that doesn't have it, you >>>>>>>>>>>>> should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer >>>>>>>>>>>> and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in >>>>>>>>>> cars today, you need to get everything exactly right to minimize >>>>>>>>>> those
    pesky stability warning lights. If they come on, the dealer can play >>>>>>>>>> gotcha and say the alignment was not properly done. Then you pay. >>>>>>>>>> And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was >>>>>>>> not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about >>>>>>> reading the
    written word. If you take your car in for a warning light, many
    things can
    cause that.

    Except the indicators for stability systems are NOT "warning lights". >>>>>
    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that >>>>>>> is only one of the original possibilities. There is no trouble code >>>>>>> for an
    improper alignment. Did you stop learning about cars in 1975? Why >>>>>>> don't you
    start with Googling "do cars store antilock brake codes?" And then >>>>>>> go down
    your list and ask the same about the rest of your list. And then you >>>>>>> can come
    back and say, "oops", or you can just get ignored going forward. >>>>>>> It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars >>>>> "don't
    store codes" for a list of things, including ABS. Did you change your >>>>> mind?


    ...NOT when you simply brake hard enough that you cause the ABS to >>>>>> activate.

    An intelligent person always considers the possibility that he is
    wrong. So
    you either think you know everything when the polar opposite is true, >>>>> or you
    are a troll. You could have Googled all of this and found that
    everything you
    have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where >>>> to begin.

    Your thesis was (apparently) that if you got a fault code (which you
    didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance >>>> from ideal alignment no loading the car with the recommended weights
    would be...

    ...when compared to the tolerances that are permitted in the alignment >>>> value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight
    distribution. Assuming the position of the driver's centre of gravity is >>>> approximately at 48% of the wheelbase behind the front axle, then my
    weigh (about 195 lb) will be divided the same way between front and rear >>>> as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and
    with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by >>>> about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will >>>> change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce >>>> travel? Answer: almost zero. To be specific, the camber change per inch >>>> is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an
    acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#, >>>> when the driver drops into the seat, you'd increase by only a small
    fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.

    Shocking.

    I provide quantitative analysis of the issue you THOUGHT you understood... >>>
    ...and you have nothing to say.

    Everyone knows different things. No one knows everything, although you believe
    you do. What I have to say is based on not only master tech certs in ASE and >> all the GM lines, but also spending decades working in service departments of
    new car dealers, where I had - and used - direct access to the factory reps, >> engineers, and tech support. I know what they do on warranty claims, and
    plenty of it is absurd. I was trying to tell everyone how they think, and how
    they justify their positions. I would never bother putting weights in my own >> car to align it. I don't need all the tech spew above to know it would change
    nothing at all for my purposes. And yes, some forms of misalignment can set a
    code and warning light, in spite of your ridicule. Just look it up if you
    don't believe me. And again, if the car doesn't have all those new driver
    assist features, then of course it won't set a code. Do I really have to tell
    you that? Of course I do, because you simply cannot accept that you might be >> wrong about your stupid little arguments over nothing at all. You would argue
    that a misfire won't set a CEL, and then tell me that you drive a 55 Chevy. >> And the only reason I bother with this is that I have this enjoyment from
    making fun of ridiculous people.

    And yet you don't address a single factual point I just made...

    You say "look it up"...

    ...but won't provide a source.

    Illuminating.

    Because I am not your research assistant. I am not your trained monkey. I
    guess you don't use Google because you know everything it knows, right? LIke I said, people like you never learn anything. Answer one question. Have you ever said the words, "I didn't know that"?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,alt.os.linux,alt.satellite.gps,comp.lang.python,rec.autos.tech on Wed Nov 11 22:21:38 2026
    From Newsgroup: comp.lang.python

    On 2026-11-11 22:16, Bob West wrote:
    On Nov 11, 2026 at 11:07:02rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-11 21:59, Bob West wrote:
    On Nov 11, 2026 at 9:42:08rC>PM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-10 11:56, Alan wrote:
    On 2026-11-10 09:54, Bob West wrote:
    On Nov 10, 2026 at 2:00:39rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>
    On 2026-11-10 00:13, Bob West wrote:
    On Nov 10, 2026 at 1:00:23rC>AM CST, "Alan" <nuh-uh@nope.com> wrote: >>>>>>>>
    On 2026-11-09 23:57, Bob West wrote:
    On Nov 10, 2026 at 12:48:05rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:39, Bob West wrote:
    On Nov 10, 2026 at 12:34:32rC>AM CST, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-11-09 23:29, Bob West wrote:
    On Nov 9, 2026 at 11:37:29rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>> wrote:

    On 2026-11-09 22:20, Bob West wrote:
    On Nov 9, 2026 at 10:56:03rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>>> wrote:

    On 2026-11-09 21:50, Bob West wrote:
    On Nov 9, 2026 at 8:46:55rC>PM CST, "Alan" <nuh-uh@nope.com> >>>>>>>>>>>>>>>>>> wrote:


    Ummmmm...no.

    The difference between an alignment done with a driver's >>>>>>>>>>>>>>>>>>> worth of weight
    in the driver's seat and one done without will NOT change >>>>>>>>>>>>>>>>>>> whether or not
    the stability warning lights come on or not. >>>>>>>>>>>>>>>>>>>
    Furthermore, what gives you the idea that cars record the >>>>>>>>>>>>>>>>>>> number of
    times the stability augmentation systems have been >>>>>>>>>>>>>>>>>>> activated?

    I did a little checking and no current production vehicle >>>>>>>>>>>>>>>>>>> keeps a log of
    when the stability systems have been activated. >>>>>>>>>>>>>>>>>>

    Okay, I've been forever using "stability" loosely as an >>>>>>>>>>>>>>>>>> all encompassing term
    for driver assist systems - lane keep, emergency braking, >>>>>>>>>>>>>>>>>> self driving, and
    more that I can't think of right now. Those systems can >>>>>>>>>>>>>>>>>> have issues if the
    alignment is not done properly. Those weight procedures >>>>>>>>>>>>>>>>>> might make very little
    difference, but it might be enough to push it past the >>>>>>>>>>>>>>>>>> tipping point for error
    codes, like when the alignment is in spec, but at the edge >>>>>>>>>>>>>>>>>> of the specs.

    I'm not sure where you're getting this claim: >>>>>>>>>>>>>>>>>
    "Those systems can have issues if the alignment is not done >>>>>>>>>>>>>>>>> properly."

    I'm going to need some source for that, because (and don't >>>>>>>>>>>>>>>>> take this
    poorly) it sounds like complete nonsense.

    The cars have at minimum steering sensors and cameras. To >>>>>>>>>>>>>>>> simplify, if the
    steering sensor says the car is going straight, but it is >>>>>>>>>>>>>>>> not going straight,
    the car senses a fault. If any sensor does not agree with >>>>>>>>>>>>>>>> other sensors, you
    are going to get a trouble code.

    You're going pretty far afield here.

    You have show not only that they have sensors... >>>>>>>>>>>>>>>
    ...but that they also record the output of those sensors to >>>>>>>>>>>>>>> be review later.

    And they just don't.

    You misunderstand. The car is not going to throw a code on the >>>>>>>>>>>>>> alignment rack,
    it will throw it while driving after the alignment. It is not >>>>>>>>>>>>>> dependent on
    recording the sensors. I have no idea if it has sensors >>>>>>>>>>>>>> because i don't know
    what specific car we are talking about. What I do know is that >>>>>>>>>>>>>> whenever I
    heard about that type of strict procedure, it tended to be a >>>>>>>>>>>>>> car with all that
    driver assist stuff. For any car that doesn't have it, you >>>>>>>>>>>>>> should obviously
    ignore what I said.

    No, I don't misunderstand at all.

    Your claim was that this code would be seen by the manufacturer >>>>>>>>>>>>> and be
    used to deny a claim.

    But cars don't store codes for stability systems.

    Not for anti-lock braking.

    Not for traction control.

    Not for steering.

    And very few (if any) cars HAVE cameras.

    I want to say, huh? But now I smell trolling.

    Nope.

    I refer you to your earlier statement:

    'The other more important one is that with the driver assist tech in
    cars today, you need to get everything exactly right to minimize >>>>>>>>>>> those
    pesky stability warning lights. If they come on, the dealer can play
    gotcha and say the alignment was not properly done. Then you pay. >>>>>>>>>>> And
    it's a lot.'

    And it's simply not so.

    Google is your friend. I'm not your research assistant.

    How is that even responsive?

    You claimed that "the dealer" could discover that an "alignment was >>>>>>>>> not
    properly done" based on "stability warning lights".

    And it JUST ISN'T SO, dude.

    You clearly know very little about auto repair, and the same about >>>>>>>> reading the
    written word. If you take your car in for a warning light, many >>>>>>>> things can
    cause that.

    Except the indicators for stability systems are NOT "warning lights". >>>>>>
    Straight outta Lewis Carroll.


    If the dealer follows the diagnosis to an improper alignment, that >>>>>>>> is only one of the original possibilities. There is no trouble code >>>>>>>> for an
    improper alignment. Did you stop learning about cars in 1975? Why >>>>>>>> don't you
    start with Googling "do cars store antilock brake codes?" And then >>>>>>>> go down
    your list and ask the same about the rest of your list. And then you >>>>>>>> can come
    back and say, "oops", or you can just get ignored going forward. >>>>>>>> It's time for
    me to sleep now.

    They store codes when the ABS system has a FAILURE...

    Uh, if you look up a bit on this page, you can see that you said cars >>>>>> "don't
    store codes" for a list of things, including ABS. Did you change your >>>>>> mind?


    ...NOT when you simply brake hard enough that you cause the ABS to >>>>>>> activate.

    An intelligent person always considers the possibility that he is
    wrong. So
    you either think you know everything when the polar opposite is true, >>>>>> or you
    are a troll. You could have Googled all of this and found that
    everything you
    have said is wrong, but you didn't. I guess I'll be moving on.

    Wow.

    There is so much about this you don't understand it's hard to know where >>>>> to begin.

    Your thesis was (apparently) that if you got a fault code (which you >>>>> didn't articulate very well) that involved one of the vehicles
    "stability systems" that a minor variance in the vehicles alignment
    might result in the dealer denying coverage for the problem.

    And that's bullshit for some many reasons.

    But the biggest one is that you don't understand how minor the variance >>>>> from ideal alignment no loading the car with the recommended weights >>>>> would be...

    ...when compared to the tolerances that are permitted in the alignment >>>>> value.

    My 2012 BMW 135i weighs 3,373 lb with about a 52%/48% F/R weight
    distribution. Assuming the position of the driver's centre of gravity is >>>>> approximately at 48% of the wheelbase behind the front axle, then my >>>>> weigh (about 195 lb) will be divided the same way between front and rear >>>>> as the car's own distribution.

    So the empty weight on the front example empty would be 1,754 lb, and >>>>> with the driver, 1,855 lb. That's an increase of 5%.

    So assuming a linear wheel rate, that would decrease the ride height by >>>>> about 5%.

    The ground clearance of the 135i is about 4". So adding the driver will >>>>> change that by about 0.2"

    How much do you think the front tire camber changes with 0.2" of bounce >>>>> travel? Answer: almost zero. To be specific, the camber change per inch >>>>> is about 0.6 degrees, so the camber change would be 0.12-#.

    The alignment spec for a 2012 BMW 135i's front wheel camber has an
    acceptable range of +0.2-# to -0.5-#

    So assuming you even COULD set the camber to the minimum value of -0.5-#, >>>>> when the driver drops into the seat, you'd increase by only a small
    fraction.

    Caster: not affected materially by the driver's weight.

    Toe: not affected.

    Your whole thesis...

    ...is bullshit.

    Shocking.

    I provide quantitative analysis of the issue you THOUGHT you understood... >>>>
    ...and you have nothing to say.

    Everyone knows different things. No one knows everything, although you believe
    you do. What I have to say is based on not only master tech certs in ASE and
    all the GM lines, but also spending decades working in service departments of
    new car dealers, where I had - and used - direct access to the factory reps,
    engineers, and tech support. I know what they do on warranty claims, and >>> plenty of it is absurd. I was trying to tell everyone how they think, and how
    they justify their positions. I would never bother putting weights in my own
    car to align it. I don't need all the tech spew above to know it would change
    nothing at all for my purposes. And yes, some forms of misalignment can set a
    code and warning light, in spite of your ridicule. Just look it up if you >>> don't believe me. And again, if the car doesn't have all those new driver >>> assist features, then of course it won't set a code. Do I really have to tell
    you that? Of course I do, because you simply cannot accept that you might be
    wrong about your stupid little arguments over nothing at all. You would argue
    that a misfire won't set a CEL, and then tell me that you drive a 55 Chevy. >>> And the only reason I bother with this is that I have this enjoyment from >>> making fun of ridiculous people.

    And yet you don't address a single factual point I just made...

    You say "look it up"...

    ...but won't provide a source.

    Illuminating.

    Because I am not your research assistant. I am not your trained monkey. I guess you don't use Google because you know everything it knows, right? LIke I
    said, people like you never learn anything. Answer one question. Have you ever
    said the words, "I didn't know that"?

    Plenty of times.

    It's just that you haven't said anything that I don't know that's
    actually factual.

    YOU make claims: YOU provide the sources to back them up, Sunshine.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to alt.comp.os.windows-10,comp.lang.python,rec.autos.tech,alt.satellite.gps on Thu Nov 12 23:46:03 2026
    From Newsgroup: comp.lang.python

    Maria Sophia <mariasophia@comprehension.com> wrote:
    Chris wrote:
    OK. For the Angeles Crest Highway

    Is this a joke? Post a link.

    That particular roadway was suggested by "The Real Bev", Chris.

    Since I'm a well-educated engineer & scientist, everything I post is fully reproducible by anyone, since I provide the GPX files & the scripts.

    You provide the files in broken forms where simple options to share them usefully exist and I have provided to you. Why do you obstinately refuse to help people help you?

    <snip useless repetition>
    --- Synchronet 3.22a-Linux NewsLink 1.2