Changes between Initial Version and Version 1 of HowToGetBrowseImg

11/01/05 08:54:38 (14 years ago)



  • HowToGetBrowseImg

    v1 v1  
     1= How can I get the browse images (jpeg, png, gif, etc) for observations? = 
     3== WARNING: Prototype == 
     5The current implementation is much more obfuscated than it should be, as it is a prototype, and is not consistently implemented 
     6between data providers. 
     8The 'browse products' are served as metadata attached to VSO records -- the VSO message format allows User Interfaces 
     9to add extra elements to the request, which the VSO will pass on to the Data Provider that seem to be able to handle the 
     10request based on the elements that the VSO knows about.  The Data Providers can then vary their behaviour based on the 
     11new parameters. 
     13We ask those Data Providers who wish to do this to either prefix the element with their provider id, or to ContactUs, so that 
     14we can make sure two different Data Providers don't use the same name for different features. 
     16The only element currently in use is 'field', which is passed an array of strings, requesting extra fields to return with the 
     17metadata.  If the array contains an item named 'thumbnail', it will return one of the following with the rest of the returned record. 
     19 1. Absolutely nothing.  Not all data providers have browse images to return, and even if they do, they may not have complete coverage. 
     20 1. A complex type 'extra', with an element 'thumbnail'.  Please note that this is ''not'' part of the formal VSO API, and it might change as this is a prototype. 
     22The return structure looks like one of the three following, when deserialized using Perl's SOAP::Lite: 
     25extra => { 
     26    thumbnail => 'url_string' 
     28extra => { 
     29    thumbnail => { 
     30        lowres => 'url_string', 
     31        hires  => 'url_string', 
     32    } 
     35extra => { 
     36    thumbnail => { 
     37        lowres => { 
     38            loc => 'url_string', 
     39            w   => 'width_in_pixels', 
     40            h   => 'height_in_pixels', 
     41        }, 
     42        hires => { 
     43            loc => 'url_string', 
     44            w   => 'width_in_pixels', 
     45            h   => 'height_in_pixels', 
     46        }, 
     47    } 
     51The first format is deprecated, and to the best of my knowledge, is no longer in use. 
     53Both 'lowres' and 'hires' are optional -- It is 
     54possible that they data provider may only have one size of images.  If they're both not there, 
     55the data provider hopefully won't send the structure, but it is a possibility. 
     57The 'lowres' should be somewhere near 128x128, and the 'hires' ones are 
     58something larger, but it's up to the individual data providers.  If they use the last format, 
     59they will specify the size of the browse images in pixels.