Multiscale Spatial Patterns in Giant Dike Swarms Identified through Objective Feature Extraction Datasets

S1 - Linked dike clusters for the Columbia River Flood Basalt group including the four identified subswarms: Chief Joseph, Monument, Ice Harbor, and Steens as compiled in Morriss et al., 2020. This dataset uses the a UTM Zone 11N projection (EPSG:26911).

S2 - Linked dike clusters for the Deccan Traps including the four identified subswarms: Saurashtra, Narmada-Tapi, Central and Coastal. Due to their overlap Central and Coastal Swarms have been combined in this dataset into the Central Swarm. This dataset uses the a WGS 84 projection (EPSG:3857). 

S3 - Dike segment data for Spanish Peaks and Dike Mountain located in the Rio Grande Rift of Colorado. This dataset was digitized using QGIS based on the map by Johnson (1961). This dataset uses the a UTM Zone13N projection (EPSG:32613). The file includes the start, end points, and midpoints of the dikes; segment length; calculated $\rho$ and $\theta$ for the Hough Transform; the origin used for the Hough Transform which is different for each subswarm (xc,yc); dike rock type if known; and a unique identification calculated based on the start and endpoints. This dataset has been preprocessed to remove curving dikes and is the data set used to produce later products (Data set S4). 

S4 - Linked dike clusters for the Spanish Peaks and Dike Mountain. This dataset was produced using the Agglomerative Clustering algorithms using the parameters set in Table 1. This dataset uses the a UTM Zone 13N projection (EPSG:32613). 

These datasets were produced using the Agglomerative Clustering algorithms using the parameters set in Table 1. The datasets are in the format of a CSV file but can be read into GIS programs using Well Known Text (WKT) linestring. TThe file includes the start and end points of the average line in the cluster and it's mid points, cluster length and width (Xstart, Xend, Xmid, Ymid, in meters and UTM coordinates, Dike Cluster Width  or R\_Width, Dike Cluster Length or R\_Length all in meters); calculated average $\rho$ and $\theta$ for the Hough Transform $\rho$ units measured in meters, $\theta$ units measured in degrees, unless otherwise stated); the origin used for the Hough Transform which is different for each subswarm ($xc$,$yc$, meters in UTM coordinates); average slope and intercept (AvgSlope, AvgIntercept meters); range and standard deviation for $\rho$ and $\theta$ for all objects in the cluster ($\rho$ units measured in meters, $\theta$ units measured in degrees); cluster size (Size); sum of segment lengths in a cluster (SegmentLSum, meters); whether the cluster crosses between negative and positive values (ClusterCrossesZero, boolean); overlap as calculated in the main text where the length of overlap is normalized by the sum of segment lengths in a cluster; maximum number of overlapping segments (nOverlapingSegments); twist angle which is the difference in angle betweeen the average cluster line and the average line formed by cluster midpoints (EnEchelonAngleDiff, degrees); the p-value for the midpoint line fit of the segments where $p<0.05$ is considered to be a significant fit (EEPValue); the maximum, median, and minimum segment nearest neighbors distances in the cluster which is calculated using the cartesian midpoints of each segment and normalized by the Cluster Length (MaxSegNNDist, MedianSegNNDist, MinSegNNDist); characterization of each cluster as filtered or not, filtered clusters are of size greater than $3$ and have a MaxSegNNDist of less than $0.5$ (TrustFilter, boolean); the date edited (Date\_Changed), and the clustering parameters used for each cluster (Rho\_Threshold in meters, Theta\_Threshold in degrees) and a unique identification calculated based on the start and endpoints (ClusterHash).