mbxmapkit icon indicating copy to clipboard operation
mbxmapkit copied to clipboard

DEPRECATED - Lightweight Mapbox integration with MapKit on iOS

Results 28 mbxmapkit issues
Sort by recently updated
recently updated
newest added

Definitely a blue sky/pet project, just putting it on the table: `npm install mbxmapkit-react-native` It would be awesome if you could could work with mbxmapkit in a react native project....

Running against an Objective-C++ XCode project, reverting back to `#import` fixes the compile errors. I did change `MBXMapKit.podspec` to reinclude the framework requirements as I was not sure whether that...

This enable a single overlay to display all saved offline databases. In my use case, I have a feature where users can save map region for offline use. When switching...

enhancement

We should figure out how to recognize resource loading failures which are caused by a mapbox.com hosting account going over its limit, and we should have an NSError error code...

enhancement

Now that we've got docs back online, we should segment them out by version so we don't break links, like https://www.mapbox.com/mapbox.js/api/v2.1.5/ does.

docs

Styles created with Mapbox Studio can't have markers, so their `markers.geojson` / `features.json` always `404` rather than return an empty collection. This creates an off-by-one bug in the offline downloading...

bug

Hi i am implemented the sdk in my app, working fine but i got this error: When the map download state changed. Error while reading offline map urls: Error Domain=MBXMapKitErrorDomain...

This should be straightforward based on [RMMBTilesSource](https://github.com/mapbox/mapbox-ios-sdk/blob/release/MapView/Map/RMMBTilesSource.h). However, linking to SQLite is a problem if we want to keep things simple for installation. Two thoughts right now: 1. For CocoaPods,...

feature

Overzooming, or scaling and cropping tiles from a lower zoom level, is useful for: 1. Maps with more than one layer, where the max zoom for one tile source is...

feature

It appears the initialization logic is designed to preserve having previously set the flag programmatically via the property, but in doing so the default value is never set on first...

bug