Version 1.1.2 (04-03-2008)

• Supported file formats:
  • Read and write support for GML 3.1.1. has been added.
  • Read and write support for KML 2.1 has been added. This means vector layers can now be exported and viewed using Google Earth.
• WFS Service:
  • Support for WFS 1.1.0 has been added.
• Map:
  • New north symbols have been added.

Version 1.1 (21-09-2007)

• Installation:
  • gvSIG installation includes now JAI 1.1.3
• JCRS Extension:
  • Now integrated in the installation.
• geoDB:
  • Now integrated in the installation.
• Field Calculator:
  • It automatically fills table fields by calculating from values in the same table or geometry properties like area, length, etc.
• Annotation Layer:
  • It can be generated from feature layers with any kind og geometry, not just points.
  • A new independent non-virtual layer is created and persisted as shp. The original layer is not removed from the View.
  • The table associated to the new shp file contains fields for Text, Font, Color, Height and Rotation.
  • There is a new menu option “Properties of annotation layer”, where it is possible to choose units (meters or pixels), to draw text only, etc.
  • In the “Add Layer” dialog, a new tab allows loading of Annotation layers.
  • The process can eliminate duplicated labels.
  • The annotation layer can be generated from selected features.
  • The process can eliminate overlapping labels.
• PostGIS:
  • When exporting to PostGIS, it is possible to specify the database Schema name to save to.
• Export to raster
  • A raster can be exported, either a complete layer or a selected area, to a TIFF file.

Version 1.1.2 (04-03-2008)

- The following problems have been fixed in this release:

• Opening/Saving projects:
  • When gvSIG is started up, an error occurs when the name of a .gvp file is passed as a parameter and when a layer is added to an existing project view.
• PostGIS:
  • Reading problems occur when a layer with over 20000 records is loaded.
  • An error occurs if incorrect information is input in the “Schema” parameter when exporting to PostGis.
• Raster layer:
  • ENVI files do not load.
• “Add layer” dialog box:
  • When added layers are moved up in this window, they disappear altogether.
• Geoprocessing:
  • An error message appears if the input and clip layers are selected in the wrong order during the “Spatial join” geoprocess.
• Oracle Locator:
  • Problems accessing layers with null geometries.
• Internationalization:
  • There is no German translation of the geoprocess toolbox.
• Map Layout:
  • Can't remove elements using keyboard.

Version 1.1.1 (21-12-2007)

- The following problems have been fixed in this release:

• Tables:
  • In some shapefiles, empty records appear.
• Oracle:
  • Problems when exporting to Oracle.
• Editing:
  • Introducing points with absolute polar coordinates doesn't work.
• DGN Files:
  • Problems when exporting this kind of files to DXF format.
• GML Files:
  • Problems when exporting this kind of files to GML format.
  • Problems when exporting this kind of files to PostGIS format.
• Export to pdf:
  • When changing page properties, export to PDF fails recalculating the position of some elements.
• Other:
  • When opening an existing project containing a layer whose path has changed, if the table associated to it is not removed from the Project manager, then the console pops up.

Version 1.1 (21-09-2007)

- The following problems have been fixed in this release:

• geoDB extension:
  • Spatial database connections are case-insensitive and this may cause connection errors.
• Annotation layers.
  • The changes in font style properties are omitted when saving.
• Gazetteer Service:
  • Problems when returning feature point and associated label.
• Tables:
  • When creating a field of type “Double”, no precision value is assigned by default. A console error pops up if the user doesn’t specify the precision value.
  • Errors in the calculation of statistics for numeric fields.
  • Field defined as Integer in a dbf table are stored as Double.
  • When editing a dbf table, text strings containing tildes cannot be added.
• Feature layers:
  • Problems managing large feature layers.
• Raster layers:
  • Raster data exported from gvSIG doesn’t load correctly.
  • Scale range cannot be defined for this type of layers.
• Save georeferenced raster:
  • Sometimes exported images are shifted along Y axis.
  • When saving a clipped area to jpeg2000, the result is incorrect if the default compression level is modified.
• Editing:
  • The polygon selection color is not maintained.
  • Refresh problems when creating polygons.
  • When a new layer is added, snapping doesn’t work with this layer’s features.
  • When using symmetry in a point layer, the view doesn’t refresh correctly after removing origin points.
