EAN-139780897475716   EAN-13 barcode 9780897475716
Product NameUs Navy Ships Camouflage Wwii: Destroyers And Destroyer Escorts - Specials Series (6099)
CategoryBook / Magazine / Publication
Short DescriptionHeight:0.2 inches / Length:10.8 inches / Weight:0.49 pounds / Width:8 inches
Amazon.comA Buy on Amazon ~ 0897475712
Price New9.14 US Dollars    (curriencies)
Price Used5.52 US Dollars    (curriencies)
Weight2.08 ounces    (convert)
AuthorAl Adcock
Page Count68
FeaturesUsed Book in Good Condition
Long DescriptionSince the formation of the Continental Navy in 1775, US Navy ships have donned numerous colors. During WWI, when the German U-boat threatened to stop US and Canadian supplies from reaching their European allies, the British Royal Navy began using a splinter-type camouflage to confuse the enemy about the speed, distance, and the course of its ships. The US also adopted similar camouflage during this timeframe. When the Bureau of Construction and Repairs began issuing instructions for different camouflage schemes and colors, the Navy took note, and by WWII, USN destroyers sported several different camouflage schemes that ranged from blue to gray to black and included painted bow waves and multiple dazzle schemes. When WWII ended in 1945, the fleet was restored to Standard Navy Gray to await the next revolution in deceptive paintwork. Illustrated with 116 b/w photos, 2 color photos, and over 30 color renderings/profiles. 68 pages.
Similar Items9781848320413: Shipcraft 13 - New Orleans Class Cruisers
9781846034442: US Destroyers 1942–45: Wartime classes (New Vanguard)
9781846030376: Us Navy Aircraft Carriers, 1942-45: Wwii-Built Ships (New Vanguard)
9781841769233: Landing Ship, Tank (LST) 1942–2002 (New Vanguard)
9781557502803: The Buckley-Class Destroyer Escorts
9780971324473: Ship Shape, a Dazzle Camouflage Sourcebook: An Anthology of Writings About Ship Camouflage During World War I
9780906290873: Camouflage and Art - Design for Deception in World War II
9780897476706: Uss Kidd On Deck (26010)
9780897475877: Us 110' Subchasers In Action - Warships No. 33
9780897475068: U.S. Navy Floatplanes Of World War Ii In Action - Aircraft No. 203
9780897474672: Us Destroyers In Action, Part 2 - Warships No. 20
9780897473781: Destroyer Escorts In Action - Warships No. 11
9780897471954: U.S. Navy Carrier Bombers Of Wwii: Tbd Devastator; Sbd Dauntless; Sb2c Helldiver; Tbf/Tbm Avenger - Aerodata International (6205)
9780713710267: United States Navy Destroyers Of World War Ii In Action
Created02-28-2013 10:20:11am
Modified06-12-2017 7:40:08am
Search Googleby EAN or by Title
Query Time0.0239861

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{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:{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.