i'm not sure what this does - in Caglar's example it only shows up here & in the title - so maybe it just names the dataset? not called on anywhere else in code

gives variables names, "county" "housing_per_m2"

makes the variables readable for the histogram & other classifications? or maybe it's just naming the axes? I'm not sure what this contributes - come back

**** how do i make the two counties w missing data show up as n/a rather than 0 - come back

Plot charts don't require code for writing in the chart, but this is to state the parameters for the histogram

how does this know what variable to use?? come back

ok, it calls on csv_data_objects which earlier i define w/ county names, and density (house/land) in the x and the number of records in y. i wonder, if counties were numerical & i used that instead of housing_per, would that change the variable it uses, or am i missing something? like is this space meant for me to choose which of the x & y variables i defined under csv_data_objs to use? .. but how does it go from y= # records in the csv_data_obj line to y= count in this one? maybe because thatwas the only y i had defined under cvs_dat_obj it just automatically knows that's what i'm calling on?

can i change the color? - come back

"d3.extent(housingdensity)" refers to range of data min-max, rather than finding & adding manually

don't change anything from the orig linear code except the domain and & colors - only 2 colors for linear

function for linear classification - names it "linear" to later be referred to in chart, map, etc code

why is the domain just "housing density" and not "d3.extent(housingdensity)"?

quantile = same number of data points in each quantile. ex) 20 entries w. 4 quantiles -> each quantile has 5 data entries. not necessarily even quantiles though, like 0-20, 21-40, etc, unless entries are evenly distributed across the range

so, data split equally by # of enumerations - more saturated, the higher the value of data in that quantile

why does the range/ color list need brackets inside the parentheses

actually don't understand what the lines after *any* of the visualizations do/mean - come back

what is ".map(v => v.pop())" at the end of this? not sure if left over from the original notebook i forked & needs to be changed or just a regular part of jenks code - come back

if i take ".map(v => v.pop())" out it turns to all one color and if i just take "=> v.pop()" out it breaks so i think it's regular part of the jenks code? - come back

split by natural grouping of the data on a histogram

added 4 colors/ hex codes -> 4 classes based on natural breaks in data

tried 3, 4, & 5 colors/ classes & always end up with 13 in the lowest and 1 in the highest. not sure if i'm doing something wrong or thats just how the data is distributed - make histogram & come back

initially was called "quantize" in the very first part of the code but renamed "equal_interval" so less confusing bc they're the same thing

threshold can be used for manual or natural breaks

using it as manual here

wait - i dont think i understand the difference between the two. i made the classes manually but based on the breaks i saw in the data ? come back

wait, this is separate from the threshold code/vis right? pretty sure, but come back

the labels like "scaleQuantile" don't show up on Caglar's & it's ugly on mine, how do I get rid of it - come back

also , whats quantize vs. quantize nice - come back

the first set of code for this vis doesn't include "housing density", only this bottom one does. if i take it out it breaks so i can see the dependence the vis has on the second set of code but still dont fully get the function

im not sure what this all is - not mentioned in assignmt or lecture recording - come back

** minimap makes it look like this is all just part of something to do w d3 so im not sure if it's required to make everyting else here function or if it's just a peak at the behind the scenes in calling on d3? assign 1 worked alright without it but it didnt have data vis - come back

put range up to 40 in order to get into the bottom 11 enumeration granularity

13* - i forgot it was considering the two zeros when they should be n/a bc of msising data

md = markdown -> text

i dont get the domain - does it auto start at 0/ the lowest value in the data?

wait - i just removed the "0.02" as the last value in the domain and it didnt change the classes/colors at all - i think it automatically includes the lowest and highest values as the max & min and i just manually insert the breaks between

if need more cells than being shown in charts, use this area to edit and increase #

this cell is what actually makes the chart, calling on the variable as defined and the classification/function as defined