<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gournellos, Th.</style></author><author><style face="normal" font="default" size="100%">Vassilopoulos, A.</style></author><author><style face="normal" font="default" size="100%">Evelpidou, N.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Examples of erosion risk maps using Boolean and fuzzy logical rules in GIS - web platforms.</style></title><secondary-title><style face="normal" font="default" size="100%"> 20th International Cartographic Conference</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2001</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;This study is dealing with two different transformation rules for creating erosion&lt;br&gt;risk thematic maps. The first rule, based on Boolean logic, is a well known theory&lt;br&gt;used for composing maps and demanding crisp sets as input data. The second one is the fuzzy logic theory, appropriate for handling fuzzy sets. In this context we present a case study from the Greek territory of Korinth. It concerns the hydrological basin where recently a catastrophic flood event has occurred. As input data we have used field measurements, aerial photos, satellite images, topographic and geological maps. These data sets were georeferrenced, digitised and introduced to a G.I.S. – web platform. The G.I.S. – web technology permits easy data and map updates. Our&lt;br&gt;software tools were the MapInfo G.I.S., the MapXtreme web interface and the&lt;br&gt;MatLab. The aim of this paper is to emphasise on the utility of erosion risk maps for&lt;br&gt;environmental protection and agricultural uses.&lt;/p&gt;</style></abstract></record></records></xml>