Querystring

Simplistic integration can be quickly achieved using a querystring. Parameters passed in can control how Dekho starts up, and Dekho can call a “callback” URL to pass information back.

 

The querystring allows Dekho to be started at a particular location, with a particular selection, etc. This is also useful when Dekho is running in simple or workflow modes.

 

The following URL starts Dekho:

http://localhost:8080/Dekho?map=1&x=331809.928&y=5818278.314&distance=100

§ on map number 1 (the mapid in the Dekho configuration database)

§ at the x,y specified

§ with the distance specified visible around the x,y.

 

The following URL starts Dekho:

http://localhost:8080/Dekho?externalapplication=systemx&externallayer=property&externalids=75611,88371

§ and pass the two ids through the integration query defined for systemx and property (direction External System to Dekho),

§ features are selected and

§ features are zoomed to

 

The following URL starts Dekho

http://localhost:8080/Dekho?integrationqueryname=queryname&externalids=75611,88371 

§ and pass the two ids through the integration query defined by queryname,

§ features are selected and

§ features are zoomed to

 

The following URL starts Dekho:

http://localhost:8080/Dekho?integrationapplication=applicationname&externalids=75611,88371

§ and pass the two ids through all the integration queries defined by applicationname,

§ features are selected and

§ features are zoomed to

 

The following URL starts Dekho:

http://localhost:8080/Dekho?bookmark=bookmarkname

§ and pass in the bookmark name of a previously saved bookmark

§ the resulting bookmark is loaded, including selected features, markup, extents etc.

 

The following URL starts Dekho:

http://localhost:8080/Dekho?queryid=12&queryvalues=12345|Main||Melbourne

§ run a specified search query with the specified input and

§ display the results.

The queryid is the id representing the search query (available when editing the query in the Admin interface), the queryvalues are the values that will be input to the user input fields, the user input for the search query. The queryvalues are delimited (separated) by a single pipe character |, a double pipe character || indicates no value, the example is passing through 3 out of 4 values, skipping the third value. When passing in a query id there is the option of including a map id. If no map id is passed in then Dekho will start with the first map it finds that is associated with the query id. When a map id is included it will start Dekho with that map in addition to the above display results. See the first URL example on how to include a map id.

 

The following URL starts Dekho:

http://localhost:8080/Dekho?externalapplication=systemx&externallayer=property&externalids=75611,88371&externalcontextid=ABCDEF&callback=http://bigiron/bigapp

§ and pass the two ids through the integration query defined for systemx and property (direction External System to Dekho).

§ The resulting features are selected and zoomed to.

§ When the user clicks the Return to Workflow tool, the selection is passed through the integration query defined for systemx and property (direction Dekho to External System), the callback URL supplied is suffixed with the supplied externalcontextid, external application, external layer and ids resulting from the integration query, and then invoked.

§ For example, the URL

http://bigiron/bigapp?externalcontextid=ABCDEF&externalapplication=systemx&externallayer=property&externalids=123,456,789

would be invoked. This provides a simple way of passing a GIS selection back to an application.

 

More sophisticated integration is achievable using JavaScript and calling the Dekho web services directly. This should always be considered the better option, as it provides a much better user experience, and better architecture. These are described below.


External Interface