|
POST
|
Rows in database tables are inherently unordered. When you view a table, you can order the rows based on the value of a particular field. One way to implement your up/down arrow idea would be to create an "Order" field on the table and fill it in. Then the up and down buttons would edit the rows to swap their Order values. Whether you should do this is another matter, since this could mean a lot of database edits. Why are you trying to order the rows? --Rich
... View more
09-08-2020
08:31 AM
|
0
|
1
|
4768
|
|
POST
|
Daniel, What kind of geodatabase are you using? I'm seeing significant performance enhancements with file geodatabases and enterprise geodatabases. With feature services, I'm seeing an improvement, probably because in this case the database insertions are already being batched. --Rich
... View more
09-04-2020
01:46 PM
|
0
|
3
|
1721
|
|
POST
|
There isn't, sorry. That might be good material for https://community.esri.com/community/arcgis-ideas --Rich
... View more
09-03-2020
11:14 AM
|
0
|
0
|
2471
|
|
POST
|
Hi Daniel, The snippet you are looking for is over in the Geodatabase snippets area. That snippet shows how to use an insert cursor in a CoreHost app (command-line). If you want to run this inside a Pro add-in, you probably want to do something like this: using (FeatureClass featureClass = featureLayer.GetFeatureClass())
{
// Insert rows using InsertCursor
EditOperation insertCursorEditOperation = new EditOperation();
insertCursorEditOperation.Name = "Create rows using InsertCursor";
insertCursorEditOperation.Callback((EditOperation.IEditContext editContext) =>
{
using (InsertCursor insertCursor = featureClass.CreateInsertCursor())
using (RowBuffer rowBuffer = featureClass.CreateRowBuffer())
{
for (int i = 0; i < countRowsToCreate; i++)
{
// Fill in RowBuffer using your data here
insertCursor.Insert(rowBuffer);
}
insertCursor.Flush();
}
}, featureClass);
}
I hope this helps, --Rich
... View more
09-02-2020
03:40 PM
|
0
|
5
|
4719
|
|
POST
|
Mike, Are you hiding fields at the layer level? That would explain why the field indices don't match up between the Layer and the feature class behind that layer. Note that you can always reference a row value by using the field name rather than the field index. var nameValue = myRow["name"]; --Rich
... View more
09-02-2020
10:13 AM
|
1
|
3
|
2471
|
|
POST
|
Hi Jordan, Is there any error message with the exception? Generally in an ArcGIS Pro add-in it's better to use the Editor. This adds your edit to the operation stack for undo/redo and refreshes the map. An example of creating a feature using the Editor can be found here. If you do want to use the low-level editing routines, perhaps because this is a CoreHost application, you should adjust your use of Dispose/using and add a transaction as follows: using (Geodatabase geodb = ObtainGeodatabaseWithCodeYouDidntShow())
{
geodb.ApplyEdits(()=>
{
using (FeatureClass fc = geodb.OpenDataset<FeatureClass>("6"))
using (RowBuffer rowBuffer = fc.CreateRowBuffer();
{
rowBuffer["SHAPE"] = poly;
fc.CreateRow(rowBuffer).Dispose(); //disposes the row created by CreateRow
} // using block disposes fc and rowBuffer
});
} // using block disposes geodb I hope this helps. --Rich
... View more
09-01-2020
04:14 PM
|
0
|
0
|
1165
|
|
POST
|
Absolutely! Just use a NetworkAttributeComparison object instead. You can use the And and Or classes to combine multiple tests together. Depending on what you are trying to do, you'd add it to the Traversability, Filter, or OutputCondition properties of TraceConfiguration. --Rich
... View more
09-01-2020
03:58 PM
|
0
|
0
|
2566
|
|
POST
|
Hi Kieren, You do this by creating a CategoryComparison object, and setting it in the TraceConfiguration, like this: CategoryComparison categoryComparison = new CategoryComparison(CategoryOperator.IsEqual, “Protective Device”);
traceConfiguration.Traversability.Barriers = categoryComparison; If you haven't read it already, this doc walks through all of the different trace classes and how they are used. Also, we have a Load Report sample that demonstrates the use of a CategoryComparison. I hope this helps. Please let us know if you have further questions. --Rich
... View more
08-25-2020
11:10 AM
|
0
|
3
|
2566
|
|
POST
|
Hi Jan, I'm not that familiar with the layer-level query routines that you're using. Have you tried just calling FeatureLayer.GetFeatureClass() and querying against that? --Rich
... View more
08-24-2020
08:06 AM
|
0
|
0
|
3172
|
|
POST
|
There are no plans that I am aware of. Many customers are using CoreHost for data migration and similar applications. --Rich
... View more
08-21-2020
12:57 PM
|
0
|
1
|
5371
|
|
POST
|
We haven't looked at it yet, but we're scheduled to investigate during the Pro 2.7 release cycle (now through fall). --Rich
... View more
08-17-2020
05:06 PM
|
0
|
1
|
3728
|
|
POST
|
Hi Joe! Hope you and your family are doing well. We've had a couple of developers looking at this, and cannot find a way to reproduce it. Is there a chance you can use Fiddler, and send us the input/output from the calls to GetFeaturesForElementsAsync for the two different calls to CreateAsync()? Obviously, if your .NET app runs on Windows as well as the iPad this is straightforward. Otherwise you might need to follow these directions here. It's probably easiest to just e-mail the Fiddler files to [email protected]. If this isn't something you can easily do, let me know and we'll see if we can find another approach. Thanks, --Rich
... View more
08-13-2020
01:12 PM
|
0
|
1
|
5412
|
|
POST
|
Hi Ryan, If you are creating a single-threaded application, like a command-line app, you shouldn't use QueuedWorker. QueuedWorker really only exists to allow WPF standalone apps to run operations in the background (on a COM compatible thread) whilst allowing the UI to remain responsive. Does this make sense? --Rich
... View more
08-12-2020
11:06 AM
|
0
|
0
|
4616
|
|
POST
|
This is not yet part of the Pro SDK, although we are considering it for a future release. For now, you have to update the row and call Store(). --Rich
... View more
08-11-2020
11:06 AM
|
0
|
0
|
858
|
|
POST
|
Hi Mody, I've been working with Nobbir Ahmed on your question. There's no direct way to work with in-memory feature classes using the Pro SDK, but there is an indirect way. When you run your geoprocessing tool with the Pro SDK, set it up to output your results to a map. If you do that, a FeatureLayer is added to the map. You can then call FeatureLayer.GetFeatureClass() to get a FeatureClass object. You should be able to treat that as a regular feature class. (Note that If you call FeatureClass.GetDatastore() you get back an object with type UnknownDatastore, which isn't especially useful). I hope this helps, --Rich
... View more
07-30-2020
10:04 AM
|
1
|
0
|
5318
|
| 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 |
Friday
|