Learn how parcel data works and is counted in Anderson Optimization
Parcel Data Overview
We partner with ReportAll USA, a national parcel data provider, to make it seamless to view parcel boundaries and landowner information throughout the siting process in Anderson Optimization. ReportAll aggregates parcel and ownership information directly from each county.
As part of signing up for Anderson Optimization, we include up to 250,000 ReportAll parcels for base level accounts and 750,000 for nationwide accounts with each year's annual subscription. This allotment will reset each year on the renewal date.
If your team needs additional ReportAll parcel data above and beyond the 250,000 or 750,000 (depending on account size) parcels that come with the annual subscription each year, we can work with you to purchase additional parcel data in bulk.
When does a parcel count towards the parcel allotment?
There are two main sets of tools where users can pull in parcel data from ReportAll and parcels will 'count' towards the annual allotment of parcels.
Parcel Search Tasks - when hitting 'Run'
Parcel layer - clicking on a parcel in the layer
Read more about each of these below.
(1) Parcel Search Tasks
There are a few different versions of the parcel search task but they all follow the same process for how parcels are counted:
On the parcel search tasks, there are 2 steps to pull in parcels:
Step 1 - Get Count: This step provides a count of the number of parcels that will be pulled into a project if the user chooses to proceed. No parcels have actually been pulled in at this stage and thus no parcels have been deducted from the allotment. If the count came back too high or too low, just adjust the search parameters and hit 'Get Count' again to see the new count.
Step 2 - Run: Hitting the Run button on the parcel search pulls those parcels into the project and deducts the 'Get Count' parcel number from the company's parcel allotment.
Rerunning a parcel search in a previously searched area will double-count the parcels that have already been pulled in. Each time you run the parcel search it fetches the latest copy of the data.
Get Count vs. Run - why are the numbers different?
You may see fewer parcels actually pull into a project than what was listed in the 'Get Count' step. This can happen when we find duplicates in the ReportAlldata once we've pulled in their data; we de-dupe the parcels before displaying them on the project.
Some counties store multi-owner properties as separate parcel polygons. Given that it would be confusing to have duplicate polygons on the map, we de-dupe any of those that we see before displaying them in AO.
Re-running a search in an area will ‘re-pull’ parcels. This is because the parcel search tool is passing on the most current meta-data for a parcel and cannot check if the data has been updated without actually pulling in the data
(2) Parcel Layer
When the Parcels layer is activated on any map (Map toolbar > layers menu > Parcels Layer)
Clicking on a parcel in the layer will count as a parcel pull
Clicking on parcels you have already pulled in while this layer is up will also count as a parcel pull, as we are querying the latest parcel record from ReportAll in case there are any changes to the parcel metadata.
Methods that do not count towards the parcel usage:
Importing parcels/site boundaries from a KML/KMZ
Drawing/tracing custom parcel boundaries
Clicking on parcels that have already been saved as assets (assuming parcel layer is not enabled)
How can I tell how many parcels I've pulled?
We monitor parcel usage for all of our accounts monthly. If you're curious about where your account's parcel usage is at, feel free to reach out to the client success team and we will provide an update for you. We will typically let you know if we see any spikes in usage and can cover parcel usage on our quarterly account calls.
Where can I go to find out what parcel data is available for each county?