anchor.diff:  
   Unlike ICAO idents, navaid idents are not globally unique. AVWX determines the most likely coordinate pair based on the next known coordinate. If the final coordinate is still multiple choice, it will pick the two nearest ones and start backfilling. It is highly recommended to bookend each flight path with either ICAO idents or coordinate pairs, but VOR to VOR navigation will still work.
   
  +Because there are many overlaps between navaid and IATA codes and the navaids are more useful for flight routing purposes, IATA codes are not supported in a flight path. You'll need to use the airport's ICAO code or coordinates.
  +
   Each routing response with include the resolved coordinates used for determining the flight path.
   
   ## Station [/station/{ident}{?format}]
  
positive.code: + Parameters
      + report: `mav` (string) - GFS report type
          + Supported: `mav`, `mex`
      + location: `KJFK` (string) - ICAO station ident or coordinate pair
          + Examples: `EGLL`, `51.47,-0.4`
      + options: (string, optional) - Additional options to include as comma-separated string
          + Supported: `info`
  
negative.code: 
  ### Get METAR Report [GET]
  
  Get the METAR for a specific station by ICAO & IATA station code or a lat,lon coordinate pair. The API will return the station nearest to those coordinates. Include `info` in the options to get details about the selected station.
  
  + Request
  
  