<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>GGL Geoprocessing language available in gvSIG</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<BR>
<P><FONT SIZE=2>As results of the Google Summer of Code at the gvSIG project, the gvSIG plug-in for GGL has been released [1].<BR>
<BR>
GGL is a specific programming language for geoprocessing where typical constructions of the more known programming languages (loops, conditionals, etc.) and specific constructions for geoprocessing to execute topological operations, filters, transformation of geometries, etc. adding help at the same time that the user write the scripts.<BR>
<BR>
The released plug-in allows to reference the data sources of the project open currently in gvSIG Desktop from the GGL scripts, making the geoprocessing of the data loaded in gvSIG possible. Anyway, the plug-in allows to visualize return results in gvSIG Desktop loading the same ones at the active view.<BR>
<BR>
Apart from the plug-in, several tutorials and reference documents [2] have been published to understand the logical language.<BR>
<BR>
Likewise, some mailing lists [3] have been created to solve any problem or doubt when the system is used.<BR>
<BR>
The advantages of using a geoprocessing specific language are:<BR>
<BR>
- The mentioned geoprocessing specific constructions: geometries in WKT, coordinates processing, typical operators of the relational algebra that add the same capacities than the spatial SQL to the language, etc.<BR>
<BR>
- Help for creating scripts: Validations at the same time that the user writes, verification of the existence of the data sources and accessed data structures, autocompletion with the fields of the accessed files, etc.<BR>
<BR>
- Pre-selection of technologies: GGL offers a series of functions to the user, that use the best internal technology currently: parsers, data access API, etc. That technology is pre-selected by the language developers, and it's a less responsibility for the user, who only has to specify the operation and not how to execute it.<BR>
<BR>
- Possibility to repeat geoprocesses, share them, give support, etc.<BR>
<BR>
<BR>
[1] <A HREF="http://www.gearscape.org/index.php/downloads">http://www.gearscape.org/index.php/downloads</A><BR>
[2] <A HREF="http://www.gearscape.org/index.php/documentation">http://www.gearscape.org/index.php/documentation</A><BR>
[3] <A HREF="http://www.gearscape.org/index.php/community">http://www.gearscape.org/index.php/community</A><BR>
</FONT>
</P>
</BODY>
</HTML>