The Milkypad approach
Earth data should be useful to people, from finding the right observation to deciding what to do next. Start with a satellite data request, then use AI-assisted GIS analysis or a custom app when your work calls for more.
Satellite observations
and the information you already use
Specify, order and receive suitable observations.
Compare sites, measure changes, prepare reports.
Create and customize tools your team can use.
How the work comes together
Bring a data specification, a site review, a client report or a tool your team needs. Acquisition comes first when you need observations; analysis and app creation let you take them further.
Explore data acquisition ↗Choose an area anywhere on Earth and describe the dates, spatial resolution, spectral bands or sensor you need. You can request data on its own, or start with a question, analysis or app.
Your location and requirementsCompare available archive observations or explore a future capture request. Review coverage, price, rights and delivery terms before ordering. Receiving the agreed data can complete your task; further analysis is optional.
A complete outcome in its own rightIf your task needs analysis, ask the assistant to compare sites, calculate measurements or investigate a pattern. Review the map, chart, table or report, with the method and its limits available to inspect.
From a question to a usable resultSave the analysis or build an app around it. Give colleagues the maps, filters, and actions they need, then customize the tool as their work changes.
Reuse the work and share the tool
Rome, Italy · Sentinel-2 · October 8, 2017Results you can explain
A site comparison should help you choose where to inspect. A report should help a client understand what changed. The evidence needs to be clear enough for that next decision.
Check the source, observation date, and coverage alongside the map or measurement.
Understand where clouds, limited detail, or missing observations leave gaps that need other data or a field visit.
Keep the relevant sources and methods with the result so colleagues and clients can review the work.
Keep control of your work
Getting help should leave you able to steer the result. These principles guide data access, analysis and app creation.
Start with suitable open or customer-owned data. Review the expected benefit and full cost before buying imagery or starting paid processing.
Know whether you can include the source in a client report, publish an image, or share an app before building your workflow around it.
Maps, tables, plain-language requests, and keyboard controls should make the same task accessible in different ways.
Ask for a new filter, a different view, or a revised analysis. Keep earlier results available so changes to the tool preserve the work you need.
Before you get started
The Milkypad workflow starts with describing the work in ordinary language, getting help with data and analysis, and shaping an app without writing its code yourself. You bring knowledge of your task. Methods, assumptions, and results still need appropriate review, especially for specialist or consequential decisions.
Ask the AI assistant for an answer, a custom analysis, or help building and changing an app. Use Studio to work with that app through maps, charts, tables, and controls. Both use your project data, so your team can continue using a saved app without keeping a conversation open.
Yes. Data acquisition is a standalone request. Specify a location and data requirements, then discuss suitable options, ordering and delivery for your existing workflow. Analysis and app creation are available directions when you need them, not a requirement for a data request.
Combining your data with satellite observations is central to Milkypad. Site boundaries, field records, asset lists, and measurements help connect an analysis to your work. Supported sources and formats will be confirmed as the first workflows are built and validated.
You can specify an area anywhere on Earth, historical or future dates, spatial resolution and required bands or sensor type. Archive observations and future collection feasibility need to be checked against that request. Matching data may not exist for every location, date or specification; suitable alternatives and delivery terms need to be clear before an order.
Try the interactive product examples and practical guides, or share your task through the early-access form. The examples use prepared content. Submitting the form sends an enquiry; it does not place a data order, create an account or run a live analysis. We will confirm access and supported workflows when we review your request.
Start with your GIS task
Tell us what you want to order, analyze or build. A location and data specification are enough to start a data acquisition discussion.
Request early access