• PostGIS:
  • When editing a PostGIS layer, existing table IDs are not taken into account and elements are duplicated.
  • Sometimes, problems when exporting to PostGIS.
• View:
  • Error if a view that contains a layer being edited is removed.
  • The default coordinate system selected is the Preferences dialog is not enforced.
• Filter Tool:
  • When applying a filter on a layer group, the selection only shows in the table, but not in the view.
• Internacionalization:
  • In some languages the description of geoprocesses doesn’t show.
• GML Files:
  • Problems opening files with points.
• Map:
  • When an element rotation is undone, and then a new one is applied, the second rotation has no effect.
  • When adding an image with draft quality, it doesn’t insert correctly.
  • If grouped elements are moved, the link between the elements (North, Legend…) and the view is lost.
• DXF Files:
  • Problems when exporting this kind of files to shp format.
  • After editing, when saving changes the original table information is lost.
  • When opening a dxf file containing polygons with filling, those polygons are shown without filling and a vertex is droped, so the polygon is incompletely visualized.
  • If the legend properties are switched to Unique Symbol, then the graphical elements disappear from the view and only text are displayed.
• DGN Files:
  • Problems when exporting this kind of files to shp format.
  • If the legend properties are switched to Unique Symbol, then the graphical elements disappear from the view and only text are displayed.
• WFS Service:
  • Can’t load layer when it contains numeric field with decimals.
• Layout:
  • In the page setting it is not possible to change the customized size.
• Printing:
  • It is not possible to define correctly a custom size. When selecting landscape page orientation (horizontal) the width parameter is ignored and, if the orientation is set to portrait orientation (vertical) the height parameter is ignored.

Version 1.1 RC2 (09-08-2007)

- The following problems have been fixed in this release:

• Shp files:
  • This file type is not loaded if the extension is uppercase.
  • Error when exporting shp point files to dxf.
• Raster layers:
  • Error when saving a project after transparency has been applied to a raster layer.
  • If transparency is applied to an ecw image, then zoom closer and then back to the image extension, the layer is not correctly displayed.
• Tables:
  • Errors when opening dbf tables.
• Annotation layers:
  • Errors when editing with scale, rotation and symmetry tools.
  • Changes in “Preferences” are not persisted.
  • Errors when copying elements.
• Installation:
  • Problems installing gvSIG on Ubuntu 7.04.
• Geoprocessing:
  • Process is not completed in Buffer and Disolve entities geoprocesses.
• PostGIS:
  • In editing, values added to a new field are not saved.

Version 1.1 RC1 (20-07-2007)

- The following problems have been fixed in this release:

• Gazetteer Service:
  • Problems when returning feature point and associated label.
• Tables:
  • When creating a field of type “Double”, no precision value is assigned by default. A console error pops up if the user doesn’t specify the precision value.
  • Errors in the calculation of statistics for numeric fields.
  • Field defined as Integer in a dbf table are stored as Double.
  • When editing a dbf table, text strings containing tildes cannot be added.
• Feature layers:
  • Problems managing large feature layers.
• Raster layers:
  • Raster data exported from gvSIG doesn’t load correctly.
  • Scale range cannot be defined for this type of layers.
• Save georeferenced raster:
  • Sometimes exported images are shifted along Y axis.
  • When saving a clipped area to jpeg2000, the result is incorrect if the default compression level is modified.
• Editing:
  • The polygon selection color is not maintained.
  • Refresh problems when creating polygons.
  • When a new layer is added, snapping doesn’t work with this layer’s features.
  • When using symmetry in a point layer, the view doesn’t refresh correctly after removing origin points.
• PostGIS:
  • When editing a PostGIS layer, existing table IDs are not taken into account and elements are duplicated.
  • Sometimes, problems when exporting to PostGIS.
• View:
  • Error if a view that contains a layer being edited is removed.
  • The default coordinate system selected is the Preferences dialog is not enforced.
• Filter Tool:
  • When applying a filter on a layer group, the selection only shows in the table, but not in the view.
• Internacionalization:
  • In some languages the description of geoprocesses doesn’t show.
• GML Files:
  • Problems opening files with points.
• Map:
  • When an element rotation is undone, and then a new one is applied, the second rotation has no effect.
  • When adding an image with draft quality, it doesn’t insert correctly.
  • If grouped elements are moved, the link between the elements (North, Legend…) and the view is lost.
