Changes between Version 3 and Version 4 of Ticket #147


Ignore:
Timestamp:
Oct 12, 2011, 8:42:03 AM (13 years ago)
Author:
blammo
Comment:

Major Update to the incubation application. Consequence of the FOSS4G (2011) Denver conference and all the hallway conversations about moving GeoMoose along through Incubation.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #147 – Description

    v3 v4  
    22
    33Request for Project Incubation, Questionnaire:
     4'''
     5Project Name:'''[[BR]]
    46
    5 Project Name:
    67
    7 GeoMOOSE (or just MOOSE) -  http://www.geomoose.org
     8GeoMOOSE -  http://www.geomoose.org
    89
    9 Project Liason:
     10    '''1.) Please provide the name and email address of the principal Project Owner.'''
     11        Bob Basques is the primary project contact for Incubation (bob.basques ci.stpaul.mn.us )
     12    '''2.) Please provide the names and emails of co-project owners (if any).'''
     13        The GeoMoose PSC is listed below:[[BR]][[BR]]
     14        danlittle yahoo.com[[BR]]
     15        klassen.js gmail.com[[BR]]
     16        bfischer houstoneng.net[[BR]]
     17        eadam co.lincoln.or.us[[BR]]
     18        bfraser geoanalytic.com[[BR]]
    1019
    11 Bob Basques - bob.basques at ci.stpaul.mn.us
     20    '''3.) Please provide the names, emails and entity affiliation of all official committers'''
     21        bob.basques ci.stpaul.mn.us - The City of Saint Paul and SharedGeo[[BR]]
     22        danlittle yahoo.com - Excensus and Freelance [[BR]]
     23        klassen.js gmail.com - SharedGeo [[BR]]
     24        bfischer houstoneng.net - Houston Engineering [[BR]]
     25        eadam co.lincoln.or.us - Lincoln County [[BR]]
     26        bfraser geoanalytic.com - GeoAnalytics [[BR]]
    1227
    13 Co-owners:
     28    '''4.) Please describe your Project.'''
     29        i. GeoMOOSE is a browser based mapping framework for displaying distributed cartographic data. It is particularly useful for managing spatial and non-spatial data within county, city and municipal offices (from which GeoMoose originated). It extends the functionality of MapServer and OpenLayers to provide built in services, like drill-down identify operations for viewing and organising many layers, selection operations and dataset searches. GeoMoose is a client-side Javascript web interface that can be configured to use most raster based mapping engines. GeoMoose'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. Each layer is considered a service unto itself that GeoMoose is configured to access. This services architecture also extends to the integration of TOOLs in the GeoMoose presentation layer. More information is available here: http://www.geomoose.org/docs/geomoose_overview.html[[BR]]
     30        ii. GeoMOOSE is fast, performing well with hundreds of layers and/or services at a time. Data from multiple custodians can be maintained with different tools and on different schedules as each map layer has it’s own set of configuration files for publishing, symbols, templates as well as source data.[[BR]]
     31        iii. Templated (MAPBOOK) 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.[[BR]]
     32        iv. A very high level of extensibility exists with GeoMoose 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.[[BR]]
     33        v. It is a very extensible client for MapServer (and most other Map Services available) and adheres strongly to a Service-Orientated Architecture[[BR]]
     34        vi. It strives to be as REST-ful as possible.
     35    '''5. ) Why is hosting at OSGeo good for your project?'''
     36        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 GeoMoose project are in alignment with, and improve upon OSGEO goals. GeoMoose is built upon existing OSGEO projects, MapServer and OpenLayers. Design objectives include:[[BR]]
     37            i. Code must be developed in an Services Oriented Architecture.[[BR]]
     38            ii. Configurability for users.[[BR]]
     39            iii. Easy maintenance for data owners.[[BR]]
     40            iv. A client interface for MapServer and WMS, but designed to be open to other image and data server engines.[[BR]]
     41            v. Targeted use cases for local governments.
     42    '''6.) Type of application does this project represent (client, server, standalone, library, etc.):'''
     43        Client-side web interface framework
     44    '''7. ) Please describe any relationships to other open source projects.'''
     45        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 such as WMS services. The Windows Installer is built on top of the MS4W stack.
     46    '''8. ) Please describe any relationships with commercial companies or products.'''
     47        i. Implementation, Support and Customization - Houston Engineering plays a role in identifying and fixing bugs in the code as well as subsidizing of the programming costs via related projects. They focus on Windows based solutions.[[BR]]
     48        ii. Implementation, Support and Customization - SharedGeo has contributed code to both the GeoMoose (and MapServer) development communities as well as implemented and supported GeoMoose based services on primarily Linux.[[BR]]
     49        iii. Implementation and support - NorthStar Geographics have implemented and support GeoMoose based services.[[BR]]
     50        iv. Implementation and Support - MidwestGIS have implemented and support GeoMoose based services[[BR]]
     51        v. Training Materials - Open Technology Group - Mastering MapServer & GeoMoose[[BR]]
     52    '''9. ) Which open source license(s) will the source code be released under?'''
     53        http://www.geomoose.org/info/license.html
     54    '''10. ) Is there already a beta or official release?'''
     55        Numerous releases. Initial release was 1.0.  The current Stable release is 2.4, and and a Beta 2.6 release is available.
     56    '''11. ) What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)?'''
     57        The City of St. Paul, MN - Public Works Department started development of an AJAX interface for MapServer. 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 active developers and commercial interests maintaining the source code. GeoMoose has been implemented in many spatial data environments for Local, County, Regional and State governments as well as by commercial interests.
     58    '''12. ) Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point?'''
     59        i. Use of direct WMS feeds has been implemented, and as funding becomes available certification of this capability will be followed up on.[[BR]]
     60        ii. Use of OpenLayers provides support for it's many standard formats[[BR]]
     61        iii. Use of MapServer provides for it's many standard input formats[[BR]]
     62    '''13. ) Is the code free of patents, trademarks, and do you control the copyright?'''
     63        Yes
     64    '''14. ) How many people actively contribute (code, documentation, other?) to the project at this time?'''
     65        Six and a few others on email list and wiki
     66    '''15. ) How many people have commit access to the source code respository?'''
     67        Six
     68    '''16. ) Approximately how many users are currently using this project?'''
     69        i. The example page on the website will give an indication of how many folks are actively using the Package. [http://www.geomoose.org/wiki/index.php/GeoMOOSE_Gallery][[BR]]
     70        ii. The email list routinely reveals deployments throughout several continents. [[BR]]
     71    '''17. ) What type of users does your project attract (government, commercial, hobby, academic research, etc. )?'''
     72        The development environment was originally from a local City Public Works and focused on Infrastructure Maintenance Management business processes, but the code base is very flexible in nature and can be used for a variety of different business needs. The project allows a data manager to more easily distribute the data maintenance tasks as well as handle potentially many hundreds of layers in the publication process. The Promotional emphasis at this time is Government, primarily Local and Regional and related Commercial interests.
     73    '''18. ) If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation?'''
     74        We, the PSC, intend to use the OSGEO infrastructure where applicable. The GeoMoose Email lists have been moved to the OSGEO servers. And we, the PSC members, would actively support moving other aspects of the project support to OSGEO as needed.
     75    '''19. ) Does the project include an automated build and test?'''
     76        GeoMoose is available as a MS4W app and has recently been incorporated into the OSGeo Live DVD project to great success. There are also .tar.gz releases. There may be future work for inclusion with ubuntu-gis ppa. The build and tests are not currently automated.
     77    '''20. ) What language(s) are used in this project? (C/Java/perl/etc)'''
     78        i. PHP and JavaScript are the primary default languages.[[BR]]
     79        ii. There is some xml, html, .map, and other various minor parts.[[BR]]
     80        iii. Users could use Python, Ruby or other scripting languages.[[BR]]
     81    '''21. ) What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?'''
     82        English
     83    '''22. ) What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released?'''
     84        The current release size (v2.4 - GeoMoose core) is: 9.2mb[[BR]]
     85        The current release size (v2.4 - GeoMoose / MS4W) is: 10.3mb[[BR]]
     86        The current release size (V2.4 - GeoMoose / MS4W / WebMercator Demo) is: 47.6mb[[BR]]
     87        The project has been open sourced since 2006 and hosted at sourceforge. In the 2008 - 2009 time frame, GeoMoose was downloaded a over 3000 times.
     88[[BR]]
     89[[BR]]
    1490
    15 Jim Klassen - klassen.js at gmail.com [[br]]
    16 Dan Little - danlittle at yahoo.com [[br]]
     91[http://www.geomoose.org]
    1792
    18 Official Committers:
    19 
    20 Jim Klassen - klassen.js at gmail.com [[br]]
    21 Dan Little - danlittle at yahoo.com [[br]]
    22 Brian Fischer - bfischer at houstonengineeringinc.com [[br]]
    23 Bob Basques - bob.basques at ci.stpaul.mn.us [[br]]
    24 Brent Fraser - bfraser at geoanalytic.com [[br]]
    25 
    26 Description:
    27 
    28 Moose is a client-side Javascript web interface that can be configured
    29 to use most raster based mapping engines.  Version one which has just
    30 been released, is built against MapServer.   Moose's strengths include:
    31 Abstraction of mapping data layer control that enables individual data
    32 custodians to manage their own mapping data including cartography and
    33 frequency of updating.
    34 
    35 Template (MapBooks) methods for initialization of the interface
    36 display.  What this does is enables interface administrators, which need
    37 not be GIS and/or programming professionals, the opportunity to set up
    38 their own Mapping Web Interface that includes just those layers, tools
    39 and services they desire.
    40 
    41 High level of extensibility related to systems integration.   All Map
    42 Layers, Tools, and (other web) Services are defined inside of the
    43 MapBook and are easily accessible and interchangeable between
    44 interfaces.
    45 
    46 It is a very extensible client for MapServer (and most other Map
    47 Services available) and adheres strongly to a Service-Orientated
    48 Architecture
    49 
    50 It strives to be as REST-ful as possible.
    51 
    52 Why is OSGeo good
    53 
    54 There is a definite overlap in the Goals of the project with those laid
    55 out by OSGEO.  It is hoped that the design goals of the Moose project
    56 are in alignment with, and improve upon OSGEO goals.
    57  
    58 and DHTML technologies to interface with other web-clients. The primary
    59 target of Moose is for integration with the University of Minnesota's
    60 MapServer, but is not dependent upon it for operation. Design objectives
    61 include:
    62 
    63  * Code must be developed in an Services Oriented Architecture.
    64  * Configurability for users.
    65  * Easy maintenance for data owners.
    66  * A client interface for MapServer, but designed to be open to other
    67 server engines.
    68  * Targeted use cases for local governments.
    69 
    70 Type of application:
    71 
    72 Client-side web interface framework
    73 
    74 Other Open Source Projects:
    75 
    76 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
    77 can be coded against other server side engines.   
    78  
    79 The Windows Installer is built on top of the MS4W stack.
    80 
    81 Commercial relationships:
    82 
    83 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.
    84 
    85 License:
    86 
    87 http://www.geomoose.org/info/license.html
    88 
    89 Beta or official release:
    90 
    91 http://www.geomoose.org/info/download.html
    92 
    93 Origin of Project:
    94 
    95 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
    96 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.
    97  
    98 Open Standards:
    99 
    100 WMS client, WFS is planned.
    101  
    102 Is the code free of patents, trademarks, and do you control the
    103 copyright?
    104 
    105 Yes.
    106 
    107 Active Contributors:
    108 
    109 Five.
    110 
    111 Commit Access:
    112 
    113 Five
    114 
    115 Users (Administrative, as in own the application, or end users of all systems in place?):
    116 
    117 The example page on the website will give an indication of how many
    118 folks are actively using the Package.
    119 
    120 http://www.geomoose.org/gallery
    121 
    122 What types of users:
    123 
    124 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.
    125 
    126 OSGEO Project Member:
    127 
    128 We, the Project developers, believe that there are features in the
    129 Moose package of interest to OSGEO members and users.   The potential for the software to be used in other disciplines beside Government are
    130 many.  We believe that OSGEO is a good fit for promotion of the package if it sees fit to accept our project.
    131  
    132 Hosting on the OSGEO Website is not out of the question either.  We
    133 would be more than happy to move the host if it's deemed to be a better method for promoting participation.
    134 
    135 Build and Test:
    136 
    137 The install for Windows is built on top of MS4W, and there is a demo
    138 application included with the install for testing.  See the GeoMoose
    139 website for more information.  http://www.geomoose.org/demo/geomoose2/geomoose.html
    140 
    141 Language:
    142 
    143 Javascript
    144 
    145 Written Language:
    146 
    147 English
    148 
    149 Size of Package:
    150 
    151 8.75 MB (including the demonstration data, interface templates, Apache,
    152 Mapserver and  MS4W.) compressed. 14.1 MB uncompressed.
    153