Foodie Geoss aip 8 presentation new

1www.foodie-project.eu

FOODIE Farm-Oriented Open Data in EuropeCIP-ICT-PSP-2013-7 Pilot Type B

Karel Charvat, Tomas Reznik, Vojtech Lukas, Karel Charvat Jr., Sarka Horakova, Michal

Kepka, Marek Musil, Zbynek Krivanek

Objectives

Main idea of FOODIE

open and interoperable agricultural specialized platform hub on the cloud for the

management of spatial and non-spatial data relevant for farming production

discovery of spatial and non-spatial agriculture related data from heterogeneous sources

integration of existing and valuable European open datasets related to agriculture

Main idea of FOODIE

data publication and data linking of external agriculture data sources contributed by different public and private stakeholders allowing to

provide specific and high-value applications and services for the support in the planning and decision-making processes of different stakeholders groups related to the agricultural and environmental domains.

GI2014 – GI/GIS/GDI – Forum

FOODIE service platform

Project objectives

O1 To make use of existing spatial information resources and services for various domains –coming from different initiatives like INSPIRE,SISE, GMES/Copernicus , GNSS, GALILEO, GEOSS , GBIF, EUNIS, EEA, etc. - where the EC and the member states have invested heavily over the past decade,

O2 To design and provide an open and interoperable geospatial platform hub on the cloud based on existing software components from research results and available solutions in the market (mostly open-source) that includes:

O3 integration of external agriculture production and food market data using principles of Open Linked Data

Project objectives

O4 an open and flexible lightweight Application Programming Interface (API), that allows private and public stakeholders in the agricultural and environmental area to publish their own datasets (e.g., datasets provided by local sensor networks deployed in situ in farms, knowledge from farm communities, agricultural services companies, etc.) and make it available in the platform hub as open linked data (and enabling it to further processing and reasoning over it)

O5 specific and high-value applications and services for the support in the planning and decision-making processes of the different stakeholders groups

O6 provision of security mechanisms to prevent the unauthorised access and use of the platform users’ personal information as well as the data published by themGI2014 – GI/GIS/GDI – Forum

Project objectives

O7 a marketplace where data can be discovered and exchanged but also external companies can publish their own agricultural applications based on the data, services and applications provided by FOODIE

FOODIE service platform hub and decision making processes

Stakeholders, decision making and data model

FOODIE Data Models

One platform for all the most common tasks• Production planning• Production monitoring, alerting and analyses• Subsidies management• Environmental burden monitoring

Ownership of farmer’s data• Farmer’s data are private and sensitive data• Remains farmer’s property

Modularity• Customizable and scalable platform

User needs

Core Data Model• Management zones• Interventions• Treatments• …

FOODIE Data Models

Core Data Model class Foodie Core Data Model v 4.1 proposal

«featureType»Agricultural and

Aquaculture Facilities Model::Holding

«featureType»Agricultural and Aquaculture Facilities Model::

+ code :Identifier+ geometry :GM_Object+ activity :EconomicActivityNACEValue [1..*]+ validFrom :DateTime+ validTo :DateTime [0..1]+ beginLifespanVersion :DateTime+ endLifeSpanVersion :DateTime [0..1]

«voidable»+ includesAnimal :FarmAnimalSpecies [0..*]

«dataType»Agricultural and Aquaculture Facilities Model::

FarmAnimalSpecies

«voidable»+ l ivestock :LivestockSpeciesValue [0..*]+ aquaculture :AquacultureSpeciesValue [0..*]

«featureType»Activ ity Complex::Activ ityComplex

+ inspireId :Identifier+ thematicId :ThematicIdentifier [0..*]+ geometry :GM_Object+ function :Function [1..*]+ userId :CharacterString

«voidable»+ name :CharacterString [0..1]+ validFrom :DateTime+ validTo :DateTime [0..1]

«voidable, l i feCycleInfo»+ beginLifespanVersion :DateTime+ endLifespanVersion :DateTime [0..1]

«featureType»Plot

+ code :Identifier+ validFrom :DateTime+ validTo :DateTime [0..1]+ beginLifeSpanVersion :DateTime+ endLifeSpanVersion :DateTime [0..1]+ geometry :GM_Object [1..*]+ description :CharacterString [0..1]+ originType :OriginTypeValue

