Alternative Standards


Here is the complete list of MIAPPE to BrAPI Field Mappings

BrAPI V2 endpoints required to fully support MIAPPE data:

  • GET /trials

  • GET /studies

  • GET /locations

  • GET /germplasm

  • GET /observationunits

  • GET /events

  • GET /samples

  • GET /variables


In BrAPI V2.1, the /events endpoint was made compatible with the International Consortium for Agricultural Systems Applications (ICASA) controlled vocabulary. This common standard connects BrAPI to agronomy focused software projects including ARDN and DSSAT. Visit the ICASA Data Dictionary for more information about the ICASA agronomy data model.


Multi-Crop Passport Descriptors (MCPD) “is a widely used international standard to facilitate germplasm passport information exchange” ( In BrAPI, the primary way to share Germplasm data is through the “GET /germplasm” endpoint. This endpoint has 24 fields out of the available 41 MCPD fields. The BrAPI specification also defines the endpoint “GET /germplasm/{germplasmDbId}/mcpd”. This alternate endpoint allows a user to access all 41 MCPD compliant data points when looking at a specific germplasm entry.


GeoJSON is a standard format for defining GPS coordinates and areas. It provides a specific JSON structure that is commonly used in other APIs across industries, including digital maps, satellite imagery, and navigation. BrAPI has adopted the GeoJSON standard for Images, Locations, and Observation Units. The full GeoJSON specification defines many different types of locations and areas that could be recorded, BrAPI has adopted a slightly simplified version. The only types of GPS data BrAPI cares about are point like objects (ie the source of an image) and simple polygon areas (ie the outline of a plot.

Please see best practices document “Location Coordinates” for more information.

GA4GH Variants Schema

The Global Alliance for Genomics and Health (GA4GH) developed an API schema for managing genotyping data. This Variants API schema forms the basis for the BrAPI-Genotyping module, with additions based on community input. The schema is originally based on the VCF file format, and represents all the concepts presented in a VCF. The Variants API is very thorough and robust, however the BrAPI community has found it to be somewhat inefficient for medium to large variant datasets. Community working groups have made an effort to augment the schema with some more performant endpoints, while staying compliant to the original GA4GH specification.