Using Shapefile Imports to Analyse a Custom Acreage Block

A custom acreage block can represent far more than a boundary on a map. It may define a proposed lease position, a group of mineral parcels, a farm acquisition, a drilling target, or an area assembled from several ownership records. By importing that boundary into Shale Navigator, you can compare your own geographic model with shale plays, permits, lease activity, pipelines, property records and other available datasets.

This workflow is especially useful for Australian professionals assessing United States opportunities from Brisbane, Perth, Melbourne or regional offices. Australian terminology can differ from American oil and gas language, and a “block” may resemble a tenement, pastoral holding or assembled land position. The underlying method remains the same: prepare a reliable shapefile, import it with the correct coordinate reference system, inspect the overlap, and use the result to guide commercial due diligence.

Prepare The Shapefile Before Uploading

A shapefile is a small collection of related files rather than a single file. The geometry normally sits in the .shp file, while the attribute data is stored in .dbf and the projection information in .prj. The .shx index file is also commonly required. Keep these components together and use the same filename before uploading or compressing them for import.

The geometry should describe the acreage area you want to analyse. A polygon is generally suitable for a lease block or project boundary, while multiple polygons can represent non-contiguous parcels. Remove duplicate features, accidental slivers and self-intersections where possible. If the source data comes from a surveyor, GIS consultant or public land registry, check whether the boundary reflects surveyed limits, a planning approximation or a proposed commercial area.

Attribute fields can make the imported layer easier to interpret. Include a project name, parcel identifier, gross acreage, net mineral acres, owner reference or internal status field if those details are available. These fields do not replace title research, but they help distinguish several blocks when multiple scenarios are loaded into the same workspace.

Check Coordinates And Projection

Coordinate errors are among the most common reasons a custom boundary appears in the wrong place. Before importing, identify the shapefile’s coordinate reference system and datum. Many United States datasets use a state plane system, UTM zone or a geographic system based on NAD83 or WGS84. A boundary prepared in Australian GDA2020 or GDA94 will describe a valid location, but it will not align with US shale data unless the project is deliberately located in Australia and the platform supports that use case.

For US acreage analysis, reproject the source data into a system appropriate for the target region when necessary. Do not simply rename the projection file or assume that latitude and longitude are interchangeable with projected metres. A GIS package can convert the layer while preserving the original as a backup. Record the source CRS, transformation method and export settings so the process can be repeated when a revised boundary arrives.

Australian users should pay close attention to local mapping habits. A Queensland consultant may supply data in a GDA2020 MGA zone, while a Western Australian project may use a different MGA zone. The same issue appears in the US when a block crosses state boundaries or when data from several vendors uses different datums. Consistency matters more than the label used for the acreage.

Import And Validate The Custom Block

After preparing the file, open the relevant map workspace in Shale Navigator and locate the shapefile import or custom-layer control. Follow the upload instructions for the account and select the prepared file package. If the application accepts a compressed archive, include the associated shapefile components together rather than uploading only the geometry file.

Once the layer appears, zoom to the imported extent and compare it with recognisable map features. Confirm that the block sits in the expected county, basin or state, and inspect each corner for distortions. A polygon in the wrong location can still look technically neat, so visual validation is essential. Use roads, rivers, town boundaries, well locations or public land outlines as practical reference points where available.

Give the layer a clear name that records the project and version, such as “Permian North Option June 2025” or “Marcellus Parcel Assembly A”. If the platform supports styling, use a strong outline and a transparent fill. This allows underlying permits, pipelines and property information to remain visible. If the imported layer contains several polygons, apply consistent styling while retaining parcel attributes for individual review.

Compare The Block With Available Data

The value of a custom boundary comes from the comparisons it enables. Turn on relevant shale play layers first to see whether the acreage lies inside, partly inside or outside a recognised development area. Then review drilling permits, existing wells, lease offers, pipeline corridors and available mineral rights. The relationship between these layers can reveal whether a block is near active infrastructure or isolated from current development.

Use the boundary as a screening tool rather than treating every overlap as proof of value. A pipeline crossing an acreage block may have limited capacity, restricted access or an unsuitable connection point. A permit near the boundary may target a different formation or have expired. Likewise, an available mineral-rights listing may require separate verification of ownership, leasing status, depth rights, royalty terms and encumbrances. Available property data can help identify areas for further investigation, but it should be tested against current records and professional title work.

For an Australian investment committee, organise the findings into a short evidence set. Record the percentage of the block inside the target play, the number and status of nearby permits, the distance to gathering or transmission infrastructure, and any visible competing land positions. This makes a US opportunity easier to compare with familiar Australian resource assessments, where tenure, access, infrastructure and development timing are considered together.

Turn Spatial Results Into A Decision

A shapefile import becomes commercially useful when its results are connected to a defined decision. A landman may use it to prioritise title research. An engineer may use it to examine well spacing and infrastructure access. A mineral-rights investor may compare a proposed acquisition with nearby lease activity. An attorney may use the map to identify parcels requiring document review, while a realtor or landowner may need a clearer picture of surrounding oil and gas activity.

Calculate simple measures from the map, such as gross area, intersected play area, distance to the nearest pipeline or count of nearby permits. Keep the measurement method consistent across candidate blocks. Acreage figures can vary because US records may distinguish gross acres, net acres, mineral acres and unit acres; an Australian reader should not assume that any single map measurement equals a legally transferable interest.

Use several versions of the boundary when negotiations are uncertain. A core case might include only confirmed parcels, while an upside case adds options or adjacent tracts. A risk case can exclude parcels with unresolved title, access or environmental concerns. Label these scenarios clearly, retain the source files and note the date of every supporting dataset.

Start the review with a free seven-day account, import a clean boundary and test the map against the questions your project must answer. Keep the original shapefile, projection notes and validation records with your investment or land files, then share the resulting evidence with your geologist, solicitor, landman or commercial team before making a commitment.