view schema/geo_functions.sql @ 4017:639bdb17c3f2

Fixed offset for fairway box This was broken by changeset: 4080:bf86f9a08733 user: Thomas Junk <thomas.junk@intevation.de> Date: Thu Jul 18 15:04:30 2019 +0200 summary: improve fairwaydiagram printing positioning For the record: I think the current implementation exceptionally flawed. Instead of adding extra offset parameters to the diagram elements the whole building block with all contained elements should be translated in one step, that would be less cluttered and less error prone...
author Sascha Wilde <wilde@intevation.de>
date Fri, 19 Jul 2019 16:59:25 +0200
parents eeeb7bf14217
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, 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;