Calculate Degrees to Feet for a QGIS Buffer
Use this premium QGIS buffer calculator to convert angular distance in degrees to linear distance in feet, or convert feet back to degrees for latitude and longitude based buffering. This is especially useful when your layer is stored in a geographic coordinate system such as WGS 84 and buffer values are entered in decimal degrees.
QGIS Buffer Conversion Calculator
Enter a distance, choose the conversion direction, select latitude or longitude behavior, and optionally provide a latitude so longitude distances can be corrected for the Earth’s curvature.
Expert Guide: How to Calculate Degrees to Feet for a QGIS Buffer
When users search for how to calculate degrees to feet in a QGIS buffer, they are usually dealing with a common GIS problem: their data is stored in latitude and longitude, but the distance they need to buffer is expressed in feet. In a projected coordinate system, the answer is simple because the units are already linear. In a geographic coordinate system such as WGS 84, however, the coordinate units are angular degrees, not feet or meters. That means a buffer distance of 0.001 does not automatically communicate a consistent real-world distance everywhere on Earth.
This matters because QGIS can create buffers in whatever units the layer uses. If the layer is geographic, the buffer value is interpreted in degrees unless geodesic tools or reprojection workflows are used. For quick analysis, preliminary mapping, or data auditing, many analysts need a dependable way to estimate degree-to-feet conversions before choosing a final workflow. That is exactly what this calculator is designed to do.
Why degree-to-feet conversion is tricky in GIS
The Earth is curved, but GIS software often represents it on a flat map. Degrees of latitude and degrees of longitude are angular measurements on the globe. A degree of latitude is relatively stable from place to place, while a degree of longitude changes dramatically with latitude. Near the equator, one degree of longitude is about the same length as one degree of latitude. Near the poles, the length of one degree of longitude becomes very small.
If you use a geographic layer in QGIS and apply a buffer directly in degrees, the visual result may look acceptable at a glance, but the real-world linear distance can be misleading. A buffer of 0.01 degrees in Florida is not the same number of feet as 0.01 degrees in Alaska if you are measuring in the east-west direction. That is why latitude-aware conversion is essential.
The practical formulas used in this calculator
For everyday GIS estimation, a widely used shortcut is to treat one degree of latitude as approximately 364,000 feet. This comes from the fact that one degree of latitude is about 69 statute miles, and 69 miles multiplied by 5,280 feet per mile is roughly 364,320 feet. Many GIS analysts round that to about 364,000 feet for quick planning work.
Longitude requires a correction based on latitude:
- Feet per degree latitude: approximately 364,000 feet
- Feet per degree longitude: approximately 364,000 × cos(latitude in radians)
- Degrees to feet: degrees × feet per degree
- Feet to degrees: feet ÷ feet per degree
The cosine adjustment is the key. At latitude 0°, cosine is 1, so a degree of longitude is close to 364,000 feet. At latitude 60°, cosine is 0.5, so one degree of longitude is only about half that distance, or around 182,000 feet.
When should you use this approach in QGIS?
This approach is best used in the following situations:
- You need a quick estimate of what a degree-based buffer means in feet.
- You are reviewing old workflows built on geographic layers.
- You want to reverse-engineer a decimal-degree buffer into a more understandable linear distance.
- You need to estimate the degree equivalent of a target feet distance before testing a layer.
It is not the best approach for precision analysis. If your work affects property lines, environmental regulation, utility offsets, construction staking, public safety planning, or permit compliance, you should generally reproject your data into a suitable projected coordinate reference system before buffering. In most cases, that means choosing a local State Plane, UTM zone, or other regional projection that uses feet or meters.
Degrees versus feet in a QGIS workflow
The biggest conceptual mistake in beginner GIS work is assuming that all coordinate values can be measured directly the same way. They cannot. Geographic coordinate systems describe position on the globe using angular measurements. Projected coordinate systems describe position on a flat plane using linear measurements. Because buffers are distance-based, projected systems are usually the right place to do serious buffering.
| Coordinate Type | Typical Unit | Buffer Meaning in QGIS | Best Use Case |
|---|---|---|---|
| Geographic CRS (example: EPSG:4326) | Degrees | Buffer value interpreted as angular distance | Quick display, global reference, rough estimation |
| Projected CRS (example: UTM, State Plane) | Feet or meters | Buffer value interpreted as linear distance | Accurate analysis, engineering, regulation, mapping production |
Real statistics: how longitude length changes by latitude
The variation in longitude distance is not minor. It is substantial. The table below shows approximate feet per degree of longitude at several latitudes using the cosine rule with a base of 364,000 feet per degree.
| Latitude | Cosine of Latitude | Approx. Feet per Degree of Longitude | Approx. Miles per Degree of Longitude |
|---|---|---|---|
| 0° | 1.0000 | 364,000 ft | 68.94 mi |
| 15° | 0.9659 | 351,588 ft | 66.59 mi |
| 30° | 0.8660 | 315,224 ft | 59.70 mi |
| 45° | 0.7071 | 257,384 ft | 48.75 mi |
| 60° | 0.5000 | 182,000 ft | 34.47 mi |
| 75° | 0.2588 | 94,203 ft | 17.84 mi |
These values illustrate why longitude-based buffering in a geographic CRS can become highly distorted in real linear terms. At 60° latitude, a one-degree east-west span is only about half the size it is at the equator. At 75°, it drops to less than 100,000 feet.
Step-by-step: converting a QGIS degree buffer into feet
- Identify whether the buffer follows a latitude-like or longitude-like interpretation for your use case.
- If it is longitude-based, determine the representative latitude of your study area.
- Find the feet-per-degree value.
- Multiply the degree value by feet per degree.
- Review whether the estimate is acceptable or whether you should reproject.
Example: suppose you buffered a layer by 0.002 degrees and your map is centered near 40° latitude. If you are approximating a longitude distance, cosine 40° is about 0.7660. Multiply 364,000 by 0.7660 to get about 278,824 feet per degree. Then multiply by 0.002. The result is about 557.65 feet. That is a reasonable estimate for the east-west component.
Step-by-step: converting feet into decimal degrees
- Choose latitude or longitude.
- If longitude, enter the latitude of the study area.
- Calculate feet per degree.
- Divide the target feet distance by feet per degree.
- Use the resulting decimal degree value only as an estimate for geographic-coordinate work.
Example: you need roughly a 500-foot buffer in a dataset stored in EPSG:4326 at 34° latitude. If you are estimating longitude, feet per degree longitude is approximately 364,000 × cos(34°), or around 301,780 feet. Then 500 ÷ 301,780 = 0.001657 degrees. That gives you a quick working value, but a projected CRS would still be the more accurate method.
Best practice in QGIS: reproject before buffering
The best professional workflow is usually simple:
- Inspect the layer CRS.
- Choose an appropriate local projected CRS in feet or meters.
- Reproject the layer or use a processing tool that supports distance in a projected environment.
- Apply the buffer using the desired linear distance.
- Reproject the result back to a geographic CRS only if needed for sharing or web mapping.
This avoids the entire problem of trying to interpret angular units as linear distance. It also gives you more defensible results in reports, audits, and public-facing maps.
Authoritative references for geospatial distance and Earth measurements
If you want official guidance on coordinate systems, map projections, and geodetic measurement concepts, review these resources:
- USGS: How much distance does a degree, minute, and second cover on maps?
- NOAA: National geodesy, mapping, and Earth measurement resources
- University of Texas GIS Guide: Geographic versus projected coordinate systems
Common mistakes people make
- Using the same degrees-to-feet factor for longitude at every latitude.
- Forgetting that QGIS buffers use the layer’s native units unless tools or settings indicate otherwise.
- Applying a single conversion factor across large north-south study areas.
- Treating estimate formulas as survey-grade measurement.
- Ignoring projection choice when final accuracy matters.
How accurate is the 364,000-foot shortcut?
It is useful, but it is still an approximation. The Earth is not a perfect sphere, and the exact distance represented by one degree varies slightly due to ellipsoidal geometry. For many planning, educational, and exploratory GIS tasks, the approximation is acceptable. For legal, engineering, navigation, or high-accuracy environmental work, use more rigorous geodetic or projected methods. The farther your project extends geographically, the more important it is to choose a proper CRS and avoid one-size-fits-all conversion shortcuts.
Final takeaway
To calculate degrees to feet for a QGIS buffer, you need to know whether you are estimating a latitude or longitude distance and, for longitude, what latitude your project occupies. A quick rule is that one degree of latitude is about 364,000 feet, while one degree of longitude equals about 364,000 multiplied by the cosine of latitude. Multiply by degrees to get feet, or divide feet by the local feet-per-degree value to get degrees.
That makes this calculator a practical helper for interpreting or estimating QGIS geographic-coordinate buffers. Still, if your output must stand up to scrutiny, project your data into a suitable linear CRS and buffer there. In GIS, the right coordinate system is often the difference between a rough estimate and a trustworthy result.