gdal.org

GDAL is released under an MIT-style Open Source License by the Open Source Geospatial Foundation (OSGeo). That means you can use, modify, and redistribute it — including in commercial and closed-source products — as long as you preserve the copyright and license notice. If you want to contribute, the project documents its process through dedicated Community, How to contribute, and How to develop GDAL pages, and it also accepts sponsorship.

License basics

The GDAL documentation states the license directly on its main page: GDAL "is released under an MIT style Open Source License by the Open Source Geospatial Foundation." The site links to a License page for the full text.

What this generally allows under an MIT-style license:

• Use the library and its command line utilities for any purpose, including commercial work.
• Modify the source code and distribute your modified version.
• Redistribute original or modified copies.
• Sublicense and combine it with other code, including proprietary code.

The main obligation is attribution: keep the license and copyright notice with copies or substantial portions of the software. For the exact wording and any project-specific additions, read the License page rather than relying on the summary here.

Ways to contribute

The documentation lists several entry points, each aimed at a different kind of contribution:

Typical contribution paths for an open source geospatial project like this include reporting bugs, improving documentation, submitting code changes, and helping other users. The specific mechanics — where to file issues, how patches are reviewed, coding conventions — are described on the How to contribute and How to develop GDAL pages, so start there for the current process.

Citing GDAL in publications

If you use GDAL in academic or technical work, the documentation provides a Digital Object Identifier (DOI) that you can use to quote GDAL in publications. Using the DOI is the recommended way to reference the project so that citations resolve consistently.

Practical next steps

1. Read the License page for the authoritative terms before shipping GDAL in a product.
2. Check How to contribute? if you want to report a problem or send a change.
3. Check How to develop GDAL? if you plan to work on the source code.
4. Visit Community to find the right place to ask questions or discuss a proposal.
5. Use the provided DOI when citing GDAL in a paper or report.

One caveat: contribution workflows, review requirements, and community channels change over time. Treat the linked documentation pages as the current source of truth rather than any third-party summary.

If you're new to Ahrefs and want to run your first SEO audit, the fastest path is: open Site Explorer, enter your target URL, review the Overview for a health snapshot, then dig into Organic Keywords, Top Pages, and Site Audit to find specific problems. From there, build a short prioritized to-do list instead of trying to fix everything at once.

This tutorial walks through that workflow using a realistic starting scenario, explains what the numbers mean, and shows how to turn findings into actions.

Before You Start: Pick a Narrow Scope

A common beginner mistake is auditing an entire large website on day one. The reports become overwhelming, and you can't tell which issues matter.

Instead, choose one of these starting points:

• A single important page (your homepage or a key product/service page)
• A small site (under ~50 pages, e.g., a personal blog or small business site)
• One section of a bigger site (e.g., /blog/)

For this tutorial, assume you're auditing a small business site with about 30 pages. The same steps scale up later.

You'll need an Ahrefs account to follow along. Ahrefs offers paid plans, and pricing and feature limits change over time, so check the current Pricing page for what's included in each tier before committing.

Step 1: Enter Your Target in Site Explorer

Site Explorer is Ahrefs' core tool for analyzing any website or URL.

1. Open Site Explorer from the top navigation.
2. In the search box, paste your domain (e.g., example.com).
3. Choose the Exact URL or Domain mode depending on scope. For a full-site view, use Domain or Prefix; for a single page, use Exact URL.
4. Press Enter.

You'll land on the Overview report. Don't try to absorb everything — focus on four numbers first.

Reading the Overview Snapshot

Important caveat: Ahrefs' traffic and keyword numbers are estimates based on its own data. They won't match Google Search Console or your analytics exactly. Treat them as directional, not absolute.

Step 2: See What You Already Rank For

Go to Organic Keywords in the left sidebar. This shows queries where your site appears in search results.

Sort by Traffic (descending) to see which pages bring the most estimated visitors. Then look for:

• Keywords ranking in positions 4–15 — these are often the easiest wins. A small content or on-page improvement can push them onto page one.
• Keywords with high volume but low position — potential opportunities if the topic is relevant.
• Irrelevant keywords — if you rank for something off-topic, it may signal thin or mismatched content.

Write down 5–10 of the position 4–15 keywords. These become your first optimization targets.

Step 3: Find Your Best and Weakest Pages

Open Top Pages. This ranks your URLs by estimated organic traffic.

Look for two things:

1. Your top performers — understand what topics and formats work. Can you create more content like this?
2. Pages with traffic but poor rankings — these may need on-page fixes (title, headings, internal links).

If a page gets zero traffic and targets a topic you care about, it's a candidate for a rewrite or consolidation.

Step 4: Run a Technical Site Audit

Now move to Site Audit. This crawls your site and flags technical and on-page issues.

1. Click Site Audit → New project.
2. Enter your domain and set crawl settings (default is usually fine for a small site).
3. Start the crawl and wait for it to finish.

Once complete, you'll see a Health Score and a list of issues grouped by category.

Which Issues to Fix First

