I subscribed to the list.<br><br>I'm a bit short on time, but I can write some thoughts, at least. Where is the most appropriate place to send these ideas to?<br><br>George<br><br><div class="gmail_quote">On Tue, Apr 6, 2010 at 11:16 PM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">FYI. This seems like something that we might want to get more involved with or at least be tracking from a development perspective.<br>
<br>
-Steve W<div class="im"><br>
<br>
-------- Original Message --------<br>
Subject: [OSGeo-Discuss] Common map printing specifications project [Fwd: Students: Get Paid to work on this project]<br></div><div><div></div><div class="h5">
Date: Tue, 06 Apr 2010 09:52:56 -0700<br>
From: Tyler Mitchell (OSGeo) <<a href="mailto:tmitchell@osgeo.org" target="_blank">tmitchell@osgeo.org</a>><br>
Reply-To: OSGeo Discussions <<a href="mailto:discuss@lists.osgeo.org" target="_blank">discuss@lists.osgeo.org</a>><br>
To: OSGeo Discussions <<a href="mailto:discuss@lists.osgeo.org" target="_blank">discuss@lists.osgeo.org</a>><br>
<br>
Hi all, just forwarding this note to this more general OSGeo channel,<br>
since it applies to several projects and communities.<br>
<br>
Year after year, one of the largest complaints about open source mapping<br>
applications is the ability to output large, high quality, printable<br>
maps. It's often "the issue" that some proprietary users say prevents<br>
them from moving to an open source platform. Recognising that we can<br>
always do better, the "Carto" project is an effort to address this in a<br>
standard way, so that all open source applications may output<br>
configuration files according to a specification and have a common<br>
'engine' application produce an output file. By using a standards-based<br>
approach, developers can work together on improving printing output<br>
overall instead of doing it in dozens of different ways.<br>
<br>
That said, attached is my attempt to try to find some students to work<br>
on the project through Google's Summer of Code :) I'm also forwarding<br>
it here for those others who are interested in trying to help move this<br>
initiative along. Either way, join our list and say hi.[1] Except for<br>
some interesting work with Mapnik and QGIS together (Dane Springmeyer's<br>
Quantumnik!) this is pretty much still theoretical.<br>
<br>
Tyler<br>
<br>
[1] <a href="http://lists.osgeo.org/mailman/listinfo/carto" target="_blank">http://lists.osgeo.org/mailman/listinfo/carto</a><br>
<br>
</div></div><br>Greetings everyone!<br>
<br>
The OSGeo Carto mailing list [1] was created to discuss developing a<br>
common approach to printable (vector-based) map output from open source<br>
mapping applications. With Google's Summer of Code program, we have a<br>
great opportunity for students to be funded to work on this project!<br>
Please forward this on to any students that you think might benefit.<br>
<br>
<a href="http://wiki.osgeo.org/wiki/OSGeo_Cartographic_Engine" target="_blank">http://wiki.osgeo.org/wiki/OSGeo_Cartographic_Engine</a><br>
<br>
Note there is room for a range of programming abilities, here are just a<br>
few...<br>
<br>
* developing XML-based map definition and print standard specifications<br>
* writing a GUI-based app for doing map layout<br>
* converting project configuration files into a common format<br>
* enhancing Mapnik to handle layout and file output definitions<br>
* What else? You tell us! Students are welcome to propose new ideas!<br>
<br>
This year, we've tied this project directly to Mapnik (and indirectly to<br>
QGIS or GRASS) just so it is clearly not a new project, but an<br>
enhancement of an existing one.<br>
<br>
Since it is really focused on developing and implementing standards, I'm<br>
not opposed to using other projects in there for either the 'client' or<br>
the engine - so if you're a student interested in MapServer or gvSIG,<br>
for example, and would rather work on implementing it that way, then<br>
please just propose it. I only had to narrow our focus to keep it clear.<br>
<br>
Time is running out for student applications, so let's get the word out!<br>
Even if you're not a student but are interested in helping in some way,<br>
join the list and say hi.<br>
<br>
[1] <a href="http://lists.osgeo.org/mailman/listinfo/carto" target="_blank">http://lists.osgeo.org/mailman/listinfo/carto</a><br>
<br>
<br>
<br>
<br>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
<br>
<br>_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>George R. C. Silva<br><br>Desenvolvimento em GIS<br><a href="http://blog.geoprocessamento.net">http://blog.geoprocessamento.net</a><br>