So do stimulus, it only will effect short term ease and increase the #'s of everything, and will return back to same place but worse each iteration of stimulus because of the siphon at top. 

For km use 6372.8 kmdLat = radians(lat2 - lat1) dLon = radians(lon2 - lon1) lat1 = radians(lat1) lat2 = radians(lat2) a = sin(dLat/2)**2 + cos(lat1)*cos(lat2)*sin(dLon/2)**2 c = 2*asin(sqrt(a)) return(R * c)This returns the distance in miles, and when iteratively applied to a db of transactions, yields your distance-filtered comps

I believe that may have been the case in a prior iteration of the exclusion... back in the mid 90s.

@Joe Gore I think you either missed my point or just chose to ignore it. 

Have 3-4 iterations ready to roll.

Additionally, understanding and navigating market challenges is a key part of my role, which involves staying agile and adapting strategies in response to market fluctuations, thus maximizing investment value.

Basically, if you get a really big take off that is multi-stage, data management becomes really hard in Square... so I end up doing multiple iterations of the same job, one for trim, doors, and windows, another for lumber, another for siding, etc. 

As long as you can screen those types and keep yourself informed and agile, you will be ok. 

@Lance JohnsonYou could reverse engineer the county assessor site API (through inspecting network traffic), then iterate through all possible parcel numbers, storing the results and their data in a database.

It's well put together in the newer iteration.