This node is currently not available in KNIME v5.2 — instead we’re showing this page for **KNIME v5.1**. You can use the version menu in the title bar to permanently switch your preferred version. This will also show the link to the update site.

This node constructs a contiguity spatial weights matrix from the input data.

- Geometry column
The name of the geometry column in the input data.

- ID column
Select the column which contains for each observation in the input data a unique ID, it should be an integer column. If 'none' is selected, the IDs will be automatically generated from 0 to the number of rows flowing the order of the input data. The IDs of this column must match with the values of the ID column selected in subsequent ESDA or spatial modeling nodes.

- Weights category
The type of spatial weights to construct. Defaults to 'Queen'. Other options are 'Rook', 'Binary Distance Band', 'Inverse Distance', 'Lattice', 'K nearest', 'Kernel', and 'Get spatial weights matrix from file'.

`Queen`

which will construct a queen contiguity weights matrix, is more robust and more suitable for areal unit data. The queen criterion is somewhat more encompassing and defines neighbors as spatial units sharing a common edge or a common vertex.- The
`Rook`

criterion defines neighbors by the existence of a common edge between two spatial units. Therefore, the number of neighbors according to the queen criterion will always be at least as large as for the rook criterion. - When choosing
`K nearest`

, select the nearest number 'Nearest k' in the following options. K-nearest are often used for point data. - When selecting
`Binary Distance Band`

, please select the distance threshold 'Threshold' in the following options. - When selecting
`Inverse Distance`

, please select the distance threshold 'Threshold' and the corresponding power 'Power' in the following options. - When 'Your own' is selected, please enter the path of the spatial weights matrix in CSV format in the following options.
- More details about spatial weights, please see the GeoDa center website.

- Order
The order of the weight matrix is 1 by default. Users can change the order of the weights, higher order weights will treat further units as neighbors.

- Threshold for Inverse Distance or Binary Distance Band
The distance threshold for constructing binary distance band and inverse distance weights. Defaults to 1

- Rows for Lattice
The number of rows for constructing a lattice spatial weights matrix. Defaults to 5.

- Columns for Lattice
The number of columns for constructing a lattice spatial weights matrix. Defaults to 5.

- Nearest k
The number of nearest neighbors to use for constructing k-nearest neighbors weights. Defaults to 4.

- Kernel K
The number of nearest neighbors to use for determining the bandwidth in kernel weights. Defaults to 12.

- Kernel type
The type of kernel to use in constructing kernel weights. Defaults to 'triangular'

- Kernel bandwidth
The type of kernel bandwidth to use in constructing kernel weights. The bandwidth of the kernel. The default is fixed. If adaptive then bandwidth is adaptive across observations.

- Get spatial weights matrix from file
The file path of a user-defined spatial weights matrix in CSV format. Defaults to ''. Please enter the path of the spatial weights matrix in CSV format in the following options. The weights matrix must be in matrix format and in the order of the samples.

- This node has no views

- No workflows found

- No links available

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

To use this node in KNIME, install the extension Geospatial Analytics Extension for KNIME from the below update site following our NodePit Product and Node Installation Guide:

v5.1

A zipped version of the software site can be downloaded here.

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud
or on-premises – with our brand new **NodePit Runner**.

Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.

**Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.**