# MtrPt

Military Training Route point data containing geographic coordinates and associated NAVAID information for each route point

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

> Ordered by ROUTE_TYPE_CODE, ROUTE_ID, ROUTE_PT_SEQ. However, the unique record key uses ROUTE_PT_ID instead of ROUTE_PT_SEQ. Sequence numbers are in multiples of ten.

## Example query

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

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 |  |  |
| `routeTypeCode` | `RouteTypeCode` | MTR Type Code indicating whether the route is IFR or VFR |  | `IR`=IFR; `VR`=VFR |
| `routeId` | `String` | Route Identifier. Along with ROUTE_TYPE_CODE creates a unique MTR identifier |  |  |
| `artcc` | `String` | List of ARTCC Idents that the MTR traverses. Multiple ARTCCs separated by spaces when route crosses multiple centers |  |  |
| `routePtSeq` | `Int` | Sequencing number in multiples of ten. Points are in order as adapted for the given MTR. Not used as part of unique key; see ROUTE_PT_ID |  |  |
| `routePtId` | `String` | Route point identifier. Used as part of the unique record key instead of ROUTE_PT_SEQ |  |  |
| `nextRoutePtId` | `String` | The next sequential ROUTE_PT_ID following this point along the route |  |  |
| `segmentText` | `String` | Concatenation of segment text preceded by the segment text sequence number, describing the segment between this point and the next |  |  |
| `latDeg` | `Int` | MTR route point latitude degrees component | degrees |  |
| `latMin` | `Int` | MTR route point latitude minutes component | minutes |  |
| `latSec` | `Float` | MTR route point latitude seconds component | seconds |  |
| `latHemis` | `LatHemis` | MTR route point latitude hemisphere indicator |  | `N`=North; `S`=South |
| `latDecimal` | `Float` | MTR route point latitude expressed in decimal degrees format | degrees |  |
| `longDeg` | `Int` | MTR route point longitude degrees component | degrees |  |
| `longMin` | `Int` | MTR route point longitude minutes component | minutes |  |
| `longSec` | `Float` | MTR route point longitude seconds component | seconds |  |
| `longHemis` | `LongHemis` | MTR route point longitude hemisphere indicator |  | `E`=East; `W`=West |
| `longDecimal` | `Float` | MTR route point longitude expressed in decimal degrees format | degrees |  |
| `navId` | `String` | Identifier of the related NAVAID associated with this route point |  |  |
| `navaidBearing` | `Int` | Bearing of the NAVAID from the route point | degrees |  |
| `navaidDist` | `Int` | Distance of the NAVAID from the route point | nautical miles |  |

## Column provenance

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

| GraphQL field | SQLite column |
|---|---|
| `effDate` | `EFF_DATE` |
| `routeTypeCode` | `ROUTE_TYPE_CODE` |
| `routeId` | `ROUTE_ID` |
| `artcc` | `ARTCC` |
| `routePtSeq` | `ROUTE_PT_SEQ` |
| `routePtId` | `ROUTE_PT_ID` |
| `nextRoutePtId` | `NEXT_ROUTE_PT_ID` |
| `segmentText` | `SEGMENT_TEXT` |
| `latDeg` | `LAT_DEG` |
| `latMin` | `LAT_MIN` |
| `latSec` | `LAT_SEC` |
| `latHemis` | `LAT_HEMIS` |
| `latDecimal` | `LAT_DECIMAL` |
| `longDeg` | `LONG_DEG` |
| `longMin` | `LONG_MIN` |
| `longSec` | `LONG_SEC` |
| `longHemis` | `LONG_HEMIS` |
| `longDecimal` | `LONG_DECIMAL` |
| `navId` | `NAV_ID` |
| `navaidBearing` | `NAVAID_BEARING` |
| `navaidDist` | `NAVAID_DIST` |