# coding: utf-8

# In[3]:

import datashader as ds

import datashader.transfer_functions as tf

import datashader.glyphs

from datashader import reductions

from datashader.core import bypixel

from datashader.utils import lnglat_to_meters as webm, export_image

from datashader.colors import colormap_select, Greys9, viridis, inferno

import copy

from pyproj import Proj, transform

import numpy as np

import pandas as pd

import urllib

import json

import datetime

import colorlover as cl

import plotly.offline as py

import plotly.graph_objs as go

from plotly import tools

from shapely.geometry import Point, Polygon, shape

# In order to get shapley, you'll need to run [pip install shapely.geometry] from your terminal

from functools import partial

from IPython.display import GeoJSON

py.init_notebook_mode()

# For module 2 we'll be looking at techniques for dealing with big data. In particular binning strategies and the datashader library (which possibly proves we'll never need to bin large data for visualization ever again.)

#

# To demonstrate these concepts we'll be looking at the PLUTO dataset put out by New York City's department of city planning. PLUTO contains data about every tax lot in New York City.

#

# PLUTO data can be downloaded from [here](https://www1.nyc.gov/assets/planning/download/zip/data-maps/open-data/nyc_pluto_17v1_1.zip). Unzip them to the same directory as this notebook, and you should be able to read them in using this (or very similar) code. Also take note of the data dictionary, it'll come in handy for this assignment.

# In[5]:

# Code to read in v17, column names have been updated (without upper case letters) for v18

# bk = pd.read_csv('PLUTO17v1.1/BK2017V11.csv')

# bx = pd.read_csv('PLUTO17v1.1/BX2017V11.csv')

# mn = pd.read_csv('PLUTO17v1.1/MN2017V11.csv')

# qn = pd.read_csv('PLUTO17v1.1/QN2017V11.csv')

# si = pd.read_csv('PLUTO17v1.1/SI2017V11.csv')

# ny = pd.concat([bk, bx, mn, qn, si], ignore_index=True)

#ny = pd.read_csv('nyc_pluto_18v2_csv/pluto_18v2.csv')

ny = pd.read_csv('pluto_18v2.csv')

# Getting rid of some outliers

ny = ny[(ny['yearbuilt'] > 1850) & (ny['yearbuilt'] < 2020) & (ny['numfloors'] != 0)]

# I'll also do some prep for the geographic component of this data, which we'll be relying on for datashader.

#

# You're not required to know how I'm retrieving the lattitude and longitude here, but for those interested: this dataset uses a flat x-y projection (assuming for a small enough area that the world is flat for easier calculations), and this needs to be projected back to traditional lattitude and longitude.

# In[4]:

wgs84 = Proj("+proj=longlat +ellps=GRS80 +datum=NAD83 +no_defs")

nyli = Proj("+proj=lcc +lat_1=40.66666666666666 +lat_2=41.03333333333333 +lat_0=40.16666666666666 +lon_0=-74 +x_0=300000 +y_0=0 +ellps=GRS80 +datum=NAD83 +to_meter=0.3048006096012192 +no_defs")

ny['xcoord'] = 0.3048*ny['xcoord']

ny['ycoord'] = 0.3048*ny['ycoord']

ny['lon'], ny['lat'] = transform(nyli, wgs84, ny['xcoord'].values, ny['ycoord'].values)

ny = ny[(ny['lon'] < -60) & (ny['lon'] > -100) & (ny['lat'] < 60) & (ny['lat'] > 20)]

#Defining some helper functions for DataShader

background = "black"

export = partial(export_image, background = background, export_path="export")

cm = partial(colormap_select, reverse=(background!="black"))

# ## Part 1: Binning and Aggregation

#

# Binning is a common strategy for visualizing large datasets. Binning is inherent to a few types of visualizations, such as histograms and [2D histograms](https://plot.ly/python/2D-Histogram/) (also check out their close relatives: [2D density plots](https://plot.ly/python/2d-density-plots/) and the more general form: [heatmaps](https://plot.ly/python/heatmaps/).

#

# While these visualization types explicitly include binning, any type of visualization used with aggregated data can be looked at in the same way. For example, lets say we wanted to look at building construction over time. This would be best viewed as a line graph, but we can still think of our results as being binned by year:

# In[5]:

trace = go.Scatter(

)

layout = go.Layout(

xaxis = dict(title = 'Year Built'),

yaxis = dict(title = 'Number of Lots Built')

)

fig = go.Figure(data = [trace], layout = layout)

py.iplot(fig)

# Something looks off... You're going to have to deal with this imperfect data to answer this first question.

#

# But first: some notes on pandas. Pandas dataframes are a different beast than R dataframes, here are some tips to help you get up to speed:

#

# ---

#

# Hello all, here are some pandas tips to help you guys through this homework:

#

