|
POST
|
Maybe I can explain it better? I have ZIP codes with known numbers of population and discharges. I want to "dub down" the discharge data to census tracts or blocks (or even arbitrary polygons such as a tessellation). Step 1 would be to ENRICH the tracts/blocks/whatever with population data. Step 2 would be to find a function that can relate the boundaries of the ZIP pop and discharges to the boundaries of the tract/block whatever by POPULATION. So, if a big ZIP had 100 discharges and 100,000 people (.001 discharges per person) and it had a tract that was half the size of the ZIP, but only had pop 100, that it would distribute only .1 discharges to the tract. Does that help? The FIND EXISTING function only uses area when "distributing" a property. Essentially, I want to ENRICH my tracts or blocks using the existing discharge data and the known populations, not areas.
... View more
07-07-2025
06:02 PM
|
0
|
0
|
299
|
|
POST
|
Yeah, you're not quite getting my problem. Trust me, there will be discharges all over a metro area no matter how far a given hospital is. The key is to distribute the known discharges in a given ZIP code down to the census tracts/blocks or even arbitrary shape by POPULATION in that block, not by AREA of that block. Again, we have areas with almost no population that are large, so using SIZE to distribute would be silly. Any other ideas?
... View more
07-07-2025
05:35 PM
|
0
|
0
|
300
|
|
POST
|
I can't crack a problem I've been working on for quite a while. I have ZIP-level data for a certain thing, let's say hospital discharges or ED visits. I want to "dub down" this ZIP-level data to tracts or blocks. This data scales better by population, not area. Summarize within only calculates by area, right? How can I do this in AGOL? As we all know, some ZIPs are very "lumpy" in where actual people live, especially out in the west where many ZIPs are mostly empty space. So tracts and blocks show were actually the people are. I want my output to be the tracts/blocks/or polygon enriched with the correct number of discharges scaled by population. Imagine we had a ZIP that was a perfect 10mi by 10mi square. 100 sq mi. 1000 pop and 1000 discharges. Imagine there's 2 blocks in there that are b2 =10mi by 7mi (70 sq mi) and b1 = 10mi by 3mi (30 sq mi). b2 has almost nobody, only 100 pop, while b1 has pop 900. I want the 1000 discharges for 1000 pop at ZIP level distributed or "enriched" to the blocks b1 and b2 by pop, resulting in b1 = 900 discharges and b2 = 1000 discharges. If I use summarize within, it goes by area, and gives all the discharges to b2 because it is bigger. How do I do this in AGOL?
... View more
07-02-2025
11:07 AM
|
0
|
3
|
398
|
|
POST
|
Do you have a reference for this in ESRI documentation? Is there a convenient variable for 18+ pop to use for enrichment? Thank You.
... View more
04-06-2025
10:25 PM
|
0
|
0
|
382
|
|
POST
|
How can I find out a few details on some ESRI demographic variables on medical insurance? E.g. is the base the ESRI 2024 population for the area of interest (just a ZIP or 2)? E.g. is the same base used for "have hmo" and "have blue cross"? or are they separate basis? Usually ESRI has the "parent" number if it is NOT the ESRI population for the area. Same question for the Medicare and Medicaid stat. MP18050a_B 2024 Personally Carry Any Medical or Hospital or Accident Insurance MP18050a_I MP18051a_B 2024 Medical Insurance Covers You Alone MP18051a_I MP18052a_B 2024 Medical Insurance Covers You and Other HH/Family Members MP18052a_I MP18053a_B 2024 Have EPO (Exclusive Provider Org) Medical Insurance MP18053a_I MP18054a_B 2024 Have HMO (Health Maintenance Org) Medical Insurance MP18054a_I MP18055a_B 2024 Have POS (Point-of-Service) Medical Insurance MP18055a_I MP18056a_B 2024 Have PPO (Preferred Provider Org) Medical Insurance MP18056a_I MP18079a_B 2024 Have AARP Medical Insurance MP18079a_I MP18057a_B 2024 Have Aetna Medical Insurance MP18057a_I MP18058a_B 2024 Have BlueCross or BlueShield Medical Insurance MP18058a_I MP18059a_B 2024 Have Cigna Medical Insurance MP18059a_I MP18060a_B 2024 Have Humana Medical Insurance MP18060a_I MP18062a_B 2024 Have United Healthcare Medical Insurance MP18062a_I MP18085a_B 2024 Obtained Medical Insurance Through Agent Representing One Company MP18085a_I MP18081a_B 2024 Obtained Medical Insurance Through Government Exchange MP18081a_I MP18084a_B 2024 Obtained Medical Insurance Through Other Government Source MP18084a_I MP18089a_B 2024 Obtained Medical Insurance Through Internet MP18089a_I MP18063a_B 2024 Obtained Medical Insurance Through Place of Work MP18063a_I MP18064a_B 2024 Obtained Medical Insurance Through Union MP18064a_I MP18065a_B 2024 Have Medicaid Medical Policy MP18065a_I MP18066a_B 2024 Have Medicare Medical Policy MP18066a_I
... View more
04-03-2025
05:44 PM
|
0
|
2
|
448
|
|
POST
|
What is the workflow for traffic counts now? The old layer is deprecated. I read this article: https://doc.arcgis.com/en/esri-demographics/latest/regional-data/traffic-counts.htm It seems there is a pre-built map, but it is not convenient. The article mentions a way to do it in AGOL with enrichment, but I can't seem to find any of the variables when searching? What is up?
... View more
02-25-2025
10:05 AM
|
0
|
0
|
276
|
|
POST
|
It's so annoying. Why did they do this? It seems to infect layers in "Old Map Viewer" too?
... View more
12-17-2024
01:59 PM
|
0
|
0
|
170
|
|
POST
|
I thought there was a way to use the aggregate function to count things accross multiple point layers? I have point layers a,b, and c. I want to aggregate to some polygon P and get statistics from all three point layers. How do I do this?
... View more
09-16-2024
06:12 PM
|
0
|
0
|
362
|
|
POST
|
yeah, it's been around for a while, and is scheduled for a fix. 1. user uploads table from xlsx file, creates hosted layer. 2. everything works fine! puts it in maps, styles it, etc. 3. does not use layer for a few days. user goes into map and does some calculation like count points, doesn't work, get's error message "no extent" or something. user can still style the layer in that map. but cannot open the layer via content or "description" options. it's like a zombie. 4. user waits a week or so...layer cures itself! Sadly, what you end up doing is exporting it as a FGDB, then loading it from that is an instant cure. I've had to do that 3 times now when there was work that HAD to be done due to deadline. Tech support says don't use xlsx, use csv, but that is a crazy extra step to get into...and I'm not sure the behaviour is that different. Very frustrating!
... View more
07-18-2024
02:35 PM
|
0
|
0
|
1294
|
|
POST
|
Thanks! It's all point features for now, but very good considerations. Plus, there's some dodging of the continual, notorious xlsx upload bug.
... View more
07-18-2024
10:26 AM
|
0
|
2
|
1324
|
|
POST
|
I ended up doing the files by region, I could always join them later. But, so far, no problem in New Map Viewer doing styling or calculations. My recollection is that the math will always be done correctly in the cloud, but the web may not be able to show things correctly sometimes.
... View more
07-18-2024
10:25 AM
|
0
|
0
|
1324
|
|
POST
|
I'm going to upload about 500k point features to AGOL. Is it best to leave it in one file? Or is it best to make 3 or 4 chunks based on what part of town (or something) to keep the table sizes down? Does it matter? One file is easier, for sure, and makes some later calculations easier. But if there were a good reason to break it up, I'd do it. Anybody know? Got some experience or an opinion? Thanks!
... View more
07-11-2024
10:28 AM
|
0
|
6
|
1445
|
|
POST
|
Layers are still up...were documented in support case.
... View more
06-10-2024
07:50 PM
|
0
|
0
|
1125
|
|
POST
|
It was the same bug as a few years ago. If you make the layer from an Excel sheet, it doesn't work. Sometimes it cures itself if you let it sit for a week or so. The "fix" is to export as FGDB, download, then re-upload. It was documented by ESRI support from this incident again. I got the impression it was well known.
... View more
06-10-2024
07:47 PM
|
0
|
0
|
1125
|
|
POST
|
Did a support case. It turns out its another instance of the "zombie layer from Excel" bug. Was able to fix it downloading part of the data as FGDB, then appending it on the original. Very nice trick! Sadly, then needed to do some work with this layer using "aggregate points" and it failed with same generic "ERROR". Did the trick to the whole thing, export as FGDB, download, re-upload from FGDB, and then it works now. Layer made from Excel get goofed up by the system! This is an old bug! I and others have written many messages about this over the last 2 years! Usually the other part is the layer can't be edited...but then if left alone for a week or so, it fixes itself. FIX IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
... View more
06-04-2024
05:26 PM
|
0
|
3
|
1200
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-08-2024 01:26 PM | |
| 1 | 02-08-2024 02:51 PM | |
| 1 | 02-06-2024 10:09 AM | |
| 1 | 04-24-2024 12:13 PM | |
| 1 | 02-08-2024 11:33 AM |
| Online Status |
Offline
|
| Date Last Visited |
07-07-2025
05:52 PM
|