Loading Profile...
No Google map display on some flights
I have some flights with a route of YWCK YWCK that do not show the Google Map. At first I thought it was because I had a ROUTE of YWCK (same thing was happening with my YMMB flights). I saw Steven Pam's flight had YPEF YPEF and displayed a map, so I changed over to YWCK YWCK and YMMB YMMB but still no map. Then I made YMMB my home base and suddenly my flights with YMMB YMMB routes all started showing maps but my YWCK YWCK flights still don't.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Maps (and points on those maps) will only display for locations that are in the database.
Currently, Jetrecord has a limited number of non-U.S. airports and even fewer navaids. When you create a route that includes an airport or navaid that is not already in the database, those locations are skipped on the map. If a map has no locations, the map won't display at all. Note that this doesn't affect your ability to create a route and have it logged for your flight, it only affects the display on a map.
That said, airports can be created on the fly. When you type in the URL for an airport that doesn't already exist in the database, Jetrecord does an airport lookup from a web service (see "Airports" on the About page for an explanation: http://jetrecord.com/about) and uses that to create the airport if it can be found.
An automated script runs twice a day that updates all of the routes to pick up any new locations that have been created. So, if you visit the airport page for the missing airport, thus creating it, you can rest assured that it will also appear on the route map fairly soon, which means it will show up on your flight page; it will be the next day at the latest.
I'm looking at changing this to do the airport lookup when a route is created but it depends on the speed. Routes are created (if they don't already exist) when you log a flight. If adding the airport lookup causes a big slowdown to logging flights, I'm not going to do it.
I may one day consider adding some kind of background work queue that can handle these types of jobs behind the scenes, but that's for another day since the system currently works, albeit somewhat confusingly.
In your case, then, if you visit http://jetrecord.com/airports/ywck it will create the airport. Sometime within the 24 hours after the airport is created, the automated script will find the new airport and add it to your route. So, at the latest, you should see a map appear for your flight less than a day after the airport is created.
Does that make sense?
I’m unsure
1 Comment
Add a comment
This solves the problem
-
OK - this does make sense. When I was loading the new routes, it didn't seem to parse them to create airport pages for YMMB and YWCK as searching through the airports list didn't find them. Once I created YMMB as my home base and clicked on it, it did create the airport page which then triggered the mapping as per the above.
Is the parsing script running OK? If it is, why wasn't an airport or FIX created for YWCK? (I used Search in the top right corner and YWCK doesn't show up anywhere). -
Inappropriate?Yes, the script is running fine. It only runs twice a day.
If you go to http://jetrecord.com/airports/ywck, the airport is there. So after the route script runs (it runs on a schedule), any and all routes that contain that airport will have it on their maps.
As for search, that's completely dependent upon the whim of Google's spiders. If they happen to index that airport, it will show up in the search. Otherwise, even though the airport exists on Jetrecord, the search won't find it.
EMPLOYEE
