Hear me out for a minute . . .
. . . I'd like you to make maps intended for online viewing.
This is partially a selfish impulse; I'm going to throw a rock through the window if I see another "PDF Download" link masquerading as a web map. I'd also like you to do this to save a few trees from their 24"-by-36"-poster fate, but mostly it's because we're at an inflection point in cartography . . .
View Larger Map
. . . I think the public - the folks who show up to input forums for development projects, and who want to know how far it is to the next lean-to on the trail - are now fully-literate in maps. Mapquest started this process and Google advanced it, but now there are tools beyond those to help you engage your audience on computers and mobile devices (No, Trimble, I am not referring to the Juno. Screw that.). Many of these tools happen to be open-source . . .
. . . If you currently describe yourself as a "GIS Analyst/Technician/Monkey" - as I did not long ago - your day largely consists of desktop GIS, and 95% of you are working entirely with some combination of ESRI products. I frequently slag ESRI for bugginess and closed-ness, but they do just fine making a desktop platform for geospatial analysis. However they have never known what "Cartography" means (that's right, you take it to Illustrator if you want your map to look good), and they're just starting to realize that they don't know what "Web Mapping" means either. . .
. . . The "open-source alternatives" are not replacements for ArcGIS. But through advances in cartography and and browser-based distribution, open tools are unearthing the truth that the rest of us forgot about while sorting through ArcToolBox: that maps tell stories. That your data can be weighted, decoupled, buffered and regressed twenty ways and it means nothing if your cartography is crap. That you can drop cash on a printed poster with a sweet imagery background and it's lost to the ether if two people show up to your hearing, then you post it publicly as a PDF.
These are issues that bedevil public and private sectors, academic and amateur alike. But I say that you can make accurate yet artistic maps and deliver them in a way that is almost universally accessible (at least in the developed world). Let's make maps that people care about.
With the 'Why' of it behind, my next post will be an introduction to the 'How.'
"Toner" tiles by Stamen Design
. . . I'd like you to make maps intended for online viewing.
This is partially a selfish impulse; I'm going to throw a rock through the window if I see another "PDF Download" link masquerading as a web map. I'd also like you to do this to save a few trees from their 24"-by-36"-poster fate, but mostly it's because we're at an inflection point in cartography . . .
View Larger Map
Routing application with Google Maps
. . . I think the public - the folks who show up to input forums for development projects, and who want to know how far it is to the next lean-to on the trail - are now fully-literate in maps. Mapquest started this process and Google advanced it, but now there are tools beyond those to help you engage your audience on computers and mobile devices (No, Trimble, I am not referring to the Juno. Screw that.). Many of these tools happen to be open-source . . .
Ecoregions of New Zealand, hosted by Github
. . . If you currently describe yourself as a "GIS Analyst/Technician/Monkey" - as I did not long ago - your day largely consists of desktop GIS, and 95% of you are working entirely with some combination of ESRI products. I frequently slag ESRI for bugginess and closed-ness, but they do just fine making a desktop platform for geospatial analysis. However they have never known what "Cartography" means (that's right, you take it to Illustrator if you want your map to look good), and they're just starting to realize that they don't know what "Web Mapping" means either. . .
. . . The "open-source alternatives" are not replacements for ArcGIS. But through advances in cartography and and browser-based distribution, open tools are unearthing the truth that the rest of us forgot about while sorting through ArcToolBox: that maps tell stories. That your data can be weighted, decoupled, buffered and regressed twenty ways and it means nothing if your cartography is crap. That you can drop cash on a printed poster with a sweet imagery background and it's lost to the ether if two people show up to your hearing, then you post it publicly as a PDF.
These are issues that bedevil public and private sectors, academic and amateur alike. But I say that you can make accurate yet artistic maps and deliver them in a way that is almost universally accessible (at least in the developed world). Let's make maps that people care about.
With the 'Why' of it behind, my next post will be an introduction to the 'How.'
I am still amazed at how many end users prefer the PDF/PowerPoint format for products. It's the old "I have to use this in a meeting and a web map does me no good." A sad state of affairs when our 4G networks are faster than most town offices.
ReplyDeleteWe need to collect some examples of paper maps failing where web maps succeed. I offer as a first possibility the PlanBTV public input tool: http://www.burlingtonvt.gov/PlanBTV/map/
DeleteThis is a breath of fresh air-- and exactly what I have been thinking lately but couldn't articulate nearly as well as you have. I am really looking forward to making some web maps using your tutorial. Thank you!
ReplyDeleteThanks! Get some maps out there!
DeleteMaps on computers, whether web, pdf, or other, have some problems. With the equipment available to most people, they don't work in sunlight. Web maps don't work on the field for volunteers who don't have the money for a portable device with good graphics, nor do they have the money for the data plan that must accompany such a device. Web maps don't work after an ice storm destroys the cellular infrastructure. And all computer maps fail when the power outage lasts longer than your battery.
ReplyDeleteAgreed. Believe me, two years in the peace corps made paper seem really valuable to me. But more frustrating was the fact that I was trying to make paper maps on an old donated copy of ArcView 3.2, on a donated computer, on two hours of electricity per day. I'd argue that web maps support offline use better than desktop. Central information gathering, with truly appropriate offline technologies like this: http://walkingpapers.org/ or a cheap GPS (I could find AA batteries even in the backcountry of Haiti).
DeleteYour point is sound that not everyone can access online maps all the time, but I think a web backbone is much more useful to support the paper on the ground.