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 🙏

© 2024 – Pkg Stats / Ryan Hefner

address-geoservices

v0.0.6

Published

Interacts with geoservices apis to help with managing addresses

Downloads

3

Readme

#address-geoservices

A collection of wrappers around tools that help you normalize and verify physical addresses.

###Installation

npm install --save address-geoservices

##Usage

There are two separate services provided by address-geoservices - normalization and correction.

###The address object:

Both normalize and validate expect to be called with two parameters: an address object with the following properties:

{
  street: '',
  city: '',
  state: '',
  zip: ''
}

and a callback. The callback will be called with two parameters: err (if an error occurred, null otherwise) and an object with the results of the API call.

####Normalization

Normalization is the process of converting the parts of an address to standard abbreviations (road and Rd to rd., for instance). It is useful to conform to USPS standards as well as effectively detecting duplicates in one's data corpus.

address-geoservices uses the Texas A&M Geoservices API to normalize addresses. This requires an API keyy. The .initTex function allows you to provide both a key and the desired version. Version is optional, and will default to 4.01 if not provided.

var geoservices = require('address-geoservices');

geoservices.initTex('myApiKey', 'desiredAPIVersion');

Once you've called initTex, you can use .normalize to normalize a given address.

geoservices.normalize({
  street: '2301 Westside Drive',
  city: 'Rochester',
  state: 'New York',
  zip: '14624'
}, function(err, address) {
  if (err) { console.error(err); }

  console.log(addresses);
});

####Validation

On the other hand, addresses can be mistyped. address-geoservices provides a service to do this as well, using the YAddress API. YAddress has a similar way:

var geoservices = require('address-geoservices');

geoservices.initYaddress('myApiKey');

Once initalized, validate can be used as such:

geoservices.validate({
  street: '2301 Westside Drive',
  city: 'Rochester',
  state: 'New York',
  zip: '14624'
}, function(err, address) {
  if (err) { console.error(err); }

  console.log(addresses);
});