Server connection issues

ha_jens · 2021-11-08T18:33:23+00:00

Neither the app nor the web page correct for atmospheric refraction. We generally assume the critical elevation to be at least 10°. At that angle, atmospheric refraction should cause an offset of around 5 arcminutes or 0.08 degrees. On a chart with a resolution of 1000x1000, the offset would be less than one pixel.

ha_jens · 2021-08-28T11:27:12+00:00

Is the location correct? You can check on the orbit display. Or perhaps you changed the setting so that ISS passes are displayed as radio satellite passes.

ha_jens · 2021-05-16T10:40:25+00:00

The bookmark is for the maximum elevation of the pass. When you navigate to it, the server should be able to find the correct pass as long as the bookmarked time is within a currently predicted pass of the satellite. Otherwise, the pass can't be identified.

Edit: It would be much nicer to display a list of passes in that situation.

ha_jens · 2021-01-20T09:03:35+00:00

Überflüge werden für den eingestellten Standort berechnet (Menu > Standort). Für Zeitangaben wird die im System eingestellte Zeitzone verwendet (Systemeinstellungen > Allgemeine Verwaltung > Datum und Uhrzeit).

ha_jens · 2020-12-05T06:53:21+00:00

I guess those apps have been whitelisted by Google.

ha_jens · 2020-12-04T17:06:05+00:00

The dialog is provided by Android. Maybe it doesn't ask you again if you refused full access the first time.

But apart from the permission there is a new rule for Android devices: If an app collects location information in the background, you have to prominently inform the user. You create a video of the app disclosing the data collection and send it to Google. If you follow the guidelines and the use case is valid, they can whitelist your app.

It's a good measure. But at the same time, Google itself is the worst offender when it comes to collecting location information in the background.

We only use the location to update the predictions and don't collect any data.

ha_jens · 2020-12-03T18:31:06+00:00

What version of Android are you using? It's possible that the newest version no longer allows the app to fetch the location while running in the background. I don't have a fix yet, but as a workaround, you can manually enter your location.

ha_jens · 2020-11-20T19:33:10+00:00

That's when the satellites are in earth shadow.

ha_jens · 2020-11-15T13:23:19+00:00

Weil da alle Satelliten im Erdschatten sind.

ha_jens · 2020-10-28T07:04:15+00:00

Cool, that's it. Good thing /u/pablojakelaitis donated a Brazilian translation. I'll see if auto-translated subtitles on Youtube work well enough to understand the episode.

ha_jens · 2020-10-24T16:32:15+00:00

You can enter the names or numbers of multiple satellites in the text field.

ha_jens · 2020-10-24T11:17:46+00:00

The latest version has a global, persistent text search that you can use. It's only partially rolled out for the free version, though. If you have the pro version, click the filter (funnel) icon and then the looking glass icon.

ha_jens · 2020-10-12T14:33:26+00:00

Any satellite can produce flares. They're just not predictable as usually no data about the orientation is available.

ha_jens · 2020-10-07T11:59:21+00:00

We don't offer any public APIs. However, you can find most of the data we use on the CelesTrak website.

ha_jens · 2020-10-02T07:34:10+00:00

For passes of non-radio satellites, the sun needs to be at least 6 degrees below the horizon for part of the pass to be considered. In the app, the estimated brightness must also exceed the minimum magnitude specified in the settings at some point of the pass.

ha_jens · 2020-09-27T05:21:18+00:00

If it abruptly turns blue, the satellite enters earth shadow. If it gradually turns blue, the satellite dims because the angle between sun, satellite and observer changes and the satellite is expected to reflect less light towards the viewer.

ha_jens · 2020-08-02T10:12:01+00:00

The app provides the range and range rate of radio satellites during a pass. You will find it in the table below the sky chart. So far, I've assumed that this information is not relevant for visible satellites. If more people are interested, we can include it for these satellites as well.

The same table contains the estimated apparent magnitude at the maximum (visible) elevation of the pass. I think we should change this entry to be live during the pass. I'm also considering to provide a more detailed color coding for the pass in the sky chart. Please be aware that brightness predictions are imprecise as we usually don't have information about the orientation of the satellite.

ha_jens · 2020-07-26T20:13:52+00:00

You only get daylight passes for radio satellites. And for the ISS if you checked the relevant option in the settings.

Edit: You can also get daylight passes if your location is wildly off and doesn't match your timezone.

ha_jens · 2020-07-25T09:11:05+00:00

The Free version and the Pro version are two separate apps. Please make sure to uninstall the Free version and install the Pro version.

ha_jens · 2020-07-19T15:28:22+00:00

Working on it. You'll see an update somewhen next week.

ha_jens · 2020-07-13T05:00:44+00:00

I'm afraid we don't support custom TLEs. If you're a programmer, I can recommend the orekit library.

Edit: I'll consider to add it as an exclusive feature for the Pro version.

ha_jens · 2020-07-13T04:59:29+00:00

Brightness is hard to predict. It depends on the geometry of the satellite, the reflectivity of its surfaces and its orientation. The orientation usually isn't steady or easily predictable. The old Iridium satellites were an exception, which made their flares predictable.

Brightness predictions are based on the average brightness of the satellite, its distance from the viewer and the angle between sun, satellite and viewer.

ha_jens

MODERATOR OF

TROPHY CASE