Monthly Archives: March 2018

What ISPs taketh away, the spatial community giveth back

By Amy Smith

The State Plane Coordinate System is comprised of 120+ geographic zones across the US. The system, developed in the 1930s by the U.S. Coast and Geodetic Survey, is a commonly used mapping standard for government agencies and those who work with them.

There’s a website that I’ve had bookmarked for as long as I can remember. It’s simply a list of State Plane zones and the US counties that fall within each. At the top of the page are state links that redirect further down on the site, but I rarely use those. I usually just cmd+f and search for the county I’m looking for. Even if I know the zone already, the site gives me a sense of security when I’m making a map that uses the US-based coordinate system – like the feeling one gets when going back to double check that the stove is off and the door is locked.

There are most certainly other ways to look up State Plane zones, but this one, hosted on a stranger’s personal website, is the one I like best. Maybe it’s the simplicity of the site, its Web 1.0 design, the fact that the person who made it picked tan for the background color. Maybe it’s the nostalgia of going back to something I’ve used time and time again, and always has what I want – like a well-loved t-shirt.

A while back, I went to the State Plane site only to find the site could no longer be reached. Russell Edward Taylor, III, experienced something similar, but instead of chalking it up as a mystery like I did, got in touch with the owner, Rick King, and asked about hosting the site on his own domain. Lucky for those of us who’ve relied on it as a useful reference, it continues to live on on Russell’s personal website. Russell also did some investigating and found nearly 400 links to the State Plane site from across the geospatial community, from universities to professionals to students. Inspired by his initiative, I decided to reach out to Russell, who put me in touch with Rick, to learn about the site’s story.

Rick King

Q: Rick, thank you for creating the State Plane site. Could you tell us a bit about yourself, and why you created the site?

A: I am currently retired having worked in GIS and Land Surveying since the 1980s. I was a Professional Land Surveyor licensed in Utah with most of my “experience” being while working in Indianapolis, Indiana, and ending after a 4-year stint working as a GIS Analyst in Los Alamos, New Mexico, documenting some hazardous waste remediation on a material disposal area that was used at the time of the Manhattan Project. I also helped with the development of an Acequia GIS for the Taos Soil and Water Conservation District in Taos, New Mexico.

My initial work in GIS was to allocate mapping resources to provide the base layers for large regional geographic information systems being developed primarily by the various utility companies. In the pre-internet days this work was accomplished by telephone inquiry starting at a state geological office or somewhere to see if there was any existing mapping available. GIS has evolved since then, but, just wanted to throw that in to let people know that GIS was existing before the world wide web.

I created the site as a reference for myself to help me at work. In the course of my work I received hundreds of datasets most all of which came without metadata and without any identification of the coordinate system on which they were based. The website I created in basic HTML would give me starting points to make the coordinate system identification. At the time of its creation, there really wasn’t anything else online to fulfill the need. I wanted to reference both the NAD 27 and NAD 83 systems, and found those references listed in the state statutes when I could find them online. The UTM references and the MS Excel spreadsheet were added later.

The state plane coordinate system page was part of a multi-part GIS reference page titled “GIS Landbase Information and Data Links”, which provided weblinks to the same.

The awful tan color of the background was carefully chosen for providing less eye-strain.

I hosted the site for many years as my contribution to the internet.

Q: Russell found almost 400 links to the State Plane page on other websites. Did you realize the site was being used by so many others in the geospatial community?

A: I did. It was Comcast’s decision to withdraw hosting personal web pages which is why it went down.

Q: When did you create the site? Looking at it now, is there anything you would change?

A: I created the site in 1999, and most of its creation is covered in the metadata I created for the page. Actually, I was one of the first people to quit using the page, so changes would have to be made by someone else.

Q: What was your reaction when Russell reached out about hosting the site. Were you surprised at all?

A: I was hoping that someone would step up and host the page as there were some educational institutions using it as a reference. A big thanks to Russell for stepping forward.

