Mapwize For Mapbox on iOS

The Mapwize iOS SDK is built as a plugin on top of Mapbox GL native for iOS.

The Mapbox map is used as base map to display the outdoor. It is an amazingly powerful SDK allowing you to do a lot of cool stuff with the map. If you want to move the map, rotate it, overlay your own data or more, you can do it directly by controlling the Mapbox map. Adding Mapwize does not remove any capability from Mapbox, it just adds more. Have a look at the Mapbox documentation to see all features.

This Mapwize plugin is adding the possibility of getting inside buildings. As you zoom on the map, you will automatically enter in buildings, see the different floors and be able to navigate inside. If you want to change floors, see different universes (views) of the building, draw directions inside or display the user's indoor location, then you'll interact with the Mapwize plugin.

The Mapwize plugin is written in Objective-C for maximum compatibility and performance. However, it is working and extensively tested in both Objective-C and Swift apps.

Open-source Mapwize UI

If you are looking for a fully featured and ready to use View to add Mapwize Indoor Maps and Navigation in your iOS app, have a look at Mapwize UI. This open-source project enriches the core SDK with interfaces for search and directions, that you can use as is or modify to your taste.

We are ourselves using Mapwize UI to build the Mapwize app available on the App Store.

Simple apps

A very simple app integrating Mapwize is available on our Github. It contains the minimum code to display the map. It is available in both Objective-C and Swift.

Mapwize simple app Objective-C

Mapwize simple app Swift

Those app come with just the map and no other UI. If you are looking for UI, take a look at Mapwize UI.


Mapwize is compatible with iOS 10 and higher.

Adding Mapwize to your project


Mapwize is available through CocoaPod. Using pod, all dependencies, including Mapbox, will be added automatically. If you do not want to use pod, you will need to manually download the MapwizeForMapbox framework as we as all dependencies.

Simply add the following line in your Podfile

pod 'MapwizeForMapbox'


Mapwize is available through Carthage since 1.7.0.

Add the following lines to you Cartfile

github "IndoorLocation/indoor-location-ios" ~> 1.0.5
github "Mapwize/SSZipArchive" == 3.0.0
binary "" ~> 4.9.0
binary "" ~> 2.1.3

Mapwize API Key

You'll need a Mapwize API key to load the plugin and allow API requests. Simply add MWZMapwizeApiKey with the key in your info.plist.

To get your own Mapwize API key, sign up for a free account at Then within the Mapwize Studio, navigate to "API Keys" on the side menu.

Mapwize demo keys are available for testing in the demo projects. Please note they cannot be used in production.

Changing api key at runtime

In some case, you may want to display a map using a different api that the one used for initialization. For example, you displayed a first map for an organization A and you want to display another map for an organization B.

The methods setApiKey on the MWZAccountManager is available.

As the AccountManager is a Singleton, you CANNOT display two maps that use different api key at the same time.

Setting the api key when a map is already loaded won't reload the map and will display inconsistent data.

Configuring the outdoor map

MapwizePlugin is using Mapbox for the outdoor map. There are 2 options regarding the outdoor:

To use the default Mapwize outdoor map:

If you want to use your custom Mapbox style, get your Mapbox API key by sign up at

Adding your first map

Instanciate a Mapbox map, either through storyboard or through code. See details here

When the map is loaded, you can load the MapwizePlugin and attach it to the Mapbox map. You can instantiate Mapwize as soon as you get a MGLMapView with one of the following constructors:

- (instancetype) initWith:(MGLMapView*) mglMapView options:(MWZOptions*) options;
- (instancetype) initWith:(MGLMapView*) mglMapView options:(MWZOptions*) options uiSettings:(MWZUISettings*) settings;

Like for example

MapwizePlugin* mapwizePlugin;

