Image
EAN-139780321013125   EAN-13 barcode 9780321013125
Product NameAmerican Nations: A History Of The Eleven Rival Regional Cultures Of North America
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0143122029
SKU1101671972
Price New8.79 US Dollars    (curriencies)
Price Used7.38 US Dollars    (curriencies)
Width0.9 inches    (convert)
Height8.4 inches    (convert)
Length5.5 inches    (convert)
Weight11.2 ounces    (convert)
AuthorColin Woodard
Page Count384
BindingPaperback
Published09/25/2012
FeaturesPenguin Books
Long Description• A  New Republic  Best Book of the Year •  The Globalist  Top Books of the Year • Winner of the Maine Literary Award for Non-fiction • Particularly relevant in understanding who voted for who in this presidential election year, this is an endlessly fascinating look at American regionalism and the eleven “nations” that continue to shape North America According to award-winning journalist and historian Colin Woodard, North America is made up of eleven distinct nations, each with its own unique historical roots. In American Nations he takes readers on a journey through the history of our fractured continent, offering a revolutionary and revelatory take on American identity, and how the conflicts between them have shaped our past and continue to mold our future. From the Deep South to the Far West, to Yankeedom to El Norte, Woodard (author of American Character: A History of the Epic Struggle Between Individual Liberty and the Common Good ) reveals how each region continues to uphold its distinguishing ideals and identities today, with results that can be seen in the composition of the U.S. Congress or on the county-by-county election maps of this year's Trump versus Clinton presidential election.
Similar Items9780131954953: Cultural Geography Of The United States (Foundations Of Cultural Geography Series)
9780131944244: The Cultural Geography Of The United States: A Revised Edition
9780131499966: War and Peace and War: The Life Cycles of Imperial Nations
9780130383808: Across This Land: A Regional Geography Of The United States And Canada (Creating The North American Landscape)
9780080442921: Doing Business Internationally, Second Edition: The Guide To Cross-Cultural Success
9780071378321: Doing Business Internationally, Second Edition: The Guide To Cross-Cultural Success
9780060926847: East Main Street: Asian American Popular Culture
9780029030905: American History: A Very Short Introduction (Very Short Introductions)
9780028625829: The History Atlas Of North America (History Atlas Series)
9780004724652: On Glasgow And Edinburgh
View 59 more similar items
Created09-04-2012 11:06:22pm
Modified04-30-2020 6:26:23pm
MD5d2d536f705df2e52044d9ae4b7356209
SHA2567c297cafd77025fe4812c049b74045681d21b3eaee6de7a02d0e72ad5cb88ad3
Search Googleby EAN or by Title
Query Time0.0192440

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share