Hi All,
I use mapbender and geoserver. At
http://www.mapbender.org/index.php/FeatureInfo they say:
"Every click into the map with the mouse cursor starts a spatial request for
features at that coordinate. Frequently the request is performed with a
server side configurable tolerance of 7 to 10 pixels"
Is there a possibility in geoserver to adjust the tolerance? It seems to be
smaller than 7 Pixels, perhaps 4 or 5 on my maps. Can it be adjusted to
larger values?
Regards,
Tilo
Hi Tilo,
Currently this is not configurable. but i agree that it would be useful
for the client to be able to specify the size of a buffer. As clicking
on points and lines sometimes can be quite tedious.
Do you want to create a feature request in the issue tracker?
-Justin
Tilo Wütherich wrote:
Hi All,
I use mapbender and geoserver. At
http://www.mapbender.org/index.php/FeatureInfo they say:"Every click into the map with the mouse cursor starts a spatial request for
features at that coordinate. Frequently the request is performed with a
server side configurable tolerance of 7 to 10 pixels"Is there a possibility in geoserver to adjust the tolerance? It seems to be
smaller than 7 Pixels, perhaps 4 or 5 on my maps. Can it be adjusted to
larger values?Regards,
Tilo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,471f2f159713327367457!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Hi Justin,
Do you want to create a feature request in the issue tracker?
yes, I will try...
I'm wondering why this is an issue for the server and not for the SLD. BTW, for myself I do not have problems to hit small symbols accurate, but if you have larger ones with no obvious centre it's really a quest 
Regards,
Tilo
Justin Deoliveira ha scritto:
Hi Tilo,
Currently this is not configurable. but i agree that it would be useful
for the client to be able to specify the size of a buffer. As clicking
on points and lines sometimes can be quite tedious.Do you want to create a feature request in the issue tracker?
Tilo has created the issue here:
http://jira.codehaus.org/browse/GEOS-1434
Now, I was thinking about it a little and it occurred to me it
has a striking resemblance to the meta-buffer issue.
The meta-buffer is the number of extra pixels we consider around
an image to make sure every feature contributing to the
current map gets rendered for good. When features such as points
have big symbolizers (think a big circle) they do contribute
(partially) to the current map even if their geometry lay outside
of the map bounds. The meta buffer is the measure of the biggest
symbolizer (bigger point, thicker line) used in the map styling.
Now, if you think about it, the size of the ideal getfeatureinfo
search area is exactly the meta-buffer. What's more interesting is
that we already have code to automatically compute the meta buffer
from the map style, so most of the time you would not even need
to provide it manually.
To recap the idea is:
* make GetFeatureInfo use the metabuffer computation code and
use a search area that matches the biggest symbol size for each
layer (in fact, half of the symbol size)
* as with GetMap, if the user provides "&buffer=xxx" then use
it as the search area for GetFeatureInfo.
How does this sound?
Cheers
Andrea
+1, sounds like a good way to handle it.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi Tilo,
Currently this is not configurable. but i agree that it would be useful
for the client to be able to specify the size of a buffer. As clicking
on points and lines sometimes can be quite tedious.Do you want to create a feature request in the issue tracker?
Tilo has created the issue here:
http://jira.codehaus.org/browse/GEOS-1434Now, I was thinking about it a little and it occurred to me it
has a striking resemblance to the meta-buffer issue.
The meta-buffer is the number of extra pixels we consider around
an image to make sure every feature contributing to the
current map gets rendered for good. When features such as points
have big symbolizers (think a big circle) they do contribute
(partially) to the current map even if their geometry lay outside
of the map bounds. The meta buffer is the measure of the biggest
symbolizer (bigger point, thicker line) used in the map styling.Now, if you think about it, the size of the ideal getfeatureinfo
search area is exactly the meta-buffer. What's more interesting is
that we already have code to automatically compute the meta buffer
from the map style, so most of the time you would not even need
to provide it manually.To recap the idea is:
* make GetFeatureInfo use the metabuffer computation code and
use a search area that matches the biggest symbol size for each
layer (in fact, half of the symbol size)
* as with GetMap, if the user provides "&buffer=xxx" then use
it as the search area for GetFeatureInfo.How does this sound?
Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,472051e0273333668746562!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
I have received a shapefile that has a custom projection associated with it. I loaded it into PostGIS and then linked it to geoserver, however, I do not know how to indicate what the native SRS WKT is. Can anyone give me any pointers? Thanks, David Robison
--
David R Robison
Open Roads Consulting, Inc.
708 S. Battlefield Blvd., Chesapeake, VA 23322
phone: (757) 546-3401
e-mail: drrobison@anonymised.com
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/book_detail.php?id=2579
Hi David,
So are you saying that you have the SRS WKT? or that you do not have it
and need a way to figure it out. If its the former you can follow the
instructions here:
http://docs.codehaus.org/display/GEOSDOC/Custom+projection+definition+in+Geoserver+1.5.0+(onwards)
If the latter i am unsure. Reverse engineering the projection of a
shapefile is kind of tough. I will leave that one for the experts.
-Justin
David R Robison wrote:
I have received a shapefile that has a custom projection associated with
it. I loaded it into PostGIS and then linked it to geoserver, however, I
do not know how to indicate what the native SRS WKT is. Can anyone give
me any pointers? Thanks, David Robison
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
+1 on the metabuffer stuff.
Also, it is not strange that it gets difficult to find a point through
GetFeatureInfo. When sending a GetFeatureInfo from a ui, it gets really
tricky to click on a point near enough to the actual point. See for example
the attached image. Its the result of rendering the same point with a small
circle marker and a bigger triangle marker.
The triangle is never centered at the point location, but its top most corner
seems to be.
So, I don't quite remember if the SLD spec says nothing about how to locate a
marker regarding the point location, still it seems quite intuitive (as a
user) to get them centered.
So, should we open an issue against the renderer at all?
Gabriel
On Thursday 25 October 2007 05:26:52 pm Justin Deoliveira wrote:
+1, sounds like a good way to handle it.
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi Tilo,
>>
>> Currently this is not configurable. but i agree that it would be useful
>> for the client to be able to specify the size of a buffer. As clicking
>> on points and lines sometimes can be quite tedious.
>>
>> Do you want to create a feature request in the issue tracker?
>
> Tilo has created the issue here:
> http://jira.codehaus.org/browse/GEOS-1434
>
> Now, I was thinking about it a little and it occurred to me it
> has a striking resemblance to the meta-buffer issue.
> The meta-buffer is the number of extra pixels we consider around
> an image to make sure every feature contributing to the
> current map gets rendered for good. When features such as points
> have big symbolizers (think a big circle) they do contribute
> (partially) to the current map even if their geometry lay outside
> of the map bounds. The meta buffer is the measure of the biggest
> symbolizer (bigger point, thicker line) used in the map styling.
>
> Now, if you think about it, the size of the ideal getfeatureinfo
> search area is exactly the meta-buffer. What's more interesting is
> that we already have code to automatically compute the meta buffer
> from the map style, so most of the time you would not even need
> to provide it manually.
>
> To recap the idea is:
> * make GetFeatureInfo use the metabuffer computation code and
> use a search area that matches the biggest symbol size for each
> layer (in fact, half of the symbol size)
> * as with GetMap, if the user provides "&buffer=xxx" then use
> it as the search area for GetFeatureInfo.
>
> How does this sound?
> Cheers
> Andrea
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> !DSPAM:4007,472051e0273333668746562!
Gabriel Roldán ha scritto:
+1 on the metabuffer stuff.
Also, it is not strange that it gets difficult to find a point through GetFeatureInfo. When sending a GetFeatureInfo from a ui, it gets really tricky to click on a point near enough to the actual point. See for example the attached image. Its the result of rendering the same point with a small circle marker and a bigger triangle marker.
The triangle is never centered at the point location, but its top most corner seems to be.
So, I don't quite remember if the SLD spec says nothing about how to locate a marker regarding the point location, still it seems quite intuitive (as a user) to get them centered.
So, should we open an issue against the renderer at all?
Yes, please do. In fact I've just checked with circle and square, and they are centered, so it seems to me the problem is triangle spefic.
In fact, the full set of well known marks should be tested, there
are others:
Square
Triangle
Cross
Circle
Star
X
Arrow
Hatch
Cheers
Andrea