When i click on Scunthorpe it comes up with a totallly different name - Foddingham or something like like.

Any reasom why?

Yeah, there was a tiny town in our database at exactly the same location that was being picked up by the waypoint resolver. Fixed, thanks.

I've been following this & trying the home based prog. from the start on this forum. It's great !
Could you kindly alter the strip height for Jackrell's Farm to 230 ft. pls, next time you have the opportunity.

Thanks,

mikehallam.

I can't personally, but the data for non-AIP airfields comes from FlightNav.co.uk. If you spot an error in that data, that's the place to go to get it corrected.

SkyAngel 0.9.9 Released!
 

Hi Guys,

It's that time of the week again. This build adds a great deal of polish as we work towards the full version 1 release. Here's a breakdown of what's changed and new:

InFlight
---
Cut down data loading time by roughly two thirds, compared with previous release
Added "inspect" context menu item for examining all the information about any item on the main map
Approaching Features instrument enhanced with inspection capabilities, better warnings and more features drawn
When you exit the software, if the GPS was active it is automatically started next time
Follow mode (north/heading up) is now in Options, simplifying the menu item under the Chart menu to a simple check box
The map position and zoom level is now remembered
Warning thresholds are now adjustable, like they are in Plan, via the Options window
Route and track log folders have been changed to reside within the SkyAngel directory, because many devices were discarding the contents of the My Documents folder

Plan
---
Enroute Features view improved with better drawing and more helpful weather tooltips
PLOG format improved with more usage of colours to denote differences between waypoint types, radio aid types etc
The TAS for a route now comes from the aircraft default speed unless a route TAS is explicitly specified
User Waypoints window added for centralised management of user waypoints
User Waypoints are now exported to InFlight along with a route
Planned fuel is now saved along with a route
The last-used aircraft is now selected when the application is next started
Fixed a bug introduced two builds ago that would prevent SkyAngel from working on 64-bit Windows

Enjoy.

Thanks for the link. Tim,

I've got in touch & now sent them correct data which they've incorporated on their site for Jackrell's Farm.

mikehallam

Hi Tim
I just loaded the new version of Plan and found that I had lost all my user waypoints. No problem to load them again but I thought I would try to load them from a saved route. Now here's a strange thing - if I highlight a waypoint in the old route, then right click to create a user waypoint it ends up a long way from where the old waypoint in the route was. Tried it with a few and they all seem to be 1 or 2 miles from where I expected.

Tone

The user waypoint should end up in the exact position of the mouse cursor when you right-click; is this not happening?

We changed the user waypoint storage medium in this version. They're all stored in your My Documents folder under SkyAngel now, in a simple XML file so it's easy to share/edit/transfer/backup all of them without worrying that a future version might not find them (as has occurred here). Previously they were stored alongside the software's general settings.

How does one get into an xml file to edit it or copy some/all of its contents?

Chris N.

At the very least, any text editor; but if you manage to screw up the formatting of the contents, there is no guarantee the original application will load it again afterwards.

There are graduated levels of self-description and validation of XML, and editors which take this into account and ensure your changes are validated, but in the first instance try notepad....or vi.....:E

Thanks. So "Notepad" should do it.

Obviously, if amending or adding, format of carriage returns, commas and spaces etc. have to be maintained.

Chris N.

Yes notepad will do it just fine. XML isn't that strict; as long as the elements are there (between the angle brackets) it will read the data just fine. Don't worry too much about carriage returns or other whitespace. You'll see that there's just one waypoint per line.

Having said that, it shouldn't be necessary to edit the file manually when you can use SkyAngel to do it. But, if you wanted to import a load of waypoints from a friend, pasting them in to the file would work just fine.

Superb addition Tim, many thanks.

Hi Tim
I have tried this again by setting up a new route to include Bottesford VRP and Hucknall. With this route loaded I right clicked on the Bottesford and Hucknall boxes and created user waypoints. Both turned out to be some distance from where I expected them to be.
From the route data;
<Hint Location="N525753.00 W0004654.00" Name="Bottesford" />
<Hint Location="N530052.00 W0011306.00" Name="Hucknall" />
and from the user waypoints;
Bot N525804.00 W0004644.00
Huc N530027.00 W0011048.00

The cursor was in the middle of the descrition box when I right clicked. This oddity only occurs if you try to create user waypoints from an existing route and the only reason I was trying to do this was because I thought I had lost all my user waypoints.
Perhaps not serious but you should be aware of it.
Tone

Tone, I'm pretty sure this is happening because you're expecting the new waypoint to be created in exactly the same position as the centre of the turningpoint box. This isn't the case; it'll be created in the position of the mouse cursor which is likely off by a few pixels, which will translate to a few seconds of accuracy.

Thanks for bringing it to my attention though. In the future it might be possible to detect the case where you're clicking on an existing turningpoint and enforce the exact position of the turningpoint, rather than getting the current mouse cursor position.

Tim
Thanks for the quick reply. The thing that brought this to my attention was the fact that the user waypoints I created were well ouside the turning point box, up to a mile or more. If it were only a few pixels different I would't have noticed.
Tone

Well now that I cannot explain. :ugh:

I love being able to insert custom NOTAMs for my home FIR.

However, there's a bug in the implementation. It will only work when copying the NOTAM list in IE. When using Google Chrome, you get all the NOTAMs parsed as one giant NOTAM.

The culprit is the end-of-line detection. IE copies the NOTAMs as

while Google Chrome enters the same NOTAMs on the clipboard as

Cut and paste into Word to replace each carriage return with a double carriage returns solves the problem, so apparently SkyAngel expects double CRs for some reason.

Yet another item on the to do list, but a rather small one I'd say. :)

If you want more of a challenge, make it possible to present the full text of each notam when double clicking them. As it is, there are plenty of notams which are not easily deciphered when truncated to only the text portion and the position.

Cheers!
/Fred

NOTAMs should always end with a double newline. Chrome not copying text to the clipboard properly isn't something I intend to work around in SkyAngel.

Where's that requirement found? Not saying I doubt it exists, I just can't locate it from a quick browse through Annex 15/Doc 8400 and I'm curious by nature. :)

Regarding the copying algorithms, you'll have to blame Naviair (which you link in SkyAngel) and not Google Chrome. It's the Naviair site which (re)publishes the NOTAMs without any newlines at all, as the NOTAM page is an HTML table rather than raw text. This gives browsers a lot of freedom to implement the copying any old way they please, regardless of what ICAO says.

As a user, I kindly request this feature in order to be able to use my standard browser in conjunction with your software. ICAO compliant or not, the current implementation hampers the usability of the software.

Ideally, we'd have access to the raw NOTAM feeds for every FIR in the world but looking at it realistically, you'll have users copying NOTAM text from pretty much any source they can get their hands on. Strict enforcement of the data format will mean lots of frustrated users around the world. This far, it's just luck that IE copies tables in a (non-ICAO-compliant) format which the parser can handle.

Cheers,
/Fred