Opened 16 years ago

Last modified 5 years ago

#618 new enhancement

Theming stylisation order isn't respected in a layer

Reported by: jnel Owned by:
Priority: medium Milestone: 4.0
Component: Rendering Service Version:
Severity: major Keywords:
Cc: External ID:


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.

Attachments (1)

minor+raods+overlaping+main+roads.jpg (29.1 KB ) - added by zspitzer 16 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by zspitzer, 16 years ago

Summary: Display order in thematicsAdd ability to specify order by in layer definitions for thematic styling
Type: defectenhancement

I think this is a really good idea

FDO already supports ordering,

It would require an additional parameter in LayerDefinition

comment:2 by zspitzer, 16 years ago

Component: GeneralRendering Service
Priority: lowmedium
Severity: minormajor

This really affects what is possible with mapguide and the workaround is painful

comment:3 by zspitzer, 16 years ago

Summary: Add ability to specify order by in layer definitions for thematic stylingTheming stylisation order isn't respected in a layer

comment:4 by tomfukushima, 16 years ago

Check out the Rendering Pass concept in RFC 29. Is this what you are asking for?

comment:5 by zspitzer, 16 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 jbirch, 15 years ago

Version: 2.0.2

I think there was some mailing list discussion of this... should this ticket be closed?

comment:7 by jng, 12 years ago

Milestone: 2.5

comment:8 by jng, 11 years ago

Milestone: 2.52.6

comment:9 by jng, 6 years ago

Milestone: 3.03.3

Ticket retargeted after milestone closed

comment:10 by jng, 5 years ago

Milestone: 3.34.0

Milestone renamed

Note: See TracTickets for help on using tickets.