By Sahana Murthy
on February 22, 2021
This February, we have a big update for you!
Announcing the launch of our nationwide standardized land-use codes as a premium feature in our product suite!
That’s right, in addition to high quality, standardized nationwide parcel data, we have put together highly contextual, standardized nationwide land use codes as part of our premium data package. These codes will help you get the nuanced context on land use for your projects.
From community and urban planning, to site selection, to understanding what activity is allowed on a particular piece of land, and to commercial real estate, the use cases are endless & Landgrid’s standardized use codes have you covered.
Data driven decisions and faster time to market for your projects!
Email us if you are interested in getting these codes as part of your data.
What do we mean by land-use codes, you ask???
We offer standardized land use information for 5 dimensions:
- describes the actual activity & use of the property.
- describes the broader economic or social use of the parcel.
- describes the type of structure & building on the parcel.
- describes the physical characteristics of a site or land.
- mainly describes if it's publicly or privately owned land.
You can find the descriptions of each one of our land use codes across all 5 dimensions here
Why is this valuable?
There isn’t any one universal format for standardized land use codes. Because this data varies by the county, Landgrid’s nationwide standardized classification becomes a one stop-solution that makes it easy for anyone who works with our parcel data to make use of nuanced contextual land use information.
As a result, our parcel data is your one turn-key solution for all of your contextual property data needs.
How to get it?
All of our new customers can get our standardized land use code attributes as part of our premium data package along with our other premium derivative fields.
Premium fields include:
We have spent over a year working on improving our process to populate land use codes into our dataset.
Our current data & platform customers - you may have noticed the LBCS (Land based classification system) related columns in your dataset. As we populated this data, we made them available to our existing standard data customers, along with our Landgrid Pro, Team & Enterprise customers.
We've made sure that you will continue to get the LBCS columns as part of your current accounts & subscriptions with us and as long as you are a customer with us. Please don't hesitate to reach out to us if you have any questions.
All new data customers will be able to get the land use codes as part of our premium offering.
That was our February update. Please email us at firstname.lastname@example.org if you are interested in our land use codes and we will get you a sample today.
Until next time, stay safe & warm.
By Ray Visser
on February 19, 2021
The parcel data made available by counties across the US varies widely in how land use is classified (if that information is available at all). Our standardized land use codes describe each parcel across five dimensions (Activity, Function, Structure, Site, and Ownership). These codes are 4-digit numbers, with the first digit denoting the broadest category, and each successive digit describing the parcel in more detail. For example, in the Activity dimension:
An Activity code of 3000 means 'Industrial, manufacturing, and waste-related activities'.
An Activity code of 3100 has one more digit of detail--it still falls under the above description, but it refers to 'Plant, factory, or heavy goods storage or handling activities'.
An Activity code of 3120 means 'Primarily goods storage or handling activities'--still industrial in nature, and related to plant, factory, or heavy goods storage or handling, but much more specific!
In the image below, where codes are indented to show their hierarchy, you can see how an Activity code of 3120 is just one of several different codes (e.g. 3110, 3120, 3210, 3220, 3230) at the same level of specificity (three digits):
When you expand this potential for specificity across five dimensions, each intended to describe an aspect of the land use for a particular parcel, you can see how useful Loveland's standardized land use codes can be to identify land used for general or specific purposes.
Our standardized land use codes are derived from the Land-Based Classification System (LBCS), a method devised by the American Planning Association. Activity describes the actual human activities that take place on the parcel, while Function describes the broader economic or social use the parcel serves. Structure and Site describe the type of structure on a parcel and, independently, whether the parcel is developed or not. Ownership describes whether the owner of the parcel is a public or private entity.
The five-dimension approach gives a sense of what is actually there for any given parcel, and we fill as many of the five dimensions as we can when we apply our standardized land use codes. This work is done manually, county by county, matching each place's assessor-provided land use information (where available) to the applicable codes for each dimension. For example, a parcel that is used as a parking lot for a public school would be encoded like this using our system:
Activity: 5210 (Vehicular parking, storage, etc.)
Function: 6100 (Educational services)
Structure: 5200 (Automobile parking facilities)
Site: 5300 (Developed site with roads, train tracks, and other linear structures)
Ownership: 6100 (Nonprofit educational)
Whereas, in a traditional single-dimension system, a choice would have to be made between classifying that same school parking lot as simply "parking" or "educational", or possibly even just "public property".
Currently, in the top 50 metro areas in the country, over 80% of parcels have codes for Activity and Function, and over 60% have codes for Structure and Site. In Loveland's entire nationwide dataset of more than 147 million parcels, two-thirds of all parcels have a standardized land use code for Activity and Function. We continually add new places and fill in codes for existing ones. You can stay up to date on which places have standardized land use codes using our coverage report.
In addition to the standardized land use codes, our data also includes human-readable '_description' fields for each dimension. To use the same example from earlier, an 'lbcs_activity' value of 3120 would have an 'lbcs_activity_description' value of 'Primarily goods storage or handling'. We keep the standardized land use codes and text descriptions separate to allow for easier processing and sorting of our data.
Users of Loveland's data and the mapping platform can perform queries to find patterns across the dataset, or to count certain types of parcels. Our Border Parcels project shows how our standardized land use codes can be used to generate insights into how land is used across areas of interest that span multiple states and counties, each of which provided entirely separate and incompatible land use data.
Likewise, finding and mapping all the residential parcels in a city could help with understanding and tracking the spread of disease outbreaks like the current COVID-19 pandemic. If you are a local government or a fellow mapping and data company that could use parcel data to push forward your study, outreach efforts and research on COVID-19, or if you have questions about LBCS in general, please contact us at email@example.com, or check out the parcel data FAQ.
Loveland Data Team
By Sahana Murthy
on February 9, 2021
Dear Friends of Loveland Parcel Data and landgrid.com,
A summary of updates in January of 2021 and the upcoming pipeline is below.
Key Data Stats:
- Average parcel age - 198 days, down from 205 last month.
- Average county age - 275 days, down from 277 last month.
- Added 34,000 parcels and refreshed 252 counties since last month.
USPS Vacancy, Residential indicators: Now updated monthly. Updated in January 2021, next update in February.
Coverage Report: Updated for this month and available here:
For all full dataset customers, the updated data is available for download to bulk data clients in these formats: GeoPKG .gpkg (suggested), GeoJSON, Shapefile, and Postgres SQL files. In addition, this data has been updated on the landgrid.com website.
If your organization uses a custom export we are updating your data at the moment and if you don’t see the latest updates, please drop us a line.
A Data Dictionary for the Loveland Standard Schema is always available here:
A machine-readable version of this list is included in the `verse` table available in all the formats above as well as CSV format for use in spreadsheets. To find the latest updates in verse, sort by 'last_refresh' and use the 'filename_stem' column to identify the file.
Data refreshed or added from the county in January and live now:
( Asterisk * indicates newly added county)
Arizona - Maricopa
Colorado - Costilla
Illinois - Cook
Mississippi - Clay, Warren
North Carolina - Alamance, Alexander, Alleghany, Anson, Ashe, Avery, Beaufort, Bertie, Bladen, Brunswick, Buncombe, Burke, Cabarrus, Caldwell, Camden, Carteret, Caswell, Catawba, Chatham, Cherokee, Chowan, Clay, Cleveland, Columbus, Craven, Cumberland, Currituck, Dare, Davidson, Davie, Duplin, Durham, Edgecombe, Forsyth, Franklin, Gaston, Gates, Graham, Granville, Greene, Guilford, Halifax, Harnett, Haywood, Henderson, Hertford, Hoke, Hyde, Iredell, Jackson, Johnston, Jones, Lee, Lenoir, Lincoln, Macon, Madison, Martin, McDowell, Mecklenburg, Mitchell, Montgomery, Moore, Nash, New Hanover, Northampton, Onslow, Orange, Pamlico, Pasquotank, Pender, Perquimans, Person, Pitt, Polk, Randolph, Richmond, Robeson, Rockingham, Rowan, Rutherford, Sampson, Scotland, Stanly, Stokes, Surry, Swain, Transylvania, Tyrrell, Union, Vance, Wake, Warren, Washington, Watauga, Wayne, Wilkes, Wilson, Yadkin, Yancey
Nevada - Clark
Oregon - Baker, Clackamas, Clatsop, Columbia, Coos, Crook, Curry, Deschutes, Douglas, Gilliam, Grant, Harney, Hood River, Jackson, Jefferson, Josephine, Klamath, Lake, Lane, Lincoln, Linn, Malheur, Marion, Multnomah, Polk, Tillamook, Wasco, Wheeler, Yamhill
Texas - Hamilton
Washington - Adams, Asotin, Benton, Chelan, Clallam, Clark, Columbia, Cowlitz, Douglas, Ferry, Franklin, Garfield, Grant, Grays Harbor, Island, Jefferson, King, Kitsap, Kittitas, Klickitat, Lewis, Lincoln, Mason, Okanogan, Pacific, Pend Oreille, Pierce, San Juan, Skagit, Skamania, Snohomish, Spokane, Stevens, Thurston, Wahkiakum, Walla Walla, Whatcom, Yakima
Wisconsin - Milwaukee
West Virginia - Barbour, Berkeley, Boone, Braxton, Brooke, Cabell, Calhoun, Clay, Doddridge, Fayette, Gilmer, Grant, Greenbrier, Hampshire, Hancock, Hardy, Harrison, Jackson, Jefferson, Kanawha, Lewis, Lincoln, Logan, Marion, Marshall, Mason, McDowell, Mercer, Mineral, Mingo, Monongalia, Monroe, Morgan, Nicholas, Ohio, Pendleton, Pleasants, Pocahontas, Preston, Putnam, Raleigh, Randolph, Ritchie, Roane, Summers, Taylor, Tucker, Tyler, Upshur, Wayne, Webster, Wetzel, Wirt, Wood, Wyoming
Wyoming - Albany, Big Horn, Campbell, Carbon, Converse, Crook, Fremont, Goshen, Hot Springs, Johnson, Laramie, Lincoln, Natrona, Niobrara, Park, Platte, Sheridan, Sublette, Sweetwater, Teton, Uinta, Washakie, Weston
In the current pipeline for updating in February 2021
In the pipeline for updating in March 2021
Based on feedback and county challenges, pipeline planning is always subject to change. As always, please contact us if you have any questions about accessing or using the data, you find issues with any of our data, or you have any comments or questions about our data in specific areas or states. We also love to hear from you about which counties or regions you’d like to see us update next, as it helps inform our planning process.
Thank you for being a part of Loveland!
Loveland Data Team