Ugh. Requiring complicated combinations of bit fields strikes me as
being pretty error prone.
What about providing a string parameter which can supply the various
options in a human-readable format?
E.g. "extrude=1 tesselate=0 altitudeMode=clampToGround"
Easy to read, easy to parse, easy to extend...
Paul Ramsey wrote:
I hope others are testing this out...
I have some aesthetic concerns with how you are passing arguments, I
wonder if there is a more elegant way do to it. I feel like requiring
a precision argument in order to do the other options would be
preferable to the "size of precision" hack to distinguish between
options and precision. Others may disagree.
P.
On 14-Feb-08, at 11:01 AM, Eduin Carrillo wrote:
Add the possibility to customize KML code produced by PostGIS with
altitude mode (altitudeMode), allow lines and paths to follow the
terrain (tessellate), and how to connect primitive to the ground
(extrude).
http://code.google.com/p/postexperiments/wiki/Extrude_Tesselate_and_Altitudemode_Support
http://code.google.com/p/postexperiments/issues/detail?id=1
=
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
