Summary: Amyloid A4 N-terminal heparin-binding

Pfam includes annotations and additional family information from a range of different sources. These sources can be accessed via the tabs below.

Wikipedia: Growth factor-like domain
Pfam
InterPro

This is the Wikipedia entry entitled "Growth factor-like domain". More...

The Wikipedia text that you see displayed here is a download from Wikipedia. This means that the information we display is a copy of the information from the Wikipedia database. The button next to the article title ("Edit Wikipedia article") takes you to the edit page for the article directly within Wikipedia. You should be aware you are not editing our local copy of this information. Any changes that you make to the Wikipedia article will not be displayed here until we next download the article from Wikipedia. We currently download new content on a nightly basis.

Does Pfam agree with the content of the Wikipedia entry ?

Pfam has chosen to link families to Wikipedia articles. In some case we have created or edited these articles but in many other cases we have not made any direct contribution to the content of the article. The Wikipedia community does monitor edits to try to ensure that (a) the quality of article annotation increases, and (b) vandalism is very quickly dealt with. However, we would like to emphasise that Pfam does not curate the Wikipedia entries and we cannot guarantee the accuracy of the information on the Wikipedia page.

Editing Wikipedia articles

Before you edit for the first time

Wikipedia is a free, online encyclopedia. Although anyone can edit or contribute to an article, Wikipedia has some strong editing guidelines and policies, which promote the Wikipedia standard of style and etiquette. Your edits and contributions are more likely to be accepted (and remain) if they are in accordance with this policy.

You should take a few minutes to view the following pages:

How your contribution will be recorded

Anyone can edit a Wikipedia entry. You can do this either as a new user or you can register with Wikipedia and log on. When you click on the "Edit Wikipedia article" button, your browser will direct you to the edit page for this entry in Wikipedia. If you are a registered user and currently logged in, your changes will be recorded under your Wikipedia user name. However, if you are not a registered user or are not logged on, your changes will be logged under your computer's IP address. This has two main implications. Firstly, as a registered Wikipedia user your edits are more likely seen as valuable contribution (although all edits are open to community scrutiny regardless). Secondly, if you edit under an IP address you may be sharing this IP address with other users. If your IP address has previously been blocked (due to being flagged as a source of 'vandalism') your edits will also be blocked. You can find more information on this and creating a user account at Wikipedia.

If you have problems editing a particular page, contact us at pfam-help@sanger.ac.uk and we will try to help.

Contact us

The community annotation is a new facility of the Pfam web site. If you have problems editing or experience problems with these pages please contact us.

Growth factor-like domain Edit Wikipedia article

Amyloid precursor N-terminal

The GFLD region of amyloid precursor protein

Identifiers

Symbol

APP_CU_bd

Available protein structures:
Pfam	structures
PDB	RCSB PDB; PDBe
PDBsum	structure summary

A growth factor-like domain (GFLD) is a protein domain structurally related to epidermal growth factor, which has a high binding affinity for the epidermal growth factor receptor. As structural domains within larger proteins, GFLD regions commonly bind calcium ions. A subtype present in the N-terminal region of the amyloid precursor protein is a member of the heparin-binding class of GFLDs and may itself have growth factor function, particularly in promoting neuronal development.

[edit] References

Rossjohn J, Cappai R, Feil SC, Henry A, McKinstry WJ, Galatis D, Hesse L, Multhaup G, Beyreuther K, Masters CL, Parker MW. (1999). Crystal structure of the N-terminal, growth factor-like domain of Alzheimer amyloid precursor protein. Nat Struct Biol 6(4):327-31.

This protein-related article is a stub. You can help Wikipedia by expanding it.

This page is based on a Wikipedia article. The text is available under the Creative Commons Attribution/Share-Alike License.

This tab holds the annotation information that is stored in the Pfam database. As we move to using Wikipedia as our main source of annotation, the contents of this tab will be gradually replaced by the Wikipedia tab.

