### JavaScript for Dynamic Link Generation

Source: https://api3.geo.admin.ch/_sources/api/examples.rst

This script processes a configuration array to dynamically generate lists of links to mapping examples. It maps 'codepen' IDs to full CodePen URLs and appends them to specific HTML elements based on category, enabling interactive display of example collections.

```javascript
var conf = [{
      label: 'Map with overlay layer',
      codepen: 'qbeqPQ',
      cat: 0
    }, {
      label: 'Map with KML file overlay',
      codepen: 'eJqBVV',
      cat: 0
    }, {
      label: 'Geocoder',
      codepen: 'JGgzQG',
      cat: 0
    }, {
      label: 'Rectangle selection',
      codepen: 'NxQmvo',
      cat: 0
    }, {
      label: 'Searchbox',
      codepen: 'xZvNEY',
      cat: 0
    }, {
      label: 'Catalog',
      codepen: 'grYLdY',
      cat: 0
    }, {
      label: 'Localisation',
      codepen: 'GZKrem',
      cat: 0
    }, {
      label: 'GeoJSON integration',
      codepen: 'ZWzXgv',
      cat: 0
    }, {
      label: 'WMTS and WMS in swiss projection (EPSG:21781)',
      codepen: 'xVKLdV',
      cat: 1
    }, {
      label: 'WMTS in Pseudo-Mercator projection (EPSG:3857)',
      codepen: 'pyzwwL',
      cat: 1
    }, {
      label: 'WMTS in LV95 (EPSG:2056)',
      codepen: 'GZKEam',
      cat: 1
    }, {
      label: 'All available layers as WMTS',
      codepen: 'MyYYXR',
      cat: 1
    }, {
      label: 'Most simple example using vanilla OL6',
      link: 'https://codesandbox.io/s/geoadmin-with-vanilla-openlayers-z3dij',
      cat: 2
    }, {
      label: 'Using WMTS and WMS together in OL6',
      link: 'https://codesandbox.io/s/vanilla-openlayers-with-a-wms-layer-06h77',
      cat: 2
    }, {
      label: 'More OpenLayers 6 Examples on the official website.',
      link: 'https://openlayers.org/en/v6.5.0/examples/',
      cat: 2
    }, {
      label: 'Feature selection of KML and GeoJSON layers',
      codepen: 'yOBzqM',
      cat: 3
    }, {
      label: 'Geoadmin Terrain and WMTS CesiumJS integration',
      codepen: 'zBEYGE',
      cat: 4
    }, {
      label: 'WMTS in EPSG:3857 using Leaflet',
      codepen: 'grGOLV',
      cat: 5
    }, {
      label: 'WMS in EPSG:3857 using Leaflet',
      codepen: 'JKAjWk',
      cat: 5
    }, {
      label: 'Mapbox vectortiles example',
      codepen: 'GvgLvj',
      cat: 5
    }];
    var tpl = '<li><a href="{link}" target="_blank">{label}</a></li>';
    var cat1 = '', cat2 = '', cat3 = '', cat4 = '', cat5 = '';
    conf.forEach(function(item) {
      if (item.codepen) {
        item.link = '//codepen.io/geoadmin/pen/' + item.codepen + '?editors=0010';
      }
      var link = tpl.replace('{link}', item.link).replace('{label}', item.label);
      switch(item.cat) {
        default:
          break;
        case 1:
          cat1 += link;
          break;
        case 2 :
          cat2 += link;
          break;
        case 3:
          cat3 += link;
          break;
        case 4:
          cat4 += link;
          break;
        case 5:
          cat5 += link;
          break;
      };
    });
    document.getElementById('cat1').innerHTML = cat1;
    document.getElementById('cat2').innerHTML = cat2;
    document.getElementById('cat3').innerHTML = cat3;
    document.getElementById('cat4').innerHTML = cat4;
    document.getElementById('cat5').innerHTML = cat5;
  
```

--------------------------------

### Vectortiles Configuration Examples

Source: https://api3.geo.admin.ch/releasenotes/index

Examples of URLs pointing to vectortile configurations and styles, commonly used for map rendering and data access in web mapping applications.

