CVM Webviewer Development - Revision history

Maechlin at 21:44, 28 July 2020

2020-07-28T21:44:19Z

Maechlin at 21:01, 10 July 2020

2020-07-10T21:01:12Z

Maechlin: /* SCEC CVM Webview Development */

2019-11-15T22:49:46Z

SCEC CVM Webview Development

Maechlin: Created page with "== SCEC CVM Webview Development == Below are notes from SCEC CVM Call on Friday 8 November 2019. The software development group will work with the CXM leads to prioritize thi..."

2019-11-15T22:48:46Z

Created page with "== SCEC CVM Webview Development == Below are notes from SCEC CVM Call on Friday 8 November 2019. The software development group will work with the CXM leads to prioritize thi..."

New page

== SCEC CVM Webview Development ==

Below are notes from SCEC CVM Call on Friday 8 November 2019. The software development group will work with the CXM leads to prioritize this development list.

During this call, the SCEC CVM and CXM groups looked at the prototype CVM web-interface, and the group had comments on Current prototype which is posted at: [http://moho.scec.org/UCVM_web/web/viewer.php SCEC CVM Webviewer Prototype]

# Users would like a map-based interface to the site, so users can select point, lines, regions from the map.
# User’s would like a metadata download for queries that includes the values used in the UCVM query, including dimensions, model name, and settings of UCVM including background models and GTL settings when the query was made.
* We need to develop the metadata format. JSON is a suggested format.
* Include Date/time/UCVM version
* Include username of requestor
* Include which geotechnical layer setting was used in a query.
* It was suggested that we return the command used to query UCVM, to make it easy for users to repeat the query.
# Users want to download both the images, and the data files used to create the plots they request.
* It’s possible they don’t want the plots at all, and only the data.
* Need to describe the data format for any returned queries. Presumably the data format is the UCVM return format.
# To make the site as easy to use as possible, for beginning users, it could provide two modes, a simple option, and an advance option:
* For the Simple Option: “simple/fast” auto resolution.
* For the Advanced Options: Then give “complex/slow” manual resolution for queries including depth spacing for the requested profiles.
# To deal with the issue of long waits, and large data requests, the recommendation is that beyond some mesh-point query count, the web-based requests become non-interactive.
* In this case, the request is processed offline, and the requester gets an email when their job is done.
* This add complexity to the site, requiring both user registration (collect their email), and the need for background processing of requests.
# Users would like to provide a file containing a list of data points (lat,long, elevation/depth) and get back results.
* This will require the users to provide other information about the requested data, such as the model, elevation or depth, to be used in the query. This can be handled by asking the user to specify this information in the webpage when they submit their input file.
# Users would like to request other CVM products, currently not available on the site, such as:
* 3d volumes (mesh)
* Specification of surface defined by Strike-rake-dip values.
* Iso surfaces such as Vs30, Z1.0, Z2.5 or a user-specified Vp, Vs, or rho value
# Users recommended the names of the queries are changed. Suggested labels include: 0D (point), 1D profile, 2D cross section, 2D horizontal plot
# Users would like the site to provide more information about which DEM is used for a query
# Users discussed the issue of how the site supported CVM coverage regions.
* An initial version of the site may be simple and not support tiling. Future versions should support tiling of models
* A map-based interface should help the users understand the coverage regions for models.
* There should be consistency for how “no data”, in the air, and in the water queries are handled.
# The site should support an easy method for users to provide feedback and request new features.
# Developers should measure how long queries take on the site, and the site should provide this information to users, before they submit files.

== Related Entries ==
*[[UCVM]]
*[[CVM-H]]
*[[CVM-S]]
*[[USR]]

← Older revision		Revision as of 21:01, 10 July 2020
Line 1:		Line 1:
		+	== Current UCVM Webviewer ==
		+	*[http://moho.scec.org/UCVM_web/web/viewer.php Webviewer ]
		+
	== SCEC CVM Webview Development ==		== SCEC CVM Webview Development ==

@@ Line 38: / Line 38: @@
 # The site should support an easy method for users to provide feedback and request new features.
 # Developers should measure how long queries take on the site, and the site should provide this information to users, before they submit files.
 == Related Entries ==

@@ Line 7: / Line 7: @@
 # Users would like a map-based interface to the site, so users can select point, lines, regions from the map.
 # User’s would like a metadata download for queries that includes the values used in the UCVM query, including dimensions, model name, and settings of UCVM including background models and GTL settings when the query was made.
-* We need to develop the metadata format. JSON is a suggested format.
+## We need to develop the metadata format. JSON is a suggested format.
-* Include Date/time/UCVM version
+## Include Date/time/UCVM version
-* Include username of requestor
+## Include username of requestor
-* Include which geotechnical layer setting was used in a query.
+## Include which geotechnical layer setting was used in a query.
-* It was suggested that we return the command used to query UCVM, to make it easy for users to repeat the query.
+## It was suggested that we return the command used to query UCVM, to make it easy for users to repeat the query.
 # Users want to download both the images, and the data files used to create the plots they request.
-* It’s possible they don’t want the plots at all, and only the data.
+## It’s possible they don’t want the plots at all, and only the data.
-* Need to describe the data format for any returned queries. Presumably the data format is the UCVM return format.
+## Need to describe the data format for any returned queries. Presumably the data format is the UCVM return format.
 # To make the site as easy to use as possible, for beginning users, it could provide two modes, a simple option, and an advance option:
-* For the Simple Option: “simple/fast” auto resolution.
+## For the Simple Option: “simple/fast” auto resolution.
-* For the Advanced Options: Then give “complex/slow” manual resolution for queries including depth spacing for the requested profiles.
+## For the Advanced Options: Then give “complex/slow” manual resolution for queries including depth spacing for the requested profiles.
 # To deal with the issue of long waits, and large data requests, the recommendation is that beyond some mesh-point query count, the web-based requests become non-interactive.
-* In this case, the request is processed offline, and the requester gets an email when their job is done.
+## In this case, the request is processed offline, and the requester gets an email when their job is done.
-* This add complexity to the site, requiring both user registration (collect their email), and the need for background processing of requests.
+## This add complexity to the site, requiring both user registration (collect their email), and the need for background processing of requests.
 # Users would like to provide a file containing a list of data points (lat,long, elevation/depth) and get back results.
-* This will require the users to provide other information about the requested data, such as the model, elevation or depth, to be used in the query. This can be handled by asking the user to specify this information in the webpage when they submit their input file.
+## This will require the users to provide other information about the requested data, such as the model, elevation or depth, to be used in the query. This can be handled by asking the user to specify this information in the webpage when they submit their input file.
 # Users would like to request other CVM products, currently not available on the site, such as:
-* 3d volumes (mesh)
+## 3d volumes (mesh)
-* Specification of surface defined by Strike-rake-dip values.
+## Specification of surface defined by Strike-rake-dip values.
-* Iso surfaces such as Vs30, Z1.0, Z2.5 or a user-specified Vp, Vs, or rho value
+## Iso surfaces such as Vs30, Z1.0, Z2.5 or a user-specified Vp, Vs, or rho value
 # Users recommended the names of the queries are changed. Suggested labels include: 0D (point), 1D profile, 2D cross section, 2D horizontal plot
 # Users would like the site to provide more information about which DEM is used for a query
 # Users discussed the issue of how the site supported CVM coverage regions.
-* An initial version of the site may be simple and not support tiling. Future versions should support tiling of models
+## An initial version of the site may be simple and not support tiling. Future versions should support tiling of models
-* A map-based interface should help the users understand the coverage regions for models.
+## A map-based interface should help the users understand the coverage regions for models.
-* There should be consistency for how “no data”, in the air, and in the water queries are handled.
+## There should be consistency for how “no data”, in the air, and in the water queries are handled.
 # The site should support an easy method for users to provide feedback and request new features.
 # Developers should measure how long queries take on the site, and the site should provide this information to users, before they submit files.