The Parking Fairy Using open data effectively in mobile apps.
Background • December 2015: Proposed ‘Parking Space Alert’ for Data Movement Competition • February 2016: Became one of 3 finalist apps in Data Movement • 9th May 2016: The Parking Fairy launched (iOS Only) • 14th May 2016: Android version launched (after user requests - including from local MP Chi Onwurah)
Architecture iOS App Android App t h n t e t i p l s n c v o w e REST API i h i r t t t i i a f h c w i c i c l f a s i t i p i e t r n o e t t n v h https with API key NECA API
Node.js REST API performs parsing, ‘data set matching’, sorting and caching.
Datasets & APIs Uses both ‘static’ and ‘dynamic’ car park APIs from the NECA’s netraveldata.co.uk service. https://www.netraveldata.co.uk/api/v2/carpark/static https://www.netraveldata.co.uk/api/v2/carpark/dynamic (both have relatively friendly JSON responses)
Static API provides car park names, addresses & geolocations. Dynamic API provides live spaces data.
Live space data currently only available for indoor car parks in Newcastle & Gateshead Quays. Sunderland ‘coming soon’.
Static API polled once a day. Dynamic API polled on every request for live info (assuming a cache miss).
Data Quality Generally, very good * . (*some legwork required).
Documentation Quality Not so much*. (*virtually non-existent).
No docs? No problem!
Get a good HTTP API client and spend some time toying with the APIs. (I’d recommend Postman )
Car parks match between APIs on systemCodeNumber
Be considerate - add caching! ( node-cache is awesome for Node.js)
Play with the data. Make it useful. Have fun.
What next? Where next?
The Parking Fairy @parkingfairyapp info@parkingfairyapp.com www.parkingfairyapp.com
Recommend
More recommend
