some small WCS client appearance adjustments

[Peter Baumann]

the WCS client, while very informative, should have a few corrections applied:

• title change "Petascope Web Client" → "rasdaman WCS client"
• uniform color scheme (ie: replace orange by something matching rasdaman)
• formatting should convey when something is a link, eg by underlining (ex: Capabilities coverage list)
• ProcessCoverages: if there are example queries listed these must work. Maybe a simple way to configure this for deployment?
• InsertCoverage: "Use a generated, unique coverage id:" followed by button -> button first, then "let server generate unique coverage id"
• a simple way of configuring that Insert / Delete Coverage are inhibited
• uniform spelling: "ID" vs "id"
• "triming" → "trimming"
• is there an easy way to configure a title to appear top left boldface + large?
• scale factor applied wrong to cell estimate: increasing, instead of decreasing (cf standard)
• Get Coverage: needs some hint/link on how to change coverage selected

[Peter Baumann]

adding:

• After GetCap, GetCoverage is disabled, should be enabled
• add tab entry for Update Coverages

[Peter Baumann]

adding:

• "result will have approximately…" should have an integer result.

after that, can we close it?

[Peter Baumann]

addition:

• in GetCoverage: "triming" → "trimming"
• make sure trimming layout has good linewrap also at limited width
• "The constructed request is" → "GML request", unfolding like GML response elsewhere

[Peter Baumann]

• client should show non-Core request types only after a Cpabilities request, and only those for extensions reported in the Capabilities.
• In case of WCS-T, UpdateCoverages is missing.

[Bang Pham Huu]

It could be change to better

[Bang Pham Huu]

Hi, I also have some requests and I think it could be good for better Petascope Interface, please consider:

1. From the Get Capabilities tab:

→ I think the "Available coverages" could be changed to display the existed coverages in a table instead of a concatenated string (it could be fine with short coverage name but will be inconvenient when user has a lot of inserted coverages which complex name.

2. From the Get Coverage tab, when I test with sample data (mean_summer_airtemp) and not change any value, just click "Download Coverage". A dialog box informed that "Please check your query and remove any error".

→ I think it should have to focus on which parameters or better instruction to know about the error for user could understand (even with the Java exception).

3. From the WCPS query tab which I've experienced, I feel something could be enhanced:

+ The console to type the WCPS too small for large query. It is good if just want to demonstrate some basic query but not good in action when user need complex query. And the right place of Web Page is empty (or filled with a lot of message dialog without necessary), please view in this file ​http://rasdaman.org/attachment/ticket/899/not_good.png.

→ I think the WCPS console should be enlarged to the same side as the output console in the left.

+ Every time the query has error (syntax or structure), a "red" dialog message appear and do not disappear automatically. It is not convenient and could not help really much. And if user query again, another error appears.

→ I think we should have the error console and if has error, a "red" dialog message could appear together with the error written in the error console. And after few seconds, this dialog message should disappear.

This error console will be put below the WCPS console and take a height = current WCPS console.

+ In Firefox, the vertical scroll of output console works good (user can scroll up and down and stay at the position they want), but in Chrome, it always scroll down to the bottom of latest output when user try to scroll up to previous outputs.

+ The Image Example is a good idea but with the "strange coverage" that didn't exist on Database so it is very hard for new users can understand what is the purpose of this parameters or syntax.

→ I think it is nice to have a "small sample database" like mr, rgb and a time series coverage like mean_summer_airtemperature. If these coverages not exist in RASBASE, user could click in a button named "Create Sample Database", and after that, we could take the sample tests from WCPS_testing for user can practice (run and see the results).

[Peter Baumann]

Replying to bphamhuu:

Hi, I also have some requests and I think it could be good for better Petascope Interface, please consider:

1. From the Get Capabilities tab:

→ I think the "Available coverages" could be changed to display the existed coverages in a table instead of a concatenated string (it could be fine with short coverage name but will be inconvenient when user has a lot of inserted coverages which complex name.

I'm not in favor. If we have large amounts of coverages this will rapidly get unwieldy.

2. From the Get Coverage tab, when I test with sample data (mean_summer_airtemp) and not change any value, just click "Download Coverage". A dialog box informed that "Please check your query and remove any error".

good catch - Alex, please try to reproduce.

→ I think it should have to focus on which parameters or better instruction to know about the error for user could understand (even with the Java exception).

I do not understand this sentence well, but it might be about more adequate error messages. If this is the case, it is not the right ticket here, it needs to go into petascope error handling.

3. From the WCPS query tab which I've experienced, I feel something could be enhanced:

+ The console to type the WCPS too small for large query. It is good if just want to demonstrate some basic query but not good in action when user need complex query. And the right place of Web Page is empty (or filled with a lot of message dialog without necessary), please view in this file ​http://rasdaman.org/attachment/ticket/899/not_good.png.

→ I think the WCPS console should be enlarged to the same side as the output console in the left.

what about making it resizable for the user?

+ Every time the query has error (syntax or structure), a "red" dialog message appear and do not disappear automatically. It is not convenient and could not help really much. And if user query again, another error appears.

→ I think we should have the error console and if has error, a "red" dialog message could appear together with the error written in the error console. And after few seconds, this dialog message should disappear.

This error console will be put below the WCPS console and take a height = current WCPS console.

if we adopt this approach then I suggest to just put messages inline where the output appears. Otherwise it is confusing.

+ In Firefox, the vertical scroll of output console works good (user can scroll up and down and stay at the position they want), but in Chrome, it always scroll down to the bottom of latest output when user try to scroll up to previous outputs.

+ The Image Example is a good idea but with the "strange coverage" that didn't exist on Database so it is very hard for new users can understand what is the purpose of this parameters or syntax.

not sure I understand.

→ I think it is nice to have a "small sample database" like mr, rgb and a time series coverage like mean_summer_airtemperature. If these coverages not exist in RASBASE, user could click in a button named "Create Sample Database", and after that, we could take the sample tests from WCPS_testing for user can practice (run and see the results).

This is the purpose of the OGC conformance tests (which will need to be reworked anyway with OGC CIS 1.1 arriving I guess).

[Bang Pham Huu]

This is good even with very long coverage

[Bang Pham Huu]

Find your coverage when has very long and complex name, it is not easy

[Bang Pham Huu]

Thanks for your comments, Prof. Peter.

• It is just some minor interface we can enhance for better experience for user. I will describe why we need a table HTML instead of a long and inconvenient string, you could see: ​http://rasdaman.org/attachment/ticket/899/list_not_seeable.png

compare with ​http://rasdaman.org/attachment/ticket/899/good_list_coverage.png

• There is a problem in (Process Coverages tab) with the "vertical scroll" in the output (with image result displayed here) in Chrome that when user scroll up to view previous result, it will automatically scroll down to bottom (it is annoyed when user could not view anything except the latest query result), in Firefox it works normally.

I think Petascope help people a lot with WCPS query language and it could be enhanced for more friendly (as far as I know, there are not officially WCPS Query language document), so learning from Example is a really good way when user could click and get the result with some basic Explanation about the purpose of query and parameters.

[Alex Toader]

Thank you very much for the feedback! Keep it coming! I plan to fix all the problems next week.

[Peter Baumann]

ok, agreed that the bullet list gives more overview (ie, less need for ctrl-F). If we can scroll the list with a limited-size box, as in the screenshot, then I'm in favour.