<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Christopher,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Besides, everyone throw OpenLayers out there as an Option, I'm just
offering up another. :c)<br>
<br>
bobb<br>
<br>
<br>
Christopher Schmidt wrote:
<blockquote cite="mid:20080226210201.GA24941@alta.metacarta.com"
type="cite">
<pre wrap="">On Tue, Feb 26, 2008 at 01:20:28PM -0600, Bob Basques wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
What does GeoMoose do better than OpenLayers in this particular case, in
your opinion?
Regards,
</pre>
</blockquote>
</body>
</html>