```JSON
// Vectortiles set "base"
// https://vectortiles.geo.admin.ch/tiles/ch.swisstopo.base.vt/v1.0.0/tiles.json
```

```JSON
// Base Map Style
// https://vectortiles.geo.admin.ch/styles/ch.swisstopo.basemap.vt/style.json
```

```JSON
// Light Base Map Style
// https://vectortiles.geo.admin.ch/styles/ch.swisstopo.lightbasemap.vt/style.json
```

```JSON
// Imagery Base Map Style
// https://vectortiles.geo.admin.ch/styles/ch.swisstopo.imagerybasemap.vt/style.json
```

--------------------------------

### OpenLayers Example Links

Source: https://api3.geo.admin.ch/services/sdiservices

Links to external CodePen examples demonstrating the use of Geo Admin CH services with OpenLayers. These examples showcase specific functionalities like Cadastralwebmap as WMTS or Swissimage as XYZ.

```OpenLayers
http://codepen.io/geoadmin/pen/pyzwwL?editors=0010
http://codepen.io/geoadmin/pen/xVKLdV?editors=0010
http://codepen.io/geoadmin/pen/GZKEam?editors=0010
http://codepen.io/geoadmin/pen/MyYYXR?editors=0010
https://codepen.io/geoadmin/pen/xxYEwjQ
```

--------------------------------

### GeoAdmin API MapServer Endpoint Examples

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

Provides examples of common API requests to the GeoAdmin MapServer, including listing all layers, searching by text, and finding layers by GeoCat ID.

```APIDOC
API: GeoAdmin MapServer

Base URL: https://api3.geo.admin.ch/rest/services/api/MapServer

Methods:

1.  **List all layers**
    *   **Description**: Retrieves a list of all available layers in the GeoAdmin API.
    *   **URL**: `GET /rest/services/api/MapServer`
    *   **Parameters**: None
    *   **Returns**: JSON object containing layer information.
    *   **Example**: `https://api3.geo.admin.ch/rest/services/api/MapServer`

2.  **Find layers by text search**
    *   **Description**: Searches for layers where the specified text appears in their description or name.
    *   **URL**: `GET /rest/services/api/MapServer`
    *   **Parameters**:
        *   `searchText` (string, optional): The text to search for within layer descriptions.
    *   **Returns**: JSON object containing matching layer information.
    *   **Example**: `https://api3.geo.admin.ch/rest/services/api/MapServer?searchText=wasser`

3.  **Find layer by GeoCat ID**
    *   **Description**: Retrieves information for a specific layer using its unique GeoCat metadata identifier.
    *   **URL**: `GET /rest/services/api/MapServer`
    *   **Parameters**:
        *   `searchText` (string, required): The GeoCat ID of the layer to find.
    *   **Returns**: JSON object containing the specific layer's information.
    *   **Example**: `https://api3.geo.admin.ch/rest/services/api/MapServer?searchText=f198f6f6-8efa-4235-a55f-99767ea0206c`

4.  **Get Layer Attributes by BOD ID**
    *   **Description**: Exposes the attribute names specific to a layer, identified by its BOD ID. Useful when combined with the find service.
    *   **URL**: `GET /rest/services/api/MapServer/{layerBodId}`
    *   **Parameters**:
        *   `layerBodId` (string, required): The technical name or BOD ID of the layer.
        *   `lang` (string, optional): The language for the response. Supported values: de, fr, it, rm, en. Defaults to 'de'.
    *   **Returns**: JSON object detailing the layer's attributes.
    *   **Example**: `https://api3.geo.admin.ch/rest/services/api/MapServer/ch.bfs.gebaeude_adresse.gebaeude`
```

--------------------------------

### Example XYZ Tile URL

Source: https://api3.geo.admin.ch/services/sdiservices

An example URL for fetching a JPEG tile from the Swissimage layer using the XYZ tile service. It demonstrates the structure with specific values for projection, zoom, and tile coordinates.

```APIDOC
https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.swissimage/default/current/3857/{z}/{x}/{y}.jpeg
```

--------------------------------

### XYZ GetTile Request Parameters

Source: https://api3.geo.admin.ch/services/sdiservices

Details the parameters required for a GET request to the XYZ tile service. It specifies the meaning and example values for Scheme, ServerName, Version, Layername, StyleName, Time, TileMatrixSet, and format extension.

```APIDOC
GET <Scheme>://<ServerName>/<ProtocoleVersion>/<LayerName>/<Stylename>/<Time>/<TileMatrixSet>/{z}/{x}/{y}.<FormatExtension>

