📘 Screen: Field Map Importer
The Field Map Importer registers the whole farm at once, from a single KML file. If the agronomist handed over a Google Earth file with the farm's 80 fields drawn, each drawing in that file becomes a field in the system, already with its boundary and the area in hectares calculated — no typing field by field.
📍 Location in the system
Menu: Crops > Field Map Importer
🧩 Main function
It is the bulk import of the farm map. Each area drawn in the KML (what Google Earth calls a Placemark) becomes a field with its coordinates. The screen shows everything it read from the file before saving, so you can check it and only then confirm.
🗺️ How it differs from the import on the Field screen
Both screens import KML, but they solve different problems:
- On the Coordinates tab of the Field screen you import the boundary of one field that is already registered (and shapefile works there too)
- Here you import several fields at once, creating the records that don't
exist yet — but only in
.kml
📝 Step by step
- Upload the
.kmlfile in the screen's upload area - Check the list the system builds — one row per area read from the file
- Click "Import fields" to save
Large files take a few seconds: the progress bar shows how many fields have already been processed.
📝 List columns
| Column | Description |
|---|---|
| Sector | Comes from the name of the KML folder the area is in. If the areas in Google Earth are organized in folders by sector (e.g., "Headquarters", "Retiro"), the sector comes in already filled |
| Code | Read from the file's extra data, when present — the system looks for ID, CODIGO or COD |
| Name/Description | The name of the area in the KML. If the area has no name, the system looks in the extra data (LEGENDA, NOME, NAME, DESCRICAO, TALHAO, DESC) and, as a last resort, generates a name from the sector and a sequential number |
| No. of points | How many points make up the boundary of that area |
| Area | Area in hectares, calculated by the system from the boundary itself — it isn't typed in |
| Status | What will happen to that row when you confirm (see the table below) |
🚦 The four statuses
| Status | What it means |
|---|---|
| New field + coordinates | No field with that name exists. The record and the boundary will be created |
| Coordinates import | A field with that name already exists. The record is kept and only the coordinates are updated |
| Duplicate name | Another area in the same file already used that name. Only the first one is imported; this one is ignored |
| No coordinates | The area has no usable polygon (fewer than three points). It isn't imported |
Only rows with the first two statuses are saved. When the import finishes, the list keeps on screen only what was not imported — so you can see the reason, fix the file and try again.
🔐 Permission
The screen uses the add permission of the Field record. Users without that permission can see the screen but can't upload the file or import.
- The whole farm is registered in minutes, with the boundary of each field
- The area in hectares comes from the drawing itself, without relying on typing
- The fields are ready to receive the Season Planting and show up in the app
- Redoing the map after a re-survey doesn't register anything again: it only updates the coordinates
❓ Frequently asked questions
How do I register all of the farm's fields at once?
Use the Field Map Importer, under Crops > Field Map
Importer. Upload a single .kml file with all the areas drawn: each area becomes
a field, with its boundary and the area in hectares already calculated.
Will the import duplicate the fields I've already registered?
No. When a field with the same name already exists, the system keeps the record and imports only the coordinates into it — the row shows the status Coordinates import. The comparison is by name and isn't case-sensitive.
Can I import a shapefile here?
Not on this screen: it only accepts .kml. For shapefiles, use the Coordinates tab
of the Field record, which accepts the
.shp, .shx and .dbf files — but there it's one field at a time.
Some fields came in with the wrong name or no name. Why?
The name comes from the name of the area inside the file. If the area has no name, the system tries to use the KML's extra data and, if it finds nothing, builds a name from the sector and a number. Rename the areas in Google Earth before exporting and the list will come in right.
A row shows "No coordinates". What should I do?
That area doesn't have a usable closed boundary — the system needs at least three points forming a polygon. Loose points, lines and empty areas aren't imported. Redraw the area as a polygon in Google Earth and export again.
Where does the sector of the imported fields come from?
From the name of the folder the area is in inside the KML. If you organize Google Earth in folders by sector before exporting, all the fields come in with the sector already filled — which helps later when filtering and grouping reports.