|
POST
|
OK cool. I see the map in Collector. When I click on an asset (Well), I can view the related records. This is the expected behavior. What is not working the way you would hope?
... View more
08-03-2018
10:01 AM
|
0
|
5
|
3259
|
|
POST
|
If you want to invite me to your ArcGIS Online group I'll have a look, it'll be much easier for me to investigate your issue that way...
... View more
08-03-2018
09:42 AM
|
0
|
10
|
3259
|
|
POST
|
Have you considered using the append tool as referenced here?
... View more
08-03-2018
06:36 AM
|
1
|
2
|
943
|
|
POST
|
Hmm. In ArcMap when you #identify on the point do you see the appropriate related record?
... View more
08-03-2018
06:16 AM
|
0
|
12
|
6011
|
|
POST
|
You're on the right track. They (I) were suggesting to use GlobalID and GUID as a best practice if you're starting from scratch. If you're using existing data, then the easiest route will be to use existing primary / foreign keys. I imagine you'll have success
... View more
08-02-2018
01:21 PM
|
0
|
15
|
6011
|
|
IDEA
|
Have you considered selling your users on webmaps in lieu of paper maps? It would be some work to set up, but using a combination of different layers displayed at different scales you might be able to accomplish this task. For example, when zoomed all the way out to the market area, show only your customer's existing locations, and maybe 1 or 2 of the major competitors' locations. On zoom, you could turn on some more competitors locations.
... View more
08-02-2018
11:54 AM
|
0
|
1
|
1944
|
|
POST
|
So the way the Relationship Class will work is this: When you create a new record in the Related Table, the GUID will be populated with the GlobalID of the Feature it's related to. The reason you aren't seeing any records when you click on the feature is because there are no records related to that feature until you create them. If you're wanting to related existing records to the features, you'll need to create the relationships manually in ArcMap using GlobalID -> GUID, or, alternately, use some existing key(s) that relate the table to the features. I'd suggest reading up a little on Relationship Classes before doing any more work.
... View more
08-02-2018
11:47 AM
|
0
|
17
|
6011
|
|
IDEA
|
Out of curiosity, at approximately what scale are you making your maps?
... View more
08-02-2018
08:40 AM
|
0
|
1
|
1944
|
|
IDEA
|
This isn't an option for basemaps, which I believe is the driver behind this idea?
... View more
08-02-2018
08:22 AM
|
0
|
0
|
7496
|
|
POST
|
Joe Borgione has the right idea. I would add a word of caution about Zip Codes - These are amorphous, and they are not true polygons as explained in much detail here; they are delivery routes, and the Postal Service can and does change them regularly. I understand managers want to leverage these as predetermined service areas but it's a nearsighted approach.
... View more
08-02-2018
08:08 AM
|
2
|
1
|
1605
|
|
POST
|
To answer your first question, if you publish your data to AGOL without a GlobalID, then a GlobalID is automatically generated. It is suggested as a primary key because it is system generated, is unique and In order for the related table to appear in Collector your workflow should be: Create your feature class Use the Add GlobalIDs tool, ArcMap will handle this even if the feature class is empty. Create your related table, and include a text field called GUID Create your relationship between the feature class and the table, using GlobalID as the primary key on the FC and GUID as the foreign key on the table. Make sure both the FC and the table are present in your .mxd Publish to AGOL. Create your webmap, and then open it in Collector. Feel free to PM me if you have any questions on this one.
... View more
08-02-2018
07:45 AM
|
0
|
19
|
6011
|
|
POST
|
AFAIK, the only way in include transparency in your labels is to convert them to #annotation - see here.
... View more
08-02-2018
07:30 AM
|
0
|
0
|
2234
|
|
POST
|
The Description field should very clearly spell out the intention of the domain. For example, the domain name may be AssetOwner. The description could be "All inclusive list of electrical, water and gas asset owners". When creating coded value domains (for text) I'll typically make the coded value something like My_Coded_Value and the description will be My Coded Value. In your case, you're describing wanting to use numeric coded values and then use text as the description. I susepct that historically this was likely best practice since storage was more at a premium, and storing numbers was cheaper than long strings of text...however, anymore this doesn't seem to be the case. If you set up your domains with integers in the Coded Value field, and then a text description in the Description field, your users will see the Description in the dropdown when editing. Does this help?
... View more
08-02-2018
07:22 AM
|
0
|
0
|
3493
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-21-2019 07:46 AM | |
| 1 | 08-07-2018 12:30 PM | |
| 1 | 08-22-2018 12:51 PM | |
| 1 | 08-23-2018 09:11 AM | |
| 1 | 07-18-2018 08:45 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:24 AM
|