Master

'

s Thesis 2006 

FACHHOCHSCHULE

HOCHSCHULE F

U

R

LI Hui 

STUTTGART

TECHNIK

The implementation 

        STUTTGART UNIVERSITY OF APPLIED 

SCIENCES 

In the code structure, after users choose the operation of server list to edit, add, delete 

server,  the 

RMS

  class  was  called  to  store  the  record  storage  which  has  been 

changed. Once the users select one server and ready to connect the server, 

Validate 

the server, get the WMS Head

 class was called to validate the selected server and get 

the HEAD and Content Type from WMS.   

After  inputting  the  XY  coordinate,  GetCapabilities  request  was  send,  and 

Parse  the 

XML file from WMS

 class was called to parse the XML document from WMS, pick 

up the request parameters from the content of XML document which are needed to be 

added in the GetMapRequest URL.   

Once  users  have  set  all  the  needed  values  of  parameters  and  ready  to  send  the 

GetMapRequest, 

Send  GetMapRequest,  validate  the  result

  and 

Justify  the  image 

format

 classes were called to validate the result file which was got from WMS, if it is 

XML Document, these are two possibilities, the first is SVGT file, then go to load the 

SVGT Viewer; the second is XML document that contains the errors description from 

WMS,  when  the  value  of  parameters  was  set  in  invalidate  form  before.  And  if  it  is 

image document, then justifies whether it is PNG format image and loades the raster 

image viewer, otherwise throws one error dialog.   

If  any  processes  mentioned  before  meet  any  unexpected  error, the  error  dialog  class 

was called, and users can jump back to the former interface they have stayed just now.   

The code structure from the developers

'

 point of view: 

41