Incubator Application: GeoMOOSE

[warmerdam]

Incubator Application Committee,

Request for Project Incubation, Questionnaire:

Project Name:

GeoMOOSE (or just MOOSE) - ​http://www.geomoose.org

Project Liason:

Bob Basques - bob.basques at ci.stpaul.mn.us

Co-owners:

Jim Klassen - klassen.js at gmail.com
Dan Little - danlittle at yahoo.com

Official Committers:

Jim Klassen - klassen.js at gmail.com
Dan Little - danlittle at yahoo.com
Brian Fischer - bfischer at houstonengineeringinc.com
Bob Basques - bob.basques at ci.stpaul.mn.us
Brent Fraser - bfraser at geoanalytic.com

Description:

Moose is a client-side Javascript web interface that can be configured to use most raster based mapping engines. Version one which has just been released, is built against MapServer. Moose's strengths include: Abstraction of mapping data layer control that enables individual data custodians to manage their own mapping data including cartography and frequency of updating.

Template (MapBooks) methods for initialization of the interface display. What this does is enables interface administrators, which need not be GIS and/or programming professionals, the opportunity to set up their own Mapping Web Interface that includes just those layers, tools and services they desire.

High level of extensibility related to systems integration. All Map Layers, Tools, and (other web) Services are defined inside of the MapBook and are easily accessible and interchangeable between interfaces.

It is a very extensible client for MapServer (and most other Map Services available) and adheres strongly to a Service-Orientated Architecture

It strives to be as REST-ful as possible.

Why is OSGeo good

There is a definite overlap in the Goals of the project with those laid out by OSGEO. It is hoped that the design goals of the Moose project are in alignment with, and improve upon OSGEO goals. and DHTML technologies to interface with other web-clients. The primary target of Moose is for integration with the University of Minnesota's MapServer, but is not dependent upon it for operation. Design objectives include:

• Code must be developed in an Services Oriented Architecture.
• Configurability 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.

Type of application:

Client-side web interface framework

Other Open Source Projects:

Initial development has been focused on using MapServer as the Server side Component. The Map UI is based on the OpenLayers display Library. The Code base does not require MapServer and can be coded against other server side engines. The Windows Installer is built on top of the MS4W stack.

Commercial relationships:

Houston Engineering plays a central role in identifying and fixing bugs in the code as well as subsidizing some of the programming related costs via related projects.

License:

​http://www.geomoose.org/info/license.html

Beta or official release:

​http://www.geomoose.org/info/download.html

Origin of Project:

The City of St. Paul, MN - Public Works Department started development of an AJAX interface for MapServer ( ​http://mapserver.gis.umn.edu/ ). The AJAX client code was released in late 2006 by the City of St. Paul as open source for others to use and in hopes it would initiate a developer community to help maintain and contribute to the source. The AJAX client code has been given the name GeoMOOSE. Today there are a handful of active developers maintaining the source code. An initial project that GeoMoose was a part of was an FGDC funded project called OpenMNND ( ​http://www.openmnnd.org/ ) which had choosen GeoMOOSE as the foundation for their client application. Open Standards:

WMS client, WFS is planned. Is the code free of patents, trademarks, and do you control the copyright?

Yes.

Active Contributors:

Five.

Commit Access:

Five

Users (Administrative, as in own the application, or end users of all systems in place?):

The example page on the website will give an indication of how many folks are actively using the Package.

​http://www.geomoose.org/gallery

What types of users:

The development environment was originally in Public Works and focused on Infrastructure Maintenance Management business, but the code base is very flexible in nature and can be used for a variety of different business needs. The Promotional emphasis at this time is to Government, primarily Local and Regional.

OSGEO Project Member:

We, the Project developers, believe that there are features in the Moose package of interest to OSGEO members and users. The potential for the software to be used in other disciplines beside Government are many. We believe that OSGEO is a good fit for promotion of the package if it sees fit to accept our project. Hosting on the OSGEO Website is not out of the question either. We would be more than happy to move the host if it's deemed to be a better method for promoting participation.

Build and Test:

The install for Windows is built on top of MS4W, and there is a demo application included with the install for testing. See the GeoMoose website for more information. ​http://www.geomoose.org/demo/geomoose2/geomoose.html

Language:

Javascript

Written Language:

English

Size of Package:

8.75 MB (including the demonstration data, interface templates, Apache, Mapserver and MS4W.) compressed. 14.1 MB uncompressed.