|
POST
|
What product are you trying to connect to your license server?
... View more
08-28-2024
10:30 AM
|
0
|
0
|
557
|
|
POST
|
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
08-28-2024
10:26 AM
|
0
|
0
|
335
|
|
POST
|
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
08-28-2024
07:29 AM
|
0
|
2
|
1909
|
|
POST
|
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
08-28-2024
07:14 AM
|
0
|
3
|
1910
|
|
POST
|
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
08-27-2024
10:32 AM
|
0
|
5
|
1944
|
|
POST
|
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
08-26-2024
12:29 PM
|
0
|
7
|
1988
|
|
POST
|
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
08-26-2024
07:47 AM
|
0
|
9
|
2022
|
|
POST
|
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
08-23-2024
03:20 PM
|
2
|
1
|
939
|
|
POST
|
I upgraded to ArcGIS Pro 3.3.1 and the scale-based symbol classes are now working flawlessly. 🙄
... View more
07-31-2024
09:15 AM
|
2
|
0
|
608
|
|
POST
|
I'm trying to use scale-based symbol classes for the first time in ArcGIS Pro 3.1.3 and I'm experiencing very inconsistent results. I'm using unique value symbols based on a single field with no grouping of symbols. When I drag the left slider to set the outer limit scale and leave the right slider to None for inner scale, it seems to work for some of the symbols but not for others. I have not found any consistency or pattern in why some don't work. I've tried exporting to a file geodatabase and projecting to a different coordinate system, all with the same results: when zooming out beyond the scale set by the left slider, some of the symbols still show. I even had a coworker confirm the inconsistent behavior on a different computer.
... View more
07-30-2024
04:59 PM
|
0
|
2
|
665
|
|
POST
|
When it comes to Esri getting their money, I've found them to be helpful 😉 Are you able to log into My Esri to see the your organization? Under "Overview", "Esri Contacts", you should find contact information for a Customer Service Representative who should be able to assist you with transitioning your licenses.
... View more
07-09-2024
04:22 PM
|
0
|
0
|
1548
|
|
POST
|
Maybe this is a bug in how updateConnectionProperties() works on workspaces. I have had luck iterating over each layer rather than applying to the whole map. for layer in mymap.listLayers():
layer.updateConnectionProperties(
current_connection_info=r'C:\oldpath\database.gdb',
new_connection_info=r'C:\newpath\database.gdb',
ignore_case=True
)
... View more
07-09-2024
12:09 PM
|
1
|
0
|
1034
|
|
POST
|
The conditions are evaluated in order so put the most important one first and use elif for the other conditions. You'll also need to update the parameters in your function to accept Field2. # Expression
Reclass(!Field1!, !Field2!)
# Code Block
def Reclass(field1, field2):
if field2 == "y":
return "4"
elif field1=="x":
return "1"
elif field1 =="y":
return "2"
else:
return "3"
... View more
07-09-2024
10:58 AM
|
3
|
1
|
1118
|
|
POST
|
You can use an f-string to dynamically insert the field name into the calculate field expression. fields = arcpy.ListFields("perc_test_table")
for field in fields:
if field.name not in ['OBJECTID', 'Shape_Length', 'Shape_Area', 'SumField', 'Spatial_ID']:
arcpy.management.CalculateField(table, f"{field.name}_perc", f"!{field.name}!/!SumField!", "PYTHON3", field_type="DOUBLE")
... View more
07-01-2024
01:53 PM
|
1
|
0
|
955
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | 07-31-2025 11:59 AM | |
| 1 | 07-31-2025 09:12 AM | |
| 2 | 06-18-2025 03:00 PM | |
| 1 | 06-18-2025 02:50 PM |