Q: Now being retired from a long career in land surveying, what do you do with your spare time? Do you have any hobbies?

A: I spend a good deal of time day trading on the stock markets. The goal is to grow my retirement funds specifically so that I can afford to build a new house. Yep, that’s the goal!

Q: A geohipster is someone who works anywhere along the broad spectrum of geospatial data and applications. Usually they’re described as being on the outskirts of mainstream GIS, thinking outside of the box, and doing something interesting with maps. Would you call yourself a geohipster? Why or why not.

A: No, I just never got involved with the analytics of GIS to get that excited about it. But…

Q: Rick, thank you for your contributions to the geospatial community, and for helping bring well-documented GIS resources online throughout your career. Any words of wisdom you’d like to leave with our global readership?

A:  The world has become so dynamic. Everything is changing. People and politics, the environment, business and trade, and world economies. GIS is the only science that is capable of accumulating all the data, visualizing the data, comprehending the data, and finally using the data to forecast future models that will benefit us all. Population management, food management, resource management will be extremely vital in the near future. There will be plenty of opportunities to resolve what most of us believe are foreseeable problems, especially having clean water and adequate food for everyone.

Russell Edward Taylor, III

Q: From your resume, I see that you’re a Senior GeoSpatial Analyst at CoreLogic. Could you tell us a bit about what you do there?

A: I’m part of a group that works on a suite of data products used by clients for location intelligence. It’s based on a standardized, nationwide parcel dataset derived from point and polygon data acquired in every data format, attribute layout, and projection under the sun. Taken together, our little team likely has more experience than anyone with the quirks of the many different ways parcel mapping is done. I’m on the more technical end these days, maintaining internal tools in Python, preparing custom data deliveries for clients, managing our metadata and documentation, plus a variety of internal process-improvement initiatives that have immersed me in the database world more than I ever imagined possible when I got into GIS in the late 90s.

Q: When did you realize the State Plane site was no longer live, and what inspired you to reach out to Rick?

A: It was in July 2015; a colleague brought it to my attention when they went looking for the state plane zone of a county they were working with. After I hurriedly cached a copy from the Internet Archive for use by my team and myself, it occured to me that there were probably others out there wrestling with similar data that would miss it too. I have a personal website, and since the State Plane site is just one simple page, I realized that it would be very easy for me to keep it available to the world. Over the years, I’ve benefited greatly from the community-mindedness of others, so it seemed like a good way to do my part.

Personally, I favor open software, data, and public licenses that make works more widely available for use, but I’m also aware that not everyone does. Rather than take the risk of running afoul of an unknown benefactor by re-hosting the site without permission, I decided to do it by the book. I thought it was especially important to do it that way for two reasons: first, it would be a full, verbatim copy, and not anything that might fall under fair use if I ever had to defend it; second, if I republished it without a notice at the original URL, those who had been using it might have a harder time finding their way to its new home. So, after gathering a bit of courage, I shot off a short message that happily found a friendly response.

Q: Have you received any notes from others who’ve found the state plane site on ret3.net?

A: I have, at a rate of a few each year. Most are simple thank yous from visitors glad to find it still alive somewhere. Most emails come from businesses domains, almost as many from .edu accounts. I’ve had a couple interesting ones that led to a little research about parts of the page I’d never used for myself, most memorably as to just what an ADSZONE is.

Q: Enlighten us?

A: Oddly, I received not one but two questions about this within a few months of each other in late 2016. As near as I can tell, ADSZONE stands for Automated Digitizing System Zone, named for the tool the Bureau of Land Management used to convert NAD 27 maps to NAD 83, along with other subsequent projects, and the regions used for that project. Now knowing more about Rick’s experience, the inclusion of this bit of information makes more sense! If you’re curious (or very, very bored, although there is some fine early 90s clipart to be seen therein) the manual is online here: https://archive.org/details/automateddigitiz00unit. I don’t believe this numbering system is used very widely anymore, although in the surveying business (the field of both of my interlocutors on this topic), encountering disused references is pretty common.

