[geos-devel] Exposing Precision model through C-API

Varun Saraf varunsaraf14 at gmail.com
Fri Feb 28 06:01:09 PST 2014


Hi,

I will publish the proposal soon. The deadline for presenting the proposal
is 21st March.

Regards,
Varun Saraf


On Wed, Feb 26, 2014 at 11:08 PM, Sandro Santilli <strk at keybit.net> wrote:

> On Thu, Feb 20, 2014 at 08:57:32PM +0530, Varun Saraf wrote:
> > Hi,
> >
> > I have updated the GSoC ideas wiki page:
> > http://trac.osgeo.org/geos/wiki/GSoC
> >
> > In order to draft the API, how do I go about collecting suggestions from
> > the library users?
>
> By writing a proposal, publishing somewhere (the wiki?)
> then request comments on this list and iterate.
>
> Sean already started, but I think he's waiting for a real
> page, not just a section in another page.
>
> What's the deadline for presenting the proposal, btw ?
>
> --strk;
>
> > On Thu, Feb 20, 2014 at 12:00 PM, Sandro Santilli <strk at keybit.net>
> wrote:
> >
> > > Hi Sean,
> > >
> > > On Wed, Feb 19, 2014 at 11:15:18AM -0700, Sean Gillies wrote:
> > >
> > > > My Shapely project would benefit from this feature and I've written
> up
> > > its
> > > > requirements here: https://github.com/Toblerity/Shapely/issues/110.
> > > > Briefly, I'd like to be able to pass a precision model reference into
> > > > initGEOS and create an appropriate geometry factory in the GEOS
> context.
> > > > And I'd like to be able to switch between precision models within a
> > > Python
> > > > program, so not adding any new state outside of the context struct
> would
> > > be
> > > > my preference.
> > >
> > > I agree about making the precision model part of the context.
> > > But we can't change the initGEOS signature, so we'll need
> > > some GEOSContext_setPrecisionModel kind of method.
> > > At that point, we have to decide what happens with a previously
> > > set PrecisionModel, if it has to be allowed at all.
> > >
> > > Deleting the PrecisionModel and the GeometryFactory on finishGEOS
> > > is fine, but note that this would make any created geometry also
> > > broken (they hold a reference to the GeometryFactory that created
> > > them). Not a big deal, as long as it's clearely documented. Dunno
> > > if it would make sense for the opaque GEOSGeometry type to also
> > > hold a pointer to the context, just in case...
> > >
> > > > Once a wiki page is created, I'll be happy to copy my requirements
> there.
> > >
> > > I hope Varun will take action about the wiki :)
> > >
> > > --strk;
> > >
> > >
>
> > _______________________________________________
> > geos-devel mailing list
> > geos-devel at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/geos-devel
>
>
> --
>
>  ()  ASCII ribbon campaign  --  Keep it simple !
>  /\  http://strk.keybit.net/rants/ascii_mails.txt
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20140228/d9a0a171/attachment.html>


More information about the geos-devel mailing list