Import Your Paddock Boundaries from a Map File

Which Paddock Map Files Can I Import?

P2PAgri imports paddocks from a zipped shapefile, KML, KMZ or GeoJSON file, the formats almost every farm mapping and precision ag program can export:

• Shapefile, zipped: a shapefile is really a bundle of files, so put the .shp, .dbf, .shx and .prj files together in one .zip and import the zip.
• KML or KMZ: the format Google Earth, Google My Maps, Back Paddock and many other programs save.
• GeoJSON: files ending in .geojson or .json, for example from geojson.io or a mapping program.

How to Import Paddock Boundaries into P2PAgri

Four steps, and nothing changes on your farm until you save:

1. Open the Paddock screen for the farm the paddocks belong to and choose Import paddocks.
2. Pick your shapefile zip, KML, KMZ or GeoJSON file.
3. Review the result. Every shape from the file is drawn over the paddocks you already have, alongside its name, hectares and what the import will do with it: create a new paddock, give an existing one its boundary, replace a boundary, or skip it.
4. Save. Every paddock you chose is created or updated in one go, with its boundary on the map.

The import has its own short walkthrough inside the platform, so you are guided through it the first time.

How Do I Export Paddocks from Agworld, Back Paddock or Google Earth?

P2PAgri does not connect to other mapping programs directly. The file is how the paddocks come across, and every program below can produce one in a few clicks:

• Agworld: open the farm map, choose Export, then Shapefile or KML.
• Back Paddock: export your paddocks as KML.
• Google Earth (web): open your project, click the three-dot menu and choose Export as KML file.
• Google My Maps: open the map, click the three-dot menu and choose Export to KML/KMZ.
• Yield maps: ask your agronomist or precision ag contractor for the paddock files as a zipped shapefile.

Paddock names are read from the file wherever the program saved one. Agworld, Back Paddock and Google Earth all do. If a shape has no name, P2PAgri calls it Paddock 1, Paddock 2 and so on, and you can type the right name on the review screen before saving.

Your Existing Paddocks Are Never Overwritten by an Import

Every shape is matched to your existing paddocks by name. That means no duplicates, and nothing you have already set up or drawn is touched unless you tell the import to replace it:

• A paddock you have set up but never drawn takes its boundary from the file. Its figures are left alone.
• A paddock that is already mapped is skipped automatically and marked "Already mapped". Choose "Replace boundary of" on that row if you do want the file to take over.
• Anything that does not match a name becomes a new paddock.

The totals at the bottom of the review screen tell you exactly what Save is about to do: how many paddocks will be created, how many existing ones get a boundary, and how many shapes are being skipped. If any part of the import cannot be saved, nothing is saved and the screen tells you which row caused it, so you never end up with half a file imported.

Turn a Yield Map into Paddock Boundaries

P2PAgri turns a season's worth of yield maps into a full set of paddock boundaries in one import. The yield maps your precision ag contractor sends after harvest usually come as one shapefile per paddock, each made up of hundreds of small yield zones and no paddock name. P2PAgri recognises that layout. The zones are joined into a single outline per paddock, small gaps between zones are closed, and the paddock is named from the file name with the year taken off, so 2025_Woolshed.shp becomes a paddock called Woolshed.

Accurate Paddock Hectares, Whatever Program the File Came From

The area of every imported paddock is calculated from its boundary using the same maths the map uses when you draw by hand, so imported and drawn paddocks sit side by side with consistent figures. A few things the import takes care of:

• Whatever map projection your file uses, the import converts it so the paddocks land in the right place on the map. You do not need to know which projection it is.
• A dam or house block cut out of a paddock in the file is left out of the hectares, even though the map draws the paddock as one outline.
• A paddock stored as two separate pieces comes in as two paddocks, Home 1 and Home 2, so nothing is lost. Rename them on the review screen if you prefer.
• Points and lines in the file, such as trough markers or fence lines, are ignored. Only areas become paddocks.
• If the shapes sit a long way from the farm's location, the import warns you before you save, in case you picked the wrong file or the wrong farm.

Imported Paddocks Flow Straight into Your Gross Margins

Imported paddocks work exactly like paddocks you drew by hand. Set what each one is running this year in Production Cycles, and the hectares flow straight into crop gross margins per hectare, stocking rates in DSE per hectare, pasture carrying capacity and the colour-coded profitability overlay on the farm map.