Image | |
EAN-13 | 9780714845586 |
Product Name | Farnsworth House (Architecture In Detail) |
Language | English |
Category | Book / Magazine / Publication |
Short Description | Height:9.84 inches / Length:9.84 inches / Weight:0.83 pounds / Width:0.28 inches |
Amazon.com | Buy on Amazon ~ 0714845582 |
SKU | ACOMMP2_BOOK_USEDGOOD_0714845582 |
Price New | 14.94 US Dollars (curriencies) |
Price Used | 16.14 US Dollars (curriencies) |
Width | 0.25 inches (convert) |
Height | 9.88 inches (convert) |
Length | 9.88 inches (convert) |
Weight | 13.28 ounces (convert) |
Author | Maritz Vandenberg |
Page Count | 60 |
Binding | Paperback |
Published | 09/01/2005 |
Features | Used Book in Good Condition |
Long Description | Launched in 1991, award-winning Architecture in Detail books focus on individual seminal buildings, celebrating their exceptional character, innovative design or technical virtuosity. This book discusses the Farnsworth House as a seminal Modernist glass-and-steel house by Mies van der Rohe, one of the greatest twentieth-century architects. |
Similar Items | 9780486245829: Frank Lloyd Wright's Robie House: The Illustrated Story Of An Architectural Masterpiece (Dover Architecture) 9780470533697: Design Drawing 9780442019099: Design Drawing 9780226756004: Mies Van Der Rohe: A Critical Biography, New And Revised Edition 9780226644318: Mies Van Der Rohe: A Critical Biography, New And Revised Edition 9780226251998: Mies Van Der Rohe: A Critical Biography, New And Revised Edition 9780135866696: Modern Architecture Since 1900 9780133046434: Design Drawing 9780070283039: Design Drawing 0673419159678: Lego Architecture Farnsworth House 21009 View 13 more similar items |
Created | 01-12-2013 1:27:05am |
Modified | 04-19-2017 11:42:40pm |
MD5 | 57609dcd18780fa78103e5fed1893510 |
SHA256 | 1196ca80792ea8094d4262920fc844c1a12727b6dce716d26bad8ff5575d5fdb |
Search Google | by EAN or by Title |
Query Time | 0.0292540 |
An article of interest
Making use of the tools we offer
Data Feed API v3 - Handling Product Images
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.
- Unknown (should never actually appear in the API)
- Yes (a production image exists)
- No (there is no image)
- Pending (a pending image exists)
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.
- If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
- 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.