<html>
<head>
<style type="text/css">
<!--
body { margin-right: 4px; margin-bottom: 1px; margin-left: 4px; line-height: normal; margin-top: 4px; font-variant: normal }
p { margin-bottom: 0; margin-top: 0 }
-->
</style>
</head>
<body style="margin-right: 4px; margin-bottom: 1px; margin-left: 4px; margin-top: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">Is this still the thread about high resolution printing?</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">If so, I have a different approach that might be worth offering. . . .</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br> <br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "Tyler Mitchell (OSGeo)" <tmitchell@osgeo.org> wrote:<br> </p>
<div style="margin-right: 0; background-color: #f3f3f3; margin-bottom: 0; margin-left: 15px; border-left: solid 1px #050505; margin-top: 0; padding-left: 7px">
<p style="margin-bottom: 0; margin-top: 0">
Dane Springmeyer wrote:<br>> Because there is not a third student focusing on the OSGEO side I think<br>> was is not being addressed is the interoperability/standards<br>> specification piece. Big picture this is likely better addressed outside<br>> of a code-based GSOC project and rather by the wider community.<br><br>I think you're hitting the nail on the head here.  With my "user of<br>several apps" hat on, I mainly care about the specifications side of<br>things.  Knowing that any "engine" app is already going to be focused on<br>improving quality, features, etc. the question from a larger, OSGeo<br>ecosystem perspective does really fall into the standards doesn't it?<br><br>What I would like to avoid is inventing a new spec, only to find that<br>another app already has a well thought out model in place.  I'd much<br>rather clone an existing model, API, whatever and then see what is<br>missing from our overall needs.  I'm most familiar with MapServer's<br>model, but was able to get a good glimpse into Mapnik when playing with<br>Quantumnik.  That kind of interoperability in a client app is quite<br>encouraging to see.<br><br>In the end, I'd like to take Application X and transform its config<br>files into the engine's model.  Thereby making this project also a bit<br>of a universal translator.. but I think I'm getting ahead of myself. :)<br><br>So, how do we get a good handle on potential specs to work from?  I<br>broke it down into three components:<br>* rendering stuff<br>* map layout details<br>* output formats/resolution etc.<br><br><br>Tyler<br>_______________________________________________<br>Carto mailing list<br>Carto@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/carto">http://lists.osgeo.org/mailman/listinfo/carto</a><br>
</p>
</div>
</body>
</html>