The BORDERSCAPE Project WebGIS Repository
Bibliographic record
Abstract
The BORDERSCAPE Project WebGIS Repository: Description of Contents Data are stored in a folder named Borderscape_WebGIS_Data_v4.0.Singular files are:“READ ME.txt”: A document describing the contents of this repository.“sites.geojson”: A GeoJSON file with information on each archaeological site included in the webGIS.“sites.csv”: The list of archaeological sites and their attributes from which the “sites.geojson” file was built for the webGIS."Borderscape Archaeological Sites.xlsx":The list of archaeological sites and their attributes. “flooding-nile.geojson”: A GeoJSON with information on Nile flood levels at 86m and 94.5m ASL.“Bibliography.txt”: A bibliography with all of the sources abbreviated in the “sites.csv” file.“MergedCoronasFreeGR.tif”: A GEOtif of the georeferenced CORONA imagery showing the Lower Nubian landscape prior to the construction of the Aswan High Dam. A folder named “Metadata” contains ZIP archives with the shapefiles data:“Borderscape Archaeological Sites.zip”: A zip archive of a shapefile showing all of the archaeological sites and their attributes used in the webGIS.“Borderscape Archaeological Sites_Phase1.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 1.“Borderscape Archaeological Sites_Phase2.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 2.“Borderscape Archaeological Sites_Phase3.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 3.“Borderscape Archaeological Sites_Phase4.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 4.“Borderscape Archaeological Sites_Phase5.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 5.“Borderscape Archaeological Sites_Phase6.zip”: A zip archive of a shapefile showing archaeological sites used in the webGIS from Phase 6.“86m _flooding contour.zip”: A zip archive of a shapefile showing flooded areas at 86m ASL.“94.5m_flooding contour.zip”: A zip archive of a shapefile showing flooded areas at 94.5m ASL.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.025 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.009 | 0.016 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.008 | 0.007 |
| Open science | 0.004 | 0.007 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.249 | 0.271 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".