Chris Whong chriswhong

## 311_scratch.json
{
  "version": "2",
  "header": {
    "title": "NYC 311 Data",
    "description": "The last 3 million NYC 311 complaints",
    "navigation": [
      {
        "label": "Download",
        "url": ""
      }

## 311_test.json
{
  "version": "2",
  "header": {
    "title": "NYC 311 Data",
    "description": "The last 3 million NYC 311 complaints",
    "navigation": [
      {
        "label": "Download",
        "url": ""
      }

## boro.sql
--Replace county FIPS code with NYC boro code, concatenate with 6-digit tract ID

SELECT
	*,
	(
  		(
  			CASE WHEN (substring(geo_id2,4,2) = '61')
          	THEN '1'
            WHEN (substring(geo_id2,4,2) = '05')
        	THEN '2'

## index.html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
    <title>Bootstrap 101 Template</title>

    <!-- Bootstrap -->

## statenisland.SQL
select geom from nybb WHERE borocode < 5
UNION ALL SELECT ST_Translate(geom,.05,.2,4326) as geom FROM nybb WHERE borocode=5

## sql.txt
Socrata datasets often include a column of type 'Location', which may include a WGS84 latitude and longitude in parenthesis, separated by a comma.  `(latitude,longitude)` This format does not lend itself well to mapping the point data, as most mapping software is expecting separate attribute columns for latitude and longitude.  The SQL below is meant for use in a PostGIS database such as CartoDB.  It parses the latitude and longitude from the a Socrata location column, and creates a point geometry in `the_geom` using PostGIS' `ST_geomfromtext()` function.

With this function you can liberate point location data from Socrata's unconventional format, and put it to use in maps!

UPDATE tablename
SET the_geom =
ST_setsrid(
  ST_geomfromtext(
    concat(
      'POINT(',

## readme.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                chriswhong
                / readme.md
            
            
              Created
              October 8, 2016 04:15
            
              
                CartoDB in Docker Container https issues
              
          
    We were hosting a site on github pages that needed to use cartodb.js and maps from our self-hosted cartodb server.  Because github pages serves over https, there were mixed content errors when doing api calls to cartodb over http.
Adding ssl certificates to the nginx service on the docker host machine worked fine, but because the https traffic hitting nginx is just proxied to the cartodb services that are still running on http internally, the cartodb server is embedding http urls in some of its resources.  This will lead to mixed content errors when using the cartodb app.
2 things had to be done to fix it:

Edit cartodb/app/models/user/user_decorator.rb line 100, replace base_url: public_url, with base_url: public_url.sub('http','https'),

This will update the user_data.base_urlglobal which cdb.js uses to build many of the api calls.

  
## data.json
[
	{
		"sheetName": "FAR Part & Type of Contract",
		"layoutId": "3447568417489532966",
		"allowSubscriptions": true,
		"allowSubscribeOnDataPresent": true,
		"worldUpdate": {
			"hyc": {
				"ABX": "render-mode-client",
				"res": {

## README.md

      
              1 file
            
          
              1 fork
            
          
              1 comment
            
          
              3 stars
            
          
                chriswhong
                / README.md
            
            
              Created
              October 2, 2016 14:39
            
          
    #Using NYC geospport linux shared library from Ubuntu 16.04
I have been trying to understand more about geosupport, specifically geosupport desktop edition for linux which contains a linux .so shared library.  I would like to eventually write node.js bindings for it so that I can write geocoding scripts that don't require a ton of network traffic.
I am a C noob and this was my first time messing with C  and gcc on linux.  I was able to write and compile a simple C program that calls the Geosupport shared library with hard-coded arguments.
##What is geosupport?
"Geosupport is a data processing system originally designed to run on IBM mainframes to support geographic processing needs
common to New York City agencies." Basically, it's an NYC-specific geocoder released by the NYC department of city planning. It does many things, but at its simplest it can take human-readable address fields and return a point coordinate.

  
## chunk.sh
#!/bin/bash
FILENAME=cpdb_spending.csv
HDR=$(head -1 $FILENAME)   # Pick up CSV header line to apply to each file
split -l 200000 $FILENAME xyz  # Split the file into chunks of 20 lines each
n=1
for f in xyz*              # Go through all newly created chunks
do
  if [n -gt 1]
    then
      echo $HDR > Part${n}.csv # Write out header to new file called "Part(n)"
	{
	"version": "2",
	"header": {
	"title": "NYC 311 Data",
	"description": "The last 3 million NYC 311 complaints",
	"navigation": [
	{
	"label": "Download",
	"url": ""
	}
	--Replace county FIPS code with NYC boro code, concatenate with 6-digit tract ID

	SELECT
	*,
	(
	(
	CASE WHEN (substring(geo_id2,4,2) = '61')
	THEN '1'
	WHEN (substring(geo_id2,4,2) = '05')
	THEN '2'
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="utf-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<!-- The above 3 meta tags must come first in the head; any other head content must come after these tags -->
	<title>Bootstrap 101 Template</title>

	<!-- Bootstrap -->
	select geom from nybb WHERE borocode < 5
	UNION ALL SELECT ST_Translate(geom,.05,.2,4326) as geom FROM nybb WHERE borocode=5
	Socrata datasets often include a column of type 'Location', which may include a WGS84 latitude and longitude in parenthesis, separated by a comma. `(latitude,longitude)` This format does not lend itself well to mapping the point data, as most mapping software is expecting separate attribute columns for latitude and longitude. The SQL below is meant for use in a PostGIS database such as CartoDB. It parses the latitude and longitude from the a Socrata location column, and creates a point geometry in `the_geom` using PostGIS' `ST_geomfromtext()` function.

	With this function you can liberate point location data from Socrata's unconventional format, and put it to use in maps!

	UPDATE tablename
	SET the_geom =
	ST_setsrid(
	ST_geomfromtext(
	concat(
	'POINT(',
	[
	{
	"sheetName": "FAR Part & Type of Contract",
	"layoutId": "3447568417489532966",
	"allowSubscriptions": true,
	"allowSubscribeOnDataPresent": true,
	"worldUpdate": {
	"hyc": {
	"ABX": "render-mode-client",
	"res": {
	#!/bin/bash
	FILENAME=cpdb_spending.csv
	HDR=$(head -1 $FILENAME) # Pick up CSV header line to apply to each file
	split -l 200000 $FILENAME xyz # Split the file into chunks of 20 lines each
	n=1
	for f in xyz* # Go through all newly created chunks
	do
	if [n -gt 1]
	then
	echo $HDR > Part${n}.csv # Write out header to new file called "Part(n)"