High Seas by AJ Ashton. Pirate by Lego, clearly. |
- Step 1: ESRI rumbles toward a unified way of getting licenseholders' data online, while pulling a group of early innovators - GeoIQ - onboard to help. Admirable.
- Step 2: ESRI adopts the term "Web Map" along with "Story Map" and a few other items that they clearly stole. No worries; a bit of rebranding and we're all one big-happy-web-mappy family, ESRI, Google, FOSS4G and your grandmother with her Bing API side project.
- Step 3: ESRI kicks everyone else off the boat they just boarded. Now only ESRI makes "official" web maps, and clients should be wary of cut-rate imitators. Specifically a "Web Service" is only an ESRI REST service, and a "Web Map" is "[Like an] .mxd file, but for the web."
Fair play to the big guy with the marketing budget, you say. But here's why I want the developers that built this ship to retain control of it: THEY'RE BETTER AT IT. The user experience is uniformly superior in non-ESRI web maps, the implementation costs are lower and the data is faster. Though this will change and ESRI will catch up if new hires like Sean Gorman have anything to say about it.
But for now I would love to see a bit of humility and willingness to listen on the part of the GIS giant, instead of taking the ship by storm and kicking off everyone who knows how to steer it.
This comment has been removed by a blog administrator.
ReplyDeleteHi Jeremy (and sorry to pull the comment; the link was flagged),
DeleteI wholeheartedly agree that ESRI is the finest GIS platform out there. I have ArcMap open on my machine right now, doing a task that is still vastly easier in that platform: raster georeferencing. QGIS has come to replace ArcMap for many things in my portfolio, but that has a lot to do with my dedication to open-source development. That's not exactly what I'm ranting about above, because I don't think web mapping IS GIS as we currently understand it.
I'm talking about a different way of getting geographic information to the client end, intended as real cartography and separated from the geoprocessing (Which GIS analysts do anyway. How many time does "working.mxd" appear in your file tree?). Integrating the two is an admirable goal (props again to GeoIQ), but the public doesn't want "GIS in the cloud" to be the application with which they interact (Brian Timoney nailed it here:http://bit.ly/N1mwTS). ESRI is not good at this part, but they seem hell-bent on edging out the people who are. I object, and plan to continue objecting until ArcGIS Online isn't turning out this kind of map crap anymore: http://bit.ly/S61Zl3. At that point I'll probably add it to my toolkit.
Keep fighting the good fight, in any case. We all benefit when the discussion turns away from data-crunching and toward information design.