On 22 February 2011 07:31, Sean Gillies <[email protected]> wrote: > Implementing this feature will be complicated, requiring changes to > Shapely and also to the GEOS codebase. Shapely uses GEOS via its C > API, which does not currently expose the C++ PrecisionModel class. The > C API would need enhancement, and a new GEOS release would need to be > wrangled. After that, we'd need to come up with a good precision model > API for Shapely. Would it be enough to expose the precision model as a > variable in shapely.geos? The experience would be much like the one of > modifying sys.path, the same pros and cons, and working best if you > set the precision model once a session.
>From a Python programming viewpoint, this all makes sense. While trying to do my own homework, I was checking out dir(shapely.geos) to see if there was any access to the precision model. > Unfortunately, I'm completely committed on other projects and do not > have the time to enhance the GEOS C API. I have no expectations, and this is only an enhancement request. I have a workaround by rounding digits on all input coordinates, which is a bit messy but will suffice for now. -Mike _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
