Documentation for Test, Monitor, and Visualize Geospatial APIs 1.0.0

This is documentation for Test, Monitor, and Visualize Geospatial APIs 1.0.0, which is no longer actively maintained.

For up-to-date documentation, see the latest version (1.1.0).

Version: 1.0.0

Detecting Your Context

When you open the Quetzly popup on an ArcGIS REST page, the extension automatically detects what type of endpoint you are on:

Context Example URL Description
Services Root .../rest/services The top-level directory
Folder .../rest/services/Planning A subfolder of services
Service .../rest/services/Planning/Parcels/MapServer An individual service
Layer .../rest/services/.../MapServer/0 A specific layer

Running a Validation

  1. Navigate to any ArcGIS REST endpoint in Chrome
  2. Click the Quetzly icon in your toolbar
  3. The popup will show the detected context (e.g. Service: Parcels (MapServer))
  4. Click Validate Service
  5. A spinner appears while checks run
  6. Results are injected directly onto the ArcGIS REST page as icons

Reading Results

After checks complete, colored icons appear next to each service and layer:

Icon Meaning
🟢 All assertions passed
⚠️ One or more assertions failed
🔴 All assertions failed
⬜ Service type not supported

Hover over any icon to see a full breakdown of what passed and what failed.

What Gets Checked?

MapServer

  • Service reachability (HTTP 200)
  • Valid spatial extent (not 0,0,0,0)
  • Layer count > 0
  • Export map operation works
  • Spatial reference defined

FeatureServer

  • Service reachability
  • Layer and table count
  • Feature count per layer (via layerDefs query)
  • Capabilities defined

ImageServer

  • Service reachability
  • Valid spatial extent
  • Pixel size > 0
  • Band count > 0
  • Spatial reference defined

GPServer

  • Only checks Service reachability (HTTP 200)
  • For customization of request use the desktop app

Layer level Assertions

  • Fields names exist
  • Record count > 0