{"id":396227,"date":"2017-10-30T09:57:13","date_gmt":"2017-10-30T13:57:13","guid":{"rendered":"https:\/\/ntrs.nasa.gov\/search.jsp?R=20170010274"},"modified":"2017-10-30T09:57:13","modified_gmt":"2017-10-30T13:57:13","slug":"trajectory-specification-for-terminal-air-traffic-pairwise-conflict-detection-and-resolution","status":"publish","type":"post","link":"https:\/\/spaceweekly.com\/?p=396227","title":{"rendered":"Trajectory Specification for Terminal Air Traffic: Pairwise Conflict Detection and Resolution"},"content":{"rendered":"<p>Abstract: Trajectory specification is the explicit bounding and control of aircraft trajectories such that the position at each point in time is constrained to a precisely defined volume of space. The bounding space is defined by cross-track, along-track, and vertical tolerances relative to a reference trajectory that specifies position as a function of time. The tolerances are dynamic and will be based on the aircraft navigation capabilities and the current traffic situation. A standard language will &#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Abstract: Trajectory specification is the explicit bounding and control of aircraft trajectories such that the position at each point in time is constrained to a precisely defined volume of space. The bounding space is defined by cross-track, along-tra&#8230;<\/p>\n","protected":false},"author":60,"featured_media":615444,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-396227","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/396227","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/users\/60"}],"replies":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=396227"}],"version-history":[{"count":1,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/396227\/revisions"}],"predecessor-version":[{"id":396228,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/396227\/revisions\/396228"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/615444"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=396227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=396227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=396227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}