Re: [Geoserver-users] Larger PNG tiles after geoserver update
On Thu, Oct 9, 2014 at 12:29 AM, Tom S tom-sourcefo...@fatsheepfarm.com wrote: I am using Windows, and it is the returned tile file size that was radically different. Based on your comments, I checked the configuration (Settings/JAI) and revised this. I do not have the Java ImageIO library installed, so it looks like the system defaults to using the PNGJ library on the newer releases. When I switched to using 'Java own encoder', the sizes shrank to be the same between the old and new instance. In my case the extra file size was enough to have a major impact on slow (Mobile) connections. I'll test version 2.6, and perhaps ImageIO later to see how it behaves. In any case, even with the compression set to 90, PNGJ is still a bit larger than the original library result. It will take a bit longer to see if the system CPU impact is less using this encoder with the equivalent compression ratio. The 90% case of using PNGs is encoding rasterized vector data, so the PNGJ work (which was done exclusively in my spare time) concentrated on having much faster PNG encoding for vector data because the existing encoders were almost 80% the reason we lost the last WMS benchmarking competition (which is normally based on WMS serving speed over a local network): http://www.geo-solutions.it/blog/developers-corner-fast-pure-java-open-source-png-encoder-for-geoserver/ The raster case was not investigated in deep, and I guess we could do some more work to improve on that end, but right now my spare time is fully busy doing a rewrite of the CSS subsystem so... I cannot offer help there (well, not personally at least). Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *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. --- -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] 2.6 pink tiles
Hi, From which version did you update? Tell also a bit more about the environment: Linux/Windows, 32 or 64 bit, java version, with or without native JAI and which file format in tiles? Pink tiles mean no tile at all in that place and the reason may be timeout in seeding process or some other failure. If you create png tiles on Windows it can be for example related to http://thread.gmane.org/gmane.comp.gis.geoserver.user/43732 About seeding/reseeding having no effect, how did you test that? The OpenLayers map that opens from the layer preview does not read tiles from the cache even if the cache is seeded because the WMS GetMaps which this app is sending do not match with extents of tiles in the cache. Therefore seeding does not remove pink tiles from layer preview. The other viewer that opens through http://localhost:8080/geoserver/gwc/demo/ does hit the cache and after successful seeding it should not show pink tiles. At least this is how I understand the situation. -Jukka Rahkonen- Ismail, Mark wrote: Hi I upgraded to 2.6 today and am having some problems with my base maps They are loading much slower and I am getting quite a few pink tiles Assuming it was something to do with the geowebcache I have wiped it and am trying to regenerate the tiles The tasks are starting then when you click refresh they disappear and a few files are appearing in the cache but it is not completing I have tried seed and reseed with no luck Any tips / tricks to get it working in 2.6 ? Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council * Westmorland Road * Huyton * L36 9GL Save time - use the IT Service Desk Self Servehttp://kmbcselfservice/ Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Error Using the Pregeneralized Features module on Geoserver
Hi Joel No, this is not an error in your configuration. The renderer component does not pass a proper hint to the Data Source, the result is the log message No hint for geometry distance in query, fallback to base feature and the original geometry is used. @Andrea I think this a regression. The problem is here org.geotools.data.gen.PreGeneralizedFeatureSource.getRequestedDistance(Query) Should Joel Open a JIRA issue. Cheers Christian On Wed, Oct 8, 2014 at 6:00 PM, joel.schmitt joel.schm...@drillinginfo.com wrote: Hello, I am trying to use the pregeneralized features extension for limiting the number of vertices drawn for a large dataset that resides in PostGIS (geometry type 'MultiLineString'). I've been through the tutorials and the help forums and adjusted my .xml config file in many different ways according to all the info I've found. I have also set up my Generalizing Data Store on geoserver in the exact manner that was specified in this tutorial: http://osgeo-org.1560.x6.nabble.com/attachment/3819796/0/pregen_tutorial.html http://osgeo-org.1560.x6.nabble.com/attachment/3819796/0/pregen_tutorial.html After zooming and panning around in OpenLayers, I am still receiving the following message in the geoserver logs: 2014-10-08 10:00:10,973 WARN [org.geotools.data.gen] - No hint for geometry distance in query, fallback to base feature From my understanding, this means that something in the config file is not right and geoserver is defaulting to the base the_geom column for rendering the pipelines. Here is my .xml file: ?xml version=1.0 encoding=UTF-8? GeneralizationInfos version=1.0 GeneralizationInfo dataSourceNameSpace=pipelines_pregen dataSourceName=pipelines featureName=pipelines_general_tx_1 baseFeatureName=domestic_pipelines_tx_1 geomPropertyName=the_geom Generalization distance=5000 featureName=domestic_pipelines_tx_1 geomPropertyName=the_geom5000/ /GeneralizationInfo /GeneralizationInfos I've checked and all the parameters are populated correctly in the xml file according to the guidelines laid out in this thread: http://osgeo-org.1560.x6.nabble.com/New-postgis-feature-pregeneralized-tutorial-question-tp3797025p3797026.html http://osgeo-org.1560.x6.nabble.com/New-postgis-feature-pregeneralized-tutorial-question-tp3797025p3797026.html Does anybody know of any reasons why this would be failing to generalize my features? Any help would be greatly appreciated! Thanks! -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Error-Using-the-Pregeneralized-Features-module-on-Geoserver-tp5166527.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- DI Christian Mueller MSc (GIS), MSc (IT-Security) OSS Open Source Solutions GmbH -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] 2.6 pink tiles
Hi I updated from version 2.5.2 on windows server 2008 64bit which was using apache tomcat 8.09 and jre-8u11-windows-i586 I upgraded apache to 8.14 and the jre to jre-8u20-windows-i586 to fix a security vulnerability I am using native jai and the tiles are in png8 While I had to rebuild apache I decided to upgrade geoserver at the same time I have my data folder on the local c drive - the server is a Vmware server. The data folder included a 21gb cache of my 5 ordnance survey base maps as layer groups I decided that reseed wasn't working by emptying one the of layers using tile caching / tile layers empty option and then reseeding. I opened the cache folder where there were no tiles and hit reseed The reseed form opened with 300k ish tiles to do and said it had done a few hundred - by checking the folder I could see the files there When you hit refresh on the seed form to update progress the job disappears, the cache folder still only has a few files in it I tried this on a few layers with exactly the same result. I spent some time this morning monitoring the network traffic and managed to find an error :- ?xml version=1.0 encoding=UTF-8 standalone=no?!DOCTYPE ServiceExceptionReport SYSTEM http://geolive.knowsley.gov.uk:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd; ServiceExceptionReport version=1.1.1ServiceException Internal error Error occurred getting table name list. ORA-01000: maximum open cursors exceeded /ServiceException/ServiceExceptionReport All my data is stored in oracle - I am using the new 2.6 oracle jar file I right clicked and did show picture a few times on the missing pink tile that generated the above error and it appeared http://geolive.knowsley.gov.uk:8080/geoserver/Geostore/wms?LAYERS=OS%20MasterFORMAT=image%2Fpng8SERVICE=WMSVERSION=1.1.1REQUEST=GetMapSTYLES=SRS=EPSG%3A27700BBOX=346585.83789474,391167.5004644,347294.07541796,391875.73798762WIDTH=256HEIGHT=256 it would seem to be an issue with the oracle connection to my data Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council * Westmorland Road * Huyton * L36 9GL Save time - use the IT Service Desk Self Servehttp://kmbcselfservice/ Application From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi] Sent: 09 October 2014 08:10 To: Ismail, Mark; geoserver mailing list (geoserver-users@lists.sourceforge.net) Subject: Re: 2.6 pink tiles Hi, From which version did you update? Tell also a bit more about the environment: Linux/Windows, 32 or 64 bit, java version, with or without native JAI and which file format in tiles? Pink tiles mean no tile at all in that place and the reason may be timeout in seeding process or some other failure. If you create png tiles on Windows it can be for example related to http://thread.gmane.org/gmane.comp.gis.geoserver.user/43732 About seeding/reseeding having no effect, how did you test that? The OpenLayers map that opens from the layer preview does not read tiles from the cache even if the cache is seeded because the WMS GetMaps which this app is sending do not match with extents of tiles in the cache. Therefore seeding does not remove pink tiles from layer preview. The other viewer that opens through http://localhost:8080/geoserver/gwc/demo/ does hit the cache and after successful seeding it should not show pink tiles. At least this is how I understand the situation. -Jukka Rahkonen- Ismail, Mark wrote: Hi I upgraded to 2.6 today and am having some problems with my base maps They are loading much slower and I am getting quite a few pink tiles Assuming it was something to do with the geowebcache I have wiped it and am trying to regenerate the tiles The tasks are starting then when you click refresh they disappear and a few files are appearing in the cache but it is not completing I have tried seed and reseed with no luck Any tips / tricks to get it working in 2.6 ? Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council * Westmorland Road * Huyton * L36 9GL Save time - use the IT Service Desk Self Servehttp://kmbcselfservice/ Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this
Re: [Geoserver-users] 2.6 pink tiles
On Thu, Oct 9, 2014 at 10:42 AM, Ismail, Mark mark.ism...@knowsley.gov.uk wrote: Hi I updated from version 2.5.2 on windows server 2008 64bit which was using apache tomcat 8.09 and jre-8u11-windows-i586 I upgraded apache to 8.14 and the jre to jre-8u20-windows-i586 to fix a security vulnerability I am using native jai and the tiles are in png8 Hmm... Java 8 is not tested with GeoServer. While I had to rebuild apache I decided to upgrade geoserver at the same time I have my data folder on the local c drive – the server is a Vmware server. The data folder included a 21gb cache of my 5 ordnance survey base maps as layer groups I decided that reseed wasn’t working by emptying one the of layers using tile caching / tile layers empty option and then reseeding. I opened the cache folder where there were no tiles and hit reseed The reseed form opened with 300k ish tiles to do and said it had done a few hundred – by checking the folder I could see the files there When you hit refresh on the seed form to update progress the job disappears, the cache folder still only has a few files in it I tried this on a few layers with exactly the same result. I spent some time this morning monitoring the network traffic and managed to find an error :- ?xml version=1.0 encoding=UTF-8 standalone=no?!DOCTYPE ServiceExceptionReport SYSTEM http://geolive.knowsley.gov.uk:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd; ServiceExceptionReport version=1.1.1ServiceException Internal error Error occurred getting table name list. ORA-01000: maximum open cursors exceeded /ServiceException/ServiceExceptionReport Ah, this is a well known problem with Oracle, not much we can do on our side, Oracle prepared statements keep cursors open, prepared statements are associated to connections, we keep connections open in the pool because opening a new one with Oracle is _very_ expensive (there is a long thread on this topic, maybe one or two year ago, in this mailing list). What you can do to limit the issue is to either tune your Oracle installation to allow more cursors to be opened, or go in the GeoServer store configuration and reduce the number of prepared statements kept open per connection (the default if 50), eventually also reduce the number of connections in the pool Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *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. --- -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing
[Geoserver-users] Preventing WMS/WFS layers being requested in isolation
Is it possible to allow certain layers to be requested only when other layers are requested with it? Thanks Tom -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Preventing-WMS-WFS-layers-being-requested-in-isolation-tp5166627.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Preventing WMS/WFS layers being requested in isolation
On Thu, Oct 9, 2014 at 11:02 AM, Tom Chadwin tom.chad...@nnpa.org.uk wrote: Is it possible to allow certain layers to be requested only when other layers are requested with it? In general terms, that would break the WMS contract, which allows any combination of the exposed layers. Well, of course unless you do not expose the layer in question (make it non advertised), and eventually lump it into opaque layer groups... at this point the clients will not see it, but it will still be available as part of the layer groups If you don't mind me asking, why do you need the layer to only show up along with other layers? Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *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. --- -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] 2.6 pink tiles
I have fixed the pink tile issue by replacing ojdbc7.jar with ojdbc6.jar and changing to jre7 Which is the one I was using with 2.5.2 The issue now is the seeding / wms loading is very slow (approx 30% of normal loading speed) I uninstalled 2.6.0 and went back to 2.5.2 and speeds are back to normal Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council • Westmorland Road • Huyton • L36 9GL Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/ Application From: andrea.a...@gmail.commailto:andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] On Behalf Of Andrea Aime Sent: 09 October 2014 10:00 To: Ismail, Mark Cc: Rahkonen Jukka (Tike); geoserver mailing, list (geoserver-users@lists.sourceforge.netmailto:geoserver-users@lists.sourceforge.net) Subject: Re: [Geoserver-users] 2.6 pink tiles On Thu, Oct 9, 2014 at 10:42 AM, Ismail, Mark mark.ism...@knowsley.gov.ukmailto:mark.ism...@knowsley.gov.uk wrote: Hi I updated from version 2.5.2 on windows server 2008 64bit which was using apache tomcat 8.09 and jre-8u11-windows-i586 I upgraded apache to 8.14 and the jre to jre-8u20-windows-i586 to fix a security vulnerability I am using native jai and the tiles are in png8 Hmm... Java 8 is not tested with GeoServer. While I had to rebuild apache I decided to upgrade geoserver at the same time I have my data folder on the local c drive – the server is a Vmware server. The data folder included a 21gb cache of my 5 ordnance survey base maps as layer groups I decided that reseed wasn’t working by emptying one the of layers using tile caching / tile layers empty option and then reseeding. I opened the cache folder where there were no tiles and hit reseed The reseed form opened with 300k ish tiles to do and said it had done a few hundred – by checking the folder I could see the files there When you hit refresh on the seed form to update progress the job disappears, the cache folder still only has a few files in it I tried this on a few layers with exactly the same result. I spent some time this morning monitoring the network traffic and managed to find an error :- ?xml version=1.0 encoding=UTF-8 standalone=no?!DOCTYPE ServiceExceptionReport SYSTEM http://geolive.knowsley.gov.uk:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd; ServiceExceptionReport version=1.1.1ServiceException Internal error Error occurred getting table name list. ORA-01000: maximum open cursors exceeded /ServiceException/ServiceExceptionReport Ah, this is a well known problem with Oracle, not much we can do on our side, Oracle prepared statements keep cursors open, prepared statements are associated to connections, we keep connections open in the pool because opening a new one with Oracle is _very_ expensive (there is a long thread on this topic, maybe one or two year ago, in this mailing list). What you can do to limit the issue is to either tune your Oracle installation to allow more cursors to be opened, or go in the GeoServer store configuration and reduce the number of prepared statements kept open per connection (the default if 50), eventually also reduce the number of connections in the pool Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 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
[Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver It works fine but It is far to sensitive to where you click – if you don’t get right in the centre of a point or icon it finds nothing, it can take 2 or 3 attempts to get a response even if clicking carefully and zoomed in Is there any way to make that click “less sensitive” so it will pick up the closest point to the mouse click ? I know this isn’t strictly a geoserver issue but I’ve found nothing useful on the openlayers forums Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council • Westmorland Road • Huyton • L36 9GL Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/ Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
Hi, You can adjust the tolerance with vendor option ”buffer” http://docs.geoserver.org/latest/en/user/services/wms/vendor.html. However, the latest Geoserver versions should know the actual size and shape of icons. Which version you have? -Jukka Rahkonen- Ismail, Mark wrote: I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver It works fine but It is far to sensitive to where you click – if you don’t get right in the centre of a point or icon it finds nothing, it can take 2 or 3 attempts to get a response even if clicking carefully and zoomed in Is there any way to make that click “less sensitive” so it will pick up the closest point to the mouse click ? I know this isn’t strictly a geoserver issue but I’ve found nothing useful on the openlayers forums Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council • Westmorland Road • Huyton • L36 9GL Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/ Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
Mark, You might take a look at the clickTolerance setting as described at the link below: http://dev.openlayers.org/releases/OpenLayers-2.13.1/doc/apidocs/files/OpenLayers/Control/GetFeature-js.html#OpenLayers.Control.GetFeature.clickTolerance Hope this helps. Jerome Wendell From: Ismail, Mark [mailto:mark.ism...@knowsley.gov.uk] Sent: Thursday, October 09, 2014 9:06 AM To: geoserver mailing, list (geoserver-users@lists.sourceforge.net) Subject: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver It works fine but It is far to sensitive to where you click – if you don’t get right in the centre of a point or icon it finds nothing, it can take 2 or 3 attempts to get a response even if clicking carefully and zoomed in Is there any way to make that click “less sensitive” so it will pick up the closest point to the mouse click ? I know this isn’t strictly a geoserver issue but I’ve found nothing useful on the openlayers forums Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council ê Westmorland Road ê Huyton ê L36 9GL Save time – use the IT Service Desk http://kmbcselfservice/ Self Serve Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
There is a parameter on the call to set the number of pixels to search. Russ --- On 9 Oct 2014, at 14:06, Ismail, Mark mark.ism...@knowsley.gov.uk wrote: I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver It works fine but It is far to sensitive to where you click – if you don’t get right in the centre of a point or icon it finds nothing, it can take 2 or 3 attempts to get a response even if clicking carefully and zoomed in Is there any way to make that click “less sensitive” so it will pick up the closest point to the mouse click ? I know this isn’t strictly a geoserver issue but I’ve found nothing useful on the openlayers forums Mark Ismail Principal IT Officer Tel: 0151 443 3021 Knowsley Council ê Westmorland Road ê Huyton ê L36 9GL Save time – use the IT Service Desk Self Serve Application This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it. Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives. Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
Hi
Thanks for the replies
Ive tried
vendorParams: { buffer:100 },
tolerance: 100,
in the openlayers wmsgetfeatureinfo request but no change, the points are still
very difficult to click even with these extreme settings
From the open layers docs tolerance doesn’t seem to be a supported parameter
anymore though
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council • Westmorland Road • Huyton • L36 9GL
Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/
Application
From: Jerome A. Wendell [mailto:jawend...@suddenlink.net]
Sent: 09 October 2014 14:32
To: Ismail, Mark; 'geoserver mailing, list'
Subject: RE: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
Mark,
You might take a look at the clickTolerance setting as described at the link
below:
http://dev.openlayers.org/releases/OpenLayers-2.13.1/doc/apidocs/files/OpenLayers/Control/GetFeature-js.html#OpenLayers.Control.GetFeature.clickTolerance
Hope this helps.
Jerome Wendell
From: Ismail, Mark [mailto:mark.ism...@knowsley.gov.uk]
Sent: Thursday, October 09, 2014 9:06 AM
To: geoserver mailing, list
(geoserver-users@lists.sourceforge.netmailto:geoserver-users@lists.sourceforge.net)
Subject: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver
It works fine but It is far to sensitive to where you click – if you don’t get
right in the centre of a point or icon it finds nothing, it can take 2 or 3
attempts to get a response even if clicking carefully and zoomed in
Is there any way to make that click “less sensitive” so it will pick up the
closest point to the mouse click ?
I know this isn’t strictly a geoserver issue but I’ve found nothing useful on
the openlayers forums
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council • Westmorland Road • Huyton • L36 9GL
Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/
Application
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or retain
this email or any part of it and do not take any action based on it.
Unless expressly stated, opinions in this email are those of the individual
sender, and not of Knowsley MBC. Legally binding obligations can only be
created for, or be entered into on behalf of, Knowsley MBC by duly authorised
officers or representatives.
Knowsley MBC excludes any liability whatsoever for any offence caused, any
direct or consequential loss arising from the use, or reliance on, this e-mail
or its contents. We believe but do not warrant that this e-mail and any
attachments are virus free. You must therefore take full responsibility for
virus checking and no responsibility is accepted for loss or damage arising
from viruses or changes made to this message after it was sent. Knowsley MBC
reserves the right to monitor and/or record all e-mail communications through
its network in accordance with relevant legislation.
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or retain
this email or any part of it and do not take any action based on it.
Unless expressly stated, opinions in this email are those of the individual
sender, and not of Knowsley MBC. Legally binding obligations can only be
created for, or be entered into on behalf of, Knowsley MBC by duly authorised
officers or representatives.
Knowsley MBC excludes any liability whatsoever for any offence caused, any
direct or consequential loss arising from the use, or reliance on, this e-mail
or its contents. We believe but do not warrant that this e-mail and any
attachments are virus free. You must therefore take full responsibility for
virus checking and no responsibility is accepted for loss or damage arising
from viruses or changes made to this message after it was sent. Knowsley MBC
reserves the right to monitor and/or record all e-mail communications through
its network in accordance with relevant legislation.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
Geoserver-users mailing
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
This is my code;
control = new OpenLayers.Control.GetFeature({
protocol: OpenLayers.Protocol.WFS.fromWMSLayer(theLayer),
box: false,
hover: false,
maxFeatures: 20,
multipleKey: shiftKey,
toggleKey: ctrlKey,
clickTolerance:30
});
control.events.register(featureselected, this, function(e) {
selected.addFeatures([e.feature]); displayInfo(e); });
control.events.register(featureunselected, this, function(e) {
selected.removeFeatures([e.feature]);});
control.events.register(hoverfeature, this, function(e) {
hover.addFeatures([e.feature]); displayInfo(e); });
control.events.register(outfeature,this, function(e) {
hover.removeFeatures([e.feature]); });
map.addControl(control);
control.activate();
Note the clickTolerance line
Russ
On 9 Oct 2014, at 16:02, Ismail, Mark mark.ism...@knowsley.gov.uk wrote:
Hi
Thanks for the replies
Ive tried
vendorParams: { buffer:100 },
tolerance: 100,
in the openlayers wmsgetfeatureinfo request but no change, the points are
still very difficult to click even with these extreme settings
From the open layers docs tolerance doesn’t seem to be a supported parameter
anymore though
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council ê Westmorland Road ê Huyton ê L36 9GL
Save time – use the IT Service Desk Self Serve Application
From: Jerome A. Wendell [mailto:jawend...@suddenlink.net]
Sent: 09 October 2014 14:32
To: Ismail, Mark; 'geoserver mailing, list'
Subject: RE: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
Mark,
You might take a look at the clickTolerance setting as described at the link
below:
http://dev.openlayers.org/releases/OpenLayers-2.13.1/doc/apidocs/files/OpenLayers/Control/GetFeature-js.html#OpenLayers.Control.GetFeature.clickTolerance
Hope this helps.
Jerome Wendell
From: Ismail, Mark [mailto:mark.ism...@knowsley.gov.uk]
Sent: Thursday, October 09, 2014 9:06 AM
To: geoserver mailing, list (geoserver-users@lists.sourceforge.net)
Subject: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver
It works fine but It is far to sensitive to where you click – if you don’t
get right in the centre of a point or icon it finds nothing, it can take 2 or
3 attempts to get a response even if clicking carefully and zoomed in
Is there any way to make that click “less sensitive” so it will pick up the
closest point to the mouse click ?
I know this isn’t strictly a geoserver issue but I’ve found nothing useful on
the openlayers forums
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council ê Westmorland Road ê Huyton ê L36 9GL
Save time – use the IT Service Desk Self Serve Application
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or
retain this email or any part of it and do not take any action based on it.
Unless expressly stated, opinions in this email are those of the individual
sender, and not of Knowsley MBC. Legally binding obligations can only be
created for, or be entered into on behalf of, Knowsley MBC by duly authorised
officers or representatives.
Knowsley MBC excludes any liability whatsoever for any offence caused, any
direct or consequential loss arising from the use, or reliance on, this
e-mail or its contents. We believe but do not warrant that this e-mail and
any attachments are virus free. You must therefore take full responsibility
for virus checking and no responsibility is accepted for loss or damage
arising from viruses or changes made to this message after it was sent.
Knowsley MBC reserves the right to monitor and/or record all e-mail
communications through its network in accordance with relevant legislation.
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or
retain this email or any part of it and do not take any action based on it.
Unless expressly stated, opinions in this email are those of the individual
sender, and not of Knowsley MBC. Legally binding obligations can only be
created for, or be entered into on behalf of, Knowsley MBC by duly authorised
officers or representatives.
Re: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too sensitive
Hi,
Check with Firebug which kind of requests your application is really sending to
Geoserver. It looks like it can use WFS and GetFeature but until now I have
believed it is WMS and GetFeatureInfo. Actually you would probably get better
answers from OpenLayers list.
-Jukka Rahkonen-
Russell Hore wrote:
This is my code;
control = new OpenLayers.Control.GetFeature({
protocol: OpenLayers.Protocol.WFS.fromWMSLayer(theLayer),
box: false,
hover: false,
maxFeatures: 20,
multipleKey: shiftKey,
toggleKey: ctrlKey,
clickTolerance:30
});
control.events.register(featureselected, this, function(e) {
selected.addFeatures([e.feature]); displayInfo(e); });
control.events.register(featureunselected, this, function(e) {
selected.removeFeatures([e.feature]);});
control.events.register(hoverfeature, this, function(e) {
hover.addFeatures([e.feature]); displayInfo(e); });
control.events.register(outfeature,this, function(e) {
hover.removeFeatures([e.feature]); });
map.addControl(control);
control.activate();
Note the clickTolerance line
Russ
On 9 Oct 2014, at 16:02, Ismail, Mark
mark.ism...@knowsley.gov.ukmailto:mark.ism...@knowsley.gov.uk wrote:
Hi
Thanks for the replies
Ive tried
vendorParams: { buffer:100 },
tolerance: 100,
in the openlayers wmsgetfeatureinfo request but no change, the points are still
very difficult to click even with these extreme settings
From the open layers docs tolerance doesn’t seem to be a supported parameter
anymore though
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council • Westmorland Road • Huyton • L36 9GL
Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/
Application
From: Jerome A. Wendell [mailto:jawend...@suddenlink.net]
Sent: 09 October 2014 14:32
To: Ismail, Mark; 'geoserver mailing, list'
Subject: RE: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
Mark,
You might take a look at the clickTolerance setting as described at the link
below:
http://dev.openlayers.org/releases/OpenLayers-2.13.1/doc/apidocs/files/OpenLayers/Control/GetFeature-js.html#OpenLayers.Control.GetFeature.clickTolerance
Hope this helps.
Jerome Wendell
From: Ismail, Mark [mailto:mark.ism...@knowsley.gov.uk]
Sent: Thursday, October 09, 2014 9:06 AM
To: geoserver mailing, list
(geoserver-users@lists.sourceforge.netmailto:geoserver-users@lists.sourceforge.net)
Subject: [Geoserver-users] openlayers WMSGetFeatureInfo and geoserver too
sensitive
I am using openlayers 2 and issuing a WMSGetFeatureInfo request to geoserver
It works fine but It is far to sensitive to where you click – if you don’t get
right in the centre of a point or icon it finds nothing, it can take 2 or 3
attempts to get a response even if clicking carefully and zoomed in
Is there any way to make that click “less sensitive” so it will pick up the
closest point to the mouse click ?
I know this isn’t strictly a geoserver issue but I’ve found nothing useful on
the openlayers forums
Mark Ismail
Principal IT Officer
Tel: 0151 443 3021
Knowsley Council • Westmorland Road • Huyton • L36 9GL
Save time – use the IT Service Desk Self Servehttp://kmbcselfservice/
Application
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or retain
this email or any part of it and do not take any action based on it.
Unless expressly stated, opinions in this email are those of the individual
sender, and not of Knowsley MBC. Legally binding obligations can only be
created for, or be entered into on behalf of, Knowsley MBC by duly authorised
officers or representatives.
Knowsley MBC excludes any liability whatsoever for any offence caused, any
direct or consequential loss arising from the use, or reliance on, this e-mail
or its contents. We believe but do not warrant that this e-mail and any
attachments are virus free. You must therefore take full responsibility for
virus checking and no responsibility is accepted for loss or damage arising
from viruses or changes made to this message after it was sent. Knowsley MBC
reserves the right to monitor and/or record all e-mail communications through
its network in accordance with relevant legislation.
This e-mail and any attachments are confidential. It may contain privileged
information and is intended for the named recipient(s) only. It must not be
distributed without consent. If you are not one of the intended recipients,
please notify the sender immediately and do not disclose, distribute, or retain
this email or any part of it and do not take any
