...

The tile parameter is optional and specifies settings related to the tiles provided. The default is set according to the OSM spec, and should only be changed if you're using your own OSM tiles.

The envelope parameter  the parameter is optional and specifies the extent of the tiles. The default is set according to the OSM spec, and should only be changed if you're using your own OSM tiles.

...

Note: Before using the Google Map Service, please ensure you read through the Google Maps Terms of Service and ensure that you have correctly setup licensing with Weave.

ArcGIS

There are two ArcGIS specific methods of providing tile cache support to Weave clients, this method is specifically provided to support exposing a local compressed ArcGIS map service tile cache, i.e. a tile cache created by ArcGIS where the tiles are stored in the compressed format (with .bundle, or with .bundle and .bundlx files) on the local file system of the Weave server. If this is not your situation then you should use the ArcGIS specific map engine to expose the tiles.

For the ArcGIS tiles map engine the type value should be set to arcgis and a tilingScheme value must be provided that points to the local conf.xml file.

<?xml version="1.0" encoding="UTF-8"?>

<config xmlns='urn:com.cohga.server.config#1.0' xmlns:tiled="urn:com.cohga.server.map.tiled#1.0">

	<tiled:mapengine id="ags.tiled.aerial10cm">
		<type>arcgis</type>
		<tilingScheme>/data/spatial/raster/aerial10cm/Layers/conf.xml</tilingScheme>
	</tiled:mapengine>

</config>

Client

Once the map engine is created it must be added to a ToC model and client map view the same as any other map engine. The client map engine configuration should specify only the map engine id. Weave provides all of the parameters required to configure the map engine and it obtains these by processing the 'capabilities document' of the map service.

...