# [Indexing and Selecting](https://pandas.pydata.org/pandas-docs/stable/indexing.html): .loc and .iloc are the analogs for base R subsetting, or filter() in dplyr

#

# [Group By](https://pandas.pydata.org/pandas-docs/stable/groupby.html): This is the pandas analog to group_by() and the appended function the analog to summarize(). Try out a few examples of this, and display the results in Jupyter. Take note of what's happening to the indexes, you'll notice that they'll become hierarchical. I personally find this more of a burden than a help, and this sort of hierarchical indexing leads to a fundamentally different experience compared to R dataframes. Once you perform an aggregation, try running the resulting hierarchical datafrome through a [reset_index()](https://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.reset_index.html).

#

# [Reset_index](https://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.reset_index.html): I personally find the hierarchical indexes more of a burden than a help, and this sort of hierarchical indexing leads to a fundamentally different experience compared to R dataframes. reset_index() is a way of restoring a dataframe to a flatter index style. Grouping is where you'll notice it the most, but it's also useful when you filter data, and in a few other split-apply-combine workflows. With pandas indexes are more meaningful, so use this if you start getting unexpected results.

#

# Indexes are more important in Pandas than in R. If you delve deeper into the using python for data science, you'll begin to see the benefits in many places (despite the personal gripes I highlighted above.) One place these indexes come in handy is with time series data. The pandas docs have a [huge section](http://pandas.pydata.org/pandas-docs/stable/timeseries.html) on datetime indexing. In particular, check out [resample](https://pandas.pydata.org/pandas-docs/stable/generated/pandas.DataFrame.resample.html), which provides time series specific aggregation.

#

# [Merging, joining, and concatenation](https://pandas.pydata.org/pandas-docs/stable/merging.html): There's some overlap between these different types of merges, so use this as your guide. Concat is a single function that replaces cbind and rbind in R, and the results are driven by the indexes. Read through these examples to get a feel on how these are performed, but you will have to manage your indexes when you're using these functions. Merges are fairly similar to merges in R, similarly mapping to SQL joins.

#

# Apply: This is explained in the "group by" section linked above. These are your analogs to the plyr library in R. Take note of the lambda syntax used here, these are anonymous functions in python. Rather than predefining a custom function, you can just define it inline using lambda.

#

# Browse through the other sections for some other specifics, in particular reshaping and categorical data (pandas' answer to factors.) Pandas can take a while to get used to, but it is a pretty strong framework that makes more advanced functions easier once you get used to it. Rolling functions for example follow logically from the apply workflow (and led to the best google results ever when I first tried to find this out and googled "pandas rolling")

#

# Google Wes Mckinney's book "Python for Data Analysis," which is a cookbook style intro to pandas. It's an O'Reilly book that should be pretty available out there.

#

# ---

#

# ### Question

#

# After a few building collapses, the City of New York is going to begin investigating older buildings for safety. The city is particularly worried about buildings that were unusually tall when they were built, since best-practices for safety hadn’t yet been determined. Create a graph that shows how many buildings of a certain number of floors were built in each year (note: you may want to use a log scale for the number of buildings). Find a strategy to bin buildings (It should be clear 20-29-story buildings, 30-39-story buildings, and 40-49-story buildings were first built in large numbers, but does it make sense to continue in this way as you get taller?)

#

# ### Answer

# In[7]:

# group dataset by number of floor

trace2 = go.Scatter(

)

#graph data to find out how number of floors are distriubuted

layout2 = go.Layout(

xaxis = dict(title = 'Number of Floors'),

yaxis = dict(title = 'Building Count')

)

mean_flrs = ny['numfloors'].mean()

print(mean_flrs)

med_flrs = ny['numfloors'].median()

print(med_flrs)

max_flrs = ny['numfloors'].max()

print(max_flrs)

min_flrs = ny['numfloors'].min()

print(min_flrs)

fig2 = go.Figure(data = [trace2], layout = layout2)

py.iplot(fig2)

type(ny)

conditions = [

(ny['yearbuilt'] < 2020)]

choices = [1899, 1910, 1920, 1930, 1940, 1950, 1960, 1970, 1980, 1990, 2000, 2010, 2020]

ny['decabuilt'] = np.select(conditions, choices)

ny.head(10)

conditions = [

(ny['numfloors'] < 120)]

choices = [2, 3, 5, 10, 15, 20, 30, 40, 50, 60, 80, 100, 120]

ny['floorgrp'] = np.select(conditions, choices)

print(ny.head(10))

trace = go.Bar(

)

layout = go.Layout(

xaxis = dict(title = 'Decade Built'),

yaxis = dict(title = 'Number of Lots Built')

)

fig = go.Figure(data = [trace], layout = layout)

py.iplot(fig)

trace = go.Bar(

)

layout = go.Layout(

xaxis = dict(title = 'Number of Floors'),

yaxis = dict(title = 'Log of Number of Lots Built')

)

