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
|
113
|
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
|
327
|
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
|
357
|
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
|
357
|
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
|
478
|
POST
|
Layers are still up...were documented in support case.
... View more
06-10-2024
07:50 PM
|
0
|
0
|
352
|
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
|
352
|
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
|
427
|
POST
|
I'm just merging 2 layers...one is just additional data that needs to be added to the original due to me forgetting it. I go into merge dialog. I select "orig" layer. I select "fix" layer. They already have same headers. I give it some name "merge layer" and hit go. It starts to churn, but then puts up a dialog with on the word "Error". This literally should be the easiest merge, it's just like the example. What is going on?
... View more
06-04-2024
11:35 AM
|
0
|
4
|
497
|
POST
|
Thanks. I checked the costs, and they're basically the same as ESRI, but with more data prep. I'm a bit shocked there wasn't a cheaper solution anywhere that was attractive.
... View more
06-03-2024
08:53 AM
|
0
|
0
|
353
|
POST
|
Oh yeah? What's the URL? Must be this one? https://help.bdc.fcc.gov/hc/en-us/articles/5341095744283-How-to-Use-the-Census-Geocoder Thanks! Makes me think googling around a bit might turn something up...
... View more
05-29-2024
03:17 PM
|
0
|
0
|
416
|
POST
|
I have to geocode about 500k addresses (all in AZ USA). That should be around 20k credits. Which is about $2400 worth of credits. I thought there used to be an ESRI "bulk geocoding" service that was cheaper or something? Is there a cheaper way to do this? That's a year's worth of AGOL subscription in credits alone...there must be a cheaper way?
... View more
05-28-2024
03:41 PM
|
0
|
4
|
507
|
POST
|
We're a SAAS-only client, so no Pro to use. (I guess maybe we'll get into Pro when they begin the new licensing structure? It sure would solve a lot of problems.)
... View more
04-25-2024
04:54 PM
|
0
|
0
|
357
|
POST
|
Typical. But I wonder what an ideal workflow would be like?
... View more
04-25-2024
01:06 PM
|
0
|
2
|
373
|
POST
|
I have a question about creating a new hosted feature layer from and old one, "cloning" it, essentially via the create item dialog. It works, it's great, but I don't get exactly why it names things and has a subsidiary item in it that is the old name? 1. I go to "new item" select "feature layer". 2. select "select an existing feature layer" 3. select "old layer" 4. go thru the options, get to the "new item" dialog where you name it and save it. 5. success! But if you open the "new layer" made from "old layer", it holds a layer item named "old layer" of type "point layer" still? why? why is the old name kept? what is best practice at this point? I usually rename it to "new layer" to avoid later confusion. Why does this sub-item exist? Why doesn't it get named appropriately automatically? What is best practice for doing this workflow?
... View more
04-24-2024
12:13 PM
|
1
|
4
|
470
|
Title | Kudos | Posted |
---|---|---|
1 | 04-24-2024 12:13 PM | |
1 | 02-08-2024 11:33 AM | |
1 | 02-08-2024 11:30 AM | |
1 | 02-08-2024 11:26 AM | |
2 | 02-07-2024 03:40 PM |
Online Status |
Offline
|
Date Last Visited |
09-19-2024
04:30 PM
|