«featureType»Treatment

+ quantity :Measure [1..*]+ tractorId :CharacterString [0..*]+ machineId :CharacterString [0..*]+ motionSpeed :Measure [0..1]+ pressure :Measure [0..1]+ flowAdjustment :Measure [0..1]+ applicationWidth :Measure [0..1]+ areaDose :DoseUnit [0..1]+ formOfTreatment :FormOfTreatmentValue [1..*]+ treatmentPurpose :TreatmentPurposeValue [0..*]+ treatmentDescription :CharacterString [0..1]

«dataType»NutrientsType

+ N :Measure [0..1]+ P2O5 :Measure [0..1]+ K2O :Measure [0..1]+ MgO :Measure [0..1]+ CaO :Measure [0..1]+ S :Measure [0..1]+ Zn :Measure [0..1]+ Cu :Measure [0..1]+ Fe :Measure [0..1]+ B :Measure [0..1]+ Mn :Measure [0..1]+ Mo :Measure [0..1]

«codeList»TreatmentPurposeValue

+ weed+ pest+ disease

«featureType»CropSpecies

+ beginDate :Date+ endDate :Date [0..1]+ cropArea :GM_Object+ cropSpecies :CropType [1..*]+ production :ProductionType [0..*]

«featureType»Product

+ productCode :CharacterString [0..*]+ productName :CharacterString [1..*]+ productType :CharacterString+ productSubType :CharacterString [0..*]+ productKind :ProductKindValue+ description :CharacterString [0..1]+ manufacturer :CI_ResponsibleParty [1..*]+ nutrients :NutrientsType [0..*]+ safetyInstructions :CharacterString [0..1]+ storageHandling :CharacterString [0..1]+ registrationCode :CharacterString [0..*]+ registerUrl :URL [0..*]

«featureType»SoilNutrients

+ nutrientName :GenericName+ nutrientAmount :Measure+ nutrientMeasure :CharacterString

«codeList»ProductKindValue

+ organic+ mineral

«dataType»SoilTextureType

+ clay :Percent+ si l t :Percent+ sand :Percent

«dataType»ProductionType

+ productionDate :Date+ variety :CharacterString+ productionAmount :Measure+ productionAnalysis :ProductionAnalysisType [0..*]

«dataType»ProductionAnalysisType

+ productionAnalysisDate :Date+ property :Measure

«codeList»OriginTypeValue

+ manual+ system

«featureType»Alert

+ code :Identifier+ type :CharacterString [1..*]+ description :CharacterString [0..1]+ checkedByUser :Boolean+ alertDate :Date+ alertGeometry :GM_Object

«featureType»Intervention

+ type :CharacterString+ description :CharacterString+ notes :CharacterString [0..1]+ status :CharacterString+ creationDateTime :DateTime+ interventionStart :DateTime+ interventionEnd :DateTime [0..1]+ interventionGeometry :GM_Object [1..*]+ supervisor :CI_ResponsibleParty [0..1]+ operator :CI_ResponsibleParty [0..*]+ evidenceParty :CI_ResponsibleParty [1..*]

«featureType»TreatmentPlan

+ treatmentPlanCode :CharacterString [0..*]+ description :CharacterString [1..*]+ type :CharacterString+ campaign :TM_Period [1..*]+ treatmentPlanCreation :DateTime+ notes :CharacterString [0..1]

«featureType»ProductPreparation

+ productQuantity :Measure+ solventQuantity :Measure [0..*]+ safetyPeriod :TM_Period

«dataType»ActiveIngredients

+ code :CharacterString [0..1]+ ingredientName :CharacterString+ ingredientAmount :Measure

«codeList»DoseUnit

+ minimumDose :Measure+ maximumDose :Measure

«codeList»FormOfTreatmentValue

+ manual+ applicationMachine+ aerial

«featureType»ManagementZone

+ code :Identifier+ validFrom :DateTime [0..1]+ validTo :DateTime [0..1]+ beginLifeSpanVersion :DateTime+ endLifeSpanVersion :DateTime [0..1]+ geometry :GM_Object [1..*]+ notes :CharacterString+ dateOfAnalysis :DateTime [0..*]

«featureType»SoilType

+ soilType :CharacterString [1..*]

«featureType»SoilTexture

