Hi Milo, did you succeed? I've mapserver running here with a flamingo client example. Sailor Moon Psp Game there.

Introduction GetFeatureInfo is a WMS standard call that allows one to retrieve information about features and coverages displayed in a map. The map can be composed of various layers, and GetFeatureInfo can be instructed to return multiple feature descriptions, which may be of different types.

Introduction ¶ RFC 36 added support for defining template-driven OUTPUTFORMATs for use with feature queries, including WMS GetFeatureInfo and WFS GetFeature. Apr 07, 2014 When running a GetFeatureInfo request with. Template-file doesn’t look like a MapServer template. Missing magic string, template-file doesn.

GetFeatureInfo can generate output in various formats: GML2, plain text and HTML. Templating is concerned with the HTML one. The default HTML output is a sequence of titled tables, each one for a different layer. The following example shows the default output for the tiger-ny basemap (included in the above cited releases, and onwards).

Standard Templates The following assumes you’re already up to speed with Freemarker templates. If you’re not, read the tutorial, and the page, which has simple examples. The default output is generated by the standard templates, which are three: • header.ftl • content. Guerrilla Bob V1.0 Cracked-f4cg on this page. ftl • footer.ftl The header template is invoked just once, and usually contains the start of the HTML page, along with some CSS. The default header template looks like this (as you can see, it’s completely static, and it’s in fact not provided with any variable you could expand). Custom Templates So, what do you have to do if you want to override the custom templates? Well, it depends on which template you want to override.

Header.ftl and footer.ftl are type independent, so if you want to override them you have to place a file named header.ftl or footer.ftl in the templates directory, located in your GeoServer. On the contrary, content.ftl may be generic, or specific to a feature type. For example, let’s say you would prefer a bulleted list appearance for your feature info output, and you want this to be applied to all GetFeatureInfo HTML output.

In that case you would drop the following content.ftl in the templates directory. Bulleted List Output Looking at the output we notice that point of interest features refer to image files, which we know are stored inside the default GeoServer distribution in the demo_app/pics path.

So, we could provide a POI specific override that actually loads the images. This is easy: just put the following template in the feature type folder, which in this case is workspaces/topp/DS_poi/poi (you should refer to your Internet visible server address instead of localhost, or its IP if you have fixed IPs).