strk,
You think we can have a beta end this week or you still working on stuff. I
volunteer to do the release.
Was just waiting for you last time.
Thanks,
Regina
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/
#841: Regression in prepared polygons contains
---+---
Reporter: sgillies | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major | Milestone: 3.6.3
Component: Default
#841: Regression in prepared polygons contains
---+---
Reporter: sgillies | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major | Milestone: 3.6.3
Component: Default
Hi,
AFAICT, GeometryList class is not used anywhere.
Can we ditch the class completely?
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-dev
#841: Regression in prepared polygons contains
---+---
Reporter: sgillies | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.6.3
Component: Default
#841: Regression in prepared polygons contains
---+---
Reporter: sgillies | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.6.3
Component: Default
On 6 September 2017 at 18:12, Martin Davis wrote:
> That is correct - the precision model is not used in relate and spatial
> predicate evaluation.
Directly, not.
Indirectly, it might be, depending on how input geometries are created
(eg. via WKB I/O).
In such case, one may consider precision mod
#841: Regression in prepared polygons contains
+---
Reporter: sgillies| Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.6.3
Component: Default |Version: 3.6.2
Severity:
That is correct - the precision model is not used in relate and spatial
predicate evaluation. (It's used in a few more places than the overlay
functions, but that is its primary usage)
It is feasible to introduce a precision model into the spatial predicate
computation, but not easily in the curr
On 6 September 2017 at 17:17, Sandro Santilli wrote:
> On Wed, Sep 06, 2017 at 04:24:45PM +0200, Mateusz Loskot wrote:
>
>> In the code, there are uses of std::auto_ptr that are hard to reason about
>> what makes me suspicious:
>>
>> class T
>> {
>> auto_ptr items;
>> public
>> auto_ptr getI
On Wed, Sep 06, 2017 at 04:24:45PM +0200, Mateusz Loskot wrote:
> In the code, there are uses of std::auto_ptr that are hard to reason about
> what makes me suspicious:
>
> class T
> {
> auto_ptr items;
> public
> auto_ptr getItems()
> {
> return items;
> }
> };
>
> Is the
Hi,
In C++, well-established patterns when/how to use std::auto_ptr are:
void sink(std::auto_ptr p);
std::auto_ptr source();
TL;TR: Is it safe to assume GEOS follows the patterns?
In the code, there are uses of std::auto_ptr that are hard to reason about
what makes me suspicious:
class T
{
My understanding is that precision models are considered only in the
overlay options (and not in the geometry predicates).
Dan
On Mon, Sep 4, 2017 at 5:13 AM, Nyall Dawson wrote:
> On 4 September 2017 at 17:29, Sandro Santilli wrote:
> > On Mon, Sep 04, 2017 at 04:28:32PM +1000, Nyall Dawson w
13 matches
Mail list logo