• DXF Files:
  • Problems when exporting this kind of files to shp format.
  • After editing, when saving changes the original table information is lost.
  • When opening a dxf file containing polygons with filling, those polygons are shown without filling and a vertex is droped, so the polygon is incompletely visualized.
  • If the legend properties are switched to Unique Symbol, then the graphical elements disappear from the view and only text are displayed.
• DGN Files:
  • Problems when exporting this kind of files to shp format.
• WFS Service:
  • Can’t load layer when it contains numeric field with decimals.

Version 1.1.2 (04-03-2008)

• Export to raster:
  • Sometimes tiff and jp2 images created using gvSIG cannot be opened in other programmes.
• KML files:
  • Multi-layer KML files do not load correctly. All the features are shown in a single layer.

Version 1.1.1 (21-12-2007)

• Map Layout:
  • Can't remove elements using keyboard.

Version 1.1 (21-09-2007)

• CRS managing extension:
  • In Linux, in case the extension was installed in a path which contains whitespaces it is possible that gvSIG fail starting.
• Raster files:
  • Sometimes the error console has pop up when opening a JPG file if the view contains SHP files.
• dwg Files:
  • Some graphical entities topologies can't be loaded (see FAQ section).
  • If the legend properties are switched to Unique Symbol, then the graphical elements disappear from the view and only text are displayed.
• dgn files:
  • The MicroStation element Multi-Line will not be visualized.
• dxf files:
  • When opening a dxf file containing polygons with filling, those polygons are shown without filling and a vertex is droped, so the polygon is incompletely visualized.
  • If the legend properties are switched to Unique Symbol, then the graphical elements disappear from the view and only text are displayed.
  • A DXF file united to a DBF table cannot be labeled by none of the fields of the union.
• Units of measurement:
  • It does not measure properly areas in the views with system of geodesic projection.
• WMS Servers:
  • Since TIFF is an uncompressed image format, layers loaded from these servers can produce errors due to their size.
• Layout:
  • When modifying the size of an inserted image, this is distorted.
  • When zooming to the sheet area some errors can occur such as the program crash or the deletion of a layer in the view.
• Projections:
  • Small displacement errors when changing datum due to the system of reprojection used (GT2 v2.0), it will be solved when we use version 2.1.
  • When changing the projection of a view, the existing layers within that view are not reprojected.
• Internationalization:
  • Some translations on the GUI strings still pending.
• Printing:
  • With dgn and dxf files it may fail when the polygons have assigned a pattern symbol that is not a solid color or transparent (vertical, horizontal, oblique lines, etc), which will slow down printing.
• Labeling:
  • Layers reprojected to geodesic coords can not be labelled.
  • On occassions, refreshment problems when activating and deactivating may appear.
  • It does not draw the labels in the side margins of the graphic area.
  • Sometimes the otpion “Draw text only” has failed.
• Export to pdf:
  • When changing page properties, export to PDF fails recalculating the position of some elements.
• Macintosh:
  • Cannot read ECW files
  • Valid only for Intel-based computers. It will be available soon for PowerPC-based.
• PostGIS:
  • When adding, removing or deleting fields in a postgis 8.0 or newer version it throws an error to the console.
• Tables:
  • Some errors detected when working with table with non-ASCII field names.
• Annotation layer:
  • Scale, copy, rotate and symmetry tools don't work properly in this kind of layers.
• Geoprocessing:
  • The result of the dissolve geoprocess is incorrect.
• Export to raster
  • When clipping jpg2000 and ecw layers, the result is a raster with the RGB bands incorrectly swapped.
• Other:
  • When opening an existing project containing a layer whose path has changed, if the table associated to it is not removed from the Project manager, then the console pops up.

Version 1.1RC2 (09-08-2007)

• Others:
  • A high memory consumption in this version might cause the application to close suddenly after loading large datasets.
  • Sometimes, in Linux, a dialog box opens showing only the title bar. If the user attempts to close the dialog, an error pops up (see Annex 3 in the User Manual (version 2) of gvSIG 1.1).

Version 1.1RC1 (20-07-2007)

