Skip to content

Instantly share code, notes, and snippets.

View JJediny's full-sized avatar

John Jediny JJediny

View GitHub Profile
@JJediny
JJediny / gist:d4cc53dc021d81ed3752
Created January 20, 2015 05:49
NEPAnode Data Migration - Vector Data
_113th_congressional_district_2014
_303d_impaired_waters
_368_energy_corr_area
_368_energy_corr_centerline2
aiannh_2014
airspacehazard_faa
ak_tribal_areas
all_mammals_nov2013
aqueductglobalmap2
aquifer_area_2
@JJediny
JJediny / gist:309e55eb1362da35bead
Created January 20, 2015 05:51
NEPAnode Data Migration - Raster Data
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
@JJediny
JJediny / gist:7b2f472ad73b699fe114
Created January 20, 2015 05:54
NEPAnode Data Migration - Styles and Metadata
_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
@JJediny
JJediny / 0012_M2MCustomFieldbyQueue.py
Created February 23, 2015 09:02
Django-Helpdesk: Django South Migration for ManytoMany CustomField to Queue
# -*- 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."
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@JJediny
JJediny / map.geojson
Last active August 29, 2015 14:17 — forked from anonymous/map.geojson
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@JJediny
JJediny / Issues.md
Last active August 29, 2015 14:17 — forked from rclark/Issues.md

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

  1. You have to rely on an AJAX request, this example uses jQuery
  2. 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.
  3. 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.
  4. 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.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.