# info.title
CShapes Dataset of Historical Country Boundaries

# info.description
The CShapes 2.0 dataset maps the borders and capitals of independent states and dependent territories from 1886 to 2019. There are two versions of the dataset, which are based on the Gleditsch and Ward (1999) or the Correlates of War coding of independent states. Border changes were coded based on the Territorial Change Dataset by Tir et al (1998), the Encyclopedia of International Boundaries by Biger (1995) and the Encyclopedia of African Boundaries by Brownlie (1979).

_Note: This API is based on API building blocks (e.g., operations, query parameters, or headers) specified in OGC API Standards or drafts of those standards. For more information about OGC API Standards, see [https://ogcapi.ogc.org](https://ogcapi.ogc.org/). Some building blocks of this API can be preliminary and may change in this API, because they are not yet based on a stable specification. The maturity is stated for each building block._

# info.contact.name
Clemens Portele, interactive instruments GmbH

# paths./.get.description
The landing page provides links to the API definition (link relations `service-desc` and `service-doc`), the Conformance declaration (path `/conformance`, link relation `conformance`), and other resources in the API.

_Maturity: `STABLE`_

# paths./.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./.get.responses.200.description
The operation was executed successfully.

# paths./mcp/schema.get.description
Check the generated MCP definitions.

_Maturity: `PRELIMINARY` (the operation may change in this API)_

# paths./mcp/schema.get.responses.200.description
The operation was executed successfully.

# paths./conformance.get.description
The URIs of all conformance classes supported by the server. This information is provided to support 'generic' clients that want to access multiple OGC API implementations - and not 'just' a specific API. For clients accessing only a single API, this information is in general not relevant and the OpenAPI definition details the required information about the API.

_Maturity: `STABLE`_

# paths./conformance.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./conformance.get.responses.200.description
The operation was executed successfully.

# paths./mcp.post.description
Can be added to AI tools as connector.

_Maturity: `PRELIMINARY` (the operation may change in this API)_

# paths./mcp.post.responses.200.description
The operation was executed successfully.

# paths./collections.get.summary
feature collections in the dataset 'CShapes Dataset of Historical Country Boundaries'

# paths./collections.get.description
The dataset is organized in feature collections. This resource provides information about and access to the feature collections.
The response contains the list of collections. For each collection, a link to the items in the collection (path `/collections/{collectionId}/items`, link relation `items`) as well as key information about the collection.
This information includes:

* A local identifier for the collection that is unique for the dataset;
* A title and description for the collection;
* An indication of the spatial and temporal extent of the data in the collection;
* A list of coordinate reference systems (CRS) in which geometries may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
* The CRS in which the spatial geometries are stored in the data source (if data is requested in this CRS, the geometries are returned without any coordinate conversion);
* An indicator about the type of the items in the collection (the default value is 'feature').

_Maturity: `STABLE`_

# paths./collections.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./collections.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary.get.description
Information about the feature collection with id 'boundary'. The response contains a link to the items in the collection (path `/collections/{collectionId}/items`,link relation `items`) as well as key information about the collection. This information includes:

* A local identifier for the collection that is unique for the dataset;
* A title and description for the collection;
* An indication of the spatial and temporal extent of the data in the collection;
* A list of coordinate reference systems (CRS) in which geometries may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
* The CRS in which the spatial geometries are stored in the data source (if data is requested in this CRS, the geometries are returned without any coordinate conversion);
* An indicator about the type of the items in the collection (the default value is 'feature').

_Maturity: `STABLE`_

# paths./collections/boundary.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./collections/boundary.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary/items.get.summary
retrieve features in the feature collection 'boundary'

# paths./collections/boundary/items.get.description
The response is a document consisting of features in the collection. The features included in the response are determined by the server based on the query parameters of the request.

To support access to larger collections without overloading the client, the API supports paged access with links to the next page, if more features are selected that the page size (maximum page size is 100000).

The `bbox` and `datetime` parameter can be used to select only a subset of the features in the collection (the features that are in the bounding box or time interval). The `bbox` parameter matches all features in the collection that are not associated with a location, too. The `datetime` parameter matches all features in the collection that are not associated with a time stamp or interval, too. The `limit` parameter may be used to control the subset of the selected features that should be returned in the response, the page size. Each page may include information about the number of selected and returned features (`numberMatched` and `numberReturned`) as well as links to support paging (link relation `next`).

See the details of this operation for a description of additional query parameters supported by this resource.

_Maturity: `STABLE`_

# paths./collections/boundary/items.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./collections/boundary/items.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary/items/{featureId}.get.summary
retrieve a feature in the feature collection 'boundary'

# paths./collections/boundary/items/{featureId}.get.description
Fetch the feature with id `{featureId}`.

_Maturity: `STABLE`_

# paths./collections/boundary/items/{featureId}.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 1: Core

# paths./collections/boundary/items/{featureId}.get.responses.200.description
The operation was executed successfully.

# paths./search.get.description
This operation fetches the set of stored queries available in this API. For each stored query the id, a title, the description, information about any parameters, and links to the sub-resources are provided.

_Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)_

