[postgis-devel] [PostGIS] #1505: Deal with database dumps containing geometries with SRID > MAX_SRID

[PostGIS]

#1505: Deal with database dumps containing geometries with SRID > MAX_SRID
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  high     |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by strk):

 We just need to define ranges, CRC or simple modulo would then work at
 fitting in.
 Does anyone feel like drafting such set ?

 One range would likely be "system range", which is where we promise to put
 standard entries.
 Another range would be "user range" where we suggest users to put theirs.
 Another would be "reserved" which is those you can't put in
 spatial_ref_sys but possibly have special internal meaning.
 Finally we'd be adding a "lost+found" range, is that your proposal Paul ?
 Such "lost+found" range would be the range into which rows with
 SRID>MAX_SRID would be put, in a deterministic way. The user should then
 be warned about the need of taking his geometries out of that range and
 into the valid "user range" instead. Correct ?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1505#comment:4>
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.