https://forum.blitzortung.org/mybb/ Wed, 21 Oct 2026 15:50:08 +0000 MyBB https://forum.blitzortung.org/mybb/showthread.php?tid=4321 Tue, 13 Oct 2026 11:19:29 -0500 Anthony_Toulouse]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4321
My name is Anthony Prezman. I live in Toulouse, France, and I am developing Métanosphère, a personal, non-commercial project that aims to become a free, community space. It shows the Earth in 3D and lets people share their experiences, with a scientific section about the Earth's environment.

I am now building a page about the Schumann resonance: the way the cavity between the ground and the ionosphere vibrates at around 7.8 Hz and a few higher frequencies. This resonance is the subject of the page, not lightning. Lightning only matters here because it is what makes the cavity ring: each strike sends a wave around the globe, and these waves add up into the resonance. So lightning is a means to show where the resonance comes from and why its intensity rises and falls during the day. The page is not a lightning map and does not show lightning for its own sake, which is your field and not ours.

You can see the current prototype here: https://metanosphere.vercel.app/schumann.html
For now, the lightning on the globe is simulated from a simple model of the three main thunderstorm regions. Real data from Blitzortung.org would make the link between real thunderstorms and the resonance much more truthful, and I would like to ask whether this is possible, and under which conditions.

I have read your data policy and would like to respect it fully:
- The project is and will remain non-commercial.
- Aggregated and delayed data would be enough, for example the number of strokes per large region every 10 minutes, rather than individual strokes in real time. The page would never replace a visit to your map.
- Blitzortung.org would be clearly credited as the source, with a link inviting people who want to follow lightning itself to your map. The data would remain under CC-BY-SA 4.0.
- The data would be retrieved by our own server, at a low frequency, and never by visitors directly.
- The Schumann page is freely accessible. The rest of Métanosphère is currently in a private beta with a small team, and will be open to everyone when it launches.

If data access is reserved for participants, I would also be glad to know how to set up a station in Toulouse and contribute to the network.

With gratitude for the work of all the volunteers behind Blitzortung.org,

Anthony Prezman
Toulouse, France]]>
My name is Anthony Prezman. I live in Toulouse, France, and I am developing Métanosphère, a personal, non-commercial project that aims to become a free, community space. It shows the Earth in 3D and lets people share their experiences, with a scientific section about the Earth's environment.

I am now building a page about the Schumann resonance: the way the cavity between the ground and the ionosphere vibrates at around 7.8 Hz and a few higher frequencies. This resonance is the subject of the page, not lightning. Lightning only matters here because it is what makes the cavity ring: each strike sends a wave around the globe, and these waves add up into the resonance. So lightning is a means to show where the resonance comes from and why its intensity rises and falls during the day. The page is not a lightning map and does not show lightning for its own sake, which is your field and not ours.

You can see the current prototype here: https://metanosphere.vercel.app/schumann.html
For now, the lightning on the globe is simulated from a simple model of the three main thunderstorm regions. Real data from Blitzortung.org would make the link between real thunderstorms and the resonance much more truthful, and I would like to ask whether this is possible, and under which conditions.

I have read your data policy and would like to respect it fully:
- The project is and will remain non-commercial.
- Aggregated and delayed data would be enough, for example the number of strokes per large region every 10 minutes, rather than individual strokes in real time. The page would never replace a visit to your map.
- Blitzortung.org would be clearly credited as the source, with a link inviting people who want to follow lightning itself to your map. The data would remain under CC-BY-SA 4.0.
- The data would be retrieved by our own server, at a low frequency, and never by visitors directly.
- The Schumann page is freely accessible. The rest of Métanosphère is currently in a private beta with a small team, and will be open to everyone when it launches.

If data access is reserved for participants, I would also be glad to know how to set up a station in Toulouse and contribute to the network.

With gratitude for the work of all the volunteers behind Blitzortung.org,

Anthony Prezman
Toulouse, France]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4319 Sun, 11 Oct 2026 07:25:26 -0500 elsell]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4319
I would like permission to use live lightning data in a personal hobby app. I do not plan to earn money from the app. It will have no advertisements or subscriptions. At first, I will be the only user.

The app would show my current location and recent lightning strikes on a map. The map would follow my location. I could also move the map and change its scale. Circles around each strike would show an estimate of how far the thunder sound has travelled.

