[MIP] Multi-view Identify with external data and media rendering

[stefano.bovio]

Hi all,

I would like to keep the mailing list informed about a new proposed MIP for improving the Identify feature. Today each layer can expose only a single featureInfo, which limits how much and how varied the information shown on click can be. The idea is to let a layer configure multiple Identify views, rendered as tabs, so the same click can present different slices of information side by side.

On top of this it adds a view type that drills into a separate WFS source via a CQL template built from the clicked feature, and per-attribute media rendering (images, video, audio, panoramas, PDFs, links, iframes). The same attributes editor and renderers are reused by the existing PROPERTIES view.

Everything stays backwards compatible: existing saved maps keep working, since a legacy single featureInfo is normalized into a one-view configuration.

The full proposal, scope and acceptance criteria are in the MIP issue: https://github.com/geosolutions-it/MapStore2/issues/12594

Feedback are welcome.

Thanks,
Stefano

[Simon Nitz]

Hi Stefano

Very interesting! 🙂

Our workaround for this type of functionality uses GeoServer grouped layers and custom FreeMarker templates (content.ftl) that use html etc. to provide an accordion interface for the different layer information required including links built on the fly...

Cheers

Simon

Simon Nitz | Geospatial Lead P: +64 349 3052 | M: +64 www.whanganui.govt.nz 101 Guyton Street | Whanganui 4500

Please consider the environment before printing this email CAUTION: This correspondence is confidential and intended for the named recipient(s) only. If you are not the named recipient and receive this correspondence in error, you must not copy, distribute or take action in reliance on it and should delete it from your system and notify the sender immediately. Views expressed are those of the author and do not necessarily represent those of the organisation.

---

From: mapstore-...@googlegroups.com <mapstore-...@googlegroups.com> on behalf of stefano.bovio <stefan...@geosolutionsgroup.com>
Sent: Wednesday, July 15, 2026 2:04 AM
To: mapstore-developers <mapstore-...@googlegroups.com>
Subject: [mapstore-developers] [MIP] Multi-view Identify with external data and media rendering

 

--
You received this message because you are subscribed to the Google Groups "mapstore-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapstore-develo...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/mapstore-developers/5882d276-d157-417d-8da1-794a06df1c58n%40googlegroups.com.

[thomas hallundbæk]

Hi Stefano

Very interesting. Looks like good improvements.

In regards to https://github.com/geosolutions-it/MapStore2/issues/12596

Wouldnt it make sense to use the coupled WFS (layer.search)?

im wondering if there is some overlap with this issue

https://github.com/geosolutions-it/MapStore2/issues/12573

What do you think?

best regards

Thomas

[Stefano Bovio]

Hi Thomas,

In regards to https://github.com/geosolutions-it/MapStore2/issues/12596
Wouldnt it make sense to use the coupled WFS (layer.search)?

im wondering if there is some overlap with this issue
https://github.com/geosolutions-it/MapStore2/issues/12573
What do you think?

The new identify structure allows multiple views to be displayed as a tab,

so a user could technically connect to multiple WFS services, even with a geometric or attribute structure unrelated to the source WMS layer (e.g. an attachment table).

Instead the internal WFS search drives tools like the attribute table so it generally has a structure similar to the source WMS layer

(By default, MapStore determines the relationship between the WMS and WFS layer by using a DescribeLayer request when adding the layer from the catalog).

For this reason I think the two properties have different roles and the editor mentioned in issue https://github.com/geosolutions-it/MapStore2/issues/12573 can coexist with the new EXTERNAL DATA format. 

As for the proposed implementation EXTERNAL DATA allows freely including the WFS information

so it's possible to enter the same information as the WFS layer.search property and use them (including also a CQL expression to properly filter the target layer).

In the future we may think a way to quickly fill the WFS properties inside the EXTERNAL_DATA editor with the associated layer.search properties,

but it will require a separate issue and investigation to understand the feasibility.

Hope this answers your questions,
Thanks,

Best Regards,

Stefano 

To view this discussion, visit https://groups.google.com/d/msgid/mapstore-developers/c1d5835d-9479-4d4a-841d-e6017a162681n%40googlegroups.com.

--

Regards,
Stefano Bovio
==
GeoServer Professional Services from the experts!
Visit https://www.geosolutionsgroup.com/enterprise-support-services for more information.
==
Stefano Bovio
MapStore Technical Lead
Cesium Certified Developer

GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
https://www.geosolutionsgroup.com/
https://www.linkedin.com/company/geosolutionsgroup/
-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza
inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui
conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è
giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque
grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from disclosure. We remind
that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of
this e-mail or the information herein by anyone other than the intended recipient is prohibited. If
you have received this email by mistake, please notify us immediately by telephone or e-mail.

[Stefano Bovio]

Hi Simon,

Our workaround for this type of functionality uses GeoServer grouped layers and custom FreeMarker templates (content.ftl) that use html etc. to provide an accordion interface for the different layer information required including links built on the fly...

Thanks for sharing your approach!

Interesting usage of the FreeMarker template (I see it also includes downloads for external reports)

Thanks again,
Best Regards,

Stefano
 

To view this discussion, visit https://groups.google.com/d/msgid/mapstore-developers/SY8P300MB095087E5BA53D0EB14118A1DD1F92%40SY8P300MB0950.AUSP300.PROD.OUTLOOK.COM.