[Carto] Students: Get Paid to work on this project (isthis still the thread about high resolution printing??)

Landon Blake lblake at ksninc.com
Tue Apr 6 14:27:11 EDT 2010


I shared my ideas Bob. Let's hear about your approach.

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 
________________________________________
From: carto-bounces at lists.osgeo.org [mailto:carto-bounces at lists.osgeo.org] On Behalf Of Bob Basques
Sent: Tuesday, April 06, 2010 11:24 AM
To: Dane Springmeyer; Tyler Mitchell (OSGeo)
Cc: carto at lists.osgeo.org
Subject: Re: [Carto] Students: Get Paid to work on this project (isthis still the thread about high resolution printing??)

All, 

Is this still the thread about high resolution printing? 

If so, I have a different approach that might be worth offering. . . . 

bobb 



>>> "Tyler Mitchell (OSGeo)" <tmitchell at osgeo.org> wrote:
Dane Springmeyer wrote:
> Because there is not a third student focusing on the OSGEO side I think
> was is not being addressed is the interoperability/standards
> specification piece. Big picture this is likely better addressed outside
> of a code-based GSOC project and rather by the wider community.

I think you're hitting the nail on the head here.  With my "user of
several apps" hat on, I mainly care about the specifications side of
things.  Knowing that any "engine" app is already going to be focused on
improving quality, features, etc. the question from a larger, OSGeo
ecosystem perspective does really fall into the standards doesn't it?

What I would like to avoid is inventing a new spec, only to find that
another app already has a well thought out model in place.  I'd much
rather clone an existing model, API, whatever and then see what is
missing from our overall needs.  I'm most familiar with MapServer's
model, but was able to get a good glimpse into Mapnik when playing with
Quantumnik.  That kind of interoperability in a client app is quite
encouraging to see.

In the end, I'd like to take Application X and transform its config
files into the engine's model.  Thereby making this project also a bit
of a universal translator.. but I think I'm getting ahead of myself. :)

So, how do we get a good handle on potential specs to work from?  I
broke it down into three components:
* rendering stuff
* map layout details
* output formats/resolution etc.


Tyler
_______________________________________________
Carto mailing list
Carto at lists.osgeo.org
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 Carto mailing list