ICM Structure For Creating And Maintaining Property Database

I'm bringing this subject to the entire community that started from a different post in the comments.

I'm building a property database that will include every parcel in the US. There are currently 119,746,668 parcels in 1855 counties and 48 states in the db. There are 3143 counties in the US as of the 2020 Census. The database is currently 567.21GB. It has taken my more than 6 months to get to this point.

I would like to create an ICM folder structure that can ingest the remaining 1288 counties to reduce time and token cost. It won't change the growth of bloat to the db, but that's OK, I'm no where near the db limit.

I already have a good idea of how to update the database after all 3143 counties have been ingested by having a controlling markdown that send the request to a state markdown. The state markdown will then take the request for the county and send that request to the county markdown where the instructions for the update will be held. The largest number of counties in a single state is in TX at 253 counties.

I have already created a spreadsheet that lists all 3143 counties and gets updated with successful ingests to the db with the correct url endpoint, script, and instructions on how the the ingest for that county works.

My challenge remaining, because every remaining county has a different way to find the endpoint and the data they allow exported, is unique to each county,. How do I create an ICM folder structure to complete the remaining ingests?

Thank you for your help in advance!

David Monroe, CCIM

Founder/Investor/Broker/AI Consultant/CCIM Instructor

0 comments

ICM Structure For Creating And Maintaining Property Database