Ok, I’m probably not the first one to write a post about falsehoods programmers believe about maps, but I still remember reading “Falsehoods programmers believe about names” and “Falsehoods programmers believe about time“, and thinking “there should be a post like that about maps”. So, go ahead, read those two posts to get to know the style of a post like this and then read on here.
- All coordinates are in “Latitude/Longitude” (Why is this false?)
- If you know the “Latitude/Longitude” you can be certain of exactly where you are
- “Spatial is special”
- The earth is round (Why is this false?)
- The earth is ellipsoidal (Why is this false?)
- The GPS-satellites know where I am
- There is a single, right, map projection
- Scale numbers works on a screen (Why is this false?)
- There are no good alternatives to Google Maps
- Web Mercator works for all purposes
- The shortest path between two points is a straight line
- All programmers agree on the ordering of latitude and longitude pairs
- Given a paper map I can always digitize and georeference it
- My background map will be better if I cache it, always!
- GIS software is always expensive
- The whole world is mapped, thouroughly
- Looking up a street address and get it’s position is easy
- Offline maps is as easy as Goole Maps
That’s what I’ve come up with this far, I might fill in something here when I think about it. Comments? Additions? Any errors? Want citations? Well, the comment section is open, so go ahead!
This is good stuff, and some of it new to me, but I think it would be a lot more useful if there were explanations for why these are falsehoods. The same goes for those two posts you linked to.
Of course, such a post would also be a lot more work. 🙂
I agree with you on the explainations, on all points there (especially the last one I guess). But, maybe the “debunking” part could be material for some more blog posts, any of the myths that needs more explaination than the others?
Sure, doing it as more blog posts might work just as well. People seem to prefer shorter posts.
I’m afraid I don’t know any programmers (who work with maps) who believe more than one or two of these. While entertaining, this list has the look of the same straw man argument that popped up here a little while ago. Can we at least have some anecdotes about where these come from?
Bill: First of all; this is in no way meant as a “I know better than everyone else, listen to the expert here”. And, second: I’m rather sure that programmers that work with maps know these things (I’m myself a programmer who works with maps).
I haven’t read the blog post you are referring to, but I sure will. I am convinced that there are a lot of programmers who are great at maps (and I’m sure a lot of them will be in Portland next week).
So: bottom line: this is not a blog post saying that programmers shouldn’t work with maps, but a lighthearted way to point out some progammers perhaps have a rather shallow understanding of maps. Some of these falsehoods originate from people I’ve spoken to, some from places like stackexchange/stackoverflow and some are things I suspect that some programmers think (so: no scientific research base here).
Gotcha. I tend to hear a lot of reactionary stuff from the GIS community, understandably terrified of developers taking their jobs, so I’m probably a bit more sensitive than most. We can certainly all stand to laugh at the holes in our knowledge.