view backend/doc/schema/postgresql-drop-spatial.sql @ 6229:3fea9701d58d

Fix gauge determination. If we look upstream ( a > b ) we still have to compare the start value of our range against the gauge and not the end value. The start value is always the relevant value as we handle the direction by checking this against A or B of the gauge. Also: I will never compare doubles with == again. I will never compare doubles with == again. I will never compare doubles with == again. I will never compare doubles with == again. I will never compare doubles with == again.
author Andre Heinecke <aheinecke@intevation.de>
date Thu, 06 Jun 2013 18:23:17 +0200
parents 5aa05a7a34b7
children cc53aae06303
line wrap: on
line source
BEGIN;

DROP TABLE river_axes;
DROP SEQUENCE RIVER_AXES_ID_SEQ;

DROP TABLE river_axes_km;
DROP SEQUENCE RIVER_AXES_KM_ID_SEQ;

DROP TABLE cross_section_tracks;
DROP SEQUENCE CROSS_SECTION_TRACKS_ID_SEQ;

DROP TABLE buildings;
DROP SEQUENCE BUILDINGS_ID_SEQ;

DROP TABLE fixpoints;
DROP SEQUENCE FIXPOINTS_ID_SEQ;

DROP TABLE floodplain;
DROP SEQUENCE FLOODPLAIN_ID_SEQ;

DROP TABLE dem;
DROP SEQUENCE DEM_ID_SEQ;

DROP TABLE hws_points;
DROP SEQUENCE HWS_POINTS_ID_SEQ;

DROP TABLE hws_lines;
DROP SEQUENCE HWS_LINES_ID_SEQ;

DROP TABLE floodmaps;
DROP SEQUENCE FLOODMAPS_ID_SEQ;

DROP TABLE hydr_boundaries;
DROP SEQUENCE HYDR_BOUNDARIES_ID_SEQ;

DROP TABLE hydr_boundaries_poly;
DROP SEQUENCE HYDR_BOUNDARIES_POLY_ID_SEQ;

DROP TABLE gauge_location;
DROP SEQUENCE GAUGE_LOCATION_ID_SEQ;

DROP TABLE fed_states;
DROP TABLE hws_kinds;
DROP TABLE sobek_kinds;
DROP TABLE sectie_kinds;
DROP TABLE boundary_kinds;
DROP TABLE axis_kinds;
DROP TABLE building_kinds;

COMMIT;

http://dive4elements.wald.intevation.org