#NAD83
Someone's apparently trying to revive legendary Bay Area radio station KFOG ... on a transmitter in Berkeley with an effective radiated power of *taps earpiece* THREE WATTS!?
fccdata.org?facid=788339
September 24, 2026 at 6:45 AM
Back in my oil exploration days, when making maps, we had to be careful if the data was NAD27 or NAD83. There was one infamous example of a well being drilled in the wrong location because the datums were mixed up. Now the exploration techs will have to worry about three datums.
September 11, 2026 at 5:56 PM
NAD27 was for North America, & the ellipsoid touched the surface of the Earth at the center of the US. So it was accurate in Kansas, but the further away from there, the more distortion there was. The NAD83 update placed the ellipsoid at the center(-ish) of the Earth, & not touching the surface.
September 11, 2026 at 1:49 PM
Have not experienced the annoyance of datasets in both NAD27 and NAD83 or moved on to annoyance at state plane and state utm projections.
September 11, 2026 at 2:31 AM
I'd get into the changes between NAD27 & NAD83, & what they're for, but it's one of those things that wouldn't really mean anything to anyone. They matter a lot when it comes to GIS data & cartography, but it doesn't really impact the average person. You would likely never notice the difference.
September 11, 2026 at 2:21 AM
The only thing changing are the NAVD88 and NAD83 datums. These only cover North America and are actually split into several smaller projections. Some states have multiple projections within the state. These projections are what surveyors utilize to be able to use Cartesian coordinates on a geoid.
September 11, 2026 at 2:18 AM
They're updating the mathematical model for the Earth. Again. First there was NAD27, which was replaced by NAD83 / WGS84. Now NAD83 / WGS84 are being replaced with GEOID2022.

I've used map data that was using NAD27 in Florida, & it was a mile off from where it was supposed to be.
September 11, 2026 at 2:14 AM
Thousands of args !
Foud "more complete" field definition but ....

Latitude:
Format:
Numeric
8 digits
2 decimals
(999999.99)
Units:
Degrees, minutes, seconds and decimal seconds (DDMMSS.99)
NAD83 or WGS84

(which is useless number).

