POST
|
So, now throw in Survey123 Desktop vs. Survey123 web vs. Experience Builder vs. Solutions. Can't all this be packaged into one? Esri, your coders must be loving this?
... View more
10-13-2020
09:57 AM
|
0
|
0
|
620
|
IDEA
|
@Kory, this is still not implemented in 2.5.0. Is there any process to escalate this issue ?? It's a much needed change with a vertical bar between the others. Thank you for looking into it.
... View more
04-17-2020
06:22 AM
|
0
|
0
|
67
|
POST
|
AGP still does not show margins in 2.5.0. @KoryKramer: is this still being reported as a bug?
... View more
02-07-2020
01:57 PM
|
0
|
5
|
117
|
POST
|
Sharon Dutton, where do you see the "I want to..." in AGOL? Screenshot would help too?
... View more
10-31-2019
06:45 AM
|
0
|
2
|
780
|
POST
|
We have a feature layer in Portal map that I want to auto-populate a field. Using utility type (W for water and S for sewer) with the ObjectID to calculate the field name PipeLocationID, so the result would look like "W-123". This is the arcade exp for a custom field for the pop-up in the map: return Left($feature.PipeAssetType, 1) + "-" + $feature.OBJECTID where PipeAssetType = "Water" or "Sewer" in a pick list. My goal is to have no typing for the field crews collecting the data with iPads, so we would like to have a unique ID auto-populated. I previously set this up with an attribute rule in Pro (with some hiccups), but was thinking there may be a better way using a custom expression in Portal. Any ideas if this can be done? Steps to get there: Open AGO/Portal map, click layer in TOC ..., configure pop-up, under Attribute Expressions click Add to create a new custom expression, enter code above. Tried: $feature.PipeUniqueID = return Left($feature.PipeAssetType, 1) + "-" + text($feature.OBJECTID) , but does not calculate the field and returns " Parse Error: Line 5: Unexpected token return" . So I'm assuming it can't be done. If there's no possible way, I will post to Arcgis Ideas.
... View more
03-20-2019
01:40 PM
|
0
|
0
|
107
|
POST
|
Emmor, Can you be more specific on how you did the calculate, please? Did you use the "def encode..." part of the python code like the following: def encode ( latitude , longitude , codeLength = PAIR_CODE_LENGTH_ ) : if codeLength < 2 or ( codeLength < PAIR_CODE_LENGTH_ and codeLength % 2 == 1 ) : raise ValueError ( 'Invalid Open Location Code length - ' + str ( codeLength ) ) # Ensure that latitude and longitude are valid. latitude = clipLatitude ( latitude ) longitude = normalizeLongitude ( longitude ) # Latitude 90 needs to be adjusted to be just less, so the returned code # can also be decoded. if latitude == 90 : latitude = latitude - computeLatitudePrecision ( codeLength ) code = encodePairs ( latitude , longitude , min ( codeLength , PAIR_CODE_LENGTH_ ) ) # If the requested length indicates we want grid refined codes. if codeLength > PAIR_CODE_LENGTH_ : code = code + encodeGrid ( latitude , longitude , codeLength - PAIR_CODE_LENGTH_ ) return code in the Code Block? And what did you put in the <fieldname> = box?
... View more
02-08-2019
12:21 PM
|
0
|
1
|
102
|
POST
|
@Ted. Thank you for the code, but I got away from Access long ago. So many people I work with in the office and outside the office, either hate Access or so used to the ease of data entry in Excel (probably as bad as I hate "Pro"(longed) -verb meaning: extend the duration of. ". I'll just post it on the "ideas" page and see where it goes from there.
... View more
10-30-2018
06:13 AM
|
0
|
3
|
121
|
POST
|
Dan, tried your suggestion again just to verify. Setting column widths in Excel has no effect on output width; remains at 255 after setting several to 50 or less. Also, if I convert to .csv 1st, then use Table To Table the text field width increases to 8000. Any other suggestions or comments are appreciated.
... View more
10-16-2018
06:28 AM
|
0
|
0
|
121
|
POST
|
I get Excel from many different sources and clean up as much as possible before import. I usually set numeric fields to Number and leave the others alone. I have not found a way to set text field widths in Excel.
... View more
10-08-2018
10:28 AM
|
0
|
2
|
121
|
POST
|
I import many tables from Excel to a geodatabase regularly. Most have numerous columns (20 or more) that are Text type fields. The default text width value when setting Output Field Properties is 255, much larger than needed. Seems ridiculous users can't change the default to something like 30 or 50, something other than 255 as a width for all text fields being imported. Like many other things in Esri software modifications have to be done individually. Am I just missing something or is there a setting somewhere in the software when running the gp tool Table to Table, where the default width for text fields (under Field Map) can be changed?
... View more
10-08-2018
09:47 AM
|
0
|
9
|
549
|
Online Status |
Offline
|
Date Last Visited |
a month ago
|