POST
|
We tested this in the ArcGIS Pro 3.3 beta and confirmed that it works in that version. Thank you!
... View more
Monday
|
0
|
0
|
10
|
POST
|
I had to set a web context URL in portaladmin that pointed to my custom dns entry for portal. This fixed the Map Viewer issue. I learned this at DevSummit. https://enterprise.arcgis.com/en/portal/latest/administer/windows/using-a-reverse-proxy-server-with-portal-for-arcgis.htm#ESRI_SECTION1_7C753FB1F19349A398E5FFCC6079A821
... View more
03-14-2024
03:39 PM
|
1
|
0
|
210
|
POST
|
Thank you for that additional information and code sample. So basically anywhere GetDatastore() or GetDefinition() needs to be called we must first check with IsJoinedTable() to prevent an exception when not opening a feature class directly from the geodatabase? We cannot trust that the user didn't performed a temporary join on a layer in the map at any given time.
... View more
03-07-2024
01:47 PM
|
1
|
1
|
152
|
POST
|
In 11.2 I'm actually still seeing some issues with the "Map Viewer" where the "Map Viewer Classic" works and the new one does not. Have you tried an incognito window to 100% eliminate caches all together? Some times clearing the cache in the standard browser alone doesn't seem to clear it all the time.
... View more
03-07-2024
01:36 PM
|
0
|
0
|
246
|
POST
|
We discovered that when we copied all of these feature classes and tables from the FGDB with the spatial reference issue described above to a new FGDB, the data was magically corrected in the new database. It self-healed.
... View more
03-07-2024
08:53 AM
|
0
|
0
|
44
|
POST
|
Should the spatial reference you get from the feature class definition match the spatial reference you get from it's GetExtent()'s spatial reference property? I'm seeing the issue below and I'm wondering if the defined projection on my feature class is set to one thing while the data inside it was created in a different projection. What is the best and most reliable way to get the spatial reference? Does it matter if you get it from the feature class definition, the extent of the feature class or the feature's shape, etc.? var srFromExtent = featureClass.GetExtent().SpatialReference;
var srFromDefinition = featureClass.GetDefinition().GetSpatialReference();
// Output from above:
// srFromExtent = NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet
// srFromDefinition = NAD_1983_2011_Contiguous_USA_Albers In the Pro UI on that same feature class, I see the following:
... View more
02-22-2024
10:54 AM
|
1
|
1
|
181
|
POST
|
If you are running ArcGIS Pro while debugging, you will not see the progress bar. Try running ArcGIS Pro directly (without debugging) and see if it shows up for you.
... View more
02-13-2024
12:06 PM
|
0
|
0
|
107
|
POST
|
I created and attached a sample ArcGIS Pro project and sample Addin to demonstrate the issue so you can reproduce this exactly the way we are seeing it. See attached.
... View more
02-13-2024
07:55 AM
|
2
|
3
|
312
|
POST
|
We are using ArcGIS Pro 3.2.2 with a file geodatabase version 10.0. See images below for confirmation.
... View more
02-13-2024
07:03 AM
|
1
|
4
|
318
|
POST
|
Aashis, Thank you for your response and for providing the documentation on joins. Unfortunately this is not what I'm looking for and I believe you missed my point as I do not want to create or work with a join, I'm having to work around one. I will try to explain the issue a little better and in more detail below. Below is what we are trying to do Using the ArcGIS Pro SDK, we are getting a reference to a MapMember in the table of contents of a Map in an ArcGIS Pro project. From that MapMember, which in this case is a FeatureLayer, we get a reference to it's Dataset which is a FeatureClass. From that feature class object, we want to get a reference to it's data store, a Geodatabase, by calling GetDatastore(). The problem we are running into If the end user has created a Join on that particular MapMember/Layer/FeatureLayer in the map, the underlying FeatureClass object is getting changed after the join is created. This means that where before the end user did the join I could call FeatureClass.GetDatastore() without issue, now I get an exception making the exact same call on what appears to be the exact same object. So fundamentally, the Dataset object (Table or FeatureClass) that is returned from the MapMember is not reliable. Without constantly checking to see if the end user performed a join, how are we supposed to rely on these objects and their methods? Primary goal we are trying to achieve To clarify, I am not performing the Join in code nor do I care if a Join has been created, all I want is a reference to the MapMember/FeatureLayer/FeatureClasses Datastore without having to jump through hoops every time because the end user may have performed a join in the ArcGIS Pro UI. A Dataset/Table/FeatureClass should always be a Dataset/Table/FeatureClass at all times without changing how it's methods and properties work based on what a user has done in the map. I hope this helps explain what I'm seeing. If you can help me understand a better, more reliable way to get a reference to a Datastore from a MapMember (no matter if a join exists or not) that would be great. Maybe I've been going about that the wrong way.
... View more
02-09-2024
07:06 AM
|
1
|
6
|
365
|
POST
|
Entity Framework would likely by-pass the geodatabase versioning and agnostic approach that Esri has in place when using their APIs to access the data for CRUD operations.
... View more
02-08-2024
01:10 PM
|
1
|
0
|
131
|
POST
|
When attempting to get a data store reference from a Table or Feature Class object, if that table or feature class has a join specified on it, then the GetDatastore() call fails with an exception. I don't understand why this happens. The Table or Feature Class with the join on it is not the actual Join object because you have to call GetJoin() to get that. So why not continue to treat the original table or feature class as the original dataset object and if you want to check for a join or get a Join object you can, but let the original table or feature class work like normal without these exceptions. Below is what I have to do to get around this issue (everywhere). The "table" object is a Table class that has a spatial join assigned to it in the map. But to get the data store off that table without an exception I have to do this (see below). My question is why and is there a better way to avoid this? It feels like I'm just having to get the table from itself and that seems foolish. // Must check this because joined tables are virtual
// and fail when GetDatastore() is called on them.
if (table.IsJoinedTable())
{
// The origin table is the original table
table = table.GetJoin().GetOriginTable();
}
... View more
02-08-2024
12:47 PM
|
1
|
8
|
493
|
IDEA
|
We can get metadata from a MapMember object like a BasicFeatureLayer or StandAloneTable in 3.1. But it would be nice to be able to get the metadata from a FeatureClass, Table or RelationshipClass Dataset that is not in the project or map. Would like to be able to do something like this: var table = Geodatabase.OpenDataset<Table>(tableName);
var tableMetadata = table.GetMetadata();
var relationship = Geodatabase.OpenDataset<RelationshipClass>(relationshipName);
var relationshipMetadata = relationship.GetMetadata();
... View more
02-06-2024
11:29 AM
|
0
|
0
|
225
|
POST
|
Checking to see if any updates have happened in regards to metadata availability in ArcGIS Pro SDK. I can get meta data from a MapMember object like a BasicFeatureLayer or StandAloneTable. But it would be nice to be able to get the meta data from a Table or RelationshipClass object that is not in the project or map. Would like to be able to do something like this: var table = Geodatabase.OpenDataset<Table>(tableName);
var tableMetadata = table.GetMetadata();
var relationship = Geodatabase.OpenDataset<RelationshipClass>(relationshipName);
var relationshipMetadata = relationship.GetMetadata();
... View more
02-06-2024
11:17 AM
|
0
|
0
|
153
|
POST
|
We are finding this not to be true in regards to ArcGIS Pro maintained daml Ids. We are seeing some of these ArcGIS Pro daml Ids change from 3.1 to 3.2. This breaks compatibility if an addin was developed to target 3.1 that references an ArcGIS control by it's 3.1 daml Id when the addin is running on ArcGIS Pro 3.2 and has a different daml Id there. Is there a better method to doing this other than relying on these daml Ids that seem to change randomly as Esri refactors them randomly between each release? A good example of this is the 3.1 daml id "esri_fieldsview_commitButton" that in 3.2 is "esri_mapping_fieldsview_commitButton"
... View more
02-01-2024
02:45 PM
|
0
|
0
|
324
|
Title | Kudos | Posted |
---|---|---|
1 | 02-08-2024 12:47 PM | |
1 | 02-09-2024 07:06 AM | |
1 | 02-13-2024 07:03 AM | |
1 | 03-07-2024 01:47 PM | |
1 | 03-14-2024 03:39 PM |
Online Status |
Offline
|
Date Last Visited |
Monday
|