The other place as decimal lat/long with 6 decimals points […]
Original post on cosocial.ca
cosocial.ca
August 11, 2026 at 5:05 AM
Coordinate Operations Error for NAD83(2011) Alaska Zone 1
I am receiving the following error below when running gdalwarp to crop an input orthomosaic in the NAD83(2011)-Alaska Zone 1 CRS. The command still runs and the output cropped TIFF file renders fine when opening in QGIS or ArcGIS. What could be causing this error? I am trying to understand if GDAL does not fully support NAD83-Alaska Zone 1. Also, the input GeoTIFF and shapefile are both in NAD83-Alaska Zone 1. EPSG:6394 info: https://epsg.io/6394 gdalwarp command: gdalwarp -of GTiff -cutline [shapefile] -crop_to_cutline [input-tif] [output-tif] -wo NUM_THREADS=ALL_CPUS -co BIGTIFF=YES -co TILED=YES -co COMPRESS=JPEG -multi gdal version: 3.0.2 Terminal Output: -------------------------------------------- ERROR 6: Cannot find coordinate operations from `EPSG:6394' to `BOUNDCRS[SOURCECRS[GEOGCRS["NAD83(2011)",DATUM["NAD83 (National Spatial Reference System 2011)",ELLIPSOID["GRS 1980",6378137,298.257222101004,LENGTHUNIT["metre",1]],ID["EPSG",1116]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]],CS[ellipsoidal,2],AXIS["geodetic latitude (Lat)",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]],AXIS["geodetic longitude (Lon)",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]]]],TARGETCRS[GEOGCRS["WGS 84",DATUM["World Geodetic System 1984",ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1]]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433]],CS[ellipsoidal,2],AXIS["latitude",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433]],AXIS["longitude",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433]],ID["EPSG",4326]]],ABRIDGEDTRANSFORMATION["Transformation from NAD83(2011) to WGS84",METHOD["Position Vector transformation (geog2D domain)",ID["EPSG",9606]],PARAMETER["X-axis translation",0,ID["EPSG",8605]],PARAMETER["Y-axis translation",0,ID["EPSG",8606]],PARAMETER["Z-axis translation",0,ID["EPSG",8607]],PARAMETER["X-axis rotation",0,ID["EPSG",8608]],PARAMETER["Y-axis rotation",0,ID["EPSG",8609]],PARAMETER["Z-axis rotation",0,ID["EPSG",8610]],PARAMETER["Scale difference",1,ID["EPSG",8611]]]]' Creating output file that is 185799P x 213951L. Processing rw-11-29a.tif [1/1] : 0ERROR 6: Cannot find coordinate operations from `EPSG:6394' to `BOUNDCRS[SOURCECRS[GEOGCRS["NAD83(2011)",DATUM["NAD83 (National Spatial Reference System 2011)",ELLIPSOID["GRS 1980",6378137,298.257222101004,LENGTHUNIT["metre",1]],ID["EPSG",1116]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]],CS[ellipsoidal,2],AXIS["geodetic latitude (Lat)",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]],AXIS["geodetic longitude (Lon)",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9122]]]]],TARGETCRS[GEOGCRS["WGS 84",DATUM["World Geodetic System 1984",ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1]]],PRIMEM["Greenwich",0,ANGLEUNIT["degree",0.0174532925199433]],CS[ellipsoidal,2],AXIS["latitude",north,ORDER[1],ANGLEUNIT["degree",0.0174532925199433]],AXIS["longitude",east,ORDER[2],ANGLEUNIT["degree",0.0174532925199433]],ID["EPSG",4326]]],ABRIDGEDTRANSFORMATION["Transformation from NAD83(2011) to WGS84",METHOD["Position Vector transformation (geog2D domain)",ID["EPSG",9606]],PARAMETER["X-axis translation",0,ID["EPSG",8605]],PARAMETER["Y-axis translation",0,ID["EPSG",8606]],PARAMETER["Z-axis translation",0,ID["EPSG",8607]],PARAMETER["X-axis rotation",0,ID["EPSG",8608]],PARAMETER["Y-axis rotation",0,ID["EPSG",8609]],PARAMETER["Z-axis rotation",0,ID["EPSG",8610]],PARAMETER["Scale difference",1,ID["EPSG",8611]]]]'
gis.stackexchange.com
July 26, 2026 at 4:05 PM
Me: Why do QGIS/ArcGIS/MAPublisher have 1000s of default projections?

My data: Have you heard of NAD83(2011) / Arizona Central?

