Opened 15 years ago
Last modified 4 years ago
#618 new enhancement
Theming stylisation order isn't respected in a layer
|Reported by:||jnel||Owned by:|
At the moment you can set the display order for a layer but not within a layer e.g. a thematic.
Let's say there is a set of 20 busroutes, each indicated by different widths and colours. You can move the order in the legend up and down, but not the order of data display. The data is displayed in the order it comes out of the datasource, and you get random results. A thick line may overlay a thin line where there are shared busroutes. This means you have to set up 20 layers to get the desired results, cluttering up the user interface, and slowing down the system by doing 20 queries instead of 1 (significant when you have 200+ layers already)
Being able to manipulate the order of data display witin a thematic would be very powerful.
Change History (11)
comment:1 by , 15 years ago
|Summary:||Display order in thematics → Add ability to specify order by in layer definitions for thematic styling|
|Type:||defect → enhancement|
by , 14 years ago
comment:2 by , 14 years ago
|Component:||General → Rendering Service|
|Priority:||low → medium|
|Severity:||minor → major|
|Version:||2.0.1 → 2.0.2|
This really affects what is possible with mapguide and the workaround is painful
comment:3 by , 14 years ago
|Summary:||Add ability to specify order by in layer definitions for thematic styling → Theming stylisation order isn't respected in a layer|
comment:4 by , 14 years ago
Check out the Rendering Pass concept in RFC 29. Is this what you are asking for?
comment:5 by , 14 years ago
RFC 29 helps, but it becomes complex rather quickly.
Rather than resorting to manually editing the XML, ideally the theming order defined in studio should be respected, if not why is it there?
here is a test case purely authored in studio
comment:6 by , 13 years ago
I think there was some mailing list discussion of this... should this ticket be closed?
comment:7 by , 10 years ago
comment:8 by , 10 years ago
|Milestone:||2.5 → 2.6|
comment:9 by , 5 years ago
|Milestone:||3.0 → 3.3|
Ticket retargeted after milestone closed
comment:10 by , 4 years ago
|Milestone:||3.3 → 4.0|
I think this is a really good idea
FDO already supports ordering, http://fdo.osgeo.org/files/fdo/docs/FDO_API/df/d50/class_fdo_i_base_select.htm
It would require an additional parameter in LayerDefinition