|
POST
|
You likely just need a return statement. Myscript() Return outputpath
... View more
02-14-2020
02:39 PM
|
0
|
1
|
4389
|
|
POST
|
You could add the xls as a gdb table then use search and update cursors to do the calculations.
... View more
02-14-2020
01:51 PM
|
0
|
10
|
2681
|
|
POST
|
Theres a tool called Add X Y Coordinates, running this on your current feature will give you their true locations in new fields to your table. Then run Table to Excel to export the current table to a spreadsheet, at least then you dont have to recreate all the coordinates and can add in new rows easily. When done, add the sheet back in thru Add X Y data.
... View more
02-14-2020
11:12 AM
|
1
|
2
|
3933
|
|
POST
|
Hi Stephen, There is often alot of confusion with tables which hold lat long figures. A table can exist but hold no geospatial location. Changing these values in the table will not create or update the location of points. You need to add the table as xy data, then save it as a feature class or shapefile. Search for adding xy data in the help files or Google and you will find a trove of info.
... View more
02-14-2020
10:44 AM
|
0
|
4
|
3933
|
|
POST
|
As Dan suggests, a table join would achieve this. You could also use a search cursor to append matching values to an empty list and then use select by attribute on the FL. E.g. object_id_list = [1,2,3] query = "OBJECTID in (1,2,3)" Selectbyattribute(...
... View more
02-14-2020
07:56 AM
|
0
|
0
|
3254
|
|
POST
|
I think the mxd needs to be in the datastore as you're setting the workspace then using list layers I guess?
... View more
02-14-2020
07:27 AM
|
0
|
0
|
2786
|
|
POST
|
Is the mxd in the data store and the data referenced in the mxd through a full network path?
... View more
02-14-2020
07:17 AM
|
0
|
2
|
2786
|
|
POST
|
Other than setting the display to nearest neighbour I dont know. Would be good to find out if and when you solve it. Good luck!
... View more
02-13-2020
11:59 AM
|
0
|
0
|
3112
|
|
POST
|
Could be a DRA issue? Are they all set to the same symbology?
... View more
02-13-2020
10:11 AM
|
0
|
0
|
3112
|
|
POST
|
Hi Kathy. Date fields are python datetime objects which can be handy. Field 1 - Field 2 produces a TimeDelta object. TimeDelta.total_seconds() will produce the number of seconds of the timedelta object. I believe the timedelta will take into account leap years so the result may be off several days from what you may expect. Total_seconds = (TimeField1 - TimeField2).total_seconds() SecInYear = (60*60*24*365.25) Years = Total_seconds/SecInYear This is very basic and prone to error. Hopefully someone can give a better answer
... View more
02-10-2020
02:24 PM
|
2
|
0
|
3099
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-13-2025 01:08 PM | |
| 1 | 09-25-2025 03:19 PM | |
| 1 | 09-24-2025 02:35 PM | |
| 1 | 09-17-2025 02:42 PM | |
| 1 | 09-10-2025 02:35 PM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|