Q: When you’re not being a geospatial analyst, what do you like to do in your spare time? From your website I glean that beyond maps, you also like comics and bikes.

A: I got my start reading comics with my dad’s Silver Age DC collection, but fell out with constant reboots of the modern era, so these days I’m far more likely to pick up self-contained stories, or at least serials that aren’t under pressure to run forever. Of course, I’ve always had a weakness for maps in comics: the World of Kamandi, Krypton, Marvel’s New York City, Prison Island and other small-town memoir settings, even the dotted-line paths in Family Circus.

I’ve been a daily bike commuter for 8 years (and 110 pounds), following a 25-year hiatus from pedaling. I ride a modest 5 miles round trip on my commuter bike, plus weekend trailriding on my mountain bike and recently longer road bike events. Interestingly, all my bikes are folding models. Although it’s not closely related to my professional niche in geography, planning, land use, and transit issues have always fascinated me, more so since bike infrastructure became a rather personal concern!

I also enjoy Austin’s energetic music and craft brewing scenes, with friends in the former (go see Danger*Cakes, Bird Casino, and Oh Antonio & His Imaginary Friends!) and my neighborhood being taken over by the latter, which happens to combine well with cycling.

Q: Are you a geohipster? Why or why not?

A: That’s hard to say; most of my work is not what would come to mind for that label — it’s pretty traditional and desktop-oriented, working with shapefiles in proprietary software, focused on fundamentals of data integrity for the end user. GeoNormcore, perhaps. The GeoJSON, FOSS4G, webmapped world is something I encounter mostly at conferences and in occasional at-home dabblings. That said, I am planning a Dymaxion tattoo, so perhaps I have a bit of geohipster in me after all.

Q: Any final words of wisdom you’d like to leave with us?

A: Although I always have to remind myself of it when the opportunity arises, folks are far more willing to help and collaborate than you’d think. Muster your gumption, screw up your courage, steel your nerves and ask nicely. I know it works on me.

Anonymaps: “use.real.addresses”

Anonymaps
Anonymaps
Anonymaps is a shadowy provider of Twitter geo snark, lurking on the fringes of the under-the-counter geocoding industry. Since 2013, Anonymaps has tweeted 1,001 times, comprising 80% proprietary mapping fails, 19% three.word.barbs, and 1% obscure OpenStreetMap in-jokes. Anonymaps is somewhere between 20 and 60 years old and works in the illegal OSM import trade.

Q: It is said that positive thinking causes neuroses and makes people dependent. You are not in any danger, are you?

A: No-one quite knows how Anonymaps’ embittered, caustic personality developed. Some hint at unspeakable deeds in the early days of Cloudmade. Others say that a once-kind nature was (gdal)warped by discovering the One ST_NRings To (Python) Bind Them All. Still others tell tales of an idealistic developer blinded by exposure to the Manifold source code. Personally I think it’s PTSD from the OSM license change.

Q: Your Twitter bio says “crowdsourced sarcasm”. Do you have multiple personalities?

A: Yes. Totally. Anonymaps is essentially a loosely shared Twitter password. I’m not even sure who everyone is but I know people from at least four countries have posted.

At a conference some years ago, late one night in the bar, I got talking to a Well Known Geo Personality. He leaned over and confided: “Actually, don’t tell anyone, but I’m Anonymaps.” I sounded doubtful. “No, really, I am. Look.” And he posted a tweet. So that was me told.

Q: What is the purpose of your Twitter presence?

A: Historical accident. We were originally @FakeSteveC but the joke got old. Other than that, we’re mostly black ops funded by an unnamed geo corp with the aim of discrediting What3Words.

Q: Well, whatever your goals are, you’re more complicated and nuanced than some random troll. And you’re no sea lion either. If we call you the “Archie Bunker of GIS”, will you call us “Meathead”?

