Andrew, What does the query:
SELECT proj4text FROM spatial_ref_sys WHERE srid = 2277; Return on both your old and new. I get for 2.4.1 this: +proj=lcc +lat_1=31.88333333333333 +lat_2=30.11666666666667 +lat_0=29.66666666666667 +lon_0=-100.3333333333333 +x_0=699999.9998983998 +y_0=3000000 +datum=NAD83 +units=us-ft +no_defs I think we updated the spatial_ref_sys table in 2.4.0 to synch up with what Even Rouault provided (he manages GDAL development). So it's possible that is one of the entries changed. I notice you working ogr2ogr is using towgs84 and ellps=GRS80 So it wouldn't need the nad datum shift files whereas the definition in spatial_ref_sys does need it. I guess as a work-around you could update the spatial_ref_sys table to use the GRS80 towgs84 thing, though that still doesn't answer the question why your nad files don't seem to be picked up. Perhaps they never worked and you didn't notice since spatial_ref_sys table entry was different. I did a test transform going from 2277 to 4326 and didn't get an error SELECT ST_AsText(ST_Transform(ST_Transform(ST_SetSRID(ST_Point(-97.353287, 31.105862), 4326), 2277),4326)); POINT(-97.353287 31.1058619999995) Hope that helps, Regina -----Original Message----- From: postgis-users [mailto:[email protected]] On Behalf Of Andrew Joseph Sent: Thursday, November 09, 2017 4:44 PM To: [email protected] Subject: [postgis-users] [XX000] ERROR: AddToPROJ4SRSCache: could not parse proj4 string I receive the following error when running st_transform(geom,4326) on an ogr_fdw foreign table: [XX000] ERROR: AddToPROJ4SRSCache: could not parse proj4 string '+proj=lcc +lat_1=31.88333333333333 +lat_2=30.11666666666667 ++lat_0=29.66666666666667 +lon_0=-100.3333333333333 +x_0=699999.9998983998 +y_0=3000000 ++datum=NAD83 units=us-ft +no_defs ' unknown elliptical parameter name This does not occur when I import the data into postgis manually using ogr2ogr and then run st_transform() on the concrete table. This issue was not present on the following configuration: POSTGIS="2.3.2 r15302" GEOS="3.6.1-CAPI-1.10.1 r0" SFCGAL="1.3.0" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 2.2.0dev, released 2016/99/99" LIBXML="2.9.1" LIBJSON="0.11.99" TOPOLOGY RASTER But appears on the configuration below with the same dataset: POSTGIS="2.4.1 r16012" PGSQL="100" GEOS="3.6.2-CAPI-1.10.2 4d2925d6" SFCGAL="1.3.0" PROJ="Rel. 4.9.2, 08 September 2015" GDAL="GDAL 2.3.0dev, released 2017/99/99" LIBXML="2.9.3" LIBJSON="0.11.99" TOPOLOGY RASTER gdalsrsinfo output ================================================================ gdalsrsinfo -e ESRI::testshp.prj EPSG:2277 PROJ.4 : +proj=lcc +lat_1=31.88333333333333 +lat_2=30.11666666666667 +lat_0=29.66666666666667 +lon_0=-100.3333333333333 ++x_0=699999.9998983998 +y_0=3000000 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=us-ft +no_defs OGC WKT : PROJCS["NAD83 / Texas Central (ftUS)", GEOGCS["NAD83", DATUM["North_American_Datum_1983", SPHEROID["GRS 1980",6378137,298.257222101, AUTHORITY["EPSG","7019"]], TOWGS84[0,0,0,0,0,0,0], AUTHORITY["EPSG","6269"]], PRIMEM["Greenwich",0, AUTHORITY["EPSG","8901"]], UNIT["degree",0.0174532925199433, AUTHORITY["EPSG","9122"]], AUTHORITY["EPSG","4269"]], PROJECTION["Lambert_Conformal_Conic_2SP"], PARAMETER["standard_parallel_1",31.88333333333333], PARAMETER["standard_parallel_2",30.11666666666667], PARAMETER["latitude_of_origin",29.66666666666667], PARAMETER["central_meridian",-100.3333333333333], PARAMETER["false_easting",2296583.333], PARAMETER["false_northing",9842500.000000002], UNIT["US survey foot",0.3048006096012192, AUTHORITY["EPSG","9003"]], AXIS["X",EAST], AXIS["Y",NORTH], AUTHORITY["EPSG","2277"]] -- Sent from: http://postgis.17.x6.nabble.com/PostGIS-User-f3516033.html _______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users
