<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR>
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: "Times New Roman","serif"; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2>I think that it would be worth considering the addition of
a layer of common functionality to FDO. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2>In this case, it would mean that where providers have their
own projection implementations they are used. Where they don't, FDO will
use PROJ.4 (or I suppose Mentor for proprietary builds) to do the work for
them. This would allow for more of the typical processing to be done at
source, increasing the efficiency of spatial operations
immensely.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2>I'd actually like to see this concept of generic
functionality that can be overridden by the individual providers extended to
things like grouping, ordering, etc as well.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=804053116-07092007><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Orest
Halustchak<BR><B>Sent:</B> Friday, September 07, 2007 08:39<BR><B>To:</B> FDO
Internals Mail List<BR><B>Subject:</B> RE: [fdo-internals] RFC 11 has been
posted<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hi
Dan,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">We
didn’t want to require providers to start building coordinate system libraries
into their implementations. Currently, all coordinate system projection work is
done outside of FDO. The OS version of MapGuide does its projection work outside
of FDO using Proj4 for example. Simple calculations would be Euclidian geometry
based calculations.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">These
functions are meant to be 2d functions. We could add 3d functions in the future,
e.g. called Length3D. The proposed functions should compute area and length on
the 2d data and ignore any z that is there. 3d calculations would necessarily
need to be more complex: area of a polygon would need to deal with surfaces and
not just polygon boundaries, length would need to account for different xy and z
units, etc.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thanks,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Orest.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'">
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Dan
Stoica<BR><B>Sent:</B> Friday, September 07, 2007 11:10 AM<BR><B>To:</B> FDO
Internals Mail List<BR><B>Subject:</B> RE: [fdo-internals] RFC 11 has been
posted<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hi,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">A
few questions:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: black; FONT-FAMILY: 'Verdana','sans-serif'">“It is the proposal of
this RFC that providers that do not use coordinate system libraries simply
return simple calculations directly against the lat/long data (i.e. using
Euclidian geometry based calculations).”<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: black; FONT-FAMILY: 'Verdana','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">What “simple
calculations” means exactly? It implies returning the length in radians and area
in square radians… </SPAN><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: Wingdings">L</SPAN><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">There are algorithms
around to do such transformations. How about implementing them as common
utilities? Is it too much trouble?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">Or say the user has
a CSYS library like proj4. I believe it would make sense to allow him to use
it.<o:p></o:p></SPAN></P>
<P><SPAN lang=EN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Verdana','sans-serif'">“It
should also be noted that the functions execute 2D calculations only. Therefore,
if an object is defined in space, the functions should not be used to determine
the area or length of such an object. “<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">Do you mean these
functions will not work with 3D data (“</SPAN><SPAN lang=EN
style="COLOR: black; FONT-FAMILY: 'Verdana','sans-serif'">an object is defined
in space”) </SPAN><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">Thanks,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN
style="COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'">Dan.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'">
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <B>On Behalf Of </B>Thomas
Knoell<BR><B>Sent:</B> Thursday, September 06, 2007 5:33 PM<BR><B>To:</B> FDO
Internals Mail List<BR><B>Subject:</B> [fdo-internals] RFC 11 has been
posted<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Hi,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>A new RFC (<A
href="http://trac.osgeo.org/fdo/wiki/FDORfc11">http://trac.osgeo.org/fdo/wiki/FDORfc11</A>)
has been posted. The RFC follows up on RFC 8 by adding geometric functions to
the list of well-known FDO functions. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Please review the RFC. Any comments/suggestions and questions
are welcome. All feedback is expected by the end-of-day <U>September
12<SUP>th</SUP> 2007</U>. If no changes are required it is my intent to motion
that a vote for the acceptance of the RFC be made and subsequently voted on by
the PSC.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal> Thomas<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>