|
BLOG
|
Is there a reason why GNSS Metadata is not supported on iOS? Having GNSS metadata is pretty important and I would like to understand the reasoning why GNSS metadata is not supported on one platform but is supported on another platform. We would like the flexibility to be able to be able to switch OS platforms with an R2 unit while still receiving the same functionality, including having GNSS metadata.
... View more
03-02-2020
07:50 AM
|
0
|
0
|
30389
|
|
IDEA
|
We're experiencing an "issue" when users re-publish feature services in ArcGIS Pro and ArcGIS Enterprise and it un-shares it with the group it was previously in. Below is an example of the issue. I publish a feature service and share that feature service to a group. A second user (who is also an administrator in Portal) re-publishes the feature service, but it un-shares that feature service with the group if that user is not a member of the group. We never had this issue in ArcMap, so I don't understand why it's an issue in ArcGIS Pro. If you're an administrator, you have access to every single group in Portal, even if you are not a member of it. So I don't understand why it would un-share it with the group. I realize that it is an "easy" fix to just become a member of a group, but some users don't know what group a feature service is a part of and it's an inconvenience to go to the feature service, see what groups it is a part of, and verify that they are a member of the group. Plus, there is the added inconvenience that you (even as an administrator) can't even add yourself as a member to an existing group. You either have to ask someone else to add yourself, or change the owner of the group to yourself which doesn't make sense because you're not allowed to add yourself as a member, yet you can change the owner of the group to yourself. Again, this issue did not exist in ArcMap. This is a pretty annoying inconvenience. I propose that re-publishing feature services in ArcGIS Pro does not un-share it with any group if the user who is re-publishing is not a member of that group.
... View more
02-20-2020
08:35 AM
|
2
|
1
|
1151
|
|
POST
|
Ok, that's what I thought. Just wanted to make sure. Thank you for answering my questions!
... View more
02-11-2020
06:52 AM
|
0
|
0
|
3300
|
|
POST
|
Thank you for the link. We do no have HA Portal/Data Store. Only HA ArcGIS Server. So if that is the case, I would not need to modify the privatePortalURL, correct? It looks like I would not follow steps 8 and 9. And I've followed step 10 as we have already expanded the site. The only thing that we have not done is changed the admin URL for ArcGIS Server to point to the web adaptor URL. Where specifically do I need to update the admin URL? Is that step 11? It looks like step 11c is where I specify the HA URL, but do I need to change that URL anywhere else first? I just want to make sure I follow the correct steps.
... View more
02-10-2020
01:03 PM
|
0
|
2
|
3300
|
|
POST
|
And reading further, I specifically see the note in the documentation stating when federating with multimachine/HA sites, to use the web adaptor or load balancer URL. Since we started out as a one machine shop, we didn't have to worry about that. Now....it looks like we do. So I guess my question now is if it is possible to change that URL in a site that is already up in running?
... View more
02-10-2020
11:34 AM
|
0
|
4
|
3300
|
|
POST
|
That is correct, the admin URL is set to the machine name URL of the machine that is down (which was the original server, we've since added a second server to the site). I always thought that the admin URL has to be the machine name URL of one of the servers. Am I incorrect in thinking that? If so, what should the URL be set to (and would it be possible to update that URL)? Looking back at the documentation, it looks like I can also use the web adaptor URL as the admin URL.
... View more
02-10-2020
11:32 AM
|
0
|
5
|
3300
|
|
POST
|
I am currently using ArcGIS Enterprise 10.6.1 and have two ArcGIS Server VMs joined to the same site for high availability and load balancing. We recently experienced an issue with one of the ArcGIS Server VMs and it had to be taken down for maintenance for an extended period of time. Luckily, the other ArcGIS Server VM is fine and everything is working as expected with the exception of Survey123. I am unable to publish new Survey123 forms. The ArcGIS Data Store is working fine and I can view hosted feature services in Portal just fine, I just can't publish new Survey123 forms. I receive an error: "Create Service exception ' Exception: Connect to host [server name] failed: connect timed out'" I will add that the server name that it is trying to connect to is the server that is currently down for maintenance. Obviously I expect to be able to publish Survey123 forms once the server comes back online, but I don't understand why I can't publish Survey123 forms when one server is down. Isn't one of the points of high availability that when one server goes down, the other still functions normally and picks up the slack until the other server comes back online? If that is the case, why won't it let me publish new Survey123 even when one server is down?
... View more
02-10-2020
09:32 AM
|
0
|
7
|
3450
|
|
POST
|
Yes, I have been having the same issues with trying to sign in to ArcGIS Pro using ArcGIS Online logins.
... View more
01-28-2020
05:54 AM
|
0
|
0
|
2901
|
|
POST
|
I am on 10.6.1 and we are also experiencing this issue, except with a Kafka connector. Did you ever find a solution to this?
... View more
01-10-2020
08:06 AM
|
0
|
0
|
1770
|
|
IDEA
|
I would like to see some additional data management options in the ArcGIS Data Store. I'm currently noticing some data management issues that could probably be easily resolved if Esri provided some additional data management tools. For example, the size of our ArcGIS Data Store is getting bloated and we have no way to reduce the file size. We host the ArcGIS Data Store on its own VM, but deleting the data from the hosted feature service (such as through ArcGIS Pro) does not actually release data back to the OS. I would like to see an Esri tool that would actually release the free space back to the OS (usually accomplished by using a Full Vacuum command in PostgreSQL). I understand that deleting records from the tables will release the space back at the table level (usually through the regular vacuum command which appears to be happening, at least according to the ArcGIS Data Store logs), but I would like to extend that further to release it back to the OS. I deleted approximately 100GB worth of photos, but none of that data is being released back to the OS, and our available storage space is still going down because we're still collecting data in other tables. It is not sustainable for us to just continually adding space to the VM. We need to be able release free space back to the OS to make room for other surveys that contain photos. I have access to the ArcGIS Data Store through pgAdmin, but would prefer to perform these actions using an "Esri approved workflow", such as using an ArcGIS Data Store command utility. Furthermore, since I do have access to the ArcGIS Data Store through pgAdmin, I am noticing that Esri is not always deleting tables it no longer needs (such as when deleting the hosted feature service in Portal or when updating an existing Survey that requires it to "delete" and re-add the table because it is making a schema change to the survey). It leaves the old tables in the database, and just creates new tables. This is very dirty data management which results in a bloated ArcGIS Data Store which Esri gives us no option to cleanup unless if we modify the ArcGIS Data Store directly through pgAdmin which Esri does not recommend. If there could be some cleanup operation that detected orphaned tables and deleted them, that would be nice.
... View more
01-06-2020
12:45 PM
|
56
|
15
|
8955
|
|
POST
|
Just to update, I checked the underlying PostgreSQL database of the hosted feature service and the base table contains the 'survey_version' field, but the view does not contain it. I'm just going to publish a brand new Survey123 form.
... View more
12-09-2019
10:57 AM
|
0
|
0
|
2706
|
|
POST
|
Hello, That's what I was thinking. But there are no fields named 'survey_version'. I checked both the excel document and the hosted feature service and no fields exist with that name. Furthermore, when I click the Publish button in Survey123, it gives me a warning that the survey has already been published and that one field was not found in the feature service, which is 'survey_version'. So it definitely appears that it does not previously exist. I'm assuming the solution would be to just create a new Survey123 form. But I was hoping to avoid going that far to fix the problem.
... View more
12-09-2019
05:11 AM
|
0
|
0
|
2706
|
|
POST
|
I am trying to republish an already existing Survey123 in ArcGIS Enterprise. All I did was add a new field to the survey called "survey_version" and when I try to republish it, I get the following error message: ERROR: Field name collision found: survey_version." Error code: 500. Any thoughts on what could be causing this error message? I've been able to re-publish other forms with the exact same field name and haven't had any issues.
... View more
12-06-2019
07:17 AM
|
1
|
3
|
2837
|
|
POST
|
I am currently trying to change the ArcGIS Data Store backup location (using the configurebackuplocation command), but it is not letting me change the location. Every time I try to change the location, it says "Error encountered: Machine (machine URL) returned an error. 'There is a database backup process running.'" I've set the backup frequency to 0 so it no longer backs up and confirmed that it is no longer writing data to the backup location folder, but it is still giving me this error message. Are there any ideas on what the issue is or how to resolve it?
... View more
12-02-2019
11:25 AM
|
0
|
3
|
2359
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | a week ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
12 hours ago
|