Anatomy of the Web Map Client Application (Firefox / IE/ Chrome) Spatial Data / Queries Mapping Server (ArcGIS Server) Application Server (IIS / Apache) Flash / JS / HTML client provides parameters. server returns results.
Server-side Solution Client Application (Firefox / IE/ Chrome) Server does the work Mapping Server (ArcGIS Server) Application Server (IIS / Apache) The client provides parameters and the server returns results.
Client-side Solution Client Application (Firefox / IE / Chrome) User’s Computer Does the Work Mapping Server (ArcGIS Server) Application Server (IIS / Apache) The client does the analysis and the server provides source data.
Client-side Raster Analysis Needs… Source Data – (PNG / JPG) – PNG for rasters classified into discrete classes – JPEG for smooth continuous surfaces – Common screen size = 1024 x 768 = 786,432 – Suitability Analysis of 10 Layers = 8 Megapixels
Transferring Source Data… Continuous Data – JPEG with 60% compression – Note min/max of each dataset – Stretch dataset from black to white
Transferring Source Data… Discrete Data (Soil Type) – PNG8 or PNG24 – ***Symbolize data with known values***
Client-side Raster Analysis Needs… Ability to run analysis – Access to individual pixels – Logic to evaluate pixel values – Raw speed
Pixel Bender Kernel Language Override a single function (evaluatePixel) – Executes in CPU / GPU Simple Syntax but Limited Expressiveness – No Arrays – No Custom Functions – boolean, float, pixel, and image data types
Your consent to our cookies if you continue to use this website.