Not all issues are equal. Prioritize in this order:

Ignore low-impact warnings (like minor meta description length) until the big items are handled.

Step 5: Turn Findings Into a To-Do List

You now have raw data. Convert it into a short, actionable list. Example:

1. Fix 3 broken links found in Site Audit.
2. Rewrite title tags on 5 pages with duplicate titles.
3. Improve 4 pages ranking in positions 6–12 by adding missing subtopics and internal links.
4. Remove or update 2 thin pages with no traffic.

Keep the list to 5–10 items max for your first audit. Finishing a short list beats starting a long one.

Common Beginner Mistakes

• Chasing every red flag. Site Audit flags many minor issues. Fix what affects rankings and users first.
• Trusting estimates as exact numbers. Ahrefs data is modeled, not measured from your analytics.
• Auditing a huge site too early. Start small to learn the interface.
• Ignoring search intent. A page can be technically perfect but still fail if it doesn't match what searchers want.
• Forgetting to re-crawl. After fixes, run Site Audit again to confirm improvements.

Where to Go Next

Once your first audit is done:

• Compare with competitors using Site Explorer's Competing Domains and Content Gap reports.
• Track keyword rankings over time with Rank Tracker.
• Explore backlink opportunities in the Backlinks and Link Intersect reports.
• Set up recurring Site Audit crawls so new issues surface automatically.

Your first audit isn't about perfection — it's about building a repeatable habit: enter a target, read the key reports, pick the highest-impact fixes, and act. Do that once a month and your site's health compounds.

GDAL ships with a set of command line utilities for data translation and processing, and the documentation groups them under Programs, split into a gdal application and the "Traditional" applications. If you want to know what a specific tool does or how to call it, the fastest route is the Programs section of the GDAL documentation, where each program has its own page describing its parameters and usage. The utilities exist because GDAL is, at its core, a translator library for raster and vector geospatial data formats released under an MIT style Open Source License by the Open Source Geospatial Foundation — the command line tools are the packaged way to reach that library's translation and processing capabilities without writing code.

How the programs are organized

The documentation's Programs area is divided into two groups:

• The gdal application — the newer, unified command line entry point.
• "Traditional" applications — the long-standing individual utilities that predate the unified application.

Both groups are listed in the same Programs section, so you can browse either style depending on what you already have in your scripts or habits.

What the utilities are for

The stated purpose of the bundled utilities is data translation and processing. That covers the two data models GDAL exposes:

Because the library abstracts formats behind one model, the command line utilities can operate across the many raster and vector drivers GDAL supports rather than being tied to one file type. The driver list in the documentation is long and varied — raster drivers alone include entries such as AAIGrid, ADRG, AIG, COG, DTED, ECW, ENVI, and FITS, among many others.

Finding the right tool for a task

1. Go to the Programs section of the GDAL documentation.
2. Decide whether you want the gdal application or a "Traditional" application.
3. Open the page for the specific program — each one documents its own parameters and usage.
4. Match the tool to your task: translation (moving data between formats) or processing.

The expected result is that you end up on a single program page that tells you exactly which arguments to pass, rather than guessing from the library-level description.

Practical notes

• The documentation is also available as a PDF for offline browsing, which is useful if you need to look up program usage without network access.
• GDAL can be quoted in publications using its Digital Object Identifier, and the site maintains a NEWS page describing releases — the excerpt references the August 2026 GDAL/OGR 3.13.3 release.
• Download options listed include source code, binaries, and containers, so the utilities can be obtained in whichever form fits your environment.

Common sticking point

The main confusion is assuming there is one single command. There isn't — the documentation deliberately separates the gdal application from the traditional applications, and each program has its own page. If a command you remember doesn't appear where you expect, check the other group before concluding it doesn't exist.

GDAL supports a large and continuously growing list of raster and vector formats through a driver-based architecture. If your data is in a common geospatial format — GeoTIFF, COG, ENVI, ECW, Shapefile, GeoJSON, and hundreds more — GDAL almost certainly has a driver for it. The authoritative way to confirm support for any specific format is to check the official driver lists in the GDAL documentation, since coverage changes with each release.

How the driver model works

GDAL is a translator library for raster and vector geospatial data formats, released under an MIT-style open source license by the Open Source Geospatial Foundation. Rather than hard-coding format handling, it presents a single raster abstract data model and a single vector abstract data model to the calling application for all supported formats.

Each format is handled by a driver. A driver knows how to read (and often write) one family of files. When you open a dataset, GDAL identifies the matching driver and exposes the data through the same abstract model regardless of the underlying format. This is why the same command-line utility or API call can process a GeoTIFF, an ENVI file, or a JPEG with no code changes.

Two consequences follow from this design:

• Support is per-driver, not per-format-family. A format may be readable but not writable, or support may depend on how GDAL was built.
• The driver list is the source of truth. Because drivers are added, updated, and occasionally retired between releases, the documentation for your version is what determines what you can actually open.

Raster formats

