Quetzly

Product Introduction

1. Definition: Quetzly is a cloud-based geospatial API testing, monitoring, and visualization platform designed for technical teams. It falls under the technical categories of API development tools, GIS software, and IT operations monitoring solutions.
2. Core Value Proposition: Quetzly exists to streamline validation of location-based services by enabling developers and GIS professionals to test API endpoints, monitor service health, and visualize spatial data in real-time—reducing downtime and accelerating geospatial development workflows.

Main Features

1. Geospatial API Testing Suite:
   Quetzly allows sending HTTP requests (GET/POST/PUT/PATCH/DELETE) with adjustable headers/query parameters. Its integrated JSON editor validates responses, while built-in support for OGC standards (WMS/WFS) and ArcGIS services enables protocol-specific testing. The system parses geospatial metadata to identify malformed geometry or incorrect spatial references during validation.

2. Interactive Map Visualization Engine:
   Renders WMS, WFS, GeoJSON, and ArcGIS services on a Leaflet/OpenLayers-based map interface. Users toggle layers dynamically, zoom to feature extents, and inspect attribute tables. The engine converts rendered data to GeoJSON or Shapefile format for export, maintaining original coordinate reference systems (CRS) during data transformation.

3. Endpoint Health Monitoring:
   Continuously tracks API uptime/performance via configurable check intervals (e.g., 1-60 minutes). Monitors response codes, latency thresholds, and data integrity through automated geometry validation. Historical logs display downtime patterns on timeline graphs, with SLA compliance metrics calculated from captured performance data.

4. Quetzly Monitor (Beta):
   Enterprise-grade monitoring featuring multi-environment support (dev/staging/prod). Validates data quality through attribute schema checks and spatial reference verification. Performance tracking measures throughput/response times, while real-time alerts integrate with Slack/PagerDuty/webhooks. Custom health checks use user-defined thresholds for error rates.

Problems Solved

1. Pain Point: Eliminates manual validation of geospatial APIs by providing integrated testing/monitoring, preventing undetected data corruption (e.g., invalid polygons) and service outages that disrupt location-dependent applications.
2. Target Audience:
   • GIS Developers needing to debug WMS/WFS services
   • DevOps Engineers managing uptime for spatial APIs
   • Data Scientists requiring valid GeoJSON for analysis
   • SaaS Teams building location-based features
3. Use Cases:
   • Stress-testing ArcGIS Feature Services before production deployment
   • Validating coordinate systems in real-time during satellite data ingestion
   • Monitoring 24/7 uptime for emergency response mapping systems
   • Converting government WFS feeds to Shapefile for field operations

Unique Advantages

1. Differentiation: Unlike Postman (general API testing) or QGIS (desktop GIS), Quetzly combines protocol-aware geospatial validation, live map rendering, and endpoint monitoring in a unified web platform—removing context-switching between tools.
2. Key Innovation: Automated geometry validation during API checks detects topological errors (e.g., self-intersecting polygons) using computational geometry algorithms, while its export pipeline preserves topological relationships during format conversion.

Frequently Asked Questions (FAQ)

1. Does Quetzly support ArcGIS Online services?
   Yes, Quetzly natively integrates with ArcGIS Map Services and Feature Services, including authentication via tokens for secured endpoints.
2. How does Quetzly reduce geospatial API downtime?
   Its proactive monitoring identifies latency spikes or data schema changes before failures occur, with configurable alerts notifying teams via Slack/email within seconds of anomalies.
3. Can I test non-geospatial APIs with Quetzly?
   While optimized for spatial data, Quetzly handles any RESTful API with JSON/XML responses, though visualization features require GeoJSON or OGC-standard payloads.
4. What environments does Quetzly Monitor support?
   The monitoring module tracks separate configurations for development, staging, and production environments with isolated thresholds and alert rules.
5. Is coding required to use Quetzly?
   No-code setup for basic monitoring/visualization, but advanced testing supports JavaScript scripting for dynamic parameter generation in API requests.