Start with the data you need to receive.
You may already know the area, dates, resolution and sensor you want. Or you may know the task—reviewing a field, comparing a site or studying a coastline—and need help translating it into a data request. Both are useful starting points.
Choose a location anywhere on Earth and define the area you need covered. A point identifies a place; a boundary and area size help describe the delivery. You can acquire data for tools you already use without asking for an analysis or app.
Describe the request in ordinary language:
“I need multispectral observations for these field boundaries, covering last growing season, with red and near-infrared bands. Help me choose suitable spatial detail and a format my team can use.”
Share that brief with Milkypad to discuss acquisition options, suitability and the terms to review before an order. A request defines what you need; it does not guarantee matching data exists or that a future collection is feasible.
Choose the observation that fits the question.
The brief: compare vegetation in the same spring window across two years at a fictional northern-hemisphere site. Explore why date, sensor, and usable coverage belong in the same decision.
Optical · late season
- Your target
- Same spring window
- Measurement
- Vegetation reflectance
- Review outcome
- Date does not fit
- May 2025 · required
- May 2026 · required
- Oct 2026 · candidate
The latest picture misses the spring comparison. A new capture cannot recreate a missing historical date.
Optical · partial cloud
- Your target
- Same spring window
- Measurement
- Vegetation reflectance
- Review outcome
- Some of the site is missing
- May 2025 · partial
- May 2026 · required
- Oct 2026 · later
The date fits, but the hatched area is excluded. Radar may offer another measurement; it cannot replace optical reflectance without a different method.
Compatible optical products
- Your target
- Same spring window
- Measurement
- Vegetation reflectance
- Review outcome
- Candidate pair for review
- May 2025 · candidate
- May 2026 · candidate
- Oct 2026 · later
Matching windows and usable coverage make a stronger candidate. Check bands, calibration, quality, and method before accepting the comparison.
Radar · different measurement
- Your target
- Same spring window
- Measurement
- Microwave backscatter
- Review outcome
- Requires a radar method
- May 2025 · radar
- May 2026 · radar
- Oct 2026 · later
Radar can provide observations through cloud, but measures microwave response rather than optical reflectance. Review a suitable radar method instead of substituting it into the same vegetation calculation. This grayscale landscape indicates coverage, not radar measurements.
Prepared teaching illustration. Landscapes, dates, and results are fictional; no live imagery search, analysis, or app generation is running. Sensor background: NASA JPL explains radar observations.
Specify the dimensions that matter.
- Area: Describe the location, boundary and area to cover, including any separate sites or exclusions.
- Dates: Give historical dates, an acceptable observation window or a future collection period. Add a delivery deadline separately.
- Spatial detail: State the resolution you need or describe the smallest feature that matters. Pixel spacing alone does not guarantee a feature can be detected.
- Spectral bands or sensor: Name required bands, wavelengths or a sensor type if known. Otherwise describe the measurement, such as visible appearance, vegetation, temperature, radar response or elevation.
- Height or 3D: For elevation or three-dimensional data, describe whether you need the ground surface, buildings or vegetation, along with the required vertical accuracy and reference system.
- Quality and coverage: Explain acceptable cloud, missing area or other limits. Check usable coverage within your boundary rather than only the whole image.
- Delivery and use: Specify the format, processing level, coordinate reference system, units and intended users when known. Check the license for your planned analysis, download, publication or sharing.
- Budget: Include an approximate range if useful, and review the full quote and delivery terms before ordering.
Practice the decision
Which observation would you choose?
Consider a fictional seasonal site comparison. Explore why a promising image may still be incomplete evidence.
Recent does not always mean relevant.
Imagine that your question compares this growing season with the same season last year. A beautiful image from yesterday helps with one side of that comparison. It does not supply the historical observation.
The date fits. The coverage still matters.
Now imagine a capture from the right week with part of your site hidden by cloud. It may support a statement about the visible area, but the missing part needs to stay missing in your conclusion.
A good fit is a set of conditions.
For this fictional task, the comparison needs suitable dates, usable coverage, enough detail, and a consistent method. Meeting one condition does not establish the others.
Fictional examples for learning. No live analysis is running.
Choose archive data or request a future capture.
Archive data comes from observations already captured. Check the actual capture date, footprint and quality against your brief. Ordering an archive product may still involve processing and delivery time.
A future capture request asks a provider to collect new observations during a specified window. Feasibility, collection conditions, accepted coverage and delivery terms need to be assessed before commitment. A requested date is not a confirmed observation.
Keep the capture date, the product’s processing or publication date and your delivery deadline separate. A product delivered today may describe a place years ago. A composite can combine observations from several dates.
Time also changes how places look. The USGS’s Petermann Glacier image series shows seasonal differences in snow, ice, shadows and illumination. Explore the USGS seasonal example.
Prepare a brief you can use to compare offers.
Keep the area, dates, spatial and spectral requirements, quality limits, format, intended use and deadline together. Separate requirements you must meet from preferences you can adjust.
If no option matches, consider a wider date window, a different sensor or a revised coverage requirement. Review how each change affects the delivery before choosing an alternative.
For a data-only request, the completed outcome is receiving the agreed data with its source information and usage rights. You can then use it in your existing workflow. Explore Milkypad’s analysis and app workflows when you want to go further with the data.
Explore Data acquisition to understand the request, ordering and delivery workflow.