This is the operator reference for the Kershaw County Ground Report -- Resource Status hub. It defines:
- Standard object names for all ten resource categories
- Comment field format for APRS transmissions
- Two-letter status and specifier codes
- How the format applies across all intake modes
Intake modes covered:
- APRS object beacons
- Winlink form submissions
- Meshtastic messages
All operators contributing to KCGR are expected to use these standards. Consistent formatting allows hub operators to cross-reference reports across radio modes and post accurate, timestamped information to the resource map without ambiguity.
This reference is also available as a PDF suitable for printing and storing in your go-box. Distribute the PDF to your club and mutual aid partners well before hurricane season -- lead time is one of the advantages we have over earthquake response.
For the live resource hub with map, weather, and power outage panel, see the link in the footer.
APRS object names are fixed at 9 characters, padded with spaces if shorter. All KCGR objects use the KCGR- prefix.
Object names are self-describing by design. Any operator seeing one for the first time on their display understands it without a reference card -- unlike numbered code systems that require a lookup table.
Objects are listed in life-safety priority order:
- Shelter and medical first -- immediate survival
- Roads third -- determines if shelter and medical are reachable
- Water and food -- short survival window
- Fuel, power, cell, ATM in descending urgency
- Health and welfare relay last -- important but not immediate survival
File the most critical observations first if time or conditions are limited.
| Object Name | Meaning | Specifier Codes |
|---|---|---|
| KCGR-SHLT | Emergency shelter | CA capacity available NP no pets PP pets ok MO medical only |
| KCGR-MED | Medical facility | ER emergency room UC urgent care PH pharmacy OP open CL closed |
| KCGR-ROAD | Road / bridge status | OP passable CL closed CA caution BR bridge FL flooding TR trees/debris |
| KCGR-H2O | Potable water | DP distribution point BO boil order UK unknown quality |
| KCGR-FOOD | Food / restaurant / grocery | HF hot food GR grocery BT both |
| KCGR-FUEL | Fuel availability | GS gasoline DS diesel PP propane AL all three |
| KCGR-PWR | Power / charging / generator | GN generator CH device charging UT utility restored |
| KCGR-CELL | Cell signal location | AT AT&T VZ Verizon TM T-Mobile AL all carriers |
| KCGR-ATM | ATM / financial access | OP operational CL closed LM cash limited |
| KCGR-HW | Health & welfare relay | OP relay available HR hours follow NM no message limit |
If your observation does not fit cleanly into one of the ten object types, file it in the closest category and clarify in the comment field. When in doubt, KCGR-SHLT or KCGR-FOOD cover the widest range of general welfare reports.
SPEC 2-character specifier -- object-specific category detail
LOCATION abbreviated place name or road designation
DDHHMM local time: day / hour / minute -- always last
Fields are ordered most-critical to least-critical. A message that gets cut short loses its timestamp before it loses its location or status. Status and location survive even the worst signal conditions.
- Use a single space between fields
- Run words together when character count demands it -- drop the space, not the data
- DDHHMM is always last so any cutoff loses time before meaning
- Local time -- no UTC conversion required from field operators
If a message is received without a timestamp, the hub operator notes it as time-unconfirmed and watches for a follow-up. All of the following are acceptable:
- Full DDHHMM -- day, hour, and minute
- DDHH -- day and hour only
- DD -- day only
- No time field at all
A message missing its status code is not acceptable. Always lead with ST and SPEC.
| Code | Meaning | Notes |
|---|---|---|
| OP | Open / operational | Resource is available and functioning at time of observation. |
| CL | Closed | Resource is not available. File a follow-up if status changes. |
| LM | Limited | Available but restricted -- hours, supply, or capacity. Clarify in comment field. |
| UK | Unknown | Not verified by direct observation. Use sparingly -- report what you know. |
| CA | Caution | Accessible but hazardous or unreliable. Clarify in comment field. |
Each card shows the raw comment string as it would appear on an APRS display, followed by its plain English meaning.
Amber cards show incomplete messages -- cut short before the timestamp, but location and status are intact and still actionable.
The KCGR object prefix and ST/SPEC codes work on all three platforms. Use the compressed format on APRS where character count is strict. Expand to plain English on Winlink and Meshtastic where space allows.
- Prefix all objects with
KCGR- - Repeat beacon every 10-30 minutes during active reporting
- Send a kill message when the condition is resolved
TO:
AA4TE Subject: KCGR-RSThe form uses the same ten categories and ST/SPEC codes. Full plain English notes are encouraged -- no compression needed. Works via HF or VHF when internet is down.
The KCGR-RS form is under development for inclusion in the SC ARES SC STATE FORMS library alongside the Palmetto Resource Request form. Unlike the Palmetto RR which requests inbound resources, KCGR-RS reports outbound observed conditions. File both during active events when possible.
Example:
KCGR-ROAD CL TR US601 north of Fairfield Rd. Large pine blocking both lanes. Chain saw needed. Observed 262145Operators in mutual aid areas outside Kershaw County should use their local prefix when that system is active:
MGS- for Midlands, SCGR- for statewide.
Plain English definitions for terms used in this reference that may not be familiar to all operators.
was designed under three constraints:
1. APRS object comment field
limit of 43 characters
2. No numbered codes requiring
a lookup table under stress
3. Graceful handling of messages
cut short by poor conditions
All design decisions flow from
constraint 1. The NTS ARL numbered
radiogram system (90+ codes) was
considered and rejected. ARL codes
require memorization or lookup.
KCGR-ROAD and KCGR-FUEL are
self-describing to any operator
seeing them for the first time.
Field order (ST SPEC LOCATION
DDHHMM) places most-critical data
first. DDHHMM is always last so
a cut message loses time before
it loses location or status.
Status and location survive even
the worst signal conditions.
deliberately. A general or
miscellaneous object was proposed
and rejected -- operators filing
to the nearest category produces
more consistent, mappable data
than an undefined catchall.
If an observation truly fits no
category, KCGR-SHLT or KCGR-FOOD
are the broadest containers.
A light/dark display toggle was
proposed for this page and deferred.
Adding theme switching requires
JavaScript and additional CSS,
increasing page weight. This page
is explicitly designed to load
under degraded conditions. Dark
theme was chosen permanently for
readability in field conditions
and nighttime use.
KCGR-ROAD TR (trees/debris) was
added specifically because chain
saw operators self-deploying to
clear roads is documented community
behavior during Helene recovery.
KCGR- Kershaw County (5 chars)
MGS- Midlands (4 chars)
SCGR- South Carolina (5 chars)
MGS- gains one character in the
object name field. SCGR- matches
KCGR- exactly, so object names
port to the state level without
restructuring.
The prefix is the only redundant
element at Midlands and state level.
Field order and specifier codes
are load-bearing. Proposed changes
should shorten or replace the
prefix before modifying field
order or eliminating codes.
Developed June 2026 by AA4TE,
Camden SC, EM94. KC4RC / Kershaw
County ARES. Not a final standard
-- for review by Kershaw County
ARES EC, Midlands Section 3,
and SC ARES.