Parameters:
  Scheme: https
  ServerName: wmts[0-9].geo.admin.ch
  Version: 1.0.0
  Layername: ch.bfs.arealstatistik-1997 (See WMTS GetCapabilities)
  StyleName: default
  Time: 2010, 2010-01, current (ISO-8601 or logical value, check GetCapabilities for available values)
  TileMatrixSet: 3857 (constant, EPSG code for Webmercator)
  {z}: Zoom level
  {x}: X coordinate
  {y}: Y coordinate
  FormatExtension: png (or jpeg for some raster layers)
```

--------------------------------

### Height Service Example

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

An example URL for the Height service, which likely provides elevation data based on easting and northing coordinates.

```APIDOC
Height Service Example:
  URL:
    https://api3.geo.admin.ch/rest/services/height?easting=2600000&northing=1200000
```

--------------------------------

### Example WMTS Tile URL

Source: https://api3.geo.admin.ch/services/sdiservices

An example URL for fetching a specific tile from the WMTS service. It specifies the service version, layer, style, time, projection, zoom level, and tile coordinates.

```APIDOC
https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/9/266/180.jpeg
```

--------------------------------

### Layers Metadata Response Example

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

An example JSON response structure for the GeoAdmin API Layers Metadata endpoint, showing details of a 'Temperature monitoring stations' layer.

```javascript
{
  "layers": [
    {
      "name": "Temperature monitoring stations",
      "fullName": "Water temperature monitoring stations",
      "idGeoCat": "4f10c35a-8fac-4000-ab6d-7a294284059a",
      "layerBodId": "ch.bafu.hydrologie-wassertemperaturmessstationen",
      "attributes": {
          "wmsUrlResource": "http://wms.geo.admin.ch/?REQUEST=GetCapabilities&SERVICE=WMS&VERSION=1.3.0",
          "scaleLimit": "-",
          "inspireUpperAbstract": "Environnement, biology and geology | Space and population",
          "inspireName": "Environmental monitoring facilities | Human health and safety",
          "urlDetails": "http://www.bafu.admin.ch/hydrologie/01835/02122/index.html?lang=de",
          "abstract": "...",
          "inspireAbstract": "...",
          "dataOwner": "Federal Office for the Environment FOEN",
          "wmsContactAbbreviation": "swisstopo",
          "maps": "...",
          "wmsContactName": "Federal Office of Topography swisstopo",
          "dataStatus": "20130322",
          "inspireUpperName": "Environment biology and geology | Space and population",
          "urlApplication": "http://map.bafu.admin.ch"
      }
    }
  ],
  "tileInfo": {
    "origin": {
      "y": 350000,
      "x": 420000,
      "spatialReference": {
        "wkid": 21781
      }
    }
  }
}
```

--------------------------------

### Tile Matrix Set Overview (Example Data)

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

Presents sample data illustrating the relationship between zoom levels, resolutions, and scale factors for different tile matrix sets, as seen in WMTS GetCapabilities.

```APIDOC
Tile Matrix Set Data (Illustrative):

Zoom | Resolution (m) | Scale | Matrix Width | Matrix Height | Tile Width | Tile Height | Scale Denominator
-----|----------------|-------|--------------|---------------|------------|-------------|-------------------
21   | 5              | 1:18'898 | 1280         | 375           | 250        | 93'750      | 1 : 18'898
22   | 2.5            | 1:9'449  | 640          | 750           | 500        | 375'000     | 1 : 9'449
23   | 2              | 1:7'559  | 512          | 938           | 625        | 586'250     | 1 : 7'559
24   | 1.5            | 1:5'669  | 384          | 1250          | 834        | 1'042'500   | 1 : 5'669
25   | 1              | 1:3'780  | 256          | 1875          | 1250       | 2'343'750   | 1 : 3'780
26   | 0.5            | 1:1'890  | 128          | 3750          | 2500       | 9'375'000   | 1 : 1'890
27   | 0.25           | 1:945    | 64           | 7500          | 5000       | 37'500'000  | 1 : 945
28   | 0.1            | 1:378    | 25.6         | 18750         | 12500      | 234'375'000 | 1 : 378

