[OSGeo-Discuss] Common map printing specifications project [Fwd: Students: Get Paid to work on this project]
Landon Blake
lblake at ksninc.com
Tue Apr 6 10:01:05 PDT 2010
Tyler,
Thanks for taking the initiative on this problem domain. I am certainly
interested and will subscribe to the carto mailing list.
Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
-----Original Message-----
From: discuss-bounces at lists.osgeo.org
[mailto:discuss-bounces at lists.osgeo.org] On Behalf Of Tyler Mitchell
(OSGeo)
Sent: Tuesday, April 06, 2010 9:53 AM
To: OSGeo Discussions
Subject: [OSGeo-Discuss] Common map printing specifications project
[Fwd: Students: Get Paid to work on this project]
Hi all, just forwarding this note to this more general OSGeo channel,
since it applies to several projects and communities.
Year after year, one of the largest complaints about open source mapping
applications is the ability to output large, high quality, printable
maps. It's often "the issue" that some proprietary users say prevents
them from moving to an open source platform. Recognising that we can
always do better, the "Carto" project is an effort to address this in a
standard way, so that all open source applications may output
configuration files according to a specification and have a common
'engine' application produce an output file. By using a standards-based
approach, developers can work together on improving printing output
overall instead of doing it in dozens of different ways.
That said, attached is my attempt to try to find some students to work
on the project through Google's Summer of Code :) I'm also forwarding
it here for those others who are interested in trying to help move this
initiative along. Either way, join our list and say hi.[1] Except for
some interesting work with Mapnik and QGIS together (Dane Springmeyer's
Quantumnik!) this is pretty much still theoretical.
Tyler
[1] http://lists.osgeo.org/mailman/listinfo/carto
Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.
More information about the Discuss
mailing list