Using open datasets in software for mutual benefit
For those using a RSS reader, subscribe here: rss.xml
Without a doubt, gathering data for an application can be one of the hardest tasks. Because let’s face it, your application is not done when you can demonstrate the functionality. That is the beginning, because the next phase is the adoption phase of your software.
I want to zoom in on the result of that phase, what does the adoption of your software mean to the outside world? If people start to use your software and improve the data it is using, is that it or does that improvement translate elsewhere? This is where open datasets come in. Once you dive into them you cannot go without them anymore.
Take an example like OpenStreetMap, and why projects like VeggieKarte use its data. This dataset provide a good starting point for that application, as it can query the supported food preference if it has been entered. When people improve the data inside of OpenStreetMap, your application benefits. And when your users improve the data and update further outdated information like opening hours and contact details, everyone else also benefits. Or when someones new favorite veggie restaurant opened, and it has not been registered yet, they register it for everyone to see on the map.
That is the natural strength of using open datasets, that all applications now using the dataset are improved. Once this ball is rolling, the collaborative power is immense. So take a good look at the software you use, and if they allow open contributions to the data they use. If you are out of luck, there is always Wikipedia that can use more edits.