Latest Contributions by MarkGuagliardo

I never got around to solving this problem. I forgot that I had posted here. I did a search and found...my own question already posted by me. And I can no longer see Bill's response, which impressed me at the time. My recent thinking has identified a problem with my first approach, then a second approach, also with a significant flaw, then a third approach, which is an elaboration of the first approach, but which I don't know how to execute. Bear with me. Let's keep it simple. Consider a scenario of two hospitals with non-overlapping service areas, and we want to discover the de facto catchment area for 90% of patient cases for each hospital. (Let's also not worry that some persons have multiple encounters.) Approach #1: Create a density raster. Draw isolines. Choose the one that encloses 90% of patients. There's your catchment area. Problem: The isoline creation process is not guided by percentage or number of total cases. It is guided by a Z value assigned to each raster cell that represents density of people in the cell's immediate surroundings. So, we can estimate the isoline for 20 patients per square mile but that does not tell us how many patients are within that isoline. Approach #2: Create drive time service areas at closely spaced time intervals around each clinic location using Network Analyst. For example, one service area polygon for every additional 2 minutes. Next perform some kind of spatial join to capture the number of patient points associated with polygon. Polygon covering 90% of patents is your catchment area. Problem: The service area polygon represents potential service, not actual patient origination points. A hospital located in the center of town might draw most of it's patients from communities lying to its north. However, the service area polygons are anchored around the hospital location. Thus to get to 90% might require a very large drive time service area that reaches far north while also covering large irrelevant areas to the south, east and west. This method is objective but not necessarily reflective of actual catchment area. Approach #3: Go back to Approach #1. Draw closely spaced isolines. Export them to a polygon feature class. For each polygon, capture the number of patients it overlays, compute the percentage and find the polygon that covers 90%. Does anyone see a problem with Approach #3? It seems tedious and could be computationally intensive if applied to 150 hospitals and 5 million patients across the country. Even it is sound logic I don't know how to do it efficiently. ... View more

Bill, As always, thanks for the very thorough and thoughtful reply. This will be invaluable guidance when we get around to addressing issues that we probably should be working on. But for the moment we have a simpler goal - to objectively define the "footprint" of each hospital. Two important points of clarification: 1. Our hospitals are spaced far enough apart that they do not compete with each other for the most part, and 2. We are not concerned (for the moment) about competition from hospitals owned by other systems. I know this is an unusual situation. We are addressing a narrow and unusual question that I can't elaborate on here. The question requires us to discover the footprint of the hospital. I have called it the catchment area. That might not be the best term for it. Thanks, Mark G. ... View more

Jay, thanks for that excellent response. We were somewhat aware of the capabilities you describe. They would be particularly helpful for spatially focused areas and specific seasonal conditions. However, our task is to produce the best estimate of "average" drive time possible between 25.5 million pairs of points across the entire 50 states. (8.5 million residences and each of three different types of care location). I know of no across the board adjustments for year-around conditions or pop. density that can or should be made to improve the estimates coming from StreetMap Premium and Network Analyst. I'm looking for validation of my assumption that there are no magical adjustments, or for information about those adjustments. ... View more