[postgis-devel] [PostGIS] #1071: Ability to load tiger data into PostGIS topology structure

[PostGIS]

#1071: Ability to load tiger data into PostGIS topology structure
-------------------------+--------------------------------------------------
 Reporter:  robe         |       Owner:  robe          
     Type:  enhancement  |      Status:  new           
 Priority:  medium       |   Milestone:  PostGIS Future
Component:  topology     |     Version:  trunk         
 Keywords:               |  
-------------------------+--------------------------------------------------
 We aren't sure if we'll get to this before PostGIS 2.0.0 is released,
 but the plan is to load tiger data edges, faces, and nodes (which Leo
 noted each tlid in edges does have a corresponding start and end node id)
 into the PostGIS topology structure.  This will be both directly useful to
 many people building topogeometries against tiger data as well as a
 learning tool since tiger data is freely available.

 strk may not like this, but we plan to skirt all his loading functions and
 go straight to the tables.  The main reason is that a lot of people (e.g.
 local communities building boundaries and so forth where topology is very
 important use the tiger edges and the tlids (tiger's edge ids). The tiger
 tlids therefore have significance in meaning to be able to reconcile back
 easily with tiger data.  So we need to maintain these to make it most
 useful.

 Any rate that is the plan. This kind of borders between tiger geocoder and
 topology since the loader we create will probably piggy back at least a
 little bit on the tiger geocoder loader.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1071>
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.