Latest Contributions by BlakeTerhune

I also got this error in ArcGIS Pro 3.3.1 when trying to load all 139,396 rows in the attribute table of a feature class in a 10.8.1 enterprise geodatabase running on Oracle 19c. Failed to retrieve a page of rows. The event class for this subscription is in an invalid partition (0x8004020F) After clicking OK on the error, the attribute table closes. Trying again yields the same result. ... View more

@Wei_Ying  I'm attempting to use the Feature Info widget as a replacement for the regular pop-up. When I add multiple layers and click on the map, the Feature Info widget only includes content for the first one highlighted instead of everything from the hit test of the click (like the pop-up does). Is there a way to get the Feature Info widget to display pop-up content from all the configured layers at once (like the pop-up does)? ... View more

My first attempt to work with the query and filter widgets was to implement a way for the user to build their own SQL. The app I'm building has many layers that have different ways to search so it's not reasonable to build out every combination of SQL statements. Using the Search widget is not reasonable because the users need to specify more complex logic with AND/OR operators. Please consider adding this functionality in Experience Builder. ... View more

I have noticed this too. @Jianxia, can you confirm if this is expected behavior in Experience Builder? ... View more

I would support the idea proposed by @AlfredBaldenweck. I think the idea is not to propose functionality that isn't possible, but rather to have the list functions follow a similar pattern to most other functions and have a parameter to explicitly set the workspace. It feels odd that you need to use arcpy.env.workspace (primarily) only when dealing with a list function, but not for most other things. ... View more

What product are you trying to connect to your license server? ... View more

Creating a circle line feature in Pro (3.3.1) exports to this Esri JSON: { "displayFieldName" : "", "fieldAliases" : { "OBJECTID" : "OBJECTID", "Shape_Length" : "Shape_Length", "MyCustomField" : "MyCustomField" }, "geometryType" : "esriGeometryPolyline", "spatialReference" : { "wkid" : 3008, "latestWkid" : 3008 }, "fields" : [ { "name" : "OBJECTID", "type" : "esriFieldTypeOID", "alias" : "OBJECTID" }, { "name" : "Shape_Length", "type" : "esriFieldTypeDouble", "alias" : "Shape_Length" }, { "name" : "MyCustomField", "type" : "esriFieldTypeString", "alias" : "MyCustomField", "length" : 255 } ], "features" : [{"attributes":{"OBJECTID":3,"Shape_Length":37416.412812405986,"MyCustomField":null},"geometry":{"curvePaths":[[[409829.45079999976,6584678.9290999994],{"a":[[409829.45079999976,6584678.9290999994],[404882.20972270775,6587993.5806217846],0,1]}]]}}] } Creating an ellipse line feature in Pro (3.3.1) export to this Esri JSON: { "displayFieldName" : "", "fieldAliases" : { "OBJECTID" : "OBJECTID", "Shape_Length" : "Shape_Length", "MyCustomField" : "MyCustomField" }, "geometryType" : "esriGeometryPolyline", "spatialReference" : { "wkid" : 3008, "latestWkid" : 3008 }, "fields" : [ { "name" : "OBJECTID", "type" : "esriFieldTypeOID", "alias" : "OBJECTID" }, { "name" : "Shape_Length", "type" : "esriFieldTypeDouble", "alias" : "Shape_Length" }, { "name" : "MyCustomField", "type" : "esriFieldTypeString", "alias" : "MyCustomField", "length" : 255 } ], "features" : [{"attributes":{"OBJECTID":4,"Shape_Length":43604.943501478185,"MyCustomField":null},"geometry":{"curvePaths":[[[399919.55800000019,6592293.0635000002],{"a":[[399919.55800000019,6592293.0635000002],[403892.76152614655,6591110.3424503561],0,1,1.2814744564857963,9244.3980018598413,0.44843380967153262]}]]}}] } ... View more

If you don't choose the "Output to GeoJSON" option and let it make "Esri JSON", it preserves the true curves. Here's a full example to test with a FeatureSet. { "displayFieldName" : "", "fieldAliases" : { "OBJECTID" : "OBJECTID", "Shape_Length" : "Shape_Length", "MyCustomField" : "MyCustomField" }, "geometryType" : "esriGeometryPolyline", "spatialReference" : { "wkid" : 3008, "latestWkid" : 3008 }, "fields" : [ { "name" : "OBJECTID", "type" : "esriFieldTypeOID", "alias" : "OBJECTID" }, { "name" : "Shape_Length", "type" : "esriFieldTypeDouble", "alias" : "Shape_Length" }, { "name" : "MyCustomField", "type" : "esriFieldTypeString", "alias" : "MyCustomField", "length" : 255 } ], "features" : [{"attributes":{"OBJECTID":2,"Shape_Length":21456.640390208202,"MyCustomField":"my value"},"geometry":{"curvePaths":[[[258018.72869999986,6677229.8190000001],{"c":[[268339.47780000046,6681063.2401000001],[260595.32177711991,6686102.864274309]]}]]}}] } ... View more

Using the Features to JSON gp tool and choosing the "Output to GeoJSON" option creates a file with .geojson extension. I just tested and I got fully completed JSON. Herer's an abbreviated example.   {"type":"FeatureCollection","crs":{"type":"name","properties":{"name":"EPSG:3008"}},"features": [{ "type":"Feature","id":1,"geometry":{ "type":"LineString","coordinates":[ [235902.8376000002,6695217.4102999996], [235915.07869883571,6695060.7613401897], ... SNIP ... [235928.1163439769,6694904.1766636735], [218505.00329999998,6689909.5965] ] }, "properties":{ "OBJECTID":1, "Shape_Length":401574.90631927003, "MyCustomField":"a value here" } }] }    The JSON you posted is all empty. It should have values. EDIT: I just noticed that Feature to JSON is simplifying the geometry into straight line segments instead of a curve. Sorry. ... View more

Have you tried loading the JSON into a FeatureSet and copying it to a new feature class like the original solution suggested? fs = arcpy.FeatureSet() fs.load(r'C:\path_to_your_json_file.json') arcpy.management.CopyFeatures(fs, r'C:\some_folder\test_workspace.gdb') ... View more

Yes, you can use the same method for creating regular (non-curve) polyline features. As for how to construct your GeoJSON, I don't have experience doing that with curves. I recommend reading the documentation. For practice, you can manually create sample features (with curves) in ArcGIS Pro, then export them to GeoJSON to see how the structure changes for different geometries. ... View more

It looks like the geometry object in arcpy does not support the creation of true curves. Any true curves in the geometry will be densified into approximate curves in the WKT string. A possible workaround seems to be to create your feature as GeoJSON and load it in a FeatureSet, then copy the features. ... View more

We store our raster images on a network file storage drive. The folder data store allows us to serve the imagery directly from a mosaic dataset in a file geodatabase on the network drive. ... View more

I upgraded to ArcGIS Pro 3.3.1 and the scale-based symbol classes are now working flawlessly. 🙄 ... View more