• Others:
  • A high memory consumption in this version might cause the application to close suddenly after loading large datasets.
  • Sometimes, in Linux, a dialog box opens showing only the title bar. If the user attempts to close the dialog, an error pops up.

Version 1.1.2

Update

gvSIG version 1.1.2 is a partial update of version 1.1 or version 1.1.1. These earlier versions must be installed correctly on your PC beforehand.

Warning: Do not install over a gvSIG version which contains the 3D Pilot.

To install, follow these steps:

• Download the file from the webpage.
• Unzip it.
• Run the file install.exe. (During installation, file deleting information windows appear. Click on OK to continue.)

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Version 1.1.1

Update

gvSIG version 1.1.1 is a partial update of version 1.1. This earlier version must be installed correctly on your PC beforehand.

Warning: Do not install over a gvSIG version which contains the 3D Pilot.

To install, follow these steps:

• Download the file from the webpage.
• Unzip it.
• Run the file install.exe. (During installation, file deleting information windows appear. Click on OK to continue.)

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Complete version

The full version of gvSIG 1.1.1 is installed in the same way than gvSIG 1.1.

Version 1.1

Installation

You can download gvSIG in two installation modes:

• gvSIG + prerequisites (JRE 1.5.0_12, JAI and JAI Image I/O):
  • Download and unzip the Windows installation package from the downloads table (in the downloads section).
  • Execute the EXE file and follow the instructions. 
  • The following components will be automatically installed:
    • Java Virtual Machine *
    • JAI libraries *
    • JAI image I/O libraries *
    • gvSIG

            * These components will be installed only if they are not present in the system or if the version of the installed ones is not compatible with the program requirements

• Only gvSIG:
  • Download and unzip the Windows installation package from the downloads table (in the downloads section).
  • Execute the EXE file and follow the instructions.
    • During the installation you will be required to choose the Java Virtual Machine that you wish to use to run gvSIG. The installation program checks if the prerequisites are correctly installed. If they are not, the installation program asks the user for download and install them (it requires an Internet connection).

Run the program by doing one of the following:

• From the Desktop shortcut.
• From the Start/Programs menu.
• From the command line:
  • Step into the application directory (it is the one choosed at the installation time).
  • Type “gvSIG”.

gvSIG language defaults to the system language, if it matches with one of those supported (valencian, spanish, gallego, english, czech, german, basque, french, italian, portuguese, chinese, polish and romanian). Otherwise, english language is used. 

There are two ways to change the language:

1. From the Window menu, select Preferences then go to General/Language panel and select the language you wish. To apply the changes exit and run again gvSIG.
2. From the command-line or the console

• Type “gvSIG [language]”
• The values currently supported by the language variable are:

• es: Spanish
• va: Valencian
• gl: Gallego
• en: English
• cs: Czech
• de: German
• eu: Basque
• fr: French
• it: Italian
• pt: Portuguese
• zh: Chinese
• ro: Romanian
• pl: Polish

 Uninstall

To uninstall gvSIG v1.1, execute gvSIG Uninstall icon from the Start/Programs Menu.

Version 1.1.2

Update

gvSIG version 1.1.2 is a partial update of version 1.1 or version 1.1.1. These earlier versions must be installed correctly on your PC beforehand.

Warning: Do not install over a gvSIG version which contains the 3D Pilot.

To install, follow these steps:

• Download the file from the webpage.
• Unzip it.
• Run the file install.bin. (During installation, file deleting information windows appear. Click on OK to continue.)

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Version 1.1.1

Update

gvSIG 1.1.1 is a partial update to be applied over the 1.1 version, so gvSIG 1.1 must be already and correctly installed in the computer.

To install, follow these steps:

• Download the file from the webpage.
• Unzip it.
• Run the file install.bin

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Complete version

The full version of gvSIG 1.1.1 is installed in the same way than gvSIG 1.1.

Version 1.1

Installation

You can download gvSIG in two installation modes:

• Download and unzip the Linux installation package from the downloads table (in the downloads section).
• Execute the .bin file and follow the instructions. 
• The following components will be automatically installed:
  1. Java Virtual Machine *
  2. JAI libraries *
  3. JAI image I/O libraries *
  4. gvSIG

            * These components will be installed only if they are not present in the system or if the version of the installed ones is not compatible with the program requirements