# paths./search.get.externalDocs.description
The specification that describes this operation: Testbed-18: Filtering Service and Rule Set Engineering Report (PREDRAFT)

# paths./search.get.responses.200.description
The operation was executed successfully.

# paths./search.post.description
An ad-hoc query expression is expressed as a JSON object. The query expression object can describe a single query (the properties "collections", "filter", "properties" and "sortby" are members of the query expression object) or multiple queries (a "queries" member with an array of query objects is present) in a single request.
For each query:

The value of "collection" is an array with one item, the identifier of the collection to query.
The value of "filter" is a CQL2 JSON filter expression.
The value of "properties" is an array with the names of properties to include in the response.
The value of "sortby" is used to sort the features in the response.

For multiple queries:

If multiple queries are specified, the results are concatenated. The response is a single feature collection. The feature ids in the response to a multi-collection query must be unique. Since the identifier of a feature only has to be unique per collection, they need to be combined with the collection identifier. A concatenation with "." as the joining character is used (e.g., "apronelement.123456").
The direct members "filter" and "properties" represent "global" constraints that must be combined with the corresponding member in each query. The global and local property selection list are concatenated and then the global and local filters are combined using the logical operator specified by the "filterOperator" member.
The global member "filter" must only reference queryables that are common to all collections being queried.
The global member "properties" must only reference presentables that are common to all collections being queried.

General remarks:

A "title" and "description" for the query expression can be added. Providing both is strongly recommended to explain the query to users.
The "limit" member applies to the entire result set.
"sortby" will only apply per query. A global "sortby" would require that the results of all queries are compiled first and then the combined result set is sorted. This would not support "streaming" the response.
In case of a parameterized stored query, the query expression may contain JSON objects with a member "$parameter". The value of "$parameter" is an object with a member where the key is the parameter name and the value is a JSON schema describing the parameter. When executing the stored query, all objects with a "$parameter" member are replaced with the value of the parameter for this query execution. Comma-separated parameter values are converted to an array, if the parameter is of type "array".
Parameters may also be provided in a member "parameters" in the query expression and referenced using "$ref".
_Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)_

# paths./search.post.externalDocs.description
The specification that describes this operation: Testbed-18: Filtering Service and Rule Set Engineering Report (PREDRAFT)

# paths./search/countries-over-time.get.summary
execute stored query Query the boundaries or the area of countries over time

# paths./search/countries-over-time.get.description
This query returns either the boundary geometry (geometry) or the area in square kilometers of one or more countries (area_km2) over time with the county name (name), the name of the captial (capname) and the Gleditsch and Ward code (gwcode) for each time period. The start and end date of the time period for which the data is valid is also returned (gwsdate and gwedate).

_Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)_

# paths./search/countries-over-time.get.externalDocs.description
The specification that describes this operation: Testbed-18: Filtering Service and Rule Set Engineering Report (PREDRAFT)

# paths./search/countries-over-time.get.responses.200.description
The operation was executed successfully.

# paths./search/{queryId}/parameters.get.summary
fetch parameters of stored query {queryId}

# paths./search/{queryId}/parameters.get.description
Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)

# paths./search/{queryId}/parameters.get.externalDocs.description
The specification that describes this operation: Testbed-18: Filtering Service and Rule Set Engineering Report (PREDRAFT)

# paths./search/{queryId}/parameters.get.responses.200.description
The operation was executed successfully.

# paths./search/{queryId}/parameters/{name}.get.summary
fetch parameter with name {name} of stored query {queryId}

# paths./search/{queryId}/parameters/{name}.get.description
Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)