fig = go.Figure(data = [trace], layout = layout)

py.iplot(fig)

# In[18]:

#choices = [2, 3, 5, 10, 15, 20, 30, 40, 50, 60, 80, 100, 120]

flr1 = ny[['bbl', 'decabuilt', 'floorgrp']]

flr1

def flrprnt(flrnum, num1,num2):

return 0

flrser = [0, 2, 3, 5, 10, 15, 20, 30, 40, 50, 60, 80, 100, 120]

for i in range(len(flrser)-1):

flrprnt(flr1[flr1.floorgrp == flrser[i+1]],flrser[i],flrser[i+1])

# ## Part 2: Datashader

#

# Datashader is a library from Anaconda that does away with the need for binning data. It takes in all of your datapoints, and based on the canvas and range returns a pixel-by-pixel calculations to come up with the best representation of the data. In short, this completely eliminates the need for binning your data.

#

# As an example, lets continue with our question above and look at a 2D histogram of YearBuilt vs NumFloors:

# In[17]:

yearbins = 200

floorbins = 200

yearBuiltCut = pd.cut(ny['yearbuilt'], np.linspace(ny['yearbuilt'].min(), ny['yearbuilt'].max(), yearbins))

numFloorsCut = pd.cut(ny['numfloors'], np.logspace(1, np.log(ny['numfloors'].max()), floorbins))

xlabels = np.floor(np.linspace(ny['yearbuilt'].min(), ny['yearbuilt'].max(), yearbins))

ylabels = np.floor(np.logspace(1, np.log(ny['numfloors'].max()), floorbins))

data = [

go.Heatmap(z = ny.groupby([numFloorsCut, yearBuiltCut])['bbl'].count().unstack().fillna(0).values,

colorscale = 'Greens', x = xlabels, y = ylabels)

]

py.iplot(data)

# This shows us the distribution, but it's subject to some biases discussed in the Anaconda notebook [Plotting Perils](https://anaconda.org/jbednar/plotting_pitfalls/notebook).

#

# Here is what the same plot would look like in datashader:

#

#

# In[18]:

cvs = ds.Canvas(800, 500, x_range = (ny['yearbuilt'].min(), ny['yearbuilt'].max()),

y_range = (ny['numfloors'].min(), ny['numfloors'].max()))

agg = cvs.points(ny, 'yearbuilt', 'numfloors')

view = tf.shade(agg, cmap = cm(Greys9), how='log')

export(tf.spread(view, px=2), 'yearvsnumfloors')

# That's technically just a scatterplot, but the points are smartly placed and colored to mimic what one gets in a heatmap. Based on the pixel size, it will either display individual points, or will color the points of denser regions.

#

# Datashader really shines when looking at geographic information. Here are the latitudes and longitudes of our dataset plotted out, giving us a map of the city colored by density of structures:

# In[10]:

NewYorkCity = (( -74.29, -73.69), (40.49, 40.92))

cvs = ds.Canvas(700, 700, *NewYorkCity)

agg = cvs.points(ny, 'lon', 'lat')

view = tf.shade(agg, cmap = cm(inferno), how='log')

export(tf.spread(view, px=2), 'firery')

# Interestingly, since we're looking at structures, the large buildings of Manhattan show up as less dense on the map. The densest areas measured by number of lots would be single or multi family townhomes.

#

# Unfortunately, Datashader doesn't have the best documentation. Browse through the examples from their [github repo](https://github.com/bokeh/datashader/tree/master/examples). I would focus on the [visualization pipeline](https://anaconda.org/jbednar/pipeline/notebook) and the [US Census](https://anaconda.org/jbednar/census/notebook) Example for the question below. Feel free to use my samples as templates as well when you work on this problem.

#

# ### Question

#

# You work for a real estate developer and are researching underbuilt areas of the city. After looking in the [Pluto data dictionary](https://www1.nyc.gov/assets/planning/download/pdf/data-maps/open-data/pluto_datadictionary.pdf?v=17v1_1), you've discovered that all tax assessments consist of two parts: The assessment of the land and assessment of the structure. You reason that there should be a correlation between these two values: more valuable land will have more valuable structures on them (more valuable in this case refers not just to a mansion vs a bungalow, but an apartment tower vs a single family home). Deviations from the norm could represent underbuilt or overbuilt areas of the city. You also recently read a really cool blog post about [bivariate choropleth maps](http://www.joshuastevens.net/cartography/make-a-bivariate-choropleth-map/), and think the technique could be used for this problem.

#

# Datashader is really cool, but it's not that great at labeling your visualization. Don't worry about providing a legend, but provide a quick explanation as to which areas of the city are overbuilt, which areas are underbuilt, and which areas are built in a way that's properly correlated with their land value.

# In[ ]:

output = np.correlate(ny["assessland"],ny["assessland"],mode='full')

print(output)

# In[19]: