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.
>
> 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=154622311&iu=/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=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
