payload_configuration documents describe a payload (no prizes for guessing that).
They contain instructions to habitat: how to parse telemetry that listeners upload;
and radio settings: how to setup listeners' radios.
If you fly one payload multiple times, you shouldn't have to change payload configuration document.
flight documents describe the time and date of a planned flight. They allow us
to add the flight to the calendar, set the title on the tracker, and select only relevant
telemetry to go into the flight archive (i.e., exclude test data).
A flight document contains a list of payload configuration documents - i.e., the payloads that are going to be launched. You can add more than one, if there are several payloads on one balloon/flight train - but for multiple launches, create a flight document per balloon.
I've just programmed my brand new payload, and am now testing it.
You only need to create a payload_configuration document using the "new format wizard".
I'm going to launch a balloon soon.
Create a flight document, then ask on IRC for the doc to be approved.
Note that you may also create documents by copying and modifying the last document you created for your payload, so you need not start from scratch each time.
The sentence and radio settings in a payload configuration document are ordered lists: the first sentence format that matches successfully is used, and the first item in the radio list is the default.
You can't edit documents once they're saved. You can however load, modify and save a new copy of your configuration document: habitat will use the newest version.
Flight documents are only valid for an amount of time, preferably as small as possible. Parsed strings that don't belong to an active flight document are treated as 'test' uploads, and will only be shown in the testing section of the new tracker.
Since anyone at all can create flight documents, they must be checked before they appear on the various websites. Payload configuration documents referenced by approved and active (within the launch window) flights are given priority when parsing.
Please tell habitat how to convert all of your sensor readings into their relevant SI base or derived unit without a metric prefix (except: use Celsius for temperature; degrees for latitude, longitude, heading; kilograms for mass). For example: Volts for battery readings, Pa (not kPa) for pressure, m/s for speed. You can scale your fields with habitat, your payload need not do the conversion.