Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

determine annotation policy for > +/- 85.xxx latitude #1671

Closed
incanus opened this issue Jun 1, 2015 · 1 comment
Closed

determine annotation policy for > +/- 85.xxx latitude #1671

incanus opened this issue Jun 1, 2015 · 1 comment
Labels
MapKit parity For feature parity with MapKit on iOS or macOS

Comments

@incanus
Copy link
Contributor

incanus commented Jun 1, 2015

When we add point or shape annotations, as of bf6be3c we now properly clamp high latitude values to avoid problems with projection. We leave the passed latitude intact, though, so data queries still work as expected.

We need to determine render behavior, though. Per @1ec5, Apple MapKit doesn't render points at high latitude, but maintains them in mapView.annotations for querying. Behavior for shapes isn't known yet, but we probably want to just clip them as we do at tile edges.

Related: #1660

@incanus incanus added the GL JS parity For feature parity with Mapbox GL JS label Jun 1, 2015
@1ec5 1ec5 added MapKit parity For feature parity with MapKit on iOS or macOS and removed GL JS parity For feature parity with Mapbox GL JS labels Aug 15, 2016
@jfirebaugh
Copy link
Contributor

Closing. Almost two years with no action and never heard this come up in practice. Presumably the existing behavior is acceptable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
MapKit parity For feature parity with MapKit on iOS or macOS
Projects
None yet
Development

No branches or pull requests

3 participants