Journal of Precision Agriculture

Journal of Precision Agriculture

Journal of Precision Agriculture – Data Archiving Permissions

Open Access & Peer-Reviewed

Submit Manuscript

Data Archiving Permissions

Support transparent, responsible data sharing for precision agriculture research.

FAIR DataFindable, accessible, interoperable data.
Farm PrivacyProtect sensitive farm data.
Code TransparencyShare pipelines and scripts.
Long Term PreservationStable repositories and metadata.

Journal at a Glance

ISSN: 2998-1506
DOI Prefix: 10.14302/issn.2998-1506
License: CC BY 4.0
Peer reviewed open access journal

Scope Alignment

Precision agriculture, spatial variability, sensors, geospatial analytics, automation, and sustainable crop and livestock systems. We prioritize field validated, data driven decision support.

Publishing Model

Open access, single blind peer review, and rapid publication after acceptance and production checks. Metadata validation and DOI registration are included.

Review Time09 daysFrom submission
Acceptance Rate68%Recent average
Decision Time12 daysSubmission to decision
Publication3 daysAfter acceptance
Data Archiving Permissions

JPA supports open, responsible data sharing for precision agriculture research. Authors should deposit data and code in trusted repositories when possible, with clear access instructions.

We recognize that some datasets require controlled access due to farm privacy, proprietary management practices, or partner agreements. Authors should document restrictions and access pathways.

Recommended Repositories
  • Agricultural data repositories such as USDA Ag Data Commons or DataONE
  • Remote sensing and geospatial repositories such as Google Earth Engine assets
  • General repositories such as Zenodo or Figshare with DOI support
  • Code repositories such as GitHub or GitLab with release tags
  • Controlled access repositories governed by data use agreements
Sensitive Data and Privacy

Farm locations, grower identifiers, and proprietary management data must be protected. When full sharing is not possible, provide deidentified summaries and clear instructions for requesting access.

Authors should document data governance, including data custodians and access review procedures.

Data and Code Availability Statements
  • Include repository links or accession numbers in the manuscript
  • State licensing terms for data and code when applicable
  • Provide documentation for custom scripts or pipelines
  • Describe any access restrictions and approval requirements
Preferred File Formats
Data TypePreferred FormatsNotes
Yield monitor dataCSV, shapefileInclude coordinate system
Remote sensing imageryGeoTIFF, NetCDFProvide spatial resolution
Soil and lab dataCSV, XLSXInclude measurement units
Equipment logsCSV, TXTDocument sampling intervals
Archiving Checklist
  • Dataset metadata complete and consistent
  • Repository accession numbers included
  • Code and pipelines documented
  • Data use permissions documented
  • Access restrictions clearly stated
  • Include README files that describe variables, field zones, and file structures.
  • Provide data dictionaries for geospatial and agronomic variables.
  • Specify repository version and update schedules for evolving datasets.
  • Document deidentification steps for sensitive farm location data.
  • Provide checksum or hash values for large data downloads.
  • Ensure code dependencies are listed with version numbers.
  • Describe how access requests are reviewed and approved.
  • Include contact details for data access queries.
  • Provide sample metadata templates used for repository submissions.
  • Clarify licensing terms for data and code reuse.
  • Mention embargo periods and expected release dates if applicable.
  • Provide guidance for citing datasets in related publications.
  • Share workflow diagrams for data processing pipelines.
  • Ensure file names are descriptive and consistent.
  • Note spatial resolution and coordinate system in metadata.
  • Provide scripts for merging sensor and yield datasets.
  • Specify data collection intervals and units for each sensor.
  • Document calibration dates for sensors and yield monitors.
  • Include field boundary files where permissions allow.
  • Describe anonymization steps for partner farm data.
  • State whether raw and processed datasets are both shared.
  • Provide versioned releases for updated datasets.
Data Archiving FAQ

Can I embargo data?

Yes. Provide embargo details and expected release dates.

What if data are proprietary?

Explain restrictions and provide access request steps.

Is code sharing required?

We strongly encourage code sharing or detailed documentation.

JPA Commitment

JPA is committed to rigorous, transparent publishing in precision agriculture and digital farming. We emphasize reproducible field trials, clear reporting of agronomic outcomes, and ethical compliance across all article types.

The editorial office supports authors, editors, and reviewers with clear guidance and responsive communication. For questions about scope or workflow, contact [email protected].

We encourage continuous improvement in reporting practices and share updates that help the community maintain high standards in agricultural data science, field validation, and technology transfer.

Need Data Sharing Guidance?

Contact the editorial office for questions about repositories or permissions.