Mercurial > gemma
view schema/geo_functions.sql @ 3301:6514b943654e
Re-enable checking of gauge availability
This partly reverts rev. 1cb6676d1510, which removed this code in
favour of handling database errors later. The thinko in this was
that possibly many NtS messages for the same gauge would lead to
many errors for a single reason and the same amount of unnecessary
database round-trips. Checking whether the current user is allowed
to import data for a gauge now also handles sys_admin correctly
and the import stops with status unchanged if no such gauge is
available.
author | Tom Gottfried <tom@intevation.de> |
---|---|
date | Thu, 16 May 2019 17:22:33 +0200 |
parents | 69292eb68984 |
children | 033366f94abf |
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, 2019 by via donau -- – Österreichische Wasserstraßen-Gesellschaft mbH -- Software engineering by Intevation GmbH -- Author(s): -- * Sascha L. Teichmann <sascha.teichmann@intevation.de> -- * Tom Gottfried <tom@intevation.de> CREATE OR REPLACE FUNCTION best_utm(g geography) RETURNS integer AS $$ DECLARE center geometry; BEGIN -- Centroid should be calculated on geography to get accurate results -- from lon/lat coordinates, but the respective PostGIS function returns -- POINT(-NaN NaN) for some invalid polygons, while the calculation on -- geometry seems to give reasonable approximations in this context. SELECT ST_Centroid(CAST(g AS geometry)) INTO center; RETURN CASE WHEN ST_Y(center) > 0 THEN 32600 ELSE 32700 END + floor((ST_X(center)+180)/6)::int + 1; END; $$ LANGUAGE plpgsql IMMUTABLE;