| #!/usr/local/bin/fontforge | |
| # Usage: fontforge -script ttc2ttf.pe /path/to/font.ttc | |
| fonts = FontsInFile($1) | |
| n = SizeOf(fonts) | |
| i = 0 | |
| while (i < n) | |
| Open($1 + "(" + fonts[i] + ")", 1) | |
| index = ToString(i + 1) |
| # Ubuntu Server automated installation | |
| # by Scott Lowe (scott.lowe@scottlowe.org) | |
| d-i debian-installer/locale string en_US | |
| d-i console-setup/ask_detect boolean false | |
| d-i keyboard-configuration/layoutcode string us | |
| d-i netcfg/choose_interface select eth0 | |
| d-i netcfg/get_hostname string hostname | |
| d-i netcfg/get_domain string domain.com | |
| d-i netcfg/wireless_wep string |
| #!/bin/bash | |
| # The MIT License (MIT) | |
| # | |
| # Copyright (c) 2015 Philip Huppert | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy of | |
| # this software and associated documentation files (the "Software"), to deal in | |
| # the Software without restriction, including without limitation the rights to | |
| # use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of |
Note on how to install caffe on Ubuntu. Sucessfully install using CPU, more information for GPU see this link
###Installation
lspci | grep -i nvidia
Detailed walk through of building extraction using postgis
First lets pull a data layer from of openstreetmap. You can do this any which way you’d like, as there are a variety of methods for pulling openstreetmap data from their database. Check the [wiki] (http://wiki.openstreetmap.org/wiki/Downloading_data) for a comprehensive list. My favourite method thus far is pulling the data straight into QGIS using the open layers plugin. For those who may want to explore this method, check [this tutorial] (http://www.qgistutorials.com/en/docs/downloading_osm_data.html). For building extraction you only need building footprints, and include the building tags. Not all polygons are of type building in OSM, so we can download all the polygons, and then filter the layer for only polygons tagged as buildings.
LiDAR data was pulled from USGS via the Earth Explorer site. [Here] (http://earthobservatory.nasa.gov/blogs/ele
| package main | |
| import ( | |
| "net/http" | |
| "database/sql" | |
| "fmt" | |
| "log" | |
| "os" | |
| ) |
Cython has two major benefits:
Cython gains most of it's benefit from statically typing arguments. However, statically typing is not required, in fact, regular python code is valid cython (but don't expect much of a speed up). By incrementally adding more type information, the code can speed up by several factors. This gist just provides a very basic usage of cython.
A simple Ghostscript command to merge two PDFs in a single file is shown below:
gs -dNOPAUSE -sDEVICE=pdfwrite -sOUTPUTFILE=combine.pdf -dBATCH 1.pdf 2.pdfInstall Ghostscript:
Type the command sudo apt-get install ghostscript to download and install the ghostscript package and all of the packages it depends on.
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j