I would like to use the app with Apple CarPlay and Android Auto. This depends on approval from Apple and Google and their display requirements. The purpose is to view lightning activity for personal interest. The app would not provide storm warnings or support safety decisions.

Could you please answer these questions?

1. May I use your live strike locations and times for this project?
2. Which data feed should I use?
3. What credit must I give to Blitzortung and its contributors?
4. What limits apply to connections, data storage, and requests? I can use my own server to limit traffic to your servers.
5. Is a private prototype allowed? Your external project rules say that apps must be freely accessible. Would I need to make this app available to everyone at no charge?
6. Must I operate a detector to get access, or can you grant permission without one?

Thank you for your time and for maintaining the network.]]>
I would like permission to use live lightning data in a personal hobby app. I do not plan to earn money from the app. It will have no advertisements or subscriptions. At first, I will be the only user.

The app would show my current location and recent lightning strikes on a map. The map would follow my location. I could also move the map and change its scale. Circles around each strike would show an estimate of how far the thunder sound has travelled.

I would like to use the app with Apple CarPlay and Android Auto. This depends on approval from Apple and Google and their display requirements. The purpose is to view lightning activity for personal interest. The app would not provide storm warnings or support safety decisions.

Could you please answer these questions?

1. May I use your live strike locations and times for this project?
2. Which data feed should I use?
3. What credit must I give to Blitzortung and its contributors?
4. What limits apply to connections, data storage, and requests? I can use my own server to limit traffic to your servers.
5. Is a private prototype allowed? Your external project rules say that apps must be freely accessible. Would I need to make this app available to everyone at no charge?
6. Must I operate a detector to get access, or can you grant permission without one?

Thank you for your time and for maintaining the network.]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4318 Fri, 09 Oct 2026 04:37:20 -0500 Massimo Ciavarro]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4318 much less than what is shown on the map? Yesterday I was monitoring my area, southern Piedmont, and on the map I saw a lightning strike near Alessandria, which however is not present in the 10-minute data files.

The same for Savona.

The squares I drew on the map are approximate; these are the coordinates.

Searching in the 10-minute files, there are no lightning strikes within these squares, whereas they are shown on the map.

The time range is 14:00 – 16:00 UTC of 08 Oct. 2026

Alessandria: [8.52682, 44.97476], [8.83306, 44.97476], [8.83306, 44.81478], [8.52682, 44.81478], [8.52682, 44.97476]
Savona: [8.41797, 44.31886], [8.51600, 44.31886], [8.51600, 44.26840], [8.41797, 44.26840], [8.41797, 44.31886]

In the 10-minute files, I don't have any lightning strikes in these squares, while on the map there are. Why is that?

Are the 10-minute files subjected to further validation? Are they cleaner from false positives that are instead present on the live map?

I also have 2 screenshots:

1) blitzortung


2)lightningmaps (I know it is no longer supported)
]]> much less than what is shown on the map? Yesterday I was monitoring my area, southern Piedmont, and on the map I saw a lightning strike near Alessandria, which however is not present in the 10-minute data files.

The same for Savona.

The squares I drew on the map are approximate; these are the coordinates.

Searching in the 10-minute files, there are no lightning strikes within these squares, whereas they are shown on the map.

The time range is 14:00 – 16:00 UTC of 08 Oct. 2026

Alessandria: [8.52682, 44.97476], [8.83306, 44.97476], [8.83306, 44.81478], [8.52682, 44.81478], [8.52682, 44.97476]
Savona: [8.41797, 44.31886], [8.51600, 44.31886], [8.51600, 44.26840], [8.41797, 44.26840], [8.41797, 44.31886]

In the 10-minute files, I don't have any lightning strikes in these squares, while on the map there are. Why is that?

Are the 10-minute files subjected to further validation? Are they cleaner from false positives that are instead present on the live map?

I also have 2 screenshots:

1) blitzortung


2)lightningmaps (I know it is no longer supported)
]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4315 Fri, 02 Oct 2026 15:05:17 -0500 CoastalGeorgia]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4315
It appears that the slot for the 4 thru-hole legs of the USB connector were not defined correctly, and they are being interpreted as 0.4mm holes instead of slots per the part diagram. I've checked with all of the major PCB fabs, and they all interpret the current 22.2b GERBER files as this way.

I was wondering if the owner of the PCB project files would be able to revise this and release a corrected revision on the public index, as this current version is incompatible with assembly of the USB connector.



]]>
It appears that the slot for the 4 thru-hole legs of the USB connector were not defined correctly, and they are being interpreted as 0.4mm holes instead of slots per the part diagram. I've checked with all of the major PCB fabs, and they all interpret the current 22.2b GERBER files as this way.

I was wondering if the owner of the PCB project files would be able to revise this and release a corrected revision on the public index, as this current version is incompatible with assembly of the USB connector.



]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4312 Wed, 30 Sep 2026 01:58:11 -0500 onurd]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4312 I am working on a very small personal hobby project related to local thunderstorm forecasts and live lightning activity, and I would like to ask whether my intended use of Blitzortung data would be acceptable.
This is not a commercial product and I do not plan to monetize it. It will most likely remain a personal learning project used by myself and perhaps a few friends.
I am not a professional software developer. I have been building the project mainly with the help of AI coding tools while learning about lightning detection, weather forecasting and geospatial processing.
The project currently shows a simple local thunderstorm forecast. I would like to add a separate live-observation layer using Blitzortung data.
The intended use would be limited to simple informational summaries such as:
nearest recently detected lightning strike, number of recent detections within 10 / 25 / 50 km, time since the most recent nearby detection

At a later stage, I may also experiment with non-authoritative trend wording such as “activity appears to be approaching” or “moving away,” based on recent strike patterns. I understand that this would only be an approximation and would not be presented as a storm track, safety guarantee, or official warning.

I also understand that Blitzortung data must not be used as an official storm-warning or safety-critical system. The project would clearly state that it is informational only and that users should follow official meteorological and emergency guidance.

Technically, I would not want every browser to connect directly to Blitzortung. If permitted, my preferred setup would be a single server-side connection, very short-term in-memory retention of recent detections (for example up to 60 minutes), and only derived proximity information shown to the user.
Before proceeding, I would like to ask:

1. Would this type of small, non-commercial personal hobby use be acceptable?
   
2. Which current live-data access method would you recommend for such a project?
   
3. Is temporary in-memory retention of recent strikes acceptable for distance/count calculations?
   
4. May derived information such as nearest-strike distance and recent strike counts be shown?
   
5. Would optional proximity notifications such as “lightning activity detected nearby” fall under the prohibited storm-warning category, or could they be acceptable if clearly informational and non-authoritative?
   
6. Are there any specific attribution, rate-limit, retention, geographic-scope, or redistribution requirements I should follow?
   

I am completely happy to keep the project private or very limited if public use is not appropriate. My main goal is simply to learn and experiment while respecting the Blitzortung project and its rules.
Thank you very much for your time and for maintaining such an interesting community project.]]> I am working on a very small personal hobby project related to local thunderstorm forecasts and live lightning activity, and I would like to ask whether my intended use of Blitzortung data would be acceptable.
This is not a commercial product and I do not plan to monetize it. It will most likely remain a personal learning project used by myself and perhaps a few friends.
I am not a professional software developer. I have been building the project mainly with the help of AI coding tools while learning about lightning detection, weather forecasting and geospatial processing.
The project currently shows a simple local thunderstorm forecast. I would like to add a separate live-observation layer using Blitzortung data.
The intended use would be limited to simple informational summaries such as:
nearest recently detected lightning strike, number of recent detections within 10 / 25 / 50 km, time since the most recent nearby detection

At a later stage, I may also experiment with non-authoritative trend wording such as “activity appears to be approaching” or “moving away,” based on recent strike patterns. I understand that this would only be an approximation and would not be presented as a storm track, safety guarantee, or official warning.

I also understand that Blitzortung data must not be used as an official storm-warning or safety-critical system. The project would clearly state that it is informational only and that users should follow official meteorological and emergency guidance.

Technically, I would not want every browser to connect directly to Blitzortung. If permitted, my preferred setup would be a single server-side connection, very short-term in-memory retention of recent detections (for example up to 60 minutes), and only derived proximity information shown to the user.
Before proceeding, I would like to ask:

1. Would this type of small, non-commercial personal hobby use be acceptable?
   
2. Which current live-data access method would you recommend for such a project?
   
