<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \, serif";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Comic Sans MS";
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext">Bob,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext">This is probably further than you want to go, but I would be inclined to build a folder watcher or listener script that watches the contents of a folder and adds
any new content automatically to a Database for retrieving. The process of adding the data to the database should also provide a semblance of validation as well. Then the results are easy to query for, even in a double pass scenario, IE get ID in the view
desired, then iterate through for those links attached to that ID, all handled via a SQL statement. Easy to add to for may different files too.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext">Bobb<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS";color:windowtext"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> geomoose-users-bounces@lists.osgeo.org [mailto:geomoose-users-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Bistrais, Bob<br>
<b>Sent:</b> Tuesday, April 09, 2013 3:30 PM<br>
<b>To:</b> Brent Fraser<br>
<b>Cc:</b> geomoose-users@lists.osgeo.org<br>
<b>Subject:</b> Re: [Geomoose-users] Linking search results to templates<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Yes, I’m thinking of looking parsing the file names, concerned about search times, but need to give it a try. The photo names are fairly consistent but not 100% so.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Brent Fraser [<a href="mailto:bfraser@geoanalytic.com">mailto:bfraser@geoanalytic.com</a>]
<br>
<b>Sent:</b> Tuesday, April 09, 2013 4:25 PM<br>
<b>To:</b> Bistrais, Bob<br>
<b>Cc:</b> <a href="mailto:geomoose-users@lists.osgeo.org">geomoose-users@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [Geomoose-users] Linking search results to templates<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I'm always paranoid when it comes to data, so I prefer to have a step where I "load" the data and confirm the result. But as long as the data is consistent (when does that happen?), maybe you could just modify
the PHP to:<br>
1. get the contents of a directory where the photos are stored<br>
2. parse the file names<br>
3. and generate the output HTML.<br>
<br>
Basically doing a "join" and template process in the PHP. Might be a performance issue if there are thousands of photos in the dir....<br>
<br>
<o:p></o:p></p>
<pre>Best Regards,<o:p></o:p></pre>
<pre>Brent Fraser<o:p></o:p></pre>
<p class="MsoNormal">On 4/9/2013 2:11 PM, Bistrais, Bob wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:#1F497D">Thanks Brent,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Looks like most sites have 4 photos, but not all. I’m finding cases of fewer or more than 4 photos. Problem is, this could change as the customer adds more sites, or more photos to existing sites. So I’d have
to modify a table every time the customer sends data updates. I was hoping maybe I could do this through MapServer templating?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Brent Fraser [<a href="mailto:bfraser@geoanalytic.com">mailto:bfraser@geoanalytic.com</a>]
<br>
<b>Sent:</b> Tuesday, April 09, 2013 3:57 PM<br>
<b>To:</b> Bistrais, Bob<br>
<b>Cc:</b> <a href="mailto:geomoose-users@lists.osgeo.org">geomoose-users@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [Geomoose-users] Linking search results to templates</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Bob,<br>
<br>
<br>
Depends on the data. Are there usually 4 photos? If so, just create 4 columns in the Site table and populate them with the path to photos. If it is more variable (sometimes 1, sometimes 5 photos), create a table to relate Sites to Photos:<br>
<br>
SitePhotos<br>
-----------<br>
siteID: photoPath:<br>
1234 1234Front.jpg<br>
1234 1234Rear.jpg<br>
<br>
and do a table join within Mapserver's Map file (in the LAYER's DATA statement) to relate sites to tables.<br>
<br>
<o:p></o:p></p>
<pre>Best Regards,<o:p></o:p></pre>
<pre>Brent Fraser<o:p></o:p></pre>
<p class="MsoNormal">On 4/9/2013 1:14 PM, Bistrais, Bob wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">I’m working on an application which depicts various sites (several thousand of them). The customer has photos of the different sites, each site usually has 4 pictures, from different angles. The spatial data does not have an attribute
linking the photos to a particular record. But each photo has the site ID as part of its name. Example- Site 1234 has photos with names like “1234Front.jpg”, “1234Rear.jpg”, etc.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">What I’d like to do is display search/query results so that the corresponding photos (actually, links to them) will appear in an Identify or query result tab. I can form the URL’s based on the site’s ID number, but don’t know how to insert
these into the identify/query templates. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Has anyone done something similar to this, and would have any advice on how to do this?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman , serif","serif""><br>
<br>
<br>
</span><o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Geomoose-users mailing list<o:p></o:p></pre>
<pre><a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><o:p></o:p></pre>
<pre><a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman , serif","serif""> </span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>