I'm curious to see what follows this story out of Kansas. Equal time for Intelligent Flattening as an alternative to projections in Geography classes?
Last night I read much of Producing Open Source Software [link] by Karl Fogel, and then implemented some of his recommendations. I'd been overlooking the need to make it explicit that the Python Cartographic Library is open source, and also retooled the mission statement.
The goal of PCL is to completely replace MapServer's mapscript and become the way for Python programmers to use the C/C++ open source mapping software stack composed of PROJ.4, GEOS, GDAL/OGR, and MapServer. MapServer's mapscript module, my ward of the past few years, has an awkward, un-Pythonic API that routinely trips up programmers. MapServer is mature software and strongly obliged to be backwards compatible with old scripts, so while I've been able to fix many of its bugs and plug memory leaks, its clunky API is pretty much carved in stone. PCL, on the other hand, behaves like one expect a Python package to behave. It has actual classes, iterators, docstrings, unit tests, and warm fuzzy feelings. It is what Python programmers should be evaluating for use with new projects.
A larger goal of mine is to see something like SciPy for geospatial programming. PCL could be the cartographic component, PySAL might be the spatial analysis component. Hobu, who pointed me at Fogel's book, has been talking about overhauling the old PyOGCLib; that might provide a component for parsing and writing GML, and working with OGC W*S protocols.
I've been maintaining HTML versions of the mapscript docs on this site, but am going to redirect users to the new MapServer site starting today. See the note at http://sgillies.net/mapserver/.
I have nothing much to say about ArcGIS Explorer other than that the buzz about it is starting to remind me of the "Gabbo" ad blitz in The Simpsons episode 9F19 (Krusty Gets Kancelled).
Tyler Mitchell, author of Web Mapping Illustrated, has been talking up the idea of a MapServer Foundation for a while. Recently, he's taken his advocacy to the next generation MapServer site (login required) and invited discussion and comment on the proposal.
I wrote previously about MapServer and foundations. While I think that MapServer needs higher quality stewardship than is currently provided by the University of Minnesota, I think that a foundation is probably overkill. But that's just me; many MapServer users would welcome the right kind of foundation, one that really looks out for the integrity of the software above all else. In my opinion, a good foundation would be formed through a public and democratic process that emphasizes openness and consensus. If the grassroots really want a foundation, I'd like to be part of such a process.
The wrong way to launch a MapServer Foundation would be to begin in secret, and orchestrate the incorporation for the competitive advantage of a few select entities. The Mambo Foundation Fiasco provides us a great recent example of how to screw up a foundation in exactly this way. Any future MapServer Foundation, no matter how well intentioned, has to begin in the open or risk a FUBAR state.
Update: my mistake, login is not necessary.
Update 2: It seems that some are reading "login required" as "top secret". Sorry to disappoint, but you're reading too much into this. I merely mistook the publication state: Tyler's proposal is not the Doomsday scenario at all. I welcome his effort to persuade the user base of the benefits of a foundation. Although I'm not personally persuaded, I think his proposal is a must-read for MapServer users, and could be the catalyst for a grassroots initiative.
Update 3: my Doomsday scenario bears some resemblance to the current state of affairs, does it not?
It's true that the geospatial blogosphere has been pretty quiet about this issue. I've been thinking about it a lot, but have avoided writing about it until I had something coherent to say. Adena's pointed questions have helped me, and I hope that will others ask themselves and share their thoughts.
I do care about the future of mapping at the USGS. Public geodata and maps, maintained by and for We the People, is a good thing. Census boundaries, voting districts, boundaries of our public lands and waterways, etc, all these should be freely available to the public forever. I hate to start dropping buzzwords so early into this post, but open geodata is fuel for the small organizations and companies that operate in the long tail of GIS. A grade school class can't afford to buy data from NavTech for a class mapping project, and shouldn't be dependent on the largesse of data providers. The same goes for a local non-profit mapping the demographics of their community. Open geodata helps these people get in the game.
That said, mapping is no longer region-specific, and I lean in favor of a consolidation of the centers. There is a world-class Tropical Meteorology group here in Fort Collins (smack in the middle of the continent at 40 degrees North and 1500 meters above sea level) at CSU's Department of Atmospheric Science; you don't have to be physically located in a particular region of the world in order to study or catalog its properties. If we can save some money by shutting off the A/C, lights, and sprinklers at a few sites, I am all for it. Realistically, these operating expenses are smaller than the payroll, but every little bit helps.
I have mixed feelings about moving the mapping duties of the USGS to the private sector. The notion that the private sector is always more efficient than government is largely a myth, albeit a popular and powerful myth in our society which puts doctrine and faith ahead of reason and analysis. The more important factor is the level of maturity and inertia in an organization, whether public or private. I'd like to see the evidence that Raytheon/IBM/Microsoft, private sector monoliths, could run our public geodata and mapping operations any more effectively than a consolidated, ship-shape USGS. As Adena notes, the USGS is already heavily partnered with such companies now. If we go even further in this direction, I fear more outdated (Web 1.0) boondoggles such as the Geospatial One-Stop. It's fresh out of 1995, and we're using it as much as we listen to Rednex on our iPods. That's not at all for you old folks ;) Instead, let's try to invigorate the USGS with fresh, cutting edge ideas from universities and smaller companies that are still in their early innovative stage.
Now, let's find out if there is anything to these assertions of cronyism. If so, a reorg of the USGS is only going to bring more of the status quo.
Correction: a reader, who understandably wishes to remain anonymous, points out that my original musical reference, Vanilla Ice, predates mainstream emergence of the web.
I've heard bits and pieces already, but now Hobu takes Directions readers inside katrina.telascience.org.