From the intro: "[...] we’ll lay out some major drawbacks of standard web portals as well as suggest a few alternatives along the way. While the baseline scenario I have in mind are public-facing government mapping portals, those rolling corporate intranet solutions would do well to take heed."
Some quotes taken from the entries, but go read the full 5 entries, it's worth:
Because if you are building any public-facing interface you have exactly four requirements: FAST • INTUITIVE • INFORMATIVE • FAST
The GeoServer team is happy to announce the release of GeoServer 2.2.4, now available for download.
This is the latest release of the stable 2.2 series. The changes that might interest the most users are:
The changelog also contains the following minor bug fixes
Also, looking at the corresponding GeoTools release changelog we have the following extra goodies in:
Thanks again for using GeoServer!
From the announcement: "Rejoice, everyone — after 4.5 months of development with 26 contributors involved since the previous major release, I’m happy to announce the release of Leaflet 0.5 stable, hooray!
0.5 highlights include IE10 touch devices and Metro apps support, retina-enabled markers, a much better panning inertia implementation, hand cursors for dragging and a new zoom control design. But the real power of this release comes with about a hundred of subtle improvements and bugfixes, improving usability, performance and overall “feel” of browsing the map even further."
Directions Mag offers an article named Research Explores How to Keep Up With Changing Web Mapping Technology, starting with 'change is inevitable: deal with it'.
From the results: "Despite the fact that the Google Maps API delivered on more of the requirements set out in the Needs Assessment Survey, the team selected Leaflet as the answer to the first question of which technology should be used for teaching. Leaflet was, in fact, second best in supporting the requirements, but the Diary Study suggested students made more progress and felt better working with that set of libraries. The team suggests that might be due to the added transparency and control provided by a fully open source library."
The major features of 6.2:
Here's the latest batch-mode edition of the geonews.
From the open source front:
From the Esri front:
From the Google front:
In the miscellaneous category:
And finally, at the suggestion of a Slashgeo user which made a donation, we added a 'Paypal button' to ease the process of making donation to Slashgeo.
One of the main open source competitors to OpenLayers, Leaflet 0.4.5 has been released and they share their plans for version 0.5.
From the announcement: "Highlights of things already implemented in the
master branch include touch interaction support for IE10 touch devices and Metro apps and a more smooth and responsive panning inertia. Follow the full changelog for more details. We’re also in the process of a major refactoring of vector rendering code to allow much simpler extension of base functionality with custom shapes, additional rendering systems (like WebGL in addition to existing SVG/VML and Canvas renderers), easy switching between renderers, also making the code simpler and easier to understand. The same goes for projection-related code to make using Leaflet with non-standard projections easier, inluding plain projections for game and indoor maps."
The project that initially emerged from Autodesk and became MapGuide Open Source just released its version 2.4.
I haven't found a summary of the changes so far. There seems to be numerous improvements to MapGuide OS's core, to Fusion Tools and FDO. Here's what looks like their list of major new items:
My main question when MapGuide Open Source comes to my mind: what's the status of its adoption? I had a lot of hopes for it when Autodesk made MapGuide open source along with providing the financial support for OSGeo's birth, but it seems like MapGuide does not get much love nowadays, at least not as much as competing solutions like GeoServer and MapServer. Any comments?
The Cartography and Geovisualization Group at Oregon State University has been experimenting with ways to improve web mapping. An OSU summary page explains the current situation:
"Today's web maps (such as those by OpenStreetMap, Google, Bing, or Yahoo!) have two major shortcomings.(1) They use the Mercator projection for all scales and for all locations, and(2) they only provide pre-rendered views for a series of predefined scales."
Almost a week ago, one of the most popular web mapping server engine has been updated, GeoServer 2.2 has been released. As they wrote: "The release of a new major version update is a big deal (the last one was over 16 months ago) [...]", here's some of the highlights, follow to link to get the full overview!
And much much more...