POST
|
It appears there's different limitations with either method. Method 1 is good for carrying through metadata from the enterprise GDB, allowing users to search but it doesn't maintain links to related tables (eg. the inspection tables we use for field work). Not so good for defining style but we train our Portal users to modify styles in web maps. Method 2 is better for defining layer style prior to publishing.
... View more
01-08-2024
04:09 PM
|
0
|
0
|
232
|
POST
|
That's correct, it doesn't currently work within the one app which is why I am asking if there is an alternative. The Nearby widget in Web App Builder gave the option to intersect with polygons in addition to listing nearby point features. All in the one widget. Combining these types of queries is quite common in non-ESRI Local Government 'Near Me' solutions.
... View more
10-30-2023
02:02 PM
|
0
|
0
|
206
|
POST
|
In a single app, I need to list nearby points but also list the coincident polygon (zone) at the same time. Eg. Here are your nearest playgrounds and you live in this Council ward area. Is this possible using any of the templates ? Thanks
... View more
10-29-2023
10:34 PM
|
2
|
2
|
301
|
POST
|
Sorry I'm not following exactly. By Query Analyzer do you mean the Analyze geoprocessing tool? By 'Running my package' do you mean re-running the Project tool ? I don't understand the inserting master/detail sets comment. I assume the multistep operation is the Project tool.
... View more
08-27-2023
11:31 PM
|
0
|
0
|
853
|
POST
|
The problem disappeared the following day. Not sure what caused it. Possibly ArcGIS Pro (3.2.1) was not working properly at the time. I suggest if this occurs for you, close ArcGIS Pro and re-open. The only other thing that had changed overnight is that ArcGIS Server was stopped, databases were compressed, versions re-created and ArcGIS Server restarted. The problem feature classes were not in versioned datasets though but reside above them.
... View more
08-27-2023
06:51 PM
|
0
|
0
|
928
|
POST
|
In ArcGIS Pro version 3.1.2 When adding a SQL Server Enterprise feature class to the map or attempting to open the properties of the feature class : An error pops up saying "A check constraint violation has occurred." This occurred on feature classes that were created as a result of a Project (Data Management) geoprocess. Input and output feature classes reside in separate geodatabases within the same SQL server instance. Input and output layers used from the reprojection process are not within versioned datasets. ArcGIS Enterprise version 10.9 SQL Server version 2016
... View more
08-27-2023
06:47 PM
|
2
|
2
|
938
|
IDEA
|
I agree. I really need this on AGOL. If there's a workaround, please let me know.
... View more
05-24-2023
08:08 PM
|
0
|
0
|
403
|
IDEA
|
I am getting a similar error with NAType when trying to convert dataframe to a File geodatabase Feature Class too. df.spatial.to_featureclass (TypeError: value #5 - unsupported type: NAType) Would be nice to have options to deal with these things within the command.
... View more
03-22-2023
08:30 PM
|
0
|
0
|
1131
|
IDEA
|
When trying to look up a method or property for an item in the Python API reference, there is no single list of them. For example: Everything in the Item Class is on one extremely long web page. We need to see a quick list of methods and properties to click and navigate to that bookmark. Currently we have to scroll endlessly to find if a method or property exists. A lot of time would be saved for coders of all levels if the documentation was easier to navigate.
... View more
03-20-2023
05:19 PM
|
4
|
0
|
470
|
POST
|
I worked it out and have uploaded my code here. I hope it helps somebody. import sys
sys.path.insert(0, r'C:\myscripts\OverwriteFS')
import os
import OverwriteFS
# Import ArcGIS Python API and make a connection to Portal
from arcgis.gis import GIS
gis = GIS(username="johndoe", password="johnspwd")
# Get View item from Portal
itemId = "84a62b29fff5477f814ac7db77fb223c" # ID for feature layer view
parcelview = gis.content.get(itemId)
# set up the relationship of the view to A and B feature service items (I only had to run this once and the relationships held)
#relitems = ["6bbd1f51215f459796c8f026344e13a4","bf5680ef5e294d7t507810b3e448a735"] # related feature layers A & B versions. The view will point only to one of these alternating.
#OverwriteFS.updateRelationships( parcelview, relateIds=relitems, unRelate=False, verbose=True, outcome=None, dryRun=False)
# Determine which layer is Current and which layer is Target at the moment
outcome = OverwriteFS.getFeatureServiceTarget(parcelview, verbose=None, outcome=None, ignoreDataItemCheck=False)
# will check for error here and action it
# Set correct path-filename for source service definition
sdpath = r'C:\service_definitions' # In this folder, I have 2 service definition files, one named after the A version and one after the B
sd_fname = outcome["filename"] # name of target service definition.
print ('sdfname = ', sd_fname)
sourcefile = os.path.join(sdpath, sd_fname)
# Run the swapFeatureViewLayers function that updates target (idle) service and then Points the view to newly updated service.
# This also backs up the service's properties (eg. Summary, Tag etc) and restores it back to the service after overwrite
dry_run = False # Set it to true to run it in test mode where it just veries everything without making an overwrite or swapping
Service_Prop_Backup_Folder = r'C:\property_service_backup'
outcome = OverwriteFS.swapFeatureViewLayers(parcelview, updateFile=sourcefile, touchItems=True, verbose=True, touchTimeSeries=False, outcome=None, noIndexes=False, preserveProps=True, noWait=False, noProps=False, converter=None, outPath=Service_Prop_Backup_Folder, dryRun=dry_run, noSwap=False, ignoreAge=False)
# Check results
if outcome["success"]:
print( "Service Overwrite was a Success!")
elif outcome["success"] == False:
print( "Service Overwrite Failed!")
... View more
02-21-2023
10:37 PM
|
0
|
0
|
386
|
IDEA
|
We will be relying on the data replication tool in ArcMap to reproject all our data keeping relationship classes intact. ArcPro really needs this functionality.
... View more
02-15-2023
04:56 PM
|
0
|
0
|
1146
|
POST
|
I have imported the OverwriteFS module and wish to overwrite a feature service using the Feature layer View that alternates pointing to an A and a B version. The tool's documentation does not provide an example code for this approach. It's difficult to fully understand without an example. Is anybody able to share how they applied python commands for this overwriting approach ? Here is a link to download the OverwriteFS module if needed. https://www.arcgis.com/home/item.html?id=d45f80eb53c748e7aa3d938a46b48836
... View more
02-13-2023
10:30 PM
|
0
|
1
|
442
|
POST
|
Thanks Marlon, this is what we already do so we are on the right track I guess. Tags and descriptions go through to the metadata in the published services but it seems the metadata tool in ArcPro (ISO19115-3) does not accept 'custom' topic categories so we will need to maintain those separately in Portal only. The topic categories in the ISO standard are too broad for local government.
... View more
12-11-2022
10:22 PM
|
0
|
0
|
732
|
POST
|
Our aim is to publish many feature layers from our SDE geodatabases. (ArcGIS v 10.9, SQL Server 2017) We want the portal user to find data easily using tags and categories. We have applied metadata nicely within SDE. (Descriptions, Tags, etc) These layers are for querying and analysing only (not editing). How do most large organisations publish their layers for these Portal users ?? 1. Bulk publish (Sync) their SDE datastore connections and share accordingly 2. Create a few monster map documents and publish those from Pro. 3. Use a script to publish a single feature service for each layer. Test so far prove that number 1 works OK. The tags and descriptions can be searched when finding layers. Although I find the administration of the datastore a little cumbersome as I have to ensure the database connection username has access to the layer first. Approach number 2 is not helpful because all the sub-layers of a feature service do not store their individual Tags or descriptions. So the user can't search for the individual layers. Approach number 3. Is this worth pursuing ? What do large ArcGIS Enterprise clients normally do here ?
... View more
11-30-2022
11:58 PM
|
1
|
4
|
814
|
POST
|
Very late reply but it's a good question. We are at 10.9 and related tables are still not respected. From what I have tried, domains & subtypes are respected. Haven't tried attribute rules. Not all metadata goes through to the feature services. Only really the name, the tags, and description. Categories are not sent through to the service.
... View more
11-30-2022
11:34 PM
|
0
|
0
|
235
|
Title | Kudos | Posted |
---|---|---|
1 | 11-30-2022 11:58 PM | |
2 | 10-29-2023 10:34 PM | |
2 | 08-27-2023 06:47 PM | |
4 | 03-20-2023 05:19 PM | |
2 | 06-15-2020 10:41 PM |
Online Status |
Offline
|
Date Last Visited |
Sunday
|