id summary reporter owner description type status priority milestone component version severity resolution keywords cc 2221 Bad 'angle follow' case -- possibly a use for splining crschmidt sdlime "http://boston.freemap.in/bugs/2221/poor_follow.png Uses: http://boston.freemap.in/bugs/2221/poor-follow.map All data in: http://boston.freemap.in/bugs/2221/ Command used: shp2img -m poor-follow.map -o poor_follow.png -e 232376.94043 900487.441406 232524.42627 900634.927246 -l roads_3_1 Discussion on IRC: {{{ 20:24:28 < hobu> Someone needs to do some splining 20:24:29 < crschmidt> Should I bother to file it as a bug? 20:25:06 < hobu> You could file an enhancement for 5.2 that says, 'we should improve ANGLE FOLLOW to support simple interpolation methods like splining for degenerative cases"" 20:25:24 < hobu> It's way too big to be dealt with in the throws of our 5.0 release right now though 20:25:40 < crschmidt> understood 20:25:46 < crschmidt> Just wasn't sure if it was worth filing at all 20:26:19 < hobu> Another thing about the splining is we could maybe take advantage of it for feature rendering as well 20:26:38 < hobu> something those paleogeographers do from time to time ;) what is that? straightening out of too-curvy borders? smoothen disjointed ones. They add map noise for very little information * crschmidt nods something like what a simplification algorithm would do only automatic/built into the rendering? right, except not one that has to preserve topological relationships http://en.wikipedia.org/wiki/B-spline Would be a simple approach Maybe you'd tell the mapserver renderer, 'hey, use 6-8 consequtive vertices to calculate your splines, if the incident angle is less than x degrees"" or something like that ;) It'd be spendy, for sure and not very useful for Manhattan grid systems :) }}} " defect closed high 6.0 release MapServer C Library svn-trunk (development) normal fixed aboudreault dmorissette tbonfort woodbri jmckenna