Graham McIntire
82e97e5e31
- Added position_ambiguity field (integer, 0-4) to packets table - Created migration to add the new database column - Updated packet schema and processing to extract position ambiguity - Position ambiguity levels indicate precision of reported coordinates: - 0: No ambiguity (exact position) - 1: ~0.1 mile ambiguity - 2: ~1 mile ambiguity - 3: ~10 mile ambiguity - 4: ~60 mile ambiguity - Automatically captures ambiguity level when parsing APRS packets - All tests pass with no failures 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
9 lines
191 B
Elixir
9 lines
191 B
Elixir
defmodule Aprsme.Repo.Migrations.AddPositionAmbiguityToPackets do
|
|
use Ecto.Migration
|
|
|
|
def change do
|
|
alter table(:packets) do
|
|
add :position_ambiguity, :integer
|
|
end
|
|
end
|
|
end
|