Signup Sample Report


Signup for a free 7 Day account and view Marcellus, Utica, Eagle Ford, and Antrim shale map layers in Pennsylvania, Ohio, West Virginia, Texas, and Michigan. Subscribe to view recent Lease Offers and Available Property, and additional pipeline layers. Click the Free Signup to get started, no software downloads required! (Firefox is recommended Browser)

Recent Maps


EQT Wetzel Co WV Permit Location 02-2016


Chesapeake Jefferson Co OH 12 2015 Permit.Pipeline


Gulfport Belmont Permit Location 11-24-2015


11-2015 Gulfport Belmont Co Permit


XTO Belmont Co Permit Loc w/Pipelines

Ten Lease Data Fields Worth Exporting Every Time

A lease record is more useful when it can leave the mapping platform in a structured, repeatable format. Exporting the same core fields for every property creates a dependable dataset for screening opportunities, comparing mineral rights, monitoring obligations, and sharing due diligence with colleagues or advisers.

This matters to Australian users assessing US shale investments from Brisbane, Perth, Melbourne, or regional offices. The terminology and ownership systems differ from Queensland’s Surat Basin or Western Australia’s Canning Basin, yet the need is familiar: a lease file should show who controls the rights, what was agreed, where the property sits, and how its value may change.

Why A Consistent Lease Export Matters

A browser map is excellent for exploring patterns, but it is not always sufficient for a portfolio review. A downloaded spreadsheet or GIS file lets you filter leases by expiry date, compare royalty terms, join records to permits, and identify gaps before a landman, solicitor, engineer, or investment committee reviews the opportunity.

Consistency is the key. If one lease is exported with a legal description and another only has a map label, later comparisons become unreliable. A standard export template also helps Australian teams translate US county-level information into familiar workflows involving title review, risk registers, valuation models, and investment approvals.

The lease identifier should be stable across every export, even when a property changes status or receives a new offer. Record the state, county, shale play, operator, and source date alongside it. A “last checked” field is especially useful when data is being reviewed from Australia, where a time-zone difference can make a supposedly current record several hours or a day out of date.

Ownership And Land Description

The first essential field is the lessor or mineral-rights owner, including the recorded ownership type where available. Capture whether the interest is held by an individual, family trust, company, estate, public body, or another entity. Add the lease status, such as offered, active, expired, assigned, producing, or under review, so a contact list is not mistaken for a current contractual position.

The second field is the legal land description. Include parcel identifiers, survey information, section or tract references, county and state, and any available GIS geometry. A street address alone is often inadequate in rural US shale areas, just as a lot address may not identify the relevant tenement or access arrangement in regional Australia.

The third field is the net mineral acreage, supported by gross acreage where it is available. Net mineral acres provide a more realistic basis for comparing exposure because a large tract may be divided among several owners or subject to existing burdens. Store the acreage units explicitly and preserve the original source value rather than silently rounding it.

Boundary context can prevent expensive misunderstandings. When a lease overlaps a school district, municipality, conservation area, or other planning boundary, an overlay checklist can help structure the review. Australian users will recognise the same principle from checking local government areas, environmental overlays, and Native Title considerations before relying on a mapped boundary.

Commercial Terms And Timing

The fourth field is the financial consideration. Export the signing bonus, offer amount, annual rental, extension payment, and currency, with a note explaining whether the value is per acre, per tract, or a total figure. A simple number without its unit or payment trigger can distort a portfolio comparison.

The fifth field is the royalty and economic interest structure. Capture the gross royalty rate, overriding royalty, working interest, deductions, and any production-based adjustments. Include a source note where the figure is inferred from an offer rather than confirmed in the executed lease. This distinction is important when comparing US opportunities with Australian gas projects, where royalty, tax, and state-based tenure arrangements operate differently.

The sixth field is the lease term. Record the effective date, primary term, extension periods, renewal rights, expiration date, and any hold-by-production language. Dates should be stored in an unambiguous format such as ISO year-month-day, while the original wording can remain in a notes field for legal review.

An expiration date should never stand alone. Add the event that may extend it, such as drilling, production, payment, unitisation, or force majeure. A lease that appears close to expiry may have substantial remaining value if production has preserved the term, while an apparently long-dated lease may carry an approaching payment or performance obligation.

Obligations, Wells And Permits

