Filters
Selected Filters
None
Available Filters
Modern Countries and Continents
File Formats
Network Tags
Network Topics
Node Topics
Edge Topics
Directionality
Weighted
General

Search Fields

The following fields can be used for targeting a specific field as described in the query syntax below.

canonicalCitation
collectionTags
description
fileFormats
id
name
tags.txt
authors.firstName
authors.lastName
authors.orcidId
construction.additionalComments
construction.description
construction.sources.sourceTypes.txt
license.licenseId
relatedPublications.canonicalCitation
structure.directionality
structure.weighted
topic.edgeAttributes.txt
topic.edgeTopics.txt
topic.modernCountriesAndContinents.name
topic.networkTopics.txt
topic.nodeAttributes.txt
topic.nodeTopics.txt

Query Syntax

TitleOperatorExampleDescription
Phrase / Exact match
""
"Roman"
"Roman Road Network"
The term or phrase must be matched exactly (case insensitive) to get a match.
Field Search
FIELD_NAME:()
name:(Roman Road Network)
name:("Roman Road Network")
Field searches makes it possible to narrow the search to a specific field instead of searching all fields. The same operators as used in a normal search can be applied to field searches.
Wildcard
?, *
Roma?
Ro*
Search words including or ending with and an unknown set of characters. The wildcard
?
matces a single character and
*
matches 0-n characters.
Fuzzy
~
Roma~
Squire~
Find words which are similar (spelling wise) to the given word. Good for finding misspelled words. The examples could e.g. result in "Roma, Roman, Rome" or "Squire, Super, Squibb".
Given the length of the word different rules apply *:
[0-2]:
No fuzzyfication is applied - the word must match exactly
[3-5]:
One edit** is allowed
[6-*]:
Two edits** are allowed
* The default rules for edits can be overwritten by applying one of [0, 1, 2] after the "~", where the number specifies the number of edits allowed.
** An edit is an insertion, deletion or substitution of a character.
Must
+
+Roman Road +Network
+name:(Roman Road)
+"Roman Road" Network
Express which terms must be present to get a match:
+Roman Road +Network
Both "Roman" and "Network" must be present, "Road" is not required but would make a better result if present
+name:(Roman Road)
One of the terms must be present in the title field (If all terms must be present prefix each term with a "+")
+"Roman Road"
The exact phrase must be present
Must Not
-
-Roman Road
-name:(Roman Road)
-"Roman Road" Network
Express which terms must not be present to get a match:
-Roman Road
"Roman" must not present
-name:(Roman Road)
One of the terms must not be present in the title field (If all terms must not be present prefix each term with a "-")
-"Roman Road"
The exact phrase must not be present
Grouping
( )
(+Roman +Road) (+Ancient +Network)
Group expressions together to form sub-queries. The Example reads: match ("Roman" and "Road") or ("Ancient" and "Network").
time
1 - 1 / 1
Authors
Maintainers
Formats
xls, xlsx
Nodes
1549
Edges
1549
Years
-2200-1400
Access
|
Added
2025-12-01
23

"Archaeologists use differences in metals from burial contexts to identify variation in social inequalities during the European Bronze Age. Many have argued that these social inequalities depended on access to, and control of, trade routes. In this paper, I model critical gateways in the Tisza river—a river system in the Carpathian Basin that might have enabled privileged access to metal in some areas but not others. I then evaluate the concentration of metal on different topological nodes of the river network in an attempt to understand what best explains the distribution of metals across this landscape. I do this by describing Bronze Age metal consumption and display in cemeteries from four micro-regions of the Tisza, and compare them with network ‘betweenness centrality’ values for locations along the river. I find support for the argument that favourably located river nodes had better access to metal in the earlier part of the Bronze Age."

From https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0238526

