Partner with Opatrné pole

Fields and alerts in your application.

Add field overviews, crop changes and weather for fieldwork to your service for growers. Display the information where your users already work.

Explore the working demo

No key needed. The demo uses my own farm near Plánice.

One shared output

Field. Reason. Time.

  • Field overview

    Field identifiers and areas for each farm.

  • What needs attention

    Crop changes and conditions for fieldwork.

  • Information for decisions

    Explanation, validity and data sources.

Your application, your relationship with users.

An outline of the package contents. See the demo for current data.

Who it is for

Three ways to work together.

Software provider

Add field data and operational alerts to your software. Your users can keep working in a familiar environment.

Organisation working with growers

Test a shared overview for selected farms. We will agree in advance who can see the data and which tasks it should support.

Research partner

Let us design a validation study using real observations. We will define the research question, required data and evaluation method before starting.

Standard package

Fields and operational alerts.

One shared foundation for participating farms. Your application controls how the data is displayed and used in subsequent tasks.

Content for growers

  • The farm's fields, with identifiers and areas.
  • Satellite crop changes to check in the field.
  • Suitable spraying hours based on the weather forecast.
  • Current weather warnings for the farm's locations.

Integration resources

  • An alert title and explanation in Czech.
  • An item identifier for ongoing updates.
  • Validity times and data source information.
  • A link to the overview and interface documentation.

A satellite shows a change; the grower checks its cause. A forecast describes expected weather. When applying a crop protection product, its label and the actual conditions on site take precedence.

Technical interface and public endpoints

The API returns JSON. Your application retrieves the data from its own server. Alerts have a persistent id, so subsequent requests do not create the same tasks again.

Sample farm alerts
/api/v1/ukazka/upozorneni
Sample farm fields
/api/v1/ukazka/dily

Both endpoints work without a key and return only my own sample farm. Other farms require assigned access. Send the key in the Authorization header from your server, never in a URL or in public page code.

Open the documentation and demo

From demo to partnership

Test the use case first. Then agree on operation.

  1. Try the shared foundation

    Explore the output and integration using my own farm. Check whether it fits your users' work.

  2. Define a bounded pilot

    We will choose the farms, scope, duration and people responsible. We will set criteria in advance: correct field matching, data freshness and the usefulness of alerts for the agreed tasks.

  3. Evaluate and agree on a licence

    Based on the results, we will agree on a recurring licence, price, data updates, support and how the service can be ended. Each item will be included in a specific proposal.

We will agree on the pilot's scope and price before it starts. Sending an enquiry does not place an order.

What to expect

The status of each part is clear.

Working demo

Explore the output now

The public field and alert demo uses my own farm. You can check the source and timestamp of the data.

Operation by agreement

A specific proposal defines the scope

We will agree on access for other farms, updates, support and pricing. The public demo alone does not establish these operating terms.

Research and validation

Model estimates have limitations

Flowering or damage estimates require separate validation. They are not promised as part of this standard package.

Privacy, sources and partnership requirements

Public testing uses only my own sample farm. Before adding other farms, we will define authorised users, access scope and rules for handling the data provided.

The foundation is public data from the Czech Ministry of Agriculture, Copernicus satellite data and weather data from ČHMÚ and MET Norway. Sources, timestamps and terms of use are described in the interface guide and data sources overview on this website. Availability and update frequency depend on each source.

For a research pilot, we will separately define the origin of observations, permissions for their use and the validation method. A calculation alone does not demonstrate savings or the effect of an intervention.

Let us agree on the scope

Where should the data help your users?

Briefly describe who your service is for and what it should help with. I will get back to you with a suggested next step.

Ing. Martin Opatrný
Opatrné pole, a farm near Plánice

Choose the closest option. We will clarify the scope together.