# AWS Tweet Crawler

1. What is AWS Tweet Crawler?
==============
A Java project that craws Tweets via Twitter's streaming API then publishes and stores them on AWS. 

2. Configuration
==============

2.1. AWS Credentials
--------------
* **`aws.accessKey:`** Your AWS access key
* **`aws.secretKey:`** Your AWS secret key

These properties can be specified as system property or can be given from **`aws-credentials.properties`** configuration file.

2.2. Twitter Credentials
--------------

To use Twitter API, you need to have a registered application. If you have not, you can create it from [here](https://apps.twitter.com/).

* **`twitter.oauth.accessToken:`** Access token of your Twitter application
* **`twitter.oauth.accessTokenSecret:`** Access token secret of your Twitter application
* **`twitter.oauth.consumerKey:`** Consumer key of your Twitter application
* **`twitter.oauth.consumerSecret:`** Consumer secret of your Twitter application

These properties can be specified as system property or can be given from **`twitter-credentials.properties`** configuration file.

2.3. Tweet Stream Configurations
--------------

* **`aws.tweet.bucketName:`** Bucket name for **AWS S3 to** store tweet data
* **`aws.tweet.streamName:`** Stream name for **AWS Kinesis Firehose** pushing tweet data
* **`aws.tweet.bufferSize:`** Size in MBs to buffer tweet data on **AWS Firehose** before uploading to **AWS S3**. Minimum value is `1MB`, maximum value is `128MB`. Default value is `16 MB`. 
* **`aws.tweet.bufferTime:`** Time in seconds to buffer tweet data on local before pushing to **AWS S3**. Minimum value is `60 seconds` (1 minute), maximum value is `900 seconds` (15 minutes). Default value is `120 seconds` (2 minutes).

These properties can be specified as system property or can be given from **`tweet-stream.properties`** configuration file.
`128MB`. 

2.4. Tweet Search Configurations
--------------

* **`aws.tweet.searchDomainName:`** Domain name for **AWS Elasticsearch** cluster to index tweet data

2.5. Tweet Filter Configurations
--------------

* **`tweet.filter.languages:`** Interested languages to filter tweets. There can be multiple languages seperated by **comma** (`,`) but **without any space**. For example: `tr,en,fr`.
* **`tweet.filter.keywords:`** Interested keywords to filter tweets. There can be multiple keywords seperated by **comma** (`,`) but **without any space**. For example: `football,basketball,tennis`.
* **`tweet.filter.locations:`** Interested geographical region to filter tweets. Geographical points are given as `longitude,latitude` tupples. This means that given points are grouped as pair sequentially and first one is longitude value and the second one is latitude value. Each location point must be seperated by **comma** (`,`) but **without any space**. Default value is `[-180.0 longitude, -90.0 latitude] [+180.0 longitude, +90.0 latitude]` means all world. For example: `12.21,34.43,56.65,78.87`.

These properties can be specified as system property or can be given from **`tweet-filters.properties`** configuration file.

2.6. General Configurations
--------------

* **config.tweetSearch.enable:`** Enables indexing tweet data on **Elasticsearch** cluster. So further analysis and queries can be done on these indexed tweet data and also can be visualised via **Kibana**. When seach is disabled, tweet data is only stored on **AWS S3**. But if search is enabled, tweet data is **also** stored and indexed on **AWS Elasticsearch**. So in this case (search is enabled), there is also backup on **AWS S3** for indexed data on **AWS Elasticsearch**. Default value is `false`.

These properties can be specified as system property or can be given from **`config.properties`** configuration file.

3. Deploy
==============
You can build and deploy the this Tweet crawler application to AWS via maven by `mvn -Pawseb clean package deploy` (or just run `build-and-deploy.sh`). So the crawler is packaged with its dependencies, uploaded to **AWS S3**, **AWS EC2** instance is provisioned and deployed onto it via **AWS Elastic Beanstalk**. Then it starts listening tweets and pushing them to **AWS S3** though **AWS Kinesis Firehose**.

**IMPORTANT NOTE:** Notice that the **AWS Elastic Beanstalk**'s maven [plugin](http://beanstalker.ingenieux.com.br/beanstalk-maven-plugin/usage.html) needs `~/.aws/credentials` file that contains your AWS access and secret keys in the following format:

```
[default]
aws_access_key_id=XYZ123...
aws_secret_access_key=ABC567...
```

There are also some configurable properties in the `pom.xml`. Here are some of remarkable ones:
* **`beanstalk.instanceType:`** Specifies instance type of the **AWS EC2** machine where crawler runs. See [here](https://aws.amazon.com/ec2/instance-types) for more details about **AWS EC2** instance types.
* **`beanstalk.keyName:`** Specifies **AWS EC2** key pair for connecting to the **AWS EC2** machine where crawler runs.
* **`beanstalk.environmentType:`** Specifies whether crawler will run as a single instance or as a cluster behind the load balancer on multiple **AWS EC2** instance with auto scaling options. In this project we are using `Single Instance` environment type because current logic (behaviour) of the application is not suitable for clustering and auto scaling because even though there are multiple applications on multiple instances, all of them will receive same tweets and so there will be no load distribution between the applications in the cluster. I have just mentioned this configuration to show that there is a AWS feature that  can be useful for other cases.
* **`aws:autoscaling.???:`** Specifies what is the limits of the cluster (minimum and maximum instance count in the cluster) for scaling up/down and in which conditions cluster will scale up/down.


Simulation of a 2 dimensional cloud of space dust

# 2D-Accretion-Simulation
This is an old, now abandoned project I did in my senior year of high school to explore multi-threading and physics simulations.  
If you'd like to watch a few of the renderings of the simulation, check out this [YouTube playlist](https://www.youtube.com/playlist?list=PL8DyCuld6vsKOp_jDzYFnVmI58OQiFuPw)!


# FroggySwim-2D

## Game Introduction
Four score and seven years ago our fathers brought forth on this continent, a new nation, conceived in Liberty, and dedicated to the proposition that all men are created equal. Now we are engaged in a great civil war, testing whether that nation, or any nation so conceived and so dedicated, can long endure. We are met on a great battle-field of that war. We have come to dedicate a portion of that field, as a final resting place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we should do this. But, in a larger sense, we can not dedicate -- we can not consecrate -- we can not hallow -- this ground. The brave men, living and dead, who struggled here, have consecrated it, far above our poor power to add or detract. The world will little note, nor long remember what we say here, but it can never forget what they did here. It is for us the living, rather, to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced. It is rather for us to be here dedicated to the great task remaining before us -- that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion -- that we here highly resolve that these dead shall not have died in vain -- that this nation, under God, shall have a new birth of freedom -- and that government of the people, by the people, for the people, shall not perish from the earth.
## Main Character
### The elder
![alt tag](http://www.people.com.cn/mediafile/200512/09/F2005120913054600000.jpg)


Friction: Zero
==============

A racing game about hovering vehicles.


TODO
----

### Bugs

* Move the `* dt` from the gyro's ECU into `apply_gyroscope()`.
* Animations
  * See branch magnesium-animation-bug. Using subParts in an Actor causes an
    exception when .pose is used, as Actor seems to look for the file with the
    animation, despite it being present in the model file.
    * Revert to last commit before the merge; animations are now in separate
      files. Whoops...
    * Monitor issue or fix it yourself: https://github.com/panda3d/panda3d/issues/647
* All physics-related things that use `globalClock.dt` should pull the time step
  size from the Environment instead, so that they too are capped by the physics
  minimum framerate.
* When a vehicle flips on its back, it gets repulsor contacts above (globally)
  the repulsors.


### Features

* Clamp timestep in physics simulation
  * (SMALL) Move value min_frame_rate into settings file
* (SMALL STUFF) Default controller for NPC vehicles
* Controls
  * Space mouse bindings
* ECU
  * Gyroscopic stabilization
    * Replace numpy.linalg.eig() with a PCA-based approach
  * (low importance) Make angular stabilization deactivateable
* Aerodynamics
  * Airfoil effect
* Course gates
  * Check which gate has been passed this frame
  * Race rules accounting
  * Timekeeping
* Particle systems
  * Repulsor contact points
  * Vehicle-terrain crashes
  * Vehicle-vehicle crashes
* Sound
  * Background music
  * Crashes
* GUI
  * (SMALL) Basic setup: In a separate render bin
  * (SMALL) Elevation: Fighter jet like height-over-ground indication
  * (SMALL) Speed direction
* Camera controls and automatics
  * (SMALL) HUD element for camera mode
  * Camera distance and FOV should be related to vehicle's linear speed.
  * Camera should respect the ground / objects.
  * Cinematics
* Shadows
* Repulsoring other vehicles
* Game Mode: Free Driving
* Countdown to start
* Game Mode: Timed solo race
* Recording races
* Game Mode: Racing against ghosts (recorded races)


### Art
* racetrack
  * Add lane demarcations (ca. 2.75m apart)
  * Align starting positions with track
  * Add a gentle hilliness to the terrain
  * Add a stretch gently curving back and forth
  * Make hard curves gentler and/or add a bowl shape to their outsides
  * Move trees a few meters away from the track
    * More trees!
  * There should be something big in the center of the map that makes it easier
    to estimate one's position on the map.
* Lab map
  * More visual cues to determine up and down in tunnels
  * Plug up holes, basement_pool sticks out in east-tunnel.
* hilltrack
  * Make the texture direction align with the track, so that you can see where
    in the pipe you are on the left/right direction.
  * Make the bends at the edge higher and more overbearing, to reduce the risk
    of slipping off the track.
* Driving school: A tutorial map.
* Sounds:
  * engine (playbackrate to speed?)
  * vehicleXvehicle impact
  * vehicleXenvironment impact
* Music:
  * menu
  * track


### Tools

* Normalize pman build / asset workflow
* Map / vehicle verification


### Other

* Add license: BSD and CC0?
* Add CREDITS


### Post-Prototype

* ECSify everything
* Driver g-meter
* Exchangeable vehicle parts
* Menu
  * Main menu
  * Options
  * Track selection screen
  * Vehicle selection screen
    * Vehicle material color-picker
    * Choose repulsor model
* Keybindings
  * Allow for multiple players
  * Allow for multiple devices (per player?)
* Limits on thruster
  * Fuel, replenishable by pit stop
* Ingame screens from trackside AI cameras
* Surfaces: Different materials can be repulsed differently well
* Points (bonus time?) for tricks
* Game mode Tricks: Get as many tricks points as possible in a limited time
* Game mode Rally: Timed race with time deducted for tricks
* Game mode Treasure Hunt: Find items hidden on a map
  * Radar may indicate distance and/or direction when close
* Quantum lock: Become locked to a track like a superconductor in a magnetic
  field
* Minimap
* Repulsor pads on maps
* Optional gates
* AI
  * Cruise mode / Autopilot
    * Follow a given direction or given path
    * ...and correct if pushed from it
  * Racing
  * Civilian
  * Escaper
    * Try to stay away from a given set of points
    * Try to get away from a given set of vehicles
  * Pursuer
    * Stay close to a given vehicle
* Game mode: Series (requires racing AI)
  * Formula R: Rally-style tracks
  * Formula 0: Race and city tracks
  * Formula C: Cross-country longhaul drive
  * Formula Q: Quantum lock tracks (requires quantum lock)
  * Formula X: One of each, with or without changing cars between races
* Game mode: Taxi driver / Transporter (requires civilian AI)
  * Pick up and drop off guests / cargo
  * Optimize for time and / or passenger comfort
* Game mode: Escape and Pursuit (requires escaper and pursuer AI)
  * The escaper tries to stay a distance away from the pursuer
  * The pursuer tries to not let that happen until a timer runs out
* Multiplayer
  * Split-screen
  * Networked
* Damage model
  * Artwork for aesthetic damage
  * Systems (repulsors, gyros, thrusters) suffer performance loss (low-powered
    or offline) for a time (or permanently)
* Game mode: Demolition Derby (requires damage model. May require weapons.)
  * Last one standing
* City map: Start with a few blocks and expand.


Models checklist
----------------

* Vehicles
  * Scene
    * friction			(1)
    * mass			(1000)
  * fz_repulsor:N
    * activation_distance	(5)
    * force			(3000)
  * fz_thruster:N
    * force			(20000)
  * fz_spawn_point_connector
  * fz_cockpit
    * fz_cockpit_camera

* Map
  * Scene
    * gravity (temp)		(9.810)
  * fz_collision
    * named_collision
      * friction		(1)
  * fz_spawn_point:N


Python script to interact w/ NMEA 0183 compatible usb GPS receivers

# Author: Jonathan Woolf jwool003@ucr.edu

This GPS package is compatible with all NMEA 0183 compliant <a href="https://www.amazon.com/HiLetgo-G-Mouse-GLONASS-Receiver-Windows/dp/B01MTU9KTF/ref=sr_1_8?keywords=gps+usb&qid=1560277792&s=gateway&sr=8-8">USB GPS receivers</a>. When called, the gpsData() function connects to the active port, for example "ttyACM0", to read in NMEA sentences and return latitude, longitude, MPH, timestamp in PST, and the date. The function also outputs data to three separate text files. Pos.txt will always store the most recent position of the device, log.txt will maintain a log of position and speed that is updated once per minute, and speed.txt will keep a log that only updates as the device moves.

In the example script, getIPAddress() prints out the IP address of the device, then gpsData(), whithin an infinite loop nested in a try / except block, prints its return statement to terminal. Type 'ctrl c' to guarantee that the port is closed when you end the program.

The final script included is chartPath.py which combines the functionality of gps.py with pygmaps.py to generate an html map which shows the device's journey from point A to point B. Simply run the scipt at your starting location and press 'ctrl c' when you have reached your destination to generate the map.

## Give yourself permanent access to the port:
 # Discover which serial port is in use
 python -m serial.tools.list_ports
 # Navigate to rules.d directory
 cd /etc/udev/rules.d
 # Create a new rule file
 sudo touch my-newrule.rules
 # Open the file
 sudo vim my-newrule.rules
 # Add the following:
 #KERNEL=="ttyACM0", MODE="0666"

## Tutorial:
#### Dependencies
 pip install PYserial
#### Access gpsData()
 import gps
 port = gps.serialPortInit()
 gps.gpsData(port)

# Investigation of Forest Fires with Google Earth Engine

## Contents
##### 1. Introduction
 1.1 What is Google Earth Engine and How it Works
 1.2 Audience
 1.3 License
 1.4 Comparasion Between Supervised and Unsupervised Methods
 1.5 Tools and Functions
 1.6 Register to Google Earth Engine
 1.7 Google Earth Engine Javascript Browser Layout
 
##### 2. How to use Code
 2.1 Code's User Workflow
 2.2 User Workflow Youtube Tutorial Video
 2.3 Importing Code
 2.4 Saving Code
 2.5 Area Selection
 2.6 Choosing Dates Before and After Burn
 2.7 Training Sample Selection

##### 3. Analysing Results
 3.1 Visual Image Analysing
 3.2 Chart Analysing
 3.3 Numerical Analysing
 3.4 Exporting Images and Charts
 
---

## INTRODUCTION:

### 1.1 What is Google Earth Engine and How it Works:

* Google Earth Engine (GEE) allow us to reach satellite image catalogs (catalog of the Sentinel – MODIS – Landsat) and use geospatial or image processing algorithms on those images. There are three different methods (JavaScript – Python – REST) to reach this image catalogs. In this tutorial we use the JavaScript (JS) as it is the native language of GEE.

* Javascript has its own Google Earth Engine platform can be reachable from any browser. The browser link is (https://code.earthengine.google.com/) 

* When you click to link it will tell you need to register. Process Explained in section 1.5.

* When we start the code; it sends a request to servers for compute and then gets results. So it will need internet connection.
 
![alt text](https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/01_What%20is%20Google%20Earth%20Engine_.png "Logo Title Text 1")

---

### 1.2 Audience:

* This open source code can be usable by anyone who want to see neutral true data about forest fires and environment also who want to test, develop for better forest fire investigation and researches.

---

### 1.3 License:

* This tutorial prepared by Berk Kıvılcım under the mentorship of Berk Anbaroğlu and Nusret Demir.

---

### 1.4 Comparasion Between Supervised and Unsupervised Methods:

**Supervised Method:**
* Mostly the results will be better. (Depends on training sample quality)
* The code works faster than unsupervised method. (Still slower than unsupervised in overall time because we need to select training sample)

**Unsuperivised Method:**
* The results depends on algorithm not the human so results will be more standardized.
* No need to select training sample so it need less human power and faster than supervised method.
* Easy to use but the code works slower than supervised method.

---

### 1.5 Tools and Functions:

* The code can be able to compute how many forest field burned (in hectare unit as default), Normalized Burn Ratio (NBR) and Normalized Difference Vegetation Index (NDVI) Charts, Burn Severity Rate, Heat Graphics, time interval of the burning and shows before-after satellite image results by using Sentinel-2 Satellite. Those datas can be downloadable.

* **IMPORTANT: You need to change something in this code for some spesific results like burn severity calculation. Each time you change something from code please don’t forget reclick to Run button for see the latest results.**

---

### 1.6 Register to Google Earth Engine:

* When you try to access https://code.earthengine.google.com/ you will face up with register screen. If you registered once you will never face it again.

* Click to "here" button then in next page fill the form and send a request to google. Usually your request approve immediately but sometimes it will take a while.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/%C3%A7emberli.jpg" width="100%">

---

### 1.7 Google Earth Engine Javascript Browser Layout:

![alt text](https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/layoutb%C3%BCy%C3%BCk.jpg "Logo Title Text 2")

* **Script Area:** The area is where we put our code.

* **Console Area:** The area is where graphical and numerical results displayed.

* **Map Area:** The area is where results of visualization displayed.

---

## HOW TO USE CODE:

### 2.1 Code's User Workflow:

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/workflowframe.jpg" width="70%">

---

### 2.2 User Workflow Youtube Tutorial Video:

[[VIDEO LINK HERE CLICK ME]](https://www.youtube.com/watch?v=nVx4gLdaU9A)

---

### 2.3 Importing Code:

* Download and see the source code with the help of notepad softwares or directly open the code from the link below here then copy paste to whole source code into the Google earth engine's script section.

* **The Link for source code**: https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/Forest_Fire_Gee_with_more_comments.js

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/birle%C5%9Fik2.jpg" width="100%">

---

### 2.4 Saving Code:

* If you wanted to save your code into your Google Earth Engine account create a repository and load the script code into it.

* Click NEW, then click Repository:
<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/makereposi.jpg" width="50%">

* Write your repository name and create. It will Show up in Owner section.
<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/newrepo.jpg" width="40%">

* Then click to save it in your repository. You can use the code in this repository anytime you want.
<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/save.jpg" width="50%">

---

### 2.5 Area Selection:

* There are two different methods to identify polygons in other name areas.

* As default an example area sample identified which is cover to Izmir/Karabaglar region.

* **First method:** If you estimate or know the corner coordinates of the polygon which is you want to work it can be directly input by manually.

Just replace those coordinates with which coordinates you want to use. You can add or remove more polygon corner. **Those coordinates must be in Geodetic Coordinate format (latitude and longitude) which is based on WGS84 Ellipsoid .**

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/koordinat.jpg" width="60%">

* **Second Method:** If you want to select your area manually follow the steps below here. Also you can easily find your work area with search bar just typing your adresses.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/adress.jpg" width="100%">

**Step - 1:** Click to draw polygon button.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/%C5%9Fekil%C3%A7iz.jpg" width="30%">

**Step - 2:** Draw your polygon on map area.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/poligon%C3%A7iz.jpg" width="60%"> 

* Also you can change the back layer of the visualization area for better visual understand. Two different options in here. Map and Satellite. If you select the satellite; the program will show the area with high quality satellite images.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/uydu.jpg" width="30%">

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/Screenshot_5.jpg" width="50%">

* When you finish the drawing polygon, the properties of this polygon will Show up above the script. Just don’t forget delete the whole initial ‘var geometry’ because we identify new polygon.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/yenikor%C3%A7er.jpg" width="50%">

---

### 2.6 Choosing Dates Before and After Burn:

* The dates are in ‘yyyy-mm-dd’ format. Enter a date you think was before the fire into the “var Start’s date section” and after the fire into the “var End’s date section”. When inputing the dates try to close them to date during burn. The closer to date during burn is gives better results.

```javascript
var Start=ee.Date('2019-07-05'); //date before burn
var End=ee.Date('2019-10-05'); //date after burn
var END =End.advance(50,'day');
```

**Some Date Selection Tips:**

* **Tip - 1: If your "var End" date is to close to present day you should change the "var END's" 50. This 50 means 50 days later from the "var End's" so sometimes it exceed the present day.**

* **Tip - 2.1: Trees will show different health situation with different seasons and also some exterior parameters like snow can effect the results. For example; you think the fire starts at july. Then select your time interval between june and August not like the January to December. In conclusion if Start and End dates close to burn date results will be more correct. If your region not tropical and you know the burn not start during winter season you can apply the filter below here for winter-autumn changes.**

* **Tip - 2.2: This season based erros in charts can be ignorable. Initial date filter shows the all data during the whole year (first day to 365th day) but If you change this initial values in the code's line 60 then you can filter the datas. For example If you write 122 and 275 as start and end dates of the filter then the code only count the dates between 1 May to 1 October so not count the winter days and in the conclusion there would be no winter data in charts. In the example above here; 122 represent 122th day of the year which is means 1 May and 275 means 275th day of the year and its the 1 October.**

```javascript
.filter(ee.Filter.dayOfYear(122, 275)) 
```

<pre class="tab"> Unfiltered 2018-2020 graphic for 2019 forest fire. Filtered 2018-2020 graphic for 2019 forest fire.</pre> 

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/biti%C5%9Fikgraf.jpg" width="100%">

* **Tip - 3: Google Earth Engine is a new technology so If you try to get old fire datas like 1999-2007-2010... There would be no data catalog so the code won't work and If you try to get newest fire datas like today's date the satellite probably not collect the data yet so you should wait a couple days or check the other satellite's datas.** 

---

### 2.7 Training Sample Selection:

* The code uses supervised classification for calculting how much area burned. For this process code needs to select some training areas. We can select it with point or polygon methods. I suggest to use polygon method. 

* Firstly create classes. Default classes are ("soil" (soil or dry land), "tree" (healthy vegetation area), "burned" (burned areas)) so this classes must be created by user but still new classes can be added.

* Click to +new layer

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/new%20layer.jpg" width="50%">

* Determinede class properties. Type your Name; "soil", "tree" or "burned". Those names need to be exactly same from tutorial. Select FeatureCollection. Write **LC** which is mean landcover (do not type landcover or something different just type LC) to property section then write the values started from 01. **Burned areas property value always must be 03.** The reason behind that is the code export the 3rd class from classified image as only burned area layer so class value must be 3.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/%C3%B6zellik_%C3%A7er%C3%A7eve.jpg" width="50%">

* Then select the samples like from the below picture.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/sample.jpg" width="100%">

* If you want to add more classes than default there would be an extra step. Create your class and determine properties then in the code add .merge('your_new_class') to "var feature".

```javascript
var feature= soil.merge(tree).merge(burned);
```

* Also change classified picture's map.addLayer's max:___ to how many classes you want. In the beginning we have 3 classes so max: would be 3. We should change it.

```javascript
Map.addLayer(classified,{min:1, max:3, palette:['0000FF','00FF00','FF0000']},'classification');
```

Now we entered all things the code needed for run. Just click to run button and see the results.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/run.jpg" width="100%">

---

## ANALYSING RESULTS:

### 3.1 Visual Image Analysing:

* When we click run, the code process some algorithms which they will explained in workflow section of the tutorial. Results are show in console and map panels. For visual analysis use map section and for the numerical analysis check to console section.

* After the running code its divide map area into two section. The left part shows RGB – NBR images before burn and classified image after burn. The right part shows RGB – NBR images after burn and only the burned areas which is calculated from classified image.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/b%C3%BCt%C3%BCn.jpg" width="100%">

**RGB Image:** The image which is formed from red, green, blue layers. This layer shows us to what human eye can see.

**NBR Image:** NBR image maded from NBR calculation results. This layer help us to understand burning.

**Classified Image:** The image which is shows dry ground, healthy vegetation areas and burned areas.

**Only Burned:** The layer which is represent only the burned areas.

* We can check all of them from Layers section as a layer of each panels.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/layers.jpg" width="60%">

### **VERY IMPORTANT:** 
**Please check the classification is good or not. Its all about your training sample selection. Best way to check it; look the "only burned layer (white layer)" and "RGB Later layer or base satellite vision" together. If burned areas not cover the most of real burned areas or cover too much area like dry ground or healthy vegetation then click to Reset button. This button will turn back to inital layout which is shown in section 2.5's screenshot. Don't worry your previous training samples will be protected. Then select more training samples from where the classification looks wrong.**

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/layerli.jpg" width="60%">

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/bilgili.jpg" width="60%">

---

### 3.2 Chart Analysing:

* After the clicking run button, charts automaticly will show up in console section. There is two different chart. One shows the NBR and the other one shows NDVI. This both charts gave us the information about vegitation health and date interval of the burning.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/nbr.jpg" width="50%">

* NIR means Near Infra Red and SWIR means Shor Wave Infra Red bands of the satellite sensor.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/sentinel.jpg" width="50%">

* If you wanted to understand burning date interval put your Mouse on to graphic’s line. The breaking points (where the graphic mostly changed) will shows the date of burning.
For example: According to below graphic the fire started at ‘16-08-2019‘ and continued until the ’21-08-2019’. This example based on İzmir Karabağlar and also its burning date data published from trthaber (turkish radio and television institution news).
* Referance web site for Izmır Karabağlar forest fire new is https://www.trthaber.com/haber/turkiye/izmir-ve-mugladaki-orman-yanginlari-uydudan-goruntulendi-427564.html

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/haber.jpg" width="70%">
<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/grafikler.jpg" width="70%">

---

### 3.3 Numerical Analysing:

* This code provide some numerical calculations like how many hectare burned or how bad is the burned area. Before the start we need to understand GSD (Ground Sample Distance).

* **GSD:** Ground Sample Distance is the lenght of each pixel’s edges corresponds in the real world distance. In this tutorial we used Sentinel-2 satellite which has the 10 meter GSD lenght for maximum resolution. That means each pixel correspond 100 (10*10) meter square area. Less GSD number means better resolution. 

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/istatistik.jpg" width="70%">

* **Burn Severity Calculation:** When we checked break points of the charts we understand the burn dates. Now check the NBR values of this breakpoints and input it to this beforevalue (NBR value of the date when fire begin) and aftervalue (NBR value of the date when fire stop). This will tell you the burn severity.

```javascript
var beforevalue=0.174
var aftervalue=-0.045
var delta=beforevalue-aftervalue
```

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/tablo.jpg" width="70%">

**Referance for the burn severity levels:** http://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio#:~:text=The%20Normalized%20Burn%20Ratio%20(NBR,shortwave%20infrared%20(SWIR)%20wavelengths.

---

### 3.4 Exporting Images and Charts:

* Exporting before and after RGB images quite simple. If you want before the burn images then click to “Export to Drive” button of left side map. If you want to after images then click to right side’s button. The difference between getting screenshot and pressing export; Exported images will be geotiff format which means images also have coordinate datas.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/button.jpg" width="20%">

* After the clicking button check the Task Section and clik to RUN.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/task.jpg" width="50%">

* Then click to Run again. This will export the image into your Google Drive adress. 
* **Note:** If the code tells, you passed the pixel limit you can select smaller area or increase the scale. Scale also is GSD. **That will decrease your image’s resolution.**

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/son.jpg" width="50%">

* If you want to export charts click to upper-right button of the chart.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/grafik%20indir.jpg" width="50%">

* Then select to which format you want to download.

<img src="https://github.com/axecasper/Google-Earth-Engine-Forest-Fire/blob/master/images/formats.jpg" width="50%">


---

This is an attempt of reproducing the game asteroids using modern programming languages

# ASTEROIDS ALMOST FROM SCRATCH
This is an attempt of reproducing the game [asteroids](https://en.wikipedia.org/wiki/asteroids!) using modern programming languages. The idea is to track the progress and time each stage of development in this document. If possible, I want to finish this project in under 24h. Feel free to see the `diff` between the commits and maybe learn something just like I did.

#### Check it out [here](https://asteroids-almost-from-scratch.herokuapp.com/)

The game is based in `html5 canvas`, `CSS` and `ES6 javascript`. No extra libraries or engines will be used.

Since I've already worked on a project to reproduce [spacewar-almost-from-scratch](https://luxedo.github.io/spacewar-almost-from-scratch/), I'll be using much of it in here. If you want to see how it was done, check it out on [GitHub](https://github.com/luxedo/spacewar-almost-from-scratch).

## GOALS
* ~~Add `LICENSE.md` and `README.md~~
* ~~Copy the `spacewar` files~~
* ~~Host somewhere~~
* ~~Make screens square~~
* ~~Remove gravity, player2 and `blackhole`~~
* ~~Modify `Ship` class~~
* ~~Modify `Shot` class~~
* ~~Create `Asteroid` class~~
* ~~Draw asteroids~~
* ~~Create `Saucer` class~~
* ~~Draw saucers~~
* ~~Create `Score` class~~
* ~~Modify collision mechanics~~
 * ~~Collision with borders~~
 * ~~Create Asteroid breaking mechanics~~
 * ~~Collision Asteroid-Player~~
 * ~~Collision Shot-Asteroid~~
 * ~~Collision Saucer-Shot~~
 * ~~Collision Saucer Player~~
 * ~~Collision Saucer Shot-Player Shot~~
 * ~~Collision Saucer Shot-Player~~
* ~~Create level mechanics~~
* ~~Create life mechanics~~
* ~~Implement saucer AI~~
* ~~Modify menu screens~~
 * ~~Modify `start screen`~~
 * ~~Modify `credits screen`~~
 * ~~Modify `game over screen`~~
* ~~Create High scores screen~~
* ~~Find someplace to host high scores~~
* ~~Implement pause~~
* ~~Modify sounds~~
* ~~Improve webpage~~
* ~~Get play testers feedback, List requests/bugs~~
* ~~Fix requests/bugs~~
* ~~Finished!~~

## Progress Reports
00:00 - Start! This project started October 23rd, 2016 at 17:30 (BRT). I'll be timing each step and will be placing the time it took from the beginning along with the achieved goal.

## 00:10 - LICENSE and README
This project is under a [GNU GPL3](https://www.gnu.org/licenses/gpl-3.0.en.html) license. Have fun! :wink:

## 00:15 - Host somewhere
For now, I'll be hosting it in [github pages](https://pages.github.com/) since it's easy deploy. Check it out [here](https://luxedo.github.io/asteroids-almost-from-scratch/)

## 00:30 - Copy the `spacewar` files
Since this game is also made with vector graphics, I copied the [spacewar](https://luxedo.github.io/spacewar-almost-from-scratch/) I made to the project folder and changed the favicon, the main color and a few tweaks. In the end it was looking like this:
![spacewar copy](report-assets/spacewar-copy.png "spacewar copy")

## 00:45 - Make screens square
Asteroids have a square screen, so I removed the stars and the round mask of the spacewar.

## 01:00 - Remove gravity, player2 and `blackhole`
The game does not have the `blackhole` (star) in the middle as `Spacewar` has, so it has been removed along with the gravity mechanics. Also, I don't want to add a 2 player mode because in the original game the players took turns playing. Instead I'll try to make a online highscore.

## 01:20 - Modify `Ship` class
The ship sprite is much simpler in Asteroids. So it was easy to draw: ![ship](report-assets/ship.png "ship")
![ship thrusters](report-assets/ship-thrusters.png "ship thrusters"). I changed some properties to make the ship more agile and interesting to play.
```javascript
const player1Vectors = [[[5, 0], [-4, -3], [-3, -2], [-3, 2], [-4, 3], [5, 0]]];
```

## 01:30 - Modify `Shot` class
The shots were also easy. I just changed some properties and done.

## 02:50 - Create `Asteroid` class and draw asteroids
To create the asteroid class, I inherited the `BaseClass`. The only addition was a rotation speed property that makes the asteroid spins continuously.

To draw the asteroids, I made a function that randomly generates points in a grid and used those vectors.

```javascript
function makeAsteroidVectors() {
 let vectors = [randomCoords(0, 0), randomCoords(1, 0), randomCoords(2, 0), randomCoords(3, 0),
 randomCoords(3, 1), randomCoords(2, 1), randomCoords(3, 2), randomCoords(3, 3),
 randomCoords(2, 3), randomCoords(1, 3), randomCoords(0, 3), randomCoords(0, 2),
 randomCoords(0, 1)];
 vectors.push(vectors[0])
 return [vectors];
}
```

Luckly for me, in the constructor, I have made the vectors translate to make the centroid of the object the coordinates (0, 0), then it's easy to rotate the object around the centroid. And there's also a scaler in the constructor to chose the size of the objects which came in handy to make asteroids of different sizes.
This is the end result

![asteroid class](report-assets/asteroid-class.gif "asteroid class")

## 03:10 - Create `Saucer` class and draw saucers
Instead of making a `Saucer` class, I'm recycling the `Ship` class and will control it in the gameloop.
The vectors for the
![saucer](report-assets/saucer.png "saucer") are:
```javascript
const saucerVectors = [[[-1, 0], [1, 1], [5, 1], [7, 0], [5, -1], [1, -1], [-1, 0]],
 [[2, 1], [2.5, 2], [3.5, 2], [4, 1]],
 [[-1, 0], [7, 0]]];
```

## 03:20 - Create `Score` class
The score class is super simple, it took 10 min to make and test it.

![score](report-assets/score.png "score")
```javascript
class Score {
 constructor(x, y, size) {
 this.x = x;
 this.y = y;
 this.size = size;
 this.score = 0;
 }
 draw() {
 writeText(this.x, this.y, this.score.toString(), this.size);
 }
}
```
I thought about making the score like the original game, but I really liked working with the [Hershey Vector Font](http://paulbourke.net/dataformats/hershey/).

## 03:25 - Modify collision mechanics - Collision with borders
It was changed in the `update` method of `BaseSprite` the way the game computes a collision with the borders.
```javascript
// border collision
if (this.x < 0) this.x = 600;
if (this.x > 600) this.x = 0;
if (this.y < 0) this.y = 600;
if (this.y > 600) this.y = 0;
```
## 04:10 - Modify collision mechanics - Collision Asteroid-Player
Since the collision function was implemented in `Spacewar`, it was easy to calculate the collisions with the asteroids. I just had to add a conditional to make the asteroids split in smaller ones.

## 05:00 - Modify collision mechanics - Collision Asteroid-Shot
The collision mechanics were easy to implement again, but this part took a while longer because I wasn't using correctly the splice method and along with the non-blocking property of JavaScript I was getting lots of bugs.

## 05:20 - Modify collision mechanics - Collision Saucer
The last part of the collisions was easier because there were code from Spacewar that did exactly that.

## 06:00 - Create level mechanics
The game is played in waves of increasing difficulty, so, when the count of asteroids is zero, a new level starts with more asteroids. The saucers appears randomly with increasing probability (1/level) over time.
Also, the score system was upgraded:
* Asteroids - 20 (large), 50 (medium), or 100 points (small).
* Saucers - 200 (large), or 1000 points (small).

## 06:00 - Pause!
Right now, October 24rd, 2016 at 00:45 (BRT), I'm giving a break from the project. About 2/3 of the goas are done, maybe I can finish it in under 12h, that would be neat!

## 06:45 - Create life mechanics
The life mechanics could have been a class, but I opted for implementing all in the gameloop. I used the `ShipCursor` class and an array to draw ships bellow the score that indicates the life of the player. Now the game is playable and looks like this:

![game so far](report-assets/game-so-far.gif "game so far")

## 07:30 - Implement saucer AI
The saucer AI was also salvaged from `spacewar`, the main change is that the saucer is much slower and the shots interval is much higher.

![saucer ai](report-assets/saucer-ai.gif "saucer ai")

## 08:00 - Modify menu screens
All the screens were partially done, so it was just a matter of changing the text and the position of some stuff. I added a few asteroids in the screens to make them look more interesting.

![new screens](report-assets/new-screens.gif "new screens")

## 08:40 Create high score screen
I copied the `credits screen` and modified it to make the `high score screen`. At this point I didn't worry about how I'm connecting the high scores with some server.
Also, I added a space for the player to put his/hers name in the `game over screen`.

![high score screen](report-assets/high-score-screen.png "high score screen")
![game over name](report-assets/gameover-name.png "game over name")

## 14:00 - Find someplace to host high scores
It took 5 hours to convert the project to be hosted at [Heroku](https://www.heroku.com/
), learn a bit of [Postgres](https://www.postgresql.org/) and learn how [Heroku Postgres](https://www.heroku.com/postgres) works. Phew, it took a while longer than I expected, but it's working!

I started by setting up a server with [node](https://nodejs.org/en/) and [express](http://expressjs.com/) and created some routes. I'm using [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) to GET and POST
the high scores. I didn't put the effort to make an authentication, so my API is compvarly exposed.

```javascript
let express = require('express')
let bodyParser = require('body-parser')
let app = express()
let pg = require('pg');

app.use(bodyParser());
app.set('port', (process.env.PORT || 5000));
app.use(express.static(__dirname + '/docs'));
app.get('/highscores', getHighScores);
app.post('/sendscore', postHighScores); // shhhh, pretend you didn't see this
app.get('*', (req, res) => res.redirect('/'));
```

When calling the high scores screen, I place the results of a query inside the screen
object which is rendered on screen. I used [jQuery](https://jquery.com/) for the requests,
I allowed myself to use an external library in this case because this is not related
to the game engine.

```javascript
$.get("/highscores", data => highScoreScreen.scores = data);
```

## 14:40 - Modify Sounds
Luckly for me, it was easy to find the sound assets. I downloaded all the sounds from
[http://www.classicgaming.cc/classics/asteroids/sounds](http://www.classicgaming.cc/classics/asteroids/sounds). Thanks guys! I just changed the names of the assets and done.

In html5 it's a bit hard to work with sounds, they sound choppy sometimes and the same
sound asset doesn't like to be called while it's playing.

## 15:40 - Improve webpage
For the webpage, I added a static page to get a list of the high scores.

![highscores](report-assets/highscores.png "highscores")

## 16:00 - Get play testers feedback, List requests/bugs
* ~~Fix player explosion - `me`~~
* ~~Footer is leaking into game-frame - `Thiago Harry`, `Ule`, `Rodrigo Mendes`~~
* ~~Transpile code to ES5 - `permith`~~
* ~~Add a blinking cursor for the name input - `me`, `Rodrigo Mendes`~~
* ~~Improve saucer and thruster sounds - `me`~~
* ~~Improve keyboard input - `me`~~
* ~~Duplicating highscore - `Ule`~~
* ~~Ship Spawn Effect - `Guno`, `poppij`~~
* ~~Spawned outside the screen - `Cae`, `Guno`~~
* ~~Query for name in `gamover` screen - `me`~~
* ~~Check multiple keypresses - `poppij`~~

## 19:00 - Fix requests/bugs
Thanks to the playtesters for the feedback!!
 * Caetano Sato
 * Gustavo Ogg
 * permith
 * poppij
 * Rodrigo Mendes
 * Thiago Harry
 * Ulisses Sato

I listed the requests and fixed them (I hope so). The game got so much better with the new indicator of the spawn point and the player destruction debris are much nicer.
The input for the High Scores is better, and the keypress events also.
Unfortunately I wasn't able to reproduce the problem of `poppij` with multiple keypresses. I looked a little and found that it might be a hardware limitation.

![explosion](report-assets/explosion.gif "explosion")

## 19:00 - Finish pt1.
Well, that was fun once again.
This is my third game made this way, check the other ones:
* [spacewar-almost-from-scratch](https://github.com/luxedo/spacewar-almost-from-scratch)
* [pong-almost-from-scratch](https://github.com/luxedo/pong-almost-from-scratch)

I think that the most valuable lesson was messing with heroku's database. Have I not created the high scores features and I would have finished in almost 12h.

Since there's still 5h to complete the proposed 24h, I'm launching a patch if there's enough feedback.

That's it for now!
### Bye

Download Meteorological Data from NASA POWER API (https://power.larc.nasa.gov/)

# NASAMeteoDataTool
![nasa](https://user-images.githubusercontent.com/18232521/75673566-eb882880-5c8b-11ea-9a65-995f94b876bf.png)

Download Meteorological Data from NASA POWER API (https://power.larc.nasa.gov/)

The NASA POWER database is a global database of daily weather data
specifically designed for agrometeorological applications. The spatial
resolution of the database is 0.25x0.25 degrees. It is
derived from weather station observations in combination with satellite
data for parameters like radiation.
The meteorological data is updated with a delay of about 3 months which makes
the database unsuitable for real-time monitoring, nevertheless the
POWER database is useful for many other studies.
Finally, note that any latitude/longitude within a 0.25 x 0.25 degrees grid box
will yield the same weather data, e.g. there is no difference between
latitude - longitude 5.3 - 52.1 and latitude - longitude 5.1 - 52.4.
For more information on the NASA POWER database see the documentation
at: https://power.larc.nasa.gov/

#### Input parameters

1. latitude - Latitude (float)
2. longitude - Longitude (float)
3. start_date - Starting date (datetime.date)
4. end_date - Ending date (datetime.date)
5. to_PCSE - If true the tool will write the results in a format compatible to PCSE. In other case it will write as in the dataframe
6. to_file - Save to file if true (bool) (Optional, default = False)
7. filename - Name of the new file (string) (Optional, default = meteorological_data.xls)

#### The NASAPowerMeteorologicalData attributes

1. data - All the downloaded data in pandas dataframe (pandas dataframe)
2. description - A brief description of the downloaded data
3. elevation - Elevation in meters
4. latitude - Latitude
5. longitude - Longitude
6. angstormA - Angstrom A value
7. angstormB - Angstrom B value
8. power_variables - A list with the variables to download (from NASA)

#### Installation

```bash
git clone https://github.com/alekfal/NASAMeteoDataTool.git
cd NASAMeteoDataTool/
pip3 install .
```

#### Examples

Download Meteorological data

```python
import datetime as dt
from pyNASAPower import NASAPowerMeteorologicalData

# Latitude, Longitude for Athens, Greece
latitude = 37.983810
longitude = 23.727539

# Dates for downloading meteorological data in format (y, m, d)
start_date = dt.date(2017, 1, 1)
end_date = dt.date(2017, 12, 31)

# Download data
meteo = NASAPowerMeteorologicalData(latitude, longitude, start_date, end_date, to_PCSE = False, to_file = True, filename = 'meteorological_data.xls')

# Or PCSE format
meteo = NASAPowerMeteorologicalData(latitude, longitude, start_date, end_date, to_PCSE = True, to_file = True, filename = 'PCSE_meteorological_data.xls')
```

#### Results

1. Option to_PCSE = False (meteorological_data.xls):

![meteo](https://user-images.githubusercontent.com/18232521/94548147-f70af480-0258-11eb-885d-0fab180c700b.png)


2. Option to_PCSE = True (PCSE_meteorological_data.xls):

![PCSE](https://user-images.githubusercontent.com/18232521/94549025-400f7880-025a-11eb-923f-535d27dcc4f4.png)


911 Emergency Tactical Mapping for the Future

Leverage the power of the Esri Geospatial Cloud, 9-1-1 device location from RapidSOS, traffic from Waze &amp; more. Find callers quickly. Radius automatically displays ALI/ANI location and RapidSOS location side by side, helping you determine the incident location and track callers in motion. Everything is integrated with your 9-1-1 phone system, no need to manually enter a number. Locate what you need. Radius allows you to perform searches for addresses, points of interest, and place names in addition to all common geodetic formats such as latitude/longitude/altitude, What3Words, and Google plus codes. Understand the situation at a glance. Radius also provides you with additional situational awareness tools such as real-time traffic and incident data from TomTom and Waze, as well as real-time Weather data from DarkSky. Leverage your GIS investment. Like all RapidDeploy products, Radius is powered by an NG9-1-1 GIS platform that leverages the Esri Geospatial Cloud and your own authoritative GIS data. In addition to countless base maps and feature layers, you’ll be able to easily configure custom map layers and authoritative geocoding services.<o:p></o:p>

Aerospace and Defense Libraries - Page 14

aws-tweet-crawlerby serkan-ozal

Java 4 Version:Current
License: No License (No License)

A Platform that crawls tweets on AWS

2D-Accretion-Simulationby quietsamurai98

Java 4 Version:Current
License: Permissive (MIT)

Simulation of a 2 dimensional cloud of space dust

FroggySwim-2Dby Onewayr9

C# 4 Version:Current
License: No License (No License)

First Unity Game

friction_zeroby Schwarzbaer

Python 4 Version:Current
License: No License (No License)

gpsby jonathanwoolf

Python 4 Version:Current
License: Strong Copyleft (GPL-3.0)

Python script to interact w/ NMEA 0183 compatible usb GPS receivers

Google-Earth-Engine-Forest-Fire-Supervisedby axecasper

JavaScript 4 Version:Current
License: No License (No License)

asteroids-almost-from-scratchby luxedo

JavaScript 4 Version:Current
License: Strong Copyleft (GPL-3.0)

This is an attempt of reproducing the game asteroids using modern programming languages

NASAMeteoDataToolby alekfal

Python 3 Version:Current
License: Strong Copyleft (GPL-3.0)

Download Meteorological Data from NASA POWER API (https://power.larc.nasa.gov/)

Radius Tactical Mappingby RapidDeploy

cloud_api 0 Version:Current
License: Proprietary (Proprietary)

911 Emergency Tactical Mapping for the Future

aws-tweet-crawlerby serkan-ozal

2D-Accretion-Simulationby quietsamurai98

FroggySwim-2Dby Onewayr9

friction_zeroby Schwarzbaer

gpsby jonathanwoolf

Google-Earth-Engine-Forest-Fire-Supervisedby axecasper

asteroids-almost-from-scratchby luxedo

NASAMeteoDataToolby alekfal

Radius Tactical Mappingby RapidDeploy

Open Weaver – Develop Applications Faster with Open Source

kandi

Community and Support

Company

Follow

Aerospace and Defense Libraries - Page 14

aws-tweet-crawlerby serkan-ozal

Java 4 Version:Current License: No License (No License)

A Platform that crawls tweets on AWS

2D-Accretion-Simulationby quietsamurai98

Java 4 Version:Current License: Permissive (MIT)

Simulation of a 2 dimensional cloud of space dust

FroggySwim-2Dby Onewayr9

C# 4 Version:Current License: No License (No License)

First Unity Game

friction_zeroby Schwarzbaer

Python 4 Version:Current License: No License (No License)

gpsby jonathanwoolf

Python 4 Version:Current License: Strong Copyleft (GPL-3.0)

Python script to interact w/ NMEA 0183 compatible usb GPS receivers

Google-Earth-Engine-Forest-Fire-Supervisedby axecasper

JavaScript 4 Version:Current License: No License (No License)

asteroids-almost-from-scratchby luxedo

JavaScript 4 Version:Current License: Strong Copyleft (GPL-3.0)

This is an attempt of reproducing the game asteroids using modern programming languages

NASAMeteoDataToolby alekfal

Python 3 Version:Current License: Strong Copyleft (GPL-3.0)

Download Meteorological Data from NASA POWER API (https://power.larc.nasa.gov/)

Radius Tactical Mappingby RapidDeploy

cloud_api 0 Version:Current License: Proprietary (Proprietary)

911 Emergency Tactical Mapping for the Future

aws-tweet-crawlerby serkan-ozal

2D-Accretion-Simulationby quietsamurai98

FroggySwim-2Dby Onewayr9

friction_zeroby Schwarzbaer

gpsby jonathanwoolf

Google-Earth-Engine-Forest-Fire-Supervisedby axecasper

asteroids-almost-from-scratchby luxedo

NASAMeteoDataToolby alekfal

Radius Tactical Mappingby RapidDeploy

Open Weaver – Develop Applications Faster with Open Source

kandi

Community and Support

Company

Follow

Java 4 Version:Current
License: No License (No License)

Java 4 Version:Current
License: Permissive (MIT)

C# 4 Version:Current
License: No License (No License)

Python 4 Version:Current
License: No License (No License)

Python 4 Version:Current
License: Strong Copyleft (GPL-3.0)

JavaScript 4 Version:Current
License: No License (No License)

JavaScript 4 Version:Current
License: Strong Copyleft (GPL-3.0)

Python 3 Version:Current
License: Strong Copyleft (GPL-3.0)

cloud_api 0 Version:Current
License: Proprietary (Proprietary)