Ordering a Field

Defining your field

There are three ways to put a field on the order map:

• Draw it directly. Trace the boundary on the map. You can draw several polygons in one order — useful when a road, river, or hedgerow splits a field — and they'll be treated as a single field for analysis. Click a finished polygon to remove it.
• Upload a shapefile. Upload a .zip archive containing a shapefile (.shp, .shx, .dbf together). The system reprojects to WGS84 automatically if your file uses a different coordinate system. If the archive holds multiple shapes, you'll get a picker to choose which ones to include.
• Pick a saved field. Once you've placed one order, your fields are saved automatically — future orders let you pick one from a dropdown with the geometry already filled in.

Field size limits

Fields larger than 1,000 ha need to be split into separate orders, or you can reach out for enterprise handling.

Coverage area

Orders are currently supported across Europe, including Ukraine. Drawing a field outside this region triggers a warning at order time — calibration outside Europe hasn't been validated, so results from those areas aren't officially supported.

Picking the analysis date

Each order can include up to 6 analysis dates, each producing its own complete report, viewable through a shared date slider. A few rules govern dates:

• Earliest available date: 1 January 2020 — the point from which Sentinel-2 imagery has reliable global coverage.
• Latest available date: today. Future dates aren't selectable.
• Recent vs. historical pricing: dates within the past 12 months are charged at the standard rate; older dates get a lower historical rate (see pricing).

There's no enforced season for ordering, but the model reads best when bare or lightly vegetated soil is visible — dense canopy hides the surface. In practice, the most useful dates are early spring before crop emergence, post-harvest in late summer or autumn, or any fallow window. If you're tracking change over time, use comparable points in the rotation (post-harvest each year, for instance) so you're comparing like with like.

Multiple polygons and field clusters

If a field is made up of disjoint polygons, the system automatically splits them into clusters. Each cluster gets its own tab in the report — its own data table, heatmaps, and charts — but you order the whole thing as one field and pay one combined price based on total area.

Region restrictions for partner accounts

Orders placed through a partner account may be restricted to a region your partner organization has configured (a country, province, or custom area). Fields outside that region are rejected — talk to your partner administrator if you need wider access.

What happens after you submit

1. Payment runs through Stripe, and you get an emailed invoice right away.
2. Your order enters the queue and starts processing within seconds.
3. Satellite imagery is pulled for the 8 months before each analysis date, cloud-masked and composited (see Methodology for the full pipeline).
4. The model runs and the report is assembled.
5. You get an email with a link to the finished report — typically a few minutes per analysis date for a typical field size.

If something goes wrong — too much cloud cover on a given date, for example — the report page will tell you which date failed and why. There's no automatic retry; contact support if a date needs to be re-run.

Next steps

• The report — how to read every tab once your order is ready.
• Soil properties — what each value means and how to interpret the labels.