John Jediny JJediny

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.

	aridity_oftheworld
	atl_vessel_count_all
	bald_eagle_wgs84
	baldeagle_gap_model_downsized
	baldeagle_gap_model_render
	baldeagleoccurences_heatmap_render_downsized
	ccvi_natureserve_precip2050
	ccvi_natureserve_precip2050_1
	ccvi_natureserve_precip2050_render
	ccvi_natureserve_temp2050

	_113th_congressional_district_2014.sld
	_113th_congressional_district_2014.xml
	_2076_2100_a1fi.sld
	_2076_2100_a2.sld
	_303d_impaired_waters.sld
	_303d_impaired_waters.xml
	_368_energy_corr_area.sld
	_368_energy_corr_area.xml
	_368_energy_corr_centerline2.sld
	_368_energy_corr_centerline2.xml

	# -- coding: utf-8 --
	from south.utils import datetime_utils as datetime
	from south.db import db
	from south.v2 import DataMigration
	from django.db import models

	class Migration(DataMigration):

	def forwards(self, orm):
	"Write your forwards methods here."