<div dir="ltr"><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Got it, thanks for the help!</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">After much flailing, it turned out to be an illegal field name buried deep in the file (137 fields, and one name included a period, ugh). This meant that the GML being returned was malformed, and GeoMoose couldn't even parse it.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Once past that error, the hint about case sensitivity became relevant, because as soon as the GML was parsable, it would not populate the template until the case of the field names matched.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">thanks again!<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Dec 10, 2018 at 12:35 PM Jim Klassen <<a href="mailto:klassen.js@gmail.com">klassen.js@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>GetFeatureInfo doesn't take any query parameters that are case
sensitive, but it's response contains field names. GeoMoose cares
about the case of those field names matching the template (in the
mapbook) and any other place they are used. Different data
sources to MapServer have different defaults for how they handle
the case of field names.<br>
</p>
<p>For example, in the mapbook (or GeoMoose remote template):<br>
</p>
<p>{{ properties.pin }} is not the same as {{ properties.PIN }} and
to work it must match the field name as it is returned by
MapServer. If it doesn't, the field will be shown as "???".</p>
<p><br>
</p>
<div class="gmail-m_-3831341768387645068moz-cite-prefix">On 12/10/18 12:48 PM, TC Haddad wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Thanks - I'll experiment a bit more.
Case doesn't seem to be having an impact.<br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">What's confusing is that the
GetFeatureInfo request doesn't use anything that would be
case-sensitive, and my map file is set to return all fields,
regardless of field name. <br>
</div>
<div class="gmail_default"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Dec 10, 2018 at 9:45 AM James Klassen
<<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="auto">I tried changing the demo parcels layer to
GeoPackage with ogr2ogr and it worked for me.
<div dir="auto"><br>
</div>
<div dir="auto">I also I tried SpatiaLite, but identify
returned ???? for all the fields. I suspect this is a
case issue, but I didn't have time to check if changing
the case in template would fix it.</div>
<div dir="auto"><br>
</div>
<div dir="auto">SpatiaLite might be case insensitive itself
but it does present a case to MapServer and then MapServer
passes that onto GeoMoose. MapServer and GeoMoose are
both case sensitive.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Dec 10, 2018, 11:36 TC Haddad <<a href="mailto:tchaddad@gmail.com" target="_blank">tchaddad@gmail.com</a> wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Thanks, I think I am ok on
the GM includes, but will play with the field name
case. Everything I've seen says SQLite/SpatiaLite is
case-insensitive...<br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">The GetFeatureInfo response
is showing some sort of return, but it is not
intelligible. <br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Other things I've tried: <br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">- identifying the same data
in GeoPacakge (identify fails in the same way), and <br>
</div>
<div class="gmail_default">- ESRI PGDB (identify
succeeds, which is frustrating!)</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Dec 10, 2018 at 9:12 AM James
Klassen <<a href="mailto:klassen.js@gmail.com" rel="noreferrer" target="_blank">klassen.js@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">One thing to check is if the case of
the properties. Different formats have different
conventions about lower/mixed/uppercase for the
properties/field names.
<div><br>
</div>
<div>If you look at the response to the
GetFeatureInfo request is it showing data?</div>
<div><br>
</div>
<div>Another thing if you aren't using the standard
GeoMoose includes, you might be missing the
metadata block to enable all the WMS/WFS request
types.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Dec 10, 2018 at 8:49 AM TC
Haddad <<a href="mailto:tchaddad@gmail.com" rel="noreferrer" target="_blank">tchaddad@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Does anyone
have a successful GM3 example of
enabling Identify on items in a
SpatiaLite db?</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">I have a
working example in GM2 that I am trying
to transfer to GM3, and everything I've
tried is failing.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">The layer draws
just fine, and there are no significant
error messages, just no results.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Layer def and
Mapbook snippet below, SpatiaLite db was
created in QGIS 2.18.<br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">----------------
fwd ---------------- >></div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default"> LAYER<br>
NAME 'points'<br>
CONNECTIONTYPE ogr<br>
CONNECTION "\data\points.sqlite"<br>
DATA "points" <br>
STATUS ON<br>
TYPE POINT<br>
PROJECTION<br>
'init=epsg:3857'<br>
END <br>
METADATA<br>
'ows_title' 'points'<br>
'ows_include_items' 'all'<br>
'gml_include_items' 'all'<br>
END <br>
LABELCACHE ON<br>
LABELITEM 'SERVICELOC'<br>
TEMPLATE 'foo.html'<br>
CLASS<br>
NAME "Service Locations" <br>
STYLE<br>
SYMBOL "square" <br>
SIZE 8.0<br>
OUTLINECOLOR 0 0 0<br>
COLOR 0 0 255<br>
END<br>
LABEL<br>
TYPE TRUETYPE<br>
FONT vera_sans<br>
SIZE 8<br>
ANTIALIAS TRUE<br>
WRAP ' '<br>
COLOR 0 0 255<br>
OUTLINECOLOR 255
255 255<br>
BUFFER 4<br>
MINFEATURESIZE
auto<br>
PARTIALS FALSE<br>
POSITION uc<br>
END<br>
END<br>
TOLERANCE 30<br>
END<br>
</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">++++++++++++++++++++</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">
<map-source name="points"
type="mapserver"><br>
<file>points.map</file><br>
<layer name="points"
status="off"><br>
<template
name="identify"><![CDATA[<br>
<div><br>
<div
style="background-color:Gainsboro"><br>
<b>Points</b><br>
</div><br>
<div
class="item"><br>
<label>Location
Number:</label> {{
properties.LocNumber }}<br>
</div><br>
<div
class="item"><br>
<label>Location
Street:</label> {{
properties.LocStreet }}<br>
</div><br>
<br>
</div><br>
]]></template><br>
</layer><br>
<param name="FORMAT"
value="image/png;bits=8"/><br>
</map-source><br>
</div>
<br>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" rel="noreferrer" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a></blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote></div>