From: Thomas Lockhart <lockhart@fourpalms.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tim Hart <tjhart@mac.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [SQL] line datatype
Date: Mon, 15 Jul 2002 23:10:29 -0700
Message-ID: <3D33B8D5.D8A2E1CE@fourpalms.org> (raw)
References: <200207160333.g6G3Xnc22777@candle.pha.pa.us>
> It would be nice to get the line type working 100%. Thomas says the
> problem is input/output format. I don't completely understand.
The issue is in choosing an external format for LINE which does not lose
precision during dump/reload. Internally, LINE is described by a formula
which is likely subject to problems with limited precision for some line
orientations.
Does anyone have a suggestion (perhaps drawn from another GIS package)
for representing lines? We already have this implemented internally, and
the algorithms are used to support other data types; the only unresolved
issue is in how to input the values.
- Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: lockhart@fourpalms.org, pgman@candle.pha.pa.us, tjhart@mac.com, pgsql-hackers@postgresql.org
Subject: Re: [SQL] line datatype
In-Reply-To: <3D33B8D5.D8A2E1CE@fourpalms.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox