Tormi Tabor tormi

There are a bunch of reasons why this is convoluted, mostly in building the URL to make the request:

You have to rely on an AJAX request, this example uses jQuery
To make a GetFeatureInfo request, you must provide a BBOX for a image, and the pixel coordinates for the part of the image that you want info from. A couple of squirrely lines of Leaflet code can give you that.
Output formats. The info_format parameter in the request. We don't know a priori which will be supported by a WMS that we might make a request to. See Geoserver's docs for what formats are available from Geoserver. That won't be the same from WMS to WMS, however.
WMS services return XML docs when there's a mistake in the request or in processing. This sends an HTTP 200, which jQuery doesn't think is an error.

	var fs = require("fs");
	var path = require("path");
	var _ = require("lodash");
	var utf8 = require('utf8');
	require("natural-compare-lite");

	var IGNORE = [
	"node_modules",
	".git",
	"SUMMARY.md",

	<!DOCTYPE html>
	<html>

	<head>
	<meta charset="utf-8">
	<title>Shopping Mall Messing</title>
	<script src="http://d3js.org/d3.v3.min.js" charset="utf-8"></script>
	</head>

	<body>

	<!DOCTYPE html>
	<html>
	<head>
	<link href="http://cdn.leafletjs.com/leaflet-1.0.0-b1/leaflet.css" rel="stylesheet" type="text/css" />
	<script src="http://cdn.leafletjs.com/leaflet-1.0.0-b1/leaflet.js"></script>
	<meta charset="utf-8">
	<title>Leaflet JS Bin</title>
	<style>
	#map {
	width:600px;

	uuid: b32c2427-340e-4c5c-8c1c-281789b67fea
	langcode: en
	status: true
	dependencies:
	config:
	- core.entity_view_mode.node.teaser
	- field.storage.node.field_kasutamise_algus
	- field.storage.node.field_kasutamise_alus
	- field.storage.node.field_kinnisvara_eluea_etapp
	- field.storage.node.field_kinnisvara_kasutaja