• Only gvSIG:
  • Download and unzip the Linux installation package from the downloads table (in the downloads section).
  • Execute the .bin file and follow the instructions. Don't forget to set execution permission to the .bin file before run it.
    • During the installation you will be required to choose the Java Virtual Machine that you wish to use to run gvSIG. The installation program checks if the prerequisites are correctly installed. If they are not, the installation program asks the user for download and install them (it requires an Internet connection).

Run the program by doing one of the following:

• From the Desktop shortcut.
• From the Start/Programs menu.
• From the command line:
  • Step into the application directory (it is the one choosed at the installation time).
  • Type “./gvSIG.sh”.

 gvSIG language defaults to the system language, if it matches with one of those supported (valencian, spanish, gallego, english, czech, german, basque, french, italian, portuguese, chinese, romanian and polish). Otherwise, english language is used.

There are two ways to change the language:

1. From the Window menu, select Preferences then go to General/Language panel and select the language you wish. To apply the changes exit and run again gvSIG.
2. From the command-line or the console

• Type “./gvSIG.sh [language]”
• The values currently supported by the language variable are:

• es: Spanish
• va: Valencian
• gl: Gallego
• en: English
• cs: Czech
• de: German
• eu: Basque
• fr: French
• it: Italian
• pt: Portuguese
• zh: Chinese
• ro: Romanian
• pl: Polish

Uninstall

• To uninstall gvSIG 1.1 execute gvSIG Uninstall icon from the Start/Programs Menu.

Version 1.1.2.

Update

gvSIG version 1.1.2 is a partial update of version 1.1 or version 1.1.1. These earlier versions must be installed correctly on your PC beforehand.

Warning: Do not install over a gvSIG version which contains the 3D Pilot.

To install, follow these steps:

• Download the file from the webpage and open it.
• Execute the 'Actualizador gvSIG 1.1.2' file of the Desktop. (During installation, file deleting information windows appear. Click on OK to continue.)

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Version 1.1.1

Update

gvSIG 1.1.1 is a partial update to be applied over the 1.1 version, so gvSIG 1.1 must be already and correctly installed in the computer.

To install, follow these steps:

• Download the file from the webpage and open it.
• Execute the 'Actualizador gvSIG 1.1.1' file of the Desktop.

The installation will attempt to automatically find the directory where the previous installation is. If it does not, then the directory have to be manually indicated.

Complete version

The full version of gvSIG 1.1.1 is installed in the same way than gvSIG 1.1.

Version 1.1

gvSIG runs on OS X 10.3 and 10.4 (PowerPC and Intel). GDAL library works fine, but mrSID is still only available for PowerPC. ECW is not available for OS X.

gvSIG prerrequisites are:

• Java Advanced Imaging (JAI)
  • Is preinstalled on OS X 10.4. For 10.3, there is a downloadable installer in Apple's website. gvSIG will detect the availability of JAI, and offer taking you to the installer webpage or installing the basic files itself.
• JAI Image I/O
  • There is no official installer for OS X. A common partial workaround is installing the pure java part of it; gvSIG will offer doing so.

Obligatory requirements

These requirements must be installed in order to execute the application.

• Virtual java machine 1.5.0_12
  • Linux: jre-1_5_0_12-linux-i586.bin
  • Windows: j2re-1_5_0_12-windows-i586-p.exe
• JAI (Java Advanced Imaging): Install it in the same virtual machine with which you will run the program
  • Linux: jai-1_1_3-lib-linux-i586-jre.bin
  • Windows: jai-1_1_3-lib-windows-i586-jre.exe
• JAI Image I/O: Install it in the same virtual machine with which you will run the program
  • Linux: jai_imageio-1_0_01-lib-linux-i586-jre.bin
  • Windows: jai_imageio-1_0_01-lib-windows-i586-jre.exe

Specific requirements

These requirements must be installed in order to execute certain features.

• Drivers for Oracle table

                To install Oracle drivers, please follow the steps bellow:

1. Go to Oracle Database 10g Release 2 (10.2.0.3.0) drivers.
2. Accept the license terms.
3. In the next page, download the file ojdbc14.jar (1,536,979 bytes) - classes for use with JDK 1.4 and 1.5. (Registration required)
4. Move this file to the next folder:

• Windows:
  • Move the file to the bin\gvSIG\extensiones\com.iver.cit.gvsig\lib folder, that is in the directory where gvSIG is installed.
• Linux:
  • Move the file to the bin/gvSIG/extensiones/com.iver.cit.gvsig/lib folder, that is in the directory where gvSIG is installed.

The functionality of breaking up chains of text into different parts and storing them in table fields is added to gvSIG with the new normalization extension. These chains of text can have their origin in plain text files or in the different records of a table field.

The following organizations have participated in the extension:

• Sponsor:
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  • Prodevelop SL
  • IVER Tecnologías de la Información

• It allows normalizing chains of text of a plain text file and storing them in a new table.
• It allows normalizing chains of text of a table field and storing them in new fields of the same table.
• Chains of text of a table field can be normalized and stored in a new table with the possibility of adding fields to the original table and perform a JOIN later on.

The extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:  

• Download the file from the web appropiate to the operating system and execute it.

 If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a extension for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2
 

Extension to easily manage the user interface over a gvSIG installation, allowing for the translation to new languages without having to install a new version of gvSIG. It also allows updating or to complete languages already installed, facilitates the translation to new languages using some of the ones already installed as a reference by exporting the necessary files, as well as the uninstalling of a language translation.

The following organizations have participated in the extension:

• Sponsor:
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  • DiSiD Technologies
• Collaborator:
  
  • Model Driven Development S.L. 

• It substitutes the language selection panel in the gvSIG preferences.
• It allows selecting the active language of gvSIG.
• It makes possible the installation of translations of new languages by means of a .zip file containing the translation property file.
• It allows updating languages already installed, also by means of a .zip file.
• It is possible to export the translation of a language already installed, so much for its update as to translate to a new language.
• It allows uninstalling existing languages.

• Sometimes the compress files created in Windows with some of the common utility programs such as 7zip, WinZip or WinRar (especially this last one) are not properly recognized and cannot be imported.

The extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web, appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a extension for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2

DielmoOpenLidar is a GNU/GPL free and open source software based on gvSIG for managing LiDAR data. It allows to access, visualize and analize original LiDAR data, so the user is able to visualize a large amount of uncut LiDAR data (irregular points cloud in LAS and BIN format) together with other geographic data. In the future it also will allow to create basic products (DTM, DSM, intensity images, etc.) and final products with an added value.

The following organizations have participated in the Dielmo Open Lidar Extension for gvSIG:

• Sponsor:
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
  • Dielmo S.L.
• Developer:
  • Dielmo S.L.

BN4 (2-12-2008) 

• Read/Write Driver for LiDAR data (LAS and BIN file formats).
• Automatic symbology depending on height, intensity or classification for LiDAR layers.
• Default legend as an unique random symbol for LiDAR layers.

The extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web, appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a extension for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2.

The aim of this metadata prototype is to make catalogation of geospatial information easier, providing gvSIG with some specific features. First of all, it allows us to extract automatically some metadata from the data source (only from shapefiles right now). Secondlly it has an editor that allows us to complete the rest of the metadata. And finally we´ll be able to publish the metadata on a catalog server (only on Geonetwork right now).

The following organizations have participated in the metadata prototype for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  
  • Universitat Jaume I

The extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system
• Execute it

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a extension for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2

The goal of the publishing extension is to provide users with the functionality of publishing geospatial data and metadata through standard OGC web services, right from the gvSIG user interface without the need to interact directly with any server software. In this way, without specific knowledge of the server applications, the gvSIG user will be able to publish cartography and metadata on-line with extreme ease.

This first version specifically includes publishing of geospatial services through these software packages and standards: 

• Mapserver: WMS, WCS & WFS.
• Geoserver: WFS.

The following organizations have participated in the publishing extension for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  
  • IVER Tecnologías de la Información
• Collaborator:
  
  • Munich City Council (Germany)

The extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a extension for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2

The extension to synchronize gvSIG desktop with gvSIG Mobile allows information to be exported directly from the gvSIG desktop to gvSIG Mobile, including layer information and (simplified) symbols. In addition, the extension creates the project file which is opened in gvSIG Mobile.

The following have taken part in the extension to synchronize gvSIG with gvSIG Mobile:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developers:
  • Prodevelop SL
  • Institute of Robotics (Universitat de València)