A: Delighted. Archie was a great geo thinker. He once said “East is East and West is West, but none of us is gonna meet Mark Twain”. I’m not sure what the EPSG code is for that particular projection but I swear I saw a shapefile in it once.

Q: You’re our second interview (after @shapefiIe) where, honestly, we have no idea who you actually are. But you sound like you might be on Shapefile’s side in the “best geo format” debate. Might you be kindred spirits?

A: Honestly, have you ever tried to use GeoJSON? #shp4lyfe

Q: You’ve had compliments for Mapzen’s work in the past. Any words of encouragement to their team and/or users now that they’ve closed up shop?

A: Full of admiration for Mapzen. How Randy manages to repeatedly hoodwink massive companies into spending millions on OpenStreetMap development is a source of wonder to me.

Mapzen was a curious experiment in developing superb software entirely devoid of any commercial imperative. All that code is now sitting there, ready to be exploited by avaricious sales guys who perhaps spend more time reading Clayton Christensen than T.S. Eliot.

I’m not at all surprised that Mapbox swooped on Valhalla – what surprises me is that no-one bought up the Tangram/Tilezen stack and team. If I were Amazon or Foursquare I would do that in a heartbeat. Right now Mapbox owns the mobile location market and no one much is challenging them.

Q: So a while back you posted a poll (https://twitter.com/Anonymaps/status/944298450061086721) on what the OSMF should focus on and mapping won by double digits over diversity and being inclusive. That was a rather pointed poll you put out. So why run the poll?  

A: Sometimes you get the hot takes by throwing a flamethrower through a window and seeing who comes running out shouting.

So how diverse are TomTom’s surveyors, or HERE’s? How diverse are their specs, their algos, their cartographic choices? My sense is not very, certainly less diverse than OSM. But they won’t tell us so no one bothers asking. OSM is open so you can ask the question, but the answer is sometimes used as a stick with which to beat OSM and its existing contributors. Better to use it as a carrot for improving OSM.

It’s self-evident that more, diverse contributors mean a bigger, fuller map. Preppy Silicon Valley kids training ML models to trace buildings, and bearded Europeans surveying biergartens do not a full-featured map make. OSM needs more mappers with young families, mappers who live in backwoods areas. It shouldn’t just be the best map of SF and Berlin.

Is that focusing on mapping or diversity? You tell me.

Q: Multiple choice question: The Humanitarian OpenStreetmap Team is: A. the best thing to happen to OSM or B. the worst thing to happen to OSM. Explain your answer.

A: A for comedy reasons. Where would Worst Of OSM be without HOT?

Certainly HOT has transformed expectations of OSM. Compare the map of Mozambique to that of, say, Michigan. You wouldn’t expect good maps in a land of cultural impoverishment, potholed roads, miles of slums and gang warfare, and sure enough, Detroit’s pretty bad in OSM. Maputo meanwhile is immaculately mapped. As you’d expect from the name.

The harder question is whether remote mapping is essentially imposing Western values on communities who, left to their own devices, might evolve their own, quite different map. Erica Hagen wrote thoughtfully a couple of years ago that “it’s actually pretty easy to bypass the poor, the offline, the unmapped… in spite of attempts to include local mappers, needs are often focused on the external (usually large multilateral) agency.” Gwilym Eades was ruder: “remarkably self-centred, expert-driven, and dominated by non-local actors.” That’s going too far but the next challenge for HOT is to enable the local mapping that marks out OSM at its best, rather than just serving as unpaid Mechanical Turks.

Q: Do you consider yourself a geohipster? Why/why not?

A: We try and cultivate a detached, post-ironic air of mystery while leading life on the technological cutting edge (PostGIS nightly builds and Mapnik trunk, which leaves about one hour a day of free CPU time). But actually we live for that sweet retweet juice. Maybe it would be truer to call us a geohuckster.

Q: On closing, any words of wisdom for our global readership?

A: use.real.addresses. Meathead.

Howard Butler: “Like a good song, open source software has the chance to be immortal”

Howard Butler
Howard Butler
Howard Butler attended Iowa State University and departed with Bachelor’s and Master’s degrees after studying parts of Agronomy, Agricultural Technology, and Agricultural Engineering. He learned GIS software development during his thesis effort, where he needed to make ArcView 3.x do a complicated and completely unrealistic analysis. After failing to find a precision agriculture job because a GPS for a tractor cost $2,000 at the time, the Iowa State Center for Survey Statistics and Methodology took a chance on him to develop some GIS data collection and management software for the National Resources Inventory. Fifteen years later he’s helping to write open source software that's powering data management systems for autonomous vehicles.

Howard lives in Iowa City, Iowa with his wife Rhonda, his two boys Tommy and Jack, two dumb cats, and a squirrel or raccoon or something that takes residence in his attic every winter despite efforts otherwise. He has a neglected blog at https://howardbutler.com/, and he tweets less and less at https://twitter.com/howardbutler.

Howard was interviewed for GeoHipster by Randal Hale.

Q: Howard – where are you located and what do you do?

A: My three-person company called Hobu, Inc. is located in Iowa City, Iowa, and we write, manage, and enhance open source point cloud software and help our clients use that software to solve their challenging problems. We initially focused on LiDAR (Light Detection and Ranging — think radar with lasers) with a project called libLAS, evolved that into PDAL (GDAL for point clouds), and then continued with streaming technology in the form of Greyhound and Entwine.

I started contributing to open source with MapServer and GDAL back in 2002 when I discovered it was the only software capable of building the systems my job demanded at the time. I came to enjoy the camaraderie and common purpose those good projects exuded, and I learned over the years how to contribute in a way that matched my skills. Among other things, that evolved into writing a number of geospatial Python bits (you can thank/hate me for plenty of ogr.py and gdal.py) and helping to author a bit of the GeoJSON specification (you can thank/hate me for coordinate systems there).

In 2007, I struck out on my own and promptly learned that I didn’t know how to run a business. My banker still doesn’t really understand how or why we give away our software, but people get it when I say our product is consulting with a software toolkit we incidentally give away. Over the years we’ve built up a stable client base that values what we do and how we do it, and I think that the software we’ve written will outlast my company or my career because it represents solutions to problems people hate to solve again and again.

Q: So how did you end up working with LiDAR? I’ve had the chance to use PDAL and see some of your presentations at FOSS4G and FOSS4GNA.

A: The Iowa Department of Natural Resources led Iowa to be one of the first states to do a statewide LiDAR collection, and they had a grad student semester of funding they wanted to use to be able to use Python for ASPRS LAS data management, verification, and inspection. There was no open source requirement, but since it was what I was doing otherwise, it seemed natural to build a library that anyone could use. Mateusz Loskot and I started working on what became libLAS to achieve it, and once it was clear it was viable, I was able to attract more funding to enhance and improve it.

U.S. Army Corps of Engineers found libLAS and wanted to do a lot more with it — supporting a bunch more formats, getting it speaking to databases, and enhancing it to do a bunch more algorithmically. We learned stacking all those desires on a library based on the LAS format wasn’t a great fit. We started PDAL (Point Data Abstraction Library — pronounce it the same way you do GDAL 🙂) after some fits and starts and it has matured into a general-purpose library for building geospatial point cloud applications.

PDAL takes GDAL’s VRT pipeline approach and puts it into the context of geospatial point clouds, but with JSON instead of XML. It works on Windows, OSX, and Linux, and it has a command line application like GDAL to drive processing. Its workflow is optimized to template data operations and batch them up over a pile of data with whatever batching/queuing/cloud tools you have. That might be GNU parallel if you want to melt your laptop locally or something like AWS SQS in a cloud situation.

Q: I saw your presentation on Gerald Evenden at FOSS4G in Boston. Did he know that the PROJ library…or software…was going to go as far as it did? Actually – what does PROJ do?

A: PROJ or PROJ.4 is a cartographic reprojection library that was written by Gerry Evenden at USGS in the 1980s and 90s. It contains the math to reproject coordinates from UTM to Plate Carrée, for example. Gerry originally intended for PROJ to be a cartographic projection library (pure math only!), but in the 90s, Frank Warmerdam came along and started adding convenience for geodetic transformation (datum shifting). This caused some creative differences, but that geodetic convenience enabled PROJ to be bootstrapped or ported into almost every open source geospatial software package in some form or another.

While attempting to dig up some old documentation, I discovered Gerry died in 2016. This saddened me because I’ve felt that Gerry didn’t get his due for the impact that PROJ has on the entire geospatial software ecosystem. It is truly everywhere — open source, commercial, and government software all depend upon PROJ. I submitted my FOSS4G 2017 talk in an attempt to tell his story and shine the spotlight on him even though he probably would have detested it.

I’m a fan of 60s and 70s rock n roll, and now that those guys are starting to die off, people are rediscovering a lot of back catalog. Plenty of it is still crap, but songs that shined then often sparkle today. Those songs were written for the audience of that time, but a good one can transport you there even if you weren’t a part of it. Like a good song, open source software has the chance to be immortal. It is optimized for solving today’s problem in today’s context, but a few programs and libraries end up lasting multiple generations. Unlike a hit song, open source software isn’t a static fount of royalties. It is a liability that must be maintained or it will crumble back into the ground. People need to cover it, make it their own, and feed it attention as Paul Ramsey wonderfully described in his FOSS4G 2017 keynote.

For PROJ, two longtime contributors have been covering the song and keeping the music alive. Thomas Knudsen and Kristian Evers from the Danish Agency for Data Supply and Efficiency (kind of like Denmark USGS) refactored PROJ to be a full service geodetics library and they have modernized its API in the process. Kristian has led this PROJ 5.0.0 release process, and everyone’s software is now going to be able to get a lot smarter about geodetic transformations. While the old APIs are still available so as to not break existing software, their improvements will make PROJ last for another couple of generations.

Q: Thoughts on Mapzen shutting down?

A: Anxious and hopeful. As someone with an organization and employees, the thought of having to tell them they’re now on their own is a front-of-mind fear. Organizations fail for many reasons despite the effort of the people pouring their sweat into them. To work so hard and have it be called a failure doesn’t seem fair, but I’m thankful for Mapzen’s postmortems, which have given everyone the chance to learn.

I’m hopeful due to the fact that I think Mapzen’s employment model demonstrated a successful one for the employees. Many Mapzen’ers worked out in the open on public projects, and in the process made themselves and the teams they belonged to more valuable for it. Developing open source software in public, as opposed to never going out beyond your own wall, is something that makes you a better software developer. You have to listen to rightful criticism about your software, and you have to temper your emotional response to people rationally not liking the precious thing you just made (ok, not always). To solve hard problems in public leaves you exposed, but in exchange for that vulnerability, you generate a professional currency that follows you the rest of your career.

An influential quote I saw early in my career came from Tim Peters of the Python language:

You write a great program, regardless of language, by redoing it over & over & over & over, until your fingers bleed and your soul is drained. But if you tell newbies that, they might decide to go off and do something sensible, like bomb defusing<wink>.  

The only thing you can do is make your software suck slightly less every day you touch it. My formative experience in geospatial open source was watching folks like Frank Warmerdam, Steve Lime, Martin Davis, and Markus Neteler do exactly that. They controlled the complexity in front of them, resisted the urge to overdesign a solution, and they treated everyone with respect even when they didn’t deserve it. I’ve tried to follow their approach with my projects, although I’d consider myself a worse developer than each of them by most measurements.

Q: You were there at the beginning for OSGeo back in 2006(?) I think. How has it changed or remained the same? How did you get pulled into the organization?

A: OSGeo’s reason to exist in 2006 was different than it is in 2018. In 2006, it was supposed to be a group of geospatial software projects with a common thread about open source. In 2018, it is a group of people with a shared interest in open source geospatial software. The former was frustrating for different reasons than the latter, but it has been an organization that achieved substantial things despite the messy way in which it is able to go about it. Many of its challenges relate to the fact that it is a volunteer organization throughout, and personalities with drive and determination can have short-run impact, but long-run sustainment is very difficult. Recently, it has slowed its precession about the axis of outreach, education, and conferences, which are topics that fit the current makeup of the organization very well.

I’ve had many roles in the organization over the years, including helping to set up some of the first project infrastructure and acting as a board member. In 2006, software project infrastructure was a real cost, but in 2018, access to repositories, mailing lists, continuous integration, and bug reporting can all be had in exchange for some spam tolerance. Recently my contributions have been presenting at conferences and being a strong supporter of the mid-winter OSGeo Code Sprint that has oscillated back and forth between the EU and North America. Sprints are a primary opportunity for developer camaraderie and collaboration, and they provide the high-bandwidth communication forum for projects to grow and enhance each other.

Q: I’m not a developer by any stretch – but I like going to talks by developers on their software. You’ve built PDAL to manipulate LIDAR Data – what’s the weirdest use case you’ve seen for PDAL so far?

A: Nothing too weird, but it is an everyday occurrence for users to use the tools in ways we didn’t foresee or intend. Every permutation of data size, composition, and fault gets hit eventually. For every success story using PDAL in a way we never thought of, there’s a corresponding failure story due to assumptions that don’t line up. Many times a great bug report is simply a challenge of those assumptions.

Q: What’s the Best Thing about Iowa? What’s the Worst Thing? I drove through it once and didn’t stop but long enough to eat a sandwich.

A: The Public Land Survey System in Iowa means I’m never lost. You probably weren’t ever concerned on your drive either. Also, the proximity to so much animal agriculture means that meat-as-a-condiment to more meat isn’t just a specialty no-carb lifestyle choice here. You would think with 90+ percent of the land in the state used for agriculture there would be more vegetables around.

It’s not the worst, but opportunities for Big Culture stuff like museums, art, and music shows are somewhat limited here, especially once you get out of the larger towns. Lack of diversity is a challenge too, although you find it in places in Iowa you wouldn’t expect. These are the same challenges for all rural states with aging, out-migrating populations.

Q: Can you tell us something people might not know about you?

A: I grew up on a corn and soy farm in Southern Minnesota, and I was convinced that maps and computers were interesting after some quality time on the Dinty Moore Beef Stew assembly line. I have a pilot’s license I haven’t used in more than a decade, and my car was once struck by lightning while driving down the freeway at 70 mph (I shouldn’t have bought it back from the insurance company). A long time ago, I won an Esri Conference award using AVPython and ArcView 3.x, and I could still sling VTables and FTables around in Avenue if I was cornered.

Q: Almost 4 years ago we defined the geohipster to be a person who lives on the outskirts of mainstream GIS. Would you describe yourself as a geohipster?

A: I guess. GIS™ as a name is an outdated view of how the intersection of geography, computers, and databases is to be constructed. Each of its areas has been dumped over at least a couple times since GIS™ as a fashionable term came to describe our industry. Many still GIS™ on desktop software with a 2D map frame and 🔍 zoom and ✋pan icons like twenty years ago, but geo+computers+databases is now oriented toward phones, sensors, and deriving locality from incidental data with cloud computing and pervasive networking. To call what’s going on with all of that GIS™ seems rather trite.

Q: I leave the last question to you – anything you want to tell the readers of GeoHipster?

A: Please make sure to buy a GeoHipster calendar or a t-shirt or something. We’re all just learning here, and sites like this one make the job much easier and need our support.