Git Product home page Git Product logo

comt-ui's People

Contributors

brianmckenna avatar cgalvarino avatar radomishel avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

Forkers

birdage

comt-ui's Issues

anything vector GFI needs to be u,v

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.

@brandonmayer @brianmckenna @kknee

estuarine_hypoxia

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

now that there are 4 categories, stuff is wrapping strangely

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.

@kknee

need space for timeseries graphs

@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.

image

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.

Handle variable unit conversions

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.

need a spot for legend(s)

@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):

image

It looks like we'll need to do something a bit more solid w/ the eyeball zoom icon while we're at it.

Should Filter by Event and Filter By Model be reactive to selected category?

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

make download link a real link in info popup

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?

Tiling issue?

Looks like not all tiles are being requested. Not sure if this is sciWMS or UI side.

See two SLOSH screenshots as an example.

SS1 - full extent, data extends east into Mississippi:
image

SS2 - zoom in to northern Gulf, data gets cut off in Louisiana
image

clean up of catalog

@bnfish @kknee I think the catalog listing needs a bit of cleanup.

  • The (currently 3) category tabs at the top are off center and look a bit lost.
  • Everything looks like a link. The things that should be links are the layer names. I vote we add some kind of info button per catalog row that will take you to the TDS data source.
  • We may have thumbnails for each catalog hit. Can you create a dummy thumbnail (you pick a nice w x h) for each row?

Ben, if you want to try and map something, stick w/ the 2nd category (inundation) and only map eta or etamax.

Same layer displays two different ways.

Depending on what order you turn layers on and off the same layer displays two different ways. In both screenshots below, the bottom layer is drawing one top. Not sure if this in an interface or backend thing.

Screenshot 1:
image

Screenshot 2:
image

live data causing width issues

@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.

add time span and download to catalog listing

@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.

image

@kknee this is how things look now. Maybe you have an idea of where these 2 new fields could go?

image

filler text / image for empty graph

@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

comt-ui/main.js

Line 432 in e04e974

$('#time-series-graph').html('Click somewhere on the map please!');

inundation_tropical - Hurricane Ike (final only) goal

@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)

  • inundation_tropical_MDL_SLOSH_Hurricane_Ike_final_run_egm3
  • inundation_tropical_UND_ADCIRC_Hurricane_Ike_2D_final_run_with_waves
  • inundation_tropical_UND_ADCIRC_Hurricane_Ike_2D_final_run_without_waves
  • inundation_tropical_UND_ADCIRC_Hurricane_Ike_3D_final_run_with_waves
  • inundation_tropical_UND_ADCIRC_Hurricane_Ike_3D_final_run_without_waves
  • inundation_tropical_UND_SLOSH_Hurricane_Ike_final_run_egl3
  • inundation_tropical_UND_SLOSH_Hurricane_Ike_final_run_egm3
  • inundation_tropical_USF_FVCOM_Hurricane_Ike_2D_final_run_with_waves
  • inundation_tropical_USF_FVCOM_Hurricane_Ike_2D_final_run_without_waves
  • inundation_tropical_USF_FVCOM_Hurricane_Ike_3D_final_run_with_waves
  • inundation_tropical_USF_FVCOM_Hurricane_Ike_3D_final_run_without_waves
  • inundation_tropical_VIMS_SELFE_Hurricane_Ike_2D_final_run_wave_only
  • inundation_tropical_VIMS_SELFE_Hurricane_Ike_2D_final_run_with_waves
  • inundation_tropical_VIMS_SELFE_Hurricane_Ike_2D_final_run_without_waves
  • inundation_tropical_VIMS_SELFE_Hurricane_Ike_3D_final_run_with_waves
  • inundation_tropical_VIMS_SELFE_Hurricane_Ike_3D_final_run_without_waves

ADCIRC 2D runs need u,v

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

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.