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 2 and therefore purchased catchment and point descriptors can be exported in xml format & loaded directly into the software. ReFH can be purchased from Wallingford HydroSolutions.
With the release of the BFIHOST19 descriptor a new set of exports was added to the FEH Web Service incorporating this new descriptor. The 'Descriptors for ReFH2.3+ (XML)' are required to use the ReFH2.3 model. The 'Descriptors for ReFH2.2 (XML)' can still be used in ReFH2, but use of this data excludes the new functionality available in the ReFH2.3 model.
The new export files are available for new and existing purchases of catchment and point data.
The ReFH technical guide and supporting science reports detail the full scope of the ReFH 2 software.
An organisational account allows 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. Catchments or points bought by one member of the organisation are be visible to all the organisation’s members. This encourages collaboration and avoids duplicated purchases.
The map displays an additional layer to show or hide organisational purchases, distinguishing them from data purchased by the current user.
One or more users are designated ‘lead users’ for the organisation, responsible for purchasing credits and allocating them to users. Credits are allocated on a flexible quota basis that allows 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 shows 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.
Bulk credit purchases for 10,000 or above payment must be paid via purchase order.
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.