- (void)viewDidLoad {
[super viewDidLoad];
mapwizePlugin = [[MapwizePlugin alloc] initWith:self.mapView options:options];
mapwizePlugin.delegate = self;
mapwizePlugin.mapboxDelegate = self;

Take a look at the simple apps for details and Swift version.

Mapwize plugin options and UISettings

The plugin can be loaded with the following options available in the MWZOptions class:

Options referring to UI component are provided in the MWZUISettings class:


MapwizePlugin needs access to the Mapbox map delegate to work properly. At this point, Mapbox only allows a single delegate to be set. If you need access to the Mapbox delegate, you can set yours in MapwizePlugin.mapboxDelegate which provides a copy of all events. Setting MGLMapView.delegate will cause Mapwize plugin to fail.

The Mapwize delegate provides callback for the following events:

- (void) mapwizePluginDidLoad:(MapwizePlugin*) mapwizePlugin;

- (void) plugin:(MapwizePlugin*) plugin willEnterVenue:(MWZVenue*) venue;
- (void) plugin:(MapwizePlugin*) plugin didEnterVenue:(MWZVenue*) venue;
- (void) plugin:(MapwizePlugin*) plugin didExitVenue:(MWZVenue*) venue;

- (void) plugin:(MapwizePlugin*) plugin didTap:(MWZClickEvent*) clickEvent;

- (void) plugin:(MapwizePlugin*) plugin didChangeFloor:(NSNumber*) floor;
- (void) plugin:(MapwizePlugin*) plugin didChangeFloors:(NSArray<NSNumber*>*) floors;

- (void) plugin:(MapwizePlugin*) plugin didChangeFollowUserMode:(FollowUserMode) followUserMode;


In order to react to click events on the map, Mapwize provides an object that helps you know on which object the user clicked. It can be a venue, a place or just the map.

It is represented with 3 event types :

typedef enum MWZClickEventType: NSUInteger {

The following attributes can be retrieved :

MWZClickEventType eventType;    // Enum, see above
MWZLatLngFloor* latLngFloor;    // The latLngFloor at which the click was made. The latitude and longitudes are always set, but the floor can be null. Available for all event types.
MWZPlace* place;                // Not null if eventType == PLACE_CLICK
MWZVenue* venue;                // Not null if eventType == VENUE_CLICK

A typical way to handle those event (in SWIFT):

func plugin(_ plugin: MapwizePlugin!, didTap clickEvent: MWZClickEvent!) {
    switch clickEvent.eventType {
        case VENUE_CLICK:
            let venue = clickEvent.venue
            // Do something with venue
        case PLACE_CLICK:
            let place =
            // Do something with place
            let latLngFloor = clickEvent.latLngFloor
            // Do something with coordinates

Indoor Location

Displaying the user's location on the map is done by connecting an IndoorLocationProvider to Mapwize.

There are a lot of IndoorLocation providers already freely available as part of the IndoorLocation open-source framework.

If you are missing your provider, contact us at or build your own starting from the base classes.

To set the IndoorLocationProvider on the MapwizePlugin:
- (void) setIndoorLocationProvider:(ILIndoorLocationProvider*) locationProvider;
- (void) setIndoorLocationProvider:(ILIndoorLocationProvider*) locationProvider userOnFloorImage:(UIImage*) userOnFloorImage userOutOfFloorImage:(UIImage*) userOutOfFloorImage;

If you want to manually set the user location, you can use the ManualIndoorLocationProvider

You can retrieve the current user position on the map using ILIndoorLocation* userLocation.

There is no delegate to be notified of any new user location. Subscribe to the IndoorLocationProvider's delegate instead.

The user's heading is also displayed on the map as an arrow from the user position. The heading is retrieved directly from the device. You can read the user heading using NSNumber* userHeading. It is not possible to manually set the user heading at this point.


You can use the follow user mode feature to automatically move the map as the user location changes.

3 modes are available on the MWZFollowUserMode class:

You can retrieve the current mode using the FollowUserMode followUserMode property and you can set it using

- (void) setFollowUserMode:(FollowUserMode) followUserMode;

The FollowUserMode is automatically set to NONE when the user manually moves the map or changes floor.


Indoor maps are defined inside venues. The map will automatically enter in a venue when the zoom is sufficient, and exit the venue when the map is moved away. Only one venue can be open at a time.

The currently displayed venue can be retrieved using the getVenue method

- (MWZVenue*) getVenue;

The method returns null if no venue is displayed on the map. The willEnterVenue, didEnterVenue and didExitVenue events from the delegate can be used.


Venues can have multiple universes. Universes are like views. In Mapwize Studio, it is possible to define which elements are displayed in each universe and define security policies for each of them.

When a venue is displayed, the method (MWZUniverse*) getUniverse will return the currently displayed universe for that venue, and (void) setUniverse:(MWZUniverse*) universe will change the universe.

You can set and get the universe for each venue using

- (void) setUniverse:(MWZUniverse*) universe forVenue:(MWZVenue*) venue;
- (MWZUniverse*) getUniverseForVenue:(MWZVenue*) venue;


Venues usually have multiple floors. Floors are identified by a number which can be decimal.

When a venue is displayed, the method (NSNumber*) getFloor will return the currently displayed floor for that venue and (NSArray<NSNumber*>*) getFloors will return the list of active floors for that venue. A floor is considered active if the geometry of one layer of that floor is intersecting with the visible region on the screen.

You can change floor using

- (void) setFloor:(NSNumber*) floor;
- (void) setFloor:(NSNumber*) floor forVenue:(MWZVenue*) venue;

The didChangeFloor event is fired when the floor changes.
The didChangeFloors event is fired when the list of active floors changes, which may or may not happen at venue enter, venue exit, universe change or camera move.


The title of the places that are displayed on the map can be translated in multiple languages and you can control what language is used.

Firstly, you can set the preferered language of the user. By default, titles will be displayed in the preferred language if available in the venue. Otherwise, the main language of the venue is used.

- (void) setPreferredLanguage:(NSString*) language;
- (NSString*) getPreferredLanguage;

It is also possible to specify what language to use for a specific venue

- (void) setLanguage:(NSString*) language;
- (void) setLanguage:(NSString*) language forVenue:(MWZVenue*) venue;
- (NSString*) getLanguageForVenue:(MWZVenue*) venue;
- (NSString*) getLanguage;

Moving the map

The Mapbox map offers lots of options to move the camera viewing the map. Some specific methods are available on the MapwizePlugin to move the map towards Mapwize objects:

- (void) centerOnVenue:(MWZVenue*) venue forceEntering:(BOOL) force;
- (void) centerOnPlace:(MWZPlace*) place;
- (void) centerOnUser;

Please note that the centerOnVenue takes the forceEntering parameter. If set to false, the bounds of the maps are fit so that the entire venue is visible. For large campuses, this may mean that the zoom level is not high enough to enter the venue. If forceEntering is set to true, the map will be zoomed in to be sure that the venue is displayed, possibly not showing the entire campus.

If you want more flexibility with the centerOnVenue and centerOnPlace methods, you can use the center attribute of the MWZPlace and MWZVenue objects to build your own MGLCamera object and use the Mapbox methods to move the camera. Here is an exemple :

MGLMapCamera* camera = [[MGLMapCamera alloc] init];
camera.centerCoordinate = [place center];

// You can add more properties to the camera object if you want
// camera.altitude
// camera.pitch
// camera.bearing
// ...

[mapboxMapView setCamera:camera];
// Note that mapbox offers different setCamera methods allowing to control the animation

// If it is a place, don't forget to change the floor
if (place.floor) {
    [self setFloor:place.floor];

Adding markers

Markers is a convenient way to add simple pins on the map.

Mapwize Markers are positioned on a specific floor and therefore only displayed if that floor is selected. However, they are not attached to a specific venue and will be displayed even if the venue is not visible.

If you want to add more complex annotations on the map, you have all the power of Mapbox at your disposal. Have a look at their documentation

By default, the image used for the pin is the standard Mapwize pin. However, you can specify your own using an UIImage. The anchor of the marker is always the center of the image, meaning that it's always the center of the image that is on top of the coordinates you specified. If you want to have your marker only on top, simply use an image with transparency.

- (void) addMarker:(MWZLatLngFloor*) latLngFloor completionHandler:(void (^)(MWZMapwizeAnnotation*)) completionHandler;
- (void) addMarker:(MWZLatLngFloor*) latLngFloor image:(UIImage*) image completionHandler:(void (^)(MWZMapwizeAnnotation*)) completionHandler;
- (void) addMarkerOnPlace:(MWZPlace*) place completionHandler:(void (^)(MWZMapwizeAnnotation*)) completionHandler;
- (void) addMarkerOnPlace:(MWZPlace*) place image:(UIImage*) image completionHandler:(void (^)(MWZMapwizeAnnotation*)) completionHandler;
- (void) addMarkersOnPlaceList:(MWZPlaceList*) placeList completionHandler:(void (^)(NSArray<MWZMapwizeAnnotation*>*)) completionHandler;
- (void) addMarkersOnPlaceList:(MWZPlaceList*) placeList image:(UIImage*) image completionHandler:(void (^)(NSArray<MWZMapwizeAnnotation*>*)) completionHandler;

- (void) removeMarker:(MWZMapwizeAnnotation*) marker;
- (void) removeMarkers;

Promoting places

The title of places are displayed based on the zoom level. The objective is to display as many as possible without having collisions. By default, the order specified in Mapwize Studio is used to define which place is displayed first.

However, there are situations where you would like to change dynamically the order. For example, if the user clicks on a place and you display informations about it, you might want to make sure that the title of that place is displayed. Basically, you want to promote that place to the first position.

Promoting places make them come first on the rendering. Of course, the collision mechanism still apply so if 2 promoted places collide, then only the first in the promotion list comes first. Also, promoted places only show on their floor when their venue are visible.

- (NSArray<MWZPlace*>*) getPromotedPlacesForVenue:(MWZVenue*) venue;
- (void) setPromotedPlaces:(NSArray<MWZPlace*>*) places forVenue:(MWZVenue*) venue;
- (void) addPromotedPlace:(MWZPlace*) place;
- (void) addPromotedPlaces:(NSArray<MWZPlace*>*) places;
- (void) removePromotedPlace:(MWZPlace*) place;
- (void) removePromotedPlaces:(NSArray<MWZPlace*>*) places;
- (void) removePromotedPlacesForVenue:(MWZVenue*) venue;

Showing Direction

To display directions on the map, the first step is to compute them. For that, you'll need to use the API methods to get a MWZDirection object as described in the API section.

When you have a MWZDirection object, you can display it on the map using

- (void) setDirection:(MWZDirection*) direction;
- (void) setDirection:(MWZDirection *)direction  options:(MWZDirectionOptions*) options;

The first method will use defaut DirectionOptions.

Here is the list of options with their default value:

@property (nonatomic, strong) UIImage* endMarkerIcon;   // nil
@property (nonatomic, assign) BOOL displayEndMarker;    // YES
@property (nonatomic, assign) BOOL centerOnStart;       // YES
@property (nonatomic, assign) BOOL setToStartingFloor;  // YES

If endMarkerIcon is null and displayEndMarker is true, default Mapwize marker will be used.

Once a direction is set, you can retrieve it or remove it.

- (MWZDirection*) getDirection;
- (void) removeDirection;

Showing Navigation (Dynamic direction)

Navigation is used as direction is. The difference is that navigation show the evolution of the user on the direction line.

The navigation should be used only if the starting point of the direction is the user position and if you have a IndoorLocation system working in your venue.

In order to provide an understandable visualization, Mapwize recompute the IndoorLocation to put the user position dot at the most realistic position on the direction path. Below, you will read how to use this information to recompute direction if needed.

- (void) startNavigation:(MWZDirection*) direction options:(MWZDirectionOptions*) options navigationUpdateHandler:(NavigationInfoDidUpdate) navigationUpdateHandler;
- (void) stopNavigation;

NavigationInfoDidUpdate is a block that have 3 parameters :

Styling places

Do you want to show if a meeting room is available or not, or color the prefered shops of the user? Then dynamic styling of places is what you are looking for.

You can overwrite the style of any place at any time using the setStyle function. Set the style to nil to return to the default style.

- (void) setStyle:(MWZStyle*) style forPlace:(MWZPlace*) place;

The available attributes for the style are


When developing an app around a map, it is advised not to resize the map at every user interaction. However, it might be interesting to overlay elements on top of the map. Since MapwizePlugin is adding controls on the map like the user position control or the floor control, padding can be used to free the top and bottom of the map to make space for overlay.

- (void) setBottomPadding:(CGFloat) bottomPadding;
- (void) setTopPadding:(CGFloat) topPadding;
- (void) setBottomPadding:(CGFloat) bottomPadding animationDuration:(CGFloat) duration;
- (void) setTopPadding:(CGFloat) topPadding animationDuration:(CGFloat) duration;


Maps can be made available offline using the MWZOfflineManager. When offline, the following features are available:

Data is downloaded for specific universes of specific venues.

If a venue/universe has been taken offline, all data for that venue/universe will come from the local database regarless the network availability. Changes made to the venue map on Mapwize Studio will not be available in the app until a new download is done. It is the developer's responsibility to trigger venue re-downloads.


To download content for a specific universe of a venue and make that venue/universe available offline, use downloadDataForVenue:

+ (void) downloadDataForVenue:(MWZVenue*) venue universe:(MWZUniverse*) universe success:(void (^)(void)) success progress:(void (^)(int)) progress failure:(void (^)(NSError* error)) failure;
+ (void) downloadDataForVenue:(MWZVenue*) venue universe:(MWZUniverse*) universe skipMapboxDownload:(BOOL) skipMapboxDownload success:(void (^)(void)) success progress:(void (^)(int)) progress failure:(void (^)(NSError* error)) failure;

To update the local data for a venue, the same downloadDataForVenue method can be used again.

If a venue/universe does not need to be offline anymore, removeDataForVenue can be used to delete all data from database and filesystem.

+ (void) removeDataForVenue:(MWZVenue*) venue universe:(MWZUniverse*) universe;

Note: After removing or downloading data, displayed maps need to be refreshed using MapwizePlugin#refreshWithVenue:(MWZVenue*) venue universe:(MWZUniverse*) universe. Otherwise, maps might not display properly or be inconsistent.

The following methods allow you yo check which venues and universes are available offline.

// Check if a venue/universe is offline or not
+ (BOOL) isOfflineForVenue:(MWZVenue*) venue universe:(MWZUniverse*) universe;

// Get the list of offline venues
- (NSArray<MWZVenue*>*) getOfflineVenues;

// Get the list of offline universes for the given venue
- (NSArray<MWZUniverse*>*) getOfflineUniversesForVenue:(MWZVenue*) venue;


A complete set of functions are available to query raw Mapwize objects.

Mapwize objects are cached as much as possible in the SDK to reduce network traffic. Also, some API functions are available offline if the venue and universe was downloaded using the MWZOfflineManager.

You can disable this cache using the MWZAccountManager#cacheEnabled property.

The API behaviour is as follows:



@property NSString* venueId;
@property NSString* universeId;
@property NSNumber* isVisible;
@property NSString* organizationId;
@property NSString* alias;
@property NSString* name;
@property NSString* floor;
@property NSNumber* latitudeMin;
@property NSNumber* latitudeMax;
@property NSNumber* longitudeMin;
@property NSNumber* longitudeMax;


@property NSString* query;
@property NSString* venueId;
@property NSString* organizationId;
@property NSString* universeId;
@property NSArray<NSString*>* objectClass;



Access can be granted at runtime by calling the MWZApi directly :
+ (NSURLSessionDataTask*)getAccess:(NSString*) accessKey success:(void (^)(void)) success failure:(void (^)(NSError* error)) failure

Using this, you have to refresh the MapwizePlugin manually using
- (void) refreshWithCompletionHandler:(void (^)(void)) handler;

You can also call the grantAccess method on the MapwizePlugin. This method handle the Api call and the refresh.
- (void) grantAccess:(NSString*) accessKey success:(void (^)(void)) success failure:(void (^)(NSError* error)) failure

Access are not available offline.

You can also sign in (and sign out) with the following methods. Sign in will give you all access that you have on studio.mapwize

+ (NSURLSessionDataTask*)signin:(NSString*) token success:(void (^)(void)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)signoutWithSuccess:(void (^)(void)) success failure:(void (^)(NSError* error)) failure;

Once connected, you can get the user information with the following :

+ (NSURLSessionDataTask*)getUserInfoWithSuccess:(void (^)(MWZUserInfo* userInfo)) success failure:(void (^)(NSError* error)) failure;


+ (NSURLSessionDataTask*)getVenueWithId:(NSString*) identifier success:(void (^)(MWZVenue* venue)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getVenuesWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZVenue*>* venues))success failure:(void (^)(NSError *error))failure;
+ (NSURLSessionDataTask*)getVenueWithName:(NSString*) name success:(void (^)(MWZVenue* venue)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getVenueWithAlias:(NSString*) alias success:(void (^)(MWZVenue* venue)) success failure:(void (^)(NSError* error)) failure;


+ (NSURLSessionDataTask*)getPlaceWithId:(NSString*) identifier success:(void (^)(MWZPlace* place)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlacesWithName:(NSString*) name venue:(MWZVenue*) venue success:(void (^)(MWZPlace* place)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlacesWithAlias:(NSString*) alias venue:(MWZVenue*) venue success:(void (^)(MWZPlace* place)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlacesWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZPlace*>* places)) success failure:(void (^)(NSError* error)) failure;


+ (NSURLSessionDataTask*)getConnectorPlaceWithId:(NSString*) identifier success:(void (^)(MWZConnectorPlace* connectorPlace)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getConnectorPlacesWithName:(NSString*) name venue:(MWZVenue*) venue success:(void (^)(MWZConnectorPlace* connectorPlace)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getConnectorPlacesWithAlias:(NSString*) alias venue:(MWZVenue*) venue success:(void (^)(MWZConnectorPlace* connectorPlace)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getConnectorPlacesWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZConnectorPlace*>* connectors)) success failure:(void (^)(NSError* error)) failure;

ConnectorPlaces are not available offline


+ (NSURLSessionDataTask*)getPlaceListWithId:(NSString*) identifier success:(void (^)(MWZPlaceList* placeList)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlaceListsWithName:(NSString*) name venue:(MWZVenue*) venue success:(void (^)(MWZPlaceList* placeList)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlaceListsWithAlias:(NSString*) alias venue:(MWZVenue*) venue success:(void (^)(MWZPlaceList* placeList)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getPlaceListsWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZPlaceList*>* placeLists)) success failure:(void (^)(NSError* error)) failure;

MainFrom & MainSearches

+ (NSURLSessionDataTask*)getMainFromsWithVenue:(MWZVenue*) venue success:(void (^)(NSArray<MWZPlace*>* places)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getMainSearchesWithVenue:(MWZVenue*) venue success:(void (^)(NSArray<id<MWZObject>>* mainSearches)) success failure:(void (^)(NSError* error)) failure;


+ (NSURLSessionDataTask*)getLayerWithId:(NSString*) identifier success:(void (^)(MWZLayer* layer)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getLayerWithName:(NSString*) name venue:(MWZVenue*) venue success:(void (^)(MWZLayer* layer)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getLayerWithAlias:(NSString*) alias venue:(MWZVenue*) venue success:(void (^)(MWZLayer* layer)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getLayersWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZLayer*>* layers)) success failure:(void (^)(NSError* error)) failure;

Layers are not available offline.


+ (NSURLSessionDataTask*)getUniverseWithId:(NSString*) identifier success:(void (^)(MWZUniverse* universe)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getUniversesWithFilter:(MWZApiFilter*) filter success:(void (^)(NSArray<MWZUniverse*>* universes)) success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getAccessibleUniversesWithVenue:(MWZVenue*) venue success:(void (^)(NSArray<MWZUniverse*>* universes)) success failure:(void (^)(NSError* error)) failure;


+ (NSURLSessionDataTask*)getDirectionWithFrom:(id<MWZDirectionPoint>) from to:(id<MWZDirectionPoint>) to isAccessible:(BOOL) isAccessible success:(void (^)(MWZDirection* direction))success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getDirectionWithFrom:(id<MWZDirectionPoint>) from tos:(NSArray<id<MWZDirectionPoint>>*) tos isAccessible:(BOOL) isAccessible success:(void (^)(MWZDirection* direction))success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getDirectionWithFrom:(id<MWZDirectionPoint>) from to:(id<MWZDirectionPoint>) to waypoints:(NSArray<id<MWZDirectionPoint>>*) waypoints isAccessible:(BOOL) isAccessible success:(void (^)(MWZDirection* direction))success failure:(void (^)(NSError* error)) failure;
+ (NSURLSessionDataTask*)getDirectionWithFrom:(id<MWZDirectionPoint>) from tos:(NSArray<id<MWZDirectionPoint>>*) tos waypoints:(NSArray<id<MWZDirectionPoint>>*) waypoints isAccessible:(BOOL) isAccessible success:(void (^)(MWZDirection* direction))success failure:(void (^)(NSError* error)) failure;

Directions with waypoints and/or multiple "To" parameters are not available offline.


You can get a list of distance between a 'from' point to a list of 'to' points using :

+ (NSURLSessionDataTask*)getDistanceWithFrom:(id<MWZDirectionPoint>) from tos:(NSArray<id<MWZDirectionPoint>>*) tos isAccessible:(BOOL) isAccessible sortByTravelTime:(BOOL) sort success:(void (^)(MWZDistanceResponse* distance))success failure:(void (^)(NSError* error)) failure

Distances are not available offline.


+ (NSURLSessionDataTask*)searchWithParams:(MWZSearchParams*) searchParams success:(void (^)(NSArray<id<MWZObject>>* searchResponse)) success failure:(void (^)(NSError* error)) failure;

The offline search does not return the same results as the online search.

Custom Server Url

If you are using a custom instance of Mapwize server you have to set the api URL. This is done by adding a MWZCustomApiUrl to your info.plist.

The default value is ""

Evolution and support

The SDK is evolving quickly. If you wish you had an extra function or if you have any remark, don't hesitate to contact us. Updates can be pushed quickly for critical matters.

For any question, contact us at