Template talk:FAA-airport: Difference between revisions
Line 4: | Line 4: | ||
== Form 5010 PDF generation == |
== Form 5010 PDF generation == |
||
{{Edit template-protected}} |
{{Edit template-protected|ans=y}} |
||
I found the link for Form 5010 PDF did not work (error 404 no file or directory found) for an airport (RNT). So I went to the [https://www.gcr1.com/5010web/airport.cfm?Site=RNT airport master record web page] and clicked on the PDF icon in the upper right-hand corner. That resulted in the PDF getting generated and then the webpage is redirected to the direct link to the Form 5010 PDF. My suspicion is that when a PDF becomes outdated that it is deleted from their system and only regenerated when the first person clicks on the PDF link for the form, at which the PDF document is created and kept around until it is no longer up-to-date. What that means is that instead of directly linking to the PDF file itself, which may or may not yet exist, the template should link to the url that generates the PDF if it is needed. |
I found the link for Form 5010 PDF did not work (error 404 no file or directory found) for an airport (RNT). So I went to the [https://www.gcr1.com/5010web/airport.cfm?Site=RNT airport master record web page] and clicked on the PDF icon in the upper right-hand corner. That resulted in the PDF getting generated and then the webpage is redirected to the direct link to the Form 5010 PDF. My suspicion is that when a PDF becomes outdated that it is deleted from their system and only regenerated when the first person clicks on the PDF link for the form, at which the PDF document is created and kept around until it is no longer up-to-date. What that means is that instead of directly linking to the PDF file itself, which may or may not yet exist, the template should link to the url that generates the PDF if it is needed. |
||
Revision as of 20:19, 14 January 2019
{{WikiProject banner shell}}
to this page and add the quality rating to that template instead of this project banner. See WP:PIQA for details.Aviation: Airports Template‑class | ||||||||||
|
The link to the Form 5010 PDF doesn't work anymore. Adrian Archer (talk) 15:18, 17 November 2015 (UTC)
Form 5010 PDF generation
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I found the link for Form 5010 PDF did not work (error 404 no file or directory found) for an airport (RNT). So I went to the airport master record web page and clicked on the PDF icon in the upper right-hand corner. That resulted in the PDF getting generated and then the webpage is redirected to the direct link to the Form 5010 PDF. My suspicion is that when a PDF becomes outdated that it is deleted from their system and only regenerated when the first person clicks on the PDF link for the form, at which the PDF document is created and kept around until it is no longer up-to-date. What that means is that instead of directly linking to the PDF file itself, which may or may not yet exist, the template should link to the url that generates the PDF if it is needed.
So, taking Renton Municipal Airport (RNT) for an example. Instead of linking to http://www.gcr1.com/5010ReportRouter/RNT.pdf, the link should be to https://www.gcr1.com/5010ReportRouter/default.aspx?airportID=RNT.
<span class="PDFlink">[http://www.gcr1.com/5010ReportRouter/{{{ID|{{{id}}}}}}.pdf Form 5010]</span>
should change to be:
<span class="PDFlink">[https://www.gcr1.com/5010ReportRouter/default.aspx?airportID={{{ID|{{{id}}}}}} Form 5010]</span>
While making the update, I also recommend removing the code that generates the text and link for "PDF": (PDF). Do we really need to include that? In my opinion it just clutters up the page.
- — Archer1234 (talk) 05:40, 12 January 2019 (UTC)
- @Archer1234: in your examples above the "instead of" example of a broken link appears to be working fine for me, is this still an issue? — xaosflux Talk 19:38, 14 January 2019 (UTC)
- Xaosflux, I suspect this is a Catch-22. In putting together a coherent argument with example Archer1234 has fixed that instance. The documentation links to Ridge Soaring Gliderport for which the 5010 link in Ridge Soaring Gliderport#References returns a 404. I won't try the fix or again you won't see the problem. Cabayi (talk) 20:12, 14 January 2019 (UTC)
- Tried it on 13M / Aeronut Park Balloonport. Problem & fix were as described.
Done Cabayi (talk) 20:19, 14 January 2019 (UTC)