|
POST
|
If you're starting from a FeatureClass object, just try to cast it to an AnnotationFeatureClass: FeatureClasss myFeatureClass;
...
if (myFeatureClass is AnnotationFeatureClass)
{
AnnotationFeatureClass myAnnotationFeatureClass = myFeatureClass as AnnotationFeatureClass;
...
} Is this what you are looking for? --Rich
... View more
06-03-2020
08:07 AM
|
0
|
2
|
1943
|
|
POST
|
Uma's solution will work for file geodatabases. For shape files, we don't yet provide this functionality. I've added it to our backlog for a future release. In the meantime, your existing algorithm of looping through files in the directory with the .shp extension is your best bet. --Rich
... View more
06-01-2020
12:51 PM
|
0
|
0
|
1609
|
|
POST
|
You're correct. `Row.Handle` is not stable. Under the hood, the Handle property is just a pointer to an underlying ArcObjects object. When you open the same table twice, ArcObjects reuses the same COM objects, so Table.Handle is identical for both Table objects. With rows, this isn't true. Fetching the same two database rows with two cursors will create two different row objects (and different Row.Handle values). Flipping it around, if you use a recycling cursor, all of the rows fetched from that cursor will use the same underlying object, and Row.Handle will be the same for every one. (Since I've seen your other post, I'll also add that Table.Handle will have a different value every time you start ArcGIS Pro.) I hope this helps, --Rich
... View more
05-26-2020
09:10 AM
|
0
|
0
|
1402
|
|
POST
|
As Wolfgang Kaiser states above, you need to use a table name instead of an ID. Other than that your list above looks correct. --Rich
... View more
05-26-2020
08:52 AM
|
0
|
0
|
2463
|
|
POST
|
Anuj, The Pro SDK is implemented in terms of ArcObjects. While I've never tried it personally, I expect the two APIs would interfere with each other. It's definitely not supported. --Rich
... View more
05-26-2020
08:38 AM
|
0
|
0
|
4913
|
|
POST
|
Anuj, Matt is correct. The Pro SDK does not yet support Data Definition Language (DDL) operations directly. If you are writing a Pro Add-in, you need to use the geoprocessing API. In a stand-alone CoreHost application, you need to shell out to a Python script. --Rich
... View more
05-22-2020
08:52 AM
|
1
|
2
|
4913
|
|
POST
|
Hi Than, I think you want to take a look at QueryDefs (ProConcepts Geodatabase · Esri/arcgis-pro-sdk Wiki · GitHub ). This is another join construct in ArcGIS. It works with datasets that come from the same geodatabase. There are a lot of different query constructs available in the Pro SDK. In addition to just a basic query on a single table using Table.Search, we support QueryDefs, Joins, QueryTables, and QueryLayers. If the document above doesn't clarify the difference enough, my colleagues and I gave a session on the Geodatabase SDK at the (virtual) DevSummit this year: https://www.youtube.com/watch?v=EKx1kzQARlM&list=PLaPDDLTCmy4Ys8vfmC7DbX3FHSsyosvh7&index=151&t=0s The section on Queries starts at 14:40. I hope this helps, --Rich
... View more
05-20-2020
09:16 AM
|
0
|
1
|
2264
|
|
POST
|
Hi, I've been talking to Renato and other Esri staff offline, and wanted to add some information. 1. As you know, we do not provide access to the fine-grained network topology on the client. We've developed a detailed and flexible set of tracing configuration options to address the most common workflows, but we're no under no illusions that we've got them all covered. 2. You can use the Export Subnetwork geoprocessing tool to return the network connectivity for a subnetwork. Depending on the workflows you are trying to accomplish, this might help. 3. Our documentation hints that this capability is available with Trace. As Renato pointed out, this hasn't been implemented yet. In the short term we're in the process of removing this from the doc, but it remains on our long-term roadmap. 4. Starting with ArcGIS Enterprise 10.8.1, the Enterprise SDK will allow access to utility network topology in a Server Object Extension (SOE). You'll also need a way to call this SOE, either via directly calling a REST endpoint, or by writing a Server Object Interceptor (SOI). I hope this helps some. --Rich P.S. If you have more specific information about the business cases you are trying to solve we can investigate whether we could add the necessary options to our core product. Here are some ideas for the cases you described above. * You should be able to use the Nearest Neighbor filter to return the two nearest devices of a particular type. (You might need a second trace to find the nearest device so that you know the order of the devices.) * You might be able to use Functions to find voltage drop along a downstream path
... View more
04-28-2020
01:54 PM
|
1
|
3
|
4665
|
|
POST
|
At Pro 2.6 we will be adding a Version.ChangeOwner routine. This routine will only work with branch versioning, not traditional versioning.
... View more
04-25-2020
11:11 AM
|
2
|
0
|
1723
|
|
POST
|
The bug where the AuthenticationMode property was not returning the correct value will be fixed in Pro 2.6 (summer 2020).
... View more
04-25-2020
10:43 AM
|
0
|
3
|
3478
|
|
POST
|
If you post the schema of tables A and D, along with the geoprocessing command that you're using to create the relationship class, we can try to help you out. You might have better luck however, if you post in the Geoprocessing space rather than here in the SDK space. --Rich
... View more
04-15-2020
07:53 AM
|
1
|
0
|
1687
|
|
BLOG
|
Joins are read-only, although you can edit the underlying tables that make up a join. This is by design. Note that instead of using geoprocessing to create a join, you can also call the low-level geodatabase routines directly, as described here.
... View more
04-07-2020
04:25 PM
|
0
|
0
|
3076
|
|
POST
|
Hi Kenny, Your technique should work fine. In the upcoming Pro 2.6 release (summer 2020), we will be adding a GetPath() method directly to the FeatureLayer class so that you don't have to go through this to get the path. But if you're going through all of this just to find out if you are looking at a shape file, I would do something like this: bool IsShapeFile(FeatureLayer featureLayer)
{
using (FeatureClass featureClass = featureLayer.GetFeatureClass())
using (Datastore datastore = featureClass.GetDatastore())
{
if (datastore is FileSystemDatastore)
{
return true;
}
else
{
return false;
}
}
} I hope this helps, --Rich
... View more
04-07-2020
08:57 AM
|
2
|
2
|
2909
|
|
POST
|
Hi Sreeni, The geodatabase API doesn't allow schema changes (DDL). To programmatically add attribute rules, you will have to either Write a Python script Execute geoprocessing tools using the geoprocessing API Here is an overview of the attribute rules toolset. I hope this helps, --Rich
... View more
04-06-2020
08:17 AM
|
1
|
1
|
1775
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-13-2024 11:22 AM | |
| 2 | 01-29-2026 09:34 AM | |
| 2 | 01-28-2026 08:20 AM | |
| 1 | 12-10-2025 09:15 AM | |
| 2 | 11-30-2025 12:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|