Search by property

From CSDMS

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Describe length scale and resolution" with value "Length scale: ~10's of meters to ~1000's of km". Since there have been only a few results, also nearby values are displayed.

Showing below up to 51 results starting with #1.

View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)


    

List of results

  • Model:REF-DIF  + (Assumptions: The REF/DIF 1 model, in parabAssumptions:</br>The REF/DIF 1 model, in parabolic form, has a number of assumptions inherent in it and it is necessary to discuss these directly. These assumptions are: </br># Mild bottom slope.</br># Weak nonlinearity.</br># The wave direction is confined to a sector ±70 ◦ to the principal assumed wave direction, due to the use of the minimax wide angle parabolic approximation of Kirby (1986b). parabolic approximation of Kirby (1986b).)
  • Model:GLUDM  + (At the moment the resolution of the input controls the resolution of the output. This is a global model but can be applied to smaller domains.)
  • Model:WBMsed  + (Available datasets are for global and continental domains. Realistic high-res simulations for global scale is 6 arc-min and for continental 3 arc-min. Higher resolution datasets are available for both (e.g. 15 arc-sec for Europe).)
  • Model:GEOMBEST++  + (Cell length - 10 - 100 meters Cell height - 0.01 - 0.5 meters)
  • Model:GEOMBEST++Seagrass  + (Cell length: 10 - 100 m (typically 50 m) Cell height 0.01 - 0.5 m (typically (0.1 m))
  • Model:CarboLOT  + (Cells are approximately 1-1000m in scale; map areas 10-100km on side.)
  • Model:Barrier Inlet Environment (BRIE) Model  + (Coastal barrier ~10-100 km length scales, and ~100 m alongshore resolution. Parameterizations not suitable for small-scale (tidal inlet etc) analyses)
  • Model:RASCAL  + (Code has been most commonly run for 10x5 mCode has been most commonly run for 10x5 m cells (with the long axis parallel to flow) and domain size of 1.27 x 1.86 km. Other scales are possible, but adding additional cells will slow down processing. This model is only designed to simulate mean flows; resolution of fine turbulence structure is not possible with the code.e structure is not possible with the code.)
  • Model:Area-Slope Equation Calculator  + (Computer memory.)
  • Model:GEOMBEST-Plus  + (Constraints: * Cell length - 10 - 100 meters * Cell height - 0.01 - 0.5 meters)
  • Model:BarrierBMFT  + (Cross-shore transect length can extend 10's of km from the ocean barrier shoreface into the mainland. Grid resolution on the barrier is 10 m, and 1 m spacing from the back-barrier marsh to the mainland.)
  • Model:CAM-CARMA  + (Currently there are only initial data sets for 10x15 degrees longitude and latitude. This model is meant for global scale dynamics.)
  • Model:WACCM-EE  + (Currently, 4x5 degree, with 66 vertical levels up to 140 km. Resolution can be increased if neccessary)
  • Model:Avulsion  + (Delta-scale)
  • Model:GSSHA  + (Dependent upon computational power and memory.)
  • Model:Landlab  + (Depends on application/process)
  • Model:ParFlow  + (Depends upon application.)
  • Model:PyDeltaRCM  + (Domain should be 10s of Kms in x and y. Cell spacing should be 10s of meters.)
  • Model:FineSed3D  + (Domain should be large enough to resolve the bottom boundary layer, meanwhile, the grid resolution should be fine enough to resolve all the essential turbulence scales.)
  • Model:Kirwan marsh model  + (Domain size is 3 km by 3 km, grid cell is 5 m by 5m.)
  • Model:CruAKTemp  + (Downsampled from original data to 10 km by 10 km resolution)
  • Model:CosmoLand  + (Drainage basin size controls the length of the model runs. Cell size should not be increased to shorten model runs.)
  • Model:ROMS  + (Estuary, regional, and basin scales. There are couple of global applications.)
  • Model:ChesROMS  + (Estuary, regional, and basin scales. There are couple of global applications.)
  • Model:CBOFS2  + (Estuary, regional, and basin scales. There are couple of global applications.)
  • Model:UMCESroms  + (Estuary, regional, and basin scales. There are couple of global applications.)
  • Model:GPM  + (From a few hundred m to a few hundred Km)
  • Model:TAo  + (From continental to regional scale (>50 km). Up to a few thousand cells are well handled.)
  • Model:ISSM  + (From hundreds of meters to thousands of kilometers (constraints are mainly HEC-related).)
  • Model:GSFLOW-GRASS  + (GSFLOW is intended for modeling catchments from the km-scale to the 100s-of-km scale)
  • Model:Caesar  + (Has been applied to catchments ranging from 1km^2 to 500km^2, at grid resolutions ranging from 1m to 50m.)
  • Model:GOLEM  + (Has been used on scales from small (few km2) watersheds to sub-continental areas.)
  • Model:WEPP  + (Hillslope simulations are recommended for Hillslope simulations are recommended for lengths not greatly exceeding 100 meters. Watershed simulations should not exceed areas above 260 hectares. Larger areas can be simulated for hillslope spatial analyses only - but the channel processes will not be accurate at these larger scales.ll not be accurate at these larger scales.)
  • Model:Subside  + (Horizontal resolution is typically 100s of meters)
  • Model:Inflow  + (Horizontal resolution is typically 10s of meters)
  • Model:Sakura  + (Horizontal resolution is typically 10s of meters)
  • Model:FVshock  + (Hundreds of Km (the reach of a river).)
  • Model:HydroTrend  + (HydroTrend should be applied to river larger than 100km; and basins smaller than 75000km2.)
  • Model:Pllcart3d  + (In its current state, the code is restricted to low Reynolds number and Peclet number of order 1000.)
  • Model:CHILD  + (In principle, the model can address spatiaIn principle, the model can address spatial scales ranging from gullies and small (~1km2) catchments to mountain ranges, as long as setup and parameters are chosen appropriately. Resolutions greater than about 10,000 nodes normally require significant computation time.ally require significant computation time.)
  • Model:Quad  + (In the field, this model is applicable in the range of landscape and regional scales (~10-100km). It has also been successfully applied at the scale of physical experiments.)
  • Model:IDA  + (Increasing the number of processors should allow larger/higher resolution landscapes to be considered.)
  • Model:RivMAP  + (Input channel masks can be arbitrary resolution)
  • Model:HexWatershed  + (It is best performance for high resolution (<100m) simulation. With the version 3.0, coarser resolution is supported through stream burning feature.)
  • Model:TOPOG  + (It is intended for application to small catchments (up to 10 km2, and generally smaller than 1 km2).)
  • Model:Morphodynamic gravel bed  + (It's a reach scale. It is applied to 30km downstream of the Buech river. However, if dx is changed upward/downward, the time step should be adjusted.)
  • Model:CEM  + (Kilometers to hundreds of kilometers. Numerically, the model can be discretized with much smaller spatial resolution. However, the assumptions of approximately shore-parallel shoreface contours becomes unreasonable at scales smaller than kilometers.)
  • Model:LISFLOOD  + (LISFLOOD is grid-based, and applications so far have employed grid cells of as little as 100 metres (for medium-sized catchments), to 5,000 metres for modelling the whole of Europe and up to 0.1° (around 10 km) for modelling on a global scale.)
  • Model:CASCADE  + (Large scale (100 km+) model, suitable for orogenic scale modeling but could easily be adapted)
  • Model:SPACE  + (Length scale should be reach or larger (~100m and up). Run time depends on grid size and resolution.)
  • Model:TUGS  + (Length varies, resolution is on the order of several channel width (i.e., 1D model produces only reach-averaged results).)
  • Model:GNE  + (Limited by resolutn of input & river systems data; basins < 20,000 km2 currently poorly represented)
  • Model:DeltaClassification  + (Methods has been applied to data set of 100's of individual delta islands derived from Landsat satellite data (30-60m resolution).)
  • Model:Icepack  + (Minimum ~50m in x, maximum hundreds of kilometers)
  • Model:FuzzyReef  + (Model does not place any spatial constraints.)
  • Model:River Temperature Model  + (Model is 1D, we have used it over a x-section of a floodplain with varying flood inundation depth and durations.)
  • Model:DeltaSIM  + (Model is intended to generate stratigraphy for 2D profiles of large deltas (100's of km's))
  • Model:Princeton Ocean Model (POM)  + (Model used for grid size ranging from ~1m to 1000km)
  • Model:1D Hillslope MCMC  + (Model uses a fixed hillslope length of 30 m constrained from topographic measurements.)
  • Model:Lake-Permafrost with Subsidence  + (Near surface, length scale should be 5-10 cm if subsidence occurring. Deeper in permafrost, 1+ m okay.)
  • Model:NearCoM  + (Nearshore regions from shoreline to 10 meter water depth. Model resolution depends on specific modules.)
  • Model:SNAC  + (No inherent length scale or resolution as long as the continuum hypothesis is satisfied. A practical constraint on length scale and resolution is computational cost.)
  • Model:CarboCAT  + (No intrinsic constraints)
  • Model:IceFlow  + (No longitudinal coupling, not full Stokes)
  • Model:MARSSIM V4  + (None except elapsed time and memory limits.)
  • Model:Demeter  + (Output is typically in a 0.05degree resolution)
  • Model:Marsh column model  + (Point on marsh surface, depth of modeled column can extend to 10s of meters. Sub cm vertical resolution.)
  • Model:TopoFlow  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Channels-Diffusive Wave  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Channels-Dynamic Wave  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Channels-Kinematic Wave  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Diversions  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Infiltration-Green-Ampt  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Infiltration-Smith-Parlange  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Meteorology  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Snowmelt-Degree-Day  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Snowmelt-Energy Balance  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Saturated Zone-Darcy Layers  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Evaporation-Read File  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Evaporation-Energy Balance  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Evaporation-Priestley Taylor  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:TopoFlow-Infiltration-Richards 1D  + (Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.)
  • Model:Hilltop and hillslope morphology extraction  + (Requires high resolution (1 m LiDAR) topographic data.)
  • Model:GEOtop  + (Resolution is limited by RAM. Processes however are parametrized at a few square meter scale.)
  • Model:Bedrock Fault Scarp  + (Resolution on order of one to a few meters. Domain length grows over time, reaching order tens to hundreds of meters long.)
  • Model:SBEACH  + (SBEACH is a beach profile evolution model. The model domain should extend from the landward limit of wave run-up offshore to the depth of closure.)
  • Model:SWAN  + (SWAN can be used on any scale relevant forSWAN can be used on any scale relevant for wind generated surface gravity waves. However, SWAN is specifically designed for coastal applications that should actually not require such flexibility in scale. The reasons for providing SWAN with such flexibility are:</br></br>* to allow SWAN to be used from laboratory conditions to shelf seas and</br>* to nest SWAN in the WAM model or the WAVEWATCH III model which are formulated in terms of spherical coordinates.mulated in terms of spherical coordinates.)
  • Model:OTTER  + (Sediment transport models can become unstable and limit computational efficiency.)
  • Model:PHREEQC  + (See 'Description of Input and Examples for PHREEQC Version 3 - A computer program for speciation, batch-reaction, one-dimensional transport, and inverse geochemical calculations'.)
  • Model:WRF-Hydro  + (See WRF-Hydro Technical Description https://ral.ucar.edu/projects/wrf_hydro/technical-description-user-guide)
  • Model:SPHYSICS  + (See manual)
  • Model:FwDET  + (See: Version 2.0: Cohen et al. (2019), TheSee:</br>Version 2.0: Cohen et al. (2019), The Floodwater Depth Estimation Tool (FwDET v2.0) for Improved Remote Sensing Analysis of Coastal Flooding. Natural Hazards and Earth System Sciences (NHESS)</br> </br>Version 1.0: Cohen, S., G. R. Brakenridge, A. Kettner, B. Bates, J. Nelson, R. McDonald, Y. Huang, D. Munasinghe, and J. Zhang (2017), Estimating Floodwater Depths from Flood Inundation Maps and Topography. Journal of the American Water Resources Association (JAWRA):1–12. Water Resources Association (JAWRA):1–12.)
  • Model:SimClast  + (SimClast can theoretically be used on a leSimClast can theoretically be used on a length scale upwards of 20 kms, the upper limit is dependant on memory and processing restrictions. Typical length scales vary from 25 to 500 km. The highest resolution is mainly dependant on the use of intracellular fluvial deposition, as described in Dalman & Weltje (2008) this restricts the minimum cell size to 4 kms. Recent addition of floodplain process reduces this to 500 m.n of floodplain process reduces this to 500 m.)
  • Model:SISV  + (Since we are doing DNS, we are restricted to low Reynolds numbers. Up to ~50,000 or possibly higher but very slow.)
  • Model:Kudryavtsev Model  + (Solutions are generated for a 1D vertical column. When input data are gridded, maps of 1D vertical columns can be made.)
  • Model:MCPM  + (Spatial resolution 0.1-1 m Cross section generally 100 m wide)
  • Model:CoastMorpho2D  + (Spatial resolution from 1 m to 1 km Spatial extent up to hundreds of km)
  • Model:HydroPy  + (Spatial resolution is determined from the auxiliary data and meteorological forcing)
  • Model:MarshPondModel  + (Spatial resolution of 1 m to simulate small ponds)
  • Model:Shoreline  + (Spatial resolution of coastline is typically 1 to 50 meters.)