Protocols

Undocumented

Fill in this protocol to provide images when individual markers/labels are clustered.

This is the protocol for marker/label clustering. You must fill this in and register the cluster

Elevation Source Delegate provides elevation data for a given tile.

The Elevation Source Delegate provides elevation data on demand for a given tile. It returns a MaplyElevationChunk or nil if no data is available. Your delegate may be called on a random thread, so act accordingly.

This object is probably being used in conjuction with a MaplyTileSource, but is treated separately. We may reuse the same elevation source for multiple image pyramids and they tend not to be packaged together.

Undocumented

A delegate called during various parts of the tile loading and display operation.

The remote tile source delegate provides feedback on which tiles loaded and which didn’t. You’ll be called in all sorts of random threads here, so act accordingly.

This delegate interface can also be used to modify data as it comes in.

Protocol for receiving an offline rendered image.

This is used by the MaplyQuadImageOfflineLayer to hand over images as they are rendered.

The paging delegate is used by the paging layer to load tiles.

The Maply Paging Delegate is used by the MaplyQuadPagingLayer to do feature (e.g. not image) paging. You set up an object that implements this protocol and talks to the paging layer. This is how you load things like vector tiles.

It’s up to you to do the actual loading of tiles and turn the data into Maply features. Once you do that, the paging layer will handle the rest.

Undocumented

Undocumented

A delegate called during various parts of the tile loading and display operation.

The remote tile source delegate provides feedback on which tiles loaded and which didn’t. You’ll be called in all sorts of random threads here, so act accordingly.

This delegate interface can also be used to modify data as it comes in.

The protocol for a Maply Tile Source.

Fill out this protocol and you can pass in your own data tile by tile. This protocol is used by the MaplyQuadImageTilesLayer to pull in image data per tile. This can be one or more images, they can be local, remote or even generated on the fly. It’s up to the object itself to return suitable data as requested or indicate failure (by returning nil).

The tile source should know its coordinate system, which is handed to Maply separately.

The update delegate is called if the viewer moves, but not too often.

Use this delegate to generate features around the viewer when they move. You can control how far they have to move (in display coordinates) and how often you’ll receive updates.

An animation delegate that can be set on a MaplyViewController to control the view over time.

Filling out these methods will get you animation callbacks at the proper time to control position, heading and height on a frame basis.

You pass the resulting object in to

A protocol to fill out for selection and tap messages from the MaplyViewController.

Fill out the protocol when you want to get back selection and tap messages. All the methods are optional.

An animation delegate that can be set on a WhirlyGlobeViewController to control the view over time.

Filling out these methods will get you animation callbacks at the proper time to control position, heading, tilt, and height on a frame basis.

You pass the resulting object in to

Globe View Controller Delegate protocol for getting back selection and tap events.

Fill out the methods in this protocol and assign yourself as a delegate in the WhirlyGlobeViewController to get selection and tap events.