The reason I am favoring table at this point is that it allows rapid scrolling to catch things of interest to the user. I like allowing scrolling followed by typing in the search box to be the most immediate means for traversing bounding boxes to find one you like. Note, you can sort by columns by clicking on column headers. So there may be some fine tuning we can do to find good default sorting.
Since the coverage area already shows the location, we can remove latitude and longitude columns and instead have min of {vertical variable} (geospatial_vertical_min) and max of {vertical variable} (geospatial_vertical_max) displayed.
Finally, one column to display the title or we can display the title in the same column as the reference since link of the reference will take us to the main article.
I'm gonna try to roll something custom to make test wrapping work for each html element besides the thumbnail globe because that's holding this table back from working out of the box.
Since I was away from my computer, I was checking this notebook on my phone. I was surprised to see that you have removed all columns except model variables. Now that I checked it on my computer, it looks beautiful! Anything we can do about smaller screens?
Hello, I hope that it is okay for me to comment here! I noticed that the Alaska.JointInversion_RF+Vph+HV-1.Berg.2020 model will not load in the EMC horizontal slicer, either from this page, or if I download the netCDF and try to upload it.
Thank you! This is a really neat and useful tool!
This particular model appears to be NetCDF-4. Looks like we need to update our reader to ensure it works with NetCDF-4 and then everything should work. We inspect the file format and prevent attempting to render anything if it is not NetCDF-3 "Classic". Thank you for bringing this to our attention. I'm on it! Please let us know whatever other feedback you have so we can make these tools better.
When users concentrate on a particular area and select a region, that means they are more interested in higher resolution for that area. Since all global models covering (~-180 to ~180 longitude) would cover all regions and often they are low resolution, I suggest including a checkbox next to the map for including global models. Users would see global models in the list if they checked that box.