nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Provide one XSLT Template per Service for WMS GetFeatureInfo Customization

MarcelFrehner

WMS GetFeatureInfo responses can be customized by editing the default XSLT templates. However, this will affect all WMS services on the server. The ArcGIS documentation does therefore discourage users from putting service-specific logic into the templates and presents the XSLT_TEMPLATE parameter as a client-side alternative.

In my opinion, separate XSLT templates for each service would add flexibilty while style control remains with the service author.

Use case:
A service author might use a service-specific XSLT template to convert attribute values representing a URL to an HTML hyperlink. They could apply this transformation to field "URL" in the case of service "A" whereas they could apply the same transformation to field "RESOURCES" in the case of service "B".

Encuentra más publicaciones etiquetadas con

Status: Abrir

Comentarios

AntjeKügeler1

This would be very useful!

AntjeKügeler1

...however it would be good to have the choice of using either a default template or a service-specific XSLT template, so the admin isn't forced to repeat the same changes in each template if no service-specific changes are needed.

GerdArns-Krogmann

Alternativly the concept of HTML-Popup configuration in ArcMap could be used to apply styling for feature info output of each layer. As far as I know this method will only work for ESRI-Feature Services but not for OGC-WMS.

Únete a la Conversación

Inicia sesión para publicar, seguir contenido y más. ¿Nuevo aquí? Regístrate gratis.