From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tim Hart <tjhart(at)mac(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [SQL] line datatype |
Date: | 2002-07-16 06:10:29 |
Message-ID: | 3D33B8D5.D8A2E1CE@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-07-16 06:11:23 | Re: fmtId() and pg_dump |
Previous Message | Tom Lane | 2002-07-16 06:05:50 | Re: Unused system table columns |
From | Date | Subject | |
---|---|---|---|
Next Message | Marcus Claesson | 2002-07-16 08:09:14 | How do I concatenate row-wise instead of column-wise? |
Previous Message | Bruce Momjian | 2002-07-16 03:33:48 | Re: line datatype |