Zartico

Zartico GeoServer OGC Web Services

Zartico operates a public, anonymously readable GeoServer instance at geoserver.zartico.com serving OGC Web Services over its destination geospatial estate. The WMS 1.3.0 capabilities document advertises 34 named layers across two workspaces (zartographer and regions_app) - client boundary polygons, client regions, census tracts, county subdivisions, incorporated places, ZCTA boundaries, state and county boundaries, synthetic cities and point-of-interest layers - with GetCapabilities, GetMap and GetFeatureInfo, eleven output image formats and 7,957 supported CRS codes. The WFS 2.0.0 capabilities document advertises 27 feature types and eleven operations including Transaction, LockFeature, GetPropertyValue and stored queries, with GeoJSON, GML 3.2 and KML output, result paging and a CountDefault of 1,000,000. A WCS 2.0.1 endpoint answers GetCapabilities but currently advertises zero coverages. The service declares Fees "none" and AccessConstraints "none". This is a self-describing OGC contract, not an OpenAPI - the GetCapabilities documents ARE the machine-readable interface.

GitHub

Other Resources

🔗
GetCapabilities
https://raw.githubusercontent.com/api-evangelist/zartico/refs/heads/main/openapi/zartico-geoserver-wms-capabilities.xml
🔗
GetCapabilities
https://raw.githubusercontent.com/api-evangelist/zartico/refs/heads/main/openapi/zartico-geoserver-wfs-capabilities.xml
🔗
GetCapabilities
https://raw.githubusercontent.com/api-evangelist/zartico/refs/heads/main/openapi/zartico-geoserver-wcs-capabilities.xml
🔗
WMS
https://geoserver.zartico.com/geoserver/ows?service=WMS&version=1.3.0&request=GetCapabilities
🔗
WFS
https://geoserver.zartico.com/geoserver/ows?service=WFS&version=2.0.0&request=GetCapabilities
🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/zartico/refs/heads/main/conformance/zartico-conformance.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/zartico/refs/heads/main/apis.yml

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.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/zartico-geoserver"
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 email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: zartico-geoserver
name: Zartico GeoServer OGC Web Services
description: Zartico operates a public, anonymously readable GeoServer instance at geoserver.zartico.com
  serving OGC Web Services over its destination geospatial estate. The WMS 1.3.0 capabilities document
  advertises 34 named layers across two workspaces (zartographer and regions_app) - client boundary polygons,
  client regions, census tracts, county subdivisions, incorporated places, ZCTA boundaries, state and
  county boundaries, synthetic cities and point-of-interest layers - with GetCapabilities, GetMap and
  GetFeatureInfo, eleven output image formats and 7,957 supported CRS codes. The WFS 2.0.0 capabilities
  document advertises 27 feature types and eleven operations including Transaction, LockFeature, GetPropertyValue
  and stored queries, with GeoJSON, GML 3.2 and KML output, result paging and a CountDefault of 1,000,000.
  A WCS 2.0.1 endpoint answers GetCapabilities but currently advertises zero coverages. The service declares
  Fees "none" and AccessConstraints "none". This is a self-describing OGC contract, not an OpenAPI - the
  GetCapabilities documents ARE the machine-readable interface.
image: https://go.zartico.com/hubfs/zartico-logo-final_rgb-white-horizontal.png
humanURL: https://geoserver.zartico.com/geoserver/index.html
baseURL: https://geoserver.zartico.com/geoserver/ows
tags:
- Geospatial
- OGC
- WMS
- WFS
- WCS
- Maps
- Location Intelligence
properties:
- type: GetCapabilities
  url: openapi/zartico-geoserver-wms-capabilities.xml
- type: GetCapabilities
  url: openapi/zartico-geoserver-wfs-capabilities.xml
- type: GetCapabilities
  url: openapi/zartico-geoserver-wcs-capabilities.xml
- type: WMS
  url: https://geoserver.zartico.com/geoserver/ows?service=WMS&version=1.3.0&request=GetCapabilities
- type: WFS
  url: https://geoserver.zartico.com/geoserver/ows?service=WFS&version=2.0.0&request=GetCapabilities
- type: Conformance
  url: conformance/zartico-conformance.yml