Tags
burials
metal
rivers
Modern Countries and Continents
Hungary
Structure
Directionality
undirected
Weighted
no
Hypergraph
no
Longitudinal
no
Multigraph
no
Multilayer
no
Multipartile
-
Probabilistic
no
Self Loops
no
Signed
no
Spatial
yes
Canonical Citation
Duffy PR (2020) River networks and funerary metal in the Bronze Age of the Carpathian Basin. PLoS ONE 15(9): e0238526. https://doi.org/10.1371/journal.pone.0238526
Funding
"This research was supported by the Social Science and Humanities Research Council of Canada (756-2011-0060) (www.sshrc-crsh.gc.ca) and the National Science Foundation (BCS-1460820, BCS-1226439) (www.nsf.gov).The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript."
Network Topics
burials
metal
rivers
Node Topics
river
Edge Topics
river
Node Attributes
latitude
longitude
Edge Attributes
line
Uncertainties
Nodes
no
Edges
no
Node Attributes
no
Edge Attributes
no
Statistics
Avg. Clustering Coefficient
-
Avg. Degree
-
Construction

"For the river network, nodes are defined when two or more reaches come together, or if two or more rivers drain into a marsh, and come out as a single reach downstream. The hydrology at both scales was digitized into polyline shapefiles and then combined by attaching vector lines of both scales, using the lower resolution data where the higher resolution data was not available . I then simplified the river geometry into single polylines breaking only at river confluences, eliminating any trace of the vectorization process. These confluences would become one kind of node in the river network."

"Adding nodes to the river polylines was accomplished in two steps using ET Geowizards, first by splitting the polyline into 10 km segments and then by creating a point shapefile comprised of the beginning and ending vertices of the polyline segments using ‘Renode Polyline’ . I then obtained the geographic coordinates (easting and northing in meters, from a UTM projection) and elevation (masl, from a SRTM raster) of each point in the shapefile, which serve as attributes for the nodes in network software (4).

In the process of creating a node shapefile, the ‘Renode Polyline’ Wizard application in ET Geowizards, also adds two columns to the original polyline shapefile, the ‘ET_FNode’ and ‘ET_TNode’ columns. These values refer to the nodes in the created point shapefile, essentially a list of edges for an adjacency matrix (that is, two columns specifying the connected nodes). This was exported as a text file for manipulation in UCINET.

The next step is the creation of a distance matrix for a vector of XY (easting and northing) pairs. This was accomplished by taking the locational coordinates of each river node from the ArcGIS output and producing a matrix using the stock dist() function in R. The output is a matrix in meters between each node.

The remaining operations were carried out mostly in Ucinet and NetDraw, simple network software available for matrix analysis and display (5). The edges of the river network were imported to Ucinet and then exported as a 2D array for manipulation in Microsoft Excel. In this matrix, river nodes are either connected (1) or they are not (0). To achieve a matrix with connections identifiable as river or land, however, a multiplier matrix was created in Excel. In this ‘Inverse’ matrix, produced using the ‘Find and Replace’ function in Excel, river connection cells are zero and all other cells are one. Using the ‘Command line / matrix algebra’ tool in Ucinet, the ‘Inverse’ matrix is multiplied by the distance matrix to cancel out the distance values where there are river connections. The original river matrix is then added to the distance matrix using the ‘Command line / matrix algebra’ tool. In this network, all nodes are connected to each other by ‘1’ or higher values representing the Euclidean distance between nodes in meters."

Sources

Farr TG, Rosen PA, Caro E, Crippen R, Duren R, Hensley S, et al. The Shuttle Radar Topography Mission. Reviews of Geophysics. 2007;45(2).

5.

Source Types
map
publication
software
topography

Bak Bl. Magyarország történeti topográfiája : a honfoglalástól 1950-ig. Budapest: Historia- MTA Történettudomány Intézete; 1997.

Source Types
publication

Györffy G. Az Árpád-kori Magyarország történeti földrajza. Budapest: Akadémiai Kiadó; 1966.

Source Types
publication

Gyucha A, Duffy PR, Frolking T. The Körös Basin from the Neolithic to the Hapsburgs: Linking Settlement Distributions with Pre-Regulation Hydrology Through Multiple Data Set Overlay. Geoarchaeology. 2011;26(3):293-419.

Source Types
map
publication

Borgatti SP, Everett MG, Freeman LC. Ucinet for Windows: Software for Social Network Analysis. Harvard, MA.: Analytic Technologies; 2002.

Source Types
software
1 - 1 / 1