# MaaShp

Polygon boundary coordinate points defining the shape of each MAA

**Source:** NASR table `MAA_SHP` · version `e25086c3e952` · effective 2026-04-16

> Ordered by MAA_ID, POINT_SEQ. References MAA_ID in MAA_BASE. Points should be connected in sequence to form the MAA boundary polygon.

## Example query

```graphql
# Introspect the MaaShp type in GraphiQL at https://api.nav.sortie.co/graphql
# Example shape (pair with a compatible root query field):
{
  # ...rootQuery... {
    effDate
    maaId
    pointSeq
    latitude
  # }
}
```

Run at https://api.nav.sortie.co/graphql (GraphiQL available in-browser).

## Fields

| Field | Type | Description | Units | Enum |
|---|---|---|---|---|
| `effDate` | `String` | The 28-day NASR Subscription Effective Date in format YYYY/MM/DD |  |  |
| `maaId` | `String` | Unique identifier for a Miscellaneous Activity Area; references MAA_ID in MAA_BASE |  |  |
| `pointSeq` | `Int` | Unique sequence number for MAA polygon coordinate points, defining the order in which points form the boundary |  |  |
| `latitude` | `String` | Latitude of the MAA polygon boundary coordinate point, formatted as DD-MM-SS.SSSSh |  |  |
| `longitude` | `String` | Longitude of the MAA polygon boundary coordinate point, formatted as DDD-MM-SS.SSSSh |  |  |

## Column provenance

Every field maps 1:1 to a column in the `MAA_SHP` table of `nasr.db`. Original FAA column names:

| GraphQL field | SQLite column |
|---|---|
| `effDate` | `EFF_DATE` |
| `maaId` | `MAA_ID` |
| `pointSeq` | `POINT_SEQ` |
| `latitude` | `LATITUDE` |
| `longitude` | `LONGITUDE` |