# paths./search/{queryId}/parameters/{name}.get.externalDocs.description
The specification that describes this operation: Testbed-18: Filtering Service and Rule Set Engineering Report (PREDRAFT)

# paths./search/{queryId}/parameters/{name}.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary/queryables.get.summary
retrieve the queryables of the feature collection 'boundary'

# paths./collections/boundary/queryables.get.description
The Queryables resources identifies the properties that can be referenced in filter expressions to select specific features that meet the criteria identified in the filter. The response is a JSON Schema document that describes a single JSON object where each property is a queryable.

Note: The queryables schema does not specify a schema of any object that can be retrieved from the API.

The descriptive metadata (title and description of the property) as well as the schema information (data type and constraints like a list of allowed values or minimum/maxmimum values are provided to support clients to constructmeaningful queries for the data.

_Maturity: `STABLE`_

# paths./collections/boundary/queryables.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 3: Filtering

# paths./collections/boundary/queryables.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary/sortables.get.summary
retrieve the sortables of the feature collection 'boundary'

# paths./collections/boundary/sortables.get.description
The sortables resources identifies the properties that can bereferenced in the 'sortby' parameter to order the features of the collection in the response to a query.The response is returned as a JSON Schema document that describes a single JSON object where each property is a sortable.

Note that the sortables schema does not specify a schema of any object that can be retrieved from the API.

JSON Schema is used for the sortables to have a consistent approach for describing schema information and JSON Schema is/will be used in other parts of OGC API Features to describe schemas for GeoJSON feature content including in OpenAPI documents.

_Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)_

# paths./collections/boundary/sortables.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 8: Sorting (DRAFT)

# paths./collections/boundary/sortables.get.responses.200.description
The operation was executed successfully.

# paths./collections/boundary/schema.get.summary
retrieve the schema of features in the feature collection 'boundary'

# paths./collections/boundary/schema.get.description
Maturity: `PRELIMINARY` (specified in a draft standard; the operation may change in this API)

# paths./collections/boundary/schema.get.externalDocs.description
The specification that describes this operation: OGC API - Features - Part 5: Schemas (DRAFT)

# paths./collections/boundary/schema.get.responses.200.description
The operation was executed successfully.

# components.schemas.featureCollectionGeoJson_boundary.properties.timeStamp.description
This property indicates the time and date when the response was generated.

# components.schemas.featureCollectionGeoJson_boundary.properties.numberMatched.properties.numberReturned.description
The number of features in the feature collection.

A server may omit this information in a response, if the information about the number of features is not known or difficult to compute.

If the value is provided, the value shall be identical to the number of items in the "features" array.

# components.schemas.featureCollectionGeoJson_boundary.properties.numberMatched.description
The number of features of the feature type that match the selection parameters like `bbox`.

# components.schemas.featureGeoJson_boundary.properties.properties.properties.area.description
The polygon area in square kilometers, computed using an Eckert VI projection.

# components.schemas.featureGeoJson_boundary.properties.properties.properties.caplong.description
Longitude of the capital, in decimal degrees

# components.schemas.featureGeoJson_boundary.properties.properties.properties.caplat.description
Latitude of the capital, in decimal degrees

# components.schemas.featureGeoJson_boundary.properties.properties.properties.gwcode.description
Numeric identifier code in the source data.

# components.schemas.featureGeoJson_boundary.description
Core territories of the given country, excluding colonies and other dependent territories, between the start and end date.

# components.parameters.access_token.description
Set the authorization token for the request. If no value is provided, the standard HTTP rules apply, i.e., the authorization header will be used to determine the token.

_Maturity: `STABLE`_

# components.parameters.fCommon.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `STABLE`_

# components.parameters.prettyCommon.description
Controls whether the response content should be pretty-printed. Only applicable for JSON responses.

# components.parameters.fCollections.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `STABLE`_

# components.parameters.fCollection.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `STABLE`_

# components.parameters.bbox.description
Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four numbers:

* Lower left corner, coordinate axis 1 
* Lower left corner, coordinate axis 2 
* Upper right corner, coordinate axis 1 
* Upper right corner, coordinate axis 2 
The coordinate reference system of the values is WGS 84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter `bbox-crs`. For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge).

_Maturity: `STABLE`_

# components.parameters.bbox.schema.description
Only features that have a geometry that intersects the bounding box are selected. The bounding box is provided as four numbers:

