I think it would benefit the most from some kind of CAD package that can clip polygons for me, so I don't have to do all the math manually. I was rendering semi-transparent, so I needed to prevent polygon overlap. (or use a different technique like rendering to a texture then rendering the texture semi-transparent, but that gets into zooming artifacts and awkwardness) There was also the problem where roads can turn at sharp bends and the default polygons for that look horrible without some sort of smoothing around the corner. And UGH, intersections...
Geo::SpatialDB itself is just a database of things described in lat/lon, designed to be loaded tile-by-tile at varying levels of detail for the zoom level. I don't think that's really a PDL problem. The polygons it exports could be, if that's what a rendering pipeline wants to consume. But, PDL would need the polygon objects to be available without GLUT installed, because one of the use cases is server-side rendering.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.