In order to aid in the processes of data collection, interpolation, analysis, and predictive model development the integration of commercial remote sensing and spatial information technologies (CRS&SI) with object oriented modeling (OOM) using the model view controller architecture (MVC) has been applied. A Decision Support System (DSS) application that uses CRS&SI for collecting atmospheric, subsurface, and predicted weather data, is used to compare, interpolate, measure, predict, and determines the depth of frost and thaw penetration into the subsurface of roadways across New England, This process is used in order to guide State Departments of Transportation (DOT) in determining when to impose Seasonal Load Restrictions (SLR). Seasonal load restrictions limit the travel of heavy trucks on certain roads such that state DOT's can limit the damage to the roadway surface. The implemented DSS consists of a web based front end graphical user interface (GUI) that leverages popular web based technologies, programming interfaces, data collection scripts, data evaluation scripts, data interpolation scripts, predictive modeling, and a centralized database. The database was developed for storing newly collected, historic, and predicted data. This paper includes the description of the general purpose and use of the system and a discussion regarding the architecture, individual components, interactions, and a description of the sequence of events for data collection, processing, prediction, and interpolation.
General TermsCommercial Remote Sensing and spatial information technologies (CRS&SI), Model View Controller Architecture (MVC), Object-Relational Mapping (ORM) Keywords commercial remote sensing, decision support system, seasonal load restrictions, frost-thaw predictive model, and satellite data collection, model view controller, object relational mapping 32
Fig 3: Many tables in the database represent entities (objects), as shown in this partial view of the preliminary ER diagram. Some entities include states, establishments, sites, data loggers, sensors, sensor readings, and sensor types while other tableswere created simply to house calculated data or track service import schedules.