Repo for the IoT Hackathon

Clone this repo:


  1. dedc753 deleting test file by Rajani Gundimeda · 7 years ago master
  2. c6f7467 testing push by Rajani Gundimeda · 7 years ago
  3. 7e789e8 Fourth Commit by kdw174 · 7 years ago
  4. f5f4879 Third Commit by kdw174 · 7 years ago
  5. 4ce0f7f Fourth Commit by nimonix · 7 years ago

Traffic Seed App

Getting Started

To take advantage of Traffic Seed App you need to:

  1. Get a copy of the code.
  2. Install the dependencies if you don't already have them.
  3. Modify the application to your liking.
  4. Add UAA Support.
  5. Deploy your code to Predix, Cloud Foundry.

Browser Support

The traffic seed app is currently supported in Google Chrome 40.x.x and above.

Get the code

Get the code from the following git location: Download

Alternatively, use the git command as below:

git clone

Install dependencies

  1. Install CF CLI (Cloud Foundry Command Line Interface) from this website:
  • Go to the Downloads Section of the README on the GitHub and download the correct package or binary for your operating system.
  • Check that it is installed by typing cf on your command line.
  1. Be sure that CURL is installed on your machine
  1. Be sure to set your environment proxy variables before trying to run the script.
export ALL_PROXY=http://<proxy-host>:<proxy-port>
export http_proxy=$ALL_PROXY
export https_proxy=$ALL_PROXY

Predix Platform and Cloud Foundry

Traffic Seed App is using Predix Platform and Cloud Foundry to push the application to cloud. If you do not have account created in Predix, please click here to create one.

For more information on using Predix platform and Cloud Foundry, check this website.

Login to Cloud Foundry

Use the below command to login to Cloud Foundry:

cf login

It will prompt for the email and password. Give the email and password which you have used to create the predix account. It might ask you to select an org (if you have more than one org) then select the one showing your email. It will result as below:

cf login
API endpoint: https://<>

Email> # predix account email

Password> ****** # predix account password

Select an org (or press enter to skip):
1. intelligent_environments

Org> 2
Targeted org

Targeted space dev

API endpoint:   https://<> (API version: 2.51.0)   
Space:          dev   

Quick-install (for experienced users)

With Node.js installed, , run the following one liner from the root of your seed app download:

npm install -g gulp bower && npm install && bower install

Prerequisites (for everyone)

The full starter kit requires the following major dependencies:

  • Node.js, used to run JavaScript tools from the command line.
  • npm, the node package manager, installed with Node.js and used to install Node.js packages.
  • gulp, a Node.js-based build tool.
  • bower, a Node.js-based package manager used to install front-end packages (like Polymer).

To install dependencies:

  1. Check your Node.js version.
node --version

The version should be at or above 0.12.x.

  1. If you don't have Node.js installed, or you have a lower version, go to and click on the big green Install button.

  2. Install gulp and bower globally.

npm install -g gulp bower

This lets you run gulp and bower from the command line.

  1. Once the node, bower and gulp are installed, run the below commands to add the node_modules and bower_components dependencies.
npm install
bower install

This installs all the element sets and tools required to build and serve apps.

Development workflow

Serve / watch (Local Testing)

gulp serve

This outputs an IP address you can use to locally test and another that can be used on devices connected to your network.

Build (Create a dist version)


Build and optimize the current project, ready for deployment. This includes linting as well as image, script, stylesheet and HTML optimization and minification.

Setup services for your own development

You can setup services using below 2 ways:

  1. Auto Setup : It uses shell scripts commited in this repository. It will only set up the services used in traffic seed app.

  2. Manual : You will have to follow steps mentioned in 'Manual' section to create their own services. Useful when you want to use services other than ie-traffic service.

Auto Setup

  1. Go to TrafficSeedApp/pre-settings/scripts/, and open this file in a text editor. This file contains environment variables that are used by the application for quick setup. Services and plans are set to the default values for the Predix VPC.

Modify the following:

  • FRONT_END_APP_NAME="predix-node-js-starter-yourname"
  • CF_HOST=""
  • CF_ORG="your_org_name"
  • CF_SPACE="your_space"
  • CF_USERNAME="your_predixio_user_name"

See the comments in the file for more information.

1. By default, the Cloud Foundry Organization and the username is your email
2. By default, no proxy host:port is set
3. By default, the username used to login to the application is "hacker1"
4. By default, the password used to login to the application is "hacker1"
  1. Now you’re ready to run the scripts. cd TrafficSeedApp/pre-settings
  • Run ./scripts/ command . This script is responsible for deleting the applications and services if already present.
  • Type ./ First you will be prompted for your Cloud Foundry password(if you are not already logged in to cloud foundry). After that the script will begin setting up the various micro services, hooking them together using the parameters set in the file.
  1. Upon completion, cd TrafficSeedApp and check if your manifest.yml has been modified to have the correct environment variables.

  2. After the script is complete, run the command 'cf apps' to see the list of cloud foundry apps you have created. Within that list the app pushed by the script will have the name set in the file.

Congratulations! You have successfully created your first Predix Application! You are now a Predix Developer!


If you have used the Auto Setup steps to set up services, skip this section and continue from 'Service Reference' section.

  1. Deploy Hello World App

  2. Subscribe to UAA and IE services via Predix Catalog

  1. Bind UAA and IE services to Hello World
cf bind-service <your_app_name> <service_instance_name>
  1. Updating the OAuth2 Client to Use Your Service Instance
  • Make sure you provide the IE services oauth-scope in the scope and authorities from “step 10” when using the Predix Starter Kit to generate the client_id, client_secret and token.
  • To retrieve the oauth-scope, use this command:
cf env <your_app_name>
  • Enter the oauth-scope when generating the client token
   "client_id": "traffic_test2",
   "client_secret": "traffic2",
   "scope": [
   "authorized_grant_types": [
   "authorities": [
   "autoapprove": [
  • Now, you can start making Predix API calls using this token.
  1. You also need to create a user and associate the user to a group for login page in the Predix Starter Kit.

Update manifest.yml (required only while doing Manual setup)

You’ll need to change these fields in your manifest.yml file before pushing the application to the cloud. You can pull these field from VCAP_Services by using below command

cf env <Your-App-Name>

You’ll also need to create a client_id in the Predix Starter Kit. See step 4 in above section “Setup services for your own development”

  - name: traffic-seed-app # change this to your application name
            - your_redis_instance # change this to your redis service instance name
            - your_view_service_instance # change this to your view service instance name
      UAA_CLIENT_CREDENTIALS: "Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ=" # change it to your client_id:client_secret base 64 encoded string. Use [this]( to convert client_id:client_secret to base 64 encoded value.
      RESOURCE_URL: # change to your api resource url which can be found in Cloud Foundry marketplace
      UAA_URI: # change to your UAA uri shown in VCAP services
      UAA_CLIENT_ID: client_id # change it to your client id. See step 4 in above section “Setup services for your own development”
      PREDIX_ZONE_ID: zone_id # change to your zone id shown in VCAP services

  "ie-traffic": [
    "credentials": {
     <b>"url": "",</b>
     "zone": {
      "http-header-name": "Predix-Zone-Id",
      **"http-header-value": "334d60f8-2bdf-4b9b-a561-1b16a6f2df0e",**
      "oauth-scope": "ie-traffic.zones.334d60f8-2bdf-4b9b-a561-1b16a6f2df0e.user"
    "label": "ie-traffic",
    "name": "janine_parking",
    "plan": "Beta",
    "provider": null,
    "syslog_drain_url": null,
    "tags": []
  "predix-uaa": [
    "credentials": {
     "issuerId": "",
     **"uri": "",**
     "zone": {
      "http-header-name": "X-Identity-Zone-Id",
      "http-header-value": "a14f01fc-f50e-4db7-8bb0-bed1c887ea98"
    "label": "predix-uaa",
    "name": "janine_uaa2",
    "plan": "Tiered",
    "provider": null,
    "syslog_drain_url": null,
    "tags": []

Service Reference

Once the UAA and services setup is done, you will have to get the service reference to be used in manifest.yml.

Quick Start with Intelligent Environment (Cities and Enterprise APIs)

  1. Get List of Asset or Location using HATEOAS. For specific event-type or location-type, see Get List of Asset and Get List of Locations, respectively.

  2. Modify the query string parameters for each tile.


  • For media (images, audio, and video), subscribe to the ie-public-safety tile in the Predix Catalog.
  • Use the timestamp values in epoch format, which can be found here. Please make sure that the epoch format time includes the milliseconds as well. Example of getting timestamp in JavaScript in this format is as below:
(new Date()).getTime();

Additional information can be found in Traffic Seed App where we are using moment.js for getting the timestamp in epoch format.

  • API Responses are in HTTP and not HTTPS. When making requests, please ensure you are using HTTPS.
  "_links": {
    "assets": {
      "href": ""
    "locations": {
      "href": ""

Check nginx.conf

You need to make sure that nginx.conf (in the root folder which gets copied into dist) has references to the RESOURCE_URL and PREDIX_ZONE_ID which is whatever you specified in 'Update manifest.yml' section.

# for example,
set $user_token "";
location /services/ {
  # Code executed for all on /service
  access_by_lua_file '<%=ENV["APP_ROOT"]%>/nginx/scripts/set_access_token.lua';
  proxy_set_header Authorization $user_token;
  proxy_set_header Predix-Zone-Id <%=ENV["PREDIX_ZONE_ID"]%>; # it uses the PREDIX_ZONE_ID you have set in 'Update manifest.yml' section
  proxy_set_header accept application/hal+json;
  rewrite  /services/(.*) /$1 break;
  proxy_pass "<%=ENV["RESOURCE_URL"]%>"; # it uses the RESOURCE_URL you have set in 'Update manifest.yml' section

Deployment to Predix, Cloud Foundry

Once gulp is used to Build and optimize the current project, it becomes ready for deployment.

Please go on the below link to get detailed information about and Cloud Foundry deployment. Deployment to Predix, Cloud Foundry

Push to the cloud.

User the below cloud foundry command to push the app to cloud.

cf push

Accessing the Application

Once the cf push is successful, it will output the similar result as below:

Showing health and status for app <traffic-seed-app> in org your-organization-name / space <your-space> as

requested state: started
instances: 1/1
usage: 64M x 1 instances
last uploaded: Tue May 4 21:32:28 UTC 2016
stack: <stack name>
buildpack: <predix_openreg_buildpack>

     state     since                    cpu    memory         disk           details   
#0   running   2016-05-04 02:32:54 PM   0.0%   32.7M of 64M   137.6M of 1G     

Use the 'urls:' part from above output as the application login url by appending /login at the end. So, based on above result, the url to access application will be:

In your case it will be


It will take you to the predix login page where you have to use the user id and password created from UAA service step. Once you login, it will take you to Traffic Seed App page.

How do I use GE Current Intelligent Environments Services and APIs

For more information on usage of the Intelligent Environments Services and APIs, please visit the following urls:

  1. Intelligent Environments Overview

  2. General APIs

  3. Intelligent Cities APIs

Application Theming & Styling

Polymer 1.0 introduces a shim for CSS custom properties. We take advantage of this in app/styles/app-theme.html to provide theming for your application. You can also find our presets for Material Design breakpoints in this file.

Read more about CSS custom properties.


  1. main.css - to define styles that can be applied outside of Polymer's custom CSS properties implementation. Some of the use-cases include defining styles that you want to be applied for a splash screen, styles for your application 'shell' before it gets upgraded using Polymer or critical style blocks that you want parsed before your elements are.
  2. app-theme.html - to provide theming for your application. You can also find our presets for Material Design breakpoints in this file.
  3. shared-styles.html - to shared styles between elements and index.html.
  4. element styles only - styles specific to element. These styles should be inside the <style></style> inside template.
<dom-module id="my-list">
      :host {
        display: block;
        background-color: yellow;
      <template is="dom-repeat" items="{{items}}">
        <li><span class="paper-font-body1">{{item}}</span></li>

These style files are located in the styles folder.

Unit Testing

Web apps built with Polymer Starter Kit come configured with support for Web Component Tester - Polymer's preferred tool for authoring and running unit tests. This makes testing your element based applications a pleasant experience.

Read more about using Web Component tester.

Dependency Management

Polymer uses Bower for package management. This makes it easy to keep your elements up to date and versioned. For tooling, we use npm to manage Node.js-based dependencies.

Service Worker

Polymer Starter Kit offers an optional offline experience thanks to Service Worker and the Platinum Service Worker elements. New to Service Worker? Read the following introduction to understand how it works.

Our optional offline setup should work well for relatively simple applications. For more complex apps, we recommend learning how Service Worker works so that you can make the most of the Platinum Service Worker element abstractions.

Enable Service Worker support?

To enable Service Worker support for Polymer Starter Kit project use these 3 steps:

  1. Uncomment Service Worker code in index.html
<!-- Uncomment next block to enable Service Worker support (1/2) -->
<paper-toast id="caching-complete"
             text="Caching complete! This app will work offline.">

<platinum-sw-register auto-register
  <platinum-sw-cache default-cache-strategy="networkFirst"
  1. Uncomment Service Worker code in elements.html
<!-- Uncomment next block to enable Service Worker Support (2/2) -->
<link rel="import" href="../bower_components/platinum-sw/platinum-sw-cache.html">
<link rel="import" href="../bower_components/platinum-sw/platinum-sw-register.html">
  1. Uncomment 'cache-config' in the runSequence() section of the 'default' gulp task, like below: (gulpfile.js)
// Build Production Files, the Default Task
gulp.task('default', ['clean'], function (cb) {
    ['copy', 'styles'],
    ['jshint', 'images', 'fonts', 'html'],

Filing bugs in the right place

If you experience an issue with Service Worker support in your application, check the origin of the issue and use the appropriate issue tracker:

I get an error message about "Only secure origins are allowed"

Service Workers are only available to "secure origins" (HTTPS sites, basically) in line with a policy to prefer secure origins for powerful new features. However http://localhost is also considered a secure origin, so if you can, developing on localhost is an easy way to avoid this error. For production, your site will need to support HTTPS.

How do I debug Service Worker?

If you need to debug the event listener wire-up use chrome://serviceworker-internals.

What are those buttons on chrome://serviceworker-internals?

This page shows your registered workers and provides some basic operations.

  • Unregister: Unregisters the worker.
  • Start: Starts the worker. This would happen automatically when you navigate to a page in the worker's scope.
  • Stop: Stops the worker.
  • Sync: Dispatches a 'sync' event to the worker. If you don't handle this event, nothing will happen.
  • Push: Dispatches a 'push' event to the worker. If you don't handle this event, nothing will happen.
  • Inspect: Opens the worker in the Inspector.

Development flow

In order to guarantee that the latest version of your Service Worker script is being used, follow these instructions:

  • After you made changes to your service worker script, close all but one of the tabs pointing to your web application
  • Hit shift-reload to bypass the service worker as to ensure that the remaining tab isn't under the control of a service worker
  • Hit reload to let the newer version of the Service Worker control the page.

If you find anything to still be stale, you can also try navigating to chrome:serviceworker-internals (in Chrome), finding the relevant Service Worker entry for your application and clicking 'Unregister' before refreshing your app. This will (of course) only clear it from the local development machine. If you have already deployed to production then further work will be necessary to remove it from your user's machines.

Disable Service Worker support after you enabled it

If for any reason you need to disable Service Worker support after previously enabling it, you can remove it from your Polymer Starter Kit project using these 4 steps:

  1. Remove references to the platinum-sw elements from your application index.
  2. Remove the two Platinum Service Worker elements (platinum-sw/..) in app/elements/elements.html
  3. Remove 'precache' from the list in the 'default' gulp task (gulpfile.js)
  4. Navigate to chrome://serviceworker-internals and unregister any Service Workers registered by Polymer Starter Kit for your app just in case there's a copy of it cached.

Yeoman support

generator-polymer now includes support for Polymer Starter Kit out of the box.

Frequently Asked Questions

Where do I customise my application theme?

Theming can be achieved using CSS Custom properties via app/styles/app-theme.html. You can also use app/styles/main.css for pure CSS stylesheets (e.g for global styles), however note that Custom properties will not work there under the shim.

A Polycast is also available that walks through theming using Polymer 1.0.

Where do I configure routes in my application?

This can be done via app/elements/routing.html. We use Page.js for routing and new routes can be defined in this import. We then toggle which <iron-pages> page to display based on the selected route.

Why are we using Page.js rather than a declarative router like <more-routing>?

<more-routing> (in our opinion) is good, but lacks imperative hooks for getting full control over the routing in your application. This is one place where a pure JS router shines. We may at some point switch back to a declarative router when our hook requirements are tackled. That said, it should be trivial to switch to <more-routing> or another declarative router in your own local setup.

Where can I find the application layouts from your Google I/O 2015 talk?

App layouts live in a separate repository called app-layout-templates. You can select a template and copy over the relevant parts you would like to reuse to Polymer Starter Kit.

You will probably need to change paths to where your Iron and Paper dependencies can be found to get everything working. This can be done by adding them to the elements.html import.

Something has failed during installation. How do I fix this?

Our most commonly reported issue is around system permissions for installing Node.js dependencies. We recommend following the fixing npm permissions guide to address any messages around administrator permissions being required. If you use sudo to work around these issues, this guide may also be useful for avoiding that.

If you run into an exception that mentions five optional dependencies failing (or an EEXIST error), you may have run into an npm bug. We recommend updating to npm 2.11.0+ to work around this. You can do this by opening a Command Prompt/terminal and running npm install npm@2.11.0 -g. If you are on Windows, Node.js (and npm) may have been installed into C:\Program Files\. Updating npm by running npm install npm@2.11.0 -g will install npm into %AppData%\npm, but your system will still use the npm version. You can avoid this by deleting your older npm from C:\Program Files\nodejs as described here.

If the issue is to do with a failure somewhere else, you might find that due to a network issue a dependency failed to correctly install. We recommend running npm cache clean and deleting the node_modules directory followed by npm install to see if this corrects the problem. If not, please check the issue tracker in case there is a workaround or fix already posted.

How do I add new JavaScript files to Starter Kit so they're picked up by the build process?

At the bottom of app/index.html, you will find a build block that can be used to include additional scripts for your app. Build blocks are just normal script tags that are wrapped in a HTML comment that indicates where to concatenate and minify their final contents to.

Below, we've added in script2.js and script3.js to this block. The line <!-- build:js scripts/app.js --> specifies that these scripts will be squashed into scripts/app.js during a build.

<!-- build:js scripts/app.js -->
<script src="scripts/app.js"></script>
<script src="scripts/script2.js"></script>
<script src="scripts/script3.js"></script>
<!-- endbuild-->

If you are not using the build-blocks, but still wish for additional files (e.g scripts or stylesheets) to be included in the final dist directory, you will need to either copy these files as part of the gulpfile.js build process (see the copy task for how to automate this) or manually copy the files.

I'm finding the installation/tooling here overwhelming. What should I do?

Don't worry! We've got your covered. Polymer Starter Kit tries to offer everything you need to build and optimize your apps for production, which is why we include the tooling we do. We realise however that our tooling setup may not be for everyone.

If you find that you just want the simplest setup possible, we recommend using Polymer Starter Kit light, which is available from the Releases page. This takes next to no time to setup.


Polymer Starter Kit is a new project and is an ongoing effort by the Web Component community. We welcome your bug reports, PRs for improvements, docs and anything you think would improve the experience for other Polymer developers.