The devDependency tap-min was updated from 1.2.2 to 1.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap-min is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

may related to #35

the used endpoint https://data-live.flightradar24.com/zones/fcgi/feed.js (in radar.js) is now redirected to https://www.flightradar24.com/static/legacy/feed.json so this module does'nt work anymore.

Did not dig into the website if the new url is usable (may with changed parameters).

At the moment the other endpoint https://data-cloud.flightradar24.com/zones/fcgi/feed.js is still working so a quick fix would be to replace this ...

Version 0.5.21 of moment-timezone was just published.

This version is covered by your current version range and after updating it in your project the build failed.

moment-timezone is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi! Great client app.
Would it be possible to search on callsign or flight?

Trying to use this library within a React app, and making calls from the app running on localhost yields a 418 response code. Am I missing some setup step, or why is this happening?

Version 1.2.2 of tap-min just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tap-min is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Please write more clearly that those numbers actually represent!
I think they mean the bounding box of:

• Northern edge latitude
• Western edge longitude
• Southern edge latitude
• Easter edge longitude

# radar(north, west, south, east)
const radar = require('flightradar24-client/lib/radar')
radar(53, 13, 52, 14)

The fun part is of course converting distance (in km) to the correct (lat,lon)'s.

Version 0.5.15 of moment-timezone was just published.

This version is covered by your current version range and after updating it in your project the build failed.

moment-timezone is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 5.0.1 of fetch-ponyfill was just published.

This version is covered by your current version range and after updating it in your project the build failed.

fetch-ponyfill is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Please add some instructions how to use this.
I.e. The steps from git clone, to terminal json output. Perhaps like this:

$  npm install flightradar24-client
...
$ # Edit the file below so that:
$ cat getplanes.js

#!/usr/bin/node
const radar = require('flightradar24-client/lib/radar')
radar(53, 13, 52, 14)
.then(console.log)
.catch(console.error)

$ # Run with:
$ ./getplanes.js

