| - Log into GeoNode as Admin | |
| - In the menu, click on GeoServer and open a new tab | |
| - In the GeoServer data menu, click on 'styles' |
Daadab and Dollo Ado Refugee Camps were mapped in May 2012 http://www.disruptivegeo.com/2012/05/imagery-to-the-crowd-early-results/
Here are the OverPass Turbo queries to extract the buildings, roads, and POIs done during that time.
[diff:"2010-05-01T15:00:00Z","2012-07-01T15:00:00Z"];
(
// get all roads
way[highway]({{bbox}});
| <!--how to embed a gifv! --> | |
| <video autoplay loop poster="http://i.imgur.com/xIlXXEg.jpg" id="backgroundgif" width="500" height="300"> | |
| <source src="http://i.imgur.com/xIlXXEg.webm" type="video/webm"> | |
| <source src="http://i.imgur.com/xIlXXEg.mp4" type="video/mp4"> | |
| </video> |
| <!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 |
jquery tip: attach listener to body tag
$("body").on("click", "a", function(event) {
... your custom code
.... this attaches the listener to the body, but will match against any click from an <a> tag.
.... so you don't have to attach to every a tag every time, but can use only 1 listener
... also good, because you can attach the listener to a parent element and not have to update the listners whenever a new <a> tag is created
});
For geonode.state.gov here is the harvest page: https://catalog.data.gov/harvest/geonode-state-csw
On the about page is the source url CSW call:
By default GeoNode only returns at max 10 records in a csw request at a time
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.
Clone some repo (you've probably already done this step)
git clone git@github...some-repo.git
install nvm https://github.com/creationix/nvm
Install node version LTS 6.9.5
nvm install --lts 6.9.5
sudo apt-get update
https://medium.com/coderscorner/installing-oracle-java-8-in-ubuntu-16-10-845507b13343
sudo apt-get update
edited the /etc/apt/sources.list file and added:
deb https://qgis.org/debian xenial main deb-src https://qgis.org/debian xenial main
(I don't think this step is needed: sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable)