Digimap from EDINA

Page last modified on 03 March 2016, at 04:56 PM (initially posted on 4 January 2008)

Digimap is a collection of EDINA services that deliver maps and map data of Great Britain to UK tertiary education.

Data is available either to download to use with appropriate application software such as GIS or CAD, or as maps generated by Digimap online. There are a number of collections available, each requiring a separate institutional subscription: Digimap (Ordnance Survey® Collection), Environment Digimap (land cover map data from the Centre for Ecology & Hydrology), Historic Digimap (historic maps from Landmark), Geology Digimap (geological maps & data from the British Geological Survey), Marine Digimap (hydrographic maps & data from SeaZone).

Once subscribed, access is free at the point of use. Some collections also require individual registration.


User Accountability: required

WAYFless URL: http://edina.ac.uk/Login/digimap?idp=xxx
(where xxx is the entity ID of your organisation's IdP)

Please note that WAYFless URLs cannot be guaranteed to remain unchanged over time.

This service is available for subscription to UK HE, FE & research councils through JISC Collections.


1. The only attribute that an identity provider must release for its users to be able to access many services that are licensed for use by everyone at a particular organisation is eduPersonScopedAffiliation. This is a scoped attribute, which might, for example, have the value "member" in scope "uni.ac.uk", often written as:


It is used for the basic authorisation decision: does uni.ac.uk subscribe to the service in question? If so, the user is allowed access. The service provider will maintain its own list of which organisations (scopes) can access its service. For allowed organisations, the federation's Technical Recommendations for Participants indicate that, in HE/FE, users with scoped affiliation values from the set {member, student, staff, faculty, employee} are typically authorised to access content licensed on the basis of the JISC Model Licence, while {affiliate, alum} are not.

While a Shibboleth identity provider can generate eduPersonScopedAffiliation statically by setting the required value in attribute-resolver.xml, this should only be done when it is known that all users are authorised. Otherwise, the value can be picked up from your LDAP / Active Directory as described on the IdP setup page.

Users of other IdP software should check their documentation.

2. Many services can make use of the eduPersonTargetedID attribute. This is a persistent opaque identifier, which enables service personalisation (remembering data about a user over different login sessions) without the service provider knowing who the user is. If the identity provider supplies the eduPersonTargetedID attribute, the session is treated similarly to an Athens personal account. Otherwise, the service's personalisation features (e.g., saved searches) may be disabled, though the service will still function in the same way as with Athens shared accounts. With some services (e.g., Zetoc Alert) this attribute is mandatory. If so, it is marked as "Required/Yes" in the table in Attribute Usage.

For a Shibboleth IdP, generation of eduPersonTargetedID in attribute-resolver.xml is described on the IdP setup page.

Release of eduPersonTargetedID by attribute-filter.xml is described further down the same page.

Users of other IdP software should check their documentation.

8. When a service provider permits or requires individual user registration, they will require the identity provider to present eduPersonTargetedID or eduPersonPrincipalName. This allows logins to be related back to the user's registration details.

NB: in general we recommend the use of eduPersonTargetedID as presentation of eduPersonPrincipalName has implications under the DPA. Configuration of eduPersonTargetedID is described in note 2 above.

9. Some services (including EDINA services which require individual user registration) will only grant access to users from an identity provider marked in the UK federation metadata as offering user accountability as defined in section 6 of the federation's Rules of Membership. Identity providers that offer user accountability are marked by having an <AccountableUsers> element within the <Extensions> element of the IdP's <EntityDescriptor>.