+ soilTexture :SoilTextureType [1..*]

«featureType»pH

+ pH :Measure [1..*]

«featureType»OrganicMatter

+ organicMatter :Percent

«featureType»ElectricConductiv ity

+ electricConductivity :Measure [1..*]

«featureType»ZonePolygon

+ area :Measure

«dataType»CropType

+ name :CharacterString+ scientificName :CharacterString+ description :CharacterString+ notes :CharacterString+ seedingAdvice :CharacterString+ harvestingAdvice :CharacterString

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Data Model compliant to:• Directive 2007/2/EC (INSPIRE)• ISO standards 19100 series

Open and scalable

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Holding attribute ValueIdentifier http://foodie-project.eu/CZ/MJM/TrsickaFunction agricultureUser identifier 47674814Name Tršická zemědělská, a.s.Valid From 1993-12-13Begin Lifespan 2015-03-11

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Site attribute Value

Identifier http://foodie-project.eu/CZ/MJM/Trsicka

Activity (NACE code)

A1.1.1 - Growing of cereals (except rice), leguminous crops and oil seeds

Valid From 2014-03-15

Begin Lifespan 2015-04-07

“Site” level is the lowest INSPIRE-defined one• However, differently defined within various INSPIRE spatial data

themes (issue addressed by the INSPIRE clusters)

Key for the integration to a Land Parcel Identification System (LPIS)• Typically managing Ministry of Agriculture of each Member State• 45 LPIS’ within 28 European Member States• Some countries have LPIS connected to the cadaster, some not• Basic level for subsidies

Successful integration of the Czech LPIS within the Pilot 3 of the FOODIE project

Core Data Model – Site

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Plot attribute Value

Identifier http://foodie-project.eu/CZ/MJM/Trsicka/Plot/001

Valid from 2015-04-09

Origin type manual

Crop species wheat

… …

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Plot attribute Value

Identifier http://foodie-project.eu/CZ/MJM/Trsicka/Plot/001

Valid from 2015-04-09

Origin type manual

Crop species wheat

… …

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Intervention attribute Value

Type tillage

Status ongoing

Intervention start 2015-04-22

Supervisor John First, senior manager, phone 7435

… …

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Treatment attribute Value

Intervention type herbicide application

Status ongoing

Treatment quantity 70 litres

Application width 25 meters

Form of treatment Application machine

Product Roundup®

… …

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Treatment attribute Value

Intervention type herbicide application

Status ongoing

Treatment quantity 70 litres

Application width 25 meters

Form of treatment Application machine

Product Roundup®

… …

Product attribute ValueProduct code 01475200

Product name Roundup®

Product type herbicide

Manufacturer MONSANTO®

Register URL http://agro-register.cz/?1475

Safety instructions Eye contact: may cause may cause pain, redness and tearing based on toxicity studies.…

FarmAnimalSpecies

«featureType»Plot

+ organic+ mineral

+ manual+ system

«featureType»pH

+ area :Measure

+contains

1..*HoldingSites

+containsZone

+HoldingPlot

+containsPlot 1..*

HoldingPlots0..*

0..1 0..1

+crop 0..*

Separate data stores• Data model according to the data source• Core data mode stores user-specified (interpreted) data

Satellite and aerial images• Data harvester component as a part of the FOODIE cloud• LANDSAT 8 and later on Sentinel data imported into the platform

immediately as available Including the basic processing like computation of vegetation indices

Volunteer geographic information (VGI)• Lightweight profile of the core model to be developed within the

second year of the project

Supportive data

Sensor Data Model• ISO 19156 O&M• also VGI

FOODIE Data Models

<swe:encoding><swe:TextEncoding decimalSeparator="." tokenSeparator="," blockSeparator="@@"/></swe:encoding><swe:values>2014-10-28T18:47:07+0100,urn:ogc:object:feature:tom:foi0792,24.61,49.2241229,16.5398454@@2014-10-28T19:00:00+0100,urn:ogc:object:feature:tom:foi0792,24.06,49.2241229,16.5398454@@2014-10-28T20:00:00+0100,urn:ogc:object:feature:tom:foi0792,22.87,49.2350641 16.5770019@@</swe:values></swe:DataArray></om:result>

