Nicole was interviewed for GeoHipster by Mike Dolbow.
Q: You and I met at State of the Map US in Minneapolis this past fall. Did you enjoy the conference and your trip to Minnesota?
A: Yeah, we met at the cool kid table with Ana Leticia Ma, I think. Loved the conference, but still can’t believe there weren’t more people there. We’re talking about maps, after all, not some arcane tech.
Rant aside, there are three sessions I keep sending people links to:
Mapping Prejudice: Next time you want to show someone how redlining works and why it matters
Q: Tell our readers how you got into mapping, GIS, and/or OSM.
A: I was looking to do more with data journalism, and the first awkward project I took on involved scraping Craigslist to figure out where and when people most often got parted with their iPhones. Usually, when I’m trying to learn something, I like to layer different aspects of it, so I went out in the field as a GIS volunteer at the San Francisco Botanical gardens, waving the Trimble around in the misty fog. And from there, MOOCs, a GIS certificate and a lot of trial and error. I still think (and work) way more like a journalist than someone with a traditional GIS background, for better but often worse.
Q: How was the idea of Resiliency Maps inspired?
A: The map you need but don’t have is probably the most compelling one to make, right? A couple of years ago, I moved to South of Market, a part of San Francisco that I’d never lived in and didn’t know that well.
I’d recently renewed my Neighborhood Emergency Response Team (yes, NERT!) training so all the teaching about how to spot soft-story buildings and potential hazards was fresh in my mind. I realized that I had no idea where to go and how to get there if an earthquake hit. The map in my go-bag was from the tourist board. At the time, it wasn’t to scale and didn’t cover the whole city!
The basic idea is to create a neighborhood map, built with all open-source tools, that can be downloaded, used offline and printed for emergency prep. It shows assets and hazards, so you can navigate your surroundings safely.
I’ve volunteered and worked in open source and felt strongly that OpenStreetMap and open-source tools were the way forward. My first approach to OSM was a mapathon after the 2015 Nepal earthquake, so I knew how powerful it is post-disaster. But talking to people, some skepticism bubbled up about how easy OSM was to use, “were there mobile apps?”, “could you use paper?”, things like that.
I wrote a tutorial for every question people had to show that it was viable, and then thought, “Wait, I should do something with this.”
Q: What do potential users need to know about it?
We’re still in the early stages and looking for contributors, especially cartographers with OSM knowledge. The next step for Resiliency Maps (RM) is to create a template to represent the most common features necessary during an emergency. We have some promising visualizations already but we’d love to get more tests and more communities to try them and give us feedback.
Q: You grew up in the Bay Area, right? Does that factor into your interest in maps?
A: Disaster maps, for sure. I’ve spent about half my life in San Francisco, the other half in Italy. Both places are pretty complicated, seismically, so it’s always hovering in the background. This old Red Cross poster comes to mind:
Or maybe it’s the disaster mentality that travels with you? In any case, the differences in approach to preparedness in the two countries is fascinating.
The Civil Protection in Tuscany developed a free app (with OSM as basemap!) to show you where to go in a flood or landslide for the entire region. It shows things like which school might serve as a shelter and what its amenities are (number of beds, showers, defibrillator, etc.) and whether the building is suitable for shelter in an earthquake.
The app pushes weather alerts and will eventually have a navigation feature to route you while avoiding hazards like flood-prone underpasses. The datasets are available in an open data portal, too. We don’t have free, public resources like that for San Francisco, let alone regionally.
However, I’ve convinced exactly none of my friends or relatives in Italy to get a go-bag together. Outside the capillary network of Civil Protection volunteers and local associations, the average Italian feels much less impetus to prepare. There’s a faint superstition that preparing somehow invites disaster?
Q: Tell me about your latest adventure, becoming a licensed Ham radio operator.
A: Getting the HAM license early in 2019 felt like crossing some kind of nerd Rubicon, but I did it because in a disaster the tech we use everyday can’t be trusted to see us through.
It’s late 19th-century tech that still plays a powerful role, because when everything else fails you have a dedicated network of FCC-licensed volunteers who come to the rescue. During 9/11, the Amateur Radio Service kept New York City agencies in touch after their command center was destroyed, and it was also used in Hurricane Katrina, etc.
You hear of folks managing to use WhatsApp or messenger or similar during an event, but you can’t count on that. Redundancy matters!
Q: It’s possible that you’re a geohipster. What would you say the chances are?
A: Mmmm. Very low. Unless it’s more about shunning hoodies than the maps you make? What we’re doing at RM is deeply uncool, and I haven’t gotten over the embarrassment of being a San Francisco native promoting downloaded, static and/or paper maps. It’s so retro! And not in a hip-to-be-square kind of way.
We recently produced three neighborhood maps for NERT that work in 11×17 and larger formats using QGIS. What sold them on the maps was that they were really, really simple: building outlines, street names, fire stations and battalion boundaries. (The battalions are the only fire stations in a neighborhood open after a major event.) And they have to work in black and white. That’s it! The neighborhood NERTS now have a tool that they can mark up however they want, use for planning and also post-event.
Making maps that simple is harder than it looks, as you’d probably expect. Also, print maps are an unruly beast. But that doesn’t make it geo hip, for sure.
A: The secret to a good risotto: Mantecare. It’s an Italian verb that’s basically only ever used to remind you to fold in grated parmesan and generous dollops of butter right before serving. It’s the difference between novice and maestro in terms of the result, but can’t be more idiot-proof to pull off.
Frankly, I’m too new to GIS to offer any pearls of wisdom in that area.
Hello GeoHipster fans! It’s Mike D. here, checking in from Minnesota. Whether it’s hot or cold here, I like to think of this photo Jason Benedict shared with us via Twitter! I’m always excited to see our stickers making their way around the world.
But enough about the weather! In case you missed it in our post this past weekend, we’ve officially migrated all of our content here to this brand-spanking new WordPress site, complete with a new header image, mobile-friendlier design, and a spiffy SSL cert that hopefully keeps your network admins from blocking us.
Why now? Well, when I incorporated GeoHipster as an independent business back in 2017, the “OG” Atanas Entchev transferred most of the GeoHipster assets and operational responsibilities to me. One of the things that was left behind was the WordPress site he started (way back in 2013!) on the geohipster.com domain. To be frank, I just wasn’t ready to take over that part of the GeoHipster enterprise.
But now that I’ve got a few good years under my belt running the business, it seemed like the right time to make a transfer. Atanas and I have settled into our respective roles along with chief designer Jonah Adkins, and we’ve got all kinds of ways for you to support our work, including of course our 2020 Calendar. And we’ll continue publishing long-form, in-depth interviews with the most interesting characters in the geospatial world. To me, it’s amazing to see how far we’ve come since late 2013, when Will Skora transferred the @geohipster Twitter account to Atanas and Glenn Latham suggested the poll about what defines the GeoHipster.
We hope you like our new design and the benefits that come along with it! See you out there in the interwebs, or on Null Island…
On December 7, 2013, the “OG” Atanas Entchev posted a poll on geohipster.com entitled “What defines the GeoHipster?” Little did he know at the time that he would be launching a movement (or something) that would be filled with hundreds of interviews, opinion pieces, stickers, calendars, and t-shirts. Well, six years in, we’re still going strong, with more volunteers, a brand new 2020 calendar, and now, this newly designed website. So what better way to celebrate our six-year anniversary than with a reboot of the poll that started it all?
On November 26th, we at GeoHipster were informed of a dispute regarding potentially incomplete credits for one of the maps in our 2020 calendar. In the following days, we entered into discussions with the involved parties in an attempt to reach a satisfactory resolution. As a result of these discussions, on December 2nd we created a Second Edition of the 2020 calendar by substituting a map from Miguel Marques. Miguel’s map ranked highly among the original submissions, and will be included in all calendars ordered after our update. The Second Edition also includes an updated cover with Miguel’s name listed among the authors.
Please join us in congratulating Miguel for becoming part of this amazing product!
Let us here at GeoHipster be some of the first to wish all of you GeoJSON lovers out there a happy #PostGIS Day, just in case you don’t have our 2019 calendar to give you a handy reminder. And this year, we’ve actually had our act together well enough to be able to release our 2020 calendar to mark the occasion!
If you absolutely can’t wait to get your own, the button above will take you to the calendar on Lulu. (Order by December 10 in the US if you want it by Christmas with regular shipping.) But, some of you are also wondering who the lucky map authors are! So without further ado, here are the amazing cartographers that have been selected for our 2020 calendar:
Greg Fiske – featured on the cover (preview above)
Congratulations to all the map authors! And, special thanks to everyone who submitted a map for our competition; you all made the voting very difficult! We’d also like to thank Bill Dollins for leading the charge on this effort, Jonah Adkins for the finishing touches, our Editorial Board for judging, and this year’s guest judges: Eben Dennis, Daniel Huffman, and Sophia Parafina.
Hello GeoHipster fans, cartographers, and map geeks around the world! While we’ve put out teasers over the last few weeks, today we’re making it official: we’ve set a deadline of October 25 for you to submit your map for the 2020 GeoHipster Calendar. We’re trying to move a bit quicker this year so we can have the calendar ready to order for Black Friday. But 10/25 is over a month away, so we know you’re all going to get us some amazing maps to consider!
David Haynes II is an Assistant Professor with the Institute for Health Informatics at University of Minnesota-Twin Cities, and a health geographer who uses cutting-edge spatial analysis methods to advance knowledge of health and cancer disparities.
David was interviewed for GeoHipster by Mike Dolbow.
Q: You got your undergrad degree in Biology, then a Master’s in GIS shortly after. I’ve met people who have taken all kinds of different roads to discover GIS, but I think a biology degree is a new one. So tell our readers, how did you get started in geospatial?
A: I went to a small liberal arts college in Cedar Rapids, Iowa, (Coe College). When I originally went to school I thought I was going to be a medical doctor, so I took a lot of biology courses. I was generally interested in human and environmental biology. It was in an environmental biology course that a professor offered me a summer research position. She had heard that I was good with computers and needed some help analyzing GPS locations. That was my first real experience with “GIS and Geography”. We were running Arc 3.1 and I started playing with AML / Avenue. It was a very cool experience and led to me going to St. Mary’s in Winona, MN for my master’s in GIS.
Q: You and I crossed paths by working with some mutual colleagues in the Health disciplines. We both know that where someone lives, commutes, and works can have huge impacts on their health, but sometimes I’ve found the area to be relatively slow to adopt spatial technologies. Have you found the same, and if so, do you feel like you’re constantly selling the business case?
A: So the medical field like every field goes in waves. 20+ years ago there was the idea of the environment being a factor for causing negative health outcomes. However, GIS was just at its beginning for the broader community and much of that literature showed that the scale of analysis was critical for determining that. So health went away from that to personal behaviors and thinking that was the main cause. We are at a point now, we know that if we control for many of these personal demographic characteristics (age, race, sex), we still see large gaps or disparities. We hypothesize that the environment could explain the disparities. However, the environment now needs to be more specifically defined which is causing a headache for everyone. Most researchers approach this from the traditional epi point of view and try to add spatial on at the end. So I spend much of my time on studies that want to add spatial to them. Not many studies start with spatial as the primary focus.
Q: It does seem like the field of ‘health geography’ is growing. Can you tell us what it’s like, in your experience?
A: Yes, I think the ability to use smart devices is going to make Geography extremely important in designing interventions. I am thinking of designing a study for smoking cessation that would send you SMS notifications if you are in a business that sells tobacco.
Q: How would you describe “health geo-informatics”? Is this just another way to say spatial (or GIS)?
A: Yeah, pretty much. I think my focus is to make health spatial and to integrate more sophisticated spatial analyses that most researchers wouldn’t.
Q: You were once a rugby player. I don’t know much about the sport, but it appears to me to be a lot like soccer and American football: where an awareness of space, angles, and boundaries is an advantage. Did you ever think of it like that? Ever map your games?
A: Funny, Yes. I want to teach a class one day call the “Geography of Sport”. Actually all sports are about Geography. You have a limited defined extent in which you have to operate. In many classic team sports (i.e., football, basketball, hockey, etc.), the goal for the defense is to limit the space and time for different players. If a QB is throwing the football they need time and the receivers make the pass easier by creating distance between themselves and the defenders. Staying with football, every defense seeks to limit potential areas of the field while leaving other areas open. The offense tries to exploit these areas. I could go on all day about this as I really enjoy watching sports from a geographic perspective. One last thing, this is why the prevent defense in football gets no credit. The prevent defense is to prevent a touchdown on the hail mary pass not prevent the Tom Brady 5-10 yard passes. Defensive Coordinators need to develop new defenses that use a mixture of man to man with zone to be more effective in the 2 minutes offense.
Q: In Minnesota, we have a saying that there are only two seasons: winter, and construction. But you’re into aquaponics and sustainable gardening. Isn’t there a gardening analogy to that, like, “weeding and canning”?
A: Yeah, aquaponics is a labor of annoyance. It always starts out great and then something breaks two weeks later. But mostly I’m dreaming farmer. I read the book “5 Acres & a Dream” and was hooked. One day, that’s what I want to do. I’d be more of a hobby farmer in the day and do some serious programming at night.
Q: What do you think of some of the indoor, urban, industrial agriculture systems that are cropping up, sometimes as CSAs? Given the rising environmental costs of shipping, and unpredictable climate we’re facing, this seems to me like something we need to invest in more as a society. But can aquaponics really save the world?
A: Realistically, I think it’s a part of the solution. It won’t save the world, but it would improve some things like the food supply chain. Every year there are 10 e-coli outbreaks related to vegetables. This isn’t going to change. But this might be an area where aquaponics could help. I have grand ideas of how aquaponics could be used to provide benefits to society. Mostly, I do it to help my kids understand where food comes from and what waste is. I like aquaponics because it recycles the water and is kind of a closed-loop system, although I feed the fish. But I think getting people familiar with the idea of how an ideal nature system could operate would help us. It is an opportunity to learn more about ecosystems and how plants, animals, and people can all interact in a sustainable way.
Q: I’m not sure how much you know about GeoHipster, but you’re a big PostGIS user in a nascent field – which makes you different than a lot of people I know, but more like some of the “geohipsters” I’ve met. So what do you think, might you be a geohipster?
A: After re-reading your definition, I would definitely be a geohipster. Geography and using GIS in the broader health world isn’t new, but it is really in demand right now and this trend will likely continue for at least 5-10 years. I’d also say, like many of the geohipsters you have interviewed that I am a big advocate for spatial and try to help people understand why spatial is important.
I’d say I’m a big spatial database advocate. I tend to use a variety of tools that fit the need of the project. Which I think is the mantra of your GeoHipster definition poll. I think industries and the medical world tend to be OK with the installation of a validated commercial software. However, that can take weeks or months. They always seem to have a database around and if you can move data into that they seem to roll with it. Databases just seem safe. Plus I think the ability to scale analyses out in databases is easier than programming. But you need to know how to program if you’re working with big data.
Q: You’ve got a year or more of teaching under your belt. What career advice would you give to your students – or to our readers?
A: If you are into Geography that is great, and if you are just coming into GIS I feel sorry and excited for you. The GIS field is really changing, which can be daunting at first. When I came into Geography there was a general feeling that you could learn ArcGIS and get a job. You could learn a second proprietary software and be set for life. Programming was something you could do, but wasn’t necessary. That has all changed for me and any future students.
Google Maps, MapBox, OpenStreet Map, Uber, Lyft. etc have all changed this. We are truly embracing the big data and computational science revolution. This means that you need to have mid-level understanding of computer science. You need to know how to program in an Object Oriented Language for either front end or back end. I would tend to recommend students or new people to the field to learn the back-end over the front-end. Because there are a million web designers out there that can make a map better than you. They won’t know what they are doing. They won’t know what a coordinate system is and how it matters, but they can stick it together fast. The benefit of the back-end is that you will be viable forever if you apply your spatial analysis skill within a programming framework. Be flexible and adaptable to the programming platform. I write code in R, Python, SQL (PostGIS) and Scala. Some language may be your favorite, but keep your eyes open. One resource, I’ll point people to is Packt. They have a lot of good books that I’ve purchased online.
Chris Whong is an NYC-based civic hacker, urbanist, mapmaker, and data junkie. He most recently worked as the founder and director of NYC Planning Labs, promoting the use of agile methods, human-centered design, and open technology to build impactful tools at the NYC Department of City Planning. He’s perpetually tinkering with open source geospatial technology, open data, and web projects, sharing his work via tweets, blog posts and speaking events. He teaches graduate level technology courses for Urban Planners at NYU’s Wagner School of Public Service, promoting the use of open source tools for mapping, data analysis, and visualization.
Chris was interviewed for GeoHipster by Mike Dolbow.
Q: Whong’s law states that “Every government agency, everywhere is working on a ‘new system’; It will solve all of their data problems and will be ready to use in 18-24 months.” My 20+ years in government have taught me that you’re 100% right on this, and I can’t believe I didn’t think of it myself. Please tell me this will be the subject of your first TED talk.
A: I actually came up with this a few years ago when I was in sales, and was speaking to different state and local governments several times a week. There was always a huge amount of faith everyone had that the “new system” would solve all of their data woes in the near future, but it never seemed to actually arrive. I’d love to do more research on this front, as every government technologist I’ve encountered has some version of this story for “new systems” large and small.
Q: Even after all the gigantic government IT failures, I still can’t believe how many ginormous contracts I see being awarded. (Despite their past success, I’m still looking at this $26 million award with side eye.) But they can’t all be failures, right? Maybe just the billion dollar ones?
A: I think the ones you hear about are the BIG ones… there are probably hundreds of little ones that are just as bad but not big enough to show up on anyone’s radar. There has been some reporting recently in NYC about ballooning construction costs for what should be simple projects like park restrooms. I think you’ll find a lot of the same incentives and poor practices at play in both construction and IT projects. My hunch is that it’s the bigness of NYC that allows for these kinds of things to slip through the cracks. A $14M bathroom is peanuts in a $11B capital budget… and you can’t really inspect that budget unless you’re willing to slog through hundreds of pages of screen printouts published as a PDF.
Q: You recently left your post at NYC Planning Labs. What was your favorite project to work on in that job?
A: That would be ZAP Search. It’s a frontend search tool for looking up information on land use applications in NYC. Basically, anyone who wants to change zoning (including the city) has to go through a governmental process, and there’s an information system that tracks each action. I love this project because we were able to seamlessly integrate spatial data into a non-spatial database. You and I know it’s just a simple join to add geometries to a row in a table, but this has eluded everyone and been a huge excuse for years. In government, spatial is still the realm of “GIS people”, who tend to not be the same thing as app developers.
When you’re dealing with a city that’s the size of New York, the map becomes a critical part of the search UI for making individual projects discoverable. Adding geometries and displaying them on a map goes a long way towards making the data instantly relatable to people. Nobody knows obscure project names or even addresses of things being built near them, but everyone knows where they live and can relate to things happening nearby.
I should add that the GeoSearch API comes in at a close second. (GeoSearch is the autocomplete geocoder API that powers address search in all of our apps) We didn’t even build it, the heavy lift for us was transforming the city’s official address database into a format that would work with the Open Source Pelias geocoder built at Mapzen. It’s a wonderful open source story, and I like to think a contract to build a highly-available autocomplete geocoder in government would have taken years and millions of dollars. We did it in a few weeks, basically for free, by leveraging open source. We also made it publicly available and wrote a nice little documentation site to help people get started using it.
Q: Can you tell us what’s coming next for you? And whether or not you’ll need to add a corollary to Whong’s law?
A: I’m planning to write a book about my 3-year stint in local government (but I know I’ll just get consumed with side projects during my time off!) I want it to be a relatable easy read full of anecdotes and things I’ve learned being a solo open source developer and building a small (but highly effective) digital team. I’ve accepted a position at Qri (qri.io), an open source startup building technology for distributed data collaboration, discovery, and version control. It touches on a lot of the pain points I’ve experienced working with, publishing, and sharing data over the years. I’ll be exploring use cases, building tooling around the core platform, and trying to grow the Qri user community.
Q: Do you think every government organization needs “an 18F” to show the way towards better IT, better user experiences, better designs in government apps?
A: Yes, and it’s important to remember that the culture change is the most important thing these teams bring. The tech tooling is just a fraction of the overall environment. Openness, collaboration, good design practices, continuous learning, introspection/retrospection, sharing, focusing on the user, iterating and shipping code continuously, etc. are what lead to better products. These things require culture change way beyond just saying “use open source software”.
I’ve also described all of the above characteristics as values that are at odds with the way government is usually structured when it comes to tech delivery.
It’s important to think about the long-term sustainability of these progressive values. How do you get them out of the 18F-style team and into the regular standing operating procedure of an agency? How to you make the myriad controls and requirements codified into tech policy support this new way of working? These are things I didn’t stick around NYC Planning Labs long enough to tackle, but they remain issues that my former colleagues are faced with every day.
Q: Have you always been a New Yorker? What do you like – or dislike – about the city?
A: I came here in 2011 to study Urban Planning at NYU. Someone once told me that it takes 7 years to finally call yourself a New Yorker, so I guess I’ve passed that milestone. I always say that once I started getting involved in civic tech, I began bumping into the same people at meetups and events all over the city, and found “my scene”. After that, the big, busy, hectic city got a lot smaller and really felt more like home.
I love that there is so much opportunity here. Whatever you’re interested in, the best and brightest people on the planet who do that thing are either already here or will be passing through regularly. There’s always a meetup or conference, there’s always someone who wants to grab a coffee or a drink, and there’s always someone who knows someone who wants to chat about their bold idea or passion project.
Q: I’m an old school jQuery guy. But I know you’re more impressed with the modern frameworks. What’s your preference and why?
A: My lead developer and I had a healthy React vs Ember debate when I first stood up Planning Labs, and he won because he had better arguments for why Ember was a better fit for a small scrappy team. It’s opinionated, but it brings everything you need for building single-page apps so you can prototype quickly and not have to worry about the myriad parts of the app architecture you would if you were assembling things from scratch. I am still a fan of React, if only because I don’t have to have 3 files open to manage the same component, and I actually like JSX (don’t hate, congratulate!). I was able to squeeze a little React into our portfolio via gatsby.js, the static site generator that powers planninglabs.nyc. Everything else is made with Ember, which we’ve built some powerful mapping integrations with and has served us well.
Q: As a former Carto employee, your GeoHipster cred is already well established, as far as I’m concerned. Now’s your chance to embrace the label, or provide evidence to the contrary.
A: I’m proud of the progressive spatial stack we put together at Planning Labs. We were pulling vector tiles out of the carto maps API before they were officially released (you know, “before it was cool”), and figured out how to consume them with MapboxGL. We even got to play with the new PostGIS ST_AsMVT() function to produce vector tile protobufs right from the database. We pioneered print-friendly web map layouts using paper.css, and even got to automate print map creation for New York Land Use Applications, effectively building GIS on the web with automated data and a custom UI. So yeah, I’m a geohipster and proud! I’m bummed to miss JSGeo this year 😦
Q: As a geographer, does it bug you that so many “New York” teams actually play in New Jersey?
A: I care so little about professional sports that I didn’t even know New York teams play in New Jersey. I didn’t care before and I still don’t care.
Q: What are the merits of a saltwater reef aquarium, and do you provide treasure maps to the inhabitants?
A: A reef tank was something I really wanted to do back in 2010, but I was about to move to NYC and it wasn’t a good time to start the hobby. My wife finally gave permission last year and I’ve been obsessive over starting up the tank. We’ve got a nice 34-gallon reef set up in our apartment with a few fish, some corals, a shrimp, and a crab. It’s high-maintenance, and requires a lot of water production, saltwater mixing, water chemistry testing, cleaning, etc. The payout is worth it, my kid loves to help with feeding and water changes, and the critters all have their own little habits and personalities. The tank is a big stress-reliever, and it’s just fun to nurture a little ecosystem and look to the community for advice and support. I have not integrated mapping or open source technology or into my fish tank yet.
Q: I’m sure our readers in between jobs, or considering a change, would appreciate any final words of wisdom.
A: We were successful at Planning Labs because I refused to compromise on the really important things. I always said “how we build is as important as what we build”, and that meant not doing things the way government IT is comfortable doing them. We still had lots of government cruft in our way over the years, but the basics of modern technology-building were not up for debate, and that made all the difference. By the way, sharing is a BIG part of what I consider to be part of the basics, and is probably our most progressive trait. Half the fun of working on something is sharing the achievements and lessons learned (and the finished product) with others in your community. In my experience, talking openly about what you are working on in government is either discouraged or flat out forbidden.
In summary, figure out what your values are, and apply them to every decision, every project, etc. If your personal values don’t align with your organization’s you will need to fight, defend, and evangelize them at every turn (or go find another organization whose values match yours). The former is preferable if you’re in public service.
A: I was surprised that we were the only collaboration to submit an entry, we are a team of two strong here at Team Bright Rain:
Bright Rain Solutions’ owner, operator, geospatial developer, data wrangler and self professed Grand Poobah. I’ve been part of the Geo Community for over twenty years and still get fantastically excited about all things geo. I’ve been known to run a workshop or two and have taught a class on web mapping. I consider myself a ‘bridger’ between the proprietary and open source worlds. And some of my best friends are “proprietarians”.
Bright Rain’s Dynamic Technologist with an earnest mission to change the way you put boots and hats on maps. Drew has been with Bright Rain for two years and earned a degree in Geography from the University of British Columbia. He was also the star student in my GIS programming class, from which I promptly drafted him.
Q: Tell us the story behind your map (what inspired you to make it, what did you learn while making it, or any other aspects of the map or its creation you would like people to know).
A: When it hit me, I literally jumped out of my chair and hollered, “Hexes in Texas!,” with a rousing “Yes! Divorce Rates in Texas!” and All My Hexes Live in Texas was born. It could have been the boots… I happened to be wearing cowboy boots that day… It could have been the H3 hexagon project we had going. But it was definitely cosmic inspiration.
The map is honest to goodness tongue-in-cheek grit but it also brought several interests together for us and that’s why we were excited (and committed enough) to create and submit it. It’s funny yet not so silly that we couldn’t actually wrangle some real data and present it in, dare I say, a (geo)hip way. We love the slight clash between the slick, modern feel of the web map and the old timey western feel of the title text, hat and boot.
Q: Tell us about the tools, data, etc., you used to make the map.
Data was gathered from the state of Texas (population per county and divorces per county) and the US Census Bureau (us states: Tennessee).
Analysis was conducted in QGIS where the divorce rate per thousand was calculated and the hexagons were assigned a value for extrusion (based on divorce rate calculation). The resulting hexagons with divorce rates assigned were exported as geojson for direct use in the web application.
Tobin Bradley is an indoor enthusiast. His hobbies include staring at screens (computers), staring at screens (books), staring at screens (movies), and staring at screens (video games). He wrangles code at Mecklenburg County Government in North Carolina and occasionally writes about it on his blog.
Tobin was interviewed for GeoHipster by Mike Dolbow.
Q: Good gracious, you’ve been blogging over at Fuzzy Tolerance since 2005! When you started, did you ever think it would last over 14 years? What does that first post make you think of?
A: Something Jeff Atwood of Stack Overflow fame said that stuck with me is the worst code he’d ever seen was the code he wrote six months ago, and that that was always the case. Looking at my first blog post from 14 years ago on Loading .NET User Controls at Run Time, complete with poorly formatted code from one of my 47 blog engine migrations, makes me contemplate the sturdiness of the window across from me and the elevation of this floor.
But it also makes me realize why I’ve never gone back and edited those old blog posts, even the ones that make me cringe. It’s me, or at least the part of me I choose to share. Fuzzy Tolerance started even earlier as (oh it pains me to write this) The Programming Consultant Newsletter, a PDF I’d share with our staff and other local GIS folks every month. I’m an introvert and slightly autistic, the kind of person you’d see at a conference pretending to be part of a wall while eyeing the exits. Writing has always been the way I can help people and express myself. So it doesn’t surprise me that I’ve been doing it for so long, and in the event of a civilization-ending zombie apocalypse, I’d probably still write blog posts with spray cans on the sides of abandoned grain silos.
Plus it’s a good way to archive my aging brain. Recently somebody thanked me for a bit of complicated PostGIS-related SQL I shared that I had no recollection of whatsoever. I was pretty sure I was being confused with a smart person until I found the blog post.
Q: All right, let’s back up a little for our readers here. How did you get into GIS…or geospatial…or whatever we’re calling it these days?
I was always headed for something related to problem solving and technology. My parents bought me a Commodore VIC-20 in my formative years, a 5KB of RAM powerhouse (if you had the Commodore 64, (a) congratulations and (b) I hate you). It marked the point in my life when I became an indoor enthusiast. The things I managed to do with BASIC are probably still illegal in most states.
Naturally I went to college expecting to become a programmer. Two classes later and I was disabused of that notion. I could do the work, but I didn’t enjoy it. This is a failing on my part; I have an awful time learning things if I don’t have an immediate practical application for them. I realized I didn’t like programming per se, I just liked solving complex and interesting problems. If I weren’t an indoor enthusiast with an aversion to dirt I’d be perfectly happy being an auto mechanic.
During that existential crisis I happened to take Geography 101 as an elective with an amazing professor, Dr. Tyrel Moore. I went in thinking I’d memorize the state capitals, which was what I thought geography was at the time. Boy was I wrong. I was fascinated by the breadth and scope of the subject matter, but I’ve often thought if my first geography professor wasn’t an amazing teacher, I could have gone in an entirely different direction. Thanks, Dr. Moore.
I had no idea GIS was a thing when I became a geography major. With my programming background, it was a natural fit, and the rest is a succession of lucky breaks and happy accidents. We still call it GIS in Mecklenburg County, but once Data Science becomes a hackneyed term nobody uses anymore, I’m sure local government will switch to it.
Q: Your second Fuzzy Tolerance post was on Open Source Software. Even though the first FOSS4G conference (under that moniker) was only a year away, that still seems awfully prescient to me, especially considering that you work in public sector IT. Did you have a crystal ball hidden somewhere? And did you feel like a lonely voice back then?
A: A nice thing about local government is the antiquated technology actively encourages one to experiment with other things. Combine that with my natural nerd inclinations and I was playing around with things like Linux and MySQL and PHP very early on. At that point I had a loose understanding of what open source was; my interest in open source software was born out of practical rather than idealistic considerations.
The big turning point for our GIS group was when we launched an important website using new internet mapping software from our proprietary GIS vendor with much public fanfare, only to have it explode in a furious ball of nothing. We were battling “server unavailable” messages around the clock. We threw more hardware at it. It crashed faster. We brought the vendor in, who gave us a very expensive shrug. It was black-box proprietary software, so we couldn’t fix it. We couldn’t even tell what was wrong.
Fortunately that wasn’t one of my apps, but I had some apps coming down the pipe, and there was no way I was building them around that software. Some people looked cool and important with a pager strapped to their waist; I was not one of those people.
So I tried UMN’s MapServer, not overly optimistic about it because I thought web mapping was too niche for open source software. MapServer was better than our proprietary product in every imaginable way. It was faster. It was stable. It scaled better. And from a programming perspective it was much easier to work with. I released a couple of apps using it, and we had zero problems. It was…awesome.
That opened our eyes. We’re still a mixed proprietary and open source shop, but it’s exceedingly rare that we create something that doesn’t use open source software, and many of our projects are built entirely with open source software. We also release a lot of our software under an open source license. While I love the ethos and spirit of open source software, our use of open source is still entirely for practical reasons. For many problems, it’s the best tool for the job.
Personally, I’ve been rocking Linux at home (currently Manjaro KDE) exclusively for 15+ years. The open source community and ethos feels like home to me.
Q: You’ve been working for Mecklenburg County for a long time. Is there anything special about this organization that keeps you interested and invested?
A: Oh, not really. Don’t get me wrong, it’s a great place to work, but it has the perks and pitfalls of most local governments. If our GIS group can be said to have accomplishments, I don’t think they’re accomplishments other local governments couldn’t achieve.
I’ve been very lucky in two ways. First, I’ve managed to have great bosses. One bad boss and I would have fallen back on my rock guitar god/professional video gamer career. Second, our GIS group does work with all of our government agencies, making for a wide variety of interesting and ever-changing problems to solve. Even after 20+ years (!), I still look forward to coming to work.
Q: I think I first caught on to your blog around when you started writing about customizing Google Maps, which inspired me to do the same for the organization I was supporting. Back then, they were one of the few choices for a slippy map API, but now there’s probably a dozen, depending on how you count. How do you keep up with technology changes, and how do you decide what to recommend/implement at work?
A: Without the constant technology changes, I’d have left GIS at some point. It’s the constant learning that makes this job so interesting.
At the start of every month I write out the things I want to learn more about. It’s my job to investigate these things, but in all honestly I’d do it even if it wasn’t, and I think it’s something everybody should do. It’s very easy to turn on autopilot and keep doing the same thing the same way over and over, but if you aren’t learning, you aren’t growing, and if you aren’t growing, you’re shrinking. Literally. You’ll shrink.
I try not to steer the ship by recommending or advocating a particular technology direction unless I’m directly asked or I see an iceberg ahead. I tried that early in my career with limited success. I’ve found it’s much more effective to drop guideposts and let people come to them on their own. When people notice my apps are always up, or that an app does a particular thing they’ve been struggling with, they move in that direction naturally. Otherwise it’s whip-cracking and cat-herding, and I have no talent for those things.
Q: You’ve got a lot of code on Github, like your Bootstrap and Leaflet template. Does your organization actively support you open sourcing your apps, or do you just ask for forgiveness later?
A: Ug, that’s an old one. I should probably redirect that repo to Bryan McBride’s Bootleaf, which is much better. Mine was first (ha!), but as with most things, if Bryan McBride and I both did it, you should go with Bryan’s version.
I wouldn’t say my organization actively supports open sourcing apps (I don’t know of anybody else in the organization that has), but it isn’t opposed to the idea. In the early days it was something I did and waited patiently to see if I was going to be flogged, but these days even crusty old mainframe programmers know what GitHub is. Most people I talk to don’t share their code because they think it’s terrible, which is true. What they don’t understand is everybody’s code is terrible. No matter how terrible your code is, there are people it can help, and there are people that will help you make your code better.
My county has a park locator app. So do all 100 other counties in North Carolina. So does every county in the United States, and probably every local government around the world. The wasted effort and money in government because we aren’t sharing code with each other should be an outrage. I’m not big into leadership by fiat, but making all publicly funded code open source is a law I would wholeheartedly support.
You’ve also open sourced your current GeoPortal, which when I use it, strikes me as the “anti-portal”. This app is so simple, I can use it and browse it even though I live over 1,000 miles away. I have to believe there will be other local governments using this somewhere. Are you aware of any?
A: GeoPortal is a fun project. It’s one we initiated within our group, which is different — most of our projects are initiated by our customers, aka other county agencies. That gives us leeway in terms of design and functionality that we often don’t have on our projects (read: when you see one of our apps with 37 buttons, know that a battle was lost). It’s also very fun modern tech: vector tiles, reactive UI components, progressive web app, etc. It’s good to have one project your group completely owns that can be used to try new things and blaze trails for future apps.
I know places that are using our projects like GeoPortal and the Quality of Life project and our Dirt Simple PostGIS HTTP API, and if they want to give us a hat tip for that, that’s very nice. I don’t like to call them out myself though. Taking something we wrote like GeoPortal and customizing it for their own jurisdiction is a herculean effort (I’ve seen my code), and I don’t want a smidgen of credit redirected from somebody that worked really hard on their app to us. But I’ll say this to others that may be functionally autistic/dead inside like myself: knowing that something you shared is helping other people will touch and affect you in ways you won’t expect. When people thank me for a project I’ve shared, I hide in my office for an hour.
Speaking of hat tips, GeoPortal needs to give a giant one to Brian Timoney. His blog posts on how people actually interact with web sites was a real eye opener, and it got me started on a path of learning more about UI and UX, to the point where the map on GeoPortal is now an optional click (gasp!). For my money, good design is still the most glaring problem in government websites today, and unfortunately it’s an area governments rarely invest in.
Q: Judging by your Twitter bio picture, you’re both a musician and a dad, like me. I personally find that lessons I learn in those two roles can be applied in GIS, in IT, and in public sector work. Have you found the same thing, and if so, are some experiences more influential than others?
A: To call me a musician is stretching the term a bit. 23andme has officially confirmed the dad part though.
My first lesson as a father was that I owe my parents an apology. Beyond that, it’s hard to pick out individual things, as I ama fundamentally different person since my son was born. I have a lot more patience. I understand that people have their own motivations and histories, and if I want to connect with and motivate people I need to understand those things and not judge them. A number of children’s cartoons no longer piss me off. It’s a really strange experience going from not understanding people at all to having a wife and son that I’d step in front of a bus for without a second thought, but I wouldn’t trade it for anything.
Being a musician, aside from the expense of new gear and the noise complaints, is a total quality of life improvement. It builds focus, tenacity, patience, confidence, and peace of mind, all of which translate to your life in positive ways. I did not pick up the guitar at 16 for any of those reasons. I picked it up because I thought it would help me woo women in ways that my personality and stick-like figure did not. Turns out an autistic stick-figure kid carrying a guitar around everywhere is mostly just weird.
Q: Tube amps or solid state? Seriously.
A: If your gear inspires you to play and create music, it’s the right gear. If it doesn’t inspire you to play and create music, it’s the wrong gear. If a Squier Strat plugged in to a Peavey Bandit is what inspires you, make your music and tell all of the gear snobs to stuff it.
But the correct answer is tube amps.
Q: OK, the evidence is building. But I’m starting to feel like I don’t have to ask EVERY interviewee if they’re a geohipster. Would you be OK if I skipped it this time?
A: I have never owned a non-functional scarf, which I think rules out the hipster part. I have also never intentionally achieved “cool”, though after many years of work I have “non-threatening” down pat. It mostly involves smiling a lot without showing teeth. I do own a tie that plays Christmas carols. Do with that what you will.
Q: Any words of wisdom or parting shots for our readers?
A: For my fellow local government tribe, I try to encourage people to be present and thoughtful about everything they do. The most common answer to why a local government does something the way it does is because that’s the way it did it yesterday. This is always a bad answer.
But for everybody, my biggest wish is that people would realize how amazing they are, how important they are to other people in ways they don’t understand, how smart they are and the ways they can and do contribute. Imposter syndrome isn’t a new thing, but it seems to hit the tech field pretty hard. The next time your inner voice is giving you an itemized list of your failures, ask yourself if that inner voice was an actual person, how long would you listen to it before you punched it in the mouth. If the answer is not very long, feel free to ignore that voice and go do awesome things with whatever time you have on this planet. And share some code along the way.