Note: Zoom level 24 is generated but not used in API. Levels 27/28 are layer-dependent.
```

--------------------------------

### WMTS GetTile Request Example

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

Demonstrates the structure of a typical GetTile request URL for WMTS services, specifying the layer, version, projection, zoom level, and tile coordinates.

```APIDOC
GetTile Request URL Structure:

http://wmts.geo.admin.ch/1.0.0/<LayerName>/<Style>/<Time>/<CRS>/<ZoomLevel>/<XCoordinate>/<YCoordinate>.jpeg

Example:
https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/3857/9/266/180.jpeg

Parameters:
  <LayerName>: The identifier for the map layer (e.g., ch.swisstopo.pixelkarte-farbe).
  <Style>: The style to apply to the layer (e.g., default).
  <Time>: The time dimension, often 'current' for the latest data.
  <CRS>: The Coordinate Reference System identifier (e.g., 21781 for LV03, 2056 for LV95, 3857 for Pseudo-Mercator).
  <ZoomLevel>: The zoom level of the tile.
  <XCoordinate>: The X (column) coordinate of the tile.
  <YCoordinate>: The Y (row) coordinate of the tile.

Note: Axis order can vary; EPSG:21781 uses row/col, while others use col/row.
```

--------------------------------

### GetTile API Endpoint and Parameters

Source: https://api3.geo.admin.ch/services/sdiservices

Details the structure of the GET request for the GetTile API endpoint, including all required path parameters and their explanations. It also covers the definition of the TileMatrixSet and the mapping between resolutions and zoom levels.

```APIDOC
GET <Scheme>://<ServerName>/<ProtocoleVersion>/<LayerName>/<Stylename>/<Time>/<TileMatrixSet>/<TileRow>/<TileCol>.<FormatExtension>

Parameters:
  Scheme: The scheme type (e.g., https).
  ServerName: The server name (e.g., wmts[0-9].geo.admin.ch).
  ProtocoleVersion: WMTS protocol version (e.g., 1.0.0).
  LayerName: The name of the layer (e.g., ch.bfs.arealstatistik-1997). Refer to GetCapabilities for available layers.
  StyleName: The style name (only 'default' is supported).
  Time: Date of tile generation in ISO-8601 format or logical value like 'current'. Check GetCapabilities for available values.
  TileMatrixSet: EPSG code for the projection (e.g., 2056 for LV95).
  TileRow: The row index of the tile.
  TileCol: The column index of the tile.
  FormatExtension: The image format (e.g., png, jpeg).
```

```APIDOC
TileMatrixSet Definition (Example for EPSG:2056):
  MinX: 420000
  MaxX: 900000
  MinY: 30000
  MaxY: 350000
  TileWidth: 256
  TileOrigin: Top-left corner of the bounding box.
