I would like to propose an improvement to GeoServer. By default the pixel tolerance on getfeatureinfo queries is set to 2 pixels. Unfortunately this is hard-coded into GeoServer. There are feature types like line and point features that this level of tolerance is far from ideal in most situations. Therefore I suggest that the pixel tolerance should be made user configurable on a per layer basis.
The proposal is available here:
best regards
Darren Graham
Win £3000 to spend on whatever you want at Uni! Click here to WIN!
Hi Darren,
I looked over the proposal and I definitely think that this is something that might be worth while in GeoServer. Is this something you plan to implement and submit a patch for? Or is it more of a feature request?
If its a feature request I think the more appropriate route would just be to issue a feature request in the bug tracker, as its a relatively uncomplicated request. Full blown proposals are more meant for larger changes in which the individual who writes the proposal intends to implement it.
-Justin
Darren Graham wrote:
I would like to propose an improvement to GeoServer. By default the pixel tolerance on getfeatureinfo queries is set to 2 pixels. Unfortunately this is hard-coded into GeoServer. There are feature types like line and point features that this level of tolerance is far from ideal in most situations. Therefore I suggest that the pixel tolerance should be made user configurable on a per layer basis.
The proposal is available here:
- http://geoserver.org/display/GEOS/GSIP+27+-+Pixel+Tolerance+on+GetFeatureInfo
best regards
Darren Graham
------------------------------------------------------------------------
Win £3000 to spend on whatever you want at Uni! Click here to WIN! <http://clk.atdmt.com/UKM/go/111354032/direct/01/>
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
hi Darren,
You will probably be interested in this thread from the developers list:
http://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg04500.html
In short, it looks like this is going to get implemented soon and be available in the 1.7.4 release.
-Justin
Darren Graham wrote:
sorry for the lateness. but I agree this should be a feature request. So far I've been adjusting the pixel tolerance manually and recompiling. which is fr from ideal. In short I don't know enough about the inner workings to suggest the best course of action to implement this change specially if it's customizable per featuretype/layer.
has there been any developments in this area since then?
best regards
Darren
> Date: Thu, 16 Oct 2008 10:23:14 -0600
> From: jdeolive@anonymised.com
> To: darrenfgraham@anonymised.com
> CC: geoserver-users@lists.sourceforge.net
> Subject: Re: [Geoserver-users] GSIP#27 - Pixel Tolerance on GetFeatureInfo
>
> Hi Darren,
>
> I looked over the proposal and I definitely think that this is something
> that might be worth while in GeoServer. Is this something you plan to
> implement and submit a patch for? Or is it more of a feature request?
>
> If its a feature request I think the more appropriate route would just
> be to issue a feature request in the bug tracker, as its a relatively
> uncomplicated request. Full blown proposals are more meant for larger
> changes in which the individual who writes the proposal intends to
> implement it.
>
> -Justin
>
> Darren Graham wrote:
> > I would like to propose an improvement to GeoServer. By default the
> > pixel tolerance on getfeatureinfo queries is set to 2 pixels.
> > Unfortunately this is hard-coded into GeoServer. There are feature
> > types like line and point features that this level of tolerance is far
> > from ideal in most situations. Therefore I suggest that the pixel
> > tolerance should be made user configurable on a per layer basis.
> >
> > The proposal is available here:
> > -
> > http://geoserver.org/display/GEOS/GSIP+27+-+Pixel+Tolerance+on+GetFeatureInfo
> >
> > best regards
> >
> > Darren Graham
> >
> > ------------------------------------------------------------------------
> > Win £3000 to spend on whatever you want at Uni! Click here to WIN!
> > <http://clk.atdmt.com/UKM/go/111354032/direct/01/>
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> > Build the coolest Linux based applications with Moblin SDK & win great prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Geoserver-users mailing list
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
------------------------------------------------------------------------
" Upgrade to Internet Explorer 8 Optimised for MSN. " Download Now <http://extras.uk.msn.com/internet-explorer-8/?ocid=T010MSN07A0716U>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
hi Darren,
You will probably be interested in this thread from the developers list:
http://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg04500.html
In short, it looks like this is going to get implemented soon and be available in the 1.7.4 release.
It has actually already been implemented thanks to the sponsorship of
an italian company. The fixes are described in these two jiras:
http://jira.codehaus.org/browse/GEOS-1008
http://jira.codehaus.org/browse/GEOS-1434
There is no "per feature type" configuration, but the mechanism is probably better than that. You can specify the tolerance per request,
and if you don't, GeoServer will figure out an optimal radius on
a per layer basis inspecting the sizes of the symbolizers in
the associated style. The automatic lookup fails only if there is
any size is the value of an attribute (and thus cannot be known
beforehand).
Also, with the GEOS-1008 fixes GFI takes into account the current
zoom level and the rule filters, so it should report back only
features that actually drawn on the map.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.