Das Thema wurde hier https://www.pilotundflugzeug.de/forum/2025,08,22,09,0859848 ausführlich diskutiert. Die KI-generierten Summaries sind eindeutig als solche gekennzeichnet, inklusive der Information, dass sie fehlerhaft/veraltet sein können (was übrigens generell für PIREPs gilt). Ich werde sie nicht rausnehmen, aber sobald Du einen PIREP für einen Platz postest, verschwindet die Summary.

Insofern würde ich mich freuen, wenn Du einen PIREP für LFRC postest.

Dear Mr Rockhopperflyer (known as Berlinflyer on EuroGA; lots of posts there)

You should generate your own content. Not scrape it from the EuroGA airport database e.g.

https://airports.euroga.org/record.php?id=1058

https://airfield.directory/airfield/EGEY

EuroGA.org:

Lovely airfield in lovely location. Not much around, but whole island is walkable if you're fit and have some time.
No fuel. No mobile signal at the airport.
Nice food in the hotel in Scalasaig. Wild camping possible at various places on the island (some nice spots just south of the airfield).
No parking charges and no handling necessary. Out of hours permit bust be organised in advance. Can be obtained free from Oban airport by sending your insurance details. It's valid for 1 year. Landing fees paid to Oban airport.
Caves to the North of Kiloran Beach are well worth a visit.

Also check other EGEY reports at
https://airports.euroga.org/search.php?icao=egey
for "relevant" wording ;)

Yours:

Colonsay (EGEY) requires an out-of-hours permit for landings outside the limited scheduled commercial flights; this permit is available free of charge from Oban Airport and is valid for one year. Permit applications can be completed online or by email, and insurance details are required; PPR by phone to Oban is also necessary before each landing. No parking fees apply for the first 24 hours, and there are no handling charges. Landing fees are paid to Oban Airport, with one report describing them as moderate. There is no fuel or other facilities at the airfield. Parking must be on grass areas rather than the small asphalt apron, with caution advised due to uneven ground; high-visibility vests are mandatory on the airfield. The Colonsay Hotel offers food and can arrange pickup from the airfield on request; otherwise, it is a 45-minute walk away. Wild camping is possible near the airfield, and there are now good mobile phone reception and several camping spots in the vicinity. The island is walkable for those with time and fitness, and notable sites include caves north of Kiloran Beach. Approaches may be turbulent due to local topography.

Allowing for translation changes, and looking across all the 3 reports, it is obvious that you are scraping the EuroGA airport database, so please do not pretent to be running some sort of "open" project.

You and your colleague(s) pushed hard for getting the EuroGA data for your own use

https://www.euroga.org/forums/website/12612-euroga-airports-database-data-accessibility/post/274204#274204

and now you are extracting it anyway, pretending it is your work, or "AI".

We will keep an eye for other examples of ripping off data and post them here when I/we get time to bother.

There have been several bots, notably some running on Hetzner, which have been diligently scraping the EuroGA database 24/7/365. So it looks like you have been at this for some time.

The problem is that most people don't contribute to databases if they feel the data will just be ripped off and distributed everywhere including (as you allow) commercially. It will be just another dead database. I know a number of Germans approached eddh.de and (they told me) were told to go away; that guy (who I have never spoken to) clearly knows how it works and how it doesn't work.

There is a lot of loyalty involved. Germans like to contribute to eddh.de (because it is explicitly German), while many pilots around Europe like to contribute to airports.euroga.org (because it is explicitly pan-European). There are satnav databases but they seem to be of widely varying quality, perhaps because they make it very easy to drop in a few lines. For Europe that is about it.

Eventually whoever runs an airport database (and I am sure you will be scraping Acuwkik too, and Jeppesen data, and the various ULM ones) will take countermeasures, and those with money will sue you for copyright. Then everybody who contributed to yours will have wasted their time.

The accuracy of "AI" is half garbage anyway but, like everybody else, you know that. It is a joke to publish airfield data like runway lengths. That will be for you to worry about.

