Armin
I will stick to the custom.js and $extend() then, makes sense. Thanks for
the info.
Chris
On 28 August 2010 13:31, Armin Burger wrote:
> Chris
>
> the whole query output is determined by sort of template design. It allows
> for a certain amount of restructuring of the output by changing
Chris
the whole query output is determined by sort of template design. It
allows for a certain amount of restructuring of the output by changing
(or extending) the default template, but without modifying directly the
Javascript code that generates the HTML.
It's also possible to do all the par
Armin
Due to dabbling in not my usual code I am scratching my head to know what
syntax to use to embed numResult session value in pm_cjs.js/pm.query.js as
an output. Going further than that I was already trying to add a new
session variable in squery.php (eg numResult2) beofre your last email, bu
On Wed, Aug 25, 2010 at 3:44 PM, Chris Jackson wrote:
So back to the query.php code,
> do you retrieve a count of matched features from the shapefile before
> looping through them or is it even possible?
>
You can check the returned JSON string using eg. Firebug and the
response for x_info.php.
Armin
Although I had been doing some JS error checking in firefox I have done most
of the selects in IE7 - as you hinted big mistake (unfortunately IE is still
used by ~50% share of the intended UK audience)! FF is about 20secs for
5000 features - hohum! I agree about how many results do you need
just an update: I made a quick test, using the normal highlight. This
is not really slowing down things. If I disable the result table
creation the map is rendered quite fast with the default highlight,
even when 6 or 7000 features are returned. The JSON string returned
however is close to 2 MB! So
If you want to try the highlight method with the 2 files I put in the
zip file, you need to limit the number of features to be returned for
the result table. Just try setting it to 100. The highlight using the
querymap will nevertheless highlight *all* found features. So I guess
it should make a di
Armin
Tried your code and timed the two selection techniques with a 5000 feature
limit querying a shapefile - both about 8.5 mins!!! - so no real performance
gain using the old code. Takes ~45sec with a 1000 feature limit and about
13 secs with a 500 feature limit (working from a low performance
Armin
Thanks for racking your brains on this, sounds promising and will give it a
go tomorrow.
Much appreciated.
Chris
On 24 August 2010 21:43, Armin Burger wrote:
> Chris
>
> something that came into my mind was the use of queryMap. I had not used
> it since eternities because it became obsole
Chris
something that came into my mind was the use of queryMap. I had not used
it since eternities because it became obsolete to me using the p.mapper
highlighting method. I made a quick test and it would need just a few
lines in query.php and map.php to change/add.
Note that this will only wo
Chris
the way the highlight works, is taking all shape features' ID's and
adding one by one to a temporary dynamic layer, using a Mapscript
function addFeature(). This is for sure not an efficient way but has no
problems for "normal" selections up to a few 100's. Having a result
table displaye
Hi all
One of the underlying datasets in my P.Mapper app is a model grid (many
thousand cells) in a shapefile. The data displays nice and quick when just
viewing, but if I allow the user to select say 5000 cells (using the select
by rectangle tool or even the seach tool) it is very (extremely) sl
12 matches
Mail list logo
