<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2722" name=GENERATOR>
<STYLE> font-face {
FONT-FAMILY: Tahoma
}
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=034531709-05102006><FONT face=Arial
color=#0000ff size=2>Robert,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=034531709-05102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=034531709-05102006><FONT face=Arial
color=#0000ff size=2>From what I can see, the documentation that comes with Map
2007 is somewhat lacking when it comes to detailing how data, including the
geometry, can be put into SQL Server. E.g. do we need a blank database on the
SQL instance? Can you point me to any documentation?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=034531709-05102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=034531709-05102006><FONT face=Arial
color=#0000ff size=2>Keith</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> Robert Fortin
[mailto:robert.fortin@autodesk.com] <BR><B>Sent:</B> 04 October 2006
18:03<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2>Jim,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><SPAN
class=537435416-04102006><FONT face=Arial color=#0000ff size=2>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2>The AGF is a legacy name valid until FDO 3.1 that is
showing in the doc. Although it still show up in the doc, it
has been replaced by FGF (FDO Geometry Format) for API function and
class names in FDO 3.2 e.g. GisAgfGeometryFactory became
FdoFgfGeometryFactory</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV>Look into the FDG_FDODevGuide.pdf under "The Geometry API". It describes
the binary format.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2>There is an API to simplifies reading/wrting binary
AGF.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2>There is also a text version AGF text (search AGF
Text).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=537435416-04102006><FONT face=Arial
color=#0000ff size=2>RF</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> Lockyer James
[mailto:James.Lockyer@bradford.nhs.uk] <BR><B>Sent:</B> Wednesday, October 04,
2006 11:37 AM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText92036 dir=ltr>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2>Hi
Robert</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2>Thanks for that, I read
some of the documents but none stated that the FDO SQL only worked if you had
Map 3D - it was something I guessed by accident when I was trying to reverse
engineer the process of connection. So effective FDO to me would mean one
that didn't rely on me purchasing a third software package.
</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2>What information is there
about FGF binary format? I've managed to create an SQL file which sorts out the
meta data on the SQL file. I'd stopped when I established that the
expected datasource was in fact binary rather than GML (which was my firt
thought as to how data could be stored).</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2>Jim</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN lang=en-gb><FONT face=Arial
size=2></FONT></SPAN> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Robert Fortin
[mailto:robert.fortin@autodesk.com]<BR><B>Sent:</B> Wed 04/10/2006
15:59<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV dir=ltr>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>Jim,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>I guess as for the documentation, it is an oversight
and should be fixed. Some of this documentation exist from the FDO side
(FDG_FDODevGuide.pdf and FET_TheEssentialFDO.pdf available on the open source
side) But I agree that even there there is not enough and
could be further refine.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>Mapguide SP1 will introduce performance enhancement for
reading data. I hope that it will cover some of your concern with your
Odbc case.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>"And is there any intention of creating an effective
FDO for SQL." </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>I'm not sure what you would consider an effective
provider for SQL server. SQL Server doesn't have native support for
geometry. Therefore, we need some mechanism to deal with it. Like I
said, you can still read data out of SQL server but that has limited use if you
can't get your geometry out of it. The geometry is currently stored in FGF
binary format and the database requires FDO metadata in order to work with
geometry. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>We look at supporting geometry stored in OGC WKT format
to give some flexibility for non-FDO enable database but it is not currently
implemented at this time.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=592134114-04102006>RF</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Lockyer James
[mailto:James.Lockyer@bradford.nhs.uk] <BR><B>Sent:</B> Wednesday, October 04,
2006 10:09 AM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText86679 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Cheers,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Can I ask why it has taken three months to
point that out or why this is not mentioned in the any of the help files/
published material on the internet or for that matter why the UK resellers are
unaware of this fact. And is there any intention of creating an effective
FDO for SQL.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT><FONT face=Arial
size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2><SPAN class=584443213-04102006><FONT
face=Arial color=#0000ff size=2>In case you have X,Y,Z coordinates stored in
different columns, the ODBC provider should be used against SQL Server data.
-<FONT color=#000000> has this been speeded up in the latest release? As
when I tried this it took over 40 minutes to map out four
points.</FONT></FONT></SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2><SPAN
class=584443213-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><SPAN
class=584443213-04102006>Has anyone thought about using GML as a storage
mechanism?</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><SPAN
class=584443213-04102006></SPAN></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><SPAN
class=584443213-04102006>Jim</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV id=idSignature30214 dir=ltr>
<DIV>
<DIV><STRONG><FONT face=Arial>James Lockyer</FONT></STRONG></DIV>
<DIV><FONT face=Arial size=1>GIS Specialist</FONT></DIV>
<DIV><FONT face=Arial size=1>IM&T</FONT></DIV>
<DIV><FONT face=Arial size=1>Bradford and Airedale Teaching PCT</FONT></DIV>
<DIV><SPAN lang=en-gb><FONT face=Arial color=#000000 size=1>New Mill, Victoria
Road, Saltaire, Shipley, West Yorkshire, BD18 3LD</FONT></SPAN></DIV>
<DIV><SPAN lang=en-gb><FONT face=Arial size=1></FONT></SPAN> </DIV>
<DIV><SPAN lang=en-gb><FONT face=Arial size=2>Tel: 01274
366031</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><SPAN lang=en-gb><FONT face=Arial><FONT size=1>This email is intended for
the use of the addressee </FONT><U><FONT size=1>only</FONT></U><FONT size=1> and
may contain confidential information, copyright material or views/opinions that
do not necessarily reflect those of the organisation. If you receive this email
by mistake please advise the sender immediately. All should be aware that this
email may be subject to public disclosure under the Freedom of Information Act
2000 and that emails are monitored periodically.</FONT></FONT></SPAN></DIV><PRE></PRE></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Robert Fortin
[mailto:robert.fortin@autodesk.com]<BR><B>Sent:</B> Wed 04/10/2006
14:39<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV dir=ltr>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2>The SQL Server provider is intented to work with datastore
created with Map 3D 2007 inside SQL Server 2000 and 2005.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2>It has it's own geometry storage and spatial indexing
mechanism. Although it could reverse engineer existing database, this
would be done for non-spatial data only as it has no mean to identify geometry
property in the database.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2>In case you have X,Y,Z coordinates stored in different
columns, the ODBC provider should be used against SQL Server
data.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2>Just wanted to make sure the provider was not being used
for what it was not design for.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=584443213-04102006><FONT face=Arial
color=#0000ff size=2>RF</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> Lockyer James
[mailto:James.Lockyer@bradford.nhs.uk] <BR><B>Sent:</B> Wednesday, October 04,
2006 2:59 AM<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText99100 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Supported yes - does it
work... now that's the question.</FONT></DIV>
<DIV dir=ltr><BR> </DIV>
<DIV dir=ltr>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr><FONT face=Tahoma size=2><B>From:</B> Gord McKenzie
[mailto:gord.mckenzie@canam.com]<BR><B>Sent:</B> Tue 03/10/2006
22:04<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> RE:
[mapguide-users] SQL Server 2005<BR></FONT><BR></DIV></DIV>
<DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Warren
Medernach [mailto:warren.medernach@imaginit.ca] <BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, October 03, 2006 1:33
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
users@mapguide.osgeo.org<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [mapguide-users] SQL Server
2005</SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hello
Gord,</SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I was informed by the
ADN that the FDO provider supports: SQL Server 2000 (SP4) and SQL Server
2005.</SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Warren
Medernach</SPAN></FONT></P></DIV></DIV></DIV></DIV><BR><BR><FONT
style="BACKGROUND-COLOR: #ffffff">
<P align=center><FONT style="BACKGROUND-COLOR: #ffffff">This message has been
scanned for viruses by </FONT><A
href="http://bluepages.wsatkins.co.uk/?4318150"><FONT
style="BACKGROUND-COLOR: #ffffff"
color=#000000>MailControl</FONT></A></P></FONT><br><br>
<P align=center><FONT style="BACKGROUND-COLOR: #ffffff" color=#ff0000><STRONG><FONT color=#000000>This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding</FONT>.</STRONG></FONT><A href="http://www.blackspider.com/"><FONT style="BACKGROUND-COLOR: #ffffff" color=#000000></FONT></A></P>
</body></HTML>