POST
|
I have 9 GB of tpk files that I am side loading to a variety of devices for use in Survey. All of them are larger than 400MB. They are working across different mobile devices, the only limitation being your devices available memory to store them, not a Survey limitation.
... View more
05-10-2018
10:37 AM
|
0
|
0
|
17
|
IDEA
|
Thanks! What I found was it wasn't even 'Unknown' It was completely blank, and the expanders under it were gone. Too bad I didn't screengrab it.
... View more
04-16-2018
08:27 AM
|
0
|
0
|
10
|
POST
|
It would be very nice if this list updated with the form's list.
... View more
11-15-2018
09:13 PM
|
0
|
0
|
12
|
POST
|
Thank you for your help. My level of code is basic, so I’m not sure what to do with this. Re: Attatched Code I used this code with no issues, maybe it will help folks on this thread. I added the source at the top of the code. Michelle Williams Geospatial Technical Specialist Geospatial Analysis | Real Properties | Transmission & Distribution PAX 63217 | (909) 274-3217 M. 951-538-3735 | E: michelle.williams@sce.com<mailto:michelle.williams@sce.com> 2 Innovation Way, 2nd Floor, Pomona, CA 91768 P Please consider the environment before printing this email.
... View more
08-02-2019
01:24 PM
|
0
|
0
|
143
|
POST
|
If you have lines, the labels defined for the lines will follow the rotation of the lines: Currently it would require quite some coding to determine the angle of the line. Although with the AGOL update of December 6th geometry functions where added to Arcade, these do not include functions to extract the angle of a portion of the line. See: Geometry Functions | ArcGIS for Developers Which part of the line would you use to determine the angle anyway? The default labeling applied by ArcGIS Online, implement complex things like conflict handling. You will not be able to determine which part of the line will be used to place the label and calculate the angle. Can you explain a little more why the default labeling of ArcGIS Online does not yield to required result?
... View more
12-17-2017
11:39 AM
|
1
|
0
|
9
|
POST
|
I see. So we could just create a generic level 1, e.g. 'routing_services' account and let the apps use that then?
... View more
11-28-2017
06:13 AM
|
0
|
0
|
0
|
POST
|
"Limiting the max record count to 2000 records does no prevent more than a total of 2000 records from being requested from the service, but does keep requests more concise for server performance. Check out this blog for more details on how ArcGIS Online makes requests to the data." Yes, that is correct, but....If you run your query, you click on those dot thingies, and export to .csv, it will only export 2,000 records. To get all the records, you have to scroll, scroll, scroll and scroll down, down, down, right to the end of all the records that appear in the search pane, then export. This isn't obvious, and this is what I'm saying. I thought there was a problem with the map, and kept refreshing/adding layers/removing layers/rebuilding it to see if it would bring up all records for export. I spent a lot of time troubleshooting why it would only bring up 2,000 records for export, even after I had increased the MaxRecordsCount to 20,000, and it was saying in small print '10,756 records found' (Hmmm, okay, so it has 'found' 10,756 records, so it knows that they're there, MaxRecordsCount = 20,000, correct layer is being queried, but why is it exporting only 2,000 to .csv?) It was purely by accident that I happened to start scrolling deep down through the records that more of them started magically appearing when I exported (Again I thought this was a problem with the map, or the way the all browsers were rendering things). If you don't scroll all the way down, you'll only get a few thousand extra, so you have to be careful and check the .csv against the no. of records found to make sure you're got them all. If the user sees that it has found 10,756 records, then it should grab all of them for export. There should be no scrolling required. The exact same problem applies to saving features to My Content. Moreover, this isn't a complicated query, it just runs a single query against a single Yes/No field in a table containing about 15 fields. Again, performance wise, this is where we have found that Firefox and Chrome stand out way above IE and Edge because these last two browsers get completely bogged down and stopped responding trying to scroll down through the (tiled service) records.
... View more
11-28-2017
12:36 PM
|
0
|
0
|
17
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|