# A GeoNode-Based Platform for an Effective Exploitation of Advanced DInSAR Measurements
## 4 GeoNode Modifications for the Advanced DInSAR Processing Results Integration
More specifically, as defined in Table 1, in the relation schema of the geodatabase table there are no attributes of _date_ type, but each date of the deformation time-series is identified by an attribute name (zYYYY_xxxx (1), for instance). Accordingly, each attribute name, relevant to a date of the deformation time-series, is _associated with_ one deformation value. The reason for this choice is that it allows us to have any pixel represented by a single row of the geodatabase table. Moreover, this also allows us to dynamically update the table adding new columns in case new dates are added to the deformation time-series. Figure 8: Pictorial representation of the pre-build tiles for different levels of zoom. Specifically, in order to plot and over-plot graphs of the DInSAR deformation time-series relative to pixels belonging to the same layer or to different layers, we developed a PHP module based on the open source pChart library [111]. Accordingly, for each measurement pixel it has been added a plot button in the geodatabase record, which is nothing more that a link calling the PHP module to visualize the deformation time-series. Note that, the choice of using a link in each record of geodatabase has the advantage to visualize information by using different GIS clients, without developing a specific plug-in for each GIS client (see Figure 9). Finally, two GeoNode webGIS plug-in have been also implemented, one to plot cross-sections of the mean deformation velocity layers (see Figure 10) and the other to download data from a selected area (see Figure 11). Both of these plug-in have been inserted in the map section of the GeoNode code and they permit us to retrieve information directly from the map, showing a pop-up with the list of intersected layers. Concerning the cross-sections plug-in, we highlight that it is possible to select one layer or more layers for which the spatial information of the mean deformation velocity have to be shown; instead, for the download plug-in it is possible to select only one layer at a time from which to download the pixel information included in the selected area. Both these routines are written in the Python Language and integrated in the section _Map Code_ of GeoNode. This integration allows  
Figure 9: Flow chart of the deformation time-series plotting procedure. us to use the Django [81] framework for permissions management on the layers. Moreover, for the cross-section plug-in the open source library Bokeh [112] has also been used. Note that, the choice of a dedicated implementation of a web plug-in instead of using standard WPS [113] functionalities has been determined by the efficiency gained thanks to the direct access to geodatabase, which is even more relevant when considering the huge amount of data to be processed in our DInSAR scenario (multi-million pixels). In any case, we remark that a WPS service can be deployed as an alternative, less efficient--at the moment--solution. Figure 10: Flow chart of the mean deformation velocity cross-section plotting procedure.