Hi all,
I'm going to show some images for comparing the old wmsTileFuser class and
its modified version, both in *fullWMS* mode enabled.
I made the *fullWMS* parameter configurable from the geowebcache.xml file
by adding the <fullWMS>TRUE(or FALSE)</fullWMS> field.
I added the possibility for the user to change the image quality by setting
an additional WMS parameter called *hints*. The user can choose one of the
3 following values: *speed*, *default*, *quality*.
The first image represents the result of a WMS request on a vectorial
layer, in image/png format. The other 3 images represent the same WMS
request with the new WMS parameter.
The second image value represents the result with the *speed* value which
takes minor time without any care about the quality.
The third image (*default* value selected) provides a better image quality
but requires more time than the *speed* configuration.
The last image with the *quality* value takes more time than the others but
the final image has the best quality between the 4 images.
>From the results, in fact, it is easy to note that the image created with
the *quality* hints has a better quality than that returned by the old
WMSTileFuser class.
I hope this could help to review the pull requests.
P.S. The images are too big to be sent by mail, I add the following links
for download:
old wms request:
https://drive.google.com/file/d/0B_H-B1p4qGi6VVgyVGJPYVV1c1hBMDMzakhPRTZlQTdzRFl3/edit?usp=sharing
new wms request with speed hints:
https://drive.google.com/file/d/0B_H-B1p4qGi6MEhJR1NxTkV2Tnh0Y3Zza2JJdHNtY0RhZVN3/edit?usp=sharing
new wms request with default hints:
https://drive.google.com/file/d/0B_H-B1p4qGi6bk5adnNYN2NjRUk/edit?usp=sharing
new wms request with quality hints:
https://drive.google.com/file/d/0B_H-B1p4qGi6b1RTYktBSjBtYlpOdGdFS3NVWkVIb1Rzd3g4/edit?usp=sharing
Cheers,
Nicola.
2014-03-07 10:15 GMT+01:00 Nicola Lagomarsini <
nicola.lagomars...@geo-solutions.it>:
> Hi all,
>
> I'm going to show some images for comparing the old wmsTileFuser class and
> its modified version, both in *fullWMS* mode enabled.
>
> I made the *fullWMS* parameter configurable from the geowebcache.xml file
> by adding the <fullWMS>TRUE(or FALSE)</fullWMS> field.
>
> I added the possibility for the user to change the image quality by
> setting an additional WMS parameter called *hints*. The user can choose
> one of the 3 following values: *speed*, *default*, *quality*.
>
> The first image represents the result of a WMS request on a vectorial
> layer, in image/png format. The other 3 images represent the same WMS
> request with the new WMS parameter.
>
> The second image value represents the result with the *speed* value which
> takes minor time without any care about the quality.
> The third image (*default* value selected) provides a better image
> quality but requires more time than the *speed* configuration.
> The last image with the *quality* value takes more time than the others
> but the final image has the best quality between the 4 images.
>
> From the results, in fact, it is easy to note that the image created with
> the *quality* hints has a better quality than that returned by the old
> WMSTileFuser class.
>
> I hope this could help to review the pull requests.
>
> Cheers,
> Nicola.
>
>
>
>
> 2014-03-05 16:47 GMT+01:00 Andrea Aime <andrea.a...@geo-solutions.it>:
>
> On Wed, Mar 5, 2014 at 4:41 PM, Simone Giannecchini <
>> simone.giannecch...@geo-solutions.it> wrote:
>>
>>> Ciao Nicola,
>>> I would leave this parameter as it was originally, which is False.
>>>
>>> This behaviour should be, IMHO, enabled explicitly if needed.
>>>
>>
>> The annoying bit is that now it's enabled in Spring app context files (
>> http://geowebcache.org/docs/1.5.1/services/wms.html#support-for-regular-wms-clients
>> ),
>> it's not easily configured, if we want it configurable we should move it
>> to geowebcache.xml instead, so that we don't have to modify
>> jars (at least in GeoServer integration) to enable it.
>>
>> Cheers
>> Andrea
>>
>> --
>> == Our support, Your Success! Visit http://opensdi.geo-solutions.it for
>> more information ==
>>
>> 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
>>
>> -------------------------------------------------------
>>
>
>
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> information.
> ==
>
> Ing. Nicola Lagormarsini
> Junior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Nicola Lagormarsini
Junior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