<om:result><swe:DataArray><swe:elementCount> <swe:Count> <swe:value>5</swe:value> </swe:Count></swe:elementCount><swe:elementType name="Components"><swe:DataRecord> <swe:field name="Time"> <swe:Time definition="http://www.opengis.net/def/property/OGC/0/SamplingTime"> <swe:uom xlink:href="http://www.opengis.net/def/uom/ISO-8601/0/Gregorian"/> </swe:Time></swe:field> <swe:field name="feature"> <swe:Text definition="urn:ogc:data:feature"/> </swe:field> <swe:field name="temperature"> <swe:Quantity definition="urn:ogc:def:phenomenon:tom:temperature"> <swe:uom code="°C"/> </swe:Quantity></swe:field><swe:field name="latitude"> <swe:Quantity definition="urn:ogc:def:latitude"> <swe:uom code="decimalDegrees"/> </swe:Quantity></swe:field><swe:field name="longitude"> <swe:Quantity definition="urn:ogc:def:longitude"> <swe:uom code="decimalDegrees"/></swe:Quantity></swe:field></swe:DataRecord></swe:elementType>

Sensor Data Model• ISO 19156 O&M• also VGI

Transport Data Model• OSM for navigation

FOODIE Data Models

vertexvertex

vertex

edge edge

Road segment attributes

Identifier, e.g. http://foodie-project.eu/dat/tn/654787

National code, e.g. 43

Road width, e.g. 5 meters

Maximum height, e.g. 2.1 meters

Maximum weight, e.g. 2 tons

Speed limit, e.g. 20 km·h-1

Surface category, e.g. asphalt, unpaved,…

HAZMAT limitation, i.e. flammable/explosive/corrosive/toxic/oxidizing

Transport data model

Maximum height• Expressed as integer with units of measure• Tunnels out of INSPIRE standardization

Missing attributes

<<featureType>>Barrier height

+ height: MeasureConstraints

(Applies to road transport elements only)

Limitations of the hazardous material transportation for the road segments• flammable• explosive• corrosive• toxic• oxidizing

Missing attributes

<<codelist>>HazmatTransportLimitValue

+ flammable

+ explosive

+ corrosive

+ toxic

+ oxidizingtags

extensibility = any

Development based on open source• PostgreSQL 9.3.6 with PostGIS 2.1.0• PostgreSQL XL with OpenStack as a cloud solution• Freely available SQL script for setting up the database schema at the end of

the project

Data model achievements• Extended data models of three INSPIRE spatial data themes

Agriculture and aquaculture facilities (AF) Transport Networks (TN) Environmental Monitoring Facilities (EF)

• Negotiations with the standardization bodies Open Geospatial Consortium (Agriculture Domain Working Group) Joint Research Centre of the European Commission FOODIE platform is a part of the GEOSS Architecture Implementation Pilot –

Phase 8

Implementation and further development

FOODIE APIs

Discover• Be informed about available data within (and ideally also beyond)

the platform

Preview• Have a possibility to see the data at a glance

Process• Display only relevant information

Download• Obtain the desired data

Alert• Be informed when some situation occurs

Integrate• Platform to other systems/other systems to the platform

User needs (1/2)

In fact more than 50 APIs defined by the user needs:• Interface to the Network and Devices (I2ND)• Machinery Tracking Service• Data Harvesting Service• Weather Forecast Service• CO2 Saving Simulator• Data Semantisation Service• Linked Data Publication Service• Report Generator Service• Marketplace Service• Data Logging Service• Registration Service• …

User needs (2/2)

Two kinds of APIs• Open (interoperable, typically based on OGC and/or INSPIRE)• Lightweight (proprietary, fast)

Open• So far OGC CSW, WMS, WFS, WCS, WPS, SOS, SPS

Lightweight• Following best practices like OGC/ESRI GeoServices REST

Specification• REST interface (resource oriented)• (Geo)JSON as the exchange format

Initial Development of APIs

Rules for URI (URL) definition• Core structure http://foodie-project.eu/api

btw, should be replaced by http://foodie/platform.eu/api

• Then indication of the API type mapimage for a data preview search for searching resources data for download of data notification for sending the requested information process for computation of vegetation indices semantic for semantic annotation service iaas for cloud services (Infrastructure as a cloud) …

Lightweight APIs (1/2)

