New 42-day free trial
Smarty

Can you trust crowd-sourced address data?

Pros and Cons of Open Source and Crowd-Sourced Data
Andrew Townsend
Andrew Townsend
 • 
August 24, 2023
Tags

Crowd-source data is a term that has gained significant traction in recent years. In a recent webinar, we brought in our own Adam Charlton to talk about what can and can’t be trusted when using Open Source or Crowd-Sourced address data.

Defining crowd-source data

At the outset, it's imperative to understand what we mean by crowd-source data. It essentially refers to data that is both gathered and curated by individuals. The distinguishing feature here is that the data's curation process isn't dictated by a centralized authority or stringent verification system but by the same community that's gathering and supplying the data. If you're familiar with Wikipedia, that's a practical example of this model in action. For a more industry-centric illustration, consider OpenStreetMaps, an exemplar of crowd-source data in the addressing world. 

The good

Local regionalization

One of the standout advantages of crowd-source data is its ability to reflect local nuances. Whether it's New York, New Orleans, Hawaii, or Los Angeles, addresses are influenced by the local culture, traditions, and customs. OpenStreetMaps is a testament to this, capturing the authentic flavor of addresses in places like Utah, where traditional suffixes like 'street' or 'road' aren't commonly used. 

Global scope

Beyond the US, crowd-source data projects a global narrative, capturing information from every corner of the globe - be it London, Canada, or Australia. 

Community engagement

Perhaps the biggest boon of crowd-source data is the community that backs it. These passionate individuals not only provide the data but also assist others in making the most of it. 

Cost-effectiveness

A significant upside is the affordability factor. Most crowd-source data is available at minimal to no cost. 

Swift updates

Another upside is the rapid update cycle. For instance, a new building's address might find its way onto OpenStreetMaps before it's officially registered by the government.

Lesser vandalism concerns

Compared to larger platforms like Wikipedia, platforms like OpenStreetMaps experience lower levels of sabotage or vandalism. While not entirely immune, the threat is considerably reduced.

The not-so-good

Quality consistency

The flip side of local regionalization is the lack of standardization. Without centralized standards, data can vary widely, even within the same vicinity.

Genuine errors

While vandalism might not be a significant concern, genuine mistakes do creep in. For instance, mistakes in designating one-way roads can have real-world implications.

Incomplete data

The voluntary nature of data input means there can be considerable gaps. Some areas might be densely populated with information, while others are glaringly empty.

The balancing act

 

Crowd-source data presents an intricate balancing act. While the benefits are clear, they are intrinsically tied to the drawbacks. Excellent localization comes at the price of inconsistent standardization. Swift updates might mean lesser verification. And while you might get high-quality data, the coverage could be inconsistent.

 

Want to learn more about what Adam covered in this webinar? You can view the recording right here:

Pros and Cons of Open Source and Crowd-Sourced Data

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?