MIDOP is by nature extensively customizable. Whenever you find a button “Edit”, by clicking it you will be able to directly modify the source code using a built-in source code editor.
Off course such modifications requires at least a basic PHP and HTML coding knowledge, but also novice users might understand it by reading existing code. A big effort while developing MIDOP is being putted on the coding style adopted: extensive use of comments, PHP variable with self-explaining names and simple text files for storing each managed website settings.
Available symbols used for plotting macroseismic intensities can be customized and new symbols can also be created by clicking the button “Edit” within the page “MDP map”: a popup window will open presenting a source code editor.
Have a look at the PHP coding standards and *DO* make a backup of your data!
Intensity symbols are organized in sets, each with as many symbols as the possible range of macroseismic intensities. Each intensity symbol within a set is defined using again four lines:
The built-in symbol sets used for representing MDP on a map are contained in the php file “settings \ symbols \ symbol_mdp.php”
Below the source code used for defining the 9th symbol of the “NERIES_NA4” set defining the represented intensity “4-5”:
$symbol_mdp['NERIES_NA4'] = new stdClass; $symbol_mdp['NERIES_NA4']->is = '4-5'; $symbol_mdp['NERIES_NA4']->symbol = '<circle cx="0" cy="0" r="1000" fill="#FDF323" stroke="#FF963F" stroke-width="600" />'; $symbol_mdp['NERIES_NA4']->onoff = 1;
A problem occurs if the original macroseismic intensity data adopts intensity diction that doesn’t match the defined intensity symbol set. If MIDOP found the intensity “IV-V” and a symbol linked to this intensity doesn’t exists the intensity point will simply not be rendered on the map.
In order to solve this problem you can automatically convert your custom intensity values instead of changing the whole intensity symbols set or altering the data contained in the intensity tables.
This conversion is based on the file “settings \ symbols \ symbol_conversion.php”. If for example you would like to convert the roman value “V-VI” into “5-6” two lines of code must be inserted:
$symbol_convert_cases = 'IV-V'; $symbol_convert_value = '4-5';
You can specify multiple conversion at once, so, if you would like to convert both the original values “V-VI” and “5.5” into “5-6” write something like:
$symbol_convert_cases = '4.5|IV-V'; $symbol_convert_value = '4-5';
Epicentre symbols are defined by four PHP lines:
Below the source code used for defining the rectangle:
$symbol_epicentre['SquareBlack'] = new stdClass; $symbol_epicentre['SquareBlack']->id = 'idSquareBlack'; $symbol_epicentre['SquareBlack']->symbol = '<rect x="-1500" y="-1500" width="3000" height="3000" stroke="#000000" stroke-width="500" fill="#FFFFFF" />'; $symbol_epicentre['SquareBlack']->onoff = 1;
Geographical layers in MODOP are plain text files containing SVG elements. Before trying to create such files you can find further information on the SVG specifications at the W3C website (http://www.w3.org/TR/SVG/).
Layers are stored in the folder “data” separately for the general earthquake map and for single earthquake intensity maps, and for each UTM zone and covered area following this structure:
An identical file structure is used for storing geographical layers for earthquake intensity maps in folder “data \ layers_mdp \”.
Layers files must follow some important rule:
Styling the layer is possible within the dedicated control panel window (below) available both for layers in the “EQ map” and “MDP map” page. Through the visual interface can specify both the fill and the stroke style and the layer opacity (transparency).
New geographical layers can be created for example from ESRI shapefiles (“.shp” extension).
These files must be already projected using the corresponding UTM zone to the geographical area where they are going to be used. The conversion can be done using the freely available “shp2svg” [Neumann, 2007] utility at the CartoNet website (http://carto.net/papers/svg/utils/shp2svg/) composed by two MS Windows executables “ogis2svg.exe” and “shp2pgsql.exe” that works in the Windows Command Prompt. The conversion is done entering the following command:
ogis2svg.exe --input your_shapefile --output svg_output_file.svg --roundval 1
When asked, answer “n” to every question. Below an example output of the conversion of the shapefile called “administrative_alps.shp”:
At the end of the conversion process, the output generated SVG file can be found in the same folder. In order to use such file in MIDOP as a geographical layer you must open the SVG file in a text editor and delete all the lines that don’t contain SVG elements and save the file with the “.layer” extension.
Below an example screenshot with the converted “administrative_alps.svg” file loaded into a text editor (enlighten in blue lines that must be deleted):
Once you have your file with the “.layer” extension you can upload it into MIDOP by clicking the button “upload a new layer” in the control panel.
Please, note that MIDOP will load the layer file as is and no geographical projection or other transformation will be performed.
For simple changes to the layers source code a text editor can fulfill the task.
If complicated SVG manipulation is required, you can use the freely available graphic tool Inkscape (http://www.inkscape.org/) which uses SVG as its native format of manipulating graphical object. Once you’ve done your changes within Inkscape remember to save the file as “plain SVG code” and, again, strip off all the unnecessary SVG lines of code.
MIDOP can load custom SVG objects that will be rendered in selected earthquakes. In order to obtain such feature you have to create a dedicated field within the earthquake catalogue table in which your SVG custom code will be stored. You then need to tell MIDOP to load such SVG code by selecting the created field in the “MDP page” at “SVG code from catalogue field” (see below) and specify at which layer level MIDOP will render it.