Indicator
You get one wetland indicator for each parcel: high, medium, low, none, or not assessed. Its reasoning is written below the indicator.
Field verification is recommended
HighManyas example
Medium
Low
None
Not assessed
Wetland screening
Wetland screening uses the satellite archive to check, before the project starts, whether each parcel overlaps with a wetland. We deliver one result per parcel, with its reasoning, in a KMZ file that opens in Google Earth. When you set risky parcels aside at the first stage, your project file moves on to the next stages without them.
Send your parcel
2026 · partial yearWetland Indicator
- HighThis example
- Medium
- Low
- None
- Not assessed
- Field verification
- recommended
- Nearest open water
- 0 km
Wetland screening and Dynamic World land cover, 2026 (partial year) · 10 m · Lake Manyas area, Balıkesir (46,974 ha)
This dataset is produced for the Dynamic World Project by Google in partnership with National Geographic Society and the World Resources Institute. Contains modified Copernicus Sentinel data 2016, 2026 · CC BY 4.0 · © OpenStreetMap contributors
- Who it is for
- Those who want to check early whether their parcels qualify for a project
- What we deliver
- One result per parcel with its reasoning, in a KMZ file
- Indicator
- High, medium, low, none, or not assessed
- File language
- Turkish, English, or both
- Input
- Parcel boundary file (KML, KMZ, SHP, or GeoJSON) or corner coordinates
What you get
Reasoning
The reasoning shows which satellite observations support the result and which period they come from. The distance from the parcel to the nearest open water is also given in kilometers.
Wetland Screening
Wetland Indicator: High
Field verification is recommended.
Open-water indicators
- Permanent water, 12 months
Vegetated-wetland indicators
- Flooded vegetation 1.9%, strong
201 net observations
- 24Jan-Mar
- 69Apr-Jun
- 83Jul-Sep
- 25Oct-Dec
Nearest open water: 0 km · Coordinates: 40.1845°, 27.9720°
Field verification
When the indicator comes out high or medium, the file recommends field verification. A parcel without enough observations is marked "not assessed" and kept separate from the "none" result; for these parcels, you decide by reading the reasoning.
- HighMediumField verification is recommended.
- Not assessedKept separate from the "None" result; you decide by reading the reasoning.
Together with land cover
We run the screening in the same job as the land cover analysis; each parcel's KMZ file holds the land cover map next to the wetland result. The file is prepared in Turkish, English, or both.
- Info balloon
- The wetland indicator, its reasoning, and the cover table for both years
- Layers
- 2016 and 2026 land cover maps; 2026 is a partial year
- Language
- Turkish, English, or both
| 2016 | 2026 (partial year) | |
|---|---|---|
| Crops | 57.2% | 55.6% |
| Water | 32.2% | 31.9% |
| Trees | 3.2% | 3.4% |
| Built area | 2.5% | 2.9% |
| Grass | 3.3% | 2.5% |
| 2016 | 2026 (partial year) | |
|---|---|---|
| Flooded vegetation | 0.7% | 2.0% |
| Shrub & scrub | 0.9% | 1.7% |
| Bare ground | 0.1% | 0.1% |
| Snow & ice | 0.0% | 0.0% |
Dynamic World land cover, 10 m · Lake Manyas area, Balıkesir (46,974 ha) · percentages for 2016 and 2026
This dataset is produced for the Dynamic World Project by Google in partnership with National Geographic Society and the World Resources Institute. Contains modified Copernicus Sentinel data 2016, 2026 · CC BY 4.0 · © OpenStreetMap contributors
How we work
- 1
We take your parcel boundary file.
- 2
We set the scope together with you: which parcels to screen, which year or years the land cover map covers, and the file language.
- 3
We screen every parcel with the same settings; each observation period used appears in the file with its dates.
- 4
We deliver each parcel's KMZ file.
Turnaround time
With a system we built ourselves, we cut file and report preparation from months to weeks, even days.
What it documents
Shows with satellite observations whether the parcel bears signs of a wetland.
The indicator is based on observations of open water and vegetated wetland; the balloon states which observation contributed to the result and which period it comes from. This is a screening result: when the indicator is high or medium, the file recommends field verification.
Records the parcel's distance to the nearest open water in kilometers.
Even when the parcel has no overlap with a wetland, you see in the same file how close it is to the water's edge.
Records which period of satellite data the screening is based on.
The file states the years the indicator is based on and how many net observations were used; data for the current year runs up to the day the file was created. The indicator, the reasoning, and the land cover map sit in the same file, which you can add to your project records.
Inputs
What we need from you
- Parcel boundary file: KML, KMZ, SHP, or GeoJSON. Without a file, a list of parcel corner coordinates is enough; we draw the boundaries.
- One year for the land cover map, or two years to compare, from 2016 to this year. We set the screening's observation periods based on the job date.
- Your cut-off date, if any; we choose the land cover years accordingly.
- File language: Turkish, English, or both.
What we prepare
- One wetland indicator per parcel
- The indicator's reasoning and observation periods
- The distance to the nearest open water, in kilometers
- The parcel's land cover map, in the same KMZ file
Pilot
Let's first screen a single parcel, set up for your goal; once you have seen the result, move on to the whole portfolio.
Other services
Batch parcel analysis
We analyze every parcel in your portfolio for your chosen periods with the same settings.
View
Land cover
We deliver a Google Earth file showing which parts of the parcel are trees, crops, water, or built area, and how that changed over the years.
View
Change and loss detection
We map where and how much changed between two dates; for fire and cover loss, we provide the event period and a change table relative to the cut-off date.
View
Land cover: Esri, Impact Observatory, Microsoft · Contains modified Copernicus Sentinel data 2020, 2024, 2026 · CC BY 4.0 · clipped to the parcel · © OpenStreetMap contributors