The only fishing data API that doesn't suck.

Overview

We took 11 states worth of scattered government fishing data and turned it into something developers can actually use.

No XML nightmares. No FTP servers from 1997. No “contact your regional biologist” dead ends.

Just clean JSON, real coordinates, and data that updates fast.

The Technical Flex

5-Layer Data Enrichment (PA & AK showcase)

Most fishing APIs give you a water body name and maybe some stocking dates.

We built a multi-layer enrichment pipeline that turns raw government data into location intelligence.

Pennsylvania — The Gold Standard

RAW DATA (PFBC):
{
  "waterBody": "Bald Eagle Creek",
  "section": 4,
  "upperLimit": "RT 150 BRIDGE",
  "lowerLimit": "1/4 MILE DOWNSTREAM AARONSBURG"
}

↓ ENRICHMENT PIPELINE ↓

ENRICHED OUTPUT:
{
  "waterBody": "Bald Eagle Creek",
  "section": 4,
  "latitude": 40.96422,           // PASDA GIS Layer (88% coverage)
  "longitude": -77.74758,
  "waterType": "Stream",           // Smart inference
  "region": "South Central",       // Geographic context
  "freshness": "Fresh (2 days)",   // Trip planning intelligence

  // SECTION-LEVEL GEOCODING (NEW!)
  "sectionLengthMiles": 1.2,       // Haversine calculation
  "elevationChange": -15,          // Open-Elevation API
  "sectionGeometry": {             // Map-ready GeoJSON
    "type": "LineString",
    "coordinates": [[-77.7480, 40.9650], [-77.7470, 40.9630]]
  },
  "sectionCoordinates": {
    "upperLimit": { "lat": 40.96562, "lng": -77.74758, "elevation": 850 },
    "lowerLimit": { "lat": 40.96282, "lng": -77.74758, "elevation": 840 }
  }
}

PA Enrichment Layers

1. PASDA Coordinate Fusion → 88% GPS accuracy (1,130 locations)
2. Water Type Inference → Stream/Creek/River/Lake classification
3. Facility Intelligence → Hatcheries, ramps, state parks
4. Geographic Context → North/South/Central regions