Web mapping Study Guide

📖 Core Concepts Web Mapping – Creating, serving, and interacting with maps over the Web via Web GIS. Web Cartography – Production of static (non‑interactive) maps; contrasted with the interactive nature of web mapping. Web GIS – Server‑client system that delivers maps, stores spatial data, and performs GIS analysis on the Web. Location‑Based Services (LBS) – Consumer services (e.g., navigation, check‑ins) that rely on web‑map infrastructure. Static vs. Dynamic vs. Analytical vs. Real‑Time Maps – Spectrum from unchanging images to constantly refreshed, analysis‑driven visualizations. Spatial Database – Object‑relational DB with geometry types, spatial indexes, and OGC Simple Features support (e.g., PostGIS). Tile‑Based Delivery – Maps broken into small raster or vector “tiles” that are fetched on demand (TMS, WMTS). Web Map Service (WMS) – Standard API that returns a rendered map image based on layer, style, extent, etc. --- 📌 Must Remember Static Web Maps → PNG/JPEG/GIF/TIFF (raster) or SVG/PDF/SWF (vector). Dynamic Web Maps → Enable zoom/pan; data can update automatically. Real‑Time Maps → Sensor‑driven, refreshed every seconds‑to‑minutes. Vector Tiles = resolution‑independent, style‑on‑the‑fly; raster tiles = pre‑rendered images. OGC Simple Features → Defines geometry model (POINT, LINESTRING, POLYGON) + common operators (INTERSECTS, CONTAINS). Cloud‑Based Mapping → SaaS eliminates local install, provides auto‑updates, and enables data mash‑ups via APIs. Privacy Rule – Personal location data must be encrypted, transmitted over HTTPS, and protected by access control. --- 🔄 Key Processes Serving a Tiled Map Store source data → render tiles at fixed zoom levels → save tiles in {z}/{x}/{y} folder hierarchy → client requests needed tiles → server returns PNG/JPEG (raster) or protobuf/JSON (vector). WMS Request Workflow Client builds GetMap URL with parameters: LAYERS, STYLES, CRS, BBOX, WIDTH, HEIGHT, FORMAT. Server validates, composes map from layers, applies styles, renders image, returns in requested format. Real‑Time Map Update Loop Sensor → ingest → store in temporal DB → trigger tile/feature refresh (push via WebSocket or poll) → client re‑renders or applies new vector data. --- 🔍 Key Comparisons Static Web Map vs. Dynamic Web Map Static: single image file, no interaction, pre‑generated. Dynamic: interactive (zoom/pan), can query layers, updates on demand. Raster Tiles vs. Vector Tiles Raster: fixed resolution, larger bandwidth for many zoom levels, styling baked in. Vector: single source for all zooms, client‑side styling, smaller file size, but requires more client processing. WMS vs. TMS WMS: on‑the‑fly rendering, supports custom styles, larger server load. TMS: pre‑generated tiles, fast CDN delivery, limited styling flexibility. --- ⚠️ Common Misunderstandings “Web mapping = only static maps.” – Incorrect; web mapping includes dynamic, analytical, and real‑time services. “Vector tiles are always smaller than raster tiles.” – True for many cases, but complex styling or large attribute payloads can increase size. “Using a spatial DB guarantees data accuracy.” – Database enforces geometry rules, but source data may still be outdated or erroneous. --- 🧠 Mental Models / Intuition “Map as a LEGO set.” – Tiles (raster or vector) are LEGO bricks; the server provides the right bricks for the view, the client assembles them on‑the‑fly. “WMS = on‑demand printing.” – Think of a printer that receives a request (layers, size, style) and spits out a fresh map image each time. --- 🚩 Exceptions & Edge Cases Cross‑origin restrictions – Browsers block map tiles from domains without proper CORS headers. Projection mismatches – WMS must honor the CRS parameter; using unsupported projections returns an error. Large attribute payloads in vector tiles – Some browsers hit memory limits; consider simplifying attributes for mobile clients. --- 📍 When to Use Which Static image (PNG/JPEG) – Simple brochure‑style maps, no interaction needed, low bandwidth. Raster tiles (TMS/WMTS) – High‑traffic consumer maps where styling is fixed (e.g., base road maps). Vector tiles – Applications requiring on‑the‑fly styling, feature‑level interactivity, or multiple zoom levels from one source. WMS – When the client needs custom styling, temporary layers, or on‑the‑fly analysis (e.g., overlaying a user‑drawn polygon). Cloud SaaS GIS – Small teams or rapid prototyping; avoid heavy on‑premise infrastructure. --- 👀 Patterns to Recognize “Zoom level → tile coordinate conversion” – Look for formulas x = floor((lon + 180) / 360 2^z) and y = floor((1 - ln(tan(lat) + sec(lat)) / π) / 2 2^z). “Real‑time update → push vs. pull” – If the problem mentions sensors & sub‑second latency, expect WebSocket or server‑sent events; longer intervals often use periodic AJAX polling. “Security mention + HTTPS” – Indicates a requirement for encrypted transport and possibly token‑based authentication. --- 🗂️ Exam Traps Choosing raster tiles for a feature‑rich, style‑changing app – The exam may list “vector tiles” as the correct answer; raster tiles will lock in style and waste bandwidth. Confusing “Web cartography” with “Web mapping” – Remember that cartography = static map creation only. Assuming any DB can store geometry – Only spatially‑enabled DBs (PostGIS, Oracle Spatial, etc.) support OGC Simple Features; a plain MySQL instance without the spatial extension cannot. Overlooking CORS – A question about loading tiles from a different domain may be trying to test knowledge of cross‑origin header requirements. ---