Finds named trails near a point via the same free, keyless Overpass API BeachFinder already calls — MIP-0030 §4.2: OSM has global, uniformly-tagged trail coverage, unlike bathing-water data, so this is BeachFinder's pattern, not ImaScWaterQualityClient's per-region-scraper one.
Named highway=path/track ways within NearRadiusKm of a beach or a named lake, same-named segments merged into one Trail (MIP-0030 §8: OSM splits one trail into many ways).
Named highway=path/track ways within NearRadiusKm of a beach or a named lake, same-named segments merged into one Trail (MIP-0030 §8: OSM splits one trail into many ways).
nearby, degraded to no trails when Overpass fails (429 is its documented back-pressure): trails are enrichment on an already-complete result, so a failure must not discard the run.
nearby, degraded to no trails when Overpass fails (429 is its documented back-pressure): trails are enrichment on an already-complete result, so a failure must not discard the run.
How close a trail's geometry must come to a beach/lake anchor to count as "near" it — MIP-0030 §3/§8: matches MIP-0021's accessibility radius for consistency, not independently verified against user expectation (§8, §11 open question).
How close a trail's geometry must come to a beach/lake anchor to count as "near" it — MIP-0030 §3/§8: matches MIP-0021's accessibility radius for consistency, not independently verified against user expectation (§8, §11 open question).