Geospatial Viewer

Purpose & User Intent: The GS Viewer tool provides lightweight geospatial data visualization and basic spatial analytics. It solves the problem of quickly inspecting geospatial datasets, layers, and extents without deploying desktop GIS. Target users include GIS analysts, urban planners, researchers, and developers who need fast, shareable views during project scoping, data QA, or classroom demonstrations. When data is large or formats are varied, it prioritizes performance and clarity over full analytics.\n\nCore Logic & Features: Required features include dataset_source input (ID or URL), CRS specification, one or more layers, and an active viewport. Optional/advanced features include AOI clipping, reprojection, simple metrics (feature count, area, extent), export options (PNG, GeoJSON, WKT), and batch rendering. The system enforces data validity, checks CRS compatibility, and returns a structured result containing viewport metadata and export-ready artifacts.\n\nInputs & Outputs: Inputs include dataset_source (string, required), layers (array of strings, optional), crs (string, required, e.g., EPSG:4326), bounding_box (array [minx,miny,maxx,maxy], optional), render_style (string, optional). Outputs include viewport_metadata (object), feature_count (integer), extent (array), and outputs like export_links (object) or image_url (string). All numeric outputs have defined units: degrees for coordinates, meters for projected extents where applicable.\n\nAlgorithms & Calculations: The tool parses the dataset, computes the bounding box, converts coordinates to the requested CRS, aggregates simple metrics (feature_count, area), and renders a raster or vector preview. It uses standard GIS coordinate math, with simple reprojection fallback when data CRS is unknown.\n\nError & Edge Cases: Invalid dataset_source, unsupported formats, non-conforming CRS, or missing required inputs trigger explicit error codes and empty results. Large datasets may cause partial rendering with progress indicators. External data unavailability results in timeouts after defined thresholds.\n\nIndustry/Region & Localization: Uses ISO CRS naming and WGS84 where explicit. Units default to degrees for geographic CRS and meters for projected CRS. Supports common data formats (GeoJSON, Shapefile-friendly inputs) and aligns with geospatial metadata standards.\n\nAssumptions & Exclusions: Assumes dataset is geospatial and that the user has rights to access provided data. Excludes full GIS analytics, complex spatial joins, temporal analysis, or advanced 3D visualization.