• Collaborators:
  
  • Inter-island Council of La Palma

BN5 (13-03-2008)

• Select area to export:
  • Active view.
  • Frame.
• Export to gvSIG Mobile:
  • Select layers to export according to their location in the View and the area to be exported.
  • Full layers can be exported.
  • Clip by rectangle.
  • Select geometries to export.
  • Select attributes to export.
  • Generate gvSIG Mobile export project.
  • Export simple symbols.
  • Export viewing scales.

BN5 (13-03-2008)

• “Cut” process:
  • Exporting SHP files with spatial index and databases does not function properly.

The extension to synchronize gvSIG with gvSIG Mobile must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it. 

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of an extension to synchronize gvSIG with gvSIG Mobile for gvSIG 1.1.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.2.

* We strongly recommend to update the synchronization extension, since a major bug found in build number 5 has been fixed. The new distribution (build number 6) will automatically replace the previous one when it's installed.

SEXTANTE is a Geographical Information System that has been developed by the Regional Government of Extremadura (Spain). It has provided gvSIG with both raster and vector geographical analysis capabilities with over 150 extensions, geo-statistics, vegetation indexes, profiles and hydrological analysis, to name but a few of the implemented functions.

The ArcSDE client extension for gvSIG allows users to access this kind of spatial databases, easily loading geometries by using the same interface as the rest of database layers available in gvSIG. So far this extension only allows access to vector layers in the database.

The following organizations have participated in the ArcSDE Client extension for gvSIG:

• Sponsor:
  
  • Consejería de Desarrollo Sostenible y Ordenación del Territorio de la Región de Murcia (Spain)
• Developer:
  
  • IVER Tecnologías de la Información.
• Coordinator:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)

The ArcSDE extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of an ArcSDE Client for gvSIG 1.1.1 in Windows XP, the folder could be C:\Program Files\gvSIG_1.1.1.

To access ArcSDE databases is necessary to download two libraries, following the next steps:

1. Access to ArcSDE 9.1 General Update Patch 3.
2. Depending on the operating system, continue by:

•   On Windows: 
  • In the section ESRI Products connecting to ArcSDE (Application and Direct Connect connections) go to Windows.
  • Download the file sde91-genpatch3-esri-win.zip and uncompress it.
  • Move the files jpe91_sdk.jar and jsde91_sdk.jar in the folder lib of the uncompressed file to the folder bin\gvSIG\extensiones\org.gvsig.sde\lib, inside the gvSIG installation folder.
• On Linux:
  • In the section ESRI Products connecting to ArcSDE (Application and Direct Connect connections) go to UNIX.
  • Download the file sde91-genpatch3-esri-lx.tar.Z and uncompress it.
  • Move the files jpe91_sdk.jar and jsde91_sdk.jar in the folder lib of the uncompressed file to the folder bin/gvSIG/extensiones/org.gvsig.sde/lib, inside the gvSIG installation folder.

 

Pilot' application awarded the contract to develop the 3D Extension by the Regional Ministry of Infrastructure and Transport of Valencia (Spain). It allows the creation of 3D Views, XYZ-projected as well as spherical (planetary). Local and remote data sources can be loaded as layers on them, and displayed using most of the options available in 2D like transparency, labeling, legends, etc.

The following organizations have participated in the 3D pilot extension for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developers:
  
  • Fujitsu
  • IVER Tecnologías de la Información
  • Ai2 Institute (Universitat Politècnica de València)

The 3D pilot extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

•  Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a 3D pilot extension for gvSIG 1.1.1 in Windows XP, the folder could be C:\Program Files\gvSIG 1.1.1.
 

1. In the case Linux OS is used, the libc library installed should be version 2.4 or higher. Lower versions (for instance, in Ubuntu Dapper) will cause problems.
2. In the case Mac OS X is used, it must be taken into account that gvSIG doesn't include so far the library to read ECW image files in this operating system. The corresponding exercises in the tutorial can be done with the TIF version of the images.

Warnings

It is highly recommended to follow the steps in this manual to install a gvSIG version compatible with the 3D extension. If the 3D extension is installed on an earlier version of gvSIG, there will be incompatibility problems.

