Changes between Version 10 and Version 11 of GoogleSummerCode2022

Timestamp:

02/19/22 14:27:04 (3 years ago)

Author:

robe

Comment:

--

GoogleSummerCode2022

@@ -38 +38 @@
 shp2pgsql will have new switches for loading into a topology. For topology elements, whether it loads into faces, edges, nodes will be dictated by the type of the data in the ESRI shapefile and will ignore the attribute data if any.
 
-For topogeoms, the user would need to specify the table to create, topology, and column, with default column name being topo if the user does not specify. This will behave more or less the same as geography/geometry loading.  For the first pass, we will assume this will just use basic topo element types (areal, lineal, punctal) and will not use subelements.
+For topogeoms, the user would need to specify the table to create, topology, and column, with default column name being ''topo'' if the user does not specify. This will behave more or less the same as geography/geometry loading.  For the first pass, we will assume this will just use basic topo element types (areal, lineal, punctal) and will not use subelements.
 
 pgsql2shp will be used to export topogeoms and will use the topo::geometry casting to do so. Since topology tables faces, edges, and nodes are already tables, there is no need to support exporting topology.