3. Is temporary in-memory retention of recent strikes acceptable for distance/count calculations?
   
4. May derived information such as nearest-strike distance and recent strike counts be shown?
   
5. Would optional proximity notifications such as “lightning activity detected nearby” fall under the prohibited storm-warning category, or could they be acceptable if clearly informational and non-authoritative?
   
6. Are there any specific attribution, rate-limit, retention, geographic-scope, or redistribution requirements I should follow?
   

I am completely happy to keep the project private or very limited if public use is not appropriate. My main goal is simply to learn and experiment while respecting the Blitzortung project and its rules.
Thank you very much for your time and for maintaining such an interesting community project.]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4304 Tue, 22 Sep 2026 11:16:11 -0500 fuchswetter]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4304 https://forum.blitzortung.org/mybb/showthread.php?tid=4303 Mon, 21 Sep 2026 16:17:59 -0500 Hoelters]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4303 who has a finished uildet e-field platin for the blue system?
See picture.
When yes, how many money?
greetings from Nettetal NRW

  E-Field.png (Size: 223.04 KB / Downloads: 7) ]]> who has a finished uildet e-field platin for the blue system?
See picture.
When yes, how many money?
greetings from Nettetal NRW

  E-Field.png (Size: 223.04 KB / Downloads: 7) ]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4301 Sun, 13 Sep 2026 07:12:54 -0500 Pascual]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4301 My name is Pascual, EA5WU. I am a radio amateur and the author of dxcontest.org, a free web-based DX cluster for radio amateurs. It is a personal, non-commercial project with no advertising, funded by donations. It has around 665 registered users, about 440 of whom log in every month, most of them in Europe.
I would like to add one simple feature: to alert a registered user when Blitzortung detects lightning closer than a distance they choose themselves (20, 30 or 50 km, for example) to their station, so they can disconnect antennas and equipment in time. The alert would be a banner on the site and, optionally, a push notification. There would be no lightning map and no other visualisation of your data.
How I would do it, following your conditions for external projects:
* A single WebSocket connection from my own server. Users never connect to your servers. My server filters by distance and alerts each user, so traffic towards Blitzortung does not grow with the number of users.
* Visible attribution on every alert and on the credits page: "Lightning data: Blitzortung.org", with a link, under CC BY-SA 4.0.
* Free access for all users, at no cost and with no conditions attached.
* A clear statement that Blitzortung is not an official warning service and that the data comes from hobbyists, for hobbyists.
I am aware that some Blitzortung participants are radio amateurs themselves. This feature would serve them just as much as anyone else: an antenna on the roof and a storm approaching is a problem they know well.
I know your conditions exclude "storm warning systems". I would rather ask you directly: what I am proposing is to protect the amateur's own station equipment, with no commercial, insurance or risk-analysis purpose whatsoever. If this use does not fit within what you allow, I understand, and I will not implement it.
Thank you for your work, and for taking the time to read this.
73, Pascual - EA5WU]]> My name is Pascual, EA5WU. I am a radio amateur and the author of dxcontest.org, a free web-based DX cluster for radio amateurs. It is a personal, non-commercial project with no advertising, funded by donations. It has around 665 registered users, about 440 of whom log in every month, most of them in Europe.
I would like to add one simple feature: to alert a registered user when Blitzortung detects lightning closer than a distance they choose themselves (20, 30 or 50 km, for example) to their station, so they can disconnect antennas and equipment in time. The alert would be a banner on the site and, optionally, a push notification. There would be no lightning map and no other visualisation of your data.
How I would do it, following your conditions for external projects:
* A single WebSocket connection from my own server. Users never connect to your servers. My server filters by distance and alerts each user, so traffic towards Blitzortung does not grow with the number of users.
* Visible attribution on every alert and on the credits page: "Lightning data: Blitzortung.org", with a link, under CC BY-SA 4.0.
* Free access for all users, at no cost and with no conditions attached.
* A clear statement that Blitzortung is not an official warning service and that the data comes from hobbyists, for hobbyists.
I am aware that some Blitzortung participants are radio amateurs themselves. This feature would serve them just as much as anyone else: an antenna on the roof and a storm approaching is a problem they know well.
I know your conditions exclude "storm warning systems". I would rather ask you directly: what I am proposing is to protect the amateur's own station equipment, with no commercial, insurance or risk-analysis purpose whatsoever. If this use does not fit within what you allow, I understand, and I will not implement it.
Thank you for your work, and for taking the time to read this.
73, Pascual - EA5WU]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4298 Sun, 06 Sep 2026 12:08:25 -0500 AA5H]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4298 Some Questions on Signal Optimization Metrics for the System Experts!

