Errata

Very basically, I followed the example from the Geo Mapping chapter (12).

Data is corrupted for the Virginia state: translation to path makes it a huge rectangle, filling over the whole svg, hence nothing is seen.

Note from the Author or Editor:
Already fixed for 1st ed

Confirming Anonymous' submission of the problem with the path for Virginia.

Cause: the second polygon in the state's definition is composed of 4 coordinates that all have the same latitude (37.95325) making the polygon a line which is not gracefully handled when rendered.

Quick Fix: removed the second polygon with the colinear coordinates from the geometry definition for Virginia.

Chapter 12 examples are not useable without a working version of us-states.json.

Note from the Author or Editor:
Fixed already for 1st ed

Example specifies "to apply a 0.2-second transition"

However CSS uses 0.3 second transition.

Note from the Author or Editor:
Fixed for 2nd ed.

9.3 Transitions, belong the "Please Do Not delay()" section:
1,000,400 seconds or 11.5 days -> 1,000,400 ms or 16.67 seconds

Note from the Author or Editor:
There was an error in my math here, but the reporter of this erratum also has an error in his/her math.

On the top of page 147, this parenthetical reads:

(1,000,400 seconds or 11.5 days to be precise)

The corrected text should read:

(1,000,400 ms or 16.67 minutes to be precise)

Also, at the bottom of page 146, the first "long," could be removed, so this text:

you could spend a long, long time

is changed to read:

you could spend a long time

Mismatch between text "(Note how under �Computed Style� is listed display: block.)" and Figure 3-4, in which "Computed Styles" are folded and the opened "Matched CSS Rules" instead reveals the "display: block" text.

Note from the Author or Editor:
Fixed for 2nd ed

The image is supposed to show three different bar chart, each the result of a random dataset. However, the first two charts are exactly the same. Either the random generator is broken, or the same chart got included twice.

Note from the Author or Editor:
Report confirmed. When the illustrations were merged, the top chart was duplicated. To fix: Figure 6-8 needs to be updated, replacing the middle chart with the original chart I had generated.

This statement "There are no additional anonymous function parameters to learn about later" is inaccurate. A third parameter "j" is also supported.

See https://groups.google.com/forum/?fromgroups#!searchin/d3-js/index$20j/d3-js/bpBkf9arDOA/58wI0U0j9vcJ

See also the following sentence from http://bost.ocks.org/mike/nest/#data :

"You can also access the row index (j) by adding a third argument to the function."

Note from the Author or Editor:
Fixed for 2nd ed

On p. 103 when the data is meant to drive the color of the bar chart, the
Math.round function should be used to make the "blue" component an
integer. The rgb() function doesn't seem to like floating point.

i.e. return "rgb(0,0," + (d*10) + ")";

works better as

return "rgb(0,0," + Math.round(d*10) + ")";

The problem does not show up if you use an integer dataset, but if you
allow the data to be randomized (as I did from a previous example) you need
to round the color first.

Note from the Author or Editor:
Fixed in 2nd ed

"This tells the scale to take whatever input domain that you gave to range() and expand both ends to the nearest round value. "

Is not range() domain()? nice()is a method for expand domain().

Note from the Author or Editor:
Fixed for 2nd ed

Apologies for the duplicate - this supersedes the previous one.

The sample cities data referenced in Chapter 12's geomapping example has incorrect coordinates for several cities (e.g., Seattle, Dallas...). The correct locations and updated population data from Wikipedia are posted on my github page:

https://github.com/jimcarson/d3-book/blob/master/chapter_12/us-cities.csv

The data file is part of the supplemental files downloadable from Github; however the error manifests itself on page 225 of the PDF version.

Note from the Author or Editor:
Fixed for 2nd ed.

This paragraph discusses using d3.request, but that is now deprecated. Methods in d3-fetch such as d3.text should be used instead.

Note from the Author or Editor:
This erratum was submitted for the 1st edition of the book, which, yes, is now out of date. This report is correct that API methods have changed in subsequent versions of the software, so affected parts will have to be rewritten substantially.