Hexagon Geospatial
MENU

WebGIS

Need a push in the right direction when configuring WebMap, Portal or SDI services? Looking for hints and tips, or just looking for Ideas and information? The WebGIS discussion board is where you start those discussions, connect and share information.
Showing results for 
Search instead for 
Do you mean 
Reply
Occasional Contributor
Posts: 10
Registered: ‎09-28-2017

Polygons label layers

Polygons label layers take a long time to load, it is a dynamically generated layer on a layer of polygons of cadastral parcels. Is there a way to speed it up?

Technical Evangelist
Posts: 1,119
Registered: ‎09-11-2015

Re: Polygons label layers

Hi Sergio,

 

  • What service is used and, if applicable, which format?
  • Is Geospatial Portal (or Publisher) used for the display?

Thanks,

Jan

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Occasional Contributor
Posts: 10
Registered: ‎09-28-2017

Re: Polygons label layers

We use sql server 2016 and WebMap Publisher Portal
Technical Evangelist
Posts: 1,119
Registered: ‎09-11-2015

Re: Polygons label layers

Ok, so I assume WMPS (WebMap Publisher Service) is used to provide the data.

  • How many features does the related legend entry in GeoMedia have?
  • Do you use SVG or PNG/JPEG format?
  • Is the weak performance seen on the client (slow responsiveness) or rather it takes too long to display the vector layer at all (slow server)?
Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial

Staff
Posts: 294
Registered: ‎11-05-2015

Re: Polygons label layers

One thing worth remembering is that authoring the label placement rules in the Label Rule File so that they allow for greater flexibility of placing labels bogs performance down. The engine tries its best at displaying the maximum number of labels it can fit in the visible area according to the rules. If, for example, you allow for font downsizing, the engine first tries to place all labels with the original font size. Then, it determines the colliding labels and restarts the placement process with selectively applying a smaller font size to them. With multiple features to label and other options allowing more wiggle room for the engine, you can see this can quite intense pretty quick.

 

For dynamic labeling to work fast, it's best to limit the number of possibilities for the labeling engine to account for. Very important labels that decidedly should be in the output image, are best done using static labels (textpoint feature classes work the fastest). Using dynamic labeling for such labels is asking for trouble, performance-wise.

 

Maybe you'd like to share the LRF you use as well?

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.