This is going to be a long and verbose post, so apologies in advance.

I realize there are dozens of posts on how to optimize; most take a "do this" and "do that" shotgun approach by eliminating common impairments. As a former military signals analyst, I prefer to take a systems approach based on baseline measurements of the circuit's known voltage and noise levels.
 My challenge is determining the correlation between the system's electrical metrics and the optimized signal received by the servers.
From my perspective, these factors impact system optimization:

Home Receiver Unit baseline metrics:

1. Noise floor: Drives the signal-to-noise ratio (SNR).
   
2. Pre-amplifier gain: Typically provides a stronger received signal, but can also reduce the SNR depending on the receiver's ability to reject or filter out-of-band signals.
   
3. Filters: Dampen or suppress out-of-band signals.
   
4. OSI Wireline and Network settings: Duplex mode and packet size (to prevent packet fragmentation in routers with DF/DNF settings).
   
5. A/D serialization Settings: Left at Defaults
   
   

Server-side metrics:

1. Timestamp quality: The accuracy of timestamps on server-received packets compared to the server's PPS Stratum 1 source.
   
2. Packet latency: Measured in jitter.
   
3. Packet distortion: Noise resulting in random or out-of-sequence characters and CRC errors.
   
4. Surplus packets: Packets received by the server error-free, but rejected as surplus in areas with high receiver counts.
   
5. Factor "X": (More on that below).
   
   

Now, to the meat and potatoes: When it comes to system optimization, what server-reported metrics actually determine success?

1. Packet Count: Not accurate; it can include routed packets with broken UDP or higher-layer structures.
   
2. Packets Valid/Involved: Partially accurate, but valid/involved counts may only reflect the integrity of the UDP structure, not the quality of the payload.
   
3. Packets Used: What I consider true success—packets received at the server with an intact payload, timestamps within the system threshold, and a payload needed by the server to complete a calculation.
   
4. Packet "Efficiency": The ratio of "Valid" to "Used" packets (just my guess).
   

And now for "Factor X"...
I've systematically eliminated as many variables as possible from my setup. I use a field strength meter to identify RFI hotspots and mitigate them either by shutting off the source or using ferrite rings and clamps optimized to the source frequency. I've built three separate antenna types, tried various grounding scenarios, and added external RFI suppression to the antenna leads (1mF–2mF poly caps).

After a week of trial and error, my "Packets Used" count rose steadily into the 2,000–4,000 range—placing it in the top tier compared to similar receivers. 

Success! Or so I thought; read on

Unfortunately, my high "Packets Used" count isn't sustainable over time. It regularly declines to the 400–500 range for hours; it sometimes recovers to 1,000–1,500, and occasionally spikes back up to 2,000–4,000. My "Packets Used" count fluctuates wildly without any configuration changes, antenna changes,  environmental changes (including local weather), or additional RFI sources. I live 1 km from any neighbor, switching station, or other external RFI source. These fluctuations occur without any GPS errors, identified interference events, or filtering changes.

My only explanation is "Factor X" on the server side. Is it normal for "Packets Used" to vary wildly throughout the day as atmospheric or server conditions change, or is this shift caused by something on "my end"?

Again, apologies for such a detailed and long-winded post.

Current Setup:

• System Blue-Mini
  
• Three Coils of Times Microwave LMR-600 (2x each, with a 90-degree polarization shift)
  

Thanks

Brian (AA5H)


  Screenshot 2026-09-06 115010.png (Size: 59.89 KB / Downloads: 16)

  Screenshot 2026-09-06 115221.png (Size: 73.75 KB / Downloads: 17) ]]> Some Questions on Signal Optimization Metrics for the System Experts!

This is going to be a long and verbose post, so apologies in advance.

I realize there are dozens of posts on how to optimize; most take a "do this" and "do that" shotgun approach by eliminating common impairments. As a former military signals analyst, I prefer to take a systems approach based on baseline measurements of the circuit's known voltage and noise levels.
 My challenge is determining the correlation between the system's electrical metrics and the optimized signal received by the servers.
