Misasa Airfields Guide....great idea or waste of time?

[Bundy]

Guys a microlight pilot wrote the Airportiki. Where does it fall short for a micro pilot? Seems a pity to duplicate efforts - especially when the main challenge is the crowd sourcing of the information.

Oh - and an app is already in development.

Hey SB, how are ya.

It falls short (for me at least) in that there are very few contact details. As I said before...finding the co ords and general aerodrome details like runway info, circuit direction etc etc is easy....we need to come up with an easy to use system which includes regularly updated contact info for every field. Even the new APP you give an example of above has no contact details...pretty useless for the guys who want to know about Acc nearby or hangerage, or fuel avalability etc etc etc.

The idea of having a std template that you simply edit is a good one. The real challenge is getting pilots like you and me to regularly update the info, as well as keeping the details private with some sort of function where the phone numbers can be "requested" if you are registered on the system? They can then be displayed if you are logged in or maybe even e mailed directly to you. Believe me it's not as easy as it sounds and I have yet to see anything on the net that does this efficiently.

Airportiki is good, but the contact details are (again) missing in many cases. So far I can see no other way than to design a whole new, but simple website which can be edited and added to by anyone who is registered and has access to it. Someone will have to develop it, host it and pay for it's upkeep. Not so easy...but if it can be done at reasonable cost it will be an incredibly valuable tool for anyone to use.

Please keep the comments and suggestions comming chaps, as I said, this is simply an idea at this stage.

[skybound®]

Correct Bundy - the information gathering and upkeep is most definitely the issue. No app/website, existing or new, will solve that, so to create a new one will be throwing good effort after bad.

As far as privacy goes on contact details - not too sure that is a huge issue - most allow their details to be published - and if not, can easily be 'protected' via current structures. For example - look on Uitenhage's entry - I have PM Skybound for more info. That is easy enough.

I have some ideas on how to encourage the crowd sourcing of info, but need some more thought before implementing.

[mulderpm]

In my opinion to get people to provide/update the info requires the following:
1) The web site must be simple and user friendly, like a template with fields to be filled in ..some mandatory and others not
2) From the beginning there must be a value add for the pilot that visits the web site. He/She must want to visit the site and get some value. This will encourage contribution
3) A downloadable version must be available so that the pilot can get info when offline.
4) The info must be free to the user.
5) The personal info must only be visible to registered users on the web site. I am not in favour of the PM option because when you need this info and the contact person does not respond, for whatever reason i.e. tired of responding or just not reading e-mails or etc., your trip may be in jeopardy. A phone call is the best option as it indicates clear intent and commitment.
6) ?

[skybound®]

Excellent mulderpm - the thinking moves forward


In my opinion to get people to provide/update the info requires the following:
1) The web site must be simple and user friendly, like a template with fields to be filled in ..some mandatory and others not

Open to suggestions on the Airpotiki interface for any improvements.

2) From the beginning there must be a value add for the pilot that visits the web site. He/She must want to visit the site and get some value. This will encourage contribution

Dont think it is so much the value add - that by default of the info being available is why a person would visit. There are also many more persons willing to take information, but far less willing to contribute freely. My idea is to investigate a points type system like other crowd sourcing apps make use of. Points could be just to recognise who have made contributions - some are happy just to receive that basic recognition. One could extend that to also say reward in other ways the contributors by way of gifts or other rewards.

3) A downloadable version must be available so that the pilot can get info when offline.

Already available in excel and pdf on Airportiki

4) The info must be free to the user.

Agreed.

5) The personal info must only be visible to registered users on the web site. I am not in favour of the PM option because when you need this info and the contact person does not respond, for whatever reason i.e. tired of responding or just not reading e-mails or etc., your trip may be in jeopardy. A phone call is the best option as it indicates clear intent and commitment.

I only used the PM as an example of one method to protect the details. The problem with registration is that you would require this registration to be administered to offer any protection. If it is too simple to register, the protection disappears. Administering takes resource, and if user is short of time, may end up not being approved in time to use the information.