Thanks for the row fix! I had already known there was an issue but I didn't realize how bad it was until today, and it was also a low priority. Turns out almost all counties were actually wrong due to a data error I didn't know about in Labor bureau data. Some of the counties listed in the labor bureau do not contain their actual FIPS code and are completely arbitrary and sometimes this led to a duplicate FIPS code.
They are identified as like CN(state FIPS code)(3 digit number)(ID of dataset) but for about half the 3 digit number was the fips code and half weren't. Which is why some counties didn't appear with any data, because the ones that weren't FIPS codes sometimes conflicted with a real FIPS code and overwrote it in the DB. I had already begun fixing it, and its completed now after having to get a file from the Labor bureau to map all Labor Bureau ID's to FIPS codes. Then reconstructed the entire DB. Part of the reason for such a big error is I run a command to generate the mapping codes after inserting the 900,000 rows into the DB. The counties are not listed by in order or by state in the files so its a pretty hard to create its mapping code that is an auto-increment 16 bit Hex number by state. Since some counties are overwritten by other counties, that county mapping ID is now passed on to the next county in the list, making all the counties after the missing county wrong. MA is correct now :) -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/groups/opt_out.
