27.06.2013 Views

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

João Agrela et al.<br />

ETRS 89 projection was used as the INSPIRE European Directive states. Several changes had to be<br />

made in the thematic layers of information.<br />

Every variable was stored within a geoDataset, <strong>and</strong> every dataset in a geoDatabase. This is needed<br />

for it allows better operational flow within the model. It was necessary to create some layers of<br />

information from other sources, <strong>using</strong>, for instance, PDF imagery from municipal services (for<br />

example, the information on Geology did not exist on shapefile format <strong>and</strong> had to be recreated<br />

through vectorization from a PDF municipal file).<br />

Another important step was to limit all the information to the institutional municipal limits, so as to limit<br />

any error that might occur during the map algebra stage of this process.<br />

All the above steps were needed just to create a viable geographical information database, with<br />

correctly georeferenced information, limiting redundant information <strong>and</strong> allowing quicker processing of<br />

all Model Builder tools. One aspect has to be pointed out by the authors: these steps are vital not only<br />

for a Model Builder based project. It is necessary to take all these steps in any GIS based project to<br />

achieve maximum efficiency. All the data normalization may be, at times, a time consuming <strong>and</strong><br />

troublesome stage but it is essential to create a steady basis for the project. It does not do well to<br />

build a castle on s<strong>and</strong>y foundations.<br />

The theoretical starting point is a simple assumption: some geographical variables have in their<br />

nature a prohibitive aspect that does not allow the installation of the above mentioned public<br />

installation. Geographical variables have between themselves relations of neutrality, repulsion <strong>and</strong><br />

attractiveness. Giving a quick example, the geographical nature of the variable “Hospital” repels the<br />

geographical nature of the variable “Sewage Treatment Plant”. The intensity of repulsion or<br />

attractiveness is directly related to the direct or partial incompatibity of natures of the geographical<br />

variables.<br />

After all the pre-project stages of data formatting <strong>and</strong> preparation it is thus necessary to identify the<br />

nature of all the variables <strong>and</strong> the variables that are absolutely opposite, or only partially opposing (for<br />

instance, there might not be any geologically suitable l<strong>and</strong> parcel in the municipality, which means we<br />

would have to choose the “lesser evil”, which is to say, a less suitable l<strong>and</strong> parcel).This method<br />

implies that there will be intermediate cartography created. This is a useful fact, because the users of<br />

the models can always go back to the intermediate cartography to check why the final choice of<br />

location was made. It is also a very valuable stage of direct validation of the model, since the users<br />

can check which branch of the model is returning more accurate outputs. In this model we may point<br />

out three Intermediate outputs.<br />

These intermediate outputs have meaning <strong>and</strong> an ethical <strong>and</strong> value related approach to it. The first of<br />

the three branches is named Favorable Placing Cartography (FPC) <strong>and</strong> every pixel has a positive<br />

numeric value.<br />

Figure 3: Favorable placing cartography branch<br />

5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!