pmapper-users — p.mapper users mailing list

Re: [pmapper-users] search one layer

[Bogumił S. <sz...@ku...>]

I have tried and it doesn't work.
Like before I have normal "search for" label and then I have to select 
my one layer to search.
:(

Bogumił


W dniu 2014-07-23 20:38, Armin Burger pisze:
> Ok, the change event is not applied if no change happens... Try the
> following for the custom.js which should also improve the labels and
> logic in this case:
>
> $.extend(PM.Query,
> {
>       createSearchItems: function(url) {
>           $.ajax({
>               url: url,
>               dataType: "json",
>               success: function(response){
>                   var searchJson = response.searchJson;
>                   var action = response.action;
>
>                   if (action == 'searchitem') {
>                       PM.Query.createSearchInput(searchJson);
>                   } else {
>                       delete searchJson.options[0];
>                       var searchHtml = PM.Query.json2Select(searchJson, "0");
>                       $('#searchoptions').html(searchHtml);
>                       PM.Query.setSearchInput();
>                       $('#searchoptions').html(_p("Search
> for")).css({"white-space": "nowrap"});
>                   }
>               },
>               error: function (XMLHttpRequest, textStatus, errorThrown) {
>                   if (window.console) console.log(errorThrown);
>               }
>           });
>       }
>
> });
>
>
> On 07/23/2014 08:58 AM, Bogumił Szady wrote:
>> Hello,
>> Thanks. I have tried to insert this modification.
>> I see my layer defined, but without white box on the right to put the
>> search attribute.
>> Where is the the problem?
>>
>> best
>>
>> Bogumił
>>
>>
>> W dniu 2014-07-22 23:11, Armin Burger pisze:
>>> not a very elegant solution, but should work:
>>>
>>> add the following block at the end of your
>>>        /config/[your-config]/custom.js
>>> file
>>>
>>> $.extend(PM.Query,
>>> {
>>>         createSearchItems: function(url) {
>>>             $.ajax({
>>>                 url: url,
>>>                 dataType: "json",
>>>                 success: function(response){
>>>                     var searchJson = response.searchJson;
>>>                     var action = response.action;
>>>
>>>                     //---------------------------
>>>                     delete searchJson.options[0];
>>>                     //---------------------------
>>>
>>>                     if (action == 'searchitem') {
>>>                         PM.Query.createSearchInput(searchJson);
>>>                     } else {
>>>                         var searchHtml = PM.Query.json2Select(searchJson, "0");
>>>                         $('#searchoptions').html(searchHtml);
>>>                     }
>>>                 },
>>>                 error: function (XMLHttpRequest, textStatus, errorThrown) {
>>>                     if (window.console) console.log(errorThrown);
>>>                 }
>>>             });
>>>         }
>>>
>>> });
>>>
>>>
>>>
>>>
>>> or use
>>>
>>>                     //---------------------------
>>>                     if (Object.keys(searchJson.options).length < 3) {
>>>                         delete searchJson.options[0];
>>>                     }
>>>                     //---------------------------
>>>
>>> to do this just in case the search has just 1 layer defined for search,
>>> in case you once will add another one you don't remember what you once
>>> modified...
>>>
>>>
>>> On 07/22/2014 07:25 PM, Bogumił Szady wrote:
>>>> Hello,
>>>> Is it possible to get one default search field turned on in the moment
>>>> of starting of application window?
>>>> I have only one layer to search and I would like to avoid every time
>>>> selecting layer to search.
>>>>
>>>>
>>>> all the best
>>>>
>>>> Bogumił
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Want fast and easy access to all the code in your enterprise? Index and
>>>> search up to 200,000 lines of code with a free copy of Black Duck
>>>> Code Sight - the same software that powers the world's largest code
>>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>>> http://p.sf.net/sfu/bds
>>>> _______________________________________________
>>>> pmapper-users mailing list
>>>> pma...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>>>
>>> ------------------------------------------------------------------------------
>>> Want fast and easy access to all the code in your enterprise? Index and
>>> search up to 200,000 lines of code with a free copy of Black Duck
>>> Code Sight - the same software that powers the world's largest code
>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>> http://p.sf.net/sfu/bds
>>> _______________________________________________
>>> pmapper-users mailing list
>>> pma...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] search one layer

[Armin B. <arm...@gm...>]

Ok, the change event is not applied if no change happens... Try the 
following for the custom.js which should also improve the labels and 
logic in this case:

$.extend(PM.Query,
{
     createSearchItems: function(url) {
         $.ajax({
             url: url,
             dataType: "json",
             success: function(response){
                 var searchJson = response.searchJson;
                 var action = response.action;

                 if (action == 'searchitem') {
                     PM.Query.createSearchInput(searchJson);
                 } else {
                     delete searchJson.options[0];
                     var searchHtml = PM.Query.json2Select(searchJson, "0");
                     $('#searchoptions').html(searchHtml);
                     PM.Query.setSearchInput();
                     $('#searchoptions').html(_p("Search 
for")).css({"white-space": "nowrap"});
                 }
             },
             error: function (XMLHttpRequest, textStatus, errorThrown) {
                 if (window.console) console.log(errorThrown);
             }
         });
     }

});


On 07/23/2014 08:58 AM, Bogumił Szady wrote:
> Hello,
> Thanks. I have tried to insert this modification.
> I see my layer defined, but without white box on the right to put the
> search attribute.
> Where is the the problem?
>
> best
>
> Bogumił
>
>
> W dniu 2014-07-22 23:11, Armin Burger pisze:
>> not a very elegant solution, but should work:
>>
>> add the following block at the end of your
>>       /config/[your-config]/custom.js
>> file
>>
>> $.extend(PM.Query,
>> {
>>        createSearchItems: function(url) {
>>            $.ajax({
>>                url: url,
>>                dataType: "json",
>>                success: function(response){
>>                    var searchJson = response.searchJson;
>>                    var action = response.action;
>>
>>                    //---------------------------
>>                    delete searchJson.options[0];
>>                    //---------------------------
>>
>>                    if (action == 'searchitem') {
>>                        PM.Query.createSearchInput(searchJson);
>>                    } else {
>>                        var searchHtml = PM.Query.json2Select(searchJson, "0");
>>                        $('#searchoptions').html(searchHtml);
>>                    }
>>                },
>>                error: function (XMLHttpRequest, textStatus, errorThrown) {
>>                    if (window.console) console.log(errorThrown);
>>                }
>>            });
>>        }
>>
>> });
>>
>>
>>
>>
>> or use
>>
>>                    //---------------------------
>>                    if (Object.keys(searchJson.options).length < 3) {
>>                        delete searchJson.options[0];
>>                    }
>>                    //---------------------------
>>
>> to do this just in case the search has just 1 layer defined for search,
>> in case you once will add another one you don't remember what you once
>> modified...
>>
>>
>> On 07/22/2014 07:25 PM, Bogumił Szady wrote:
>>> Hello,
>>> Is it possible to get one default search field turned on in the moment
>>> of starting of application window?
>>> I have only one layer to search and I would like to avoid every time
>>> selecting layer to search.
>>>
>>>
>>> all the best
>>>
>>> Bogumił
>>>
>>> ------------------------------------------------------------------------------
>>> Want fast and easy access to all the code in your enterprise? Index and
>>> search up to 200,000 lines of code with a free copy of Black Duck
>>> Code Sight - the same software that powers the world's largest code
>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>> http://p.sf.net/sfu/bds
>>> _______________________________________________
>>> pmapper-users mailing list
>>> pma...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>

Re: [pmapper-users] pmapper4: new plugins and options

[jose m. <jos...@gm...>]

i'm sorry

i don't really understand the operator for selections in case of the
intersection... i need a simple demonstration...

i tried to save selections with a clean pmapper install and demo date (ms4w)
but doesn't work too. I can not see the error, but I suppose it is the same:

[23-Jul-2014 10:34:54 UTC] PHP Fatal error:  Call to undefined function
getLayersByGroupOrLayerName() in
/var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
on line 461

my layers are postgis type.

Thanks a lot again



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025568.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] pmapper4: new plugins and options

[Thomas R. <tr...@si...>]

Le 23/07/2014 10:37, jose mvm a écrit :
> good morning Thomas and Armin - the sun rises earlier in France!
>
> ok, the small php notice disappears with new revision of layerview.php.
>
> thanks for your explain about clientdynamiclayers plugin - yes i have my
> code all updated.
>
> really, i can do intersections using a buffer! - but not with selections
> from the searchtool or queryeditor.

The "operators" for selections only considers objects and their ids, not 
their geometry. So you have to compare things about the same layers:
- your current selection contains countries (and others layers objects, 
why not: towns, ...)
- your will make a new attribute search on countries (by name for instance)
- with the operator intersection
- the result will be : the towns from your search that were in your 
previous selection.


>
> save selections do not work with my installation yet - and I think this
> plugin is very interesting too.

Really? Have you try with a clean pmapper install and demo date? What 
type are your layers (SHP, postgis, ...) ?

>
> Thanks
>
>
>
> --
> View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025566.html
> Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
>

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

Re: [pmapper-users] pmapper4: new plugins and options

[jose m. <jos...@gm...>]

good morning Thomas and Armin - the sun rises earlier in France!

ok, the small php notice disappears with new revision of layerview.php.

thanks for your explain about clientdynamiclayers plugin - yes i have my
code all updated.

really, i can do intersections using a buffer! - but not with selections
from the searchtool or queryeditor.

save selections do not work with my installation yet - and I think this
plugin is very interesting too.

Thanks



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025566.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] pmapper4: new plugins and options

[Thomas R. <tr...@si...>]

You can use buffer in the graphical queries to intersect geometries.

Intersection of selection is the elements that are in both of 2 selections.

Le 22/07/2014 22:30, jose mvm a écrit :
> i'm sorry.
>
> i can get intersections within only a single layer.
>
> but I suppose the intersection operation works with different layers...
>
> eg: intersect the points from one layer (POINT) that are completely within
> the polygon feature (from another layer/POLYGON)...
>
> or is not this the purpose of the tool? if not, then my only problem is to
> save the selections.
>
> Thanks again
>
>
>
>
>
> --
> View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025560.html
> Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
>

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

Re: [pmapper-users] pmapper4: new plugins and options

[Thomas R. <tr...@si...>]

In the slectionManagement README.TXT, there is :

 > Dependancies:
 > - plugins/common/selectTools.inc.php
 > - plugins/clientDynamicLayers/*

Have you got those files i?n your pmapper? Are they up-to-date?

Le 22/07/2014 21:53, jose mvm a écrit :
> ok, my php errors level is on the maximum for to help me to understand and
> report the problems.
> but i have a fatal error when i try to save the selections as i showed:
>
> [22-Jul-2014 16:40:46 UTC] PHP Fatal error:  Call to undefined function
> getLayersByGroupOrLayerName() in
> /var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
> on line 461
>
> and basicaly i can't get intersections (and i have no php errors about it).
>
> Thank you very much Armin Burger
> Congratulations for your great work!!!
>
>
>
> --
> View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025559.html
> Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
>

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

Re: [pmapper-users] pmapper4: new plugins and options

[Thomas R. <tr...@si...>]

Hi,

Le 22/07/2014 18:51, jose mvm a écrit :
> Hi Thomas,
>
> after update the pmapper code, i found some questions and difficulties:
>
> - when pmapper start up php notice apeears (repeatedly):
> [22-Jul-2014 16:06:49 UTC] PHP Notice:  Undefined variable: dynamicClasses
> in /var/www/pmapper-4.3.2/incphp/layerview.php on line 218
>
> but no problem...

Just a small notice, no pb. It will be solved solved in a future revision.

>
> - when i make a search the table of results appears closed by default... (no
> probem too)
>
> but my main problem, possibly, is that I don't understand the philosophy,
> the goal, the mechanism and operation of the "clientDynamicLayers". i don't
> understand the "examples" contained in plugin.

This is not a plugin, but a part of code shared by few others plugins: 
drawing, measure2, exportPoints, SelectionManagement, ... Its goal is to 
add dynamic data from your browser to server part of pmapper.

If you have development skills the code in example is to add in your js 
console (Firebug in Firefox for instance). Be careful to the coordinates 
in the examples: they have have to fit with your map. And you have to 
add the template-part.map to your real template.map (I've just commited 
a small correction for MapServer >= 6: 
http://svn.pmapper.net/trac/changeset/1352 )



> and without this dependence plugin, the selectionManagement plugin doesn't
> work correctly. i can't save selections.


Yes it is a dependency: you can't use selectionManagement without 
clientDynamicLayers.

>
> Thanks in advence
> Best regards
Thomas

	
	

Re: [pmapper-users] search one layer

[Bogumił S. <sz...@ku...>]

Hello,
Thanks. I have tried to insert this modification.
I see my layer defined, but without white box on the right to put the 
search attribute.
Where is the the problem?

best

Bogumił


W dniu 2014-07-22 23:11, Armin Burger pisze:
> not a very elegant solution, but should work:
>
> add the following block at the end of your
>      /config/[your-config]/custom.js
> file
>
> $.extend(PM.Query,
> {
>       createSearchItems: function(url) {
>           $.ajax({
>               url: url,
>               dataType: "json",
>               success: function(response){
>                   var searchJson = response.searchJson;
>                   var action = response.action;
>
>                   //---------------------------
>                   delete searchJson.options[0];
>                   //---------------------------
>
>                   if (action == 'searchitem') {
>                       PM.Query.createSearchInput(searchJson);
>                   } else {
>                       var searchHtml = PM.Query.json2Select(searchJson, "0");
>                       $('#searchoptions').html(searchHtml);
>                   }
>               },
>               error: function (XMLHttpRequest, textStatus, errorThrown) {
>                   if (window.console) console.log(errorThrown);
>               }
>           });
>       }
>
> });
>
>
>
>
> or use
>
>                   //---------------------------
>                   if (Object.keys(searchJson.options).length < 3) {
>                       delete searchJson.options[0];
>                   }
>                   //---------------------------
>
> to do this just in case the search has just 1 layer defined for search,
> in case you once will add another one you don't remember what you once
> modified...
>
>
> On 07/22/2014 07:25 PM, Bogumił Szady wrote:
>> Hello,
>> Is it possible to get one default search field turned on in the moment
>> of starting of application window?
>> I have only one layer to search and I would like to avoid every time
>> selecting layer to search.
>>
>>
>> all the best
>>
>> Bogumił
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] search one layer

[Armin B. <arm...@gm...>]

not a very elegant solution, but should work:

add the following block at the end of your
    /config/[your-config]/custom.js
file

$.extend(PM.Query,
{
     createSearchItems: function(url) {
         $.ajax({
             url: url,
             dataType: "json",
             success: function(response){
                 var searchJson = response.searchJson;
                 var action = response.action;

                 //---------------------------
                 delete searchJson.options[0];
                 //---------------------------

                 if (action == 'searchitem') {
                     PM.Query.createSearchInput(searchJson);
                 } else {
                     var searchHtml = PM.Query.json2Select(searchJson, "0");
                     $('#searchoptions').html(searchHtml);
                 }
             },
             error: function (XMLHttpRequest, textStatus, errorThrown) {
                 if (window.console) console.log(errorThrown);
             }
         });
     }

});




or use

                 //---------------------------
                 if (Object.keys(searchJson.options).length < 3) {
                     delete searchJson.options[0];
                 }
                 //---------------------------

to do this just in case the search has just 1 layer defined for search, 
in case you once will add another one you don't remember what you once 
modified...


On 07/22/2014 07:25 PM, Bogumił Szady wrote:
> Hello,
> Is it possible to get one default search field turned on in the moment
> of starting of application window?
> I have only one layer to search and I would like to avoid every time
> selecting layer to search.
>
>
> all the best
>
> Bogumił
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>

Re: [pmapper-users] pmapper4: new plugins and options

[jose m. <jos...@gm...>]

i'm sorry.

i can get intersections within only a single layer.

but I suppose the intersection operation works with different layers... 

eg: intersect the points from one layer (POINT) that are completely within
the polygon feature (from another layer/POLYGON)...

or is not this the purpose of the tool? if not, then my only problem is to
save the selections.

Thanks again





--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025560.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] pmapper4: new plugins and options

[jose m. <jos...@gm...>]

ok, my php errors level is on the maximum for to help me to understand and
report the problems.
but i have a fatal error when i try to save the selections as i showed:

[22-Jul-2014 16:40:46 UTC] PHP Fatal error:  Call to undefined function
getLayersByGroupOrLayerName() in
/var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
on line 461

and basicaly i can't get intersections (and i have no php errors about it).

Thank you very much Armin Burger
Congratulations for your great work!!!



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025559.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] pmapper4: new plugins and options

[Armin B. <arm...@gm...>]

First of all I would set the PHP error reporting to the value as 
described in the Wiki for the quick installation part, to avoid all pure 
notifications that just blow up your error log. What remains afterwards 
should be checked again.

/a

On 07/22/2014 06:51 PM, jose mvm wrote:
> Hi Thomas,
>
> after update the pmapper code, i found some questions and difficulties:
>
> - when pmapper start up php notice apeears (repeatedly):
> [22-Jul-2014 16:06:49 UTC] PHP Notice:  Undefined variable: dynamicClasses
> in /var/www/pmapper-4.3.2/incphp/layerview.php on line 218
>
> but no problem...
>
> - when i make a search the table of results appears closed by default... (no
> probem too)
>
> but my main problem, possibly, is that I don't understand the philosophy,
> the goal, the mechanism and operation of the "clientDynamicLayers". i don't
> understand the "examples" contained in plugin.
>
> and without this dependence plugin, the selectionManagement plugin doesn't
> work correctly. i can't save selections. when i search width searchtool
> these messages appears:
>
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: JSON_Results in
> /var/www/pmapper-4.3.2/incphp/xajax/x_info.php on line 40
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: numero in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: papel in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: embalagens in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: vidro in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: pilhao in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: oleao in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: propriet in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: freguesia in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: first_lug1 in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
> [22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: designacao in
> /var/www/pmapper-4.3.2/incphp/query/search.php on line 171
>
> when i try to save selection these messages appears:
>
> [22-Jul-2014 16:40:32 UTC] PHP Notice:  Undefined variable: content in
> /var/www/pmapper-4.3.2/plugins/selectionManagement/x_saveSelection.php on
> line 119
> [22-Jul-2014 16:40:46 UTC] PHP Notice:  Use of undefined constant
> msCurrentSelection - assumed 'msCurrentSelection' in
> /var/www/pmapper-4.3.2/plugins/clientdynamiclayers/x_clientDynamicLayers.php
> on line 46
> [22-Jul-2014 16:40:46 UTC] PHP Notice:  Use of undefined constant
> msSelection - assumed 'msSelection' in
> /var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
> on line 697
> [22-Jul-2014 16:40:46 UTC] PHP Fatal error:  Call to undefined function
> getLayersByGroupOrLayerName() in
> /var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
> on line 461
>
> in other words, my problem remains, i can't get use "intersect with actual
> selection" operator. when i try these messages appears:
>
> [22-Jul-2014 16:48:06 UTC] PHP Notice:  Undefined offset: 0 in
> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
> [22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined index: JSON_Results in
> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
> line 19
> [22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined variable: poly in
> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
> line 28
> [22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined property:
> QueryExtended::$querygroups in /var/www/pmapper-4.3.2/incphp/query/query.php
> on line 59
> [22-Jul-2014 16:48:13 UTC] PHP Notice:  Undefined offset: 0 in
> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
> [22-Jul-2014 16:48:22 UTC] PHP Notice:  Undefined offset: 0 in
> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
> [22-Jul-2014 16:48:31 UTC] PHP Notice:  Undefined variable: poly in
> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
> line 28
> [22-Jul-2014 16:48:31 UTC] PHP Notice:  Undefined property:
> QueryExtended::$querygroups in /var/www/pmapper-4.3.2/incphp/query/query.php
> on line 59
> [22-Jul-2014 16:48:32 UTC] PHP Notice:  Undefined offset: 1 in
> /var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 433
> [22-Jul-2014 16:48:32 UTC] PHP Notice:  Trying to get property of non-object
> in /var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 433
> [22-Jul-2014 16:48:32 UTC] PHP Notice:  Undefined offset: 0 in
> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
>
> Thanks in advence
> Best regards
>
>
>
> --
> View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025556.html
> Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>

[pmapper-users] search one layer

[Bogumił S. <sz...@ku...>]

Hello,
Is it possible to get one default search field turned on in the moment 
of starting of application window?
I have only one layer to search and I would like to avoid every time 
selecting layer to search.


all the best

Bogumił

Re: [pmapper-users] pmapper4: new plugins and options

[jose m. <jos...@gm...>]

Hi Thomas,

after update the pmapper code, i found some questions and difficulties:

- when pmapper start up php notice apeears (repeatedly):
[22-Jul-2014 16:06:49 UTC] PHP Notice:  Undefined variable: dynamicClasses
in /var/www/pmapper-4.3.2/incphp/layerview.php on line 218

but no problem...

- when i make a search the table of results appears closed by default... (no
probem too)

but my main problem, possibly, is that I don't understand the philosophy,
the goal, the mechanism and operation of the "clientDynamicLayers". i don't
understand the "examples" contained in plugin.

and without this dependence plugin, the selectionManagement plugin doesn't
work correctly. i can't save selections. when i search width searchtool
these messages appears:

[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: JSON_Results in
/var/www/pmapper-4.3.2/incphp/xajax/x_info.php on line 40
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: numero in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: papel in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: embalagens in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: vidro in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: pilhao in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: oleao in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: propriet in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: freguesia in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: first_lug1 in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171
[22-Jul-2014 16:37:27 UTC] PHP Notice:  Undefined index: designacao in
/var/www/pmapper-4.3.2/incphp/query/search.php on line 171

when i try to save selection these messages appears:

[22-Jul-2014 16:40:32 UTC] PHP Notice:  Undefined variable: content in
/var/www/pmapper-4.3.2/plugins/selectionManagement/x_saveSelection.php on
line 119
[22-Jul-2014 16:40:46 UTC] PHP Notice:  Use of undefined constant
msCurrentSelection - assumed 'msCurrentSelection' in
/var/www/pmapper-4.3.2/plugins/clientdynamiclayers/x_clientDynamicLayers.php
on line 46
[22-Jul-2014 16:40:46 UTC] PHP Notice:  Use of undefined constant
msSelection - assumed 'msSelection' in
/var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
on line 697
[22-Jul-2014 16:40:46 UTC] PHP Fatal error:  Call to undefined function
getLayersByGroupOrLayerName() in
/var/www/pmapper-4.3.2/plugins/clientdynamiclayers/clientDynamicLayers.php
on line 461

in other words, my problem remains, i can't get use "intersect with actual
selection" operator. when i try these messages appears:

[22-Jul-2014 16:48:06 UTC] PHP Notice:  Undefined offset: 0 in
/var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
[22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined index: JSON_Results in
/var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
line 19
[22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined variable: poly in
/var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
line 28
[22-Jul-2014 16:48:12 UTC] PHP Notice:  Undefined property:
QueryExtended::$querygroups in /var/www/pmapper-4.3.2/incphp/query/query.php
on line 59
[22-Jul-2014 16:48:13 UTC] PHP Notice:  Undefined offset: 0 in
/var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
[22-Jul-2014 16:48:22 UTC] PHP Notice:  Undefined offset: 0 in
/var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99
[22-Jul-2014 16:48:31 UTC] PHP Notice:  Undefined variable: poly in
/var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php on
line 28
[22-Jul-2014 16:48:31 UTC] PHP Notice:  Undefined property:
QueryExtended::$querygroups in /var/www/pmapper-4.3.2/incphp/query/query.php
on line 59
[22-Jul-2014 16:48:32 UTC] PHP Notice:  Undefined offset: 1 in
/var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 433
[22-Jul-2014 16:48:32 UTC] PHP Notice:  Trying to get property of non-object
in /var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 433
[22-Jul-2014 16:48:32 UTC] PHP Notice:  Undefined offset: 0 in
/var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 99

Thanks in advence
Best regards



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pmapper4-new-plugins-and-options-tp4025551p4025556.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] RES: Attribute search

[Thomas R. <tr...@si...>]

Hi,

My version doesn't works with groups, sorry...


Le 17/07/2014 21:38, Thomas RAFFIN a écrit :
> Hi,
>
> I think I've got this code.
>
> I will check it tomorrow.
>
> Le 17/07/2014 19:39, Juliano C. P. Agostinho a écrit :
>> Thank you.
>>
>> I will try implement one search to groups if I  have success I will send to
>> you.
>>
>> -----Mensagem original-----
>> De: Armin Burger [mailto:arm...@gm...]
>> Enviada em: quinta-feira, 17 de julho de 2014 14:16
>> Para: Juliano C. P. Agostinho; pma...@li... >>
>> "pma...@li..."
>> Assunto: Re: [pmapper-users] Attribute search
>>
>> Attribute searches just work on layers, not groups. So in your case you have
>> to decide which of the grouped layers to use for the search. In principal it
>> would be possible to use the same mechanism as for identify (collecting
>> results for layers of a group) but that was never implemented.
>>
>> /a
>>
>> On 07/17/2014 06:37 PM, Juliano C. P. Agostinho wrote:
>>> Hi,
>>>
>>>
>>>
>>> I have one problem, I have 2 SHAPEfiles (point and polygon) and I want
>>> search in both.
>>>
>>>
>>>
>>> Exemple:
>>>
>>> I want search Topdown's city in all SHP's (point and polygon) in same
>> time.
>>>
>>> Is there one way?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> MAPFILE:
>>>
>>>
>>>
>>>            LAYER
>>>
>>>                    NAME "City"
>>>
>>>                    GROUP CITY
>>>
>>>                    MAXSCALE 7000
>>>
>>>                    TYPE POLYGON
>>>
>>>                    STATUS OFF
>>>
>>>                    DATA City_polig.shp"
>>>
>>>                    CLASS
>>>
>>>                            NAME " "
>>>
>>>                            STYLE
>>>
>>>                               OUTLINECOLOR 128 128 128
>>>
>>>                               LINECAP butt
>>>
>>>                               WIDTH 2
>>>
>>>                               PATTERN 5 5 END
>>>
>>>                            END
>>>
>>>                            TEMPLATE void
>>>
>>>                    END
>>>
>>>                    METADATA
>>>
>>>                         "DESCRIPTION" "city"
>>>
>>>                         "RESULT_FIELDS" "NAME"
>>>
>>>                         "RESULT_HEADERS" "Name"
>>>
>>>                         "LAYER_ENCODING" "ISO-8859-1"
>>>
>>>                         "ows_title"      "City"
>>>
>>>                    END
>>>
>>>            END
>>>
>>>
>>>
>>>            LAYER
>>>
>>>                    NAME "City"
>>>
>>>                    GROUP CITY
>>>
>>>                    MAXSCALE 7000
>>>
>>>                    TYPE POINT
>>>
>>>                    STATUS OFF
>>>
>>>                    DATA "City_point.shp"
>>>
>>>                    CLASS
>>>
>>>                            NAME " "
>>>
>>>                            STYLE
>>>
>>>                               SYMBOL "circle1"
>>>
>>>                               COLOR 128 128 128
>>>
>>>                               SIZE 10
>>>
>>>                            END
>>>
>>>                            TEMPLATE void
>>>
>>>                    END
>>>
>>>                    METADATA
>>>
>>>                         "DESCRIPTION" "city"
>>>
>>>                         "RESULT_FIELDS" "NAME"
>>>
>>>                         "RESULT_HEADERS" "Name"
>>>
>>>                         "LAYER_ENCODING" "ISO-8859-1"
>>>
>>>                         "ows_title"      "City"
>>>
>>>                    END
>>>
>>>            END
>>>
>>>
>>>
>>>
>>>
>>> <searchitem name="City" description="City">
>>>
>>>            <layer type="shape" name="City">
>>>
>>>                <field type="s" name="NAME" description="Name:"
>> wildcard="0">
>>>                </field>
>>>
>>>            </layer>
>>>
>>>      </searchitem>
>>>
>>>
>>>
>>>
>> ----------------------------------------------------------------------------
>> --
>>> Want fast and easy access to all the code in your enterprise? Index and
>>> search up to 200,000 lines of code with a free copy of Black Duck
>>> Code Sight - the same software that powers the world's largest code
>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>> http://p.sf.net/sfu/bds
>>> _______________________________________________
>>> pmapper-users mailing list
>>> pma...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>
>>

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

Re: [pmapper-users] pmapper4: new plugins and options

[Raffaele M. <raf...@gm...>]

2014-07-21 19:35 GMT+02:00 Thomas RAFFIN <tr...@si...>:

> Hi all,
>
> There are few new plugins and options available in pampper4. I will
> quickly described the changes here, but for more information plugins are
> documented in pmapper wiki (here:
> http://svn.pmapper.net/trac/wiki/AvailablePlugins ) and in their own
> README file.
>
> - Selection Management (enhancement / big rewritten):
>      - now you can save, restore, merge, etc... your selections. See
>
> http://svn.pmapper.net/trac/attachment/wiki/PluginsQuery/plugin_selMan_selections.jpg
> for a quick view
>      - operators are available on pre-defined search, graphical queries,
> query editor (something like a small SQL editor), ...
>      - ...
>
> - Export Layer (new): export whole layer data in shape file (without
> selection on the contrary to export plugin)
>
> - Export Points (new): export some user-defined points in a text file
>
> - Size up and Down Object (enhancement): increase size or objects, and
> can now change label scale limit
>
> - Menu Dlg (new): add additional tools concerning selection in a menu
> instead of at the end of selection window
>
> - Switch Layers (enhancement): checked / unchecked all layer of 1
> category. Now you can see category state even if it is closed
>
> - TOC Action Menu (new): just add a button near layers to open its
> contextual menu
>
> - Unit And Projection (new): display informations concerning unit and
> projection near coordinates
>
> - Transparency2 (enhancement): transparency / opacity can be set to
> initial value
>
> - corrections in Query Editor (something like a small SQL editor),
> Drawing, Export
>
> New options (see here: http://svn.pmapper.net/trac/wiki/XmlFileSettings
> for details):
> - compact result window --> hideResultLimit
> - query on not visible groups at current scale --> queryOnInvisibleGroup
>
> If no serious bugs are reported soon, a new pmapper 4.4 will soon be
> available.
>
> Bye
>
> Thomas
>

​Great!​

Re: [pmapper-users] intersect with selection management plugin

[jose m. <jos...@gm...>]

Hi Thomas,

Thank you very much for your great work!!!
I'll try it as soon as possible.

Well, with all this effort, pmapper will not die early :-)



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/intersect-with-selection-management-plugin-tp4025534p4025553.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.

Re: [pmapper-users] intersect with selection management plugin

[Thomas R. <tr...@si...>]

Hi,

Now search operators are available for pre-definied search.

Le 17/07/2014 13:30, Thomas RAFFIN a écrit :
> I send your mail to the mailing-list after a small "cleaning"...
>
> Concerning "intersect with current selection" it is working well on my
> local pmapper copy? I'm trying to commit all local modification in
> pmapper4 trunk version.
>
> For search operators, I'm looking what is missing in pmapper4 trunk
> version to allow it...
>
> bye
>
> Thomas
>
> Le 16/07/2014 18:13, jose macau a écrit :
>> my initial post ("This post has NOT been accepted by the mailing list
>> yet."), i don't know know why, i don't now if you can see it...
>>
>> title: intersect with selection management plugin
>>
>> post:
>>
>> hi,
>>
>> i'm trying to use "intersect with current selection" (through the
>> graphical queries plugin or query editor plugin) but i can´t get any
>> results.
>>
>> i have no php errors, only php notices:
>>
>> first selection:
>>
>> [15-Jul-2014 10:38:06 UTC] PHP Notice:  Undefined offset: 0 in
>> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 96
>> [15-Jul-2014 10:38:15 UTC] PHP Notice:  Undefined index: JSON_Results
>> in
>> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php
>> on line 19
>> [15-Jul-2014 10:38:15 UTC] PHP Notice:  Undefined variable: poly in
>> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php
>> on line 28
>> [15-Jul-2014 10:38:16 UTC] PHP Notice:  Undefined offset: 0 in
>> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 96
>>
>> intersect with current selection:
>>
>> [15-Jul-2014 10:40:25 UTC] PHP Notice:  Undefined variable: poly in
>> /var/www/pmapper-4.3.2/plugins/graphicalqueries/x_graphicalqueries.php
>> on line 28
>> [15-Jul-2014 10:40:25 UTC] PHP Notice:  Undefined offset: 1 in
>> /var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 421
>> [15-Jul-2014 10:40:25 UTC] PHP Notice:  Trying to get property of
>> non-object in
>> /var/www/pmapper-4.3.2/plugins/common/selectTools.inc.php on line 421
>> [15-Jul-2014 10:40:26 UTC] PHP Notice:  Undefined offset: 0 in
>> /var/www/pmapper-4.3.2/incphp/xajax/x_select.php on line 96
>>
>> ================
>>
>> and another question:
>>
>> it´s possible to load the selection management plugin with search tool
>> plugin (like with the graphical queries plugin and query editor plugin)?
>>
>> ================
>>
>> thanks
>>
>> best regards,
>> José
>>
>>
>> 2014-07-16 16:26 GMT+01:00 jose macau <jos...@gm...
>> <mailto:jos...@gm...>>:
>>
>>      Ok, magnificent!!!
>>      Thank you very much Thomas.
>>
>>      But the my initial question was intersect with selection
>>      management plugin.
>>      I get the "replace selection", the "add to current selection",
>>      the"exclude from the current selection" but not the "intersect
>>      with current selection" operation.
>>
>>
>>      2014-07-16 16:08 GMT+01:00 Thomas RAFFIN <tr...@si...
>>      <mailto:tr...@si...>>:
>>
>>          Found!
>>
>>          In plugins/queryeditor/queryeditor.js, function
>>          "setLayerName", near line 134, you should have (like here:
>>          http://svn.pmapper.net/trac/browser/trunk/pmapper/plugins/queryeditor/queryeditor.js):
>>
>>          var options = '<option value="#"></option>\n';
>>
>>          with a "#" sign. In your code it is a "%".
>>
>>
> 	
> 	
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

[pmapper-users] pmapper4: new plugins and options

[Thomas R. <tr...@si...>]

Hi all,

There are few new plugins and options available in pampper4. I will 
quickly described the changes here, but for more information plugins are 
documented in pmapper wiki (here: 
http://svn.pmapper.net/trac/wiki/AvailablePlugins ) and in their own  
README file.

- Selection Management (enhancement / big rewritten):
     - now you can save, restore, merge, etc... your selections. See 
http://svn.pmapper.net/trac/attachment/wiki/PluginsQuery/plugin_selMan_selections.jpg 
for a quick view
     - operators are available on pre-defined search, graphical queries, 
query editor (something like a small SQL editor), ...
     - ...

- Export Layer (new): export whole layer data in shape file (without 
selection on the contrary to export plugin)

- Export Points (new): export some user-defined points in a text file

- Size up and Down Object (enhancement): increase size or objects, and 
can now change label scale limit

- Menu Dlg (new): add additional tools concerning selection in a menu 
instead of at the end of selection window

- Switch Layers (enhancement): checked / unchecked all layer of 1 
category. Now you can see category state even if it is closed

- TOC Action Menu (new): just add a button near layers to open its 
contextual menu

- Unit And Projection (new): display informations concerning unit and 
projection near coordinates

- Transparency2 (enhancement): transparency / opacity can be set to 
initial value

- corrections in Query Editor (something like a small SQL editor), 
Drawing, Export

New options (see here: http://svn.pmapper.net/trac/wiki/XmlFileSettings 
for details):
- compact result window --> hideResultLimit
- query on not visible groups at current scale --> queryOnInvisibleGroup

If no serious bugs are reported soon, a new pmapper 4.4 will soon be 
available.

Bye

Thomas


	
	

Re: [pmapper-users] RES: Attribute search

[Thomas R. <tr...@si...>]

Hi,

I think I've got this code.

I will check it tomorrow.

Le 17/07/2014 19:39, Juliano C. P. Agostinho a écrit :
> Thank you.
>
> I will try implement one search to groups if I  have success I will send to
> you.
>
> -----Mensagem original-----
> De: Armin Burger [mailto:arm...@gm...]
> Enviada em: quinta-feira, 17 de julho de 2014 14:16
> Para: Juliano C. P. Agostinho; pma...@li... >>
> "pma...@li..."
> Assunto: Re: [pmapper-users] Attribute search
>
> Attribute searches just work on layers, not groups. So in your case you have
> to decide which of the grouped layers to use for the search. In principal it
> would be possible to use the same mechanism as for identify (collecting
> results for layers of a group) but that was never implemented.
>
> /a
>
> On 07/17/2014 06:37 PM, Juliano C. P. Agostinho wrote:
>> Hi,
>>
>>
>>
>> I have one problem, I have 2 SHAPEfiles (point and polygon) and I want
>> search in both.
>>
>>
>>
>> Exemple:
>>
>> I want search Topdown's city in all SHP's (point and polygon) in same
> time.
>>
>>
>> Is there one way?
>>
>>
>>
>>
>>
>>
>>
>> MAPFILE:
>>
>>
>>
>>           LAYER
>>
>>                   NAME "City"
>>
>>                   GROUP CITY
>>
>>                   MAXSCALE 7000
>>
>>                   TYPE POLYGON
>>
>>                   STATUS OFF
>>
>>                   DATA City_polig.shp"
>>
>>                   CLASS
>>
>>                           NAME " "
>>
>>                           STYLE
>>
>>                              OUTLINECOLOR 128 128 128
>>
>>                              LINECAP butt
>>
>>                              WIDTH 2
>>
>>                              PATTERN 5 5 END
>>
>>                           END
>>
>>                           TEMPLATE void
>>
>>                   END
>>
>>                   METADATA
>>
>>                        "DESCRIPTION" "city"
>>
>>                        "RESULT_FIELDS" "NAME"
>>
>>                        "RESULT_HEADERS" "Name"
>>
>>                        "LAYER_ENCODING" "ISO-8859-1"
>>
>>                        "ows_title"      "City"
>>
>>                   END
>>
>>           END
>>
>>
>>
>>           LAYER
>>
>>                   NAME "City"
>>
>>                   GROUP CITY
>>
>>                   MAXSCALE 7000
>>
>>                   TYPE POINT
>>
>>                   STATUS OFF
>>
>>                   DATA "City_point.shp"
>>
>>                   CLASS
>>
>>                           NAME " "
>>
>>                           STYLE
>>
>>                              SYMBOL "circle1"
>>
>>                              COLOR 128 128 128
>>
>>                              SIZE 10
>>
>>                           END
>>
>>                           TEMPLATE void
>>
>>                   END
>>
>>                   METADATA
>>
>>                        "DESCRIPTION" "city"
>>
>>                        "RESULT_FIELDS" "NAME"
>>
>>                        "RESULT_HEADERS" "Name"
>>
>>                        "LAYER_ENCODING" "ISO-8859-1"
>>
>>                        "ows_title"      "City"
>>
>>                   END
>>
>>           END
>>
>>
>>
>>
>>
>> <searchitem name="City" description="City">
>>
>>           <layer type="shape" name="City">
>>
>>               <field type="s" name="NAME" description="Name:"
> wildcard="0">
>>               </field>
>>
>>           </layer>
>>
>>     </searchitem>
>>
>>
>>
>>
> ----------------------------------------------------------------------------
> --
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> pmapper-users mailing list
>> pma...@li...
>> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>
>

-- 


Thomas RAFFIN
Chef de Projet Internet
tr...@si... <mailto:tr...@si...> 	Sirap <http://sirap.fr> 	Tel 
: 04 75 72 84 10
Fax : 04 75 70 07 98
Rue Paul Louis Héroult - BP 253
26106 Romans cedex

[pmapper-users] RES: Attribute search

[Juliano C. P. A. <jul...@ho...>]

Thank you.

I will try implement one search to groups if I  have success I will send to
you.

-----Mensagem original-----
De: Armin Burger [mailto:arm...@gm...] 
Enviada em: quinta-feira, 17 de julho de 2014 14:16
Para: Juliano C. P. Agostinho; pma...@li... >>
"pma...@li..."
Assunto: Re: [pmapper-users] Attribute search

Attribute searches just work on layers, not groups. So in your case you have
to decide which of the grouped layers to use for the search. In principal it
would be possible to use the same mechanism as for identify (collecting
results for layers of a group) but that was never implemented.

/a

On 07/17/2014 06:37 PM, Juliano C. P. Agostinho wrote:
> Hi,
>
>
>
> I have one problem, I have 2 SHAPEfiles (point and polygon) and I want
> search in both.
>
>
>
> Exemple:
>
> I want search Topdown's city in all SHP's (point and polygon) in same
time.
>
>
>
> Is there one way?
>
>
>
>
>
>
>
> MAPFILE:
>
>
>
>          LAYER
>
>                  NAME "City"
>
>                  GROUP CITY
>
>                  MAXSCALE 7000
>
>                  TYPE POLYGON
>
>                  STATUS OFF
>
>                  DATA City_polig.shp"
>
>                  CLASS
>
>                          NAME " "
>
>                          STYLE
>
>                             OUTLINECOLOR 128 128 128
>
>                             LINECAP butt
>
>                             WIDTH 2
>
>                             PATTERN 5 5 END
>
>                          END
>
>                          TEMPLATE void
>
>                  END
>
>                  METADATA
>
>                       "DESCRIPTION" "city"
>
>                       "RESULT_FIELDS" "NAME"
>
>                       "RESULT_HEADERS" "Name"
>
>                       "LAYER_ENCODING" "ISO-8859-1"
>
>                       "ows_title"      "City"
>
>                  END
>
>          END
>
>
>
>          LAYER
>
>                  NAME "City"
>
>                  GROUP CITY
>
>                  MAXSCALE 7000
>
>                  TYPE POINT
>
>                  STATUS OFF
>
>                  DATA "City_point.shp"
>
>                  CLASS
>
>                          NAME " "
>
>                          STYLE
>
>                             SYMBOL "circle1"
>
>                             COLOR 128 128 128
>
>                             SIZE 10
>
>                          END
>
>                          TEMPLATE void
>
>                  END
>
>                  METADATA
>
>                       "DESCRIPTION" "city"
>
>                       "RESULT_FIELDS" "NAME"
>
>                       "RESULT_HEADERS" "Name"
>
>                       "LAYER_ENCODING" "ISO-8859-1"
>
>                       "ows_title"      "City"
>
>                  END
>
>          END
>
>
>
>
>
> <searchitem name="City" description="City">
>
>          <layer type="shape" name="City">
>
>              <field type="s" name="NAME" description="Name:"
wildcard="0">
>
>              </field>
>
>          </layer>
>
>    </searchitem>
>
>
>
>
----------------------------------------------------------------------------
--
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>

Re: [pmapper-users] Attribute search

[Armin B. <arm...@gm...>]

Attribute searches just work on layers, not groups. So in your case you 
have to decide which of the grouped layers to use for the search. In 
principal it would be possible to use the same mechanism as for identify 
(collecting results for layers of a group) but that was never implemented.

/a

On 07/17/2014 06:37 PM, Juliano C. P. Agostinho wrote:
> Hi,
>
>
>
> I have one problem, I have 2 SHAPEfiles (point and polygon) and I want
> search in both.
>
>
>
> Exemple:
>
> I want search Topdown's city in all SHP's (point and polygon) in same time.
>
>
>
> Is there one way?
>
>
>
>
>
>
>
> MAPFILE:
>
>
>
>          LAYER
>
>                  NAME "City"
>
>                  GROUP CITY
>
>                  MAXSCALE 7000
>
>                  TYPE POLYGON
>
>                  STATUS OFF
>
>                  DATA City_polig.shp"
>
>                  CLASS
>
>                          NAME " "
>
>                          STYLE
>
>                             OUTLINECOLOR 128 128 128
>
>                             LINECAP butt
>
>                             WIDTH 2
>
>                             PATTERN 5 5 END
>
>                          END
>
>                          TEMPLATE void
>
>                  END
>
>                  METADATA
>
>                       "DESCRIPTION" "city"
>
>                       "RESULT_FIELDS" "NAME"
>
>                       "RESULT_HEADERS" "Name"
>
>                       "LAYER_ENCODING" "ISO-8859-1"
>
>                       "ows_title"      "City"
>
>                  END
>
>          END
>
>
>
>          LAYER
>
>                  NAME "City"
>
>                  GROUP CITY
>
>                  MAXSCALE 7000
>
>                  TYPE POINT
>
>                  STATUS OFF
>
>                  DATA "City_point.shp"
>
>                  CLASS
>
>                          NAME " "
>
>                          STYLE
>
>                             SYMBOL "circle1"
>
>                             COLOR 128 128 128
>
>                             SIZE 10
>
>                          END
>
>                          TEMPLATE void
>
>                  END
>
>                  METADATA
>
>                       "DESCRIPTION" "city"
>
>                       "RESULT_FIELDS" "NAME"
>
>                       "RESULT_HEADERS" "Name"
>
>                       "LAYER_ENCODING" "ISO-8859-1"
>
>                       "ows_title"      "City"
>
>                  END
>
>          END
>
>
>
>
>
> <searchitem name="City" description="City">
>
>          <layer type="shape" name="City">
>
>              <field type="s" name="NAME" description="Name:"  wildcard="0">
>
>              </field>
>
>          </layer>
>
>    </searchitem>
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> pmapper-users mailing list
> pma...@li...
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>

[pmapper-users] Attribute search

[Juliano C. P. A. <jul...@ho...>]

Hi,

 

I have one problem, I have 2 SHAPEfiles (point and polygon) and I want
search in both. 

 

Exemple:

I want search Topdown's city in all SHP's (point and polygon) in same time.

 

Is there one way?

 

 

 

MAPFILE: 

 

        LAYER

                NAME "City"

                GROUP CITY

                MAXSCALE 7000

                TYPE POLYGON

                STATUS OFF

                DATA City_polig.shp"

                CLASS

                        NAME " "

                        STYLE

                           OUTLINECOLOR 128 128 128

                           LINECAP butt

                           WIDTH 2

                           PATTERN 5 5 END

                        END

                        TEMPLATE void

                END

                METADATA

                     "DESCRIPTION" "city"

                     "RESULT_FIELDS" "NAME"

                     "RESULT_HEADERS" "Name"

                     "LAYER_ENCODING" "ISO-8859-1"

                     "ows_title"      "City"

                END

        END

 

        LAYER

                NAME "City"

                GROUP CITY

                MAXSCALE 7000

                TYPE POINT

                STATUS OFF

                DATA "City_point.shp"

                CLASS

                        NAME " "

                        STYLE

                           SYMBOL "circle1"

                           COLOR 128 128 128

                           SIZE 10

                        END

                        TEMPLATE void

                END

                METADATA

                     "DESCRIPTION" "city"

                     "RESULT_FIELDS" "NAME"

                     "RESULT_HEADERS" "Name"

                     "LAYER_ENCODING" "ISO-8859-1"

                     "ows_title"      "City"

                END

        END

 

 

<searchitem name="City" description="City">

        <layer type="shape" name="City">

            <field type="s" name="NAME" description="Name:"  wildcard="0">

            </field>

        </layer>

  </searchitem>

 

Re: [pmapper-users] intersect with selection management plugin

[jose m. <jos...@gm...>]

my pmapper project runs on linux but for the last experience i used a new
installation with pmapper-4.3.2-MS4W.



--
View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/intersect-with-selection-management-plugin-tp4025534p4025546.html
Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com.