"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Minor Tweaks

As at 15 Jan 2005

Generally - it is looking good and behaving well (after a server restart by RobertWoodcock earlier today).

To make a more convincing demonstrator, it would be very nice to have
  1. an All Servers choice as the default on the Add Layer
  2. a canned query for GA

Noted Working

  • Color symbols on the map control panel working nicely.
  • Changing current layers with the "i" button seems robust.
  • Change Query panel allows you to change the query parameters for different queries and refreshes.

Bug - Colour Symbol of Current Layer after Changing Layers

The color symbol next to the current layer button below the map is incorrect after changing layers. The symbol is drawn as a square in the correct colour when you create a new layer. When you click the "i" button to change the current layer, the symbol is redrawn incorrectly.

Bug - Overlapping Layers Disable Mouse Over

This is a cute one.

Say you create a layer for Cu=200ppm from GA. (Pink layer)

Now create another layer for CU=150ppm from GA which will overlay the first one and add many more points. (Blue layer)

If you click the "i" button to enable the Pink layer, mouse-over features has no result.

Now disable the Blue layer so you can see the Pink features - mouse-over works again.

Bug (Server?) - Table of Analyte Values for GA server

The table is now presenting with the coordinate columns missing and so the analyte values appear under the wrong headings. This happens with either clicking on a feature or pressing the current layer button at the bottom of the map. It is probably a server problem with GA.

As at 10 Jan 2005

The color selector on the Add Geochemistry Data is very nice and working - we still need the color of the symbol on the map control panel to be changed to match.

Current Layer

Now that the current layer is clearly indicated (button and color), it is obviously not changing in any sensible manner. I think the current layer should change to be the one with the blue "i" button pushed in?

Deleting Layers

Glad to see the delete functionality added but it needs to be a little less aggressive smile At present it has a column of checkboxes, any one of which is reacted to instantly giving the user no chance to think and easily deleting the wrong layer by mistake.

The chance of error is increased because there's a close set of checkboxes which are persistent and multiply checked (for the active layers) which leads the user to think that checkboxes are not immediate nor dangerous (nor should they be!).

Suggestions:
  1. Simplest for now is replace the delete checkboxes with immediate action trash can icon buttons
  2. Preferred appproach - allow the checkboxes to be multiply checked and have a "Delete Marked" button.

-- AndyDent - 10 Jan 2005

As at 31 Dec 2004

Front Screen

I've noticed that there's an attempt to show a splash screen on the front screen which should be obscuring the entire button set of the normal interface but is actually too short so on a screen of 1200x768 or larger has inactive buttons showing as per the following screenshot.

MCA front Screen Overlap

Add Geochemistry Data

The improved Add Geochemistry Data screen seems to be working and generating a nice default layer name. Probably the biggest usability improvement there would be sorting the list of analytes.

The new Run Query & Add to map button is well-named and positioned appropriately above the Change symbolisation defaults area.

Incorrect Warning if no Service Chosen

There is one minor error in the warning if you forget to choose a service, the error message is You must specify valid values for : URL instead of saying service. I assume this is a by-product of the way your framework functions and is possibly not easy to change. I think it is worth considering in future - the visible label of an entry field should be what's used in warning dialogs. However it is dealt with, at present it is rather confusing.

SVG Style ignored

Specifying a color in the SVG Styling is ignored, blue is always used.

Initial Feedback & Discussion

AndyDent wrote and Main.RobAtkinson initially replied

Giving the User more Context

Show Color as Symbol

Show the colour being used for the styling as the symbol next to the layers (this may require us working together to add a new stylesheet)

This might be possible using CSS as the style syntax is the same, otherwise its a pain. This is quite an interesting exercise to see how symbolisation resources get created, distrubuted, managed, advertised and displayed when there are different "degrees of freedom" for different feature types.

I can easily produce a little stylesheet to do a single tiny SVG that could be used in another SVG area -- AndyDent - 15 Dec 2004

Indicate the active layer

Indicate the active layer by some clear arrow next to the layer itself and copy the symbol next to the Get Geo Data button.