* Lower left corner, coordinate axis 1 
* Lower left corner, coordinate axis 2 
* Upper right corner, coordinate axis 1 
* Upper right corner, coordinate axis 2 
The coordinate reference system of the values is WGS 84 longitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate reference system is specified in the parameter `bbox-crs`. For WGS 84 longitude/latitude the values are in most cases the sequence of minimum longitude, minimum latitude, maximum longitude and maximum latitude. However, in cases where the box spans the antimeridian the first value (west-most box edge) is larger than the third value (east-most box edge).

# components.parameters.bbox-crsFeatures_boundary.description
The coordinate reference system of the `bbox` parameter. Default is WGS84 longitude/latitude.

_Maturity: `STABLE`_

# components.parameters.crsFeatures_boundary.description
The coordinate reference system of the response geometries. Default is WGS84 longitude/latitude (with or without height). The parameter is ignored for HTML output as the HTML representation only supports the default coordinate reference system.

_Maturity: `STABLE`_

# components.parameters.datetime.description
Either a date-time or an interval. Date and time expressions adhere to RFC 3339.
Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

* A date-time: "2018-02-12T23:20:50Z"
* A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
* Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have a temporal property that intersects the value of `datetime` are selected.

_Maturity: `STABLE`_

# components.parameters.datetime.schema.description
Either a date-time or an interval. Date and time expressions adhere to RFC 3339.
Intervals may be bounded or half-bounded (double-dots at start or end).
Examples:

* A date-time: "2018-02-12T23:20:50Z"
* A bounded interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
* Half-bounded intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have a temporal property that intersects the value of `datetime` are selected.

# components.parameters.exclude-properties_boundary.description
The properties that should be excluded for each feature. The parameter value is a comma-separated list of property names. By default, all feature properties with a value are returned. The parameter must not be used together with the 'properties' parameter.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.exclude-properties_boundary.schema.description
The properties that should be excluded for each feature. The parameter value is a comma-separated list of property names. By default, all feature properties with a value are returned. The parameter must not be used together with the 'properties' parameter.

# components.parameters.fFeatures.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `STABLE`_