```

```APIDOC
Resolution and Zoom Level Mapping:
  Resolution [m] | Zoomlevel | Map zoom | Tile width m | Tiles X | Tiles Y | Tiles | Approx. scale at 96 dpi
  ----------------|-----------|----------|--------------|---------|---------|-------|------------------------
  4000            | 0         |          | 1024000      | 1       | 1       | 1     | 
  3750            | 1         |          | 960000       | 1       | 1       | 1     | 
  3500            | 2         |          | 896000       | 1       | 1       | 1     | 
  3250            | 3         |          | 832000       | 1       | 1       | 1     | 
  3000            | 4         |          | 768000       | 1       | 1       | 1     | 
  2750            | 5         |          | 704000       | 1       | 1       | 1     | 
  2500            | 6         |          | 640000       | 1       | 1       | 1     | 
  2250            | 7         |          | 576000       | 1       | 1       | 1     | 
  2000            | 8         |          | 512000       | 1       | 1       | 1     | 
  1750            | 9         |          | 448000       | 2       | 1       | 2     | 
  1500            | 10        |          | 384000       | 2       | 1       | 2     | 
  1250            | 11        |          | 320000       | 2       | 1       | 2     | 
  1000            | 12        |          | 256000       | 2       | 2       | 4     | 
  750             | 13        |          | 192000       | 3       | 2       | 6     | 
  650             | 14        | 0        | 166400       | 3       | 2       | 6     | 1 : 2’456’694
  500             | 15        | 1        | 128000       | 4       | 3       | 12    | 1 : 1’889’765
  250             | 16        | 2        | 64000        | 8       | 5       | 40    | 1 : 944’882
  100             | 17        | 3        | 25600        | 19      | 13      | 247   | 1 : 377’953
  50              | 18        | 4        | 12800        | 38      | 25      | 950   | 1 : 188’976
  20              | 19        | 5        | 5120         | 94      | 63      | 5’922 | 1 : 75’591
  10              | 20        | 6        | 2560         | 188     | 125     | 23’500| 1 : 37’795
  5               | 21        | 7        | 1280         | 375     | 250     | 93’750| 1 : 18’898
  2.5             | 22        | 8        | 640          | 750     | 500     | 375’000| 1 : 9’449
  2               | 23        | 9        | 512          | 938     | 625     | 586’250| 1 : 7’559
  1.5             | 24        |          | 384          | 1250    | 834     | 1’042’500| 
  1               | 25        | 10       | 256          | 1875    | 1250    | 2’343’750| 1 : 3’780
  0.5             | 26        | 11       | 128          | 3750    | 2500    | 9’375’000| 1 : 1’890
  0.25            | 27        | 12       | 64           | 7500    | 5000    | 37’500’000| 1 : 945
  0.1             | 28        | 13       | 25.6         | 18750   | 12500   | 234’375’000| 1 : 378
```

```APIDOC
Example Usage:
  http://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/21781/20/58/70.jpeg
  https://wmts.geo.admin.ch/1.0.0/ch.swisstopo.pixelkarte-farbe/default/current/21781/20/58/70.jpeg
```

--------------------------------

### Map Initialization and Interaction

Source: https://api3.geo.admin.ch/api/integrate_cms

Implements a map display using the geo.admin.ch API. It includes HTML for the map container, CSS for styling, and JavaScript to initialize the map, add a background layer, place an icon feature with a popup, and define interaction logic.

```html
<div id="map"></div>
```

```css
.element {
  background-color: white;
  padding-left: 8px;
  padding-bottom: 8px;
  padding-top: 8px;
  width: 220px;
  color: #555;
  font: 11px tahoma,arial,verdana,sans-serif;
}
.title {
  margin-top: -4px;
  font-weight: bold;
}
.undertitle {
  font-style: normal;
  margin-bottom: -3px;
  margin-top: -5px;
}
.middle {
  margin-top: -9px;
}
.close {
  cursor: pointer;
  text-decoration: none;
  position: absolute;
  top: 2px;
  right: 8px;
  font-size: larger;
  font-weight: bold;
}
```

```javascript
//Create a GeoAdmin Map
var map = new ga.Map({
  // Define the div where the map is placed
  target: 'map',
  // Create a view
  view: new ol.View({
    // 10 means that one pixel is 10m width and height
    // List of resolution of the WMTS layers:
    // 650, 500, 250, 100, 50, 20, 10, 5, 2.5, 2, 1, 0.5, 0.25, 0.1
    resolution: 5,
    // Define a coordinate CH1903 (EPSG:21781) for the center of the view
    center: [709136, 270186]
  })
});
// Create a background layer
var lyr1 = ga.layer.create('ch.swisstopo.pixelkarte-farbe');
var iconFeature = new ol.Feature({
  geometry: new ol.geom.Point([709136, 270186]),
  name: 'Null Island',
  population: 4000,
  rainfall: 500
});
var iconStyle = new ol.style.Style({
  image: new ol.style.Icon({
    anchor: [0.5, 0.5],
    anchorXUnits: 'fraction',
    anchorYUnits: 'fraction',
    src: 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9oLCAwhG8L1qXwAAAJ1SURBVDjLTZPBThRBEIa/6uleYtDVA8QHUGIw4ehVb3Ii+AK+guGid696Ud/AN4BAiFw9ePUAbmK4SIAo7OxuZtnZmZ7umfLQED1U0of6qur/q1oA9PgYWVlBBwNHCGt4v8Ws3GRa9BmPoSimDIc7jEYfqOtD+fw56MYGsruL6GCAPH6Mqjq+f9+jbZ9T1zArYVoo4zFMJsJoBMMh5PkBT55syNu3QZ89QwD07MxxcjJBZJEQFGME7+H8HC4vIc+5LqSMRsJsVuDcsnz7Fozu7zuOjvYoy0WKqeKccP8+3LkDvoHJJEVRwHQqVJVydXWXP392dXXVWcpyjbZ9DiggGIGmgdNTOPkFFxc3MMxmUJaCb5TQrBPCmmU43AKg64QQElhVMBrDZJzgsryBoaohBiFGEHllyfNNOoW2BV9DNU8G3gBlCfM51HWCQ4BOQQxo98Ly+3cfa5UQJCVVCZjP07uuUzQNhAhdB5kBI4qau5Y8hyxLlb3/B3gPtU9gDBDbZJPNQIRr2Viqaor3fWJMyU2T3G8aaGOS1ikYAZOBMSlAiLGwVNUOV1cvaVuIMU0S22uwTbvJDFgLCwsJjhFUQXXbEOMHQoC6VrxPBdr4H5wl8N49WFqC27eh11NcD5z7ZFjoHaJ6QIhCjErbpe4qSa+zcOsWLC4mCaqKdYK1X/D1YTrlN68de/s51byPqoIImUnde700Qa8HoIgIIRT8OFqWeRWMrq8j794HHj1YQuQA1XSNxkCWKSJK26YVqgqdfuHnz2WZV0EfPrz+TE+fIl+/oqurDu/XMGYLkU2c62MtwJQs28aYj1TVoQwGQVdWkONj/gL3ho+XUT2DTgAAAABJRU5ErkJggg=='
  })
});
iconFeature.setStyle(iconStyle);
var vectorSource = new ol.source.Vector({
  features: [iconFeature]
});
var vectorLayer = new ol.layer.Vector({
  source: vectorSource
});
//Create an overlay layer
var element = $('<div class="element" >' +
    '<div class="title"><h3>Kdo FU Waffenplätze</h3></div>' +
    '<div class="undertitle">' +
      '<br>Kaserne Auenfeld<br>' +
      '<div class="middle">' +
        '<br>8500 Frauenfeld<br>' +
      '</div>' +
    '</div>' +
    '<div class="close">' +
      '<div type="button" onclick="window.toggle()">X</div>' +
    '</div>' +
'</div>'
);
var popup = new ol.Overlay({

```

--------------------------------

### GeoAdmin API Help and Support

Source: https://api3.geo.admin.ch/_sources/api/faq/index.rst

Information on where to find help and support for using the map.geo.admin.ch platform. Includes a link to the dedicated help pages.

```APIDOC
Help Pages:
  URL: http://help.geo.admin.ch/
```

--------------------------------

### GeoAdmin API Development Testing

Source: https://api3.geo.admin.ch/_sources/api/faq/index.rst

Guidance on using 'localhost' for development testing of the GeoAdmin API. Emphasizes adherence to the platform's Terms of Use.

```APIDOC
Localhost Testing:
  Allowed for development testing.
  Terms of Use: https://www.geo.admin.ch/terms-of-use
```

--------------------------------

### Reverse Geocoding and Identify API Calls

Source: https://api3.geo.admin.ch/services/sdiservices

Examples of performing identify requests to find features intersecting specific geometries (envelope, point) and for reverse geocoding addresses. These examples demonstrate the use of parameters like geometryType, geometry, and layers.

```APIDOC
https://api3.geo.admin.ch/rest/services/api/MapServer/identify?geometryType=esriGeometryEnvelope&geometry=548945.5,147956,549402,148103.5&imageDisplay=0,0,0&mapExtent=0,0,0,0&tolerance=0&layers=all:ch.swisstopo.swissboundaries3d-bezirk-flaeche.fill&returnGeometry=false
```

```APIDOC
https://api3.geo.admin.ch/rest/services/api/MapServer/identify?geometryType=esriGeometryPoint&geometry=548945.5,147956&imageDisplay=0,0,0&mapExtent=0,0,0,0&tolerance=0&layers=all:ch.swisstopo.swissboundaries3d-gemeinde-flaeche.fill,ch.swisstopo-vd.ortschaftenverzeichnis_plz&returnGeometry=false
```

```APIDOC
https://api3.geo.admin.ch/rest/services/api/MapServer/identify?mapExtent=0,0,100,100&imageDisplay=100,100,100&tolerance=1&geometryType=esriGeometryPoint&geometry=600968.625,197426.921875&layers=all:ch.bfs.gebaeude_wohnungs_register&returnGeometry=false
```

--------------------------------

### Cache Update API

Source: https://api3.geo.admin.ch/services/sdiservices

This service allows for updating the cache. It specifies the URL for cache update operations and provides an example.

```APIDOC
Cache Update API:

URL:
(Not explicitly provided in snippet, but implied by context)

Example:
- (Usage example for cache update)
```

--------------------------------

### Supported Projections API

Source: https://api3.geo.admin.ch/services/sdiservices

Information regarding the spatial reference systems supported by the GeoAdmin API. Includes examples of their usage.

```APIDOC
Supported Projections API:

- Example: Demonstrates the usage of supported projections.
```

--------------------------------

### Get Layer Legend API

Source: https://api3.geo.admin.ch/_sources/services/sdiservices.rst

Retrieves the legend for a specified layer using its ID. Supports language selection and JSONP callbacks.

```APIDOC
GET https://api3.geo.admin.ch/rest/services/api/MapServer/{layerBodId}/legend

Description:
  This service retrieves a legend for a given layer ID.

Parameters:
  - layerBodId (path parameter, required): The technical name or ID of the layer.
  - lang (query parameter, optional): The language for the legend. Supported values: de, fr, it, rm, en. Defaults to 'de' if browser language is not supported.
  - callback (query parameter, optional): The name of the callback function for JSONP responses.

Example:
  - Get legend for ch.bafu.nabelstationen:
    https://api3.geo.admin.ch/rest/services/api/MapServer/ch.bafu.nabelstationen/legend
  - Get legend using JSONP:
    https://api3.geo.admin.ch/rest/services/api/MapServer/ch.bafu.nabelstationen/legend?callback=callback
```

--------------------------------

### Access Solar Energy Suitability of Facades Layer

Source: https://api3.geo.admin.ch/releasenotes/index

Provides access to the 'Solarenergie: Eignung Fassaden' (Solar energy: Suitability of Facades) geodata layer. This layer evaluates the potential for solar energy generation on building facades, managed by the Swiss Federal Office of Energy (BFE).

```APIDOC
GET //map.geo.admin.ch/?layers=ch.bfe.solarenergie-eignung-fassaden

Description: Displays the solar energy suitability of building facades.
Parameters:
  layers: The identifier for the geodata layer (ch.bfe.solarenergie-eignung-fassaden).
Returns: A map view with the specified layer activated.
```

--------------------------------

### 3D Terrain and Hillshade Layers

Source: https://api3.geo.admin.ch/releasenotes/index

Provides access to 3D terrain models and hillshade visualizations from swissSURFACE3D, including monodirectional and multidirectional lighting.

```URL
https://map.geo.admin.ch/?layers=ch.swisstopo.swisssurface3d-reliefschattierung_monodirektional
```

```URL
https://map.geo.admin.ch/?layers=ch.swisstopo.swisssurface3d-reliefschattierung-multidirektional
```

--------------------------------

### Terrain Service API

Source: https://api3.geo.admin.ch/services/sdiservices

Provides access to terrain data, including a metadata service and parameters for querying terrain information. An example of usage is also included.

```APIDOC
Terrain Service API:

URL:
(Not explicitly provided in snippet, but implied by context)

Metadata Service:
- (Details about the terrain metadata service)

Parameters:
- (Parameters for terrain queries)

Example:
- (Usage example for the Terrain Service)
```

--------------------------------

### XYZ API

Source: https://api3.geo.admin.ch/services/sdiservices

Provides access to map tiles using the XYZ tiling scheme. Supports GetTile requests and includes information on supported projections and examples.

```APIDOC
XYZ API:

- GetTile: Retrieves map tiles using the XYZ scheme.
- Result: Describes the output of GetTile requests.
- Supported projections: Lists the spatial reference systems compatible with XYZ tiles.
- Example: Demonstrates XYZ tile usage.
```

--------------------------------

### Get Layer Legend

Source: https://api3.geo.admin.ch/services/sdiservices

Retrieves the legend information for a specified layer. This service allows fetching visual representations of layer data, supporting custom styling.

```APIDOC
GET https://api3.geo.admin.ch/rest/services/api/MapServer/{layerBodId}/legend

Parameters:
  - lang (optional): The language for the response. Supported values: de, fr, it, rm, en. Defaults to 'de' if browser language does not match.
  - callback (optional): The name of the callback function for JSONP responses.

Examples:
GET https://api3.geo.admin.ch/rest/services/api/MapServer/ch.bafu.nabelstationen/legend
GET https://api3.geo.admin.ch/rest/services/api/MapServer/ch.bafu.nabelstationen/legend?callback=callback
```

--------------------------------

### Release Information and API Access

Source: https://api3.geo.admin.ch/releasenotes/index

Provides context for a specific release (20220518) and indicates the availability of API and application-related information.

```APIDOC
ReleaseInfo:
  version: "20220518"
  date: "Wednesday, Mai 18th 2022"
  notes: "Includes API & applications information."

API_Access:
  description: Information regarding the availability of APIs and applications related to the geodata services.
  details: Refer to the 'API & applications' section for specific details on accessing services programmatically or through applications.
```

--------------------------------

### 3D Tiles API

Source: https://api3.geo.admin.ch/services/sdiservices

This service provides access to 3D Tiles data, including a metadata service and examples of usage. It specifies the URL for accessing 3D Tiles resources.

```APIDOC
3D Tiles API:

URL:
(Not explicitly provided in snippet, but implied by context)

Metadata Service:
- (Details about the 3D Tiles metadata service)

Example:
- (Usage example for 3D Tiles)
```

--------------------------------

### Access Solar Energy Suitability of Roofs Layer

Source: https://api3.geo.admin.ch/releasenotes/index

Provides access to the 'Solar energy: suitability of roofs' geodata layer. This layer assesses and visualizes the potential for solar energy generation on building roofs, managed by the Swiss Federal Office of Energy (BFE).

```APIDOC
GET //map.geo.admin.ch/?layers=ch.bfe.solarenergie-eignung-daecher

Description: Displays the solar energy suitability of roofs.
Parameters:
  layers: The identifier for the geodata layer (ch.bfe.solarenergie-eignung-daecher).
Returns: A map view with the specified layer activated.
```

--------------------------------

### Get Layer Attributes

Source: https://api3.geo.admin.ch/services/sdiservices

Retrieves attribute names specific to a given layer. This service is useful for understanding the data structure of a layer, especially when combined with the find service.

```APIDOC
GET https://api3.geo.admin.ch/rest/services/api/MapServer/{layerBodId}

Parameters:
  - lang (optional): The language for the response. Supported values: de, fr, it, rm, en. Defaults to 'de' if browser language does not match.
  - callback (optional): The name of the callback function for JSONP responses.

Example:
GET https://api3.geo.admin.ch/rest/services/api/MapServer/ch.swisstopo.swissboundaries3d-gemeinde-flaeche.fill
```

--------------------------------

### Find API

Source: https://api3.geo.admin.ch/services/sdiservices

The Find API enables searching for specific data within the GeoAdmin system. It accepts input parameters to refine search queries and provides examples of usage.

```APIDOC
Find API:

URL:
(Not explicitly provided in snippet, but implied by context)

Input Parameters:
- (Parameters for search queries)

Examples:
- (Usage examples for the Find API)
```

--------------------------------

### Accessibility of restaurants Layer

Source: https://api3.geo.admin.ch/releasenotes/index

Shows the accessibility of restaurants across Switzerland, provided by the Federal Statistical Office (FSO). This is a new layer.

```URL
//map.geo.admin.ch/?layers=ch.bfs.erreichbarkeit-restaurants
```