Skip to content

Instantly share code, notes, and snippets.

Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
from __future__ import print_function
import re
import sys
import os
import csv
from pymongo import MongoClient
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A05
date: 12/16/2014
size: 64KiB
capacity: 15MiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
*-cache:0
This file has been truncated, but you can view the full file.
/var/folders/cn/w1t67kc95gjdcw052j_tyns80000gn/T/tmp.TaaaA2sP ~/dashboard/nightly-builds/girder
/var/folders/cn/w1t67kc95gjdcw052j_tyns80000gn/T/tmp.TaaaA2sP/build /var/folders/cn/w1t67kc95gjdcw052j_tyns80000gn/T/tmp.TaaaA2sP ~/dashboard/nightly-builds/girder
* Extra verbosity turned on
Reading Script: /Users/jbeezley/dashboard/nightly-builds/girder/vagrant.cmake
-- VAGRANT VERSION: Vagrant 1.8.5
-- ANSIBLE VERSION: ansible-playbook 2.1.1.0
config file =
configured module search path = Default w/o overrides
Cloning into '/var/folders/cn/w1t67kc95gjdcw052j_tyns80000gn/T/tmp.TaaaA2sP'...
An action 'destroy' was attempted on the machine 'girder',
but another process is already executing an action on the machine.
Vagrant locks each machine for access by only one process at a time.
Please wait until the other Vagrant process finishes modifying this
machine, then try again.
If you believe this message is in error, please check the process
listing for any "ruby" or "vagrant" processes and kill them. Then
try again.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"strokeColor": {"r": 1, "g": 0, "b": 0}
},
"geometry":
{

Persisting layer style

This document serves to describe requirements desired for describing and persisting styling of layers displayed in Minerva. Different kinds of data have different requirements so it may be useful to describe seperate style objects per data type. For example, vector layers (points, lines, polygons) focus more on discrete styling based on categorical values where gridded data is more focused on lookup tables on numeric values.

from __future__ import print_function
import sys
import json
import jsonschema
import requests
_schema = None
@jbeezley
jbeezley / README.md
Last active April 11, 2016 11:54
GeoJS feature data format

Overview

The top level object passed to geojs should be a GeoJSON FeatureCollection.

{
  "type": "FeatureCollection",
  "features": [],              // Array of feature objects (required)
  "crs": {},                   // [optional] Coordinate reference system (default EPSG:4326)
18 Mar 18:35:52 ERROR [geoserver.ows] -
org.geoserver.platform.ServiceException: java.io.IOException: Failed to create reader from file:data/geonode/forecast_io_airtemp and hints Hints:
STYLE_FACTORY = StyleFactoryImpl
COMPARISON_TOLERANCE = 1.0E-9
GRID_COVERAGE_FACTORY = GridCoverageFactory
TILE_ENCODING = null
FORCE_AXIS_ORDER_HONORING = http
EXECUTOR_SERVICE = java.util.concurrent.ThreadPoolExecutor@4fbe3504[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
LENIENT_DATUM_SHIFT = true
FORCE_LONGITUDE_FIRST_AXIS_ORDER = true