From my perspective, these factors impact system optimization:

Home Receiver Unit baseline metrics:

1. Noise floor: Drives the signal-to-noise ratio (SNR).
   
2. Pre-amplifier gain: Typically provides a stronger received signal, but can also reduce the SNR depending on the receiver's ability to reject or filter out-of-band signals.
   
3. Filters: Dampen or suppress out-of-band signals.
   
4. OSI Wireline and Network settings: Duplex mode and packet size (to prevent packet fragmentation in routers with DF/DNF settings).
   
5. A/D serialization Settings: Left at Defaults
   
   

Server-side metrics:

1. Timestamp quality: The accuracy of timestamps on server-received packets compared to the server's PPS Stratum 1 source.
   
2. Packet latency: Measured in jitter.
   
3. Packet distortion: Noise resulting in random or out-of-sequence characters and CRC errors.
   
4. Surplus packets: Packets received by the server error-free, but rejected as surplus in areas with high receiver counts.
   
5. Factor "X": (More on that below).
   
   

Now, to the meat and potatoes: When it comes to system optimization, what server-reported metrics actually determine success?

1. Packet Count: Not accurate; it can include routed packets with broken UDP or higher-layer structures.
   
2. Packets Valid/Involved: Partially accurate, but valid/involved counts may only reflect the integrity of the UDP structure, not the quality of the payload.
   
3. Packets Used: What I consider true success—packets received at the server with an intact payload, timestamps within the system threshold, and a payload needed by the server to complete a calculation.
   
4. Packet "Efficiency": The ratio of "Valid" to "Used" packets (just my guess).
   

And now for "Factor X"...
I've systematically eliminated as many variables as possible from my setup. I use a field strength meter to identify RFI hotspots and mitigate them either by shutting off the source or using ferrite rings and clamps optimized to the source frequency. I've built three separate antenna types, tried various grounding scenarios, and added external RFI suppression to the antenna leads (1mF–2mF poly caps).

After a week of trial and error, my "Packets Used" count rose steadily into the 2,000–4,000 range—placing it in the top tier compared to similar receivers. 

Success! Or so I thought; read on

Unfortunately, my high "Packets Used" count isn't sustainable over time. It regularly declines to the 400–500 range for hours; it sometimes recovers to 1,000–1,500, and occasionally spikes back up to 2,000–4,000. My "Packets Used" count fluctuates wildly without any configuration changes, antenna changes,  environmental changes (including local weather), or additional RFI sources. I live 1 km from any neighbor, switching station, or other external RFI source. These fluctuations occur without any GPS errors, identified interference events, or filtering changes.

My only explanation is "Factor X" on the server side. Is it normal for "Packets Used" to vary wildly throughout the day as atmospheric or server conditions change, or is this shift caused by something on "my end"?

Again, apologies for such a detailed and long-winded post.

Current Setup:

• System Blue-Mini
  
• Three Coils of Times Microwave LMR-600 (2x each, with a 90-degree polarization shift)
  

Thanks

Brian (AA5H)


  Screenshot 2026-09-06 115010.png (Size: 59.89 KB / Downloads: 16)

  Screenshot 2026-09-06 115221.png (Size: 73.75 KB / Downloads: 17) ]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4296 Sat, 05 Sep 2026 17:22:50 -0500 omardy]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4296 For a while i follow your project and really love what the community is doing.

I am a software engineer, creative coder and musician.
I developed a MIDI sequencer, which consumes geo-coordinates and translates it into MIDI notes.
By transforming latitude and longitude into pitch and velocity, we can "audialize" all kind of cool nature phenomenons which are tracked.
All of this is 100% non commercial and for the purpose of art on a small scale.
Only 1 client would listen to the web socket and use the coordinates of the strikes.
Credit can be given (if that is even wanted) to whatever extend wished.

I would be very happy to present to you in detail how that can sound and look.
A small example video of a rendering of sound and visuals is attached here and helps you to get the vibe of the music and the visuals.
As the project is in development right now, let me know if you would be keen on seeing more.

https://youtu.be/XmU6bBBaNRA

I hope this messages finds you all well. 
Best regards!]]> For a while i follow your project and really love what the community is doing.

