[GRASS-user] Finding why postgres database cannot be opened

Rich Shepard rshepard at appl-ecosys.com
Wed Nov 7 13:54:09 PST 2018


On Wed, 7 Nov 2018, Markus Metz wrote:

> I am afraid that manually adding a cat column and populating it with
> sequential numbers will not work: how do you assure that the cat numbers
> and corresponding attribute values indeed correspond to the cat values of
> the vector features? Chances are high that vector features get linked to
> wrong attributes.

Markus M,

   Grass told me the stations table has no categories, which it does not
because the map's attribute table was derived from the pre-existing postgres
database table and the geometry created by the easting/northing pairs in
that table.

   The other maps and tables were created from agency-sourced GIS
repositories and grass created cat columns for them, so it's only the
stations table needing that column to be added.

> db.select sql="select * from stations limit 3"
site_nbr|site_name|lon|lat|easting|northing|start_date|end_date|howmany|bin_col|cat
10332|Willamette R. at SP&S RR Bridge (Portland)|-122.7475|45.577944|||1979-11-06|2003-06-19|25|231:00:231|
10917|Pudding R. at Hwy 99E (Aurora)|-122.748972|45.233806|||1979-11-06|2008-03-26|22|231:00:231|
10376|McKenzie R. at Coburg Road|-123.046194|44.112722|||1980-05-07|2011-01-04|40|231:173:00|

   No cat values there now. But, updating the table and setting a distinct cat
number for each site_nbr will fill that column.

Thanks,

Rich


More information about the grass-user mailing list