## 3 Geo-Sensor Framework
### Geo-Sensor Composite Toolbox  
In this sub-section, we present the geo-sensor composite toolbox module of the proposed system.  
The geo-sensor composite toolbox has a vital role in the overall system. It provides the basic functionalities, which enable the client to add a sensor network along with its' geo-spatial context and also manages the network remotely. It has three functioning sub-modules as geo-sensor information manager, middleware information manager, and service information publishing (Figure 7).  
Figure 4: Proposed geo-sensor platform configurations.  
The geo-sensor information manager generates the spatial contextual based sensor profile for the sensor network and creates the geo-sensor profile handler for the content services access in the geo-sensor framework. The middleware manager generates the middleware mapping information for each sensor platform and creates the access handler for the geo-sensor framework. Service information publishing generates the service scripts for each added sensor network.  
A geo-sensor profile is composed of building information, floor information, and room information with marks on a map image representing the geographical location of the physically installed sensors. It also contains the physical sensor mappings for the virtual platforms and detailed sensor information. The geo-sensor profile provides the geo-sensor query functionalities as add geo-sensor network data, access geo-sensor network data, update geo-sensor network data, or delete geo-sensor network data.  
Figure 5: Geo-sensor platform’s generation procedure flowchart.  
Figure 6: Geo-Sensor Service Provision Service Sequence Diagram.  
Figure 7: Geo-sensor composite toolbox configuration.  
Figure 8 shows the sensor database entity relationship diagram. In the sensor database, we have sensor information, sensor type information, sensing data, sensing list, sensing category, and middleware information. Sensor_Information table saves sensor information. Sensing_List table saves the sensor's sensing type. Sensing_Category table saves detailed information about sensing type. Type_Information table saves the sensor's type. Sensing_Data table saves sensing data.  
Figure 9 shows the geo database entity relationship diagram. In the geo database, we have map information, map percent information, map data, building information, building mark, floor information, floor percent, room information, and room mark. Map_Informaiton table saves total map information (map size, minimap, minimap size, etc.). Percent_Information table saves the percent image information for the total map image (10%-100% reduced total map image size information). Map_Data table saves the total map image data. Building_Information table saves building information. Building_Mark table saves building area information. Floor_Information table saves floor map (map size, minimap, minimap size, etc.). Floor_Percent table saves the percent image information for floor map image (10%-100% reduced floor map image size information). Floor_Data table saves floor map data. Room_Information table saves room information. Room_Mark table saves room area information.  
Figure 8: Sensor database relationship diagram.