> All the performance talk is mostly because JTS still runs a lot faster than GEOS > for some bulk processing. My current test is a big union of watershed > boundaries, about 6MB of data, which takes about 20s under GEOS and > about 25% of that under JTS. It's a big gap, and in theory the two code bases > are pretty aligned right now. Same overlayNG engine, etc. So I figure there > has to be a big implementation ball of performance hiding under the covers > somewhere. No luck thus far. > > I think we're close, looking forward to release :) > > P > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel
You have your sample watershed data set. Would like to test it out myself. Thanks, Regina _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
