idea Identify symbology (LocalMaps v3.1.2) in LocalMaps NZ Ideas

Identify symbology (LocalMaps v3.1.2)

Palmerston_NorthCity_Council — Thu, 13 Feb 2025 22:12:46 GMT

Users wanting to do prints or screenshots of an identified feature find that the transparent blue (polygon) obscure the property they want to highlight.

Can a configurable "IDENTIFY Symbology" section be added to the Admin functions.

The administrator should be able to set outline and fill colour and transparency for an identify action.

Re: Identify symbology (LocalMaps v3.1.2) - Status changed to: Needs Clarification

Aravindh_Rajendran — Mon, 24 Feb 2025 21:43:42 GMT

Hi @Palmerston_NorthCity_Council , Thanks for the post, we need some clarification on this. While selecting the features in the map, they are highlighted with the blue fill. When you try and print the map using the Print widget, you will get only the border highlighted without any fill. Can you check and see if this helps?

E.g.

Aravindh_Rajendran_0-1740433369651.png

That being said, having an option under admin to configure the fill colour and border colour sounds good, will add this to the backlog.

Re: Identify symbology (LocalMaps v3.1.2) - Status changed to: Needs Clarification

AndreKruger — Mon, 24 Feb 2025 22:33:39 GMT

Hi team,

If multiple polygons are highlighted by an Identify the transparency overlaps and in the end you cannot see 'through' the transparency anymore.
Often a print is not the 'desired' outcome.
People just want to see what is on the map without it being obscured..

Re: Identify symbology (LocalMaps v3.1.2)

Aravindh_Rajendran — Tue, 25 Feb 2025 00:30:18 GMT

Thanks @AndreKruger . This makes sense and gives a context, will add this to our backlog and notify once it is implemented.

Re: Identify symbology (LocalMaps v3.1.2) - Status changed to: Under Consideration

Aravindh_Rajendran — Tue, 25 Feb 2025 00:30:27 GMT

Re: Identify symbology (LocalMaps v3.1.2) - Status changed to: Implemented

Aravindh_Rajendran — Mon, 01 Dec 2025 22:29:47 GMT

Hello all, this has been implemented in 3.2x.