nitzel / cellularcoverage Goto Github PK

implement /api/addmeasurement as described in the wiki

• area as rectangle
• area as polygon if supported by PostGIS

• Login/Logout button
• Login functional
  • creation of user in table users
• Logout functional

• ...

Implement /api/average as described in the wiki

When clicking on the maps you can perform a GetFeatureRequest to find out more about the object you just clicked.

• CORS enabled on Geoserver #15
• Sending the request onClick
• Displaying the data
  • do it pretty

As a logged-in-user you shall be able to view your submitted measurements.

On submission of a measurement by a logged-in-user save the relation between measurement id and user id in table measurement2user

• Speedtest working
• Geolocation working
• Upload data to the database
  • Security/Validity checks (server-side)

implement /api/addmeasurement

Since we have no use for it, is there a way to make rails omit the updated_at column in the measurements table?

• create the website
• submit link to the prof

• Step1
• Step2

When sending the request for the initial token to Twitters API according to the instructions given by Twitter Sign-In dev docs, with help of oauth, omniauth and omniauth-twitter gems, we get a 401 Unauthorized with the following header:

{
    "cache-control" : [
        "no-cache, no-store, must-revalidate, pre-check=0, post-check=0"
    ],"connection":[
        "close"
    ],
    "content-disposition":[
        "attachment; filename=json.json"
    ],
    "content-length":[
        "89"
    ],
    "content-type":[
        "application/json; charset=utf-8"
    ],
    "date":[
        "Wed, 09 Dec 2015 14:06:22 GMT"
    ],
    "expires":[
        "Tue, 31 Mar 1981 05:00:00 GMT"
    ],
    "last-modified":[
        "Wed, 09 Dec 2015 14:06:22 GMT"
    ],
    "pragma":[
        "no-cache"
    ],
    "server":[
        "tsa_b"
    ],
    "set-cookie":[
        "guest_id=v1%3A144966998241171180; Domain=.twitter.com; Path=/; Expires=Fri, 08-Dec-2017 14:06:22 UTC"
    ],
    "status":[
        "401 Unauthorized"
    ],
    "strict-transport-security":[
        "max-age=631138519"
    ],
    "www-authenticate":[
        "OAuth realm=\"https://api.twitter.com\""
    ],
    "x-connection-hash":[
        "abe5ee55f325a37df9b6737ed850e36a"
    ],
    "x-content-type-options":[
        "nosniff"
    ],
    "x-frame-options":["SAMEORIGIN"],
    "x-response-time":["8"],
    "x-transaction":["7ecc34ff643e2eb4"],
    "x-twitter-response-tags":["BouncerCompliant"],
    "x-xss-protection":["1; mode=block"]
}

If users or measurements can be deleted, also delete the entry in user2measurement (keywords FOREIGN KEYS & CASCADE?)

If not, just close this issue.

• Generate model for User (take a look at df80e01)
• Create controller for User

Allowing Cross-Origin-Resource-Sharing is necessary for

• using the Geoserver GetFeatureRequest
  • CORS on the Geoserver
• allowing access to the API to others
  • CORS on the main server

Access the view welcome#index from another url than "/" results in the map not loading.
For example accessing it from "/welcome/index" if route "get 'welcome/index' => 'welcome#index'" exists.

• Set up the 3 databases and their tables as described in the wiki
• add config/database.yml to .gitignore
• configure it differently for all 3 subdomains
• Set up Geoserver layers and stores for each db