Latest Contributions by AlexTurner

‎04-09-2015

Turns out the model only allows short integer values for the store attractiveness fields. I changed the field I was using to short integer and now it works.

‎04-01-2015

I am trying to to run the Huff model calibration tool but keep getting this error: ERROR 080001: Function does not accept floating point Not-a-Number values. Failed to execute (HuffModelCalibrationByRealData). I am using geocoded points as my customer locations with a zip code layer as the geography. I thought it might be a problem with unmatched points but even once I removed those it still gave the same error. I also tried changing my store ID fields from double to integer. Does anyone know what this error means and how to fix it? There are no NULL values in any of the fields I am using as inputs.

‎08-25-2014

I am running Optimized Hot Spot Analysis on data that shows a percent change between two years. I have multiple fields that I am running it on. However one of my fields keeps returning "ERROR 000906: Zero Variance: All of the values for your input are likely the same." However, the values in this field are not all the same, they range from -1 to 75, although 75 is an outlier and most of data is from -1 to 1. I thought maybe the negative and positive values were canceling each other out so I added 1 to each value so they were all positive but it still returned same result. Any idea why this is happening and is there a way to fix it? Thanks.

‎07-23-2014

The symbology classification in Data Driven Pages should be able to change with each page so that each map can have custom ranges that more accurately show the data. For example one location may have values ranging from 0-10 while another location may have values ranging from 100-200. I wouldn't want these two areas to be using the same symbology classification.

‎07-23-2014

I am creating a Data Driven Pages Map Document that creates maps for store locations and their respective sales by zip code. However the stores have a wide variance in sales and I am wanting to have a different classification for each page so it better suits each store's market. Is there a way to have the classification and legend change dynamically based on the page? I am already using page definitions to show only sales for each store but I do not see a way to update classification and ranges by store.

‎06-24-2014

I am trying to use python to upload service definitions when they are changed and overwrite the existing ones already on ArcGIS online. I am able to sign in through python, but then when I upload the service definition I get an error that Service Name 'Name of my layer' already exists for 'j1vNyYVuxczZ499i' Failed to execute (UploadServiceDefinition) It didn't look like there was a parameter in the tool description that turned on or off overwriting, unless I misread. How would I go about overwriting the existing service definition with the new one?

‎06-19-2014

Well, the points are finally adding to the table and showing up in the map but they are not in the correct places. I think ArcMap is reading the Lat/Long values I am putting in as coordinate values. I have tried putting it in Lat first and Long first, neither works. Is there a simple way to make sure they are read as Lat/Long or to convert them to coordinate values? EDIT: When I pull up the Identify window and look at the location field the values for Decimal Degree, which is where Lat/Long would be are -0.000835 0.000305 The values I put in were -93 and 34 Under kilometers the values were -0.093 0.034. I am not sure if that helps clarify anything but I am lost as to where to go now EDIT2: So I noticed that one of my tables actually placed the point in the correct location, but the other one didnt. However they have the same code. The future table is the one that is not working and places the point using the values above. The All table places the point perfectly. The two codes look identical, am I missing something? #Insert new row into Future table with arcpy.da.InsertCursor(Future, ["SHAPE@XY", StNameField, StNameSortField, StAbbrField, StatusField, StNumField, SqFtField, AddrField, CityField, StateField, PostalField, PhoneField, LatField, LongField, OpenField]) as cursor: cursor.insertRow(((float(Long), float(Lat)), StName, StNameSort, StAbbr, Status, StNum, SqFt, Addr, City, State, Postal, Phone, Lat, Long, Open)) del cursor #Insert new row into All table with arcpy.da.InsertCursor(All, ["SHAPE@XY", StNameField, StNameSortField, StAbbrField, StatusField, StNumField, SqFtField, AddrField, CityField, StateField, PostalField, PhoneField, LatField, LongField, OpenField]) as cursor: cursor.insertRow(((float(Long), float(Lat)), StName, StNameSort, StAbbr, Status, StNum, SqFt, Addr, City, State, Postal, Phone, Lat, Long, Open)) del cursor

‎06-18-2014

I tried your solution as you can see below but I received the same error. The error message identified line 50 which is the "cursor.insertRow..." line. #If/Then to update correct tables based on Status if Status == "Current": #Inserts new row into Current Locations table with arcpy.da.InsertCursor(Current, ["SHAPE@XY", StNameField, StNameSortField, StAbbrField, StatusField, StNumField, SqFtField, AddrField, CityField, StateField, PostalField, PhoneField, LatField, LongField, OpenField]) as cursor: cursor.insertRow(((Lat, Long), StName, StNameSort, StAbbr, Status, StNum, SqFt, Addr, City, State, Postal, Phone, Lat, Long, Open)) del cursor

‎06-18-2014

I am trying to create a custom tool to take user input about point locations and add them into an existing feature class that already contains points that have been located using their Lat/Long values. I set up multiple arcpy.getparameterastext() such as name, size, etc. Latitude and Longitude are also point values, however when I enter everything in and run the tool I get this error...TypeError: expect single [X,Y[,Z[,M]]] I assume it has something to do with setting up the XY coordinates but I am not sure how to fix this. It is probably something simple I am just not finding. Does anyone know how to fix this?

‎02-11-2014

I am running an accessibility analysis for my thesis work but I am having trouble with accessing the Lines sub-layer after I solve the OD Cost Matrix. I need to be able to work with the Lines sub-layer to move forward in my analysis. I have tried select tool and copy features and it always comes back with an error that the Dataset Lines does not exist or is not supported. Does anyone know a way to fix this? Ideally I would like to export as its own layer or a shapefile. Here is the network analyst part of my code if that helps. ODMatrix = arcpy.MakeODCostMatrixLayer_na(Network, "Travel","TravelTime", 30) #Get the layer object from the result object. The OD cost matrix layer can #now be referenced using the layer object. ODMatrix = ODMatrix.getOutput(0) #Get the names of all the sublayers within the OD cost matrix layer. subLayerNames = arcpy.na.GetNAClassNames(ODMatrix) #Stores the layer names that we will use later originsLayerName = subLayerNames["Origins"] destinationsLayerName = subLayerNames["Destinations"] lines = subLayerNames["ODLines"] #Load the census tract locations as origins arcpy.na.AddLocations(ODMatrix, originsLayerName, CTPoint) #Load the physician locations as destinations arcpy.na.AddLocations(ODMatrix, destinationsLayerName, Physicians) #Solve OD Cost Matrix arcpy.na.Solve(ODMatrix)

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by AlexTurner

Re: Huff Model Calibration by Real Data error

Huff Model Calibration by Real Data error

Hot Spot Analysis Zero Variance Error

Dynamic Symbology Classification Ranges in Data Driven Pages

Symbology Classification in Data Driven Pages

Uploading a service definition and overwriting the existing one

Re: Adding Point to Feature Class that has been created using Lat/Long and XY tool

Re: Adding Point to Feature Class that has been created using Lat/Long and XY tool

Adding Point to Feature Class that has been created using Lat/Long and XY tool

Problems Accessing Lines sub-layer of OD Cost Matrix Result

Dynamic Symbology Classification Ranges in Data Dr...