[postgis-devel] [PostGIS] #1782: [raster] rtpg_getSR fails for any spatial reference system not in EPSG.

[PostGIS]

#1782: [raster] rtpg_getSR fails for any spatial reference system not in EPSG.
-----------------------+----------------------------------------------------
  Reporter:  kempisty  |       Owner:  dustymugs    
      Type:  defect    |      Status:  reopened     
  Priority:  medium    |   Milestone:  PostGIS 2.0.1
 Component:  raster    |     Version:  2.0.x        
Resolution:            |    Keywords:               
-----------------------+----------------------------------------------------
Changes (by kempisty):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 r9647 takes care of the segfault.  There is still the matter of handling
 the query into spatial_ref_sys.  If auth_name isn't 'EPSG', the logic
 still returns an error without trying proj4text or srid.

 At the moment, with the default contents of spatial_ref_sys, that's only a
 problem for srid=900913, auth_name="spatialreferencing.org".  I suppose
 those people can use srid=3857 instead.  In my case, for a custom srs with
 no auth_name, I will still get the error.  rtpg_getSR will never try my
 proj4text or srtext strings in GDAL.

 It looks like GDAL's SetFromUserInput() will take EPSG: as well as EPSGA:
 and ESRI: and several other versions of shorthand.  I'm not sure how many
 other people add their own entries into spatial_ref_sys.  If they do, and
 if the auth_name is ESRI, or EPSGA, or null, they'll run into this.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1782#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.