gvSIG bugs #1920: Adapting to PostGIS 2.0 - Application: gvSIG desktop - gvSIG

gvSIG bugs #1920

Adapting to PostGIS 2.0

Added by Ignacio Brodín almost 11 years ago. Updated over 10 years ago.

Status:

Closed

% Done:

Priority:

Normal

Spent time:

Assignee:

Ignacio Brodín

Category:

Database

Target version:

Severity:

Add-on version:

gvSIG version:

2.0.0

Add-on build:

gvSIG build:

2217

Add-on resolve version:

Operative System:

Add-on resolve build:

Keywords:

Proyecto:

Has patch:

Hito:

Add-on name:

Unknown

Description

Now, vector layers in PostGIS 2.0 cannot be loaded in gvSIG v2.

History

#1 Updated by Ignacio Brodín almost 11 years ago

Steps to migrate:
1- Adapt old functions that have been deprecated to the new ones
2- Modify the WKB reader to load 3D geometries. Be careful, the 2D layers are loaded with two dimensions in the database but 3D layers with four dimensions 3D+M. Now gvSIG 2 does not have the M dimension.
3- Modify the getFeatureType of this provider. Now, if the layer is 3D+M it will return the type GEOM3DM. This type is defined, but does not exist an implementation, so gvSIG crashes.
4- Now, the writer send 2D geometries using the WKB writer in JTS library. We have to send geometries in 3D if the layer is edited.

#2 Updated by Ignacio Brodín almost 11 years ago

I tested the result in PostGIS 2.0 and 1.5 editing layers polylines and polygons 2D 3D. The Z coordinate cannot be change but if you modify a geometry, preserve the old value. If you create new geometries the Z is always zero.

gvsig-desktop:r40414
gvsig-desktop:r40415
gvsig-desktop:r40416
gvsig-desktop:r40417
gvsig-desktop:r40418
gvsig-desktop:r40419

#3 Updated by Ignacio Brodín almost 11 years ago

Status changed from New to Fixed

#4 Updated by Cesar Ordiñana almost 11 years ago

Nacho, thanks for adding that new capability to gvSIG! It is a very nice addition, as each day more users are using the PostGIS 2.0 version, and I think it is a must.

Only a small note: in the r:40415 of the WKBParser3.java file, you added a System.out.println sentence. Please, remove it or replace it with a call to a SLF4J logger call whenever you can.