Hi Peter, let me Copy & Paste myself from March '21:

So, please dear Sven, stop demanding that our project https://airports.euroga.org gives away the data which all the pilots contributed with some effort, when your own German domestic database does not!

I never did that, not once. You suggested I ask the other providers why they don't do that, and I asked you to explain why you didn't provide that answer first. Yourself. Without that suggestion, we wouldn't even have this conversation.

But since you brought up the question, thou shalt simply answer it yourself. I am not in touch with any other provider. But you keep reappearing here, magically. Or for some higher calling.

But you write on the the forum and deflect a question to others. Sorry, this isn't Tory politics or demagoguery, so if you have some honesty left in the tank and no double standard, simply answer your own question. With an honest answer I simply won't comment and fill up your project with current reports. It's user provided content, you know, after all. And why would I bother to line someone else's pockets or ego (even for a common beneficial cause) if that person treats his own customers or contributors with this arrogance. Give the answer, and don't deflect it. Else, as you mighth have discovered, I'll continue to point this out.

Since August 1st, 2020, at 21.50 :-).

Try asking all the other database owners out there what they think of sharing their content :)

Nah. I ask you, since you brought it up. Write a paragraph with some content, and I'm happy.

I think some people need to do more flying, so let's all hope we are back in the air soon! Maybe see you at Aero Friedrichshafen, though I will be amazed if it gets run, in April.

Agreed on that. They could not find another date later in the year, I am told, all blocked with their normal rhythm. Quite a pity.

So, since you are apparently motivated to reactivate old debates, I ask you: Are you willing to share your content? From what Rockhopper puts forward here, he is offering content for anybody. What is your reasoning?

Happy landings.

It is great to hear that pilots have have a choice.

-> If they prefer to enter PIREPs into a database which does intentionally not allow resharing , they know where to go.

-> If they prefer to publish reviews for the community and make them available under Creative Commons, they know that they can choose Airfield Directory.

Fortunately for the latter ones, I am already even working on a easy-to-use solution for the authors (=owners) of content shared to closed databases, who would easily like to migrate their content and make it available under Creative Commons.

Hi Peter,

Just to give you a bit more context, you can assume that your database (just like everybody else’s) has been already scraped by all major makers of "AI" models long ago, and now they're just making sure they're up to date.

I was also personally hit by this ever-escalating insane scraping wave. Not that I care much about the data, but the bots were so ruthless that it reminded me of the early search engine days, and I had to ban them just to keep my server running. Here is an article that you might like with some background:

https://thelibre.news/foss-infrastructure-is-under-attack-by-ai-companies/