The documentation maintains a dedicated Raster drivers section listing every supported raster format. Examples drawn from that list include:

The list also covers specialized scientific and remote-sensing formats such as CEOS, COSAR (TerraSAR-X), CPHD (Compensated Phase History Data), ERS, and many others. Some entries are generators rather than pure readers — COG, for instance, is described as a "Cloud Optimized GeoTIFF generator."

Vector formats

Vector data is handled the same way, with its own Vector drivers section. The documentation's index lists raster and vector drivers as separate top-level categories, so you can browse the vector list independently to check whether a given vector format is supported.

How to verify a specific format

1. Open the GDAL documentation for your installed version.
2. Go to the Raster drivers or Vector drivers section.
3. Search the list for your format name or file extension.
4. Read the individual driver page to confirm whether it supports reading, writing, or both, and whether it has build-time dependencies.

This matters because a driver's presence in the list does not guarantee it is active in your particular build. Some drivers depend on external libraries and may be compiled out.

Practical notes

• Check your version. The documentation notes the August 2026 GDAL/OGR 3.13.3 release, and driver coverage evolves between releases. A format supported in the current docs may not exist in an older installation.
• Offline reference. The documentation is also available as a PDF for offline browsing, which is useful when you need to check driver support on a machine without internet access.
• Command-line utilities. GDAL ships with a variety of command-line utilities for data translation and processing, so once you confirm a driver exists, you can typically convert or inspect the data without writing code.

If a format is not in the driver lists, GDAL cannot read it natively — you would need to convert it with another tool first, or check whether a newer release has added the driver.

GDAL is a translator library for raster and vector geospatial data formats, released under an MIT-style open source license by the Open Source Geospatial Foundation. You can get it in three ways — source code, prebuilt binaries, or containers — and the official documentation at gdal.org includes user API references, tutorials, and program descriptions to learn from. The right choice depends on whether you want to build from source, install a ready-made package for your OS, or run it in an isolated container.

What GDAL actually is

GDAL presents a single raster abstract data model and a single vector abstract data model to any calling application, regardless of which of the many supported formats the data is actually stored in. That abstraction is the core value: your code talks to one API, and GDAL handles the format-specific details. It also ships with a variety of command line utilities for data translation and processing, so you can work with geospatial data without writing any code at all.

The project is maintained by the Open Source Geospatial Foundation (OSGeo). The documentation notes the August 2026 GDAL/OGR 3.13.3 release on its NEWS page, so version 3.13.x is the current line described in the material.

Choosing how to get GDAL

The download page lists four distribution channels. Pick based on your environment:

If you just want to run gdal commands or call the library from Python, binaries or containers are the fastest route. If you need a specific driver compiled in, or you're on a platform without official builds, source is the fallback.

Installing

The exact commands depend on your operating system and package manager, and the documentation does not prescribe a single install path. The general flow is:

1. Go to the Download section of gdal.org.
2. Choose Source Code, Binaries, or Containers.
3. Follow the platform-specific instructions linked from that page.

For containers, the download page points to container images, which is the least invasive option if you don't want to touch your system's libraries. For binaries, you'll typically get a package for your OS. For source, you'll compile against your system's dependencies — expect this to take longer and require build tools.

Verify the install by running a GDAL command line utility from your shell. If it responds with usage information rather than "command not found," the install succeeded. The documentation's Programs section lists the available utilities so you know what to test.

Learning path

Once installed, the documentation is organized so you can go from zero to productive:

• Programs — the command line utilities. Start here if you want to translate or process data without coding. The docs distinguish the gdal application from the "Traditional" applications, so check which style matches your version.
• User API — the programming interface for calling GDAL from your own application. This is where the abstract raster and vector data models are documented.
• Tutorials — guided walkthroughs. These are the intended starting point for new users.
• Raster drivers and Vector drivers — the full list of supported formats. The raster list alone is long (AAIGrid, ADRG, COG, DTED, ECW, ENVI, and many more), so use it as a reference when you need to confirm a specific format is supported rather than reading it end to end.
• FAQ and Glossary — for terminology and common questions.

If you prefer offline study, download the PDF version of the documentation.

Practical notes

• The license is MIT-style and open source, so you can use GDAL in commercial and closed-source projects. The documentation points to a License page for the full text.
• If you publish work that uses GDAL, the docs provide a Digital Object Identifier (DOI) you can cite.
• The Community and How to contribute pages exist if you want to get involved or need help beyond the docs.
• The "Software using GDAL" page is useful for seeing real-world consumers of the library, which can help you judge whether it fits your stack.

Common sticking points

• Wrong channel for your platform. If no binary exists for your OS, containers or source are your options — don't assume a binary is available.
• Skipping the Programs vs. User API distinction. If you only need to convert files, the command line utilities are enough; the API is for embedding GDAL in an application.
• Assuming a format is unsupported. Check the raster and vector driver lists before concluding GDAL can't read your data — the coverage is broad.
• Version drift. The documentation reflects the 3.13.x line. If you install an older package from your OS repository, some documented behavior may differ.