Stories
Slash Boxes
Comments

In+ersec+ion for Spatial People

GeoMoose 1.6 Released

posted by Satri on Thursday November 20, @01:20PM   Printer-friendly   Email story  Permalink  Trackback URI  Slashdotthis  Diggthis  Del.icio.us
from the mapping-more-than-animals dept.
An anonymous voxel writes "The Moose herd is pleased to announce that GeoMoose 1.6.1 has been officially released. * Release History * Documentation * Download (GeoMoose 1.6.1 with MS4W) * Download (GeoMoose 1.6.1 [SourceForge]). The GeoMOOSE project is client-side mapping code that uses a variety of JavaScript, XML, and DHTML technologies to interface with other web-clients. The primary target of GeoMoose is for integration with the UofM MapServer, but it is not dependent upon it for operation. Design objectives include:
      * Code must be developed in an Services Oriented Architecture.
      * Configureability for users.
      * Easy maintenance for data owners.
      * A client interface for MapServer, but designed to be open to other server engines.
      * Targeted use cases for local governments.
For more information about GeoMoose, go to: * http://www.geomoose.org/moose/."
We mentioned GeoMoose before.

Related Stories

Technology: GeoMoose 1.2.0 Released [+]
The OSGeo-Announce mailing list informs us the GeoMoose open source webmapping project has released its version 1.2.0. From the GeoMoose website: "GeoMoose is a Web Client Javascript Framework for displaying distributed cartographic data. Among it's many strengths, it can handle large numbers of mapping layers, all mapping display is abstracted to separate layers. This allows for the abstraction of the maintenance and updating tasks as well. Since each display layer is abstracted in this fashion, it allows a site administrator to concentrate on running the overall system while leaving the data upkeep and publishing tasks to the respective data custodian. No more hand-off of the data to a "Publisher" is required, the data custodian can handle the publishing tasks on their own, including the frequency of updates." And on the extended page: "[...] GeoMoose is designed around the idea of using Web based URL services as an integration method. [...] GeoMoose is currently built as a front end to MapServer (CGI)." Main recent MapServer stories copied below.
Technology: MapServer 5.2.0 is out. [+]
Anonymous Voxel writes "The release of MapServer 5.2.0 was announced yesterday, featuring a variety of improvements. My personal favourite is the improved AGG rendering, and especially the ability to apply transparency at the style level — which essentially means you can visualize layers that have overlapping features by setting the opacity for the styles (instead of the entire layer after it is rendered)."
GeoMOOSE 2.2 Released [+]
The open source project GeoMOOSE 2.2 has been released two weeks ago. Since it's been a while we mentioned the GeoMOOSE project, here's a reminder of what it is: "GeoMOOSE is a Web Client Javascript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server. The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic webserver (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search datasets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written." See also related stories below.
This discussion has been archived. No new comments can be posted.
Display Options Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.