POST
|
09-06-2016
04:13 PM
|
0
|
0
|
1077
|
POST
|
I have an atlas index grid that I label with the Boundary Placement option in Maplex. In ArcGIS 10.2.2 the horizontal label on the bottom of a polygon would label properly (right side up). However I have noticed that in 10.3.1 the label is now upside down. (See PAGE25 label in the image) My thought is that the Boundary Placement option is now generating labels that always orient their "top" to be along the polygon edge. I had to have someone who still has 10.2.2 export all of our maps. I looked around the forums and couldn't find anyone else reporting this. Has anyone else experienced this? If so is there a setting to get them to orient right-side up? Thanks
... View more
03-03-2016
12:02 PM
|
0
|
1
|
1626
|
POST
|
This is a duplicate thread to this one in the Geoprocessing forum.
... View more
08-05-2013
03:46 PM
|
0
|
0
|
232
|
POST
|
I believe that Arc 10 supports Visual Studio Express 2008 and 10.1 supports Visual Studio Express 2010.
... View more
07-10-2013
10:15 AM
|
0
|
0
|
266
|
POST
|
I'm not sure what your code is but sys.argv starts at 1 whereas getparameter starts at 0. So when you are assigning the input parameters your first sys.argv should be 1 and so on. Please post your code if this is not your issue. Joel
... View more
05-14-2013
11:25 AM
|
0
|
0
|
528
|
POST
|
I've never used ExtractByAttributes but after a quick scan of the help you could maybe try something like this:
# Import system modules
import arcpy, os
from arcpy import env
from arcpy.sa import *
env.workspace = r"C:\rasters" # Whatever your workspace is
outPath = r"C:\RasterExtracts" #Output Location for your raster attribute extract
i = 1111 # Moved this outside the loop so you don't get an infinite loop
while i < 111101:
sqlClause = "Value = " + str(i)
outRaster = ExtractByAttributes("Fac", sqlClause)
outRaster.save(outPath + os.sep + "Fac" + str(i))
i += 1111 You have "fac" and "Fac" in your code. Python will treat these differently. My understanding is that "fac" is just a string you want as part of the output file name. Is "Fac" with the capital letter the name of your input raster? In my code sample I just made the both caps because I am unsure what your input data is.
... View more
05-02-2013
12:55 PM
|
0
|
0
|
578
|
POST
|
Craig, I don't think it's a good practice to use the pageID to label your exported images since the pageID is an internal index value and my not represent what you think it does. Here is the note from the help: getPageIDFromName (page_name) Parameter Explanation Data Type page_name A value in the index layer that corresponds to the Name field that was used to set up Data Driven Pages String Many of the Data Driven Pages properties and methods use an internal index value rather than the literal names of the pages used to create the index layer. The index values are automatically generated based on the Name and Sort fields. It may not be obvious which index value represents a specific page. The getPageIDFromName method provides a mechanism for this translation. pageID = mxd.dataDrivenPages.getPageIDFromName("HarborView") mxd.dataDrivenPages.currentPageID = pageID In my example I pulled the parcel number straight from the table for the current page which I think is what he wanted to use as the image name but I didn't notice that JPEG was a separate folder name so that was a good catch.
... View more
04-10-2013
11:30 AM
|
0
|
0
|
569
|
POST
|
I upgraded from 10.0 to 10.1 on the same machine not a new machine with a completely new ArcGIS install. And like I said it only started when I installed the 64-bit background geoprocessing service pack. Joel
... View more
04-10-2013
11:18 AM
|
0
|
0
|
550
|
POST
|
This is and excerpt from the help for Generate Near Table: �?�The distances calculated by this tool are in the unit of the coordinate system of the input features. If your input is in a geographic coordinate system and you want output distances to be measured in a linear unit (as opposed to decimal degrees), you must first project your input to a projected coordinate system using the Project tool. For best results, use an equidistant projection or a projection intended for your study area (UTM, for example).
... View more
04-08-2013
12:30 PM
|
0
|
0
|
657
|
POST
|
Ken, It has been a while since I've tried to figure out this issue and I believe our IT department did call ESRI support but I cannot recall what exactly they were told to try but I do remember that whatever they suggested did not appear to fix my issue. It seems that those that have posted here might have slightly different issues but all seem related to background geoprocessing. Here are my details: - I have an Advanced floating license - I do not believe our licenses were or are near expiring - The error only occured when I had the 64-bit BG geoprocessing update installed AND BG geoprocessing enabled. I think it was fine with foreground processing but I'm not 100% sure. When I uninstalled the 64-bit BG geoprocessing service pack, everything was fine and I was able to successfully run geoprocessing operations again in the background. - This appeared to be an issue for all geoprocessing tools - The only other ESRI application I had installed was ArcExplorer Desktop We are currently finishing up a large migration project and are running several large geoprocessing operations so for the foreseeable future will not be able to reinstall the 64-bit BG geoprocessing service pack to try any further testing. Perhaps in a couple months things will be settled down and I can test it again. If you have any other questions let me know, Thanks, Joel
... View more
04-08-2013
11:45 AM
|
0
|
0
|
550
|
POST
|
Without seeing how your DDP is actually set up I can't be sure but you could try something like this: import arcpy
mxd = arcpy.mapping.MapDocument("CURRENT")
for pageNum in range(1, mxd.dataDrivenPages.pageCount + 1):
mxd.dataDrivenPages.currentPageID = pageNum
fieldValue = mxd.dataDrivenPages.pageRow.PARCEL_NO
fieldValue = str(fieldValue)
arcpy.mapping.ExportToJPEG(mxd, r"P:\Township Maps\Bloomingdale\JPEG" + fieldValue + ".jpeg", resolution=100)
del mxd
... View more
04-05-2013
11:26 AM
|
0
|
1
|
569
|
POST
|
Dale, thanks for the info on the FIDSet, it was most helpful. Steve, I think what Dale has provided makes testing the Feature Class itself unnecessary. If len(d.FIDSet) > 0 then you have selected records. Also using this you can find the number of selected records. Something like this: import arcpy
# Import strftime from time module
from time import strftime
lyr = "Parcels_Layer"
# MESSAGES FUNCTION
def messages(message):
arcpy.AddMessage(strftime("%m-%d-%Y %I:%M:%S %p ") + str(message))
print(strftime("%m-%d-%Y %I:%M:%S %p ") + str(message))
d = arcpy.Describe(lyr)
if len(d.FIDSet) > 0:
Feat_Sel_List = d.FIDSet.split(";")
messages(len(Feat_Sel_List))
... View more
04-04-2013
02:01 PM
|
0
|
0
|
435
|
POST
|
From what I've read is that if you use a script tool or I'm assuming a python add-in within ArcMap, it will automatically honor your selected set. I'm not sure of the best way to determine if there is a selection but one thought is that you could run a couple of search cursors. The first one will give you the number of records in the input layer or if there is a selection, just the number of selected records. The second would be on the Feature Class. Compare the two counts. If the layer has less then you know you have selected records. Completely untested but maybe something like this:
import arcpy
# SET THE LAYER
lyr = "Parcel_Poly"
# SET THE FEATURE CLASS
fc = "C:\\parcels.gdb\\parcels"
# SEARCH THE LAYER
lyr_rows = arcpy.da.SearchCursor(lyr, "PIN")
lyr_Count = 0
for lyr_row in lyr_rows:
lyr_Count += 1
del lyr_row, lyr_rows
# SEARCH THE FC
fc_rows = arcpy.da.SearchCursor(fc, "PIN")
fc_Count = 0
for fc_row in fc_rows:
fc_Count += 1
del fc_row, fc_rows
if lyr_Count == fc_Count:
#Do Something
... View more
04-03-2013
11:07 AM
|
0
|
0
|
435
|
POST
|
If you have an "Advanced" license level you could take a look at the Generate Near Table tool. Just a note from the help: �?�Both Input Features and Near Features can be the same dataset. In that case, when the input and near features are the same record, that result will be skipped so as not to report that each feature is 0 units from itself. �?�The input features can be a layer on which you have performed a selection. The selected features will be used and updated during the execution of the tool. The remaining features will have the values of the newly created fields (such as NEAR_FID and NEAR_DIST) set to -1. I hope this points you in the right direction.
... View more
04-03-2013
10:21 AM
|
2
|
0
|
1965
|
POST
|
I am also struggling with the edit state. If I start editing and run my tool I get this message: The requested operation is invalid on a closed state. If I make at least one edit, I can run the tool just fine. I have been experiencing this problem too. I tried starting an edit session with Python first but that didn't seem to work either. I am very interested in a solution to this problem.
... View more
04-03-2013
09:28 AM
|
0
|
0
|
366
|
Title | Kudos | Posted |
---|---|---|
2 | 04-03-2013 10:21 AM | |
1 | 07-22-2010 12:15 PM | |
1 | 12-02-2011 08:38 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|