view schema/geonames.sql @ 3705:7006b92c0334

Handle updates (vs. historized and new versions) separately. We need this distinction as updated data currently can not be reviewed. More precisely: it can not be declined after review, as the old data is updated in place. The current exclusion from the review is a workaround and not meant to be the final solution. Note that there are additional minor problems, like the fact that the updated data is not counted as changed data for the import.
author Sascha Wilde <wilde@intevation.de>
date Wed, 19 Jun 2019 17:00:08 +0200
parents 2304778c4432
children
line wrap: on
line source

-- This is Free Software under GNU Affero General Public License v >= 3.0
-- without warranty, see README.md and license for details.

-- SPDX-License-Identifier: AGPL-3.0-or-later
-- License-Filename: LICENSES/AGPL-3.0.txt

-- Copyright (C) 2018 by via donau
--   – Österreichische Wasserstraßen-Gesellschaft mbH
-- Software engineering by Intevation GmbH

-- Author(s):
--  * Sascha Wilde <wilde@intevation.de>

-- Tables for data from geonames database
-- https://download.geonames.org/
-- used for searching cities and villages...

CREATE TABLE waterway.geonames (
       geonameid int PRIMARY KEY,
       name varchar(200) NOT NULL,
       asciiname varchar(200),
       alternatenames varchar(10000),
       location geography(POINT, 4326) NOT NULL,
       feature_class char(1),
       feature_code varchar(10),
       country_code char(2),
       cc2 varchar(200),
       admin1_code varchar(20),
       admin2_code varchar(80),
       admin3_code varchar(20),
       admin4_code varchar(20),
       population int,
       elevation int,
       dem int,
       timezone varchar(40),
       modification_date timestamp
);