LONG BEACH · NORTHERN GROVE · PUBLIC-INTEREST INVESTIGATION
The northern riverside grove is already alive. Before construction changes it, who can demonstrate which mature trees will be saved—and whether more can be preserved?
CONSERVATION SANCTUARY · INDEPENDENT PUBLIC-INTEREST REVIEW · PUBLIC SITE v1.6.7 · OCTOBER 19, 2026
We welcome more parkland, better accessibility, ecological restoration, and investment in the public good. We want those improvements to succeed—and to meet higher standards of engineering rigor, ecological stewardship, transparency, and mature-tree preservation.
Progress should be measured not only by what is constructed, planted, or removed, but also by what is responsibly preserved. A sapling is not a time machine.
Urgent · Forwardable · Start here
This site is for public education and action—not merely retrospective documentation. See the outreach and records-request toolkit to find a contact, copy a message and help qualified people take the next step.
The current first tree-removal date, the individual-tree removal and retention inventory, and the completed design-stage mature-tree minimization verification have not been recovered in this investigation. That is precisely why qualified independent review and immediate records clarification are needed.
New urgent oversight question: Which party is contractually responsible for verifying tree identification, protection, and removal authorization in the field—and what records demonstrate that those duties are being performed? Inspect the public contracting and schedule evidence ↓
Identify the current construction timetable, first planned tree removal, and who can prevent irreversible cutting while preservation alternatives are reviewed.
Ask qualified arborists and engineers to compare the surviving trees with the operative DEM, roadway, grading, utility and planting drawings.
Please pass this investigation to preservation groups, engineers, public-interest lawyers, community advocates and journalists—and help identify someone who can take the next step.
The PDFs are prior outreach editions and may reproduce third-party imagery as documentary excerpts. All source citations remain linked. Their technical claims should be checked against the operative project records.
Independent good-faith investigation. Readers are encouraged to verify its sources, identify errors, contribute relevant evidence, and help qualified organizations pursue preservation while the trees remain standing. Nothing here constitutes an engineering certification, legal determination, or arborist's diagnosis.
What counts as progress? · Public investment and environmental justice
We welcome more housing, better public transportation, safer streets, accessible paths, expanded parkland, ecological restoration and substantial investment in the public good. We want them to succeed together. The standard should be better development: more public benefit, more environmental health, and more of the living resources our community already cherishes preserved wherever feasible.
A walkable, transit-connected neighborhood can reduce the need to drive. That is an important gain. But density is not a complete vision of a healthy city if people cannot reach shaded, welcoming, biologically functioning green space. Greenery must be more than a promise in a rendering. Mature canopy already cooling and sustaining the community is a present public asset.
The City categorized R-7192 under “3007 — CAPITAL IMPROVEMENT PROGRAM.” That tells us how the purchase was administered, not whether every loss was a necessary price of progress. [P17 · official solicitation] Examine the contracts and oversight questions ↓
City source and scope: Long Beach Open Space and Recreation Element Update ↗. These are reported citywide park-space-access disparities; they are not tree-canopy percentages, site-specific findings for R-7192, or proof of intent.
Long Beach itself describes historic redlining, discriminatory land-use patterns and unequal access to parks and tree-lined streets. Its planning materials identify Central, West and North Long Beach among the areas where park scarcity, heat vulnerability and social vulnerability overlap. This is not an argument against new parks. It is precisely why expanding green space and retaining the mature canopy that already exists deserve to be treated as complementary objectives. City planning context ↗
Our demand is not less public investment. It is a higher standard of public investment. Show what the design creates, what it destroys, what alternatives were tested, what mature canopy remains, and who will bear any intervening losses.
The actual place · geographic evidence
The red outline identifies the resident-defined northern study grove north of Ocean Boulevard, not an official demolition or permitting boundary. The photographs show why the mature canopy must be evaluated as a continuous living landscape. The separate Coastal Commission commitment to protect 37 trees concerns an area south of Ocean Boulevard.
These are historical visual reference screenshots, not a live satellite survey. Google imagery dates and current tree status require independent verification. Observations mark trees or clusters; the original red/yellow/green classifications are not field removal permits.
Restored geographic research interface · Original clean satellite image
The original clean aerial screenshot is the background, not a simplified diagram. The colored pins form a separate interactive layer placed using the investigator's approximate 2026 screenshot registration. Toggle one class at a time, zoom, and select an observation to inspect its coordinates and provisional DEM assignment. Red indicates a screened removal/clear-and-grub conflict; yellow indicates possible construction exposure; green indicates lower identified conflict—not a formal preservation guarantee.
Orientation: north points approximately right; this image is not north-up. Red/yellow/green pins and coordinates are investigator-generated and registered by reference to the original screenshot, not survey-grade trunk locations. Historic satellite imagery dates are not independently authenticated. Save the observation CSV ↓ · Save the KML ↓ · Read the signed drawing comparisons ↓
Loading the live map… The observation register below works without map tiles.
The red/yellow/green observations are not a census of 116 distinct trees. The optional street grid does not replace the photographic references. DEM assignments remain provisional; inspect the accompanying signed plan screenshots. Blue virtual visit stops appear only in Walk the Grove.
The science · Physical health, mental health and time
Continuous or near-continuous mature canopy is not just a sum of individual trees. Its crowns, roots, soil, shade and connected habitat create conditions that can be lost even when a project's final planting tally looks favorable.
Established tree cover provides shade now. A Los Angeles modeling study examined how expanded canopy and reflective surfaces could reduce heat-related health burdens; a 2024 systematic review found lower heat-related illness and mortality in greener settings across the studies examined.
Kalkstein et al., Los Angeles (2022) ↗ · 2024 systematic review ↗
A U.S. study examined mortality patterns following major regional tree loss. A European health-impact assessment modeled premature deaths associated with urban heat and the potential benefits of greater tree cover. These results warrant serious attention to canopy loss; they do not yield a local death count for this grove.
Accessible green environments support restoration, recreation, social connection and opportunities for movement, quiet and respite without a purchase. An umbrella review evaluated the strength of evidence across many green-space health outcomes, including well-being and affect.
2024 graded evidence review ↗ · WHO urban green space and health ↗
Where a tree stands matters. Shade near a walking route, school or transit stop may serve people who cannot simply travel to a distant park. The grove also provides habitat, ecological connections, neighborhood memory and an actual lived landscape, not an abstract greening target.
What is the counterfactual? Compare preservation-first improvements with the approved design and with realistic continued maintenance. Measure mature canopy retained, mature canopy lost, land changed from pavement to planted space, new accessible parkland, construction trauma to surviving trees and ecological services through time. Account for uncertainty in old-tree survival and new-tree establishment. That is more informative than subtracting the number of trees removed from the number of saplings planted.
Evidence distinction: Peer-reviewed studies demonstrate and estimate population-level relationships, but do not prove the outcome of removing any one tree. A site-specific arboricultural, canopy, heat and design-alternatives assessment remains necessary.
Walk the grove · 40 resident-selected viewpoints
The blue positions are preserved in full, numbered SV-01 through SV-41 with 35 unused. Open each location in Google's official interactive Street View; you can turn around and examine the trees and surroundings. We have not independently confirmed every panorama's exact location, capture date or viewing direction.
Loading the separate blue Street View viewpoint map… The list below remains available without map tiles.
This map shows only the forty blue virtual-visit locations. Tree-risk observations are shown in the separate grove atlas. Select a stop to open Google's live interactive panorama; the map does not host Google Street View screenshots.
Google selects the nearest currently available panorama and may change it when imagery is updated. These are live links, not copies of Google screenshots.
Neighboring blue stops were chosen to give continuous road-level coverage where possible. Rather than discard viewpoints, we retain the complete network, while allowing readers to explore the nearest stop to any tree observation.
For launch, panoramas open on Google's site. An in-page embed can be added later using Google-provided Share → Embed code or a configured Maps Embed API key—without rehosting Street View imagery.
| Stop | Coordinates | Live Street View |
|---|
Engineering primary evidence
The twenty DEM drawings are excerpts from the City of Long Beach's signed construction set. Their removal instructions and key notes matter; by themselves they do not establish that every removal is unavoidable. These are lossless screenshots of the signed drawings, not replacements for the official vector PDF or current field revisions.
Open the City of Long Beach PW-26-759 official procurement page ↗, then look under File Attachments. Choose R-7192 Shoreline Combined Plan Sheets. The signed copy examined in this investigation is titled R-7192 Shoreline Combined Plan Sheets-signed.pdf (456 PDF pages).
| What to inspect | Signed PDF page | Drawing identifier |
|---|---|---|
| Demolition sheet key / geographic index | 13 | K-1 |
| Demolition drawings | 21–40 | DEM-1–DEM-20 |
| Planting legend and tree schedule | 362 | PL-1 |
| Individual planting plans | 363–386 | PP-1–PP-24 |
Also on the same City procurement page: R-7192 Shoreline Specifications (including tree-removal and construction requirements), R-7192 Shoreline Drive Addendum 1, and R-7192 Shoreline Drive Addendum 2. Consult the addenda and any later operative changes when checking final approvals.
Page numbers above mean the PDF viewer page count beginning at page 1, not the drawing sheet number. Selecting a DEM below displays its PDF page automatically. Some procurement downloads require free portal registration or login.
Official-link access note: Some government websites and document portals reject requests from VPNs, privacy relays, proxies, or automated browsers. An Access Denied message or failed download does not necessarily mean the link is broken or the document is missing. Try the agency's main document page, a different browser or network, or—if you're comfortable—a connection without the VPN. Some procurement files also require login. Links can genuinely change; please report persistent errors so they can be checked.
Suspected DEM-16 master-index discrepancy remains an open verification question. Check matchlines, stationing and operative signed plans.
Select a sheet to display its full-resolution engineering screenshot.
DEM-1 · signed PDF page 21 · printed drawing DEM-1 (sheet 21).
Switch DEM sheets above to inspect the corresponding investigator-captured geographic references alongside the official drawing. These image correspondences are visual aids, not survey-grade registrations or proof that every individual tree is marked for removal.
Select a DEM drawing to load the paired aerial evidence.
Official procurement record: City portal PW-26-759 → “R-7192 Shoreline Combined Plan Sheets”. Individual sheets may have amendments or field revisions not yet incorporated here.
Field index · transparent methods
| ID | Classification | Provisional DEM | Coordinates | Explore |
|---|
Download cleaned observation records (JSON) ↓ · Boundary methodology and points ↓
The older number of 103 distinct coordinates does not match the current 116 stored coordinate pairs. The current 116-count refers to location observations, including tree clusters, not 116 certified individual trees.
Source register · inspect the claims
The signed planting legend (PL-1, PDF p.362) provides a preserved-tree symbol; the field comparison has not identified tree-by-tree application on PP-1–PP-24. Demolition Note 7 directs protection of unmarked trees unless directed otherwise by the Engineer. VIS-2 calls for minimization verification. Those provisions must be reconciled with actual operative plans and field orders.
EIR/EA environmental review ↗ · Signed drawings and bid record ↗
The California Coastal Commission documented 65 proposed removals reduced to 21 within its geographically restricted southern permit review, including a commitment to retain 37 trees. These cannot be counted as protections for the northern grove.
Research library · Evidence that readers can independently check
Each finding should connect to an inspectable primary document or clearly identified scientific publication. The official City files, not this site's screenshots, are authoritative for what the adopted plans actually say. Later revisions and written Engineer directions must also be requested.
Note on official links: Government sites may block VPN or privacy-relay requests; an access error is not necessarily a broken link. See the original-document locator and access tips ↑.
City project description: 5.6 acres of proposed additional parkland and planned tree planting ↗. Long Beach Buys solicitation PW-26-759: plans, specifications, addenda and procurement record ↗.
Download the official attachment: “R-7192 Shoreline Combined Plan Sheets” (the signed research copy is R-7192 Shoreline Combined Plan Sheets-signed.pdf). K-1 = PDF p.13; DEM-1–20 = pp.21–40; PL-1 = p.362; PP-1–24 = pp.363–386.
Newly documented: the April 2020 Shoemaker Bridge Final EIR/EA identifies a proposed 7.49-acre staging area in existing parkland containing trees and ground cover—not an empty construction lot (Appendix A, Section 4(f)/6(f), printed pp.4-13–4-15; Figure S-3, printed S-17). See the annotated source discussion and figure ↓ · CEQAnet record ↗.
CEQAnet Shoemaker Bridge environmental review ↗ · 2025 California Coastal Commission staff report: separate southern permit area ↗ · Long Beach Public Records Act request instructions ↗.
The southern 37-tree retention commitment is an important design-revision precedent, not proof of northern-grove preservation.
City open space planning: 91% and 90% park-space disparities ↗ · Long Beach Parks, Recreation and Marine Strategic Plan ↗ · Long Beach 2030 Strategic Vision ↗.
These establish recognized public goals, not proof that any particular removal has or has not satisfied them.
Donovan et al. 2013 — U.S. tree mortality and health ↗ · Kalkstein et al. 2022 — Los Angeles heat mitigation ↗ · Iungman et al. 2023 — 93 European cities ↗ · Nazish et al. 2024 — systematic review ↗ · 2024 evidence-grade umbrella review ↗.
These address different populations and research designs. None is an appraisal or mortality forecast for individual R-7192 trees.
2-page urgent action brief ↓ · 15-page hyperlink-cited evidence dossier ↓ · 17-page combined packet ↓
These are dated supporting editions; the live website is continually corrigible. Treat unverified site-level observations as evidence inviting further examination.
Use the accountability questions to identify the responsible office or record custodian. Use the outreach toolkit for a practical first message. Report material errors with the exact claim, cited source, document revision, page and corrected reading.
Please forward this resource to someone better positioned to help rather than waiting for one resident investigator to coordinate every inquiry.
[P15] Long Beach City Council October 6, 2026, Item 26-56261: R-7192 construction award and RFP PW-25-547 construction management/inspection. Construction: Sully-Miller; inspection/management: PMCS Group. Agenda award terms are not the full executed scopes.
[P16] Metro Board File 2026-0662, “Long Beach–East LA Corridor Mobility Investment Plan Highway Capital Funding,” September 2026, Issue / Background / Alternatives Considered. [P16a] Metro Sept. 24 action and PDF attachments.
[P17] City of Long Beach Procurement PW-26-759, official “3007 — Capital Improvement Program” listing, attachment list and Addendum 2 · [P18] Long Beach City Clerk, Contracts Online.
Read the procurement-and-preservation audit, named roles and records requested ↓
Download the 116-location observation register and KML in their recovered v0.8 research versions. Observation markers may refer to individual trees or groups; they are not a census of 116 distinct trees, and DEM associations are provisional. Exported data should be checked against the current site register and original signed drawings.
Documentary finding · Public money, contractual authority and preservation duties
Long Beach calls this a capital improvement. That is the City's formal expenditure category, not a finding that every demolition or design choice maximizes the public good. The public should be able to trace a living tree from the original survey, through design decisions and contractual instructions, to the field authorization that determines its fate.
We welcome the promised improvements: additional parkland, safer walking and cycling, access, and restoration. The critical public-interest question is whether the City can deliver those benefits while preserving more of the mature canopy already providing ecological and civic value. A funded construction item is not evidence that the underlying loss was unavoidable.
The City of Long Beach solicitation PW-26-759, “R-7192 West Shoreline Drive Realignment Project” [P17] identifies PW — Public Works, location “3007 — CAPITAL IMPROVEMENT PROGRAM”, purchaser Lilia Hom, project-information contact Akbar Sharifian, and “Contract” as its purchase method. Its ship-to/bill-to office is Public Works, 411 W. Ocean Blvd, Long Beach, CA 90802, with lbpurchasing@longbeach.gov listed for purchasing. Those are official record fields, not proof that the purchaser selected individual trees for removal. [P17 · solicitation header]
The same official page names the attachment “R-7192 Shoreline Combined Plan Sheets” alongside “R-7192 Shoreline Specifications” and dated addenda. The signed research copy is titled R-7192 Shoreline Combined Plan Sheets-signed.pdf. Its demolition sheets are DEM-1–DEM-20, PDF pp.21–40; PL-1 is PDF p.362. Those exact labels make the underlying record independently retrievable. The amended bid schedule lists 300 EA “TREE AND STUMP REMOVAL” at Item 46; this is an estimated pay quantity, not 300 independently verified unique living trees. [P17 · attachments and Amendment 2, Items 45–46]
Long Beach City Council, October 6, 2026, agenda Item 26-56261 [P15], sets out separate proposed contract awards. Dollar amounts below are the City Council agenda amounts, not proof that every dollar has been spent, or that the executed contract contains each contemplated duty. [P15 · Council agenda, Item 26-56261]
| Authorized work / proposed contractor | Agenda base amount | Maximum with authorized contingency | Specific document to obtain next |
|---|---|---|---|
| Construction · Sully-Miller Contracting Company Plans and Specifications R-7192 | $44,106,775 | $50,722,791 | Executed construction contract, general/special provisions, plan addenda, notices to proceed, field directives and change orders. |
| Construction management and inspection · PMCS Group Inc. RFP PW-25-547 | $3,396,054 | $3,735,659 | Executed professional-services contract, scope of services, staffing assignments, inspection protocols, environmental-monitoring and document-control responsibilities. |
Do not presume the PMCS scope. The agenda specifically purchases construction-management and inspection services, but the executed statement of work is needed to establish whether PMCS, City inspectors, a Resident Engineer, an arborist, the construction contractor, or another designated person must verify each tree. City Clerk's contracts portal [P18] is an additional route to locate agreements. [P15]
Obtain adopted action, signed agreements, amendments, contingency approvals, and the legal authority for adjustments before irreversible work.
Request original tree inventory transmissions, VIS-2 design-verification records, tree-specific alternatives, approved current drawings, Engineer directions and pre-removal signoffs.
Identify contractually required tree markings, clearing boundaries, protection measures, notifications, hold points and field documentation. Confirm actual assignments from the executed agreement.
Identify the actual purchased inspection scope, assigned inspectors, logs, environmental coordination, nonconformance procedures and escalation paths. No tree-specific duty is presumed absent the contract.
Trace procurement schedule quantities, bid amendments, payment units, contract change controls and the custodian for contractor scopes—not the presumed decision-maker for tree removal.
Obtain funding agreements, schedule and reporting milestones, amendment terms, and any rules affecting the feasible time for design-preservation review.
The Los Angeles County Metropolitan Transportation Authority, Board File 2026-0662 [P16], describes a $35 million project funding shortfall at the time of its September 2026 report, the possibility of losing a $30 million federal funding award, and a target of delivering the project before the 2028 Los Angeles Olympic and Paralympic Games. Metro previously programmed $9 million; the September 24 Board action approved up to $35 million more, subject to contingencies. These are dated funding circumstances; the historical $35 million gap should not be portrayed as necessarily remaining unfunded after the action. [P16 · Issue, Background, Next Steps] [P16a · Board action, Sept. 24]
A second, unusually revealing passage deserves public scrutiny: Metro staff stated that immediately programming these funds conflicted with the previously understood approach for future mobility-program allocations developed with communities, cities and stakeholders, but described the urgency of securing the federal award and opening before 2028 as a mitigating circumstance. This is a documented tension between funding procedure, community participation and delivery urgency—not proof that this project's tree-preservation review was waived, that residents were excluded, or that trees were targeted to meet a deadline. [P16 · Alternatives Considered]
Nothing in these public funding statements establishes that an individual tree was ordered removed to meet a particular date. They do establish a reason to examine dated decisions, design-change opportunities and the operative work schedule. The City agenda additionally proposed $35 million in Metro Measure M-related appropriations; this must not be double-counted as a separate $35 million funding source on top of the same Metro allocation. [P15 · Item 26-56261]
Time-sensitive document requests, in practical order:
Evidence boundary: These questions do not accuse named employees, contractors or funders of misconduct. They identify agencies, project parties and source records from which precise duties and field decisions can be established. A procurement listing, authorized amount or funding timetable is not a substitute for an executed contract, current operative plan or signed tree-specific field order.
Follow the numbered accountability questions ↓Compare documented tensions ↓Forward to reviewers ↓
Restored from the investigation · Contract text beside preservation duties
A contract can specify exactly how to remove a tree without demonstrating that preserving it received equally explicit, enforceable consideration. The question is not whether individual engineers care about trees. It is whether the decision-making system requires their ecological, historical, public-health and intergenerational value to be considered, documented and defended before irreversible work.
The City's signed construction materials do include tree-protection provisions. This comparison presents them alongside the removal, root-work, payment and disposal procedures—not to imply an absence of safeguards, but to determine how the provisions are reconciled and enforced in the field.
| What the construction documents specify | What must still be verified for the living trees |
|---|---|
| Removal authority — §300-1.2.4, printed I-19. The contractor is instructed to “remove trees shown to be removed on the Plans or as requested by the Engineer.” This section governs already-designated removal; it does not authorize cutting every tree without a removal designation. | Who identifies each tree before work, what criteria permit an Engineer-directed change, and where is the dated, tree-specific authorization? Must new decisions undergo arboricultural and environmental-commitment checks? |
| Physical dismantling — §300-1.2.4. Authorized removals involve progressive branch/crown dismantling (the specification calls it “topping”), with other lowering methods where necessary, followed by trunk removal. That procedural detail deserves comparison with the documentation required to authorize destruction. | What prevents an outdated drawing, mistaken field mark, or unreviewed directive from initiating crown destruction? Who has stop-work authority before a tree loses its mature canopy? |
| Roots and site work — §§300-1.2.1–.3. Root shaving, pruning, removal and barriers are specified in connection with construction. These operations can affect trees intended to remain. | Where are the individual root-protection zones, allowed excavation limits, inspection points, health monitoring and methods that avoid long-term mortality of retained trees? |
| Stumps and debris — §§300-1.2.6–.7, §401-8. Stump grinding, end-of-day cleanup, off-site disposal (including the direction that material be “properly disposed of outside the right-of-way”) and construction-material diversion are operationally described. | What records show that a tree was genuinely unavoidable to remove? Recycling or salvaging its remains does not restore decades of shade, habitat or stewardship. |
| Contract quantity and payment — PW-26-759 item 46. The bid schedule estimates 300 tree-and-stump removal payment units. That is a procurement quantity, not an inventory proving 300 separate mature trees will be felled. | What is the latest approved quantity and individual-tree disposition schedule? What distinguishes removal payments from the value of trees retained or lost? |
| Default protection — DEM General Note 7. Existing trees and shrubs not marked for removal are protected in place unless the Engineer directs otherwise. PL-1 depicts an existing-tree-to-be-preserved symbol. | What current tree-by-tree inventory and reconciled DEM/planting plan are used on site, who verifies protected trees, and which signed departures from default protection exist? |
| Additional existing protections — §§300-1.2.2.1–.2 and environmental commitments. The excerpts specify ISA-qualified supervision for pruning, biological surveys/City notice-to-proceed, removal notices, a ten-working-day appeal window, and a Tree Committee; VIS-2 addresses mature-tree-removal minimization during design. | Which provisions apply to each northern-grove operation, which were modified by addenda, who completed VIS-2, and how are notice, appeal review, arborist expertise and tree identity verified before removal? The pruning qualification is not proof of independent review for every removal decision. |
Inspect the originals: Long Beach procurement PW-26-759: signed plans, technical specifications and addenda ↗ (DEM-1–20 PDF pp.21–40, General Note 7; PL-1 p.362; specifications Division I printed pp.I-17–I-20, §§300-1.2.1–.7; §401-8). The ten-day notice and Tree Committee provisions appear in the earlier specification excerpts; effective application, amendment, actual posting and review outcomes require confirmation. Addendum 2 assigns procurement of nesting-bird survey services to the City, so the original survey language must be checked against the operative addendum.
These are the actual categories in the City's technical specifications, not metaphors invented for this investigation. Division I, §401-8.3(d), printed page I-103, defines Construction and Demolition Debris broadly: it includes materials such as asphalt, concrete, brick and lumber. The definition also permits construction debris to be commingled with rock, soil, tree stumps, and other vegetative matter resulting from land clearing
. This places material from cleared trees inside a waste-management system also used for demolished structures and excavated material.
Section 401-8.3(s), printed pages I-104–I-105, defines Solid Waste to include putrescible and nonputrescible solid, semisolid and liquid waste. Its categories include refuse, demolition waste, sewage-related material, manure listed separately from vegetable or animal solid and semisolid wastes
. Animal-derived discarded material is not merely manure: depending on the material and applicable laws, it can include animal tissue or remains. This broad definition mirrors California Public Resources Code §40191 ↗.
A waste classification is not a permit to harm wildlife. Nor is it a procedure for keeping living animals out of the waste stream. The disturbing imbalance is in what the project makes explicit: how matter is classified, removed and handled after it becomes debris, versus the need for readily inspectable, site-specific instructions protecting the animals and habitat before trees, roots and understory are disturbed.
Residents need not first produce an injured animal or a carcass to ask the City what safeguards it has required. Who inspects inhabited cavities, roosts, burrows, understory and soil habitat? What must a worker do upon discovering an animal? Who can halt machinery, call a qualified professional, authorize any lawful handling, and approve restarting? Where is the biologist the City said it would procure, what areas and organisms will be surveyed, and where are the actual field instructions? These questions extend well beyond nesting birds. Read the City-biologist and whole-grove wildlife inquiry ↓
Evidence boundary: These definitions do not establish that wildlife was killed or disposed of on R-7192, that all listed materials occur on this project, or that they share one disposal route. Section 40191 excludes certain hazardous, radioactive and medical waste. None of those qualifications removes the need to demonstrate preventive measures before destructive work begins.
Meanwhile §300-1.2.7, printed page I-19, directs the contractor to remove pruning, tree-removal and stump-grinding material from the worksite and properly dispose of it outside the right-of-way. It directs green waste from these operations to be reduced, reused, recycled and/or transformed, with weight slips available to the Engineer upon request. Those measures concern what happens after removal. A well-managed waste stream cannot by itself establish that destruction of the standing tree was necessary, appropriately valued or the least harmful feasible option.
The deeper public-accountability question is what the City chose to purchase with public money. Removal procedures, pay items and waste-diversion records may be detailed and administratively enforceable. What comparably specific documents show that the mature living trees were identified and appraised as public assets; that preserving them influenced project design; and that remaining removal decisions account for heat, public health, ecological relationships, community history and intergenerational continuity? A project can satisfy its debris-management requirements while leaving that prior question unanswered.
These concerns are especially consequential in a densely developed river corridor where existing shade and access to green space are unevenly distributed. The documented preservation-oriented redesign south of Ocean Boulevard raises a separate, evidence-seeking question: What comparable tree-specific retention alternatives and verifications were completed for the more extensive northern grove? The southern and northern review areas must not be conflated.
Primary documentary locator: R-7192, 260430 R7192 Shoreline Specifications.pdf, Division I, §401-8.3(d) (printed I-103), §401-8.3(s) (printed I-104–I-105), and §300-1.2.7 (printed I-19); original procurement PW-26-759 ↗. The material above describes document categories, not proven field disposal destinations or animal mortality. Preservation remains the first question; diversion is not a substitute for it.
The decisive point comes before the first irreversible cut. A tree can lose the crown, roots or living architecture that made it valuable well before a stump is removed or timber becomes a waste-management entry. Safeguards that operate only after that threshold cannot preserve the original mature tree.
Public improvements should be assessed not only by what they build, but by what they had an opportunity to preserve. Paying to remove a mature tree records the cost of a contracted task; it does not appraise the living asset, its relationships or the years needed to recreate comparable canopy.
None of these unanswered questions is, by itself, proof of a violated rule or wrongdoing. The public evidence should make the decision chain inspectable rather than assume the motives or qualifications of a named professional. See AQ-003, AQ-011, AQ-021 and AQ-023 in the accountability register ↓
Living inhabitants · June 23 addendum · Habitat continuity
A living grove is not simply a collection of trees awaiting a removal decision. It is habitat. Its canopies, bark, cavities, dead wood, roots, leaf litter and soil support organisms and ecological relationships that may have developed over years or decades. Clearing can harm residents of that habitat without first producing a visible nest, a documented carcass or a violation notice.
We do not have to prove that wildlife has already been harmed to ask the City to demonstrate what reasonable precautions are required before harm occurs. Evidence of a particular injury would support a separate investigation. This inquiry concerns whether protections are specified, carried out, checked and enforced before clearance, grading, root work and crown dismantling.
Addendum 2 · June 23, 2026 · Question 10 · PDF p. 7
“The City will procure a biologist separately to perform the required nesting bird surveys for the project.”
The City answered a bidder asking who would furnish and pay for nesting surveys: it, rather than the tree-removal contractor, would arrange that service separately. A commitment is not a completed survey. We need the actual procurement or assignment, scope of work, named qualified professional or firm, dates, mapped survey areas, findings and instructions communicated to the field.
Addendum 2 · June 23, 2026 · Question 11 · PDF p. 7
“The intent is to minimize disturbance to aviaries and wildlife. The City expects contractors to take necessary precautions.”
The bidder had asked how a nonmechanized-hand-tools provision from a tree-maintenance policy applies to tree removal. This response acknowledges wildlife disturbance, but does not itself identify the precautions, responsible monitor, equipment restrictions, escalation pathway, or decision to proceed. Those may be established elsewhere; the current operative requirements and field records need to be shown.
Primary source: City of Long Beach, R-7192 Shoreline Drive Addendum 2, dated June 23, 2026, Question 10 and Question 11, PDF page 7. Official procurement PW-26-759 and addendum ↗. The addendum discusses the City as the permittee for a southern Coastal Development Permit in Question 9. Whether each protection and survey covers the northern grove, the southern permit area, or both must be verified provision by provision.
California Public Resources Code §40191 ↗ defines solid waste broadly, including demolition and construction waste, manure, and vegetable or animal solid and semisolid wastes
. Manure is a separately listed category; animal material cannot be reduced to manure alone. Depending on the facts and other applicable rules, discarded animal-derived material can fall within the broad definition. The statute also provides exclusions, including for certain hazardous, radioactive and medical waste.
These classifications are necessary for sanitation, lawful disposal and pollution prevention. They neither authorize harming wildlife nor provide instructions for protecting animals before clearing. Nor do they prove that wildlife was harmed on this project. But the City need not wait for a documented wildlife death to show how its construction requirements protect living organisms. The City's Addendum 2 says it will procure a biologist for nesting-bird surveys and expects contractors to take necessary precautions. The public accountability question is whether those statements have become named responsibility, site-specific surveys, coverage beyond nesting birds, written encounter and stop-work procedures, and independently checkable field records. Which provisions apply to the northern grove, and where can the public inspect them?
Waste categories do not establish that vegetation and animal-derived matter were actually commingled on this site; the governing rules and disposal procedures may differ by material. The question here is prevention and habitat continuity, not a claim of observed wildlife mortality.
A nesting-bird survey can be important, but it is not necessarily a complete assessment of an established urban habitat. A genuinely useful protection plan would address the organisms and places that could be affected—not merely whichever species is easiest to observe from a distance. We seek the site-specific scope for:
This list identifies habitat and taxonomic groups to assess, not a verified inventory of species present at R-7192. Applicable laws and permits differ by species, place, season and activity. For example, California Department of Fish and Wildlife guidance discusses pre-work nesting surveys and protective buffers for birds; other species or habitat impacts may require different assessments and authorizations. CDFW nesting-bird guidance ↗ · CDFW examples of construction minimization measures ↗.
Before irreversible work, the public should be able to inspect a dated chain of responsibility. We are requesting the documents—not asserting that every item is independently mandated in identical form by law:
Construction workers should receive clear, feasible, pre-approved procedures. Wildlife protection should not depend on an exhausted crew improvising legal or biological decisions while equipment is running.
A healthy mature tree can support a web of habitats and relationships that a newly planted sapling does not instantly reproduce. Even if animals escape the machinery, losing shelter, food sources, nesting sites, soil communities or familiar movement corridors can impose ecological costs across seasons and years. Tree retention, wildlife avoidance and long-term habitat continuity are related but distinct tests of project success.
These stakes are heightened where green space is scarce and neighborhoods already bear substantial environmental burdens. The City has documented unequal park access across Long Beach; those citywide comparisons should not be misrepresented as a tree-specific measurement of this grove. We should evaluate what the project preserves in this particular place, for current residents, living wildlife and future generations—alongside what it promises to build.
The question is not merely how discarded vegetation or animal-derived waste would be handled safely. It is what the City has required, verified and funded to prevent avoidable destruction of living trees, animals and their habitat before those decisions become irreversible. See AQ-013 and the related tree-protection questions ↓
Recovered investigative chapters · public and verifiable
This atlas is the work of an independent resident investigator acting in good faith, using publicly identifiable construction and environmental records, historical sources, geographic observations, and critical comparison. Every technical claim is an invitation to check the underlying source, correct errors, and independently assess what can still be preserved. It is not an engineering certification, legal finding, arboricultural diagnosis, or representation of any organization.
Where this began: concern about the treatment of accumulated public value—working schools, mature trees, historic structures and familiar community landscapes—as something that can be erased to make way for new capital improvements. Our first question was not whether Long Beach should invest in public infrastructure. It was whether its design and accounting systems recognize what communities already possess before authorizing its removal.
Here, that question is concrete: the existing mature grove along the Los Angeles River north of Ocean Boulevard remains the central study area. Proposed park expansion, pedestrian safety, transportation improvements and ecological restoration are legitimate public goals. Preservation should shape original design, not merely soften the consequences of decisions already made. [P01: City project] [P03: municipal tree assets]
Our working screening contains 27 red observations (explicit removal indications or apparent clear-and-grub conflicts), 61 yellow (potential construction injury), and 28 green (comparatively lower identified conflict). The distinction between a documented removal symbol, a clearing-area overlap and a possible root-zone impact is retained; none is proof that a tree has already been cut. Examine the observations → · Check the drawings →
Two parallel duties: immediate preservation review of the still-standing trees and longer-term public accountability for design, environmental compliance, institutional incentives, valuation, and eventual outcomes. The second must not hold up the first. The current cutting schedule and final operative drawing revisions are not independently verified. Uncertainty about that date is a reason to ask now, not to state that felling is certain or imminent.
The City reports stark inequalities in nearby park space: 91% less for residents of neighborhoods of color versus white neighborhoods and, separately, 90% less for residents of lower-income neighborhoods versus higher-income neighborhoods. This is a citywide park-space measure—not a canopy statistic. A scarce mature grove can therefore raise profound questions about access, urban heat and intergenerational public investment. [City open-space planning source ↗]
Individual trees matter. A continuous or near-continuous mature canopy is something more: overlapping shade, connected habitat, living soils, hydrological relationships, moderated exposure along paths, visual continuity, and an environment that people can use now. Species, health and canopy connectivity must still be studied rather than presumed for each tree.
Long Beach itself has recognized publicly owned trees as municipal capital assets and assigned its street-tree population a citywide value of approximately $369.19 million in a 2017 assessment. Those are policy and citywide valuation findings, not a site-specific appraisal of the R-7192 grove. The city's urban-forest and open-space materials recognize public-health benefits and significant inequalities in access to green space. [P04: city tree valuation] [P02: parks and equity]
Scientific reviews and cohort studies connect urban greenness to mental well-being, heat-related conditions, physical health and lower population-level mortality risk. Such research strengthens the case for considering these benefits in planning; it does not assign a precise number of years of life to any particular photographed tree. [S01: WHO] [S02: mortality review]
Existing canopy provides shade, habitat, environmental functions and places to walk, rest, gather and simply exist without purchasing anything. Its importance depends partly on where it stands and how scarce comparable green space is nearby.
New trees must establish, survive and grow. A planting count says little about when equivalent canopy, cooling, shelter, ecological function or familiar public space will return. Some aspects of continuity cannot be recreated.
What people may otherwise forget: future visitors can see an attractive new park and assume an unqualified improvement without ever seeing the mature grove it replaced. A completed project must be evaluated against the living landscape that actually existed—not an imaginary vacant lot.
Preservation is compatible with more parks, safer mobility, accessible paths, public education and restoration. The relevant test is whether a better design could incorporate more of the existing mature living infrastructure. Necessity arising from a selected design is not necessarily necessity arising from unavoidable physical constraints.
The City's October 2022 Reconnecting Communities grant application ↗ dates the environmental-clearance process to April 1, 2016 (Table 1, application p.16 / PDF p.19). It also says multiple design alternatives were evaluated during project development and public review (application p.15). Its then-projected 2022–2023 design and 2023–2025 construction milestones were forecasts as of 2022, not proof of actual completion on those dates. The 2026 contract record confirms that the planning history has extended over a decade.
That record makes a concrete, source-based inquiry possible: when did the design team obtain a mature-tree inventory; which trees influenced the roadway geometry; and what preservation alternatives were studied, rejected, or adopted? We do not yet have a complete tree-specific alternatives matrix or the completed VIS-2 minimization verification.
The California Stormwater Quality Association's EC-2, Preservation of Existing Vegetation ↗, explains why this timing matters. It emphasizes early coordination among owners, designers and contractors, vegetation incorporated into site layout, root-zone buffers, fencing, and avoiding construction storage and temporary roadways around retained trees. It notes that preservation planned during design can have low associated costs, while preservation opportunities narrow when designs omit existing vegetation.
EC-2 says vegetation preservation needs forward planning and warns that opportunities narrow when project plans omit existing vegetation. It also calls for protected root areas and for placing temporary roads, stockpiles and layout areas away from trees and other vegetation.
The guidance states that preservation planned during design can involve little cost, contrasts that with disturbance-control and replacement expenses, and calls for maintained boundaries and arboricultural attention to serious tree injuries.
The planning record extends back to 2016; a 2020 proposal also placed staging activity in parkland with existing trees and ground cover, within a park landscape containing substantial mature canopy. Which options protected the trees, and why were those options accepted or rejected? See the staging evidence ↓
Scope and limits: EC-2 is stormwater best-practice guidance concerning primarily preservation in place, not a price estimate for physically relocating mature trees. Its text recognizes that some grading and terrain conflicts make preservation difficult or expensive. Whether this particular guidance was incorporated into enforceable R-7192 requirements has not been established. Read all four original pages ↗
EC-2 is stormwater best-practice guidance, not proof that every R-7192 tree is cheap to save, or that this specific guidance imposes a separate enforceable preservation duty here. The guidance expressly recognizes that saving trees can be expensive or difficult where grading and terrain conflict with the design. Its significance is the distinction between physical necessity and constraints created by a selected layout. See also the 2020 parkland staging proposal, where equipment and supply storage were contemplated on vegetated ground ↓.
Requested design record: dated tree surveys and inventory transmissions, the original alternatives set, grading/utility/staging options, consultant scopes, preservation recommendations, the VIS-2 verification and documented reasons for accepting or rejecting each tree-sensitive alternative.
New primary-document finding · April 2020 · Existing trees and temporary construction use
The April 2020 Shoemaker Bridge Final EIR/EA contemplated staging equipment, vehicles and supplies in an existing park landscape—not a vacant lot. The report expressly acknowledges trees and ground cover; separate aerial and field-atlas evidence documents substantial, established tree canopy across this portion of César E. Chávez Park. This is not an inference from an unlabelled satellite image: the environmental analysis itself identifies a 7.49-acre proposed staging area that includes existing vegetation. A precise, tree-by-tree overlay of the historical staging footprint remains to be completed. Whether this footprint survived into the operative 2026 contractor staging plan is not established.
Area and boundaries. Appendix A, Section 4(f)/6(f), printed page 4-13, places a 7.49-acre staging area south of West Broadway, bounded by West Broadway (north), Ocean Boulevard (south), southbound West Shoreline Drive (west) and Golden Avenue (east). It distinguishes this total footprint from approximately 6.29–6.30 acres calculated as temporary parkland use; some existing roadways were excluded from that accounting.
Existing ecological landscape. The analysis calls this area open space without developed recreational facilities, yet explicitly recognizes trees and ground cover. The landscape is not interchangeable with empty land simply because it lacks built recreational amenities. The proposed use includes construction equipment, vehicles and supplies such as gravel, and the report says the area would be revegetated and improved as park space
afterward (Appendix A, p. 4-13). That wording does not, in these passages, demonstrate replacement of the functions of pre-existing mature trees.
Environmental reasoning. On printed page 4-15, the analysis says the area had no developed recreational facilities and anticipated returning the land in a condition “as good as, or better than” before its use. Its de minimis findings address specified Section 4(f) recreational-resource impacts; the wider study also discusses vegetation and wildlife. We do not claim those ecological effects were wholly ignored. We ask which measurable ecological baselines support the promise of an equivalent—or better—outcome.
Primary citation: Shoemaker Bridge Replacement Project Final EIR/EA (April 2020), Figure S-3 (printed S-17); Appendix A, “Section 4(f) and Section 6(f) Analysis,” printed pp. 4-13 and 4-15. CEQAnet official record ↗ · City Council adoption record and original EIR/EA attachment ↗
“Vegetation” is an extremely broad category. Grass is vegetation. Groundcover and shrubs are vegetation. So is a decades-old tree with a vast crown, structural roots and living habitat. These categories are not interchangeable in ecological function or recovery time.
Our aerial and mapped observations establish substantial existing mature-looking canopy in the park landscape; the 2020 report acknowledges trees within the proposed staging area. But the exact 2020-to-current boundary overlay, individual tree identifiers, ages and disposition decisions remain unverified. We should examine these trees—not erase their identity behind a generic land-cover label.
To revegetate an area may mean establishing groundcover, shrubs, new landscaping and young trees. Even a successful replanting program does not immediately reproduce the existing mature canopy, shade, biomass, root architecture, soil stability, nesting and shelter structures, microclimates or ecological relationships that had developed there. Depending on species, site conditions and survival, comparable functions may take decades to recover, and some relationships may not return in the same form. Transplanting large trees is sometimes possible, but neither promised revegetation nor a planting count establishes that it will happen here—or that it would achieve ecological equivalence.
Even temporary staging can have lasting consequences: equipment, fill and stockpiles can compact soil, injure roots, alter drainage, or affect organisms in canopy, leaf litter and soil. Some existing trees may be safely protected; which ones and under what enforceable measures must be demonstrated against the current work plan.
An accountability test, not a rhetorical promise
More usable park area and improved access can be genuine public benefits. They do not automatically demonstrate that the living ecosystem has been preserved or restored. An ecological baseline would distinguish at least:
The crucial distinction: an area can become green again without regaining the age, structure, ecological relationships or public-health functions of the original mature trees. A promise to revegetate is not, by itself, a promise to restore a living ecosystem.
The California Stormwater Quality Association’s EC-2 guidance on preserving existing vegetation ↗ recommends planning around established plants and keeping temporary roads, stockpiles and work activity away from retained vegetation. See the source-linked EC-2 exhibit ↑. What design-stage and staging alternatives were examined for the mature trees already in this park?
The 2020 Shoemaker Bridge environmental review and the 2026 R-7192 construction procurement belong to related but different stages of project development. A historical proposed footprint must not be presented as a final contractor-approved staging plan. In June 2026 Addendum 2, Question 16, the City describes the bid staging drawings as one possible approach and says the contractor would prepare detailed final staging/phasing. Find Addendum 2 at PW-26-759 ↗.
What the 2020 documents demonstrate: a park area that expressly contained trees and ground cover was contemplated for construction staging and subsequent revegetation—not merely an empty plot awaiting landscaping. What independently supplied imagery adds: extensive established mature-looking canopy in this living park landscape. What remains to establish: the exact historic/current staging overlap with individual trees, whether the relevant trees and habitat face the current work plan, what safeguards and preservation alternatives were assessed, and what evidence supports an ecologically meaningful “as good as or better than” outcome. Review the biologist and habitat questions ↑ · Find the record requests in the accountability array ↓
Evidence moves through distinct stages. The viewer should not mistake any single stage for the next.
Open coordinate-provenance check: An October 17 dossier describes 116 observation markers across 103 distinct coordinates, while both current v1.5/v1.6 site JSON exports store 116 distinct coordinate pairs at stored precision. We have not traced the discrepancy to a particular revision, rounding rule or extraction method. Neither number represents a verified census of individual trees.
The signed plans' DEM Note 7 says trees and shrubs not indicated for removal are generally to be protected unless directed by the Engineer. PL-1 includes an existing tree to be preserved symbol; the investigator's review of the PP sheets has not identified an individual application of that symbol or a comprehensive retained-tree schedule. This is an unresolved implementation question, not a claim that every northern tree lacks protection. [P05–P06: signed plans and specifications]
Correction protocol: identify the observation and source sheet, quote the disputed claim, provide the drawing revision/date and contrary evidence, preserve the earlier version in the correction log, and update the disposition without silently rewriting the history. Contact recipients are asked to review skeptically, not to endorse the analysis automatically.
Third-party satellite and Street View images are attributed investigative reference materials, not automatically licensed for unrestricted public republication. The ZIP preserves full-resolution drawings and ground-level frames; the ground-level viewer groups them by screenshot time rather than independently verified single-position 360° panoramas.
Each entry identifies the institution or role most likely to hold the record, not a person conclusively responsible for a particular decision. A reply is not the same as an answer. Request the record itself, the operative version, and the reasoned decision it documents. Here, “required” distinguishes a documented permit/contract obligation from a record we believe should be disclosed or created; the precise legal production/retention duties need professional confirmation.
| ID · question | Primary documentary anchor | Likely authority / custodian | What would resolve it | Evidence and urgency |
|---|---|---|---|---|
| AQ-030 · Which construction staging plan currently governs the vegetated parkland south of West Broadway? | [P08 · 2020 Final EIR/EA, Appendix A, 4(f)/6(f), pp.4-13–4-15, Figure S-3]; [P17 · June 2026 Addendum 2 Q16] | City Public Works / project Engineer; construction contractor; construction manager; environmental compliance and arboricultural/biological leads | Dated final staging/phasing plans, authorization and version history; tree and habitat inventories overlaid with access/stockpile areas; equipment/root-zone protections; records of alternative staging locations; applicable field inspection instructions. | Historic proposal documented · 2026 operative footprint and living-tree impacts unverified · time-sensitive |
| AQ-021 · Which northern trees face removal or retention? | [P05] DEM-1–20; PL-1; PP-1–24; resident atlas [A1/A4] | Long Beach Public Works; official plan custodian and designated project Engineer | Current uniquely identified existing-tree inventory, latest dated removal/retention plans, and reconciliation with each atlas observation. | Time-critical · final designations not yet recovered |
| AQ-003 · Where is the completed VIS-2 design-stage verification? | [P08] 2020 EIR/EA commitments; [P07] 2019 visual assessment | City environmental-compliance lead; engineering/design reviewers | The completed verification, signoff/date, alternatives and trees conserved due to design decisions. | Unlocated record · document applicability must be authenticated |
| AQ-005 · Why does PL-1 show a preserved-tree symbol without located individual uses? | [P05] PL-1 PDF p.362; PP-1–24 pp.363–386; DEM Note 7 pp.21–40 | City / landscape-design plan author / designated Engineer | Tree-by-tree retained schedule, approved plan revisions, field protection map and relevant graphical markings. | Investigator did not find mapped applications; exhaustive current-revision audit pending |
| AQ-011 · Who verifies before the first irreversible cut? | [P06] Division I §300-1.2.4; [P05] DEM Note 7 | Contractually designated Engineer; construction manager/inspectors; contractor | Signed pre-removal identification, approval and stop-work escalation protocol; field marking and applicable notice. | Urgent · role and procedure require written confirmation |
| AQ-010 · Which removals are physically unavoidable? | [P05] DEM, L, grading and utility drawings; [P08] VIS-2 | City design engineers; preservation-oriented independent engineer/arborist | Documented tree-specific alternatives, constraints, costs and root-zone preservation options. | Unresolved design necessity |
| AQ-007 · What is the actual number of unique trees to be lost? | [P01] City ~170; [P05] DEM marks; [P06] 300 EA bid item | City estimator, Engineer and inspector; contractor for actual measurements | One current unique-tree list with size thresholds, separate clearing/grubbing counts and final change orders. | Different counting units; not a verified contradiction |
| AQ-009 · What will new planting actually provide? | [P01] 500 native; [P05] PL-1=522; [P06] bid=530 | City landscape/environmental team; plant-establishment staff | Approved species/quantity list, planted locations, maturity/canopy projections, survival and monitoring rules. | Plant counts do not measure present canopy |
| AQ-013 · Where is the biologist, and how are living animals and habitat protected? | [P06] §300-1.2.2.1; Addendum 2 (23 June 2026), Q10–Q11, PDF p.7; [P09] Coastal Special Condition 3 (south only) | City environmental staff and separate biologist-procurement custodian; contractor and designated wildlife monitors as applicable | Biologist contract, scope, dated mapped surveys for north/south, protection and encounter protocols beyond nesting birds, worker briefings, stop-work authority, incident and clearance records. See dedicated inquiry ↓ | City committed to procure biologist; completed procurement, scope and field implementation unverified |
| AQ-022 · Which 37 trees were retained within the coastal permit? | [P09] p.18; [P12] special conditions | City permit applicant; California Coastal Commission permit record | Coastal revised before/after plans and individual 44-tree mapping, subsequent approved construction/landscape submissions. | Southern precedent; not northern preservation |
| AQ-015 · Why did the bid introduction omit explicit tree removals? | [P06] Notice Inviting Bids Division A p.A-1 | City Public Works and procurement drafting/approving office | Scope drafting and review history, referenced tree-treatment instructions, explanation of public-facing wording. | Absence in introductory synopsis, not complete contract omission |
| AQ-016 · What public review is still available? | [P13] City forestry policy; [P09] permit conditions | City Public Works; permitting staff; legal counsel for applicability | Notice and appeal rules applying to each tree; current permits; who can pause/review removals. | Urgent · do not presume ordinary street-tree appeal applies |
| AQ-014 · What are retained mature assets worth? | [P04] City inventories/value; existing tree assessments | City urban-forestry data custodian; independent ISA arborist | 2015 park-tree entries (if any for site), per-tree condition, canopy and ecosystem-service appraisal. | Historical valuation citywide, not a local appraisal |
| AQ-018 · Who has been notified and when? | [P01] project announcements; procurement record; tree policy/permit notices | City outreach and project manager; construction coordinator if designated | Dated notifications, alternatives presented, accessible tree-level maps and actual remaining decision opportunities. | Meaningful review may depend on timing |
| AQ-023 · Which trees left standing may be killed later? | [P05] grading, utility, irrigation drawings; [P08] PF-50 (scope to confirm) | Project arborist if assigned; City Engineer; construction inspector | Protection zones, root cuts, compaction plans, arborist inspections and post-construction monitoring. | Standing trunk ≠ protected living system |
| AQ-024 · Who can coordinate an immediate independent review? | [P14] October 2026 council project decision; [P01] project status | Potential lead recipient; City project manager; environmental legal counsel | Named review coordinator, earliest planned clearing date and decision point for feasible retention changes. | Need actionable contact / no verified first-cut date |
| AQ-025 · Who verifies tree identification, protection and removal authorization in the field? | [P15 · Council item 26-56261]; [P17 · signed DEM Note 7 / procurement] | Project Engineer; City inspection lead; Sully-Miller; PMCS under actual executed scope | Executed field responsibility matrix and inspection scope; tree-tag inventory; signed pre-removal checklists; written Engineer instructions; inspector logs; hold/release protocol. | Urgent before any removal or root-damaging work; duty-holder not yet verified |
| AQ-026 · When did contract and delivery deadlines constrain preservation alternatives? | [P16 · Metro 2026-0662]; [P15 · October 6 item] | Metro funding agreement custodian; City Public Works scheduling/design leads; City Manager designee | Baseline schedules, grant award milestone terms, design-decision chronology, risk registers, alternatives considered, change-order impact calculations and actual notice-to-proceed. | Documented financial/schedule pressures; relationship to tree decisions unverified |
| AQ-027 · Who authorized, purchased and oversees the tree-removal pay item? | [P17 · PW-26-759, Addendum 2, Item 46] | Long Beach Public Works, Procurement, Project Engineer and contract administrator | Bid quantity assumptions, unique tree-count reconciliation, signed contract, schedule of values, unit measurement rules, change-order and payment records; distinguish tree removal from clearing vegetation. | 300 EA bid estimate is not an actual tree census |
| AQ-028 · What environmental review duties were purchased from PMCS? | [P15 · RFP PW-25-547]; [P18 · executed contracts portal] | City Council/City Manager; PMCS Group; City Public Works consultant administrator | RFP PW-25-547, PMCS proposal and executed scope, staff qualifications, tree-related inspection and escalation protocols, field reporting requirements. | An inspection contract is documented; its specific tree-verification duties remain unresolved |
| AQ-029 · How did Metro handle the stated tension between urgent financing and planned community-led allocations? | [P16 · Alternatives Considered] | Metro Board and CMIP program staff; City funding liaison; community oversight participants | Board materials, contingency attachments, funding agreement, outreach records, revisions, and identification of which stakeholder process applied to this specific decision. | Metro acknowledged a process tension; this is not evidence that tree protections were waived |
Direct source keys: [P05] = signed 456-page drawing set via PW-26-759; [P06] = project specifications and Addendum 2; [P07–P08] = visual/environmental commitments; [P09–P12] = Commission permit record; [A1/A4] = investigator atlas and DEM reference screenshots. The citation-linked 15-page dossier contains the full source register. An unlocated record is not automatically a nonexistent record.
Numbers and provisions from different geographic boundaries, dates and counting rules must not be treated as mathematically interchangeable. Documented differences can be important without proving wrongdoing. The register identifies precisely what a qualified reviewer should reconcile.
| ID | Records in tension | Current finding / status | Resolution needed |
|---|---|---|---|
| DC-001 | Coastal proposed removals: 65 → 21 | Confirmed revised proposal; same restricted southern permit scope. | Identify 44 trees spared from initial proposal and why redesign worked. [P09] |
| DC-002 | Southern 44-tree group: 37 retained + 7 removed | Scope-specific arithmetic, not 37 northern trees. | Obtain individual 44-tree inventory and approved revised landscape plan. [P09] |
| DC-003 | ~170 public removals / 216 annotations on six DEMs / 300 EA bid | Unreconciled counting and scope; not three verified tree counts. | Map unique tree IDs, payment units, small-vegetation clearing. [P05] |
| DC-004 | Public “500 native” / PL-1 522 (278 native +244 nonnative) / bid 530 | Documented description and accounting differences. | Check geographic scope, revisions, species classification. [P05] |
| DC-005 | Coastal requires Afghan-pine substitution; 69 Afghan pines in PL-1 | Potentially different geography; not proof of violation. | Map 69 pines inside/outside the coastal permit. [P12] |
| DC-006 | Desert Willow common-name corrections vs later planting legend | Possible ongoing schedule label issue. | Check botanical name and revision history. [P05] |
| DC-007 | PL-1 preserved-tree symbol vs PP sheets without located uses | Unresolved individual-designation implementation. | Obtain current stamped complete retention schedule/graphics. [P05] |
| DC-008 | DEM Note 7 protect by default / Engineer may direct removals | Coexisting instructions, not intrinsically contradictory. | Identify authority, approvals and safeguards. [P05] |
| DC-009 | VIS-2 mature-tree minimization / completion record not located | Verification gap; absence from archive ≠ proof never performed. | Obtain final monitoring signoff and alternatives analysis. [P08] |
| DC-010 | Coastal 5-year landscape monitoring vs bid 90-day maintenance | Different obligations may apply to separate parties. | Identify assigned legal responsibility, location and funding. [P12] |
| DC-011 | Procurement synopsis “various Removals” / coastal report explicitly describes tree removals | Confirmed difference in public-facing specificity. | Review bid synopsis authorship and public notice. [P06] |
| DC-012 | Trees recognized as capital assets / removal and waste classification | Valuation/preservation decision pathway not shown. | Find individual asset appraisal and decision records. [P03] |
| DC-013 | Coastal 37 retention commitment / signed construction drawings | Different approved drawing sets may exist. | Match permit-applicant approved revisions to 2026 signed set. [P09] |
| DC-014 | 65 originally proposed coastal removals / 21 after revisions | Earlier alignment not automatically physically necessary. | Identify changed engineering assumptions and trees affected. [P09] |
| DC-015 | Possible DEM-16 label inconsistency on K-1 | Suspected mapping/index error; not confirmed. | Check printed K-1 location, DEM-16 matchlines and adjacent sheets. [P05] |
| DC-016 | Southern coastal preservation vs larger northern grove | Geographic jurisdiction distinction confirmed. | Keep permit and study boundaries separate. [P09] |
| DC-017 | Coastal report 278/244 species quantities / PL-1 totals 278/244 | Possible projectwide schedule reused in limited-area permit report. | Check actual planting geography and permit-approved schedule. [P09] |
| DC-018 | South coastal retention promise / unlocated PP preservation symbols | Implementation documentation still needs examination. | Obtain Commission-approved plans and final field protection maps. [P05] |
| DC-019 | Citywide 2010 street inventory / 2015 park inventory vs project trees | Different inventories and ownership scopes. | Request entries for actual river/park study area. [P04] |
| DC-020 | 2019 VIS-2 assigns Resident Engineer / 2020 VIS-2 assigns City | Documented version difference; intent and legal effect unknown. | Recover revision history and named verifying role. [P07] |
| DC-021 | Historical 103 coordinates / current v0.7 116 coordinates | Superseded count: current 116 distinct pairs. | Correct old dossiers, retain numerical correction trail. Current register |
| DC-022 | 90 provisional DEM assignments / exact tree-symbol matches | Crosswalk is useful but not complete survey or final current plan. | Build per-tree proof and survey-grade polygons if feasible. DEM gallery |
| DC-023 | Environmental review temporary disturbance area: ~62 vs ~46 acres | Historical candidate discrepancy; definitions/scope not yet verified. | Read both dated EIR/visual-impact passages and delineations. [P08] |
| DC-024 | DEM-15/16 existing conditions vs adjacent development (700 West Broadway) | Potential third-party timing/provenance confound. | Identify developer changes separately from R-7192 authorizations. [P05] |
| DC-025 | Capital Improvement Program label vs evidence of net public-asset improvement | A purchase category does not evaluate mature canopy loss, preservation alternatives or total ecological benefit. | Obtain the design alternatives and public value assessment; specify baseline C vs construction B vs preservation-first A. [P17] |
| DC-026 | Separate Sully-Miller construction and PMCS management/inspection awards vs unverified field tree-verification duty | Documented contracting structure; allocation of individual-tree verification duties not yet recovered. | Produce both executed scopes, responsibility assignment matrix, inspection sign-offs and field instructions. [P15] |
| DC-027 | Metro 2028 delivery/federal-award risk vs time needed for preservation-first engineering | Metro confirms deadline and historical funding risk, not that any tree removal was required by the deadline. | Compare grant milestones and critical path against dated alternatives and tree decisions. [P16] |
| DC-028 | Metro staff recognized procedural tension in urgent CMIP funding allocation | Report notes conflict with earlier understood participatory future-funding allocation method, describes urgency as mitigating; no finding of tree-review suspension. | Examine Metro Alternatives Considered, outreach, contingencies and City design/permit history. [P16] |
| DC-029 | October 6 authorized award and Metro up-to-$35m funding vs actual executed contracts, drawdowns and field timetable | Amounts and proposals may not equal signed scopes, completed expenditures or work mobilization. | Get executed agreements, amendments, notices to proceed, grants reporting and current construction schedule. [P15] [P16a] |
Correction preserved: June 23 Addendum 2 moved the TREE AND STUMP REMOVAL line from Item 45 to Item 46 while retaining 300 EA. The 33,000 SF figure belongs to concrete flatwork. It is not evidence of an increase to 33,000 tree removals.
Some relevant records are explicitly contemplated by an adopted environmental commitment, signed construction provision, or coastal permit condition. Others are records that an effective preservation review ought to be able to produce, but are not yet confirmed legally mandatory as standalone documents. The third group consists of analyses this independent inquiry proposes to undertake with professional help.
| Record or answer | Basis | Required/expected status | Next inquiry |
|---|---|---|---|
| Current contractor staging/phasing and vegetated-area protection | 2020 Final EIR/EA Appendix A, printed pp.4-13–4-15; 2026 Addendum 2 Q16 | Historical parkland staging proposed; contractor expected to develop the detailed plan. Actual 2026 plan, accepted revisions and tree-specific measures not yet inspected. | Obtain accepted maps, stockpile/access restrictions, tree protection and habitat controls; reconcile against the 2020 proposal. Primary evidence and map ↑ |
| Completed VIS-2 design minimization verification | 2020 EIR/EA environmental commitment | A documented commitment; final applicability, required format and completion status need record authentication. | Ask for implementation-monitoring table, any written signoff and underlying design alternatives. [P08] |
| Coastal approved final construction plan | CDP 5-25-0393 Special Condition 1, southern area | Permit condition requires submission and job-site availability under its terms. | Request approved version, stamp/date, job-site contact and preconstruction briefing record. [P09] |
| Coastal revised landscape and monitoring | Special Condition 2 as amended, southern area | Permit obligations described; timing, condition details and actual approved submissions to verify. | Get approved tree inventory and five-year monitoring/maintenance responsibility. [P12] |
| Protection of trees not marked for removal | DEM-1–20 Note 7 | Explicit drawing instruction, subject to Engineer direction; not a named-tree schedule. | Identify field maps, trees marked protected, instructions and any Engineer departures. [P05] |
| Authorized tree removal and topping procedure | R-7192 §300-1.2.4 | Contract provision establishes procedure/Engineer role; specific approvals not in reviewed set. | Request operative field approvals, tree ID and stop-work process. [P06] |
| Pre-removal nesting review | R-7192 biological conditions and southern coastal Special Condition 3 | Conditions apply as written in their geographic/seasonal scope; not proof removal necessity. | Request qualified surveys, dated notices and work limitations. [P09] |
| Public notices and possible appeal | City tree policy and permits | Applicability to specific capital-project and park trees remains undetermined. | Ask legal reviewer which notice/appeal rules truly apply. [P13] |
| Complete existing-tree inventory | City 2010 street/2015 park data and design records | Potential existing source; a new project-specific list is sought, not yet shown legally mandatory. | Request historical inventory entries, current as-built locations and tree IDs. |
| Tree-specific value and alternatives analysis | Public-assets stewardship and VIS-2 | Analytical records sought; individual valuations not established as mandatory under cited contract. | Ask engineers and arborists to evaluate retention pathways. |
| Ground-level canopy photos and ecological time series | Independent field atlas and city maintenance | Proposed evidence product, not an identified permit deliverable. | Gather legal images, dates, independent photos, monitoring, conditions after construction. |
| Waste handling and tree-preservation accounting | R-7192 §401-8 (C&D disposal/recycling) | Waste accounting clauses do not themselves measure mature-tree preservation. | Obtain tree materials disposition where recorded; separately count living mature trees saved. [P06] |
| Executed construction contract / tree treatment authority | Council Item 26-56261; R-7192 signed DEM notes | Council award recommendation/approval is public; the executed tree-specific duty scope and subsequent written approvals still require retrieval. | Obtain full Sully-Miller contract, notice to proceed, submittal register, change orders, tree-protection plan and signed Engineer authorizations. [P15, P17] |
| Executed PMCS construction-management / inspection scope | Council Item 26-56261, RFP PW-25-547 | Specific inspection and environmental-tree duties are not established by agenda title alone. | Obtain award, RFP, PMCS proposal, executed statement of work, staff roles and inspection log requirements. [P15, P18] |
| Metro/federal funding deadlines and contingency terms | Metro Board File 2026-0662, Attachments A–B | Funding terms and milestones should be established by executed agreements; a historical $35m gap is not necessarily ongoing. | Obtain Metro agreement, award conditions, schedule milestones, USDOT conditions, changes/waivers and preservation-alternative timing analysis. [P16] |
| Tree-specific pre-removal and protective-field verification | DEM-1–20 Note 7; R-7192 work records | General protection-by-default instruction is documented; the tree-by-tree verification record and who signs it remain unlocated. | Request removal permits if applicable, numbered inventory, photos of markings, Engineer orders, tree-protection barriers, inspector signoffs, work holds. [P05, P17] |
The historical research began with public assets and institutions beyond one road: functioning school facilities, mature trees, history-bearing structures and prior public investments. The concern is whether development systems genuinely count what already exists before claiming progress through replacement. This broader hypothesis—sometimes discussed as a destructive institutional attractor—requires independent testing. It is not a finding of anyone's corrupt intent.
Original investigation index T01–T20: a later handoff accidentally reassigned some identifiers. The following keeps the recovered historical meanings intact. The separate O01–O15 omission audit, E01–E25 evidence inventory, current AQ questions and DC discrepancies must not be renumbered into one another.
| Original thread | Inquiry | Original thread | Inquiry |
|---|---|---|---|
| T01 | Original canopy | T11 | Ecological value |
| T02 | Historical inventory | T12 | Public financial assets |
| T03 | Design chronology | T13 | Community health |
| T04 | VIS-2 compliance | T14 | Public process |
| T05 | Removal accounting | T15 | Coastal revisions |
| T06 | Endangered retained trees | T16 | Development coordination |
| T07 | Engineering alternatives | T17 | Institutional incentives |
| T08 | Professional responsibility | T18 | Community history |
| T09 | Landscape architecture | T19 | Related public losses |
| T10 | Replacement discrepancies | T20 | Intervention and remedies |
Further analytical tools: compare three future pathways—preservation-first design (A), approved construction (B), and the existing/no-build baseline (C)—at multiple time horizons, including decades needed for replacement canopy to mature. Track four different land-cover changes: mature canopy removed; mature canopy retained and protected; vegetation converted to hardscape; and already-disturbed land converted to functional green space. Compare actual shade, survival, habitat, access and public costs rather than just planting counts.
Historical sources also lead to early park-tree inventories, 2017 citywide valuation, the earlier 2019 VIS-2 allocation to a Resident Engineer, the 2020 environmental documents, the 2025 coastal redesign, 2026 signed drawings, and the city’s October 2026 contract decision. Reconstruct the chain of custody and design responsibility without treating every named consultant or official as the actual 2026 removal decision-maker.
R-0065, the proposed 50-year comparison: Compare (A) preservation-first design, (B) the approved construction design, and (C) the continued existing/no-build landscape. Compare not only numbers planted but canopy maturity, location-specific shade and exposure, habitat, survival and mortality, maintenance costs and public benefits over time. This is a research plan; no fifty-year model results have been calculated or validated. The no-build scenario is a comparison baseline, not an assertion that the public should abandon transportation and accessibility improvements.
A comparative investigation does not need to establish one shared institutional cause in advance. It can document outcomes that deserve examination in their own right: fewer established trees, reduced mature shade, and public processes whose ability to change destructive decisions before cutting remains a concrete question. For each project, assess the source, tree definition, actual losses, public involvement, and design changes separately.
Long Beach's official project account ↗ reports 87 initial trees; 39 removed, including 11 classified in good condition that were removed for greenspace expansion and pedestrian-trail design. The same account reports 12 trees previously slated for removal were saved by plan modifications; it describes outreach extending across multiple years and arborist oversight.
This documents genuine losses and design-responsive preservation within the same project. It does not justify saying no outreach occurred. The inquiry is what residents were told, whether healthy-tree alternatives were considered early, and when participation could still alter the outcome.
In an August 5, 2026 investigation ↗, Streetsblog LA's Joe Linton reports 174 trees affected by freeway widening and provides before-and-after photographs dated January 2024 and August 2026 from 67th Street and nearby cross streets. Its reporting describes residents' protests and objections from elected officials—evidence that people spoke, not that their objections prevented removal. The reported tree figure should be reconciled with operative Metro/Caltrans records.
Metro's project page ↗ describes an eastbound safety/auxiliary-lane project and bridge widenings. The Streetsblog article inconsistently calls the new lane westbound in one paragraph and eastbound in another. For this comparison we describe the North Long Beach SR-91 corridor without treating that conflicting directional wording as resolved.
The two cases differ in design purpose, location, jurisdiction, tree conditions, and reported public-engagement history. This panel is comparative evidence of effects and intervention opportunities, not a finding of corruption, coordinated intent, or identical environmental-law violations. It is fair to ask whether a nominal replacement-tree commitment restores mature shade to the same neighborhood at the time it is lost.
“Stakeholders” is useful administrative vocabulary here—people and institutions whose interests, duties or work may be affected. It is not a claim that public spaces are ordinary commercial products or that residents are merely consumers. The grove is a shared civic and ecological inheritance. Relevant participants include nearby residents, park users, pedestrians, cyclists, children, schools, people experiencing heat exposure, urban-forest workers, designers, contractors, community historians, wildlife and the ecological systems affected.
| Audience or role | Most useful action | Records / expertise needed |
|---|---|---|
| Residents, neighborhood and park users | Verify which mature groves, trails, shaded gathering areas and local benefits face change. | Accessible location maps, existing-condition photographs, participation timing. |
| ISA arborists and canopy scientists | Assess living tree condition, critical root zones, realistic survival and mature canopy functions. | Field inventory, root protection, grading and irrigation plans. |
| Civil/transport and landscape engineers | Test road/utility/path alignments and preservation-first alternatives. | Latest L/G/U/DEM/PP sheets; VIS-2; coastal revision history. |
| Environmental attorneys and regulatory specialists | Assess binding obligations, notice/remedies and any prudent pause mechanism. | Final EIR/EA, permit conditions, completion reports, current authorization. |
| City / contractor / inspectors | Clarify actual authority, field tree identification, work schedule and change process. | Stamped current plans, Engineer instructions, stop-work escalation and monitoring. |
| FoLAR, urban-forest and environmental-justice groups | Recruit independent reviewers and coordinate affected communities and habitat expertise. | Evidence brief and atlas, current tree risk zones, local history. |
| Sierra Club and coastal permit participants | Recover documentation of the southern redesign and methods used to spare trees. | CDP 5-25-0393 file, 65→21 changes, 37 retained southern tree identities. |
| Journalists and public-interest newsrooms | Independently verify, explain the public implications and seek documentary responses. | Exact source citations, photo locations, authoritative quotes and unanswered questions. |
| School communities, people susceptible to heat, future park users | Describe how public green space is experienced and where shade loss matters. | Local access, shade, heat, mobility and public-health measurements. |
New follow-through: direct a contract-scoping request to Public Works and the City Clerk; request the inspection-services scope for PMCS Group (PW-25-547), the executed construction contract for Sully-Miller (R-7192), and Metro agreement milestones (Board File 2026-0662). These names designate parties to publicly described transactions, not adjudicated responsibility for a particular tree. Sources and accountability questions ↓
Current release policy: the originating investigator expressly authorizes responsible forwarding of the current outreach materials and invites recipients to find the people who can lead. Do not wait for the investigator to manage every referral. The earlier request for prior consultation before forwarding is superseded. Readers should preserve citations and uncertainties; no organization has independently endorsed this investigation by receiving it.
Two parallel tracks, neither held hostage by the other: immediate protective review of still-standing trees, and continued documentary accountability after that review begins. If possible, confirm an actual coordination lead, the current clearing/cutting schedule, relevant agency contacts, and the review mechanism capable of authorizing a pause or design change where warranted. There is no verified scheduled date for the first cut in this record.
Action toolkit · Transfer the work to those with expertise or authority
The originating investigator cannot indefinitely act as the community's arborist, engineer, attorney, records custodian, reporter and organizer. Forward this investigation. Assign a responsible reviewer. Verify the records. Act while trees are standing. The materials are offered in good faith, with corrections welcomed.
Forwardable contract question: Who must authorize, mark, inspect and record the disposition of each existing tree before cutting or damaging roots? Please request the executed construction and inspection contracts, the current tree-specific plan, and all applicable dated field approvals. Read the evidence and exact responsible roles ↓
Start with the 2-page action brief, then share the cited evidence dossier and interactive geographic evidence. A recipient should not need to wait for the originating investigator before seeking qualified help or following a public-records process.
Find out when topping, clearing, felling, grading or root disturbance could begin. Do not infer a date from contract approval.
Obtain current plans, original survey transmissions, the completed VIS-2 record, written Engineer instructions and the actual tree-specific disposition.
Ask a qualified arborist and relevant engineers which trees and root systems can remain through feasible design, grading or construction changes.
Where justified, ask for a focused pause on irreversible work while unresolved material preservation questions are professionally reviewed.
These are organizations or newsrooms whose public missions or coverage may be relevant—not endorsements of this investigation or promises to respond. Recipient details may change.
| Recipient / organization | Potentially helpful role |
|---|---|
| California ReLeaf ↗ | Urban-forestry networks, grassroots referrals |
| TreePeople ↗ | Community forestry, climate and green-space policy |
| Friends of the Los Angeles River ↗ | River access, restoration and community knowledge |
| Riverpark Coalition ↗ | Los Angeles River-adjacent public-land and restoration interests |
| Los Angeles Waterkeeper ↗ | Watershed policy and legal/environmental advocacy |
| Sierra Club — Angeles Chapter ↗ | Conservation networks and coastal participants |
| LAist / KPCC story tips ↗ | Editorial review; no coverage or confidentiality implied |
| Long Beach Post newsroom ↗ | Local public-interest journalism and project accountability |
| City of Long Beach PRA ↗ | Records request to the City; identify document custodian |
| City of Long Beach R-7192 project ↗ | Official project facts and public inquiry route |
Open, copy and personalize an appropriate message. Every template includes the current public site link, preserves source-traceability and distinguishes resident observations from official findings. No message is sent automatically.
When requesting records: distinguish (a) an existing record an agency may hold or be legally required to maintain, (b) a completed record we have not located, and (c) a new analysis we propose. The California Public Records Act supplies a request process; it does not necessarily compel a City to create our preferred new spreadsheet or model. City PRA instructions ↗
Reader navigation
Correspondence · Evidence · Independent review
Thank you to everyone willing to help protect the existing mature trees, the wildlife and habitats they support, and the communities that depend on this living landscape. Your time, expertise, corrections, and referrals are genuinely appreciated.
Gabriel Filangine
Independent Conservation Inquiry
Before the Trees Become Waste
Email: BeforeTreesBecomeWaste@proton.me
We welcome correspondence from residents, arborists, ecologists, wildlife biologists, civil and landscape engineers, public-interest attorneys, historians, journalists, community groups, and anyone with relevant records, expertise, or constructive criticism.
A note about reply times: I may not always be able to reply in a timely manner. I will do what I can to respond, provide helpful clarification, share relevant supplementary materials, and offer assistance within my capacity. Thank you for your patience and understanding.
Publicly available starting points include the evidence dossier (PDF), the forwardable action packet (PDF), and the source-linked research library. The outreach toolkit provides editable messages and records-request prompts.
Additional source documents, image and map references, technical crosswalks, and other research materials may be made available on request, as appropriate and subject to provenance, privacy, source-use restrictions, and practical availability.
If you identify an error or have dated photographs, relevant approvals or revisions, biological survey records, or independent technical findings, please get in touch. Independent scrutiny and constructive correction are welcome; no endorsement by any contacted organization is implied.