asascience-open / comt-ui Goto Github PK
View Code? Open in Web Editor NEWIOOS Coastal and Ocean Modeling Testbed (COMT) user interface
License: GNU General Public License v3.0
IOOS Coastal and Ocean Modeling Testbed (COMT) user interface
License: GNU General Public License v3.0
@bnfish is this you or we need to go back to Lisa?
@bnfish @kknee sorry i forgot about a button. Could you add a Requery button to the left of the Clear button (like assets)?
My end explicitly looks for u,v to know when to try and plot arrows along a line for GFI's. I noticed at least one example of wind (windu,windv or something) that wouldn't fall into my trap. My recommendation is that you rename those on your end to u and v. Otherwise, let me know what the set of names will be that I should look for.
Hopefully this won't be too much trouble. Please don't forget to hide the (which was necessary to get the DataTables working).
When I add the estuarine hypoxia (u,v) vars to map, the zoom level is automatically set to an invalid value and no data (not even the map base layer can be displayed). Is this a ui-problem or something on our side?
@cgalvarino @bnfish @birdage @kknee @brianmckenna
was working previously, now returning nothing
Click on pr_inundation_tropical. And if your screen isn't large, some weird wrapping will occur. And that throws off the data table height.
How about pushing the 2 filters down to their own row? So we'd end up w/ row1 = category and row2 = filters. I think that would leave us room to grow, and it clearly communicates that picking a category is the big boss.
Happens no matter what screen size I have. Maybe after splitting filters onto two lines?
e.g. depth is red in extratropical and teal in tropical. possible to be consistent?
@bnfish @kknee It's time to add getfeatureinfo to the mix so we can get snazzy graphs going.
Let's bring in what we have in place for the asset map.
I need a select box for the active layer + a clear button + a div for the actual chart. Whether or not you want to make the chart vertically resizable (which shrinks the map). I'll leave to you. I would say it's easier not to, but bossman always has his opinion.
Timeseries plot reports an error, no idea if this is UI or sciWMS
I know, I know, not a UI issue...but needs to be field somewhere until there's a place for testbed specfic sciWMS issues
During our next round of updates (after the meeting). We need to deal with the potential for a single variable, like uwind,vwind, to have multiple units.
pop-up when clicking on layer name would be ideal
should that be Oct 2010?
When user clicks on DownLoad Data , or the Info button in the Map Layer list view, no .HTML at end of link so get an error when viewing link, e.g.
http://comt.sura.org/thredds/dodsC/data/comt_1_archive/inundation_tropical/MDL_SLOSH/Hurricane_Ike_final_run_egm3
@bnfish @kknee we need a spot for one legend / layer on the map view. The legends will look something like this, http://comt.sura.org:8080/wms/datasets/inundation_extratropical_UMASS_FVCOM_2007_3D_final_run_without_waves/?ELEVATION=1&LAYERS=xc&TRANSPARENT=TRUE&STYLES=facets_average_jet_0_0.5_node_False&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetLegendGraphic&FORMAT=image%2Fpng&TIME=2007-04-01T00:00:00Z/2007-05-01T00:00:00Z&LAYER=xc.
Vertical legends will not play nicely w/ our layout. How about styling it w/ a rotation and placing it on a newline below layer name? Crude (I chopped off the unit label accidentally):
It looks like we'll need to do something a bit more solid w/ the eyeball zoom icon while we're at it.
@bnfish , the date slider is in the same div as the map, but they each need to be in their own. Can you work some magic?
Not sure if this is a JSON update or a UI update, but here are the details for the datasets currently available. Obviously needs to be flexible as new datasets are added.
Inundation Extratropical:
Events = 2005, 2007, 2010
Models = UMASS_FVCOM, UND_ADCIRC, VIMS_SELFE
Inundation Tropical:
Events = IKE, RITA
Models = MDL_SLOSH, UND_ADCIRC, UND_SLOSH, USF_FVCOM, VIMS_SELFE
SHELF_HYPOXIA
Events = 2005
Models = NOAA_NGOM
I am putting the time span and the data link in the popup. Would be nice to have that link clickable or maybe made to look like the download icon on the catalog page?
Also, things get whack when you have > 1 info open. Maybe they should close whenever you click somewhere outside of the info box?
Important variables (DO, salinity, temp) vary with depth.
@bnfish can we get a 'Depth Slider'? Vertical version of timeslider for now, placed on left side of map
@brandonmayer can we add the elevation dimentions to the json?
@bnfish @kknee I think the catalog listing needs a bit of cleanup.
Ben, if you want to try and map something, stick w/ the 2nd category (inundation) and only map eta or etamax.
less cartoon-y?
@bnfish , would you pull the latest down and see how real data is causing some space / wrapping issues for the picklists?
Also, since the names are SO long, the add to map (+) can scroll out of visibility (horizontally). This seems to be less of an issue w/ the active layers.
FYI the buttons don't apply filtering yet.
not a UI isuse
Checked SST and u,v
@bnfish could you add a download icon as well as somewhere for us to put a time range? Something like earthcube? Although I think the size on earthcube is a bit extreme.
@kknee this is how things look now. Maybe you have an idea of where these 2 new fields could go?
@bnfish I have started hammering away at time series. We need something to fill in the time-series-graph div when there is no active graph. Could you put some kind of stylized text (decent sized gray font) inside that area that is centered vertically and horizontally?
It would only need to be defined here
Line 432 in e04e974
@kknee @brandonmayer @cgalvarino
Creating an issue to track the FINAL datasets for inundation_tropical - Hurricane Ike. This subset is a smaller (eg bounded) set we can realistically have fully functional ASAP and then use the process to fix the rest. Just confusing the bounce around, anything we find here, be it sciwms, catalog or UI should be usable elsewhere.
each dataset MUST have ssh
(may be geoid or reference_datum) and CAN have u,v
, uwind,vwind
and/or hs
If you believe a dataset is complete, check off and comment which variables are present below. If you believe a variable is missing or not functioning, comment as well, just don't check off.
I'm debating ignoring the preliminary datasets for now since half of them are garbage (poor variable names, not complete, etc)
Only showing up for 3D. Std name is different:
2D: water column vertically averaged east/west velocity
3D: water column vertically varying east/west velocity
so maybe use u,v for 3D and uavg, vavg for 2D. Means that @cgalvarino will have to add uavg, vavg as well as uwind, vwind
When zoomed out to the scale of the Gulf of Mexico, the ADCIRC variables looks offset, but the more I zoom in, the better the data lines up.
@bnfish is this you?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.