.. include:: /banner.rst

=====================
What's new in CFT 1.0
=====================

.. warning::
   The information on this page is for the CFT 1.0 release and is for historical reference only.
   If you are looking for the latest release, please refer to the :doc:`what's new in CFT 2.0 documentation <../v1/changelog-v2>`.

Useful resources
----------------
* For a full description of the input format, take a look at the :doc:`data schemas page <../v1/data-schemas>`.
* For the list of reference data, take a look at the :doc:`reference data page <../../reference-data/index>`.

.. contents::


Dropped support for APIv0
-------------------------

The APIv0 is no longer available and all the APIv0 endpoints have been removed as well as the related documentation and testing tool. Use APIv1 instead.

Crop API - calculate & create endpoints
---------------------------------------

New waste water section
#######################
A waste water input section is now available and can be used to calculate waste water emissions.

.. code-block:: json

   "waste_water": {
      "waste_water_production": {
        "unit": 15,
        "value": 12
      },
      "oxygen_demand": {
        "unit": 18,
        "value": 15
      },
      "oxygen_demand_type": 1,
      "water_treatment_type": 1
    }


New irrigation caculation method available
##########################################
Additionally to being able to caculate emissions based on *volume, pumping depth and distance*, they can now be calculated based on *volume only*.

An ``irrigation_calculation_type`` optional field has been added to the crop section to select the calculation method and the input format to use.

If ``irrigation_calculation_type`` is not provided, the input format based on *volume, pumping depth and distance* will be expected.

Example of an irrigation event sent as per the volume-only format:

.. code-block:: json

   "crop": {
      "...": "...",
      "irrigation_calculation_type": 2
    },

.. code-block:: json

   "irrigation": [
      {
        "method": 1,
        "allocation": 100,
        "pumping_depth": {
          "value": 0,
          "unit": ""
        },
        "horizontal_distance": {
          "value": 0,
          "unit": ""
        },
        "water_added": {
          "value": 10000,
          "unit": "litre"
        },
        "power_source": 2,
        "water_source": 2
      }
    ]


New rice section available
##########################
A rice input section is now available and can be used to calculate paddy emissions.

For more details, see the :ref:`rice documentation <crop-type-rice>`.

.. code-block:: json

    "flooding": {
         "time_under_cultivation": {
             "value": 123,
             "unit": "d"
         },
         "before_cultivation": "Not flooded pre-season (for < 180 days)",
         "during_cultivation": "Continuously flooded"
     },
     "green_manure": {
         "amount": {
             "value": 6.6,
             "unit": "tonne / ha"
     },
     "years_ago": 11,
     "allocation": 100
     }


Updated crop protection input format
####################################
The specification by application dose for seed treatment and post-emergence is no longer available. Replace 1 dose with 0.5 kg of active ingredient.

A crop protection ``type_id`` can now be specified. Although this field is optional, it will become mandatory in the future and it is advised to provide it. For now, if not defined, *pesticide* will be used as the default type. See the :ref:`pesticide-type` list for the available options.

.. code-block:: json

   "pesticides": [
      {
        "type_id": 1,
        "category_id": 3,
        "percentage_rate": 100,
        "application_rate": {
          "value": 1,
          "unit": "kg / acre"
        }
      }
    ]


Updated machinery input format for balers and updated list of available machines
################################################################################
Balers should now be entered in a specific format, using the additional ``number_of_bales`` field.

The other machines will keep using the exising format.

New machines are now available and some existing machines have been deprecated. For more details, see the :ref:`machine list <machine>`.

Example of a baler machine input:

.. code-block:: json

   "machinery": [
      {
        "operations": 4,
        "machinery": 1,
        "fuel_type": "diesel (average biofuel blend)",
        "number_of_bales": 2
      }
    ]


Dairy API - calculate & create endpoints
----------------------------------------

Updated dairy manure management options
#######################################
The existing ``Pit storage below animal confinements`` option has been deprecated.

Use ``Pit storage below animal confinements (< 1 month)`` instead.
A ``Pit storage below animal confinements (> 1 month)`` option has been added.

See the full list of :ref:`manure management options <manure type>`

Updated dairy feed components input format
##########################################
A feed component region can now be specified. Although this field is optional, it will become mandatory in the future and it is advised to provide it.

For now, if not defined, 'Global (world)' will be used as the default region. See the :ref:`feed-item-region` list for the available options and the :ref:`feed-components-item` list for the available regions for each feed component.

.. code-block:: json

    "feed_components": [
      {
        "herd_section": "Dairy calves",
        "item": "Maize / corn grain",
        "region": "Global (world)",
        "dry_matter": {
          "value": 10,
          "unit": "kg"
        },
        "certified": false
      }
    ]