Most of the services will output routing and time data in different formats. The OutputSettings POST data specifies how often the data should occur and in what format it will be delivered. Routing data can be delivered in either Earth-Fixed or Earth-Inertial coordinates, and can be formatted as Latitude/Longitude/Altitude or Cartesian X/Y/Z. Note that inertial data can only be represented as X/Y/Z.
Dates and times are represented as either a date-time string in UTC, or as an offset from some initial time. The offset is in seconds, and is offset from the route or analysis start time.
{ "Step": 60, "TimeFormat": "Epoch", "CoordinateFormat": {"Coord":"LLA"} or {"Coord":"XYZ","Frame":"Inertial"} or {"Coord":"XYZ","Frame":"Fixed"} }
{"Coord":"LLA"}
All airspace services use an AirspaceOptions parameter that allows you to select which Airspaces you want to use in the analysis. Because the sheer number of possible airspaces is so large, we offer these filtering options to reduce the number of airspaces to search for intersections or display. You can select airspaces using the following methods.
Note that with the exception of the exact airspaceId method, all of these methods can be used together to filter the large list of airspaces down to your desired list.
Airspace categories can be set to reduce the total number of airspaces to search through. The airspace categories are:
This method is the fastest. If the options parameter AirspaceIds has data in it, and the options parameter Search is false, the service will assume AirspaceIds contains exact airspace names and use only these airspaces. No other searching or filtering will be done for additional airspaces.
If you have a partial airspace name or names, you can put them in the AirspaceIds parameter and set the options Search parameter to true. This will tell the service to search for and return any airspaces that have the supplied partial name in their full name.
Note that the search is case sensitive and many airspaces use all capital letters in their names.
If you know the area you are in, you can search for airspaces by location. Specify the latitude and longitude in the RegionCenter parameter and value for the RegionRadius and set UseRegionalAirspaceQuery to true to search for airspaces in a circular region.
You can limit your search to those airspaces that touch the surface of the Earth. To enable this constraint, set the OnSurface parameter to true.
{ "AirspaceIds": ["AirspaceId1","AirspaceId2"], "Categories": ["ControlledAirspace","Laanc"], "OnSurface": false, "RegionCenter": {"Latitude":15.34,"Longitude": -120.92}, "RegionRadius": 50000, "Search":false, "UseRegionalAirspaceQuery": true }
Some of the services allow you to specify a site object as part of the post data. Since this is not a route type, it is not listed in the routing section.
Where sites can be used, they can be defined as follows:
{ "Location": { "Latitude":40.0012, "Longitude":-75.661, "Altitude":19.0 }, "MeanSeaLevel":true, "OutputSettings": {} }