epsg.io/6404
NAD83(2011) / Arizona Central - EPSG:6404
EPSG:6404 Projected coordinate system for United States (USA) - Arizona - counties Coconino; Maricopa; Pima; Pinal; Santa Cruz; Yavapai. State law defines use of International feet (note: not US surve...
epsg.io
July 20, 2026 at 7:01 PM
QGIS 3.44.12-Solothurn - Vertical transformation with GEOID18
I have been trying to get QGIS on Windows 10 to convert NAD83(2011) LongLatEllipsoidHeight files to NAD83(2011) / UTM zone 12N with NAVD88 orthometric elevations by applying GEOID18. It seems that recent versions of QGIS installed either by using osgeo4w-setup.exe or with an MSI installer no longer get a full set of proj files. Started with Ver 3.40 and did not have much luck changing the vertical; even the predefined CRS "NAD83(2011) + NAVD88 height EPSG:6349" did not do anything to transform the vertical. So following the seemingly logical assumptions that QGIS uses the version of proj that is installed with QGIS and cs2cs also uses proj, I decided to break the process down into steps. Opened the OSGeo4W Shell and entered - echo -109.0000000000 44.000000000 1500.000 | cs2cs +init=epsg:6319 +to +init=epsg:6341+5703 -f "%.3f" and things worked fine with cs2cs: successfully converted from 3D NAD83(2011) LLh to NAD83(2011) / UTM zone 12N easting/northing with NAVD / GEOID18 elevations shown below - 660349.4106 4873817.3333 1510.1279 Then I decided to update to the latest LTR version of QGIS. All the online wisdom indicates that doing that through osgeo4w-setup.exe is the way to go and that is how my Ver 3.40 was installed. For some reason that attempt went sideways and I ended up having to go through Control Panel to remove OSGeo4W and reinstall, again using osgeo4w-setup.exe. Now with Ver 3.44.12 freshly loaded I opened the new OSGeo4W Shell and tried the cs2cs command issued earlier and it no longer worked, it just converted the horizontal information to UTM zone 12N leaving the vertical information the same. Checked the contents of C:\OSGeo4W\share\proj and found there were very few files there - had checked there when 3.40 was installed and there were a bunch of geoid files and other things. It appears that at some time in the past I had downloaded from https://download.osgeo.org/proj/ a file named proj-datumgrid-north-america-1.3.zip and copied the contents to the C:\OSGeo4W\share\proj directory, so I did that again. Now cs2cs works fine again. NOTE: All the geoid files installed this way have a GTX extension. cs2cs must like them, as it resumed working? On a second Windows 10 PC that had QGIS Ver 3.34.11 installed, and the C:\OSGeo4W\share\proj directory has 438 items. There is no indication I downloaded anything extra at the time I installed that one. Vertical transformation does not work here either. NOTE: All the geoid files installed on this PC have TIF extensions. cs2cs also works on this PC, so cs2cs must like TIF files as well? On a third Windows 10 PC I uninstalled the QGIS that had been installed using osgeo4w-setup.exe, then installed Ver 3.44.11 from an MSI installer. With that installation method, the proj files are now at C:\Program Files\QGIS 3.44.11\share\proj. That directory only has 16 items, none of which look like geoid models. In that configuration cs2cs no longer converts the vertical information. On the "main" Windows 10 PC when I attempt to transform to NAD88 via EPSG:6349 using the Predefined CRS the "Select Datum Transformations" screen appears. The when the top line is highlighted the proj line reads - +proj=pipeline +step +proj=unitconvert +xy_in=deg +xy_out=rad +step +inv +proj=vgridshift +grids=us_noaa_g2018u0.tif +multiplier=1 +step +proj=unitconvert +xy_in=rad +xy_out=deg Which indicates to me that proj is expecting a TIF file. Copied the file named us_noaa_g2018U0.tif from the second Windows 10 PC and put it in C:\OSGeo4W\share\proj on the main PC. Still did not work - no vertical transformation. This post is long because it details what I have tried and possibly eliminated so far. In the process I have waded through oceans of AI hallucination and found very little actual information on how to get this working. Any assistance will be greatly appreciated, from direction on which proj files to use from where on through setting up QGIS to accomplish this should-be-simple task. For "test data" one could simply use the data I sent to and received from cs2cs. Thanks!
gis.stackexchange.com
July 6, 2026 at 2:00 AM
Confused about how to perform a vertical grid shift
I'm struggling with how to perform a vertical grid shift. I've been searching through previous postings, and I still don't understand what needs to be done. For example, I would like to reproject a DTM that's in EPSG:26911 (I assume the heights are ellipsoidal; I don't have any additional information) to using EPSG:6340+5703 GEOID18. I'm attempting to do this using GDAL with the following: gdal raster reproject -s "+proj=utm +zone=11 +datum=NAD83 +units=m +no_defs" -d "+proj=utm +zone=11 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs +geoidgrids=g2018u0.gtx" --resolution 1.0,1.0 --dst-nodata -9999 -r bilinear --to ALLOW_BALLPARK=NO --to ONLY_BEST=YES --of COG --co COMPRESS=ZSTD --co LEVEL=16 --co PREDICTOR=3 --co BIGTIFF=YES -i .asc -o .tif When I compare the elevation values before and after, there is about a 25-30 m change in value, which doesn't seem right (I'm working with data from southern Nevada). Can I stay in UTM (or any projected CRS) while doing this, or do I need convert to longitude/latitude, do the vertical grid shift, and then reproject back to a projected CRS? I've also been trying to do something similar with LiDAR data using PDAL, and I'm not sure I've been doing that correctly. I'm sure I'm doing something wrong, but I have no idea what.
gis.stackexchange.com
June 5, 2026 at 2:09 AM