Opened 6 years ago

Closed 6 years ago

#2309 closed defect (fixed)

raster2pgsql tries to process auth, code even with srid specified

Reported by: robe Owned by: Bborie Park
Priority: medium Milestone: PostGIS 2.1.0
Component: raster Version: trunk
Keywords: history Cc:

Description

I have this huge sid file I chopped up into jpegs each with an *.jpg.aux.xml denoting projection info. However in the raster2pgsql call, I explicitly state the srid. So not sure why raster2pgsql has to check the srs and authcode. I assumed it would only do that if an srid is not specified and it has to try to infer the srid.

raster2pgsql -I -e -F -C -Y -s 2249 *.jpg aerials.boston_2011 | psql 

Gives this notice:

INFO: Cound not get auth name and code. The SRS may be custom

This is using raster2pgsql compiled with GDAL 1.10.0

Attachments (1)

boston_94.zip (1.3 MB) - added by robe 6 years ago.

Download all attachments as: .zip

Change History (4)

Changed 6 years ago by robe

Attachment: boston_94.zip added

comment:1 Changed 6 years ago by robe

Minor gripe. I don't think cound has any relevance in this context :)

comment:2 Changed 6 years ago by Bborie Park

After taking a look at the code, the SRID you specify is what is actually applied. In the process on converting the GDAL dataset to raster, the code automatically tries to set the SRID. It is this automatic process that is emitting that INFO message.

After the GDAL dataset has been converted to raster, your specified SRID (2249) is applied to the raster.

So, not ideal as it is a source of confusion. But your data is still valid.

The spelling error is definitely a blocker though ;-)

comment:3 Changed 6 years ago by Bborie Park

Keywords: history added
Resolution: fixed
Status: newclosed

Fixed in r11410

Note: See TracTickets for help on using tickets.