|
POST
|
Is there advice out there for how to handle projections when collecting data in a feature service? Our workflow involves collecting polygon data from disparate areas, and we've been having field workers append locally-collected data to a feature service so it can be QC'd and pulled down by a data steward. Results seem to differ depending on various techniques, and I do not know how best to standardize it. Standard display for items on AGOL is WGS 1984. However, if you publish a layer to AGOL it retains the spatial reference it was published in (or at least it says it does). Below is a feature service, accessed in Pro, that seems to have retained the spatial reference of the original feature class. First question: Should one make sure a feature service stays in the intended output feature class? We will ultimately archive the data in Teale Albers; is it best practice to have the feature class projected as such so as to not skew out put? Second question: I have noticed changes happen as data is transformed going in/out of feature classes, and I would like to pinpoint the issue. For this scenario, the feature service is in WGS 1984. Local parent data is in Teale Albers. Map is in Teale Albers. When appending the data to the feature service it gets skewed. When it gets exported back out to Teale Albers it remains skewed. See below. However, if the original data is added to the feature service by Copy/Paste, it remains correct, both as projected in the feature service and upon export. If data is re-projected to WGS 84 prior to appending, then exported in Teale Albers, the output would be correct. I would like to avoid having field staff re-project their data prior to appending, so want to know how to set up the service properly. So: What is the appropriate technique for managing projection differences in our workflow? If we plan to collect locally stored polygons in a feature service, and then export them in a particular projection, should the feature service be in that projection? Is this further complicated if we also want to collect data in the same feature service on a mobile device?
... View more
02-24-2022
09:31 AM
|
0
|
0
|
902
|
|
POST
|
Definitely not a dumb question, as you're absolutely right. I didn't even notice the box existed.... Unchecking the box fixes the problem. A few odd things that threw me off, in case somebody else sees this....only shapefiles get generalized. You can have the box checked for any other form of data and it's not generalized. And the generalizing is not just for web display...if the feature is copied over from its generalized form that generalization is preserved.
... View more
02-17-2022
11:04 AM
|
0
|
1
|
1304
|
|
POST
|
I have noticed an issue with the Web App Builder's Add Data widget that I feel didn't used to exist. I have had this workflow in place for a few years now and do not remember this issue occurring, so I am wondering if this is a new change. The issue: the Add Data widget, when uploading a zipped shapefile, way over-generalizes polygon features. See below: You can see the 'real' version of the feature underneath it in red, and the 'Add Data' layer overlaid on top in blue. You can see how many vertices get dropped. Contrast that with using the Add Data widget with a GeoJSON... It also works equally well with using the widget with an existing feature service version of the data. Every other method of adding data to the feature service preserves the vertices (appending to feature service vis Pro, copy/paste into feature service via Pro, appending data in AGOL using the 'Update Data' option on the items home page). The only way it seems to be dropping vertices is through a zipped shapefile. This is quite problematic for our workflow, as most of our field staff will have data in shapefile format. I would rather not have to ask them to convert their data to another format, when the Add Data widget clearly accepts zipped shapefiles (and the rest of the AGOL platform seems to not have a problem with appending a zipped shapefile directly). So, rest of the community: have any of you noticed this? How long has this been going on? Esri folks: Why on earth would the platform do this? And how long has this been going on?
... View more
02-17-2022
10:09 AM
|
0
|
3
|
1332
|
|
POST
|
@ZhifangWang Thank you! This works perfectly, and I was quickly able to reference those parent records in a feature report. Seems very simple and makes plenty of sense now that I see it, so thank you for getting me there.
... View more
01-12-2022
07:16 AM
|
0
|
0
|
5709
|
|
POST
|
@ZhifangWang You have it correct! There are two iterations that I would like, in descending order of importance, as the second I can (sort of) already accomplish. Using your examples: A feature report based on Survey B (1:1 child), that accesses attributes from the parent. In my case, the parent is a jurisdiction, and the child record is a long status survey that gets updated bit by bit as they move through an inspection process. When the process is complete, I'd like to be able to produce a written report (done mostly from the child record), but also bring in attributes from the parent record, like jurisdiction name, county, personnel responsible, etc, which are all contained in the parent record. This obviously can be accomplished if I just include those attributes in the child table as well, but that seems redundant. A feature report that groups multiple records from Survey C (1:M child), while accessing information from Survey A (parent) Survey C represents inspection records, and the goal here is to produce reports based on the parent (jurisdiction) that summarize the whole inspection history. In my case this is the easiest to do, as I did not use a GUID to link the records, rather just the name of the jurisdiction, in order to avoid a URL parameter in the mobile app. So I believe I could filter by jurisdiction in the report view on Survey123 and run the report. However, it would be great to be able to work this also as a URL parameter, so field staff could click on their jurisdiction in a map (i.e., the parent record), and produce a report for the whole jurisdiction that accesses both the parent and the collection of child records. Can we do it? Do we have the technology?
... View more
01-10-2022
08:45 AM
|
0
|
7
|
5742
|
|
POST
|
I have a feature service with two related tables. I have surveys that reference all three elements separately (the parent feature service, the 1:1 table and the 1:M table). I would like to be able to run feature reports for one of the related tables, but also include attributes from the related parent record. Can this be done directly in the syntax of the feature report template, or does this need to start from data design? In this case my parent feature layer includes jurisdictions and their basic information, and the 1:1 table is a status record. They are linked through globalID, and I didn't think to include some of the basic data already contained in the primary. Can I pull that data through the report template, or should I redesign the table to include it?
... View more
01-07-2022
01:44 PM
|
1
|
13
|
6694
|
|
POST
|
Sometimes I think it just takes asking for help to push you towards finding your own solution. I was stuck just trying to get the parameter to work, but I just added a field to the feature service and calculated over the child's global ID. Since it's 1:1 this shouldn't cause any issues. Now I just feed the URL globalId={ChildID} and it does the job just fine. Thanks for your help, though! The engagement is appreciated.
... View more
01-06-2022
04:26 PM
|
1
|
1
|
3036
|
|
POST
|
I will try to clarify my workflow. Created feature class with my jurisdiction data Created two related tables. One is 1:M, linked via the City fields the other is 1:1, linked via GlobalID field in the parent and the JurisdictionID fields in the related table. Appended all jurisdictions to 1:1 table (only fields carried over were 'City', 'County', and 'JurisdictionID' sourced from the parent GlobalID field'). So now I have 539 records in feature class, 539 matching records in the 1:1 table, and 0 records in the 1:M table. Publish feature class to AGOL, which brings the two related tables with it. Create survey #1 - New survey in Connect, based on feature service. This survey edits the main table for the feature service. Create survey #2 - New Survey in Connect, based on feature service. In Settings page, change form_id to 1:M related table. Configure survey with fields found in 1:M table. Create survey #3 - New Survey in Connect, based on feature service. In Settings page, change form_id to 1:1 related table. Configure survey with fields found in 1:1 table. Open web map with feature service. Configure pop-up. The first URL parameter allows you to edit the core feature service (The first URL in my original post). Configure pop-up for 1:M table (the second URL in my original post). This feeds the form the 'key' field, which in this case is 'City.' This is likely like the plotkey in your example. This is where I'm stuck - configure pop-up to edit the 1:1 table. I plan to hand a dashboard to our staff, and I'd like them to be able to edit the core feature service, the 1:M table, and the 1:1 table from the same pop-up. However, I am having a hard time figuring out how to configure the URL to edit the 1:1 table. The mode should be 'edit' since each parent record should have a single related record, right? I could feed it to add a new record, but that's not what I want to do. This URL <https://survey123.arcgis.com/share/0b3887da838e453f8da75f66b2e937a1?mode=edit&globalId={GlobalID}> yields this: ...and this URL <https://survey123.arcgis.com/share/0b3887da838e453f8da75f66b2e937a1?mode=edit&JurisdictionId={GlobalID}> yields this... ...and this URL <https://survey123.arcgis.com/share/0b3887da838e453f8da75f66b2e937a1?mode=edit&globalId={JurisdictionID}> yields he same as above. What was unclear to me in your workflow was what relationships your related tables had to the parent (1:1 or 1:M). I understand from your post that you do not seem to think you should start from the feature service but I can't really see why not. The workflow seems more or less the same, unless it's in how the relationship is configured. In either case you have a survey and point it towards a new item. The issue here is how to edit a record in a 1:1 related table.
... View more
01-06-2022
03:29 PM
|
0
|
0
|
3043
|
|
POST
|
Howdy! I hope what I am trying to do is possible. I would like to edit data in a 1:1 related table using Survey123 and URL parameters. However, I am having trouble feeding the URL the correct GlobalID to access the record in question. I am not sure if this is possible, as what I believe to be the necessary GlobalID is not actually accessible from the parent service. But more details below. The basic setup: I have a feature service with two related tables, one is 1:1 and the other is 1:M. I have three surveys that will be used with this feature service. One edits the table of the feature service itself, and is used to update some of the core information, like personnel responsible, etc. This works fine. URL: https://survey123.arcgis.com/share/66de662f0ee040cd9e6ffe2b8cb84b16?mode=edit&globalId={GlobalId} The other creates inspection records in a 1:M table. This is also working fine. Note that this relationship is not using a GlobalID, as is typical. I wanted users to be able to use the URL parameter in the web browser as well as add records directly in the mobile app. Each jurisdiction is named uniquely, so that's the key field, and what is fed to the survey from the feature services pop-up. https://survey123.arcgis.com/share/4d675461aacf414783efd4718d16696c?field:County={County}&field:City={City} The third table is a long survey, which will only be submitted once. I did not want it to be part of the parent feature service, hence why I put it in a 1:1 related table. This table is related through the GlobalID from the parent feature service, in a field JurisdictionID. However, I believe what I need to feed the URL parameter to edit the related record is the globalID of the related record, which I do not know how to access in the feature service via URL parameter. Is this possible? Are there potential workarounds? I would like to keep the one-off survey as a separate table since it's incredibly long, and allows separate handling of the core records.
... View more
01-06-2022
02:07 PM
|
0
|
5
|
3063
|
|
POST
|
Thanks for the response. I will try that. It's a little less clean but I think I can guarantee uniqueness.
... View more
01-05-2022
07:55 AM
|
0
|
0
|
656
|
|
POST
|
I am not sure if what I am trying to do is possible (or if I'm not quite thinking about it right), but I thought I would ask. This question is very similar, but the solution is not quite what I'm looking for. I'll page @DougBrowning as he answers the original. What I'm trying to do: I would like to create related records in Survery123 but be able to make the connection to the parent record in the form itself. The workflow that I keep seeing described uses URL parameters. These are excellent, but require the users to access a secondary mobile application to produce a record. My use case involves inspections for local jurisdictions. So I have a feature service with fixed geometry and I would like to be able to relate numerous inspection records (1:M) to those jurisdictions. It's very possible to configure map or dashboard or similar to launch the survey from, but I would like my users to be able to both create a new (related) record via URL parameters in web browser as well as be able to open the mobile app and submit a new record. For instance, with URL parameters my users can click on Jurisdiction X, launch the survey to produce a record. Could they also open their mobile app, choose the jurisdiction from a drop-down list, and create a related record that way? There are other ways to achieve this, of course (like using the same jurisdiction domains in two separate datasets and then performing joins) but I want to know if the above workflow is possible.
... View more
01-04-2022
12:55 PM
|
0
|
2
|
691
|
|
POST
|
I have a tool I created in Model Builder using 2.7. It has worked as intended for several months. After recently updating to 2.9 that same tool is stuck on creating a search index. This was not, so far as I could tell, a noted part of the tool previously. I do not see this as a configurable environment setting. The tool gets to this stage and then stalls out.....Any help would be appreciated.
... View more
12-14-2021
02:07 PM
|
0
|
1
|
905
|
|
POST
|
@mpboyle are you able to actually save edits in the HTML editor in the New Map Viewer? I found your thread because I am trying to update maps to the new viewer and don't seem to have the option to save edits in the HTML mode when configuring pop-ups. I can manipulate the text but the save button is greyed out.
... View more
12-13-2021
10:55 AM
|
1
|
2
|
3284
|
|
POST
|
Thanks, @CraigWilliams for the tip about the new Map Viewer. I was unaware of that change. If you're suggesting submitting an Idea in reference to the original post, I don't think one should have to. If the advertised purpose of the language is to move between platforms it should, you know, actually move between platforms. If a layer has a Arcade-formatted labeling expression in Pro it shouldn't be sabotaged once published to AGOL. Just my two cents.
... View more
12-10-2021
12:11 PM
|
6
|
0
|
9524
|
|
POST
|
@XanderBakker, @AmirBar-Maor - Are there any updates here? Is there any plan to support this type of label configuration in ArcGIS Online? Arcade is touted for it's ability to move between platforms, which is great when it works....until it doesn't. Basic globals like TextFormatting.NewLine (even though it's clearly listed as an option in expression construction), as well as formatting tags like the example above don't translate to AGOL. Which is a bummer. Can you offer insight?
... View more
12-09-2021
11:38 AM
|
0
|
2
|
9543
|
| Title | Kudos | Posted |
|---|---|---|
| 7 | 10-31-2025 09:00 AM | |
| 1 | 08-21-2025 04:41 PM | |
| 1 | 08-14-2025 01:24 PM | |
| 1 | 07-27-2025 10:25 AM | |
| 1 | 07-23-2025 11:30 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-06-2025
12:24 PM
|