<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [postgis-users] Dateline and polar regions and any other spatialgotchas</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I have used postgis in a project for polar regions, when I received a few interesting projections, it was as simple as adding them to postgis by finding the corresponding proj4 definition and adding it to the spatial_ref_sys table.<BR>
<BR>
I used python and GDAL to get the proj4 definition for the image bbox I was registering, and then just added it to PostGIS.<BR>
<BR>
Norman<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-users-bounces@postgis.refractions.net on behalf of Gregory Williamson<BR>
Sent: Wed 6/27/2007 12:39 AM<BR>
To: postgis-users@postgis.refractions.net<BR>
Subject: [postgis-users] Dateline and polar regions and any other spatialgotchas<BR>
<BR>
Most of the work our company (GlobeXplorer) has done with postGIS has been in US markets where such things as dateline math isn't much of an issue. We use SRID 4326 to store the data in.<BR>
<BR>
We (DigitalGlobe) are evaluating PostgreSQL and Oracle for a largish project using data all over the planet, and before I make any bald assertions I thought I'd ask and see if there are:<BR>
<BR>
a) know issues with datelines or other gnarly parts of the world ?<BR>
<BR>
b) workarounds ?<BR>
<BR>
Thanks for any info ... tried trolling the website and didn't find any caveats, but the mail list archive isn't really searchable so I am hoping this is not a FAQ (if it is, point me at it!).<BR>
<BR>
TIA,<BR>
<BR>
Greg Williamson<BR>
Senior DBA<BR>
GlobeXplorer, a DigitalGlobe company<BR>
<BR>
<BR>
Greg Williamson<BR>
DBA<BR>
GlobeXplorer LLC, a DigitalGlobe company<BR>
<BR>
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and must be protected in accordance with those provisions. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.<BR>
<BR>
(My corporate masters made me say this.)<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>