Opened 10 years ago

Last modified 9 months ago

#2103 new enhancement

Ability to load topogeoms using shp2pgsql

Reported by: robe Owned by: strk
Priority: medium Milestone: PostGIS Fund Me
Component: topology Version: master
Keywords: gsoc, usability Cc:

Description

In writing chapters of the book, one exercise is to load the data with shp2pgsql and then a second step to load into a specific topology.

Aside from speed issues, I can't see why we can't just go straight to a topogeom column much like we do with geography is -G is chosen.

This would require another switch for topology name and name of topology. The only tricky part is that for the toTopogeom calls we need the generated layer id, which would require a connection to the database to get unless we have a lookup function of some sort that can lookup the layerid based on topo column table/name.

Change History (11)

comment:1 by strk, 10 years ago

I've been actually thinking that AddTopoGeometryColumn could be modified (or overloaded) to also accept an existing column for the purpose of registering it when missing (think CopyTopology). The same function could maybe return an already-registered layer_id too. I like the idea of reducing signatures …

comment:2 by robe, 10 years ago

This would make a good google summer of code project. Added to page — http://trac.osgeo.org/postgis/wiki/GoogleSummerCode2012

comment:4 by robe, 10 years ago

Keywords: gsoc added

comment:5 by robe, 10 years ago

Milestone: PostGIS 2.1.0PostGIS 2.2.0

comment:6 by strk, 8 years ago

Milestone: PostGIS 2.2.0PostGIS Future

comment:7 by robe, 5 years ago

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

comment:9 by strk, 12 months ago

shp2pgsql switches -t and -T are already taken, ideas on what switch to use for this ?

comment:10 by strk, 10 months ago

Keywords: usability added
Note: See TracTickets for help on using tickets.