[ZOO-Discuss] [ZOO Project Trac] #3: Filling optional default values issue with GIS GRASS integration

[ZOO Project Trac]

#3: Filling optional default values issue with GIS GRASS integration
----------------------------+-----------------------------------------------
Reporter:  soeren           |        Owner:            
    Type:  defect           |       Status:  closed    
Priority:  major            |    Component:  zoo-kernel
 Version:  1.0              |   Resolution:  fixed     
Keywords:  optional values  |  
----------------------------+-----------------------------------------------
Changes (by djay):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Since [changeset:63 Revision #63], the ZOO-Kernel does not fill the
 default value map of the inputs maps in the following case: it is not
 provided in the request !DataInputs and there is no default value set in
 the zcfg file for this input.

 Nevertheless, it still provides other format informations, which means for
 intance for !LitteralData dataType information and potential UOM. This
 way, from any programming language you are able to test if the value was
 provided (or default valued) or not. For instance from Python using
 {{{"value" in inputs["grass_band_number"]}}} you can check if the value
 was provided in the request or not.

 I think this is similar to what you propose as solution 2. Indeed, even if
 it does not provide specific programming language null value in inputs the
 value is well not defined in any programming languages.

 For ComplexData it would work the same.

 For outputs maps, the NULL value is still set in maps.

 Please, feel free to reopen this ticket if anything goes wrong with
 default value setting.

-- 
Ticket URL: <http://svn.zoo-project.org/trac/ticket/3#comment:1>
ZOO Project Trac <http://www.zoo-project.org/>
Open WPS Platform