
Here's an example of the UriFormatString property for an HttpMapTileDataSource that shows the replaceable parameters for the X and Y coordinates and the zoom level. That is, you insert replaceable parameters in the base Uri or filename to indicate where to pass the X and Y coordinates and the zoom level for each tile.

You simply specify the format of the Uri or filename to use to retrieve the tiles in the UriFormatString property. Each request specifies the X and Y coordinates and the zoom level for the individual tile. The MapControl requests tiles as it needs them. When you use tile sources, you don't have to write code to request or to position individual tiles. Use tile sources to retrieve third-party tiles, or to create your own custom tiles, and overlay them on the map displayed in the MapControl. Many third-party services also provide map-based data that's cut into tiles. These tiles are 256 pixels by 256 pixels in size, and are pre-rendered at multiple levels of detail. Map services such as Nokia Maps and Bing Maps cut maps into square tiles for quick retrieval and display. Tip To learn more about using maps in your app, download the Universal Windows Platform (UWP) map sample on Github. Use tile sources to overlay specialized information such as weather data, population data, or seismic data or use tile sources to replace the default map entirely. Overlay third-party or custom tiled images on a map by using tile sources.

For more info about getting and setting a maps authentication key, see Request a maps authentication key. MapControl and map services requite a maps authentication key called a MapServiceToken.
