Why Science? | BED and Genomic Feature Coordinates

Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. Browser Extensible Data (BED) is a plain-text format for recording genomic feature locations and annotations. Developed by UCSC and formalised by the GA4GH Large Scale Genomics Work Stream, it uses three mandatory fields—chrom, chromStart and chromEnd—and up to nine standard optional fields, with custom fields permitted by agreement. GA4GH lists BED as current with Active Engagement and BED v1.0 as the last approved version; the version table separately labels v1.0 maintained, development and draft dated 5 January 2022, so readers should cite the exact specification used. BED coordinates are zero-based and half-open: the start is included and the end is excluded. A valid-looking interval is not meaningful without the correct reference assembly, sequence name, feature definition and provenance. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.

Related eduKate reading: refget and globally identifiable reference sequences; GA4GH Data Connect and federated dataset queries; htsget and secure genomic data streaming; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.

Primary and official sources checked on 12 October 2026: Official GA4GH BED product page, current BED v1.0 listing; Official BED v1 specification; Official SAMtools hts-specs repository; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Standards, service interfaces and recommendations can change, so preserve the dated documentation and versions used.

A deeper reading route

BED looks simple because its first three tab-separated fields describe a sequence and an interval. That simplicity is productive: tools can sort, intersect and display millions of features. It is also deceptive. A coordinate has no biological meaning until the reference assembly, sequence naming convention, feature type and generation method are known.

The zero-based half-open convention represents an interval as [start, end). Position zero can be a valid start, the end is excluded, and length is end minus start. This makes adjacent intervals compose cleanly in software, but many reports and genome browsers describe positions differently. Conversion must name both the source and destination convention.

Optional fields progressively add a name, score, strand, display thickness, colour and block structure. A BED12 record can describe several blocks such as exons inside one overall span. The outer interval, thick region and blocks answer different questions. Treating the bounding span as continuous feature coverage can create false overlap.

Custom columns are allowed, but interoperability then depends on an external schema or contract. One file’s thirteenth column might be a p-value; another’s might be a sample name. Good producers publish field names, types, units, allowed missing values and version. Good consumers reject undocumented extras instead of guessing.

Interval operations need explicit policies. Strand, minimum overlap, reciprocal overlap, block awareness, duplicates and reference compatibility can all change the result. A command that runs without error may still answer the wrong biological question. Reproducible analysis records the tool, parameters, input hashes and assembly.

Display directives and track configuration can make a browser view helpful, but presentation must not be mistaken for the feature table itself. Colour, labels and viewing windows can emphasise one interpretation without changing the underlying intervals. A durable workflow keeps raw BED records, any browser-oriented configuration and the rendered image as separate artefacts, so a later reader can tell data from display. When a pipeline accepts headers or special lines, its behaviour should be documented and tested instead of assumed from another tool.

For students, BED is a joyful bridge from number lines to genomes. A coloured strip from 2 to 5 covers three units in a half-open system: 2, 3 and 4. Add a reference-edition label and a feature definition, and the activity becomes a miniature lesson in measurement, coordinates, evidence and scientific communication.

A four-step claim ladder for this method

Stage	Question	Evidence	Responsible output
Locate	Where does the feature begin and end?	chrom, chromStart and chromEnd	A zero-based half-open interval
Annotate	What else is known about it?	Name, score, strand, display and block fields	A richer feature record
Compare	How do features overlap or differ?	Assembly-aware interval rules and parameters	A reproducible relationship
Interpret	What does the record claim biologically?	Feature definition, method and provenance	A bounded scientific statement