npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@datafire/surrey_ca_trafficloops

v4.0.0

Published

DataFire integration for City of Surrey Traffic Loop Count API.

Readme

@datafire/surrey_ca_trafficloops

Client library for City of Surrey Traffic Loop Count API.

Installation and Usage

npm install --save @datafire/surrey_ca_trafficloops
let surrey_ca_trafficloops = require('@datafire/surrey_ca_trafficloops').create();

.then(data => {
  console.log(data);
});

Description

This API provides locations of City of Surrey traffic loops and the corresponding traffic loop counts in 15 minute intervals. While the counts are broken up by 15 minute intervals, the data is currently loaded only once per day. We are hoping to increase this frequency to at least once every hour. The LOOP_ID field is common to both datasets and can be used to cross-reference them.

Actions

TrafficLoopCounts.fmw.get

Provides traffic loop counts for the input time interval. The LOOP_ID and DATETIME combinations are unique in the output. The output timestamp will contain the time zone offset, either -08 (PST) or -07 (PDT) depending on whether daylight savings time was observed at the output datetime. In order to work with local time you may omit the time zone offset from the input and truncate it from the output.

surrey_ca_trafficloops.TrafficLoopCounts.fmw.get({}, context)

Input

  • input object
    • startdatetime number: Beginning of the required date/time range in ISO 8601. For example March 24 2016 at 1:00 PM Pacific Standard Time would be 2016-03-24T13:00:00-08.
    • enddatetime number: End of the required date/time range. For details see the startdatetime parameter.

Output

Output schema unknown

TrafficLoops.fmw.get

Provides all the traffic loops maintained by the City of Surrey in GeoJSON format. LANE_DIRECTION indicates the heading of the traffic (NB, SB, EB, WB). INTERSECTION_ID corresponds to the INTID field in the intersections dataset which can be found on the Surrey Open Data site. ROAD_FACILITYID indicates which road segment the loop is located on. This corresponds to the FACILITYID in the Road Centrelines dataset on the City of Surrey Open Data site.

surrey_ca_trafficloops.TrafficLoops.fmw.get({}, context)

Input

  • input object
    • proj_epsg number: The output projection EPSG code. Eg. WGS84 is 4326 and NAD 83 UTM Zone 10 is 26910. If this is left blank, the default is 4326. For more on EPSG codes please see http://spatialreference.org/

Output

Output schema unknown

Definitions

This integration has no definitions