Lightning strike API fun
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
From https://www.lightningmaps.org/
Unsure if there are API docs.
Websocket endpoint: wss://live.lightningmaps.org/
Needs to be given positional data at start, i.e.
```json
{"v":24,"i":{"2":1106965},"s":false,"x":0,"w":1,"tx":0,"tw":0,"a":4,"z":2,"b":false,"h":"","l":372,"t":1597360180,"from_lightningmaps_org":true,"p":[88.4,160,-89.8,-143.1],"r":"close","extra":{"sec":268.869,"msg":"invisible"}}
```
Pretty printed:
```json
{
"v": 24,
"i": {
"2": 1106965
},
"s": false,
"x": 0,
"w": 1,
"tx": 0,
"tw": 0,
"a": 4,
"z": 2,
"b": false,
"h": "",
"l": 372,
"t": 1597360180,
"from_lightningmaps_org": true,
"p": [
88.4,
160,
-89.8,
-143.1
],
"r": "close",
"extra": {
"sec": 268.869,
"msg": "invisible"
}
}
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are named. Start by investigating the wss://live.lightningmaps.org/ endpoint and whether API documentation exists, then determine how the supplied positional data should be used; the issue does not define a completion criterion.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100