Yep - this is a very good idea and we'll do this. Originally we were planning to set up a single "virtual WFS" so the active layer issue wasnt going to be so big a deal, but with the current paradigm where you can add multiple layers we need to go this route I think.

More feedback from the public demonstration to the CGI people - we discussed this issue and the consensus was that sometimes different layers are very valuable as you can turn them off and on to compare sources -- AndyDent - 15 Dec 2004

Better Name Layer

Show the query summary in the name of the layer (eg: PIRSA au > 5pm).

This can be done - its just part of javascript for the form. The issue is that we are starting to get quite a close coupling between the "query schema" which is totally configurable and the form behaviour. Can hardcode for now, but any thoughts on the way such business rules can be meaningfully bound to the schema - Simon - is this the sort of constraint we should be looking at a different language - OWL-S or Relax-NG to get the richness we need?

I've developed several query engines in the past and my general solution to this issue is that the engine is responsible for generating a readable textual form of the query, not the client -- AndyDent - 15 Dec 2004

||| done : though we havent assumed knowledge of the way the values are used internally - so have just listed the query property values - e.g. Au 5 ppm .

You are right I think that the engine should be responsible for advertising how its going to use the parameters in a query, once we move away from the trivial pure filter case where the query is assumed to be any possible set of object properties(a la WFS 1.0) - some sort of operation eg getFilter(filter,"LABEL"):String

I'd move the Layer Name and Symbolisation underneath the query and unless the user enters their own name as an override, the default name is generated from the query (which is why it should come after the query). This also helps if you can't resize the form as requested below and the least edited stuff (stylesheet) should be last.

Done

Making Life Easier - Query Entry

Require Field Entry

Error-trapping on entry - as discussed for now just require them to enter every field of the query.

We can assume every field is mandatory for now - anything more complex requires some thought, though mandatoryness can be forced XML-schema

Done

Simplify search entry

If we're not going to allow the user to enter comparative searches, remove the "Equals" single-entry popup for arg threshold and rename the label from "arg threshold" to either just "threshold" or "greater or equal to" or just ">="

This is again schema specific - have replaced "Equals" with a ":" -need to brainstorm how we would know the meaning- but I suspectit would have to be decoration of the query schema

1. Remove the "equals" popup for UOM and move the popup directly behind the analyte threshold entry. That way people enter something like 10 ppm in one line.

Again, schema specific. We have a meta language for this we use in our CMS - which is a configurable WFS in a way. The only quick way I can see would be to force something in the naming conventions like paramx_partA and param_partB into the property names so they can be identified as being logically grouped in this way

Set query fields to the last-used value, especiallly when they have a query that failed and want to go back and change just the value

probably do-able, though browsers can sometimes do this. Again, its a little complex becuase I'll need to save an array of values and then match the properties I find with these named values. Just coding though and probably not too much of a hack.

Query all Servers at Once

Make it possible to query all servers at once, for a user who doesn't know the relevant servers (this was asked at the demo).

As mentioned above,I pulled back from this initial concept becuse we needed something to run and I didnt have multiple services to test this against. It absolutelty can be done, but I want to push this into an engineering design phase prior to a production capability.

Simplify style entry

Make it possible for a savvy user to edit the raw SVG style but just have a list of colours or colour picker for normal use.

Yep - should be doable.

Warn on Duplicate Queries

Warn the user when they enter the same query on two different layers

there are many other things possible here - the user may validly have the same query but have it kick in at different scales with different symbology rules, or different links from the map query to a report. Dont want to go here without much more comprehensive analysis of workflows required.

Warn on Duplicate Colours

Warn the user when they use the same colour for two different queries on different layers

ditto

Alphabetic Analyte Code display

from MCAProjectUI

Analytes are currently listed in the order they appear in the XMML dictionaries, and the description not the code is shown...

this could be modified to be, for example

Au (Gold)

or Gold (Au)

etc and ordered in some way. All the presentation is done by an XSL over the dictionaries expressed as an XML Schema document (XSD) - alternatives are possible.

-- RobAtkinson - 06 Dec 2004

SimonCox expressed the opinion that users of this system are going to know that Au is Gold and will be looking for it as Au alphabetically.

