After the great reception at FOSS4G, where we presented our CartoDB Developers Program, we’d like to show developers and companies what it entails to develop on top of the CartoDB Platform and why it’s the best place to develop and commercialize geospatial products. And what better way to demonstrate this than by inviting those developers who are already using CartoDB to do business to share their experiences using our product?
For this first post, welcome John Branigan from Azavea. Azavea is a CartoDB partner specialized in the creation of geographic web and mobile software, as well as geospatial analysis services to enhance decision-making. John has over 13 years of experience working in geographic information systems, database design and analysis, and web development and design, and has focused for the last two years on managing large-scale web application development projects.
I started working in GIS in an ESRI shop, so all of the Arc software is my background. I am comfortable with their desktop software as well as the web services and web servers. Today, I pretty much use QGIS, PostGIS, TileMill, and CartoDB.
So one potential workflow for a project would be to load my spatial data initially into a local PostGIS database. I do this because SQL is one of my preferred methods of understanding a dataset (sometimes I go straight to CartoDB). I can load this directly into QGIS for basic visualization. If there are auxiliary attribute tables, I can ask questions in PostGIS to discover interesting trends and relationships among the data. I may or may not use TileMill to play with cartographic styling - the CartoCSS can be directly transferred to CartoDB, which is great. All of the aforementioned tools are available even without an internet connection, which can be convenient.
Once my data is prepped, and the story I want to tell is structured, I load the data into CartoDB and configure everything to be ready to share. Then it’s either published directly from CartoDB, or more likely, incorporated into a web application using the CartoDB.js or Leaflet.js library.
Having the option to use CartoDB as a PostGIS-enabled data store is incredibly valuable. Spinning up and maintaining my own database server is unnecessary now, and this accelerates project development cycles significantly. I’m also relying quite a bit on the APIs for pulling data into my apps.
A hosted, open source, spatial database. Save (at least) days of DevOps.
CartoDB.js - This is a great way to integrate data stored on CartoDB with a lightweight JS mapping library. Leaflet has been my go-to for years, and CartoDB.js provides a lot of freebies in the way it can load preconfigured visualizations in just a few lines, and wrap API requests in predefined functions.
CartoCSS and styling wizards - I’ve spent a lot of time doing cartography in desktop software. My maps look better more quickly using CartoDB - especially with the different styles available in the interface (and Torque!). I also love how the CartoCSS gets updated - I usually will set things up close to how I want them, then tweak the CSS until it’s just right.
We thank John and Azavea for taking the time to share his experiences with CartoDB. If you are interested in creating geospatial products using the CartoDB platform, take a look at this intro presentation: [CartoDB for Developers].
If you are already developing geospatial products using CartoDB, take a look at our Developers Program, and stay tuned for more developer interviews. And if you’d like to share your experiences, please write to firstname.lastname@example.org.
Today we are excited to announce the general availability of CARTO for Retail, a cloud native analytics platform designed specifically for Retailers.News
Please fill out the below form and we'll be in touch real soon.