Amyloid A4 N-terminal heparin-binding Provide feedback

This N-terminal domain of APP, amyloid precursor protein, is the heparin-binding domain of the protein. this region is also responsible for stimulation of neurite outgrowth. The structure reveals both a highly charged basic surface that may interact with glycosaminoglycans in the brain and an abutting hydrophobic surface that is proposed to play an important functional role such as in dimerisation or ligand-binding. Structural similarities with cysteine-rich growth factors, taken together with its known growth-promoting properties, suggest the APP N-terminal domain could function as a growth factor in vivo [1].

Literature references

Rossjohn J, Cappai R, Feil SC, Henry A, McKinstry WJ, Galatis D, Hesse L, Multhaup G, Beyreuther K, Masters CL, Parker MW;, Nat Struct Biol. 1999;6:327-331.: Crystal structure of the N-terminal, growth factor-like domain of Alzheimer amyloid precursor protein. PUBMED:10201399 EPMC:10201399

External database links

PANDIT:	PF02177
Pseudofam:	PF02177
SCOP:	1mwp
SMART:	A4_EXTRA
SYSTERS:	APP_N
Transporter classification:	1.C.50

This tab holds annotation information from the InterPro database.

InterPro entry IPR015849

Amyloid-beta precursor protein (APP, or A4) is associated with Alzheimer's disease (AD), because one of its breakdown products, amyloid-beta (A-beta), aggregates to form amyloid or senile plaques [PUBMED:16301322, PUBMED:16364896]. Mutations in APP or in proteins that process APP have been linked with early-onset, familial AD. Individuals with Down's syndrome carry an extra copy of chromosome 21, which contains the APP gene, and almost invariably develop amyloid plaques and Alzheimer's symptoms.

APP is important for the neurogenesis and neuronal regeneration, either through the intact protein, or through its many breakdown products [PUBMED:16406235]. APP consists of a large N-terminal extracellular region containing heparin-binding and copper-binding sites, a short hydrophobic transmembrane domain, and a short C-terminal intracellular domain. The N-terminal region is similar in structure to cysteine-rich growth factors and appears to function as a cell surface receptor, contributing to neurite growth, neuronal adhesion, axonogenesis and cell mobility [PUBMED:16406235]. APP acts as a kinesin I membrane receptor to mediate the axonal transport of beta-secretase and presenilin 1. The N-terminal domain can regulate neurite outgrowth through its binding to heparin and collagen I and IV, which are components of the extracellular matrix. APP is also coupled to apoptosis-inducing pathways, and is involved in copper homeostasis/oxidative stress through copper ion reduction, where copper-metallated APP induces neuronal death [PUBMED:12611883]. The C-terminal intracellular domain appears to be involved in transcription regulation through protein-protein interactions. APP can promote transcription activation through binding to APBB1/Tip60, and may bind to the adaptor protein FE65 to transactivate a wide variety of different promoters.

APP can be processed by different sets of enzymes:

In the non-amyloidogenic (non-plaque-forming) pathway, APP is cleaved by alpha-secretase to yield a soluble N-terminal sAPP-alpha (neuroprotective) and a membrane-bound CTF-alpha. CTF-alpha is broken-down by presenilin-containing gamma-secretase to yield soluble p3 and membrane-bound AICD (nuclear signalling).
In the amyloidogenic pathway (plaque-forming), APP is broken down by beta-secretase to yield soluble sAPP-beta and membrane-bound CTF-beta. CTF-beta is broken down by gamma-secretase to yield soluble amyloid-beta and membrane-bound AICD. Amyloid-beta is required for neuronal function, but can aggregate to form amyloid plaques that seem to disrupt brain cells by clogging points of cell-cell contact.

This entry represents a heparin-binding domain found at the N-terminal of the extracellular domain, which is itself found at the N-terminal of amyloidogenic glycoproteins such as amyloid-beta precursor protein (APP, or A4). The core of the heparin-binding domain has an unusual disulphide-rich fold, consisting of a beta-x-alpha-beta-loop-beta topology [PUBMED:10201399].

