OK, since someone already trolled about Google Maps (in a poorly reasoned way), I'll lodge my own curmudgeonly criticism: mapping is rarely the way to solve anything.
Especially in New York, and with standard Google Maps service, it's not hard to find where things are. It's hard to find that they exist -- and, if they do, whether they fit your need...and clicking around on a map is not the efficient way to do it. Nor to enumerate it.
Even the most famous map -- John Snow's cholera map -- was not revolutionary in itself. Snow didn't find out anything from mapping, it was just part of the documentary process and the one made famous by Tufte. But Snow himself would've concluded that the map was of little evidence, because such maps were used to prove the miasma theory that he was trying to disprove. And his map, without the data that he collected, fell into this visual trap.
So what is the way to do things? Use a spreadsheet. Think about the important facets about each entry. And hell, one of those could be "address", and in literally one step, you can also make a map out of it if you want.
And when I mean "especially in New York", I mean that geographical distance is not the most useful metric. Even when it comes to geography. I prefer proximity to what subway station, and that is a kind of metric that is obscured/obfuscated by a map
The map itself may not be a way to solve anything, but the data it's collecting could be. Like you say, you prefer knowing proximity to subway stations - not just seeing a map. But the need to figure out that proximity is what makes collecting locational data (in a fun and user-friendly way, like OP's map) so important.
Regarding my apparent trolling, I think HN may have missed my point. Using the Google Maps API implies agreement to their ToS, which restricts one from using non-Google basemaps, and limits usage of the map in certain ways. While many people ignore, or are never affected, by usage limits, this still obligates developers to Google's quotas and pricing tiers (updated significantly in late 2013). There are other, similarly-implemented mapping APIs with more options, where you aren't locked-in to a particular vendor's load quotas. Tying OP's project to this particular API is a bit like saying "Support Local Businesses! ...click here for our Cafe Press site."
Thank you for more information on your critique. I'm not familiar with how Google leases out their mapping software, but it sounds like it's definitely worth having a conversation about. Unfortunately, I'm in no ways tied to Freelancer's Union - Just admiring from afar.
Comments
OK, since someone already trolled about Google Maps (in a poorly reasoned way), I'll lodge my own curmudgeonly criticism: mapping is rarely the way to solve anything.
Especially in New York, and with standard Google Maps service, it's not hard to find where things are. It's hard to find that they exist -- and, if they do, whether they fit your need...and clicking around on a map is not the efficient way to do it. Nor to enumerate it.
Even the most famous map -- John Snow's cholera map -- was not revolutionary in itself. Snow didn't find out anything from mapping, it was just part of the documentary process and the one made famous by Tufte. But Snow himself would've concluded that the map was of little evidence, because such maps were used to prove the miasma theory that he was trying to disprove. And his map, without the data that he collected, fell into this visual trap.
So what is the way to do things? Use a spreadsheet. Think about the important facets about each entry. And hell, one of those could be "address", and in literally one step, you can also make a map out of it if you want.
And when I mean "especially in New York", I mean that geographical distance is not the most useful metric. Even when it comes to geography. I prefer proximity to what subway station, and that is a kind of metric that is obscured/obfuscated by a map
I agree with you, in a way.
The map itself may not be a way to solve anything, but the data it's collecting could be. Like you say, you prefer knowing proximity to subway stations - not just seeing a map. But the need to figure out that proximity is what makes collecting locational data (in a fun and user-friendly way, like OP's map) so important.
Regarding my apparent trolling, I think HN may have missed my point. Using the Google Maps API implies agreement to their ToS, which restricts one from using non-Google basemaps, and limits usage of the map in certain ways. While many people ignore, or are never affected, by usage limits, this still obligates developers to Google's quotas and pricing tiers (updated significantly in late 2013). There are other, similarly-implemented mapping APIs with more options, where you aren't locked-in to a particular vendor's load quotas. Tying OP's project to this particular API is a bit like saying "Support Local Businesses! ...click here for our Cafe Press site."
Thank you for more information on your critique. I'm not familiar with how Google leases out their mapping software, but it sounds like it's definitely worth having a conversation about. Unfortunately, I'm in no ways tied to Freelancer's Union - Just admiring from afar.