1. Park Shark Amsterdam API
December 2012
“from APP to API”
Jonathan Carter
Glimworm IT
http://api.parkshark.nl
jc@glimworm.com
@jonathanrcarter

2. non geeks
leave the
room
now..

3. It started in September 2011 with a
Hackathon

4. Options!!!
time date duration location

5. What was different
● We added the“best guess” (“obvious dumbass”)
logic.
● What would be the #1 FAQ?
● How much in total will it cost and what is the
alternative?
● I don't want to know the details.

6. How did
we “best”
guess

7. Serendipity
● In 2011 I bought a horse & a car
● I needed to park near my house on the
weekend without a permit
● My house is near 3 zones with different tariffs
and hours and I DID NOT KNOW IT !!!
● I over paid for months but worked it out just
before the hackathon
● The data that I had already thought about was
presented in front of me

9. Why us?
● Almost nobody in the parking business parks..
● Locals mostly work out a way to get a parmit
● That leaves the tourists who don't visit the same
place often enough by car to notice

10. THEY THEY
KNOW DON'T
KNOW
stuff you know
but
YOU
KNOW nice.. they don't know
but
do you know that they don't know ??

11. What other
stuff don't we
know

12. Parking money
in amsterdam
is a tax

13. It does not
matter where
you pay

14. What
happened
next

15. ●
Invited to talk at a DIVV internal meeting
●
Invited to participate at open Data Cafe
●
Invitation to input to
Smart City SDK
●
Commercial work
for CITION

16. ●
We won APPS FOR NEDERLAND with
“Vistory”
●
Invited to present to policy committee in
den Hague about app making
●
Invited by the UK
embassy to events
for UK/NL creative
entrepreneurs

17. Our story
was listened
to

18. What's the
story to data
holders?

19. ●
Open Data is not necessarily useful data
– Manage expectations
– Pursue a tipping point
Developers
Data
Open Data

21. ●
About the data
– Make sure it is complete useable
– Write background information
– Actively ask the community for feedback
– Be prepared to improve the data
– Provide a contact person
– Real time is best, otherwise update regularly

22. ●
Use the language of the developer
– Provide some specifc challenges
– If possible use english as well as dutch
– Provide json
– Provide rest
– GEO : google maps not KML
– Understand who you are dealing with

23. ●
Especially consider the indie developer
– Make sure a creative mind can understand
the data
– Provide calculations and business rules
– Provide a way to contact you
– Don't force the developer to create a server
infrastructure

25. Progress

26. Open Data Cafe
March 2012

30. What did
we do..

31. THE API..

33. The API is sometimes the missing link
Politicians
open data City government
providers
ICT Independent
Department developer
community
Citizens

34. On websites and not just on
IPhones

35. What else does it do

36. Park Shark
Antwerp
API

39. api.parkshark.nl/getthebutton-
antwerp.html

40. Park Shark
Antwerp
APP

42. Questions
we are
asked

43. ● Will there be a secondary market of worth
billions?
● Politicians answer : yes
● Our answer : no, or not in the way they envisage

44. ● Are there common standards
● Answer from politicians : don't know
● Our answer : no

45. ● Will this become a problem
● Answer : yes

47. ● What is the endpoint
● Our answer : Government as a platform

48. ● What is the biggest threat
● Our answer : badly published data

49. What can we as
developers and
creatives do?

50. ● What do we really need?
● To Use the data
● To innovate
● To be creative
●
How can we help and inform
● Data owners
● Policy makers
●
Can we give a list of our priorities?

51. Who canyou turn to

52. Find the tipping point
Developers
Data
Open Data

53. Read our report

54. All of these
people
participated
in some way