# components.parameters.filter.description
Filter features in the collection using the query expression in the parameter value. Filter expressions are written in the [Common Query Language (CQL2)](https://docs.ogc.org/is/21-065r2/21-065r2.html), which is an OGC Standard.

The recommended language for this query parameter is CQL2 Text (`filter-lang=cql2-text`).

CQL2 Text expressions are similar to SQL expressions and also support spatial, temporal and array predicates. All property references must be queryables of the collection and must be declared in the Queryables sub-resource of the collection.

The following are examples of CQL Text expressions:

* Logical operators (`AND`, `OR`, `NOT`) are supported
* Simple comparison predicates (`=`, `<>`, `<`, `>`, `<=`, `>=`):
  * `address.LocalityName = 'Bonn'`
  * `measuredHeight > 10`
  * `storeysAboveGround <= 4`
  * `creationDate > DATE('2017-12-31')`
  * `creationDate < DATE('2018-01-01')`
  * `creationDate >= DATE('2018-01-01') AND creationDate <= DATE('2018-12-31')`
* Advanced comparison operators (`LIKE`, `BETWEEN`, `IN`, `IS NULL`):
  * `name LIKE '%Kirche%'`
  * `measuredHeight BETWEEN 10 AND 20`
  * `address.LocalityName IN ('Bonn', 'Köln', 'Düren')`
  * `address.LocalityName NOT IN ('Bonn', 'Köln', 'Düren')`
  * `name IS NULL`
  * `name IS NOT NULL`
* Spatial operators (the standard Simple Feature operators, e.g., `S_INTERSECTS`, `S_WITHIN`):
  * `S_INTERSECTS(bbox, POLYGON((8 52, 9 52, 9 53, 8 53, 8 52)))`
* Temporal operators (e.g., `T_AFTER`, `T_BEFORE`, `T_INTERSECTS`)
  * `T_AFTER(creationDate, DATE('2018-01-01'))`
  * `T_BEFORE(creationDate, DATE('2018-01-01'))`
  * `T_INTERSECTS(creationDate, INTERVAL('2018-01-01','2018-12-31'))`
  * `T_INTERSECTS(INTERVAL(begin,end), INTERVAL('2018-01-01','2018-12-31'))`

_Maturity: `STABLE`_

# components.parameters.filter-crs.description
Specify which of the supported CRSs to use to encode geometric values in a filter expression (parameter 'filter'). Default is WGS84 longitude/latitude.

_Maturity: `STABLE`_

# components.parameters.filter-lang.description
Language of the query expression in the 'filter' parameter. Supported are 'cql2-text' (default) and 'cql2-json', specified in the [OGC Standard 'Common Query Language (CQL2)'](https://docs.ogc.org/is/21-065r2/21-065r2.html). 'cql2-text' is an SQL-like text encoding for filter expressions that also supports spatial, temporal and array predicates. 'cql2-json' is a JSON encoding of that grammar, suitable for use as part of a JSON object that represents a query. The use of 'cql2-text' is recommended for filter expressions in the 'filter' parameter.

_Maturity: `STABLE`_

# components.parameters.limitFeatures_boundary.description
The optional limit parameter limits the number of items that are presented in the response document. If more items are selected, only the number of items as specified with the limit parameter are included in the response document. That is, the results is provided in pages ('paging'). Only items are counted that are on the first level of the collection in the response document. Nested objects contained within the explicitly requested items are not counted. If the value is higher than the maximum value, the maximum value is used instead of the parameter value.
If no parameter value is provided, the default value applies. If more items are available, a link to the next page with more results is provided with the response (link relation type: 'next'). To avoid receiving the result in pages, try to set the limit parameter to the maximum value.

_Maturity: `STABLE`_

# components.parameters.limitFeatures_boundary.schema.description
The optional limit parameter limits the number of items that are presented in the response document. If more items are selected, only the number of items as specified with the limit parameter are included in the response document. That is, the results is provided in pages ('paging'). Only items are counted that are on the first level of the collection in the response document. Nested objects contained within the explicitly requested items are not counted. If the value is higher than the maximum value, the maximum value is used instead of the parameter value.
If no parameter value is provided, the default value applies. If more items are available, a link to the next page with more results is provided with the response (link relation type: 'next'). To avoid receiving the result in pages, try to set the limit parameter to the maximum value.

# components.parameters.maxAllowableOffset.description
This option can be used to specify the maxAllowableOffset to be used for simplifying the geometries in the response. The maxAllowableOffset is in the units of the response coordinate reference system.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.offsetFeatures.description
The optional offset parameter identifies the index of the first feature in the response in the overall result set.

_Maturity: `STABLE`_

# components.parameters.offsetFeatures.schema.description
The optional offset parameter identifies the index of the first feature in the response in the overall result set.

# components.parameters.prettyFeatures.description
Controls whether the response content should be pretty-printed. Only applicable for JSON responses.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.profileFeatures_boundary.description
Select the profiles to be used in the response. If no value is provided, the default profiles will be used.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.properties_boundary.description
The properties that should be included for each feature. The parameter value is a comma-separated list of property names. By default, all feature properties with a value are returned.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.properties_boundary.schema.description
The properties that should be included for each feature. The parameter value is a comma-separated list of property names. By default, all feature properties with a value are returned.

# components.parameters.q.description
General text search in multiple text properties of the data. Separate search terms by comma.If at least one of the search terms is included in an item, it is included in the result set.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.resultTypeFeatures.description
One of `hits` and `items`. `items` returns the features, `hits` returns no features, but only the information about the number features matched by the request. For feature formats that do not support returning the number of matched features, `hits` will be rejected. `hitsOnly` is a deprecated alias for `hits`.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.skipGeometry_boundary.description
Use this option to exclude geometries from the response for each feature.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.sortby_boundary.description
Sort the results based on the properties identified by this parameter. The parameter value is a comma-separated list of property names that can be used to sort results (sortables), where each parameter name may be preceeded by a '+' (ascending, default) or '-' (descending).

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.sortby_boundary.schema.description
Sort the results based on the properties identified by this parameter. The parameter value is a comma-separated list of property names that can be used to sort results (sortables), where each parameter name may be preceeded by a '+' (ascending, default) or '-' (descending).

# components.parameters.zoom-level.description
This option can be used to simplify geometries for the zoom level from the widely used tiling scheme in web mapping (WebMercatorQuad). The map scale of zoom level 0 is roughly 1:560 million. The scale doubles for every zoom level (e.g. zoom level 12 is 1:136495).

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.name_boundary.description
Filter the collection by property 'name' (Country name).

_Maturity: `STABLE`_

# components.parameters.name_boundary.schema.description
Filter the collection by property 'name' (Country name).

# components.parameters.area_boundary.description
Filter the collection by property 'area' (Area (km²)): The polygon area in square kilometers, computed using an Eckert VI projection.

_Maturity: `STABLE`_

# components.parameters.area_boundary.schema.description
Filter the collection by property 'area' (Area (km²)): The polygon area in square kilometers, computed using an Eckert VI projection.

# components.parameters.capname_boundary.description
Filter the collection by property 'capname' (Country capital): The name of the country capital.

_Maturity: `STABLE`_

# components.parameters.capname_boundary.schema.description
Filter the collection by property 'capname' (Country capital): The name of the country capital.

# components.parameters.gwsdate_boundary.description
Filter the collection by property 'gwsdate' (Start date): Start date of the entry.

_Maturity: `STABLE`_

# components.parameters.gwsdate_boundary.schema.description
Filter the collection by property 'gwsdate' (Start date): Start date of the entry.

# components.parameters.gwedate_boundary.description
Filter the collection by property 'gwedate' (End date): End date of the entry.

_Maturity: `STABLE`_

# components.parameters.gwedate_boundary.schema.description
Filter the collection by property 'gwedate' (End date): End date of the entry.

# components.parameters.gwcode_boundary.description
Filter the collection by property 'gwcode' (Source identifier): Numeric identifier code in the source data.

_Maturity: `STABLE`_

# components.parameters.gwcode_boundary.schema.description
Filter the collection by property 'gwcode' (Source identifier): Numeric identifier code in the source data.

# components.parameters.featureId.description
The local identifier of a feature, unique within the feature collection.

_Maturity: `STABLE`_

# components.parameters.fStoredQueries.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.fAdHocQuery.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.LinkInRequest.description
Links associated with the payload of the request. See RFC 8288 for the syntax.

_Maturity: `STABLE`_

# components.parameters.fStoredQuery.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.offsetStoredQuery.description
The optional offset parameter identifies the index of the first feature in the response in the overall result set.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.area_or_geometry_countries-over-time.description
area_or_geometryArea or Boundary Geometry: Choose whether to return the area in square kilometers (area) or the boundary geometry (geometry) of the selected countries.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.area_or_geometry_countries-over-time.schema.description
Choose whether to return the area in square kilometers (area) or the boundary geometry (geometry) of the selected countries.

# components.parameters.name_countries-over-time.description
nameCountry Names: The exact names of countries. Pick multiple names, if the name of a county changed over time.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.name_countries-over-time.schema.description
The exact names of countries. Pick multiple names, if the name of a county changed over time.

# components.parameters.name_countries-over-time.schema.items.enum[]
New Guinea (German New Guinea) (Kaiser Wilhelmsland)

# components.parameters.queryId.description
The local identifier of a stored query, unique within the API.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.name.description
The name of a parameter of a stored query.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.fQueryables.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.profileQueryables_boundary.description
Select the profiles to be used in the response. If no value is provided, the default profiles will be used.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.fSortables.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.profileSortables_boundary.description
Select the profiles to be used in the response. If no value is provided, the default profiles will be used.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.parameters.fSchema.description
Select the output format of the response. If no value is provided, the standard HTTP rules apply, i.e., the accept header will be used to determine the format.

_Maturity: `PRELIMINARY` (the parameter may change in this API)_

# components.parameters.profileSchema_boundary.description
Select the profiles to be used in the response. If no value is provided, the default profiles will be used.

_Maturity: `PRELIMINARY` (specified in a draft standard; the parameter may change in this API)_

# components.headers.Content-Bounding-Box.description
The bounding box of the coordinates in the response. The coordinates are in the coordinate reference system provided in the 'Content-Crs' header. The header is only provided, if the response is not streamed.

_Maturity: `PRELIMINARY` (the header may change in this API)_

# components.headers.ContentCrsFeatures.description
The coordinate reference system of coordinates in the response.

_Maturity: `STABLE`_

# components.headers.Content-Temporal-Extent.description
The temporal extent of the features in the response. The values are seconds since epoch. The header is only provided, if the response is not streamed.

_Maturity: `PRELIMINARY` (the header may change in this API)_

# components.headers.LinkInResponse.description
Links associated with the resource in the response. See RFC 8288 for the syntax.

_Maturity: `STABLE`_