OpenGIS / Waymark

Waymark adds powerful mapping features to WordPress that are easy to use. Create beautiful, interactive Maps that you can customise to suit your needs.
https://www.waymark.dev
GNU General Public License v2.0
20 stars 6 forks source link

Clustering of multiple waymark types #30

Open micrtoeq opened 5 months ago

micrtoeq commented 5 months ago

Hi

The new clustering fiunction is really great!

If I understood the function correctly, it is only clustering the exact same waymark type, at the moment. Would it be possible to cluster selected different waymarks?

Many thanks Daniel

morehawes commented 5 months ago

Hi @micrtoeq,

The new clustering fiunction is really great!

Great! You're the first person to mention it :0)

it is only clustering the exact same waymark type, at the moment. Would it be possible to cluster selected different waymarks?

I'm not sure I follow. Markers shouldcluster regardless of Type, and be "stacked" with a count for each Type. Are you experiencing something different than on the demo?

Cheers,

Joe

micrtoeq commented 5 months ago

Yes, it is a bit complicated to explain. Let's make an example:

I set the starting point of any of my hikes onto an overview map. I have three types of hikes, difficult, medium and easy. Now, you are right that any of those types is clustering correctly for itself. But what I would like to have is clustering those three together, independant of their type. If one easy, one medium and one difficult hike overlap, I would like to have displayed one of them and a little rectangle with the number 3. The luxury version would be that I also could select a waymark that would be shown as a replacement, if the clustered marker types are different.

Many thanks and best regards. Daniel.

morehawes commented 5 months ago

Hi @micrtoeq,

Thanks for the extra detail, I believe I understand now:

Instead of multiple stacked Markers, each with counts you would prefer one Marker (to be specified) with the total count of all types.

How are you imaging the "one Marker" would be specified - Globally in Settings, per Shortcode, per Map?

I will have a think on this and try to figure out how much work this would be.

I think it would be a nice option to have.

Cheers,

Joe

micrtoeq commented 5 months ago

Hi Joe

I think defining the common marker in the shortcode would be ok. Maybe you name it cluster_marker=”xyz”.

Maybe the easiest implementation would be, having this shortcode defined, means to cluster all markers, independent of their type, and replace them with the cluster_marker. If the shortcode is not defined, the implementation would be as it is today. I think, you can even leave the little rectangle containing the number, instead of setting the number into the common marker.

In my case, I would just have let’s say a gray marker, which would also have the little rectangle containing the marker count on the top right (as it is implemented today), replacing the overlapping blue (easy) , red (medium) and black (difficult) ones.

I hope, my explanation is not too complicated, because I think the solution is quite simple.

Many thanks and best regards. Daniel.

Von: Joe Hawes @.> Gesendet: Donnerstag, 18. Januar 2024 16:29 An: OpenGIS/Waymark @.> Cc: microteq @.>; Mention @.> Betreff: Re: [OpenGIS/Waymark] Clustering of multiple waymark types (Issue #30)

Hi @micrtoeqhttps://github.com/micrtoeq,

Thanks for the extra detail, I believe I understand now:

Instead of multiple stacked Markers, each with counts you would prefer one Marker (to be specified) with the total count of all types.

How are you imaging the "one Marker" would be specified - Globally in Settings, per Shortcode, per Map?

I will have a think on this and try to figure out how much work this would be.

I think it would be a nice option to have.

Cheers,

Joe

— Reply to this email directly, view it on GitHubhttps://github.com/OpenGIS/Waymark/issues/30#issuecomment-1898698951, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKCQDVXVOQ5YZXDKRNL7LWDYPE5TBAVCNFSM6AAAAABB22K2ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGY4TQOJVGE. You are receiving this because you were mentioned.Message ID: @.**@.>>