Real-time

Request for Weather Nowcast (GeoTIFF to XML conversion)

Purpose: 

Disease Pressure Service provides farmer the information on elevated risk of a crop (etc) disease. DPS alarms may be used e.g. to trigger a spraying event. The purpose of the data transfer is to get a weather nowcast for the Disease Pressure Service internal processes. The applicable actors are Advisory Service (Disease Pressure Service), Intermediator (Weather Service) and Field (Parcel).

Concept: 

Weather Service Provider provides weather information (e.g. nowcast) in GeoTIFF format through a Web Coverage Service interface. The actual weather data variable values are stored into metadata of a returned GeoTIFF image. Lightweight ESB like service was implemented between Disease Pressure Service and Weather Service to a) convert the WCS interface into more convenient SOA interface with XML message exchange and to b) eliminate the need to implement image metadata manipulation routines into the Disease Pressure Service server side code.

Used standards/de facto standards: GeoTIFF, WCS, ESB, SOA, XML, REST

More on SOA: https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp...

More on REST: https://www.ibm.com/developerworks/webservices/library/ws-restful/

Design: 

Interface provides XML message exchange capability for Disease Pressure Service (DPS) when requesting weather information (nowcast) from Weather Service Provider’s (WSP) Web Coverage Service interface. The sequence begins with getNowcast action request (within a XML message) from the DPS to the lightweight ESB Service (ESBS) implement. The parameters (coverage) include the coordinates of the area the weather info is requested, weather variables needed and the timestamp of the sample. ESBS parses the request into a valid WCS request format (URL) and passes it to the WSP. The WSP response input stream (GeoTIFF image) is read by ESBS and the image metadata is applied utilizing Apache Sanselan class libraries. The valid parameters are extracted from the image metadata, parsed into a XML and passed to the DPS as a response.

The DPS and the ESBS services are implemented using Java EE (http://www.oracle.com/technetwork/java/javaee/overview/index.html). In order to implement GeoTIFF metadata reader you need to download and install e.g. Apache Sanselan (used in this implement) class libraries ( http://commons.apache.org/sanselan/download_sanselan.cgi).

Implementation: 

Disease Pressure Service uses a SOAP client for message exchange with ESB Service (REST implement). The DPS’s weather request (XML message exchange) triggers an event where the Weather Service Provider’s Web Coverage Service interface is called. The method is using basic Java .io and .net class libraries (InputStream is = url.openStream() where the url is an object from a class URL created passing WSC service url to the constructor). The beauty of the Apache Sanselan is that it can read the image metadata directly from the input stream (metaData = Sanselan.getMetadata(is, null)). The Sanselan metadata container type is an array list (ArrayList <Object> al = new ArrayList() , al = metadata.getItems()). The XML messaging between DPS and ESBS is currently using proprietary format but a possibility to use e.g. AgroXML is investigated.

Source: 

agriXchange project team

Model: 

LPIS Boundery - Request via Applications & Web Service

Use cases: 
Concept: 

Request for LPIS Bounderiey with the web user interface. An desktop application provided by the IACS authorities has an exclusive access to the data.

Design: 

The farmer needs an account at the agency. With this Account he has access to the personalised data and a gis system.

Implementation: 

Web Service with an proprietary xml standard with GML.

LPIS Boundery - Request via Website - Interface

Use cases: 
Concept: 

Request for LPIS Bounderiey with the web user interface provided by the IACS authorities. Primary designed to support the IACS request but standardized data output /files enabled the further use in FMIS.

Design: 

The farmer needs an account at the agency. With this Account he has access to the personalised data and a gis system.

Implementation: 

User-Interface:
- Browser / HTML
File Download:
- XML
- GML
- CSV
- agroXML

Parcel boundary request

Concept: 

Retrieving LPIS parcel boarder lines from the government's LPIS to FMIS. Utilized in "GeoFertilizer" use case. Standard: OGC, WFS ISO19142

Design: 

Internet LAN connection between FMIS and LPIS server using Web Feature Service (WFS) interface. Stateless request - reply type protocol.

Implementation: 

Link to OGC; WFS ISO19142

Syndicate content