<!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">
I know what you mean about different applications of XML. However, can
a single file or format serve both needs? KML is an output format and
used in many programs but it can be viewed as a map description format
as well: it can point to multiple datasets, access dynamic web services
and WMS, adds style information, screen overlays, and more. Aside from
inclusion of coordinates/geometry of vectors data instead of
referencing a vector dataset, KML seems to do accomplish similar tasks
as map files. I've always thought KML becomes difficult to share when
locally referencing large rasters; KML as input to a map server engine
would solve that.<br>
<br>
It would be huge stretch to make something like this work but the lure
of incorporating the successes of KML into an open source project (as
something more than just an output format) just got me wondering.
Even converting KML files to map files (placemarks/paths/polygons
become shapefiles) may be beneficial. Just some thoughts...<br>
<br>
- John<br>
<br>
<pre class="moz-signature" cols="72">****************************************
John Callahan
Geospatial Application Developer
Delaware Geological Survey
University of Delaware
227 Academy St, Newark DE 19716-7501
Tel: (302) 831-3584
Email: <a class="moz-txt-link-abbreviated" href="mailto:john.callahan@udel.edu">john.callahan@udel.edu</a>
<a class="moz-txt-link-freetext" href="http://www.dgs.udel.edu">http://www.dgs.udel.edu</a>
****************************************</pre>
<br>
<br>
Bob Basques wrote:
<blockquote cite="mid:484FAB62.163B.00A8.0@ci.stpaul.mn.us" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2800.1505" name="GENERATOR">
<div>John,</div>
<div> </div>
<div>You're starting to think about two different applications of
XML. I was interested in setting up the XML to reflect the typical
MapFile contents and use the XML for the Map generation out of
MapServer. KML is a output format option, that would be output by
MapServer, (possibly using this new XML MapServer control) to format
the KML output.</div>
<div> </div>
<div>I would still tend to keep the configurations as file based as
well, the DB approach just aloows for much more flexibilty for those
hardcore programmers, and the MapFiles, don't input into a DB very
easily.</div>
<div> </div>
<div>bobb</div>
<div><br>
<br>
>>> John Callahan <a class="moz-txt-link-rfc2396E" href="mailto:diodata@udel.edu"><diodata@udel.edu></a> wrote:<br>
</div>
<div
style="border-left: 1px solid rgb(5, 5, 5); margin: 0px 0px 0px 15px; padding-left: 7px; background-color: rgb(243, 243, 243);">Is
it possible to allow MapServer to use KML, or a variation thereof? <br>
I really don't what would be entailed. For example, KML can store <br>
coordinates for displaying vectors, which would be pointless in our <br>
context. Can KML point to shapefiles or tables for vectors like it can
<br>
point to TIFs for rasters? If so, it seems like the infrastructure <br>
(styling, external editing packages, viewers, conversion tools, wide <br>
adoption) is already there to build on. Can we pull pieces from KML to
<br>
make it easier for people to adopt without learning a new structure?<br>
<br>
+1 on keeping the configuration maps as file based. Databases are
great <br>
for many reasons but add an entirely new level of complexity (and
points <br>
of failure) for any application.<br>
<br>
- John<br>
<br>
****************************************<br>
John Callahan<br>
Geospatial Application Developer<br>
<br>
Delaware Geological Survey<br>
University of Delaware<br>
227 Academy St, Newark DE 19716-7501<br>
Tel: (302) 831-3584 <br>
<br>
Email: <a class="moz-txt-link-abbreviated" href="mailto:john.callahan@udel.edu">john.callahan@udel.edu</a><br>
<a moz-do-not-send="true" href="http://www.dgs.udel.edu/">http://www.dgs.udel.edu</a><br>
****************************************<br>
<br>
<br>
<br>
Barend Kobben wrote:<br>
> Hi Bob,<br>
><br>
> YES, by all means do move to XML. I think this would be a very
important<br>
> step forward (and my first guess is it would be not too
complicated, but you<br>
> never know...). <br>
><br>
> I do see how some might be attracted to having an DB storage too,
but I<br>
> would urge you to always have that as an alternative, not as
instead-of:<br>
> keep the main configuration mechanism (XML-)file based! In many
use cases<br>
> there's no need for a DB and that would mean you'd have tho have a
DB plus<br>
> all its hassle, only for the configuration part. Also the current
file-base<br>
> config is ideal in situations were many people need to work on the
one MS,<br>
> such as in our educational setup, where we have many students
working on<br>
> their own config files in their private dirs, and they don't need
to touch<br>
> the 'main' MS setup on the server.<br>
><br>
> Actually, what are your reasons for preferring an SQL sdolution
over the<br>
> file based one...?<br>
><br>
><br>
> <br>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
mapserver-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapserver-users">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a>
</pre>
</blockquote>
</body>
</html>