More information about these protein can be found at Protein of the Month: Amyloid-beta Precursor Protein [PUBMED:].

Gene Ontology

The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.

Molecular function

heparin binding (GO:0008201)

Domain organisation

Below is a listing of the unique domain organisations or architectures in which this domain is found. More...

Loading domain graphics...

Alignments

We store a range of different sequence alignments for families. As well as the seed alignment from which the family is built, we provide the full alignment, generated by searching the sequence database using the family HMM. We also generate alignments using four representative proteomes (RP) sets, the NCBI sequence database, and our metagenomics sequence database. More...

There are various ways to view or download the sequence alignments that we store. We provide several sequence viewers and a plain-text Stockholm-format file for download.

Alignment types

We make a range of alignments for each Pfam-A family:

seed: the curated alignment from which the HMM for the family is built
full: the alignment generated by searching the sequence database using the HMM
RP15/RP35/RP55/RP75: Representative Proteomes (RPs) at 15%, 35%, 55% and 75% co-membership thresholds
NCBI: alignment generated by searching the NCBI sequence database using the family HMM
meta: alignment generated by searching the metagenomics sequence database using the family HMM

Viewing

You can see the alignments as HTML or in three different sequence viewers:

jalview: a Java applet developed at the University of Dundee. You will need Java installed before running jalview
HTML: an HTML page showing the whole alignment.Please note: full Pfam alignments can be very large. These HTML views are extremely large and often cause problems for browsers. Please use either jalview or the Pfam viewer if you have trouble viewing the HTML version
PP/Heatmap: an HTML-based representation of the alignment, coloured according to the posterior-probability (PP) values from the HMM. As for the standard HTML view, heatmap alignments can also be very large and slow to render.
Pfam viewer: an HTML-based viewer that uses DAS to retrieve alignment fragments on request

Reformatting

You can download (or view in your browser) a text representation of a Pfam alignment in various formats:

Selex
Stockholm
FASTA
MSF

You can also change the order in which sequences are listed in the alignment, change how insertions are represented, alter the characters that are used to represent gaps in sequences and, finally, choose whether to download the alignment or to view it in your browser directly.

Downloading

You may find that large alignments cause problems for the viewers and the reformatting tool, so we also provide all alignments in Stockholm format. You can download either the plain text alignment, or a gzipped version of it.

View options

We make a range of alignments for each Pfam-A family. You can see a description of each above. You can view these alignments in various ways but please note that some types of alignment are never generated while others may not be available for all families, most commonly because the alignments are too large to handle.

	Seed (15)	Full (356)	Representative proteomes				NCBI (317)	Meta (3)
	Seed (15)	Full (356)	RP15 (20)	RP35 (28)	RP55 (61)	RP75 (114)	NCBI (317)	Meta (3)
Jalview	View	View	View	View	View	View	View	View
HTML	View	View	View	View	View	View
PP/heatmap	₁	View	View	View	View	View
Pfam viewer	View	View

¹Cannot generate PP/Heatmap alignments for seeds; no PP data available

Key: available, not generated, — not available.

Format an alignment

	Seed (15)	Full (356)	Representative proteomes				NCBI (317)	Meta (3)
	Seed (15)	Full (356)	RP15 (20)	RP35 (28)	RP55 (61)	RP75 (114)	NCBI (317)	Meta (3)
Alignment:
Format:
Order:	Tree Alphabetical
Sequence:	Inserts lower case All upper case
Gaps:
Download/view:	Download View

Download options

We make all of our alignments available in Stockholm format. You can download them here as raw, plain text files or as gzip-compressed files.

	Seed (15)	Full (356)	Representative proteomes				NCBI (317)	Meta (3)
	Seed (15)	Full (356)	RP15 (20)	RP35 (28)	RP55 (61)	RP75 (114)	NCBI (317)	Meta (3)
