Great. Thanks for the info! I'll write up this issue with
preparedStatements not getting simplified. I did not realize that about
performance with prepared statements on postgres.




Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
ja...@newmoyergeospatial.com



On Thu, Sep 7, 2017 at 3:51 AM, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:

> On Tue, Sep 5, 2017 at 10:05 PM, Jason Newmoyer <
> ja...@newmoyergeospatial.com> wrote:
>
>> Okay, I changed PreparedStatements to false and now it is using
>> ST_Simplify!
>>
>> I think that should be considered a bug and I'll be happy to write it up.
>>
>
> Yep. Though, if you care about performance you should not be using
> prepared statements against postgresql
> (yes, I know, Oracle brainwashed us with prepared statements always on,
> but for GIS PostgreSQL makes
> smarter choices when they are off, although the most recent version of
> postgresql became smarter and
> learned to re-plan a prepared statement based on the current bound values
> so... not sure how well that
> works, it may be that with the latest version of postgresql the setting
> became irrelevant performance wise).
>
>
>>
>> I'm still interested in the question of using simplify for geometry
>> transformations is SLD. It seems like all the pieces are there to make it
>> happen. Would give map authors ultimate flexibility for cases like this.
>>
>
> In SLD it's likely useless or detrimental, GeoServer already does geometry
> decimation before rendering (unless the
> store does it on its behalf, that is).
>
>
>>
>> The on the fly simp is great. How is the scale factor determined? Would
>> it make sense to have that be configurable?
>>
>
> It's computed to be 0.8 on screen pixels (transformed back to real
> coordinates of course). If a database
> It is not configurable, if you want to play with it try changing
> RenderedImageMapOutputFormat in GeoServer
> and call setGeneralizationDistance on the StreamingRenderer instance.
>
> Cheers
> Andrea
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> 55054  Massarosa
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to