Research data
AGP object interval projection
Split object intervals into component coordinates and declared gap pieces.
Your inputs
Start with an exampleYour result
Example resultHow it works
Intersect each query with the ordered rows for its named object. Plus-oriented pieces add the object displacement to component_beg; minus-oriented pieces subtract it from component_end. Keep object order, ascending component ranges and mapped endpoint order. Retain gaps and count unknown-orientation default-plus pieces separately.
Object chr1 positions 4–15 span ctgA 104–105, a three-position gap, reverse ctgB 25→21 and two default-plus scaffoldC positions 201–202. The pieces total 12 positions: seven known-direction bases, two orientation-unknown bases and three declared gap positions.
Limits
One-level AGP2.1 structural profile, with no sequence or alignment fetch. Up to 2 MiB combined UTF-8 text, 20000 AGP rows, 2000 queries, coordinates 1–1000000000000, 100000 pieces and an 8 MiB complete report. Require exact TAB fields, canonical positive integers, contiguous object coordinates/parts and grouped object rows. Header comments precede the body; no body blanks, BOM, bare CR or unsupported controls. IDs use 1–256 printable ASCII non-whitespace characters excluding #. Components A/D/F/G/O/P/W and N/U gaps use the declared gap/linkage/evidence subset. U gaps require 100 coordinate-placeholder positions, with actual size unknown. Raw ?, 0 and na orientations use the NCBI default-plus projection while remaining explicitly unknown. Unknown objects get no invented coverage; known-object queries outside the declared end reject without clipping. Reused components are allowed and object-like component IDs are not expanded. No FASTA extraction, biological orientation/evidence validation, GFF/BED rewriting, alignment liftover or complete submission-validity claim.