the layers are set to ON/OFF for most actions in
pm.common.php->PMCommon:setGroups()
This method is called in query.php
In this file there is also the variable $this->querygroups that is for
the select mode just one (define previously). You need to add into this
array all groups/layers. You can pass the groups for query via a GET:
if (isset($_REQUEST["groups"])) {
armin
On 05/03/2010 18:49, Daniel Gaudreault wrote:
> Hi Armin,
>
> PHP & Javascript is no problem. We already have a custom tool that does
> some extra stuff past what you selection tool does. I also realize that
> we need to force it. Actually, what I was asking for was a quick sample,
> explanation as to -where- to force it and maybe a quick sample of how.
>
> Thanks,
> Dan
>
> On 3/5/2010 12:30 PM, Armin Burger wrote:
>> the behaviour of p.mapper is that it only returns queries for layers
>> that are enabled and visible at current scale (you get only what you
>> see...). If you want to have it different then you need to work directly
>> on the code and implement it. Maybe someone here can help you.
>>
>> When I said I forced select to work on 2 layers then I hard-coded them
>> for a quick test in the code. To have this for all layers you also need
>> to define a custom tool that does this.
>>
>> The wiki and some plugins might help you for this, but you still will
>> need enough knowledge of PHP+MapScript and Javascript.
>>
>> armin
>>
>>
>>
>> On 05/03/2010 03:12, Daniel Gaudreault wrote:
>>> I think you nailed the problem with your last statement, but let's see
>>> if I can clarify a little bit. I am new at pmapper so please bear with
>>> me a bit.
>>>
>>> We have a a layer of data that is disabled if it is past a certain zoom
>>> level. We can't select the layer or anything on it until we zoom in
>>> enough. Our custom selection tool works great if you are zoomed in
>>> enough. You select an area or a specific record and it opens up a web
>>> page with the custom info attached to it. Both our tool and your
>>> selection tools work great.
>>>
>>> However, when zoomed out a bit or even all the way out to the extents
>>> of the map, the data on that layer become unavailable for viewing or
>>> selection. What we would like to do is force the selection to a
>>> specific layer or to all layers regardless of zoom level. So, I think
>>> that your last statement was exactly what I am after. Could you explain
>>> to me how to force the search?
>>>
>>> Thanks,
>>> Dan
>>>
>>> On 3/4/2010 5:51 PM, Armin Burger wrote:
>>>> On 04/03/2010 21:03, Daniel Gaudreault wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am trying to figure out how to allow a selection of all object
>>>>> regardless of zoom level or layer selection. We've already created our
>>>>> own plugin that allows us to select and return a range of data and
>>>>> display related information in a custom webapp. However, we seem to be
>>>>> restrained to a specific zoom level before we can actually search this
>>>>> layer. So my question boils down to:
>>>>>
>>>>> Is it possible to search/select all objects on any layer either by
>>>>> single click or area select regardless of the zoom level. Or by the
>>>>> same token where do we set the zoom level that a given layer can start
>>>>> appearing at?
>>>>>
>>>>> My environment consists of:
>>>>> p.mapper 4.0
>>>>> PHP 5.3 running on Mac OSX Snow Leopard
>>>>>
>>>>> Thanks,
>>>>> Dan Gaudreault
>>>>>
>>>>>
>>>> I don't understand exactly your problem. If I use identify or select
>>>> functions and click at whatever zoom level on the map I always get
>>>> results. The select is currently only applied on a single layer but
>>>> also
>>>> this could be modified without too much of work (if I force it to use 2
>>>> or more layers it does it correctly, both showing the result table and
>>>> the highlight on the map for all defined layers).
>>>>
>>>> armin
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> pmapper-users mailing list
>>>> pmapper-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>>>
>>
>> ------------------------------------------------------------------------------
>>
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> pmapper-users mailing list
>> pmapper-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users