The seventh field is the obligation schedule. Export minimum drilling requirements, delay rentals, shut-in payments, continuous-development clauses, depth limitations, pooling or unitisation provisions, and assignment restrictions. These terms influence both risk and strategy, particularly when an investor is deciding whether to farm out, renew, sell, or retain an interest.

The eighth field is the linked activity record: wells, drilling permits, permit dates, well status, operator, production indicators, and completion information. Keep permit numbers and API or equivalent well identifiers where available. Linking the lease to nearby or intersecting wells makes it easier to distinguish a speculative tract from one supported by active development.

The ninth field is infrastructure and access. Include nearby gathering lines, processing facilities, highways, water access, compressor stations, and known surface-use constraints. Infrastructure can change the commercial value of a lease substantially; the gathering-line valuation notes provide useful context for assessing how midstream proximity may affect an offer.

This is where Australian operating experience can sharpen review. In the Surat Basin, gathering and processing access is central to development economics, while remote Western Australian projects may face greater transport and service constraints. For a US lease, record distance to infrastructure and the measurement method used, rather than treating a visual map proximity as a confirmed connection.

Mapping, Evidence And Data Quality

The tenth field is a source and confidence record. Store the originating dataset, export date, map layer, document reference, contact or file path, and a confidence rating. Add a short explanation for unresolved conflicts, such as acreage differences between a county record, an operator map, and a mineral-rights listing.

Geometry deserves its own validation step even when it is stored within the same record. Preserve the coordinate reference system, polygon or point type, and any parcel tolerance. A lease boundary that appears aligned at one zoom level may shift when combined with permit, pipeline, or property layers from another source.

For acquisition screening, separate confirmed facts from estimates. Mark a royalty as “reported,” “calculated,” or “unverified”; distinguish a proposed lease from an executed document; and identify whether a well is inside the tract or merely nearby. This improves auditability when records move from an analyst’s spreadsheet into a valuation model or legal due-diligence file.

Data quality is also a practical issue for Australian teams working across different state systems and US counties. State agencies may publish information at different intervals, local records may use varying legal descriptions, and a US county boundary does not carry the same administrative meaning as a Queensland local government area. A clear source trail keeps those differences visible.

A Practical Export Routine

A useful export process combines structured fields with a small amount of explanatory text. Use controlled values for status, play, operator, and lease type, then retain a notes column for unusual clauses or unresolved title issues. This makes filtering possible without stripping away the context that a reviewer needs.

Run the export at a defined frequency and save dated versions rather than overwriting the previous file. A monthly review may suit a stable investment portfolio, while active lease offers, permit-heavy areas, or approaching expiries justify more frequent checks. Preserve both the raw export and any cleaned working file so calculations can be traced.

Use these recommendations as a repeatable quality check:

  • Create one standard template for every lease, regardless of state, county, operator, or shale play.
  • Store dates in a consistent format and record the event that controls any extension or expiry.
  • Keep gross acreage, net mineral acreage, units, and the source for each figure.
  • Link leases to permits, wells, infrastructure, and property records using stable identifiers.
  • Separate confirmed contractual terms from estimates, inferred values, and marketing information.
  • Retain export dates, source references, geometry details, and notes about data conflicts.
  • Review sensitive ownership, title, and financial fields with the appropriate US adviser before relying on them.

A seven-day account can provide a practical starting point for testing this workflow with live map layers and property information. The available property data can help users compare lease records with surrounding mineral-rights opportunities, surface parcels, and other relevant layers before building a larger tracking file.

Begin with a small set of leases in one play, export the ten fields consistently, and test the results against your internal valuation or due-diligence process. Once the structure works, expand it across the portfolio and use Shale Navigator to keep the map layers, lease intelligence, and reporting workflow connected.



Welcome to ShaleNavigator
This online map application displays information specific to the leasing and development of shale plays in the United States, with particular focus on the Pennsylvania, Ohio, West Virgina, and New York's Marcellus and Utica shale leasing and drilling activity.

Data
Pipeline infrastructure, company land holdings, permit data, producing well data, and water impoundment sites provide base layers in the play, with other data layers our research team will continue to add and update regularly. Subscribers will be notified as new data are added. Our data is compiled from a variety of public and private sources for your use. We make every effort to review its quality. Contact us if you have high quality, relevant data and would like to become a data contributor.

Access ShaleNavigator
There is free registration to access ShaleNavigator's basic application and a resonably priced Subscription to access advanced data and map making, drawing, and sharing features.