<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I guess my solution would be to put the trails in a PostGIS table:<br>
    <br>
    Trails:<br>
    id&nbsp;&nbsp;&nbsp; name&nbsp;&nbsp;&nbsp; geometry<br>
    1&nbsp;&nbsp;&nbsp; trail A&nbsp;&nbsp;&nbsp; 234523452345<br>
    2&nbsp;&nbsp;&nbsp; trail B&nbsp;&nbsp;&nbsp; 5879567876454<br>
    <br>
    Use one map file with a FILTER "name='%trail_name%'".&nbsp; Now use
    <a class="moz-txt-link-freetext" href="http://.../mapserv?trail_name=">http://.../mapserv?trail_name=</a>"trail A" to have mapserver do the
    variable substitution in the mapfile.<br>
    <br>
    The bigger problem is generating the GUI layer list with the
    pointers to the mapserver URLs.&nbsp; A script/database generated mapbook
    in GeoMoose, or JavaScript list for use with OpenLayers, etc...<br>
    <pre class="moz-signature" cols="72">Best Regards,
Brent Fraser</pre>
    <br>
    On 4/16/2012 1:41 PM, Bob Basques wrote:
    <blockquote cite="mid:4F8C2FA7020000A800035435@heckle" type="cite">
      <p style="margin-bottom: 0; margin-top: 0"> <font face="Comic
          Sans MS" size="3">Individual trails, one layer per GPS to
          allow user control of visibility.</font> </p>
      <br>
      <p style="margin-bottom: 0; margin-top: 0"> <font face="Comic
          Sans MS" size="3">bobb</font> </p>
      <br>
      <p style="margin-bottom: 0; margin-top: 0"> <br>
        <br>
        &gt;&gt;&gt; Brent Fraser <a class="moz-txt-link-rfc2396E" href="mailto:bfraser@geoanalytic.com">&lt;bfraser@geoanalytic.com&gt;</a> wrote:<br>
      </p>
      <table style="margin-left: 15px; margin-right: 0; margin-bottom:
        0; font-size: 1em; margin-top: 0" bgcolor="#f3f3f3" border="0">
        <tbody>
          <tr>
            <td>
              <div style="border-left: solid 1px #050505; padding-left:
                7px">
                <p style="margin-bottom: 0; margin-top: 0"> Well, in
                  this application I don't care about a feature's
                  real-world attributes (only the&nbsp; geometry and their
                  feature "class"), so I'm able to pack all polygons
                  into one table.&nbsp; I then join the polygon table to the
                  feature class table to get the color, etc.&nbsp;<br>
                  <br>
                  Are you representing each GPS trail as a separate
                  layer?&nbsp; So the user can turn individual trail on/off
                  in a layer control?<br>
                </p>
                <pre class="moz-signature" cols="72"><p cols="72" class="moz-signature" style="white-space: pre; margin-bottom: 0; margin-top: 0">
Best Regards,</p>
          <p style="white-space: pre; margin-bottom: 0; margin-top: 0">
Brent Fraser</p>
</pre>
                <p style="margin-bottom: 0; margin-top: 0"> <br>
                  On 4/16/2012 1:07 PM, Bob Basques wrote: </p>
                <blockquote type="cite"
                  cite="mid:4F8C2790020000A80003541D@heckle">
                  <p style="margin-bottom: 0; margin-top: 0"> <font
                      face="Comic Sans MS" size="3">Hmm, interesting
                      apporach, reminds me of my ealier days with Oracle
                      (before Oracle Spatial, where each feature type
                      needed it's own table structure . . . &nbsp;Have to do
                      some more thinking on this one.</font> </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <br>
                  </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <font
                      face="Comic Sans MS" size="3">I'm trying to render
                      a predefined list of layers (from the user) of a
                      set of GPS trails that are BEGIN &nbsp;and END indexed.</font>
                  </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <br>
                  </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <font
                      face="Comic Sans MS" size="3">bobb</font> </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <br>
                  </p>
                  <p style="margin-bottom: 0; margin-top: 0"> <br>
                    <br>
                    &gt;&gt;&gt; Brent Fraser <a moz-do-not-send="true"
                      class="moz-txt-link-rfc2396E"
                      href="mailto:bfraser@geoanalytic.com">&lt;bfraser@geoanalytic.com&gt;</a>&nbsp;wrote:<br>
                  </p>
                  <table style="margin-left: 15px; margin-right: 0;
                    margin-bottom: 0; font-size: 1em; margin-top: 0"
                    bgcolor="#f3f3f3" border="0">
                    <tbody>
                      <tr>
                        <td>
                          <div style="border-left: solid 1px #050505;
                            padding-left: 7px">
                            <p style="margin-bottom: 0; margin-top: 0">
                              Bob,<br>
                              <br>
                              &nbsp; What kinds of things are you trying to
                              do with layers?&nbsp; Are the layers vectors?&nbsp;
                              Maybe there's a different way...<br>
                              <br>
                              I'm in the midst of an implementation
                              where the vectors are held in PostGIS in
                              three tables (point, line and polygon) and
                              joined to a "feature definition" table (to
                              supply rendering values).&nbsp; I use one map
                              file with three layers&nbsp; (point, line,
                              polygon) and pass a FILTER variable to get
                              my different layers which are then
                              rendered.&nbsp;<br>
                              <br>
                              Here's a snippet from the polygon layer:<br>
                              <br>
                              <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CLASS<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; STYLE # Polygon Fill<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; SYMBOL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [polyfill_symbol]<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; COLOR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [polyfill_fillcolor]<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ANGLE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [polyfill_angle]<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; SIZE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [polyfill_hatchgap]&nbsp; # e.g Hatching gap<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WIDTH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 #
                                [polyfill_hatchthick]&nbsp; # Hatching line
                                thickness (column binding doesn't seem
                                to work)&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;<br>
                                #&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; OPACITY&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 50 #
                                [attribute]&nbsp; # warning: there is no
                                OPACITY for LABEL so don't bother.<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; END<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STYLE # Polygon Outline<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYMBOL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [geom_symbol]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OUTLINECOLOR
                                [geom_outcolor]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SIZE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [geom_width]&nbsp;&nbsp;&nbsp; # for "simple" (?)
                                symbols<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; WIDTH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [geom_width]&nbsp;&nbsp;&nbsp; # for complex symbols<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; END # Style<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; TEXT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ([gid])<br>
                                &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; LABEL<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TRUETYPE<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FONT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [label_font]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANTIALIAS&nbsp;&nbsp;&nbsp; TRUE<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; COLOR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [label_fillcolor]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OUTLINECOLOR
                                [label_outcolor]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BUFFER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; POSITION&nbsp;&nbsp;&nbsp;&nbsp; cc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; #
                                [ul|uc|ur|cl|cc|cr|ll|lc|lr|auto]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PARTIALS&nbsp;&nbsp;&nbsp;&nbsp; TRUE<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SIZE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                [label_height]<br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; END&nbsp; # LABEL<br>
                                <br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; END # clas</tt>s<br>
                              <br>
                              While this method is suitable for
                              rendering, it will be a problem if you
                              want store variables for use in an
                              identify operation (or maybe not; I wonder
                              if a template name can be bound to a
                              database column...)<br>
                            </p>
                            <pre class="moz-signature" cols="72"><p cols="72" class="moz-signature" style="white-space: pre; margin-bottom: 0; margin-top: 0">
                  </p><p cols="72" class="moz-signature" style="white-space: pre; margin-bottom: 0; margin-top: 0">
Best Regards,</p>

              <p style="white-space: pre; margin-bottom: 0; margin-top: 0">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </p><p style="white-space: pre; margin-bottom: 0; margin-top: 0">
Brent Fraser</p>


</pre>
                            <p style="margin-bottom: 0; margin-top: 0">
                              <br>
                              On 4/16/2012 10:22 AM, Bob Basques wrote:
                            </p>
                            <blockquote type="cite"
                              cite="mid:4F8C0113020000A8000353FC@heckle">
                              <p style="margin-bottom: 0; margin-top: 0">
                                <font face="Comic Sans MS" size="3">All,</font>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <br>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <font face="Comic Sans MS" size="3">Did
                                  anything ever develop from this idea?
                                  &nbsp;I need to generate a variable length
                                  list of layers pro grammatically.</font>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <br>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <font face="Comic Sans MS" size="3">I'm
                                  not finding anything from a quick
                                  search of things related to passing a
                                  MAPFILE via the CGI call. &nbsp;I want to
                                  be able to generate a MAPFILE, or
                                  chunks of it, on the fly. &nbsp;A possible
                                  solution (maybe scary security wise)
                                  would be to use a param like "</font><font
                                  face="Courier" size="3">INCLUDE_&lt;someID&gt;=</font><font
                                  face="Comic Sans MS" size="3">", to
                                  pass in MAP fragments to an existing
                                  MAPFILE. &nbsp;I need to essentially add
                                  layers.</font> </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <br>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <font face="Comic Sans MS" size="3">Another
                                  thought I had (Ok, it's a bit odd,
                                  I'll admit . . .) would be to have
                                  MapServer build it's own MAPFILE as a
                                  TEMPLATE output, but I'm not coming up
                                  with a way immediately of passing the
                                  resulting MAPFILE to Mapserver in the
                                  end.</font> </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <br>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <font face="Comic Sans MS" size="3">bobb</font>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                                <br>
                                <br>
                              </p>
                              <p style="margin-bottom: 0; margin-top: 0">
                              </p>
                              <fieldset class="mimeAttachmentHeader"> </fieldset>
                              <br>
                              <pre wrap=""><p wrap="" style="white-space: pre; margin-bottom: 0; margin-top: 0">
          </p><p wrap="" style="white-space: pre; margin-bottom: 0; margin-top: 0">
_______________________________________________</p>

      <p style="white-space: pre; margin-bottom: 0; margin-top: 0">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </p><p style="white-space: pre; margin-bottom: 0; margin-top: 0">
mapserver-users mailing list</p>

  <p style="white-space: pre; margin-bottom: 0; margin-top: 0">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  </p><p style="white-space: pre; margin-bottom: 0; margin-top: 0">
<a moz-do-not-send="true" href="mailto:mapserver-users@lists.osgeo.org" class="moz-txt-link-abbreviated">mapserver-users@lists.osgeo.org</a></p>

<p style="white-space: pre; margin-bottom: 0; margin-top: 0">
&nbsp;&nbsp;&nbsp;&nbsp;
</p><p style="white-space: pre; margin-bottom: 0; margin-top: 0">
<a moz-do-not-send="true" href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" class="moz-txt-link-freetext">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a></p>

</pre>
                            </blockquote>
                          </div>
                        </td>
                      </tr>
                    </tbody>
                  </table>
                </blockquote>
              </div>
            </td>
          </tr>
        </tbody>
      </table>
    </blockquote>
  </body>
</html>