Jeem Replication Package

Replication Package (jeem-replication-package)

When to trigger

• The paper is heading to submission or acceptance and the data/code deposit is not assembled
• The analysis uses restricted or proprietary environmental data (utility, satellite, admin pollution, parcel) and you must document a replication path you cannot fully share
• The Editor must be told at submission that the data-availability conditions cannot be fully met
• Code reproduces exhibits manually rather than from a single master script

JEEM's replication expectation

JEEM has a long-standing policy: all data used must be clearly documented, computational methods explained in enough detail to permit replication, and the data made available to any researcher for replication — and the Editor must be notified at submission if these conditions cannot be met (检索于 2026-06；以官网为准; re-check the current guide for authors, as Elsevier data-availability and code-sharing requirements are tightening). Environmental papers routinely hit this wall because the data are spatial, sensor-derived, or proprietary; the package must show a credible reproduction path even when raw data cannot be posted.

Why environmental papers fail replication more often

Three structural features make environmental replications fragile, and the package must address each head-on. First, versioning: satellite and weather products are reissued (collection upgrades, reanalysis vintages), so a result is irreproducible unless the exact version is pinned. Second, spatial operations: geocoding, reprojection, and spatial joins are easy to do interactively and impossible to reproduce unless scripted with the CRS recorded. Third, proprietary inputs: utility, parcel, and licensed sensor data often cannot be posted at all, so the package must substitute derived/synthetic data and a precise access protocol. A package that ignores these three will pass a casual check and fail a serious one.

Building the package

1. One master script reproduces everything. A single entry point (e.g., make / run_all) that goes raw → cleaned → every table and figure, with no manual steps. Map each exhibit to the script that builds it.
2. Document every data source by provenance. For each source: name, version/vintage, access date, license, geographic unit and CRS, and exactly how it was obtained — pollution monitors (EPA AQS), satellite products (MODIS/Sentinel, with retrieval algorithm and grid), weather (PRISM/ERA5), parcel/assessor, permit registries, survey instruments.
3. Handle restricted data explicitly. If raw data cannot be shared (utility billing, confidential parcel, licensed satellite), provide the derived/aggregated data that can be, the exact access protocol for the rest (provider, application, cost, embargo), and synthetic or sample data so the code runs end-to-end.
4. Preserve the spatial pipeline. Geocoding, projection, buffer construction, and spatial joins are where environmental replications break — script them and record CRS/version of every spatial operation; do not rely on a one-off GIS click-path.
5. Pin the computational environment. Software versions, packages/seeds, and any HPC/cluster details; environmental papers with weather grids or large rasters need runtime and memory noted.
6. For stated-preference work, include the full survey instrument, the experimental design (choice sets, blocking), and the elicitation script.

Notifying the Editor about data constraints

JEEM's policy requires telling the Editor at submission if the data-availability conditions cannot be fully met — do not wait for acceptance. Draft a short data-availability statement that says, per source, whether it is bundled, derived-and-bundled, or restricted-with-access-protocol, and name any source you genuinely cannot share with the reason (license, confidentiality). Pair every restricted source with what you can provide: aggregated data, the code that processed it, and synthetic/sample data so the pipeline runs. A candid, complete statement at submission is far better received than a discovered gap at the replication check.

Checklist

• A single master script reproduces every table and figure from raw inputs, no manual steps
• Each exhibit is mapped to the code that produces it
• Every data source documented: provenance, version, access date, license, unit, CRS
• Restricted data: derived data shared, exact access protocol given, sample/synthetic data lets code run
• Editor notified at submission if data-availability conditions cannot be fully met
• Spatial pipeline (geocode, projection, buffers, joins) scripted with CRS/versions recorded
• Software versions, package versions, and seeds pinned; runtime/memory noted for large grids
• Survey instrument and choice-experiment design included for stated-preference papers