What Thomas did was to take an "open source" model (misuse of terminology, but that's what they are called anyways) and have it generate summaries per airfield. I don't know which one he picked, but it's not important. The point is, guess where the information that this model was trained upon was sourced from, be it OpenAI, or Google, or Microsoft? You bet, it's your database. So no wonder that answering very specific queries, an output with high similarity to the reviews on your database comes out...

This is to explain that he didn't scrape anything like you seem to think. It's all been done already and you'd better go after OpenAI if you don't like it. Not sure it makes any difference to you though. But I think it's better to stick to reality instead of some conspirative phantasies.

P.S. I find it funny that it took 6 pages of conversation for you to make it clear that you're against sharing the reviews, because you just don't want them to be accessible through any other interface other than yours, be it a commercial project or not. That's your thing, but why not just put it this way in your original answer and end the discussion at that?

P.P.S. I don't like either database (yours or eddh) exactly for this reason, and I neither use nor contribute to either of those. I do occasionally contribute reviews to FF, and I will be using this new project because it provides an API and uses unrestrictive licensing.

"You are an aviation expert writing a concise, practical executive-style summary about the GA airfield Colonsay Airport (ICAO: EGEY), aimed at non-commercial general aviation pilots. Use external sources (e.g. airport official website, Oban & The Isles Airports, council fees pages, pilot forums such as EuroGA, eddh.de, you-fly, etc.) as input—your summary must be evidence-based and cite sources. Include operational procedures (e.g. PPR requirements, out-of-hours permitting), fees (landing, parking, permit; rounded per rules), safety notes (bird activity, turbulence), and any on-site/nearby services or constraints. Do not add uncited claims. Use plain text, English only, direct declarative style, one or two short paragraphs, no headers, no storytelling—just facts."

And wherever you get them - these facts can never be "copyrighted" anyway. Even if the pireps created by AI contained some senteces or rewritten personal experience - i see little to zero chance there could be a copyright issue.

For a text to be copyright-protected, it must reach a sufficient level of originality (often referred to as the “threshold of originality”).

To be fair, I think that the jury is still out on how to handle "AI" hallucinations in terms of copyright, as evidenced by the battles going on in Hollywood right now, or emerging commotions in the gaming industry. That much should be clear though: the precedent-setting decision won't be made on the basis of EuroGA vs. airfield.directory PIREPs :)

I am not even talking about copyright for AI content – im general small fact based little texts like these pilot reports do not qualify for "copyright". No court will be interested in dealing with this stuff.

You cannot control where "AI" scrapes its semi-garbage from. The moment this project receives a credible legal threat it will have to pack up. Then everybody contributing will have wasted their time.

Let's ask the Defendant:

Building your own site with pilot reports and want AI to collect content only from certain sources.

Here’s how that works in practice:

Yes, you can restrict AI to specific sites.

If you tell me “only use EuroGA.net and Pilots of America, never AOPA or Reddit”, then I can be directed to search or scrape only those whitelisted sites.

How it’s done technically:

When fetching fresh info, you (or a developer) set the AI/web crawler to query only those domains.
Example: a search like site:euroga.org "PIREP" ensures only EuroGA is searched.

You can also exclude others using -site:aopa.org.

********

This does not mean that it "should be done", but technically it is absolutely possible, And the risk is small, because the fact based content of PIREPS (especially when re-written by the AI) can hardly be "copyrighted".

This does not work. LLMs disregard robots.txt etc etc.

The whole LLM copyright debate is regarding this. If LLM scrapers respected these controls, they would be almost useless. They would just be a "better google".

Anyway, doing this would be admitting that specific sources are targeted because they have the quality data Rockhopper is looking for ;)

I have not tried it.

The AI-generated summaries posted on Airfield Directory are legally completely fine for several reasons: they do not consist of copied texts but only of facts expressed in new wording:

• Facts such as fees, PPR rules, phone numbers, or typical wind conditions are not protected by copyright and may be freely shared.
• The texts are not taken 1:1 from databases but are automatically reformulated. This means they do not infringe copyright protection.
• The AI-generated texts themselves are freely usable, including commercially, according to the AI-provider.

Apart from that:

• The copyright of a PIREP always lies with the author, i.e. the person who wrote the text, and not with the forum in which it was published. The forum or its operator has at most the usage rights defined in its terms and conditions (e.g. for displaying or archiving posts) – if such rules exist at all. It does not thereby become the copyright holder. Copyright remains with the writer, not the forum – and a fact-based summary does not violate this right. If, nevertheless, an individual airfield operator or author (but not a forum operator) feels their copyright or other rights have been infringed, the procedure for notice & takedown is set out in the Terms of Service, section 14.
• I would like to remind everybody that under Article 20 of the GDPR, every author also has a right to ask the service operator to export their own data in a machine-readable format, which applies to forums as well.

Every forum by the way is free to attribute and import PIREPs from Airfield Directory.

The claim “The moment this project receives a credible legal threat it will have to pack up. Then everybody contributing will have wasted their time” is of course just Trump-style fear, uncertainty and doubt.

Because the posted PIREPs on Airfield Directory are Creative Commons and are regularly exported, they remain free forever, entirely independent of the continued existence of Airfield Directory. This seems, however, to be very difficult for some minds to grasp.