[mapserver-users] Advice for MapServer project

[Bob Basques]

Christopher,

The setup of the interface as well as the data sources are all 
abstracted to the point that each individual data custodian, and/or 
service owner, can implement their respective dataset/service in their 
own way and update it as frequently, or infrequently as they desire.

Everything in GeoMoose, including the Nav tools, are considered a tool 
or service of some sort, so it's very easy to add others to the mix.  
The administration of the data maintenance is also a big difference 
compared to other pacakages, because once the layer/service  is 
implemented via GeoMoose, it's up the layer/service providor to keep it 
maintained into the future.   Since everything is a service of some 
sort, these services can all be maintained and authenticated in any 
manner the custodian/owner want to use.

GeoMoose is aimed at datasets that change fairly often, on the order of 
hours or minutes, and is intended primarily to access this type of data 
set.  OpenLayers with it's Tiled interface seems to be intended for 
displaying datasets that tend to be more static in nature.  Now, either 
of the two packages can can be used for each others capabilities, but 
GeoMoose was built from the ground up based on a asset management type 
of business need with mapping as the visual identifier.

One last item, is that GeoMoose the interface is initiaqlized from a XML 
file, a MAPBOOK, so setting up business specific interfaces is very 
easy.  This XML file is even something that can be automated, so that an 
online method of setting up a Mapping interface could be built, and is 
something that is planned for as well.

Besides, everyone throw OpenLayers out there as an Option, I'm just 
offering up another.  :c)

bobb


Christopher Schmidt wrote:
> On Tue, Feb 26, 2008 at 01:20:28PM -0600, Bob Basques wrote:
>   
>> Timothy,
>>
>> This is an excellent project for GeoMoose to act as the mapping engine 
>> for.  It's precisely the sort of thing that the GeoMoose client 
>> framework was designed for.   You can set up GeoMoose fairly quickly for 
>> the mapping aspects, and the overlay pieces can be added on with some 
>> custom work by yourself via additional services.
>>     
>
> What does GeoMoose do better than OpenLayers in this particular case, in
> your opinion?
>
> Regards,
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20080226/20919066/attachment.htm>