Show HN: Rollin – Wheelchair accessibility scores for 56K+ locations (free API)(joinrollin.com)

6 pointsby thattechiedudevor 5 Monaten4 comments

Show HN: Rollin – Wheelchair accessibility scores for 56K+ locations (free API)

https://joinrollin.com/

Solo dev, Hudson Valley NY. I built ROLLIN because Google Maps gives wheelchair users a yes/no checkbox and calls it accessibility data.

  ROLLIN scores locations 0-100 across 6 features: wheelchair entry,
  accessible restroom, level entry, parking, wide aisles, elevator.
  Data pipeline pulls from OpenStreetMap, cross-references Google Places,
  and layers in community verification with a trust-weighted scoring system.

  Stack: Vanilla JS (no frameworks), Netlify serverless, Supabase/Postgres,
  Leaflet maps. ~56K locations across NY, CA, FL, MA, NJ, PA.

  Free to use, free API tier for developers. Paid tiers for
  higher volume and commercial use.

Ill be happy to answer any questions. :)

  https://joinrollin.com
  API docs: https://joinrollin.com/developers

4 comments

cjav_devvor 5 Monaten

Cool idea! The docs are a little out of sync with what I'm seeing in the responses. I created an OpenAPI spec and generated some SDKs! Here's the python one: https://github.com/stainless-commons/rollin-python

thattechiedudevor 5 Monaten

Thanks for checking it out! You're right — the docs need updating, we're fixing that now. The actual API responses are the source of truth (which it looks like you figured out). Really cool that you built the Python SDK — mind if we link to it from our developer docs as a community SDK? Happy to bump you to Developer tier if you want to keep building.Hit me up: [email protected]

turtlepurplevor 5 Monaten

This is awesome, I'm glad someone is using these tools to expand accessibility. Best wishes & endeavors : )

thattechiedudevor 5 Monaten

Thank you! Accessibility data shouldn't be a checkbox, there's so much more nuance that matters when you're actually trying to get through a door. Appreciate the kind words.