No it shouldn't. So this query works okay for you?
SELECT ST_AsText(ST_Transform(ST_Transform(ST_SetSRID(ST_Point(-97.353287, 31.105862), 4326), 2277),4326)); Can you also note what ST_SRID returns for the physical table you loaded. I presume from your foreign table structure the foreign table srid is 2277. As I recall from using ogr2ogr, if it couldn't match up an srid with entry in table and you didn't explicitly specify one it would add a new one to the spatial_ref_sys to match the proj4text it computed. I want to rule out that is happening here. If it did that then your SRID for your loaded table will not be 2277, but an equivalent one probably using the GRS80 and towgs syntax. -----Original Message----- From: postgis-users [mailto:[email protected]] On Behalf Of Andrew Joseph Sent: Friday, November 10, 2017 2:27 PM To: [email protected] Subject: Re: [postgis-users] [XX000] ERROR: AddToPROJ4SRSCache: could not parse proj4 string I should also note that I upgraded from postgres 9.6.2 to 10.1 -though I don't suspect that would make a difference with this issue. -- 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