• Kind of an interface e.g. rest, csw, wms, wfs, wcs, wps…

• Version of an interface e.g. 01

• Code of the identifier e.g. 0123

The whole URL may then look like• http://foodie-project.eu/api/data/rest/01/0123• http://foodie-project.eu/api/process/wps/ndvi• …

Lightweight APIs (2/2)

APIs definitions in Swagger

Aplication of remote sensing in FOODIE

Scenario C – Monitoring of in-field variability for site specific crop management• development of stable monitoring system for effective

identification of spatio-temporal variability of crops and to use this information for optimization of the crop management practices.

Sc.C – Site Specific Crop Management

Periodic satellite remote sensing• for identification of spatial variability and capturing the dynamics

of vegetation growth, both at medium level of spatial resolution• Suggested satellite survey is based on the free available data of

Landsat 8 or in 2015 launched Sentinel-2. • The main information are vegetation indices NDVI and EVI• The absolute values of VI, their relative to mean value of the field

and change detection will be implemented for assessment of crop stands and delineating of management zones.

Example of L8 dataset for Czech pilot farm

LC81900262015127LGN00LC81890262015200LGN00

LC81900262015143LGN00= not reliable for planning of VRA

Cloud coverage over farm area

Landsat 8 OLI• 30m spatial resolution for MS; 16 days revisit cycle• USGS EarthExplorer – at-sensor radiance data (geotiff)• USGS ESPA – surface reflectance data incl. basic set of VI

products Sentinel 2 A/B MSI

• 13 bands, 10m / 20m / 60m spatial resolution; revisit time 5 days (S2A+S2B)

• ESA Sentinels Scientific Data Hub

Data source

Estimation of field crop variability based on the recent years Landsat images and EVI2 index

FOODIE Czech pilot farm

Landsat 8 OLI images

crop development within 68-ha (spring barley) and 62-ha (winter wheat) fields in 2014 represented by NDVI

Sc.C – Site Specific Crop Management

Operative aerial remote sensing• mapping of the fields at high spatial resolution but with low frequency • the aim is to prepare the prescription maps for variable applications of

fertilizers and pesticides, estimated by the spectral measurement of crop parameters.

• aerial imaging will be carried out using multispectral camera (Ultracam) by an external provider of photogrammetric services.

• a workflow will be developed for pre-processing of acquired images (radiometric and geometric corrections) and their analysis and classification according to the MJM interpretation algorithms.

Multispectral aerial imaging (Ultracam UCX)winter wheat (69 ha)Mai 2014

Farm Telemetry

Tractor Art

The effectiveness of each production, including agriculture, is determined by the ratio of the value of the production outputs to the value of production inputs. One of the possibilities of solving the farm effectiveness problem,

FarmTelemetry focuses on is to optimize the level of farm inputs. It can be the energy needed to power agricultural machinery on the fields, energy for the transport of inputs and outputs of production

Farm Telemetry

Machinery Monitoring

Machinery monitoring

Tractor movement

Fuel consumption: tillage (l/h)

Fuel consumption: detail (l/h)

Work Log: Excel export

Daily time utilization (Excel export)

Foodie Geoss aip 8 presentation new

Environment

GEOSS AIP-5 Architecture Implementation Pilot, Phase 5 -...

AIP-6 GEOSS Water Services Sensor Web activities - a global....

NOAA Data Center Access Activities via the GEOSS...

AIP-2 Kickoff Workshop Energy SBA Scenario Description...

GEOSS Architecture

GEOSS Architecture Implementation Pilot AIP February 2011....

GEOSS AIP-2 Development Interim Design Review Portals &...

GEOSS Data CORE and GEOSS Common Infrastructure: awareness,....

GEOSS Task IN-05 Architecture Implementation Pilot AIP-5

GEOSS Architecture Implementation Pilot (AIP) 15 th ADC...

GEOSS Architecture Implementation Pilot (AIP-5) Kickoff...

1 Using the GEOSS Common Infrastructure in the Air Quality &...

AIP-2 Kickoff Workshop Energy SBA Session Ellsworth LeDrew,....

Next GEOSS – der neue europäische GEOSS Hub€¦ · Next...

GEOSS Water Services Showcase Demos 2, 3, 4 AIP-6 Water SBA....

Citizen GEOSS