franTarkenton

Outline

• CI/CD for BCDC api tests
• The Story... How I arrived at using Github Actions
• Workflow that was created
• Opportunities for Improvement

bradwilson

{
    "$help": "https://aka.ms/terminal-documentation",
    "$schema": "https://aka.ms/terminal-profiles-schema",
    "actions": [
        {
            "command": "copy",
            "keys": "ctrl+shift+c"
        },
        {
            "command": "paste",

yutannihilation

Read Parquet files from R

Prerequisite

Install libarrow and libparquet.

git clone https://github.com/apache/arrow/

cassiozen

Pixelbook Setup

Change your channel

Some of the features mentioned in this document only work on the beta or Dev channel. To change your channel:

1. chrome://help in a browser window
2. Click Detailed Build Information
3. Change Channel
4. Select Beta (Or Dev, if you're feeling adventurous)

DeanCording

This flow provides a tool for managing Over The Air firmware updates for ESP8266 Wifi SoC modules running the Arduino ESP8266 environment. It also supports Sonoff devices running the Tasmota firmware.

The ESP8266 is a very small, cheap, and reasonably powerful microcontroller with integrated WiFi. The OTA firmware upgrade process allows you to install these modules in location and have them automatically upgrade their firmware over WiFi.

The OTA upgrade library contacts a specified URL and passes the name and MD5 hash of the module's current firmware. This server implemented in this flow will compare the supplied MD5 hash against the one for the latest firmware and, if different, send the new firmware to the module. The server will uses either the module's MAC address or firmware name to identify the correct firmware file to send. The firmware can be specified in either the request URL or in the x-esp8266-version property in the

DeanCording

/**
 * ESP8266 project template with optional: 
 *  - WiFi config portal - auto or manual trigger
 *  - OTA update - Arduino or web server
 *  - Deep sleep
 *  - Process timeout watchdog
 * 
 * Copyright (c) 2016 Dean Cording  <dean@cording.id.au>
 *
 * Permission is hereby granted, free of charge, to any person obtaining a copy

pramsey

• The presentation in PDF format.
• Publishing Landsat on AWS, the use of cloud infrastructure for public data distribution and processing.
• On the size of Google Maps, now larger than most national mapping agencies.
• OpenTripPlanner and OpenStreetMap, how open data and open source leverage each other and are in turn re-consumed by governmnet and civil society.
• Michael H Goldhaber on the attention economy, a prescient take on content and the internet from 1997.
• Google aquires Skybox Imaging.
• Bibiana McHugh on Portland Trimet's [triple open strategy](https://prezi.com/vmydw-uwqalm/copy-of-you-complete

foosel

First experiments with NodeMCU to publish the current settings of my adjustable height working desk to MQTT.

NodeMCU can be found here: https://github.com/nodemcu/nodemcu-firmware

Note that you'll need a current version with support for floats (which the ultrasonic sensor library utilizes), I'm using 0.9.5 2015-03-18 with float support myself.

Support for the HC-SR04 sensor in NodeMCU can be found here: https://github.com/sza2/node_hcsr04

I provided my slightly adjusted version which makes measuring a non-blocking afair, allowing for callbacks when the measurement completes.

rclark

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.