Data and Reproducibility Policy
Scientific conclusions must be based on traceable data and sufficiently detailed descriptions of methods. This policy establishes requirements for materials needed to verify results, their deposition, citation and preservation, as well as procedures for justified restrictions on access.
Contents
- Purpose and scope
- Data and documentation requirements
- Description of methods and verifiability of analysis
- Deposition, versions and availability periods
- Data and code availability statement
- Justified restrictions and controlled access
- Software code, models and AI
- Citation and licensing
- Verification during manuscript review
- Preservation, updates and enquiries
01. Purpose and scope
The policy of “Geodesy, Cartography and Geoinformatics” applies to raw and processed data, software code, computational models, protocols, images, maps and other materials on which an article's conclusions are based. It covers both original and reused data, including materials from special issues and supplementary files.
Reproducibility here means the ability to verify how the reported results were obtained using the described data, methods and computational procedures. Repeating a study with new observations constitutes an independent verification and does not replace the provision of materials from the original work. Authors identify limitations on exact replication of calculations, such as algorithmic randomness or the unavailability of a historical version of an external service.
Research articles must include a minimally sufficient set of materials for verifying their conclusions. As a general rule, this set is made openly available by publication; justified restrictions are considered under this policy. Applying the FAIR principles means ensuring that materials are findable, accessible, interoperable and reusable; it does not require unconditional disclosure of protected information.
02. Data and documentation requirements
The minimally sufficient set includes data needed to verify the principal calculations, tables, figures and conclusions, together with information linking them to original observations. Final averages or images of graphs alone are insufficient if they do not enable the analysis to be checked. Materials from the entire project that are unrelated to the publication need not be deposited.
- For field and laboratory studies: observations for individual experimental units, identifiers of sites and replicates, dates, measurement conditions, units of measurement, and information on instruments and calibration needed to assess quality.
- For geospatial and temporal data: source, coverage, coordinate reference system, spatial and temporal resolution, time zone where relevant, handling of missing values and transformations. Sensitive coordinates are protected under controlled-access rules.
- For computational studies: input data used, significant output results, parameters and configuration files that connect calculations to the published conclusions.
- For systematic reviews and quantitative synthesis: search strategy and date, selection criteria, list of included sources, extracted values and calculations; full-text publications belonging to others must not be distributed without the necessary rights.
Files are accompanied by instructions describing their structure, variables, codes, units, missing-value indicators, processing and connection to the article. Widely used machine-readable formats are preferred; for specialised formats, the required software and method of reading are specified. Tables must not be provided solely as scans where original numerical data are available.
03. Description of methods and verifiability of analysis
Methods describe the study design, experimental conditions, criteria for including and excluding observations, sample size, independent replicates, handling of missing values and outliers, computational formulas, statistical procedures and assessment of uncertainty. Repeated technical measurements are not presented as independent experimental units. Decisions made after viewing the results are identified if they affect interpretation.
For hydraulic, hydrological and other models, initial and boundary conditions, parameters, calibration, validation and significant assumptions are reported. Authors explain the separation of calibration and validation data and the limits of transferring conclusions to other sites, seasons and operating conditions. Key calculations must be traceable, and rounding and acceptable computational differences must be understandable.
If a preregistered protocol or analysis plan existed, a link and any deviations from it are provided. Late registration is not presented as preregistration. Negative results and checks that are significant for the stated conclusion must not be concealed to make it appear stronger. These requirements do not impose mandatory registration of every engineering study.
04. Deposition, versions and availability periods
At submission, the data and analysis materials must be accessible to editors and reviewers through secure means. By publication, the open portion of the minimum set is deposited in an appropriate subject-specific, institutional or general-purpose repository. Authors select a service with clear preservation terms, metadata, version management and a persistent identifier, preferably a DOI. The repository's name does not replace verification of its actual capabilities.
Links must lead to the specific dataset and version used, not merely to a homepage. For changing external databases, authors indicate the version or extraction date and exact criteria used to obtain the data. Where rights permit, the data snapshot used is preserved. A code-development repository, personal website or temporary cloud link does not, in itself, replace an archived version of the research materials.
The deposition plan and permissible exceptions are agreed before article acceptance. A temporary private link may be used for peer review and is replaced by a permanent link before publication. An embargo is permitted only for a specific justified reason, with an agreed end date and published access conditions. An intention to prepare further articles is not, in itself, sufficient justification.
Small datasets may be placed in supplementary files only with editorial agreement, provided they are available alongside the article, unambiguously identified and suitable for reanalysis. A repository remains the preferred option. Simply uploading a file to OJS for peer review does not constitute open deposition.
05. Data and code availability statement
Every article contains a separate “Data and Software Code Availability” statement, submitted with the manuscript and updated before publication. It lists the main categories of materials, their location, version or identifier, conditions of use and all restrictions. The data statement must be consistent with the methods section and the declaration of AI use.
- Open materials: “Data [description] and code [description, version] are deposited in [repository] at [DOI or permanent link]; terms of use: [licence].”
- Third-party materials: “The study used [dataset, provider, version/date]. Access is provided through [source and conditions]. Derived materials and code are available at [location] or restricted for [specific reason].”
- Controlled access: “Materials [description] are not publicly available because of [grounds]. The custodian is [organisation/unit]; requests are accepted through [contact or page]. Request assessment conditions are [criteria, procedure and response period]. The open portion is available at [location, if applicable].”
- Materials entirely within the article: “All data necessary to verify the reported analysis are included in the article and [specifically identified appendices].” This statement is permissible only where the materials are genuinely complete and the arrangement has been agreed under the preceding section.
- No data: “No new data were generated and no existing datasets were analysed in this work. Data availability is not applicable.” This option must not be used if the work reanalyses third-party data or generates modelling results.
Code availability, or the absence of research software code, must be stated separately. Examples are completed according to actual circumstances; unverified DOIs and promises of future deposition must not be presented as existing access. The phrase “available from the author upon request” is insufficient without an explanation of the restriction and procedure.
06. Justified restrictions and controlled access
Grounds may include protection of research participants and personal data, specific safety or security risks involving protected facilities, third-party rights, contractual obligations and other applicable restrictions. Justification is submitted to the editor at submission. The word “confidential” alone is insufficient; supporting documents may, where necessary, be examined without being made public.
Where possible, authors provide a safe open portion comprising de-identified or aggregated data, metadata, variable descriptions and code. For precise coordinates of water-management facilities or farms, the adequacy of a generalised location is assessed. Generalisation must not present modified data as original or conceal significant limitations of the analysis. Applicable rights and agreed governance conditions are respected for community data.
For controlled access, the custodian, permitted purposes, applicant requirements, decision procedure, expected response time and grounds for refusal are defined in advance. Conditions must not depend arbitrarily on whether the applicant agrees with the article's conclusions; coauthorship must not be made a condition of access. If transfer is entirely impossible, this is stated explicitly rather than making a promise that cannot be fulfilled.
The editor assesses whether sufficient independent verification is possible, including permissible secure inspection or assessment by a qualified independent specialist. An exception is recorded with its reason and any available alternative. If key conclusions cannot be reliably verified, the manuscript may be rejected; the journal does not require violations of law, participant consent or the data owner's rights.
07. Software code, models and AI
Authors provide their own code, scripts, spreadsheet formulas and settings that materially affect the results. Software and dependency versions, execution instructions, input and output files and, where necessary, the computing environment, random-number generator seed and hardware requirements are specified. The instructions must enable a specialist to understand the analysis workflow without personal explanations from the author.
The use of commercial or proprietary software is not prohibited in itself. The exact version, available settings, means of lawful access to the program and verification limitations are specified; original scripts and input data are made available within the rights held by the authors. Where a key algorithm is inaccessible, the editor assesses the adequacy of alternative verification. Full reproducibility must not be claimed when significant components are unavailable.
For machine learning, significant information about training, validation and the model version used is preserved, including, where needed and permitted by rights, model weights, prompts and rules for processing responses. Measured, reconstructed and synthetic values are identified separately. Detailed requirements for AI disclosure and permissible uses are established in a separate policy.
08. Citation and licensing
Datasets, models and software products used are cited in the text and reference list as independent research materials. Where possible, citations include the creator, year, title, version, repository or provider, and DOI or another persistent identifier. A citation to an article describing a dataset supplements but does not replace identification of the data actually used.
Clear reuse conditions are provided for each deposited object. Authors select an open licence for their own data where they hold the relevant rights; an appropriate software licence is used for code. The article's CC BY 4.0 licence does not automatically relicense a separately deposited dataset, program or third-party material. Restrictions and exceptions are clearly labelled.
Authors may not grant rights they do not hold or remove source attribution when processing data. The existence of a licence does not replace citation. Detailed provisions concerning copyright and reuse of the published article are set out in the Copyright and Licensing Policy.
09. Verification during manuscript review
The editorial office checks that the statement is present and the specified access routes work. Reviewers assess whether the data and descriptions are sufficient to verify the main conclusions and may request specific files, explanations or verification calculations through the editor. Such checks do not require the editorial office to rerun every calculation or guarantee that all errors will be detected.
For double-anonymous peer review, de-identified copies or appropriate private links without author-identifying metadata are used; provenance and custodian information remain with the editorial office. If complete anonymity is impossible because an open dataset already exists, the editor is informed. Scientific verifiability must not be sacrificed merely to remove information formally.
Non-public materials received for verification are used only for the editorial task and are not shared with other persons or external generative AI services. Access is limited to the necessary participants. Before a final decision, authors resolve significant discrepancies between the article, dataset and code or provide justified explanations. The rules on independence and confidentiality of peer review apply in full.
10. Preservation, updates and enquiries
Authors ensure the preservation of source materials, documentation and code used for at least 5 years after publication; a longer period applies where required by an institution, agreement or other applicable rules. This is the journal's minimum retention period, not a universal requirement of indexing databases. Where mandatory conditions limit retention, permissible periods and the safe documentation to be preserved are agreed in advance. Materials relevant to an unresolved investigation are not destroyed within the limits of permitted retention.
A responsible custodian is designated; changes in an author's employment must not leave data without a responsible person. Authors arrange backups, access protection and transfer of responsibilities. Expiry of the minimum period does not mean an open dataset must be deleted from its repository. Preservation of research materials differs from archiving published issues, which is governed by a separate journal policy.
Corrections to data are released as a new version with a description of changes and a link to the version used in the article. Files that change the meaning of published results must not be silently replaced. In the event of a significant error, loss of access or changes to access conditions, the author informs the editorial office; implications for the article are considered under the corrections and retractions policy.
Problems with access or reproduction are reported through OJS or via the official editorial contact page, specifying the article, version of materials and problem identified. Disagreement or an unsuccessful attempt to reproduce results does not, in itself, prove misconduct; the procedures for examining allegations and appeals apply. The actual date of approval and publication is recorded for this policy. New formal requirements are not attributed retrospectively to past publications, but concerns about their reliability may be investigated.
Reference guidance
This policy takes account of the DOAJ transparency principles, FAIR principles, AGU guidance on data and software, and FORCE11 data citation principles. The specific requirements, exceptions and retention period set out below are established by the journal; they do not imply that the journal operates its own data repository.