Spatial analysis
How a variable varies across regions or places: maps from the data and recorded boundaries, Moran's I with permutation inference recomputed by e2er, optional local clusters (LISA), with the boundaries' source, CRS and weights checked before the analysis.
Where it sits
left: what it builds on · right: what builds on it · pale: exampleBy e2er authors
How studies reach it
No published study reaches it yet.
Disciplines it reaches
No study reaches it yet.
Solid: published studies. Light: examples.
Computed from the records on this site: what each study, template and specialist names as used, which study extends which, and who authored what. 0 studies in total.
- Input
- A question about how a variable varies across places, data by region and their boundaries
- Output
- Maps, Moran's I with permutation inference and optional local clusters, as a draft paper with a dossier
- At the end
- When any run ends, e2er builds the PDF, writes the audit trail and the structured export, and pushes to GitHub if you set that up.
Sources
- Methods
P. A. P. Moran (1950). Notes on Continuous Stochastic Phenomena. Biometrika 37(1/2), 17-23.
Luc Anselin (1995). Local Indicators of Spatial Association—LISA. Geographical Analysis 27(2), 93-115.
Luc Anselin (1988). Spatial Econometrics: Methods and Models. Springer Netherlands (Kluwer), Studies in Operational Regional Science.
Arthur Getis and J. K. Ord (1992). The Analysis of Spatial Association by Use of Distance Statistics. Geographical Analysis 24(3), 189-206.
Stan Openshaw (1984). The Modifiable Areal Unit Problem (Concepts and Techniques in Modern Geography 38). Geo Books, Norwich. ISBN 0-86094-134-5 (no DOI).
Steps
Greyed steps do not run in the selected mode.
- 1 checkBoundaries, CRS and weights checkAfter the data are loaded. The data architect writes spatial_design.json (units, boundaries and their source, CRS, spatial weights; schema in skills/files/data/spatial-statistics.md). The check stops the run when the boundaries' source is not recorded, the CRS is missing or does not fit the coordinates, a unit of the data has no geometry and is not listed with a reason, or the weights are not documented. A failed check sends the data architect back once with the reasons, then stops the run..
- 2 checkMoran's I and maps checkAfter the analysis, before drafting. The analysis writes the units and values it used (spatial_units.csv) and its weights (spatial_weights.csv); the check recomputes every Moran's I from them, requires permutation inference, and builds a map figure for every map the results name (choropleth or categories, from the boundaries in data.db; rendered by src/core/renderer/maps.py). A failed check sends the econometrics specialist back once..
- 3 specialistsDesign, data, estimation and draft
- 4 specialistsImprove until it stops getting better
- 5 checkEstimation check
- 6 specialistsSelf-critique
- 7 specialists, parallel
- 8 reviewers, parallelReview panel
- 9 specialistsRevision
- 10 specialistsReplication package
Technical details
Template id spatial-analysis · file pipelines/spatial-analysis.toml, checked against pipeline.schema.json.
| Step | Id in the template file | Specialists |
|---|---|---|
| 1. Boundaries, CRS and weights check | spatial_design_gate | |
| 2. Moran's I and maps check | spatial_results_gate | |
| 3. Design, data, estimation and draft | initial | idea_developer, literature_scanner, data_architect, identification_strategist, econometrics_specialist, data_analyst, paper_drafter |
| 4. Improve until it stops getting better | iterative | |
| 5. Estimation check | estimation_gate | |
| 6. Self-critique | self_attack | self_attacker |
| 7. Polish | polish | polish_numerics, polish_bibliography |
| 8. Review panel | review | methods_reviewer, data_reviewer, plausibility_reviewer, writing_reviewer, technical_reviewer |
| 9. Revision | revision | revisor, patch_revisor |
| 10. Replication package | replication | replication_packager |
At the end (finalize): compile, audit_export, github_push, structured_export. Modes: single_pass, iterative.
More
Description
Data model- Discipline
- General
- Method family
- Empirical (quantitative)
- Design
- not specified
- Research stage
- ReviewRevision and editingReplication
- Authors
- e2er authors (Software, Methodology)
- Usage
- not used in published research yet
- Source
- e2er repository · pipelines/spatial-analysis.toml · @d8fd8ab
- Record
- template:spatial-analysis · JSON
Solid tags are declared by the source or mapped from its terms; dashed tags are inferred by a published rule. Hover a tag for its provenance.
Versions and evaluations
One version, unreleasedOne version so far: pipelines/spatial-analysis.toml in e2er 0.16.1. No evaluation records exist yet.
Connectors this template can use
What a run of this template can reach outside your machine, and what each sends out.
Checks on this template
- ✓Output contracts · Every step produced the artifact it declared, in the declared form
Required of every template. - ✓Execution reliability · Analysis code ran and wrote a parseable, non-empty result
Required of every template. - ○Numbers · Every number in tables and text matches the output of executed code
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Citations · Every reference resolves to an existing publication via OpenAlex, Semantic Scholar or Crossref
Proposed. Proposed for the floor; runs log it but may not block on it. - ○Verbatim passages · Every claim about a source points to a passage found word for word in that source
Proposed. Proposed for the floor; runs log it but may not block on it.
Runs of this template
No runs yet.
Use it
Install e2er as described on the Install page, then start a run:
e2er run "<your research question>" --template spatial-analysisFrom e2er 0.16.1. Get started goes from install to publish.
On e2er.org
Loading…
Discussion
Loading…