gvSIG bugs #1531: Intersection and union don't apply the output schema correctly - | gvSIG desktop 1 - gvSIG

gvSIG bugs #1531

Intersection and union don't apply the output schema correctly

Added by Antonio Falciano over 13 years ago. Updated about 12 years ago.

Status:

Fixed

% Done:

100%

Priority:

Normal

Assignee:

Francisco Puga

Category:

Target version:

Severity:

Add-on name:

Unknown

gvSIG version:

1.11.0

Add-on version:

gvSIG build:

1305

Add-on build:

Operative System:

Add-on resolve version:

Keywords:

geoprocesses, intersection, union

Add-on resolve build:

Has patch:

Yes

Description

The output schema of resulting layer of Intersection and Union geoprocesses don't match with the fields descriptions (length and precision) of the input layers. This issue is quite similar to #1530, however it involves another method of DefinitionUtils (mergeLayerDefinitions). The patch in attachment solves the problem.
See also this post on devel mailing list in which the issue :
http://joinup.ec.europa.eu/mailman/archives/gvsig-desktop-devel/2013-January/000748.html

Cheers,
Antonio

extGeoProcessing_patch_overlay_geoprocesses.txt - Patch of extGeoProcessing (Intersection and Union) (1.87 KB) Antonio Falciano, 01/04/2013 09:55 AM

History

#1 Updated by Antonio Falciano over 13 years ago

Target version set to 1.13.0

#2 Updated by Francisco Puga over 13 years ago

Thanks for the patch.

I change it a bit, because i think it can be a bit more concise. I rewrite it to use this:

int i = 0;
for (FieldDescription fieldDesc:firstDatasource.getFieldsDescription()) {
    fields[i++] = fieldDesc;
}
for (FieldDescription fieldDesc:secondDatasource.getFieldsDescription()) {
    fields[i++] = fieldDesc;
}
solution.setFieldsDesc(fields);