#1817 closed defect (invalid)
filter problem with Maestro
Reported by: | captainst | Owned by: | jng |
---|---|---|---|
Priority: | medium | Milestone: | Maestro-4.0 |
Component: | Maestro | Version: | 2.2.0 |
Severity: | trivial | Keywords: | Filter Layer Style |
Cc: | External ID: |
Description
Thank you again Jack!
I found out another strange phenomenon with Maestro, and I think of creating a new ticket with it.
If I have understood correctly, I can add the "filter" in two places in Maestro:
1st: add to "Filter" edit box in "Layer Settings" 2nd: add with the Rules created with the ranges in "Layer Styles"
I added in "Layer Styles" 3 rules, to show only the data with type "motorway", "motorway_link", "trunk", "primary", "primary_link". These are from OSM data. (shown in Fig1 attached).
When I created a map with this layer and show in the browser, it took almost 40sec to show all. (shown in Fig2).
However, if I add these rules to "Filter" edit box in "Layer Settings" (shown in Fig3), it took only 11sec to show all.
So my impression is that the "filter" settings inside Layer Styles as shown in Fig1 does not work. Only the value in "Filter" edit box in "Layer Settings" works.
Should it be a bug ?
Attachments (3)
Change History (5)
by , 13 years ago
by , 13 years ago
by , 13 years ago
comment:1 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Exactly as you said.
I created a separate layer for each "type" of road, and, by filtering on type, mapguide significantly improved the loading time.
Thank you again.
The Layer Filter determines the whole set of features from this layer that will be rendered out. The filter specified in each rule is what each feature in this set must satisfy in order to be rendered out in the style specified by that rule.
The filters in each layer rule do not actually do any filtering per se. They just say what criteria a feature must satisfy in order to be rendered out with that rule's specified style.
This is why it still takes 40 seconds because MapGuide still has to read everything (because of no layer filter), but skips features that do not satisfy any of the filters in your 3 line rules.