EVERYTHING HAPPENS SOMEWHERE… MULTIPLE TIMES

Presentation given at TDWG 2017 in Ottowa on lessons learnt from CARTO and GEO than can apply to TDWG

Transcript

1. Javier de la Torre CEO at CARTO jatorre@carto.com @jatorre EVERYTHING HAPPENS SOMEWHERE… MULTIPLE TIMES
2. TURNING LOCATION DATA INTO BUSINESS OUTCOMES C A R T
4. ABCD
8. THE STATUS OF DATA ACCESS ON THE WEB…
11. NO ONE IS HAPPY BECAUSE NO ONE GETS WHAT THEY WANT Wants to download data and use it in some other software More interested on the data behind it and the science that in the visuals. Looking at getting an answer to a particular question, not to perform an analysis Wants to understand the data and the decisions being made Scientist GIS User Decission maker General Public
16. FITNESS FOR PURPOSE CAN YOU MEASURE SUCCESS THINK ON THE USE CASE & END CUSTOMER LIKELY SAME SOLUTION WILL NOT WORK FOR ALL STAKEHOLDERS Are you designing and building a solution who gets the job done?
18. AN OPEN SOURCE LOCATION INTELLIGENCE PLATFORM The one-stop shop for developers to power location applications in their organization. CARTO Engine delivers rapid application deployment, with connectors to your data and APIs. ANALYZE VISUALIZE AUTOMATE DEPLOY C A R T
19. Since 2012. NYC/MADRID/DC Over 300,000 users. 130 employees around the world (most in EU/US)
23. More than 500 members
24. More than 200 formats
25. SOME IMPORTANT OGC STANDARDS Generating maps via URL. Created inside OGC WMS - Web Map Service Created at Google and adopted by OGC KML - The format for Google Earth A complex standard to express geographical features GML - The Geography Markup Language A language for SQL (or non) databases to represent geographic features SFA - Simple Feature Access
26. THE REALITY OF GEO TODAY… OGC: WMS, WFS, Geo-package, CityML… Official standards Web Tiles, JSON… Community standards
28. AN EXAMPLE WITH GML/WFS Similar to TAPIR and ABCD
29. Issues with GML/WFS And it is so hard to implement that still is not well supported It was designed and then implemented (90 pages!)… That it can be adapted in so many ways that software has to understand them on the fly, and most of the time it does not work Is so flexible… Is so strict… That the performance of the software implementing it is very poor
30. So what happened… GeoJSON and specific services now used widely… Lesson: Your community is not the center of the world
31. AN EXAMPLE WITH WMS
32. Issues with WMS It is not possible to cache. So is not possible to scale. Can not be put into CDN. A workaround was needed. So dynamic…
33. So what happened… Google Maps and OpenStreetMap Tiles now widely used Lesson: No standard without scaled implementation
34. SOME LESSONS LEARNT No standard with our reference implementation. Ensure it works technically and performantly. Not 90 pages documentation IMPLEMENT FIRST DONT STOP INNOVATON Ensure that standards are not stopping innovation at the software level or they will be ignored on the long term. Users will win on the long terms, listen to them and adapt or adopt quickly to serve them or you will be ignored. Do not provide too much power to a single organization STANDARDS WITH A FIT FOR PURPOSE Start with what you need to achieve with the standard LISTEN TO THE COMMUNITY LOOK OUTSIDE There are bigger communities out there. We are not the center of the world
35. Private & Confidential THANK YOU