Raw Stockholm	Download	Download	Download	Download	Download	Download	Download	Download
Gzipped	Download	Download	Download	Download	Download	Download	Download	Download

You can also download a FASTA format file containing the full-length sequences for all sequences in the full alignment.

External links

MyHits provides a collection of tools to handle multiple sequence alignments. For example, one can refine a seed alignment (sequence addition or removal, re-alignment or manual edition) and then search databases for remote homologs using HMMER3.

HMM logo

HMM logos is one way of visualising profile HMMs. Logos provide a quick overview of the properties of an HMM in a graphical form. You can see a more detailed description of HMM logos and find out how you can interpret them here. More...

Trees

This page displays the phylogenetic tree for this family's seed alignment. We use FastTree to calculate neighbour join trees with a local bootstrap based on 100 resamples (shown next to the tree nodes). FastTree calculates approximately-maximum-likelihood phylogenetic trees from our seed alignment.

Note: You can also download the data file for the tree.

Curation and family details

This section shows the detailed information about the Pfam family. You can see the definitions of many of the terms in this section in the glossary and a fuller explanation of the scoring system that we use in the scores section of the help pages.

Curation

Seed source:

Alignment kindly provided by SMART

Previous IDs:

A4_EXTRA;

Type:

Domain

Author:

SMART

Number in seed:

15

Number in full:

356

Average length of the domain:

98.20 aa

Average identity of full alignment:

60 %

Average coverage of the sequence by the domain:

14.97 %

HMM information

HMM build commands:

build method: hmmbuild -o /dev/null HMM SEED

search method: hmmsearch -Z 23193494 -E 1000 --cpu 4 HMM pfamseq

Model details:

Parameter	Sequence	Domain
Gathering cut-off	22.1	21.6
Trusted cut-off	22.1	31.9
Noise cut-off	19.7	21.5

Model length:

102

Family (HMM) version:

11

Download:

download the raw HMM for this family

Species distribution

Sunburst
Tree

Sunburst controls

Show

This visualisation provides a simple graphical representation of the distribution of this family across species. You can find the original interactive tree in the adjacent tab. More...

This chart is a modified "sunburst" visualisation of the species tree for this family. It shows each node in the tree as a separate arc, arranged radially with the superkingdoms at the centre and the species arrayed around the outermost ring.

How the sunburst is generated

The tree is built by considering the taxonomic lineage of each sequence that has a match to this family. For each node in the resulting tree, we draw an arc in the sunburst. The radius of the arc, its distance from the root node at the centre of the sunburst, shows the taxonomic level ("superkingdom", "kingdom", etc). The length of the arc represents either the number of sequences represented at a given level, or the number of species that are found beneath the node in the tree. The weighting scheme can be changed using the sunburst controls.

In order to reduce the complexity of the representation, we reduce the number of taxonomic levels that we show. We consider only the following eight major taxonomic levels:

superkingdom
kingdom
phylum
class
order
family
genus
species

Colouring and labels

Segments of the tree are coloured approximately according to their superkingdom. For example, archeal branches are coloured with shades of orange, eukaryotes in shades of purple, etc. The colour assignments are shown under the sunburst controls. Where space allows, the name of the taxonomic level will be written on the arc itself.

As you move your mouse across the sunburst, the current node will be highlighted. In the top section of the controls panel we show a summary of the lineage of the currently highlighed node. If you pause over an arc, a tooltip will be shown, giving the name of the taxonomic level in the title and a summary of the number of sequences and species below that node in the tree.

Anomalies in the taxonomy tree

There are some situations that the sunburst tree cannot easily handle and for which we have work-arounds in place.

Missing taxonomic levels

Some species in the taxonomic tree may not have one or more of the main eight levels that we display. For example, Bos taurus is not assigned an order in the NCBI taxonomic tree. In such cases we mark the omitted level with, for example, "No order", in both the tooltip and the lineage summary.

