Skip to content

Instantly share code, notes, and snippets.

View d3netxer's full-sized avatar

@tomgertin d3netxer

35 followers · 81 following
View GitHub Profile
@t-book
t-book / Apache:GeoNode SSL-TLS LE Authority
Last active May 7, 2019 19:21
Add let´s enrypt to geonode
# - Close port 8080 for inbound networking
# - Edit your local_settings to use proxy /geonode (and not port 8080)
# - Add following to local_settings: AVATAR_GRAVATAR_SSL = True
# - make sure mod_ssl is active: $ a2enmod ssl
# add let´s encrypt repository
$ sudo add-apt-repository ppa:certbot/certbot
$ sudo apt-get update
# install certbot
@jpierson
jpierson / switch-local-git-repo-to-fork.md
Last active December 26, 2022 21:48 — forked from jagregory/gist:710671
How to move to a fork after cloning

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

  1. Clone some repo (you've probably already done this step)

    git clone git@github...some-repo.git
@aawiseman
aawiseman / Overpass turbo query by date
Created October 12, 2015 02:54
[out:json][timeout:25];
// gather results
(
// query part for: “newer:"2015-10-09T19:01:00Z"”
node(newer:"2015-10-09T19:01:00Z")({{bbox}});
way(newer:"2015-10-09T19:01:00Z")({{bbox}});
area(newer:"2015-10-09T19:01:00Z")({{bbox}});
relation(newer:"2015-10-09T19:01:00Z")({{bbox}});
);
// print results
@danielfdsilva
danielfdsilva / index.js
Last active August 29, 2015 14:26
DSO blog pagination
DSO.Views = DSO.Views || {};
(function() {
DSO.Views.BlogList = function(opts) {
this.container = opts.container;
var _posts = [];
var _self = this;
var _template = JST['card-list.ejs'];
var _perPage = 9;
@andrewxhill
andrewxhill / class01.md
Last active August 29, 2015 14:05
Maps, Lies & Storytelling | Class 1
@kalxas
kalxas / README.txt
Last active September 14, 2021 10:19
Data.gov CSW HowTo v2.0
Based on copy of https://gist.github.com/kalxas/5ab6237b4163b0fdc930 on 20 June 2014 12:27 UTC
@kalxas
kalxas / data-gov-csw-howto.rst
Last active October 25, 2022 14:23
Data.gov CSW HowTo
@d3noob
d3noob / index.html
Last active November 27, 2021 16:08
Leaflet.draw plugin with options set.
<!DOCTYPE html>
<html>
<head>
<title>Leaflet.draw Plugin</title>
<meta charset="utf-8" />
<link
rel="stylesheet"
href="http://cdn.leafletjs.com/leaflet-0.7/leaflet.css"
/>
<link
@mapsam
mapsam / README.md
Last active June 18, 2023 20:20
D3: Queue.js

A look at Queue.js and how you can load multiple files before running the rest of the code. Simple visualization of populated places in the USA. Files loaded:

  • US States - topojson
  • Populated Places - geojson
@benbalter
benbalter / geojson-conversion.sh
Last active April 23, 2024 13:16
Bulk convert shapefiles to geojson using ogr2ogr
# Bulk convert shapefiles to geojson using ogr2ogr
# For more information, see http://ben.balter.com/2013/06/26/how-to-convert-shapefiles-to-geojson-for-use-on-github/
# Note: Assumes you're in a folder with one or more zip files containing shape files
# and Outputs as geojson with the crs:84 SRS (for use on GitHub or elsewhere)
#geojson conversion
function shp2geojson() {
ogr2ogr -f GeoJSON -t_srs crs:84 "$1.geojson" "$1.shp"
}