cmdalbem/ciclomapa
cmdalbem/ciclomapa has 91 GitHub stars and 11 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-18 11:16 UTC. Last push 2026-11-17.
What you can do
- Easily visualize the different kinds of cycling structure of any brazilian city. We simplified all the technical details of OSM so everyone can understand it.
- Learn about what are the main types of cycling structures you can find around. Semantic colors help you remember that some are better than others.
- Download the GeoJSON data with a single button click so you can import in your favorite GIS application and power up your research analysis.
- Found something wrong? A direct link will take you to the OSM web editor so you can fix it and contribute.
Measured star growth
- in 24h
- 0
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Beautiful, interactive & open bike maps of Brazilian cities. Powered by OpenStreetMap.
Web & AppsREADME.md
Original
CicloMapa
An open platform to democratize access to bike maps of brazilian cities, combining the collaborative power of OpenStreetMap with web technologies and easy-to-use design.
Today in Brazil we face a big challenge of not having data on the cycling infrastructure available in our cities. This makes it very hard to paint a clear picture of our reality and calculate the relevant metrics to measure the opportunities and impacts to society of improving urban mobility. The most common problems are data not being standardized, making it hard to compare between localities, data not being available publicly or sometimes it not existing at all.
UCB (Brazil Cyclists Union) and ITDP (Transport and Development Policy Institute) are two civil society organizations that have joined forces to solve once and for all the problem of access to data on Brazil's cycling infrastructure.
We've developed the first cycling maps platform encompassing all Brazilian cities, leveraging the data and collaborativity of OpenStreetMap (OSM), the biggest initiative of this kind. We've created an open-source web application, free and accessible from any computer or smartphone, aimed at both the average citizen who wants to know more about their city, and researchers, who will have easy access to data without needing OSM knowledge.
🎓 UCB website with more useful links and tutorials on OSM
Main features
- Easily visualize the different kinds of cycling structure of any brazilian city. We simplified all the technical details of OSM so everyone can understand it.
- Learn about what are the main types of cycling structures you can find around. Semantic colors help you remember that some are better than others.
- Download the GeoJSON data with a single button click so you can import in your favorite GIS application and power up your research analysis.
- Found something wrong? A direct link will take you to the OSM web editor so you can fix it and contribute.
Architecture
The basic premise is that the OSM Overpass API is very slow and we couldn't hit it directly without damaging a lot the user experience. However, differently than other similar projects, we didn't want to have data stuck in time, since we want contributors to be continually improving the data.
We store a mirror of the OSM data in a Firebase Database. Any user (possibly an OSM contributor) can manually update this data, which will automatically update the Database.

Getting started
Requirements: Node 22.x (see engines in package.json).
This project was bootstrapped with Create React App, so if you're familiar with the tool you already know all these commands.
Environment variables
Create a .env file in the project root (or set these in your environment) for the app to work fully:
REACT_APP_SENTRY_DSN— Sentry error reporting (also required on Vercel; CRA bakes it in at build time)SENTRY_AUTH_TOKEN/SENTRY_ORG/SENTRY_PROJECT— build-time source map upload (Vercel only; notREACT_APP_, so they stay out of the bundle)REACT_APP_MAPBOX_ACCESS_TOKEN— Mapbox map tiles and geocodingREACT_APP_OPENROUTESERVICE_API_KEY— Route calculations (OpenRouteService)REACT_APP_GOOGLE_PLACES_API_KEY— Place autocomplete in the directions panel (optional)REACT_APP_PMTILES_URL/REACT_APP_PMTILES_FILENAME— Vector tile archive served from S3 (see.env.example)AIRTABLE_API_KEY/AIRTABLE_BASE_ID— server-only, used by/api/airtable/*Vercel Functions. NeverREACT_APP_. CRA inlines everyREACT_APP_*variable that is still in.env, even if unused. For local comments/metadata, runyarn dev:vercel. After the first deploy, revoke any token that used to be inREACT_APP_AIRTABLE_API_KEY.
PMtiles data pipeline
Generation already lives in scripts/:
scripts/overpass-to-geojson.js— fetch one area from Overpass → GeoJSON (yarn overpass -- --area "Brazil")scripts/generate-pmtiles.js— combine multiple areas into one.pmtilesvia tippecanoe (yarn generate-pmtiles -- --areas "Brazil" --output br.pmtiles). Pass--exclude-layers(orexcludeLayersinpmtiles-builds.json) to omit specific layers.
To batch the main regional builds and upload to S3, use the thin wrapper on top of those scripts:
yarn pmtiles:list # show regional builds (scripts/pmtiles-builds.json)
yarn pmtiles:sync:dry-run # preview generate + upload steps
yarn pmtiles:sync --build brazil-poi # runs generate-pmtiles for Brazil, then uploads to S3
Or generate locally without S3:
yarn generate-pmtiles -- --areas "Latin America,es_pt" --output la_es_pt.pmtiles
For S3 upload from CI, set AWS secrets and run .github/workflows/pmtiles.yml. See .env.example for AWS_* and optional CICLOMAPA_FROM. Each sync run prints a before/after report (S3 vs new build) and saves JSON under .pmtiles-work/reports/.
To clone the repository and install everything:
git clone [email protected]:cmdalbem/ciclomapa.git
cd ciclomapa
yarn install
Using
To start the local server:
yarn start
Comments and city metadata go through Vercel Functions (/api/airtable/*). For those locally, use yarn dev:vercel with AIRTABLE_API_KEY and AIRTABLE_BASE_ID in .env. vercel.json points that at yarn start (CRACO). If Vercel falls back to react-scripts start, Less never compiles and the UI looks broken. Plain yarn start still runs the SPA, but those API routes 404.
Production is on Vercel, which is what serves /api/airtable/*. Push to the connected branch or deploy with the Vercel CLI/dashboard, and set AIRTABLE_API_KEY / AIRTABLE_BASE_ID there (Production and Preview).
yarn deploy still publishes the static build/ folder to GitHub Pages, but that host cannot run the API routes, so comments and city metadata will 404 on a Pages-only deploy.
Contributing
We're using GitHub Issues for our backlog. Feel free to take a look around and choose the task you want. Use the tags at your advantage:
complexitytags tell you how difficult a task probably is.good first issueis the perfect place to start if you're new to the project, or to coding itself.help wantedare issues where external help is currently more needed.
Run yarn test before committing to ensure you don't introduce regressions.
Design & UI
For styling conventions, design tokens, and the BEM pilot, see docs/styling.md. The source layout is described in docs/structure.md. How cities, areas and the slug catalog relate is in docs/cities.md.
Contact
License
The source code is available under a GPLv3 license.
Data is directly imported from OpenStreetMap® and thus is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF).