Via email I learned that the open source OSM2NetworkDataset version 1.1 is now available, it readies OpenStreetMap data for ArcGIS's Network Analyst extension.
From the announcement: "Version 1.1 now supports ArcGIS 10.0, as well as ArcGIS 9.3.1. New features include restrictions for tracktype, smoothness, surface, and maxwidth.
The Java application OSM2NetworkDataset converts OpenStreetMap (OSM) data so it can be used for network analyses in the ArcGIS extension Network Analyst. It is designed to generate transportation networks for any mode of transportation and any region. The generated networks are based on OSM attributes, such as restrictions, one-way roads, turn restrictions, point barriers, and maximum speed. The path can be chosen according to the shortest distance or the shortest time with user defined average speed settings."
While we mentioned it once before, it never got its full story, until now.
I haven't found much about it on the popular geoblogs, but I recently learned about the existence of Autodesk's free 123D 3D modeling software. It's at the 'beta 6' stage and available only for Windows. It clearly sounds like Google SketchUp competition from Autodesk. This reminds me of Project Butterfly, which got launched as AutoCAD WS, another free tool from Autodesk.
From the 123D about page: "123D is a free solid modeling software program based on the same Autodesk technology used by millions of designers and engineers worldwide. Not an engineer? No problem, with Autodesk 123D you can design precise and makeable objects using smart tools that let you start with simple shapes and then edit and then tweak them into more complex shapes."
Here's recent geospatial open source software releases. All minor but welcomed updates.
The highlights: "This release is a big one, closing over 380 outstanding tickets and providing significant performance improvements. The biggest win is the mobile support enhancements. OpenLayers now allows features to be dragged and zoomed with touch gestures on mobile devices. Handlers for pinching and zooming have also been added to the library. Other key highlights are the plethora of performance enhancements and the additional support for accessing Bing Maps tiles."
You can learn the details in the 2.11 release notes.
Jumping from version number 0.7.1, Mapnik 2.0 is a major release. While we mentioned Mapnik quite a few times, I don't hear that often about it. That said, many of us experience Mapnik frequently, since Mapnik is used for the rendering of OpenStreetMap's main map. Hey, Mapnik even participated to this year's WMS shootout.
Here's a reminder of what Mapnik is: "Mapnik is a Free Toolkit for developing mapping applications. It's written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.
Mapnik is about making beautiful maps. It uses the AGG library and offers world class anti-aliasing rendering with subpixel accuracy for geographic data. It is written from scratch in modern C++ and doesn't suffer from design decisions made a decade ago. When it comes to handling common software tasks such as memory management, filesystem access, regular expressions, parsing and so on, Mapnik doesn't re-invent the wheel, but utilizes best of breed industry standard libraries from boost.org."
Here's the list of major new features for Mapnik 2.0.
Here's the recent geonews in batch mode.
On the open source front:
On the Esri front:
In the everything-else category:
In the maps category:
Here's the recent open source geospatial news in batch mode, which includes everything about FOSS4G 2011 on the geoblogs that we haven't mentioned yet.
On the FOSS4G 2011 Conference front:
In other news:
You probably know what Git is, the modern distributed revision control system, replacing CVS and Subversion for many projects. Spatially Adjusted made me aware of the GeoGit approach.
Here's what the documentation written a month ago says: "Following on the core Versioning WFS work, in 2011 OpenGeo started experimenting with a new way to handle versioning, drawing on git, a distributed versioning system built for Linux and widely used. There are two different paths taken, both of which warrant further investigation:
The code for the core repository can be found at https://github.com/opengeo/GeoGIT . This code backs both a GeoSynchronization Service module (a spec by the OGC to synchronize data) and the versioning constructs of WFS2. The plan is to eventually get both in to the standard distributions of GeoServer.
For the geogit implementation we instead code things to be optimized for the fact that a typical geospatial representation doesn't have much nesting - it's just a bunch of features. The index is orthogonal, doesn't need to be part of the tree structure. But the problem we had when we tried to use straight git with lots of leafs is that it wouldn't really work. It doesn't scale to a single directory with millions of files."
What is GeoMondrian? "GeoMondrian is an open source Spatial OnLine Analytical Processing (Spatial OLAP or SOLAP) server, a spatially-enabled version of Pentaho Analysis Services (aka. Mondrian). As far as we know, it is the first implementation of such a server and it is open source! [...] GeoMondrian provides then a consistent integration of spatial objects into the OLAP data cube structure, instead of fetching them from an external spatial DBMS, web service or a GIS file. To summarize, GeoMondrian brings to the Mondrian OLAP server what PostGIS brings to the PostgreSQL DBMS, i.e. a consistent and powerful storage and querying for geospatial data!"
Via email I learned that a week ago ESA released a new version of their open source SAR toolbox named NEST, now at version 4B-1.0. This is their first major update this year. We mentioned NEST releases since 2008.
Supported product formats include:
What's new for version 4B: