<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks Steve for all the details. <br>
</p>
<p>I'm not sure why I had SCALETOKEN in the list. Maybe however this
block deserves its own page in the docs?</p>
<p>SCALE is referred to on the <a class="moz-txt-link-freetext" href="http://mapserver.org/mapfile/map.html">http://mapserver.org/mapfile/map.html</a>
page, but only as part of the newer SCALEDENOM keyword. Should it
be added as its own keyword, with a deprecated tag? Also are all
the keywords listed at <a class="moz-txt-link-freetext" href="http://mapserver.org/cgi/controls.html">http://mapserver.org/cgi/controls.html</a>
Mapfile keywords, or are they a separate but similar set?<br>
</p>
I'm happy to take care of creating a ticket for updating the docs,
and fix these where appropriate.<br>
<br>
Regards,<br>
<br>
Seth<br>
<br>
<div class="moz-cite-prefix">On 29/06/2017 13:53, Lime, Steve D
(MNIT) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SN1PR09MB115276A06758062BF0FC3B20DAD20@SN1PR09MB1152.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
<div>Agreed. I guess I can do it... there are a couple of instance
where doc updates probably aren't warranted IMHO (simple,
compfilter). That's up for debate...<br>
<br>
Re:LATLON... More info, that parameter takes a projection
string. It allows you to override the default geographic
projection used by MapServer.<br>
<br>
--Steve<br>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
mapserver-dev <a class="moz-txt-link-rfc2396E" href="mailto:mapserver-dev-bounces@lists.osgeo.org"><mapserver-dev-bounces@lists.osgeo.org></a>
on behalf of Stephen Woodbridge
<a class="moz-txt-link-rfc2396E" href="mailto:woodbri@swoodbridge.com"><woodbri@swoodbridge.com></a><br>
<b>Sent:</b> Wednesday, June 28, 2017 1:02:16 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [mapserver-dev] Mapfile keywords
questions</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hmmm, sounds like there should be two
tickets opened:<br>
<br>
1. one for code changes at <a
href="https://github.com/mapserver/mapserver/issues"
moz-do-not-send="true">
https://github.com/mapserver/mapserver/issues</a><br>
2. one for doc changes at <a
href="https://github.com/mapserver/docs/issues"
moz-do-not-send="true">https://github.com/mapserver/docs/issues</a><br>
<br>
-Steve W<br>
<br>
On 6/28/2017 1:21 PM, Lime, Steve D (MNIT) wrote:<br>
> Hi Seth: Results of my research... Thanks for sharing
yours. I think you've identified a few places where some
cleanup is warranted. --Steve<br>
> <br>
> *RELATIVETO - I don't believe this is in use. Should be
removed.<br>
> <br>
> *COMPFILTER - My take is that COMPFILTER, while part of
the enhancement, is not actually functional in any
meaningful way so it's not worth documenting beyond RFC 113
at this point.<br>
> <br>
> *GRATICULE - more research needed here. I'm not regular
user of graticule/grid functionality, but it has not been
formally deprecated.<br>
> <br>
> *SCALETOKEN - is documented in detail here: <a
href="http://mapserver.org/mapfile/layer.html"
moz-do-not-send="true">
http://mapserver.org/mapfile/layer.html</a>.<br>
> <br>
> *LATLON - this is processed at the map level as a
shortcut to define a second geographic projection
independent of the map->projection. Presumably something
like "LATLON TRUE". It is used in some places in the CGI and
template handling for projection to geographic coordinates.
Probably should examine the need for it as it is not
documented anywhere...<br>
> <br>
> *JAVASCRIPT - I don't believe the token is needed. I
imagine it was a holdover when the thought was that block of
javascript could defined within a mapfile. Instead
referencing an external file was pursued.<br>
> <br>
> *SCALE - This is valid within the map object and is a
parameter for CGI/FCGI and documented here:
<a href="http://mapserver.org/mapfile/map.html"
moz-do-not-send="true">http://mapserver.org/mapfile/map.html</a>.
The idea is/was to set an explicit scale, center point and
size and then let MapServer compute a matching extent rather
than the other way around.<br>
> <br>
> *INDEX - I don't believe this is in use. Should be
removed.<br>
> <br>
> *SIMPLE - This is a valid TYPE value within a SYMBOL
object. It's actually the default value (e.g. a pixel) and
is never set explicitly - hence the lack of documentation.<br>
> <br>
> *TITLE - still a valid property for a class but
deprecated. Should be considered for removal.<br>
> <br>
> *VALUES - Part of the SCALETOKEN implementation and is
covered there.<br>
> <br>
> *COLORRANGE and DATARANGE - We've always considered
that functionality experimental and ripe for refactoring and
haven’t wanted to encourage their use. Lame, but that's my
story... ;-)<br>
> <br>
> *BANDSITEM - I don't believe this is in use. Should be
removed. The bandsitem and bandsitemindex still exist as
part of the layer object but are unused...<br>
> <br>
> *OVERLAYSYMBOL - It's a deprecated CLASS-level keyword
from the pre-STYLE days. It sets the SYMBOL property of the
second style. It's there for backwards compatibility only.<br>
> <br>
> *EQUALS - token is valid within the context of
MapServer expression parsing. Represents geometry (GEOS)
equality...<br>
> <br>
> *MULTIPLE, SINGLE - I don't see why we need these
keywords when we have ONE-TO-ONE and ONE-TO-MANY. We're
lucky MS_ONE_TO_ONE = MS_SINGLE, etc... and that should be
fixed in loadJoin()...<br>
> <br>
> *LINECAP - I concur with the missing triangle option.<br>
> <br>
> -----Original Message-----<br>
> From: mapserver-dev [<a
href="mailto:mapserver-dev-bounces@lists.osgeo.org"
moz-do-not-send="true">mailto:mapserver-dev-bounces@lists.osgeo.org</a>]
On Behalf Of Seth G<br>
> Sent: Friday, June 23, 2017 6:33 PM<br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
> Subject: [mapserver-dev] Mapfile keywords questions<br>
> <br>
> Hi list,<br>
> <br>
> I'm trying to get the definitive list of current
Mapfile keywords and<br>
> syntax for a Mapfile parser I'm working on<br>
> (<a href="https://github.com/geographika/mappyfile"
moz-do-not-send="true">https://github.com/geographika/mappyfile</a>).<br>
> <br>
> I've gone through the MapServer docs, and also the
sourcecode and have a<br>
> few keywords that aren't documented and I'm not sure
are still used. If<br>
> anyone has any details on the list below it would be
very useful. I can<br>
> open issues if necessary and update docs.<br>
> <br>
> RELATIVETO - mentioned in<br>
> <a
href="https://github.com/mapserver/mapserver/issues/1547"
moz-do-not-send="true">https://github.com/mapserver/mapserver/issues/1547</a>
(from 2006) and is in<br>
> the maplexer.l file. It is not in the test mapfile
created when the<br>
> issue was resolved<br>
> (<a
href="https://trac.osgeo.org/mapserver/attachment/ticket/1547/test_points.map"
moz-do-not-send="true">https://trac.osgeo.org/mapserver/attachment/ticket/1547/test_points.map</a>).<br>
> So it may never have been used?<br>
> <br>
> COMPFILTER - <a
href="http://www.mapserver.org/development/rfc/ms-rfc-113.html"
moz-do-not-send="true">
http://www.mapserver.org/development/rfc/ms-rfc-113.html</a>
-<br>
> not used? Looks interesting! Should be added to<br>
> <a
href="http://www.mapserver.org/mapfile/composite.html"
moz-do-not-send="true">http://www.mapserver.org/mapfile/composite.html</a>
?<br>
> <br>
> GRATICULE - used to be a LAYER CONNECTION type, but now
deprecated?<br>
> <br>
> SCALETOKEN - should be in <a
href="http://www.mapserver.org/mapfile/layer.html"
moz-do-not-send="true">
http://www.mapserver.org/mapfile/layer.html</a><br>
> Documented in <a
href="http://www.mapserver.org/output/kerneldensity.html"
moz-do-not-send="true">http://www.mapserver.org/output/kerneldensity.html</a><br>
> <br>
> LATLON - in maplexer.l but not sure where this would be
used in a Mapfile.<br>
> <br>
> JAVASCRIPT - it is a token in maplexer.l, but not sure
where this would<br>
> be needed (javascript is in quotes as part of the
GEOTRANSFORM options)<br>
> <br>
> SCALE - again a token, but I can only find it as a
LAYER processing<br>
> option - PROCESSING "SCALE=AUTO"<br>
> <br>
> INDEX - not sure what this keyword is for (and hard to
search for..)<br>
> <br>
> SIMPLE, TITLE, VALUES - all in maplexer.l but not in
docs.<br>
> <br>
> COLORRANGE and DATARANGE - should be added to the STYLE
doc page -<br>
> currently only documented at <a
href="http://mapserver.org/output/kerneldensity.html"
moz-do-not-send="true">
http://mapserver.org/output/kerneldensity.html</a><br>
> <br>
> Some keywords only seem valid as part of Mapscript
rather than a<br>
> Mapfile: BANDSITEM, OVERLAYSYMBOL, EQUALS, MULTIPLE,
SINGLE (I think the<br>
> last 2 are PHP join types only?)<br>
> <br>
> Also some non-quoted values also seem to be missing
from the docs:<br>
> <br>
> LINECAP - <a
href="http://www.mapserver.org/mapfile/style.html?highlight=linecap"
moz-do-not-send="true">
http://www.mapserver.org/mapfile/style.html?highlight=linecap</a><br>
> - should TRIANGLE be a documented option? It is in
maplexer.l and also<br>
> mentioned at<br>
> <a
href="http://www.mapserver.org/mapfile/symbology/construction.html#sym-construction"
moz-do-not-send="true">
http://www.mapserver.org/mapfile/symbology/construction.html#sym-construction</a><br>
> <br>
> Regards,<br>
> <br>
> Seth<br>
> <br>
> <br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus
software.<br>
<a href="https://www.avast.com/antivirus"
moz-do-not-send="true">https://www.avast.com/antivirus</a><br>
<br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a></div>
</span></font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mapserver-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
web: <a class="moz-txt-link-freetext" href="http://geographika.co.uk">http://geographika.co.uk</a>
twitter: @geographika</pre>
</body>
</html>