Archive for December 2006
You know, when I first saw Ritchie’s GeoChat for ArcMap application I thought it was pretty cool, but didn’t have much use for it as it was closed-source and ArcMap-only.
I still think that it’s cool, and the release of GeoChat for ArcGIS Explorer, noted by James a few days ago got me thinking about it again.
Imagine users of GeoChat for ArcGIS communicating with users of GeoChat for OpenLayers, GeoChat for MapGuide, GeoChat for Foo. Imagine being able to engage in collaborative mapping with anyone that has a Google Talk account.
I don’t think that this too unrealistic. The ESRI GeoChat applications use an open protocol called XMPP, and the source code for both the ArcMap and the ArcGIS Explorer versions of GeoChat are now available from ArcScripts.
I have some concerns about the licensing (it shows as public domain on ArcScripts, but the license file indicates that there is proprietary third-party code included), but maybe the message creation portion of the code is open enough to form the foundation of an ad-hoc geospatial messaging standard. Does anyone else see value in this kind of cross-platform collaborative ability?
-J
Related posts
A new website has been added to the MapGuide Open Source Live Gallery, which includes three cool new sample applications and source code provided by Bob Bray, “The Autodesk MapGuide Guy”. These applications, including Dynamic Themes, Shareable Markups (redlining), and Ad Hoc Queries, show how powerful geospatial functions can be delivered through the web using MapGuide Open Source.
Dynamic Themes
Dynamic Themes allows the end user to apply a theme to an existing data set. For instance, a user can select the Parcels layer, choose the Net Value attribute, and create a colour ramp theming from yellow to red in six quantile breaks, with 30 percent transparency. Very cool.
Shareable Markups
Shareable Markups allow users to create their own shapes and text annotation on a map, and save them so that other users can see them too.
Ad Hoc Queries
Ad Hoc Queries allow users to query by attribute (for instance, all properties with value greater than 500,000) and by spatial filter (rectangle or polygon) and get back the matching set of features.
Together, these sample applications provide a framework that developers can extend to deliver robust geospatial functionality to their end users. They also show the depth and flexibility of the MapGuide APIs.
You can access this new set of applications and source code on the following website:
http://data.mapguide.com/mapguide/gt/index.php
-J
Related posts
Please download it and give it a try so that we can nail any bugs before the final release.
Biggest news:
- Initial KML support (see this anachronous RFC for basic documentation)
- FDO 3.2 compatible (first release with full source code for all OSGeo providers)
- Fixes to WMS/WFS
- Fixed multi-line tooltip in AJAX viewer
- Better support for certain ASP.Net features
- Updated documentation
also, at AU last week Bob showed off a couple really cool sample apps, and I understand that these should be posted (along with an updated copy of the developer guide zipfile) once he has recuperated and managed to talk someone into giving him the password to the server. 
… off to download.
-J
Related posts
I got back from AU last night (late) and am starting to catch up. I can’t understand how people find time to blog at conferences, but enjoyed reading Geoff Zeiss‘ blog about the MapGuide Users Meeting and community participation in the MapGuide project.
I was meant to speak at that meeting, but snow and Air Canada managed to conspire against me. I dodged the Nanaimo airport closure bullet by taking the ferry to Vancouver the previous night. Then my morning flight was cancelled, and I picked up another flight that would have got me to the hotel part way through the meeting but in time to speak. I sorted my wants from my needs and stored what would have been my checked baggage in Vancouver, got on the flight, and proceeded to wait in line for de-icing for an hour and a half. Arrgh…
At the meeting, I would have talked a bit about my history and how I got involved in the MapGuide Open Source project. More importantly, I would have been speaking on how MapGuide Open Source is going to benefit Autodesk customers, who are used to a completely closed development process on a proprietary product.
Geoff covered (and James reinforced) one of the main benefits: an open development model. By going through the RFC process, anyone can add features to the MapGuide code stream. This means that if a customer has a real need for a new feature, instead of waiting for Autodesk to make it a priority, they can either build it themselves or fund its creation, possibly in conjunction with other interested users. This is an extremely compelling feature from my viewpoint, and I have already taken advantage of it twice.
I would also have brought up another slightly less obvious advantage. Foresight. Autodesk typically has tight controls around revealing information on products that are currently under development. This can cause extreme headaches for users who are trying to do strategic planning around application development and upgrades. The open development process that comes with good Open Source projects gives these users unique insight into MapGuide, unlike any other product in the Autodesk line. This may be opening up a bit with Autodesk Labs (which is a good thing), but Open Source does it much earlier in the development cycle. An example of this is the roadmap that was posted by Joe Francica on the All Points Blog earlier this week. This road map is still tentative (most of the features on it have not gone through the RFC cycle) but is completely open. It will also become more dynamic as we move to a new project tracking system in the new year which integrates wish list items, RFCs, and road maps into a single view of the development.
There are, of course, other benefits to Open Source (such as license fees, freedom to modify, a community of support, and more) but it is likely that without education many Autodesk customers will not take advantage of these. To try to encourage involvement in the Open Source community, I was going to be talking about some ways that users could benefit from their involvement:
- contribute code: scratches your itch and reduces internal maintenance burden of custom code by placing it in the community’s care
- pay others to write and contribute code: same as above, but does not require internal resources, and helps build a community of expertise around MapGuide
- work with consultants who have a history of contributing to MapGuide: these consultants will thrive, adding new features to the code that you can take advantage of in the future
- participate on the mailing lists, help with documentation and examples, spread the word: your participation will draw others to the community, which increases the rate of code contributions you can leverage
As an example of the third point, I would have been shown how DM Solutions Group’s Fusion application development framework can be leveraged to create maps with compelling designs and user interfaces. This framework has been developed in large part through the work DM Solutions has done for clients like the City of Nanaimo, such as our Fusion / MapGuide Cemetery application which should be released to the public sometime early in the new year. Here’s a screenshot (click for a larger image):
The City of Nanaimo is also working on a Fusion / MapGuide rewrite of our CityMap application which should have betas going public around the same time as the Cemetery map goes live.
AU was great by the way. Much like the ESRI UC (drink the kool-aid), but with a sexier presence. There’s definitely a male predominance at the show. As Lynn joked at the entertainment event on Thursday night, AU is a great place for women… there were lines at the men’s washrooms and not at the women’s.
-J
