svn-gvsig-desktop / tags / v1_1_Build_1012 / extensions / extGeoProcessing / src / com / iver / cit / gvsig / geoprocess / impl / spatialjoin / resources / description_en.html @ 12987
History | View | Annotate | Download (962 Bytes)
1 | 6749 | azabala | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
---|---|---|---|
2 | <HTML>
|
||
3 | <HEAD>
|
||
4 | <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252"> |
||
5 | <TITLE>Spatial Join</TITLE> |
||
6 | </HEAD>
|
||
7 | <BODY LANG="es-ES" DIR="LTR"> |
||
8 | <P>
|
||
9 | <FONT COLOR="#800000"> |
||
10 | <B>Spatial Join</B> |
||
11 | </FONT>
|
||
12 | </P>
|
||
13 | <P>
|
||
14 | This geoprocess transfer attributes from a source layer to a target layer (very similar to an |
||
15 | alphanumerical join). The difference with a traditional join is that the transfer criteria is not |
||
16 | the value of one (or many) given attributes. The criteria to transfer attribute values is spatial: intersection or proximity. |
||
17 | </P>
|
||
18 | <P>
|
||
19 | If users select intersection like transfer criteria, each feature of the target layer could intersect |
||
20 | many features of the source layer (a 1-N spatial relationship). |
||
21 | <br>
|
||
22 | If users select proximity (nearest neighbour) we have a 1-N spatial relationship. |
||
23 | </P>
|
||
24 | |||
25 | <P>
|
||
26 | <IMG SRC="spatialjoindesc.png" NAME="Imagen1" ALIGN=LEFT BORDER=0> |
||
27 | </P>
|
||
28 | |||
29 | </BODY>
|
||
30 | </HTML> |