Making Life Easier - Map Interaction

I think all the layers should be hotlinks to the equivalent of the Get Geochemistry Data button. The more I play with it, the less having a singular button makes any sense. I think the concept of this relating to an active layer is too obscure and it doesn't enable me going to look at the data in a different layer.

makes sense. Might be a little tricky in practice because there is quite a bit of configuranbility behind that button, and replicating that into the legend which is stylesheet generated would be a nightmare. But we can probably define an interface between the legend and the configurable button and get the legend links to generate simple events, so the configuration of the button incloudes how to interpret these.

Multiple Result Displays

Be able to keep the result table from multiple layers up at the same time.

should be ok - just pop them up into named windows. You move into a very trick area if you want to tile them on the screen - we'll just pop them up located relative to the map click I think.

Better Error Display

The Layer Status which is displayed if you had a bad query and click on the little triangular attention marker is generic - it would help if this included the query that went wrong and more info on the error returned.

these things are possible, but require quite a lot of thought to determine exaclty which engineering realities you want to expose to the user. Needs an analysis and design phase.

Change cursor over the map

Change the cursor to match the selected tool over the map, possibly some help from : http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/cursor.asp

we dont currently do that with the SVG mapper, but we do with the standard one - will look into it

Improving Overall Presentation

supply uom for result normalisation

Feed the requested uom into AnalytePortrayal1.xslt for the table output so different units can be normalised.

should be doable. Will need to pass these as config param - not sure how easy it is at runtime to add params to the stylesheet tag - Trem?

larger results window

Make the popup table of geochem data in a larger window so you don't have to immediately resize it.

yes - will do

Display request on result table

The Geochem Data result should include the service and bounding box as meta information at top

we can pass these in as params - but then all stylesheets will need to use them with a consistent name - thats probably OK

Saveable result table

Is it possible for the Geochem Data result table to be a window-type that is saveable or is that desirable to be discouraged?

it is possible, but adds another workflow - we can put a menu of output formats

I didn't mean anything particularly complicated but the window currently doesn 't have a menu and there's no Save As on the context menu - is this a characteristic of popup windows? -- AndyDent - 15 Dec 2004

If possible, make the overall form large enough that people don't have to scroll the entry form. It is annoying and looks unprofessional to have a forced scrolling form in the middle of a window twice its size. It also makes the feature results hard to read when adding a layer.

you can never tell how many results, or how big the query schema will be, so generically you need this. Its a configurable option for any UI widget to include scrollbars automatically. Have sized it so that fopr the examples used it doesnt scroll, but it will for more complex query schemas ||

Bugs

Add GeoChemistry Data refresh

The Add GeoChemistry Data tab doesn't refresh when the map refreshes, after you click the Add All Features button - it still has the Cancel and Add buttons. It's only when you click to another layer and back that it refreshes.

ok

Clarify & fix View Filter

I have no idea what the View Filter tab is supposed to do - it only ever seems to have the original query filter. Should it be renamed to Active Filter and should it vary its contents to match the current Active Layer query? "Change Query" or something - if you need the ability to edit the params instead of adding a new layer ?

Fine but it also doesn't show details from the active layer but only from the original query, as far as I can tell.

Needs an update event set up for it.

Bad Hotlink

The original layer "PIRSA Geochemical Analyses (Au > 5ppm)" is a hotlink to a missing URL. <javascript:legendpassParamsMetaWin('http://localhost:8881/seegrid/ull');>

Done - is configurable - pointed at GeoChemMetadata

Mouse Over inappropriate reaction

The other tools (eg: Hand) have the same effect as the Info tool when you mouse over a feature - it changes the feature to a silvery dome. I don't think the features should change their display for other than the Info tool.

Done
Topic attachments
I Attachment Action Size Date Who Comment
MCA-frontScreenOverlap2005-01-01.pngpng MCA-frontScreenOverlap2005-01-01.png manage 42.5 K 01 Jan 2005 - 16:38 AndyDent MCA Overlap front screen
Topic revision: r10 - 15 Oct 2010, UnknownUser
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).