GeoServer

Add ability to place a feature layer "on top"

Details

  • Type: Wish Wish
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: WMS
  • Labels:
    None
  • Number of attachments :
    0

Description

GeoServer (or the Geotool's renderer, I guess) paints labels after all features have been drawn. That means (as far as I can tell) there is no way to implement something like Google's push-pins, which appear on the map over everything, including labels. It would be wonderful if there were a way to do this (maybe a way to specify that a specific layer is "special" and should be rendered after everything else is done?). What do other's think?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brent Owens added a comment -

You would be able to pull this off with some client software such as Coimmunity MapBuilder. It will render features for you, and you can put them on top of other layers and labels.

But I do believe that geoserver renders each layer in order, no matter what labels have been rendered. So in effect you would get your pushpins if you made a second layer and had it render after the first layer.

Show
Brent Owens added a comment - You would be able to pull this off with some client software such as Coimmunity MapBuilder. It will render features for you, and you can put them on top of other layers and labels. But I do believe that geoserver renders each layer in order, no matter what labels have been rendered. So in effect you would get your pushpins if you made a second layer and had it render after the first layer.
Hide
Permalink
Chris Holmes added a comment -

Yeah, my thought is that push-pin stuff should actually be done client side. This is how google maps works as well, it's javascript produced on the client side. Or SVG (or ie's proprietary stuff) to do like the lines on top of stuff. So yeah, google's rendering is done client side, so I don't think we should be doing it server side.

Show
Chris Holmes added a comment - Yeah, my thought is that push-pin stuff should actually be done client side. This is how google maps works as well, it's javascript produced on the client side. Or SVG (or ie's proprietary stuff) to do like the lines on top of stuff. So yeah, google's rendering is done client side, so I don't think we should be doing it server side.
Hide
Permalink
Chris Holmes added a comment -

See: http://openlayers.org/dev/examples/wfs.html for an example of client side pushpins, created from WFS.

Show
Chris Holmes added a comment - See: http://openlayers.org/dev/examples/wfs.html for an example of client side pushpins, created from WFS.
Hide
Permalink
Michael Brasser added a comment -

Doing it client-side makes sense to me. Thanks for the suggestions and link!

Show
Michael Brasser added a comment - Doing it client-side makes sense to me. Thanks for the suggestions and link!
Hide
Permalink
Gabriel Roldan added a comment -

won't fix, agreed this has to be done client side

Show
Gabriel Roldan added a comment - won't fix, agreed this has to be done client side

People

  • Assignee:
    Gabriel Roldan
    Reporter:
    Michael Brasser
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: