Steve Vissault SteveViss

Crop GHRSST in R terra.

I've ignored all our detailed stuff for our COG creation - this crops into memory, converts to Celsius, writes to file (I've set up a place to set the output directory but it writes to working directory atm) - I tested from compute in California and it was fast. With that you should be able to generate the days you want with seq(as.Date(), by = "1 day") kind of construct and loop. Note that some days are missing, we have reported them so maybe fixed now, but it's worth wrapping the rast(dsn) call in a try in case the read fails

## https://urs.earthdata.nasa.gov/documentation/for_users/user_token
## the token is a long text string, the header is "Authorization: Bearer {token}"

I'm learning about SOPS and setting it up as my preferred mechanism for storing secrets. Here are my notes.

PGP

It’s security mechanism is that we (i.e. client) use a PUBLIC key from the receiver (i.e. server) and encode it with a random key (I’m saying nonce but it could be reused)

This varies from RSA and SSH because the server uses a PUBLIC key to identify the client.

Web of trust

Web of trust operates by still using PGP (i.e. encoding with recipient’s public key) but additionally, we can encrypt/sign the data as our own by signing it with the client’s private key.

This means the recipient will initially decrypt via our (i.e. client’s) public key (verifying the source) and then decrypting via their (i.e. server’s) private key to get the data.

Crossref free search

setup

Install

Configuring eslint for Atom

Dan Abramov does a really good job explaining why and how in 'Lint Like It’s 2015'

For the tl;dr version

// install atom's linter && linter-eslint
apm install linter
apm install linter-eslint

Overview

In general, it seems there are roughly five (5) ways to get "file data" (e.g. a GeoTIFF) out of a PostGIS geoprocessing workflow:

Export just the raster field as an ASCII grid
Connect to the database using a desktop client (e.g. QGIS) [1]
Use a procedural language (like PLPGSQL or PLPYthon) [2]
Use the COPY declaration to get a hex dump out and convert it to a binary file
Fill a 2D NumPy array with a byte array and serialize it to a binary file using GDAL or psycopg2 [3, 4]
Use ST_AsTiff() or the more general ST_AsGDALRaster() to get a byte array, which can be written to a binary file

	#I have >1000 bees to check its name, so I want to automatize taxize for
	# fixing misspellings when possible
	# updating synonims to accepted names
	# keeping ONLY accepted species (fully resolved at species level)

	# this uses taxize > 0.7.6.9157 If you are using older version (e.g. what its now on CRAN) see the history of this file.
	library(taxize)
	library(dplyr)

	#example: good, synomin, typo, unexisting, genus only.

	var gulp = require('gulp');
	var browserSync = require('browser-sync');
	var reload = browserSync.reload;
	var deploy = require('gulp-gh-pages');
	var cp = require('child_process');
	var harp = require('harp')

	/**
	* Serve the Harp Site
	*/

	##' Modifies 'data' by adding new values supplied in newDataFileName
	##'
	##' newDataFileName is expected to have columns
	##' c(lookupVariable,lookupValue,newVariable,newValue,source)
	##'
	##' Within the column 'newVariable', replace values that
	##' match 'lookupValue' within column 'lookupVariable' with the value
	##' newValue'. If 'lookupVariable' is NA, then replace all elements
	##' of 'newVariable' with the value 'newValue'.
	##'

	#!/bin/sh
	dirs=`ls -1d */`
	for d in $dirs
	do
	echo $d
	echo '======================'
	IFS=$'\n' lines=($(cd $d; git pull))
	for l in $lines
	do
	echo $l

	<!-- copy this to YOUR_THEME.tmTheme-->
	<dict>
	<key>name</key>
	<string>diff: deleted</string>
	<key>scope</key>
	<string>markup.deleted</string>
	<key>settings</key>
	<dict>
	<key>background</key>
	<string>#EAE3CA</string>