Open Geospatial Consortium (OGC) VectorTiles Collections API
The VectorTiles Collections API from Open Geospatial Consortium (OGC) — 1 operation(s) for vectortiles collections.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/ogc-vectortiles-collections-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
version: '1.0'
title: OGC API - Tiles VectorTiles Collections API
description: 'Example API Definition for OGC API - Tiles - Part 1: Core'
contact:
name: Open Geospatial Consortium
email: info@ogc.org
license:
name: OGC License
url: http://www.opengeospatial.org/legal/
servers:
- description: Example OGC API - Tiles server
url: https://maps.ecere.com/ogcapi
tags:
- name: VectorTiles Collections
paths:
/api/vectorTiles-collections:
get:
tags:
- VectorTiles Collections
operationId: getAPIVectorTileCollections
summary: Retrieve the list of collections supporting vector tiles available from this…
parameters:
- $ref: '#/components/parameters/f-metadata'
responses:
'200':
$ref: '#/components/responses/Enumeration'
'404':
$ref: '#/components/responses/NotFound'
'406':
$ref: '#/components/responses/NotAcceptable'
'500':
$ref: '#/components/responses/ServerError'
components:
parameters:
f-metadata:
name: f
in: query
description: The format of the response. If no value is provided, the accept header is used to determine the format. Accepted values are 'json' or 'html'.
required: false
schema:
type: string
enum:
- json
- html
style: form
explode: false
responses:
ServerError:
description: A server error occurred.
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
NotFound:
description: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
Enumeration:
description: An enumerated list of valid string values for API parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/enumeration'
text/html:
schema:
type: string
NotAcceptable:
description: Content negotiation failed. For example, the `Accept` header submitted in the request did not support any of the media types supported by the server for the requested resource.
content:
application/json:
schema:
$ref: '#/components/schemas/exception'
text/html:
schema:
type: string
schemas:
exception:
title: Exception Schema
description: JSON schema for exceptions based on RFC 7807
type: object
required:
- type
properties:
type:
type: string
title:
type: string
status:
type: integer
detail:
type: string
instance:
type: string
enumeration:
type: object
required:
- type
- enum
properties:
type:
type: string
enum:
- enum
enum:
type: array
items:
type: string