Thanks Andrea,

I've requested an account. When I get it I'll open a ticket.

I've added
      vendorParams: {
        buffer: 20  // geoserver buffer in pixels
      },
to my WMSGetFeatureInfo control and now it is working great on my mobile
device as well.

But can the buffer be scale depending, meaning can I set the pixels
afterward?
I have a lot of points along a river, at low zoom levels the points are
close to each other. Using the buffer selects sometimes the wrong point.
At higher zoom levels the points have more space between them, then the
buffer is needed.

And I'm also still struggling with the SLD because when I create an extra
rule using MinScale... to set uom="
http://www.opengeospatial.org/se/units/metre"; only at higher zoom levels I
also get an additional entry in my legend graphic.
I will do some more research, perhaps I need two separate layers each with
their own SLD and group them together. But I have 4 layers and more will be
added ;(


Thanks,

Paul


2013/8/28 Andrea Aime <[email protected]>

> On Wed, Aug 28, 2013 at 8:49 AM, Paul Meems <[email protected]>wrote:
>
>> Thanks Andrea,
>>
>> Adding uom="http://www.opengeospatial.org/se/units/metre"; to my
>> PointSymbolizer is really improving the size of the point at higher zoom
>> levels.
>> I'll alter my sld to use pixel size on low zoom levels and meter size at
>> higher zoom levels.
>>
>> But the main problem for me is not solved. This might be a non-geoserver
>> issue but more of an OpenLayers issue.
>> When I click on the point a pop-up needs to be shown using
>> OpenLayers.Control.WMSGetFeatureInfo.
>> This works great using a desktop with a mouse, but on a mobile device it
>> is very hard to select the point.
>> I'd hoped making the points bigger at higher zoom levels would improve
>> this, but there's no change.
>>
>
> Doh... I would have thought the same, but I see the GetFeatureInfo code is
> not taking into account the uom
> rescaling. This is a bug, can you open a ticket on jira.codehaus.org?
>
> About a workaround for you, you can try adding &buffer=n to your
> GetFeatureInfo request, where N is the
> number of pixels you want to use as the search area
>
> Cheers
> Andrea
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.geo-solutions.it 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
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to