These are the rules a reviewer applies to your submission. They are published so that you can apply them first.
Every article and news post must clear the same baseline before it can be approved.
GIS-centred — The subject is geographic information systems, spatial technology, remote sensing, cartography or surveying.
Technically accurate — Terminology, software capabilities and data interpretation are checked, and corrected where they are wrong.
Original — The writing is yours. Synthesising sources is welcome; copying them is not.
Readable — A GIS student can follow it. Jargon is fine; unexplained acronyms are not.
Structured — Headings, short paragraphs and visual breaks. The block editor makes this cheap.
GIS is exact, and these are the mistakes reviewers find most often.
| Checked | What the reviewer verifies |
|---|---|
| Coordinate systems | Is the CRS named correctly, and is the EPSG code right? |
| Software versions | Does the feature exist in the version you describe? |
| File formats | Are the format's limits stated accurately — Shapefile field names, GeoJSON structure? |
| Terminology | Raster and vector, datum and projection, resolution and scale — used precisely? |
| Data sources | Are cited datasets real, linked, and reachable by a reader? |
The platform is bilingual by design. Both languages is the preference, not the requirement.
Arabic and English — Reaches the whole readership. Write one version, then adapt rather than translate literally.
English only — Published as is. Readers are served the version that exists.
Arabic only — Right for work aimed squarely at the regional GIS community.
What happens between submit and publish.
Submission
You move the piece to Under review. The editorial queue picks it up.
Assignment
It goes to a reviewer who works in that domain, not to whoever is free.
Review
Accuracy, structure, taxonomy placement and clarity, usually within a few business days.
Decision
Approved and published, or returned with notes on what to change.
Approved
The piece is published, attributed to you, and findable at its taxonomy path.
Returned
It goes back to your drafts with specific notes. Revise and resubmit; there is no limit on attempts.
The Studio guide covers the editor itself; the contributor guide covers getting access.