I am a software engineer, creative coder and musician.
I developed a MIDI sequencer, which consumes geo-coordinates and translates it into MIDI notes.
By transforming latitude and longitude into pitch and velocity, we can "audialize" all kind of cool nature phenomenons which are tracked.
All of this is 100% non commercial and for the purpose of art on a small scale.
Only 1 client would listen to the web socket and use the coordinates of the strikes.
Credit can be given (if that is even wanted) to whatever extend wished.

I would be very happy to present to you in detail how that can sound and look.
A small example video of a rendering of sound and visuals is attached here and helps you to get the vibe of the music and the visuals.
As the project is in development right now, let me know if you would be keen on seeing more.

https://youtu.be/XmU6bBBaNRA

I hope this messages finds you all well. 
Best regards!]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4294 Mon, 31 Aug 2026 06:40:05 -0500 AA5H]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4294
station: 3303 Newcastle, Ok
Operator: 2529

Thanks ! 

Brian AA5H]]>
station: 3303 Newcastle, Ok
Operator: 2529

Thanks ! 

Brian AA5H]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4293 Mon, 31 Aug 2026 04:54:28 -0500 Marvyn]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4293 I am developing a non-commercial and freely accessible weather website called GermanLightning.
The website focuses on Germany and displays weather radar, DWD weather warnings, lightning activity and planned storm tracking features.
I would like to ask whether I may use Blitzortung.org lightning data for this project.
The website will be:

• completely free to use
  
• non-commercial
  
• publicly accessible
  
• clearly credited to Blitzortung.org as the lightning data source
  

I also understand that the website should not request data directly from Blitzortung.org servers. I would therefore retrieve the authorized data on my own backend/server and serve it from there to the website.
My goal is not simply to create another copy of the Blitzortung live map. The lightning data would be combined with weather radar, official weather warnings and storm tracking to provide additional information about thunderstorms over Germany.
I would of course follow the applicable Blitzortung.org conditions and attribution/licensing requirements.
Could you please let me know whether this project would be eligible for data access and, if so, how I can request the necessary access?
Thank you very much.
Best regards]]> I am developing a non-commercial and freely accessible weather website called GermanLightning.
The website focuses on Germany and displays weather radar, DWD weather warnings, lightning activity and planned storm tracking features.
I would like to ask whether I may use Blitzortung.org lightning data for this project.
The website will be:

• completely free to use
  
• non-commercial
  
• publicly accessible
  
• clearly credited to Blitzortung.org as the lightning data source
  

I also understand that the website should not request data directly from Blitzortung.org servers. I would therefore retrieve the authorized data on my own backend/server and serve it from there to the website.
My goal is not simply to create another copy of the Blitzortung live map. The lightning data would be combined with weather radar, official weather warnings and storm tracking to provide additional information about thunderstorms over Germany.
I would of course follow the applicable Blitzortung.org conditions and attribution/licensing requirements.
Could you please let me know whether this project would be eligible for data access and, if so, how I can request the necessary access?
Thank you very much.
Best regards]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4292 Fri, 28 Aug 2026 13:57:16 -0500 Alidigitaly]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4292
Or a proper detailed instruction would be great instead of https://docs.lightningmaps.org/hardware/...multi-turn , with some blurry pictures.

Where can i find such?]]>
Or a proper detailed instruction would be great instead of https://docs.lightningmaps.org/hardware/...multi-turn , with some blurry pictures.

Where can i find such?]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4288 Wed, 26 Aug 2026 09:46:54 -0500 Bruce_AB0TL]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4288
The link provided is:

https://map.blitzortung.org

I contacted trueladderline and they confirmed the website was not responsive for them either and hopes it comes up soon. 

My question to the forum is the website down, or has the domain or syntax changed for the link.]]>
The link provided is:

https://map.blitzortung.org

I contacted trueladderline and they confirmed the website was not responsive for them either and hopes it comes up soon. 

My question to the forum is the website down, or has the domain or syntax changed for the link.]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4287 Wed, 26 Aug 2026 08:41:52 -0500 cutty]]> https://forum.blitzortung.org/mybb/showthread.php?tid=4287 Message sent to Egon....

  08-26-26 Status Issue.png (Size: 13.97 KB / Downloads: 35) ]]> Message sent to Egon....

  08-26-26 Status Issue.png (Size: 13.97 KB / Downloads: 35) ]]>