Once a catchment has been purchased it remains associated with your account granting you perpetual access to the data above.
In contrast to an entire catchment, a point is a single location on the map accurate to 1m. With a point you get
The FEH99 DDF parameters (C, D1..3, E & F) are not available for points
Once a point has been purchased it remains associated with your account granting you perpetual access to the data above.
The FEH Web Service has been designed to be compatible with ReFH, versions 2.1 and upwards, and therefore purchased catchment descriptors can be exported in.xml format & loaded directly into the software.
To process point data, version 2.2 or higher of ReFH is required.
ReFH can be bought from Wallingford HydroSolutions.
The FEH Web Service provides the rainfall depths for given durations and return periods for the FEH1999 and FEH2013 models for a catchment together with a comprehensive suite of catchment descriptors. ReFH 2 allow you to interpret these data through the Revitalised Flood Hydrograph (ReFH) model, and estimate design flood hydrographs for catchment application in both rural and urbanised catchments using the latest methods which draw on both the FEH1999 and FEH2013 rainfall models. The technical guidance report details the full scope of the ReFH software. The FEH2013 rainfall model is a significant advance over the original FEH1999 rainfall model and ReFH 2 has been calibrated to use either model. Previous versions of ReFH (ReFH1 and the ReFH spreadsheet) are not compatible with the FEH2013 rainfall model.
An organisational account will allow you to share a pool of credits among all the users in your organisation, simplifying both the credit purchasing process, expanding the possibility of bulk credit discounts, and giving you greater oversight of how those credits are subsequently used. The key features are the ability to assign one or more ‘lead users’ for the organisation, responsible for purchasing credits and allocating them to users. Credit allocation will operate on a flexible quota basis that will allow lead users either to ringfence credits exclusively for certain users, or to adopt a more efficient, non-exclusive, pooled approach, or a combination of the two.
A usage report showing the lead user(s) which point and catchments have been exchanged for credits, by whom, and when. These reports can be exported to Excel for integration with your existing project billing tools. A tag field for each purchased catchment or point supplements the description field. These can, for example, be used for project/team codes. These will appear on the reports (above) allowing credit expenditure to be costed to projects or teams. Catchments or points bought by one member of the organisation will be visible to all the organisation’s members. This encourages collaboration and avoids duplicated purchases. There will be an added layer to show or hide organisational purchases, distinguishing them from data purchased by the current user.
If you place orders of less than 10,000 credits, these credits will not expire. Credits that are purchased in blocks above this threshold at the higher discount bands (see the pricing page) expire after one year. See also the bulk order purchasing page.