Closed WhiteJoker closed 11 years ago
I'm tempted to make a similar answer to #7 : if you always want those pins grouped, then why do you add two annotations to the map in the first place?
I guess you should reconsider your MKAnnotation
strategy, and instead of adding one MKAnnotation per underlying object (i.e. stations in your case), add one MKAnnoation
per "group of station with the same name".
Does that make sense?
(Plus you'd have to define "placed near to each other", which would obviously depend on your actual use case, and would make the API more complicated.)
Well in my case these are bus stops coming from an external API. Some stops have multiple platforms which the transport operator considers separate stops, but the user does not. But that does mean I need to cluster them as each stop has it's own ID.
Maybe I should cluster them in a separate annotation while I'm processing all stops.
It would be nice to permanently group annotations with the same name, which are placed near each other, together permanently as a cluster instead of splitting them up again when the user zooms in.