If the installation of the 3D pilot is done on a machine with gvSIG already installed, or if Java 1.5 is installed on a version of gvSIG using Java 1.4, it must be taken into account that the instalation of the new JAI ImageIO library will remove this library from any other Java installation, causing problems with previously installed versions of gvSIG. In addition, the installation of the 3D extension will be interrupted after the removal of JAI ImageIO and the process must be restarted.

The pilot application awarded the development contract for the gvSIG Network Analysis extension by the Regional Ministry of Infrastructure and Transport of Valencia (Spain). It includes the calculation of a minimum path across two or more locations, allowing the insertion of intermediate stops. To do so, it generates the network topology or loads a previously calculated one. In addition, the pilot includes the use of point density legends for polygon layers.

The following organizations have participated in the network pilot extension for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  
  • IVER Tecnologías de la Información

BN5 (16-10-2007)

•  The pilot has been updated to work on gvSIG 1.1

BN5  (16-10-2007)

• The following problems have been fixed in this release:
  • In the stop management dialog, the driving speed for the network links can be configured.

The network pilot extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a network pilot extension for gvSIG 1.0.2 in Windows XP, the folder could be C:\Program Files\gvSIG 1.0.2.

First delivery of the new CRS (Cordinate Reference System) module with features a CRS database engine that allows the use of the complete EPSG, IAU2000, and others, transformation of 3 and 7 parameters and also the grid based ones. In general it provides maximun precision when performing of CRS changes.

The following organizations have participated in the CRS (Cordinate Reference System) extension for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  
  • Institute for Regional Development of the University of Castilla - La Mancha

BN11 (27-11-2008)

• Potential to define new Coordinate Reference Systems (user's CRS). The definition of CRS by users can be achieved by three methods:
  • Specifying all the parameters.
  • Taking as starting point one of the EPSG CRS and modifying the selected parameters.
  • By specifying the CRS through the WKT (well known text).

• Potential to perform compound transformations related to the source CRS as well as the target CRS.
  This option is useful when there is no direct transformation between two datums, but instead there is a datum for each and a common CRS for both. A compound transformation allows to re-project between datums of which the direct transformation parameters are unknown, doing the transformation in two steps.

BN11  (27-11-2008)

• The following problems have been fixed in this release:
  • There has been a redistribution of code between the extension and the library.
  • The OGR dependency has been eliminated.

BN11  (27-11-2008)

• Upon adding/editing a new user's CRS, the rest of the CRS list disappears and only the new/edited is visible. The CRS list shows again after a new search.
• The name that shows in the selection window for the user's CRS is NOT the one assigned in the field “Name”, but the one introduced in the field “Projection name” of the “Coordinate system” tab. This does not affect the searches that are performed in the field “name” of the CRS.
• In defining a new user's CRS with origin of latitude = 90.0 , the measurement of distances and perimeters does not work for areas located in the northern hemisphere.
• The search for name and area does not work correctly when several words are introduced in the search box.

The CRS (Cordinate Reference System) extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a CRS (Cordinate Reference System) extension for gvSIG 1.0.x in Windows XP, the folder could be C:\Program Files\gvSIG 1.0.x

The pilot application winner of the raster tender offered by the Regional Ministry of Infrastructure and Transport of Valencia (Spain). It can open new image formats and apply color palettes to a DTM, compute histograms, cut out raster layers. In addition, it comes with some new visualization filters. The pilot can be installed as a new extension over the current version of gvSIG.

The following organizations have participated in the raster pilot extension for gvSIG:

• Sponsor:
  
  • Regional Ministry of Infrastructure and Transport of Valencia (Spain)
• Developer:
  
  • Andago

BN6  (10-10-2007)

• The pilot has been updated to work on gvSIG 1.1.

BN7  (27-03-2008)

• The following problems have been fixed in this release:
  • Error while checking the prerequisites. The application launcher has found JRE 1.4 instead of JRE 1.5.

The raster pilot extension must be installed on the gvSIG version it was developed, which is indicated in the download table of the extension. This version of gvSIG must be correctly installed in the PC.

The installation steps are:

• Download the file from the web appropiate to the operating system and execute it.

If the installation process doesn’t automatically find the folder where the correct version of the gvSIG application is installed, it has to be manually indicated. For instance, in the case of a raster pilot extension for gvSIG 1.0.1 in Windows XP, the folder could be C:\Program Files\gvSIG 1.0.1