Walk Score and Bike Score exist; nothing scores whether an adult tricycle can get around a place, and trikes fail differently than bikes — can't hop curbs, grade-sensitive, and wind is a real routing constraint (a slope with the wind at your back vs. against it can flip from ridable to not). I hand-mapped my own trike routes in Ilhéus, Brazil into OpenStreetMap with the relevant tags (kerb type, incline, segregation) and rendered them via CyclOSM. No scoring algorithm yet — this is just proving the mapping method works. trikescore.com
The distinction that trikes fail differently than bikes is what caught my attention.
From the people who've looked at this so far, are they mainly validating that the mapping captures the constraints they actually experience, or are they already asking for the scoring layer before they're convinced the underlying map is complete?
The wind detail is what makes this interesting. Most accessibility scoring treats terrain as static, but wind direction changes through the day, so a route that is fine at 8am could be miserable at 2pm. Are you planning to eventually pull live wind data into the score, or is this meant to stay a one time proof of the mapping method for now. Hand tagging kerb type and incline in OSM for your own routes first, before trying to scale it, seems like the right order to build this in.