<HTML dir=ltr><HEAD><TITLE>[postgis-users] Confusion about projections and Spatial Data</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText69255 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Very good questions. I may be wrong on some of my assumptions, but this is my understanding</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>1) Everyone ships in lat long format because it covers the widest area of space and can be easily transformed into other SRIDs or out of all SRIDs. Its not even entirely true that everyone does. Most state municipalities for example often ship their data in a coordinate system specific to thier area or state.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>2) As far as I know most functions will work with lat long except distance gives you funky results because it is measuring around circles for lat long.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>3) Why do databases have this whole cartesian thingy and not work straight with lat long? Because screens are flat, printed maps are flat and when you look at isolated areas you can make them look flat and not skew measurements and layout. So I guess its a hack to make your problem simpler. If you look at the upcoming SQL Server Katmai which is supposed to have Geography - it will challenge that and try to deal with geodetic data as a "first class" reference system. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>4) Not everyone stores their data projected, but often will transform on the fly if they do not project. I do when I know I am only dealing with a very isolated region like a single state or city municipality.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>5) Its not true that tools like ArcView and MapInfo want lat long. Actually MapInfo is pretty sophisticated I think when it comes to projections so its almost transparent to the user. I'm not quite sure how it does it, but encoded in each tab file is the projection info and you can lay on a bunch of layers in different projections and it will magically pick the most suitable one and reproject all the layers to that. My knowledge of ArcView is less, but I think ArcView tends to be more picky about projections so requires more knowledge on the user's side to know how to deal with multiple layers in different projections. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Hope that helps,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Regina</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> postgis-users-bounces@postgis.refractions.net on behalf of Rick Zoolker<BR><B>Sent:</B> Fri 8/10/2007 1:34 PM<BR><B>To:</B> postgis-users@postgis.refractions.net<BR><B>Subject:</B> [postgis-users] Confusion about projections and Spatial Data<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>OK, I feel like I've got a fundamental block about how spatial data is<BR>actually used in the real world and how spatially aware databases<BR>actually make use of that data. This is probably quite obvious for<BR>everyone so please bear with me.<BR><BR>I've been playing with a bunch of spatial databases (Oracle, Postgis,<BR>DB2) and from what I can tell, all tend to roughly follow the OGC SFA<BR>spec (Oracle using different terminology). Now it also seems that the<BR>SFA spec deals EXCLUSIVELY with Cartesian coordinates. Now here's my<BR>first confusion. If they only deal with Cartesian coordinates, why do<BR>they allow you to specify SRIDs that are lat/long based. Will any of<BR>the SFA functions work with lat/long (other than ST_Transform(), which<BR>is actually a SQL/MM and not even included in SFA)??<BR>My next area of confusion is that I've looked at a bunch of data from<BR>people such as Navteq, teleatlas, and a bunch of individual companies<BR>databases, and it seems that every single one ships and stores their<BR>data in lat/long. So what the heck? If the tools can't deal with<BR>lat/long, why does everyone ship and store their data in lat/long?<BR>Does everyone project this data before actually loading it into the<BR>db? Help!?<BR><BR>Now, it appears that Oracle in particular can do some functions with<BR>lat/long directly (the distance calculation comes to mind), and I know<BR>Postgis has some specialized distance functions for geodetic<BR>coordinates, but I'm not sure if that extends to the whole function<BR>set (i.e. can I do an Intersection of two polygons specified in<BR>lat/long coordinates??). Why doesn't the OGC SFA spec and libraries<BR>support all the functions with geodetic coordinates directly rather<BR>than require projected coordinates?<BR><BR>Finally, how do the analysis and visualization tools that people put<BR>on top of these databases deal with these questions? (e.g. MapInfo,<BR>ArcView, etc.) They seem to want lat/long data as well, but if you<BR>stored project coordinates in the database isn't there a problem??<BR><BR>HELP!<BR><BR> -Rick<BR>_______________________________________________<BR>postgis-users mailing list<BR>postgis-users@postgis.refractions.net<BR><A href="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR></FONT></P></DIV></BODY></HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>