|
POST
|
Hi James, Is the fix still on track for this week? I have a few folks ready to give me the Ned Stark treatment at this point, so I'll need to go with plan b if the fix wont be in place soon. Thanks, Rob
... View more
03-20-2019
10:20 AM
|
0
|
8
|
2999
|
|
POST
|
Philip Wilson James Tedrick I emailed you a copy of the photos and a report. Seems to be only portrait photos that have the issue. Device: iPad A1823 (5th gen) / iOS v12.1.4 / S123 v3.3.64 Photo is taken as a jpeg (not heic)
... View more
03-15-2019
10:29 AM
|
0
|
1
|
3682
|
|
POST
|
I am running in to this issue myself, which is causing me some grief. Some of our field users are taking photos with the device camera (this allows you to use the photo elsewhere) instead of the S123 app camera (which does not save the photo in the camera roll). James Tedrick and Philip Wilson is this a known issue with a planned fix? If not can I request a fix/enhancement?
... View more
03-14-2019
05:27 AM
|
0
|
2
|
3682
|
|
POST
|
In pre-aurora releases a, longer popup title would wrap to a new line so you could see the whole thing. In v18+ the popup titles no longer wrap and get cut off. Is this intended, or a known limitation? Can this be fixed in the future?
... View more
03-09-2019
05:24 AM
|
0
|
0
|
548
|
|
POST
|
Ok thanks for the info. Incidentally I crated a new map and everything now works as expected in the latest Collector update. Previously I was seeing the "Code=3054 "The item to be created already exists in the database."" error for some layers. Are there multiple causes for this issue? I did re-publish some data that went into the new map, but there were no significant schema changes.
... View more
03-07-2019
12:57 PM
|
0
|
1
|
2944
|
|
POST
|
Thanks for the into Philip. Is there any timeline on when reports will move out of Beta? Thanks, Rob
... View more
03-07-2019
11:49 AM
|
0
|
2
|
2999
|
|
POST
|
Based on the blog link below, the transformation to WGS84 seems like it would be embedded in the hosted feature service JSON somewhere. How can I find this? Doing some sniffing around, it seems like HFS published from ArcMap (10.4.1) has a spatial index set which references the transformation. However, I'm not seeing this in a HFS published from Pro (2.2) When you need to branch out and overlay that data on basemaps that are not the same as your organization’s basemaps, you can pick the right transformation for your data before you publish. In the latest release of ArcGIS Online, you can do just that when publishing hosted feature layers. Any supported transformation you set in the map or data frame before publishing will carry through and be used when working with the hosted feature layer. https://www.esri.com/arcgis-blog/products/arcgis-online/uncategorized/taking-control-of-transformations-with-hosted-feature-layers-september-2017/
... View more
03-07-2019
09:36 AM
|
0
|
0
|
678
|
|
POST
|
Unfortunately we need to keep the data in State Plane so that's not an option. I did resolve the issue, it was due to the coordinates passed to Survey123. A combination of different workflows by different users (impacting the transformation of WGS84 coordinates) along with some unexpected rounding issues caused the shift. Thanks for the suggestion.
... View more
03-07-2019
09:31 AM
|
0
|
0
|
1519
|
|
POST
|
I have data in NAD 83 State Plane NJ ft which was published as a hosted feature service from ArcGIS Pro 2.2. Before publishing I specified the transformation to WGS84 (NAD_1983_To_WGS_1984_5) I am passing line centroid coordinates from that HFS (in WGS84) to a Survey123 survey. The points in the Survey123 hosted feature service (which is in WGS84) do not overlay the line as expected when viewed in ArcGIS Online (with an Esri basemap). There is a shift of ~3 ft. If I bring all of the data into Pro and set the transformation to None everything lines up. However, when I set the above transformation in the Pro map I see the shift. I'm starting to suspect the centroid coordinates are to blame. I need to do more testing to see if I can narrow it down. For now, I'm asking here to see if anyone has encountered this before.
... View more
03-06-2019
04:26 PM
|
0
|
2
|
1591
|
|
POST
|
Kylie Donia was this intended to be fixed with the v19.0.1 Release? I am still getting this error after the app update.
... View more
03-06-2019
04:20 PM
|
0
|
27
|
5287
|
|
IDEA
|
Currently only the hosted feature service owner or an admin can append features to a HFS. Can this capability be expanded? A publisher in a group with update capabilities seems to be a logical place to allow this. Manage hosted feature layers—ArcGIS Online Help | ArcGIS As the owner of a hosted feature layer or the organization's administrator, you can append features to a layer within an existing hosted feature layer.
... View more
03-06-2019
05:02 AM
|
4
|
1
|
943
|
|
POST
|
Thanks James. I tried altering the schema as described in my last post but that didn't work. The only other thing I can think of is to re-publish with a new repeat but I'm not sure that's possible without overwriting the service. Now that I'm thinking more about it, I suppose I can also add new fields, calc over the values, delete the old fields, then published a new survey on top of the existing HFS. Any other recommendations?
... View more
03-03-2019
09:32 AM
|
0
|
15
|
3834
|
|
POST
|
Bethany what is the error you receive? I have a workflow set up as you described (S123 publishing to a related table in an existing hosted feature service based on a string, not a GUID). The caveat is that you need to verify the "supportsApplyEditsWithGlobalIds" parameter in the hosted feature service is equal to true (view the HFS JSON and search for that parameter). The easiest way to make sure this happens is by enabling sync when you publish the HFS (and leave it enabled even if you don't plan top sync, because disabling can trigger a bug). I would suggest you find a way to use GlobalIDs to avoid any future issues. You can add GLobalIDs to your esixting data, then use the address to create a lookup to rebuild the relationship.
... View more
03-02-2019
11:06 AM
|
0
|
0
|
2265
|
|
POST
|
I had a little time to mess around with the issue this afternoon. I reproduced this error by creating a field label that is the same value as a repeat (either repeat label or repeat name, I didn't look at which one was the cause). James Tedrick do you have a suggested fix in the meantime? I re-published the survey with an revised label, then re-generated a report template but the error still persists. I also manually changed the field alias in the feature service settings but that didn't work either.
... View more
03-02-2019
10:47 AM
|
0
|
17
|
3834
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 3 | 2 weeks ago | |
| 1 | 03-20-2026 04:14 AM | |
| 1 | 07-01-2025 05:11 AM | |
| 1 | 06-13-2022 11:18 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|