[ { id: '103b6cbc',
    registration: 'D-AKNT',
    flight: 'EW8102',
    callsign: 'EWG8102',
    origin: 'TXL',
    destination: 'BRU',
    latitude: 52.5271,
    longitude: 13.0341,
    altitude: 8450,
    bearing: 254,
    speed: 252,
    model: 'A319',
    modeSCode: '3C6DD4',
    radar: 'F-EDDT2' },
...

Everything else is great. Thanks!

Following your README we get the following error:

$ npm install flightradar24-client
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

+ [email protected]
added 17 packages in 15.042s

Maybe add these files...

@derhuerst
Hi Jannis,

I've finally been able to put your client to proper use! Very nice. If you are familiar with the MagicMirror development, I have created a module to display current flights above a certain location, using the radar() function. It is called MMM-FlightsAbove.

Thanks again and cheers.
E:V:A

Apparently the endpoint has changed its response format. The build is failing.

Version 2.0.2 of pinkie-promise was just published.

</td>

This version is covered by your current version range and after updating it in your project the build failed.

pinkie-promise is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Int'l standard seem to benefit meters as a altitude unit.
Please consider converting the result to meters.

Hey, thank you for your client!

I would like to use it for a TS-based project, but unfortunately since there are no published types, the typescript server throws errors. As a local fix, I manually added a flightradar24-client.d.ts file. Of course, it would be nicer if the types were recognised automatically.

Would you be willing to convert this client to TS or would you accept a PR that does this? As an interim solution, it would also be possible to add this .d.ts file manually, which could look something like this:

{
        "name": "flightradar24-client",
	"files": [
		"index.js",
		"lib"
	],
+	"typings": "types.d.ts",
	"keywords": [
		"aviation",
		"airplanes",
		"flights",
		"flightradar24"
	]
}

// types.d.ts
declare module 'flightradar24-client' {
  function fetchFlight(flight: string): Promise<{
    id: string | null;
    callsign: string | null;
    liveData: boolean;
    model: string | null;
    registration: string | null;
    airline: string | null;
    origin: {
      id: string | null;
      name: string | null;
      coordinates: {
        latitude: number | null;
        longitude: number | null;
        altitude: number | null;
      };
      timezone: string | null;
      country: string | null;
    };
    destination: {
      id: string | null;
      name: string | null;
      coordinates: {
        latitude: number | null;
        longitude: number | null;
        altitude: number | null;
      };
      timezone: string | null;
      country: string | null;
    };
    departure: string | null;
    scheduledDeparture: string | null;
    departureTerminal: string | null;
    departureGate: string | null;
    arrival: string | null;
    scheduledArrival: string | null;
    arrivalTerminal: string | null;
    arrivalGate: string | null;
    delay: number | null;
  }>;

  function fetchFromRadar(
    north: number,
    west: number,
    south: number,
    east: number,
    when?: number,
    opt?: Partial<{
      FAA: boolean;
      FLARM: boolean;
      MLAT: boolean;
      ADSB: boolean;
      inAir: boolean;
      onGround: boolean;
      inactive: boolean;
      gliders: boolean;
      estimatedPositions: boolean;
    }>
  ): Promise<
    {
      id: string;
      registration: string | null;
      flight: string | null;
      callsign: string | null;
      origin: string | null;
      destination: string | null;
      latitude: number;
      longitude: number;
      altitude: number;
      bearing: number;
      speed: number | null;
      rateOfClimb: number;
      isOnGround: boolean;
      squawkCode: string;
      model: string | null;
      modeSCode: string | null;
      radar: string;
      isGlider: boolean;
      timestamp: number | null;
    }[]
  >;
}

I'm not sure if this project is still maintained but since a few days it doesn't work anymore.

Api calls using radar come back with forbidden error.

I think they put your User-Agent header on a black list, when changing this to another value it works again ...

I propose to also process the additional fields given in the JSON.
Currently only these fields are processed:

aircraft.push({
				// 10: timestamp, not needed
				// todo: 6, 14
				id,
				registration: d[9] || null,
				flight: d[13] || null,
				callsign: d[16] || null,
				origin: d[11] || null,
				destination: d[12] || null,
				latitude: d[1],
				longitude: d[2],
				altitude: d[4], // in feet
				bearing: d[3], // in degrees
				speed: d[5], // in knots
				model: d[8] || null,
				modeSCode: d[0] || null,
				radar: d[7]
})

But there are 18 fields (0-17) in total:

,"10572608":[
  "800B9C", 13.3638, 73.6369,
  91, 29500, 450,
  "6231", "F-VOCL1", "B738",
  "VT-GHD",1517871136,"DXB",
  "IXE","IX814",0,
  -2112, "AXB814", 0
]

Of these there are a few additional ones known:

• d[10] is the Unix Timestamp in Epoch format, which is useful for determining exactly when the data was obtained.
• d[6] is the 4-digit ATC Squawk code. Very useful for determining if aircraft is a military, in emergency etc.
• d[15] is the vertical speed in [ft/min].

Then there are two unknowns:

• d[14] which seem to be either "0|1".
• d[17] which is always 0 AFAICT.

Version 4.9.0 of tape was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.9.1 of tape was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 4.8.0 of tape just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tape is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 0.5.18 of moment-timezone was just published.

This version is covered by your current version range and after updating it in your project the build failed.

moment-timezone is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

RAAAH !!!
Code installed 7 days ago, and from yesterday (14/07/23) it's again "forbidden".
But they change the detection method.
If I change the user agent i'm still dropped in NodeRed, but if i take a browser with the same public IP , it's ok.
Investigating.

Tried to run the example.js with different lat/lon and get the following error:

$ ./testradar.js
TypeError: Cannot read property 'id' of undefined
    at radar.then (/home/pi/testradar.js:10:31)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)

Hi there, thanks for developing this software @derhuerst.

While investigating how this API works, I found this message:

The contents of this file and all derived data are the property of Flightradar24 AB for use exclusively by its products and applications. Using, modifying or redistributing the data without the prior written permission of Flightradar24 AB is not allowed and may result in prosecutions.

I planned to use FR24 data to enrich information in my platform (feature in development yet). The point is that using this software could make you waste too much money 💸 .

It is perfect for small local tests (and enough).

Also, I contacted FR24 for asking permission for using their data. This is their response:

Thank you for contacting us.

You're right that it's not permitted to scrape our website for integration into other tools - thank you for taking note of this.

We are in the process of developing an API, which should be available towards the end of the year. Please keep an eye on our website for further details.

So be careful guys 😕

Hello there,

is this library compatible to be used with react native?
are you planning to implement the UI for flight radar when tracking a flight ?

Thank you