On Tue, Dec 31, 2013 at 3:13 PM, Andrea Aime
<[email protected]>wrote:
> On Tue, Dec 31, 2013 at 3:07 PM, Juan Marín Otero <
> [email protected]> wrote:
>
>> Andrea & Jonathan,
>>
>> Thanks for this thorough benchmark, I think it's very useful. My 2c would
>> be to introduce these options, but I'd be against simplifying geometries by
>> default, as I know of a few use cases that require their geometries to be
>> "exact" (or at least, exact in the sense of representing whatever they have
>> captured as raw data). A rendering hint sounds great to me though, and I
>> see most use cases benefiting from this.
>>
>
> Ah sorry, when I said "by default" I meant any time the already existing
> Hints.GEOMETRY_SIMPLIFICATION Query hint
> is passed down, which happens only when rendering.
>
And oh, we should not pass down that hint when a rendering transformation
is used, because it may need valid geometries to w
work with.
Do you know of other cases?
Cheers
Andrea
--
*== GeoSolutions will be closed for seasonal holidays from 23/12/2013 to
06/01/2014 ==*
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