Unmapped species names

The tree is built by looking at each sequence in the full alignment for the family. We take the name of the species given by UniProt and try to map that to the full taxonomic tree from NCBI. In some cases, the name chosen by UniProt does not map to any node in the NCBI tree, perhaps because the chosen name is listed as a synonym or a misspelling in the NCBI taxonomy.

So that these nodes are not simply omitted from the sunburst tree, we group them together in a separate branch (or segment of the sunburst tree). Since we cannot determine the lineage for these unmapped species, we show all levels between the superkingdom and the species as "uncategorised".

Sub-species

Since we reduce the species tree to only the eight main taxonomic levels, sequences that are mapped to the sub-species level in the tree would not normally be shown. Rather than leave out these species, we map them instead to their parent species. So, for example, for sequences belonging to one of the Vibrio cholerae sub-species in the NCBI taxonomy, we show them instead as belonging to the species Vibrio cholerae.

Too many species/sequences

For large species trees, you may see blank regions in the outer layers of the sunburst. These occur when there are large numbers of arcs to be drawn in a small space. If an arc is less than approximately one pixel wide, it will not be drawn and the space will be left blank. You may still be able to get some information about the species in that region by moving your mouse across the area, but since each arc will be very small, it will be difficult to accurately locate a particular species.

Loading sunburst data...

Tree controls

Hide

The tree shows the occurrence of this domain across different species. More...

Species trees

We show the species tree in one of two ways. For smaller trees we try to show an interactive representation, which allows you to select specific nodes in the tree and view them as an alignment or as a set of Pfam domain graphics.

Unfortunately we have found that there are problems viewing the interactive tree when the it becomes larger than a certain limit. Furthermore, we have found that Internet Explorer can become unresponsive when viewing some trees, regardless of their size. We therefore show a text representation of the species tree when the size is above a certain limit or if you are using Internet Explorer to view the site.

If you are using IE you can still load the interactive tree by clicking the "Generate interactive tree" button, but please be aware of the potential problems that the interactive species tree can cause.

Interactive tree

For all of the domain matches in a full alignment, we count the number that are found on all sequences in the alignment. This total is shown in the purple box.

We also count the number of unique sequences on which each domain is found, which is shown in green. Note that a domain may appear multiple times on the same sequence, leading to the difference between these two numbers.

Finally, we group sequences from the same organism according to the NCBI code that is assigned by UniProt, allowing us to count the number of distinct sequences on which the domain is found. This value is shown in the pink boxes.

We use the NCBI species tree to group organisms according to their taxonomy and this forms the structure of the displayed tree. Note that in some cases the trees are too large (have too many nodes) to allow us to build an interactive tree, but in most cases you can still view the tree in a plain text, non-interactive representation. Those species which are represented in the seed alignment for this domain are highlighted.

You can use the tree controls to manipulate how the interactive tree is displayed:

show/hide the summary boxes
highlight species that are represented in the seed alignment
expand/collapse the tree or expand it to a given depth
select a sub-tree or a set of species within the tree and view them graphically or as an alignment
save a plain text representation of the tree

Loading...

Please note: for large trees this can take some time. While the tree is loading, you can safely switch away from this tab but if you browse away from the family page entirely, the tree will not be loaded.

Structures

For those sequences which have a structure in the Protein DataBank, we use the mapping between UniProt, PDB and Pfam coordinate systems from the PDBe group, to allow us to map Pfam domains onto UniProt sequences and three-dimensional protein structures. The table below shows the structures on which the APP_N domain has been found. There are 12 instances of this domain found in the PDB. Note that there may be multiple copies of the domain in a single PDB structure, since many structures contain multiple copies of the same protein seqence.

Loading structure mapping...

Archea	Eukaryota
Bacteria	Other sequences
Viruses	Unclassified
Viroids	Unclassified sequence

Family: APP_N (PF02177)

Jump to...