We’re actually two teams working towards one common goal: Bike for Brussels.
To ensure that the woes of cyclists in Brussels, who contend with motorists, trams, buses, and annoying traffic light intersections, are eased, imperative for them would be accurate and contextual travel information. This information must be presented nicely enough so people would actually want to use it. Most unique is that the visual step-by-step info presented via a web app. It constantly relates to cycling route signage (route code name and colour) in the real world.
So our two teams sort of worked together, especially after the Post-it® Revolution of July 2017, sometime in the second week. Instead of Brussels Mobility teams 1 and 2, we sort of just became the Bike for Brussels team, since work directly contributes to their campaign.
So as I was saying, our super-team is actually composed of two different sub-teams – aka division of labour:
- Brussels Mobility 1 team aka Bike for Brussels appdata team aka…
Just like how a real predator in the wild seeks out its prey with stealth and precision, our project (aka bike away data aka Brussels Mobility 1) seeks out menacing issues in OSM that could cause havoc to Brussels cyclists. So, that why we created our webtool, because the OSM data needs a bit of help to be even more reliable for everyone to use.
More precisely (without the animal of prey analogy), our project assists the OSM community perfectly map the regional bike routes of Brussels. Simple enough, eh, but if you want a more detailed explanation check out our ‘about’ webpage at oSoc17.github.io/rideaway-data
- The Brussels Mobility 2 team aka RideAway Bike for Brussels app team
Our project was closely coordinated with the Bike Away team. Their app uses OSM data, therefore it’s really important that the data source is virtually 100% correct and complete. They were enthusiastic to create a bike for people in Brussels to just ‘ride away’ on the right routes.
The Brussels regional network is special to the point that there’s many thousands of street signs that were specially dedicated to the regional cycling route. Each route has a code and there’s a colour scheme as well. However, not many people are aware of this network, and that’s why this app is really important. If you’re interested to learn more about the app, then check out routeplanner.bike.brussels/landing.
And during the whole time, it was only pitches, pitches, and more pitches…
During the last four weeks, we had a lot of ‘to the point’ presentations aka pitches that were met to persuade anyone listening. Even towards random people, who had absolutely background information about our work, we had to convince them that we have the most viable and efficient solution to the pressing problem of misguided OSM mappers and cyclists using app based on OSM data. We even had to pitch to the Minister of Brussels Mobility himself, and he seemed pretty impressed.
And now it’s D-Day
For the last day (aka D-Day), we wanted to go all out. First things first we wanted an actual cycling street sign. Any better way to convince our audience that we mean business? Then we made a lot of designs and even created an interactive routing game. It turned out cool, along with our booths.
So it all ends… well not really.
Even though #oSoc17 concludes today, our open data and coding project doesn’t. That’s the best thing of being involved with open projects since our work has the potential to persist and make a positive impact in the future, wherever someone wants to improve their city or community with our code.