Latest Contributions by HighKevin

‎07-23-2015

Yes, even on 10.3.1. However, it seems every once in a while the copy/paste of features will work without having to clear the features beforehand. This is pretty sporadic and I don't have an explanation as to why it does/doesn't happen. #3 on my list is related to NIM099678 - The Identify tool fails to identify SDEBINARY feat.., but has been logged as a new bug. "BUG-000088625: The Identify tool fails to identify SDEBINARY features if the joined table contains a nvarchar(max) field." Workaround: 1. Create a new nvarchar(1500) field, and use Field Calculator to populate the new field based on the original field. 2. Delete the original nvarchar(max) type field.

‎01-14-2015

I've been playing around with the 'US Address - Single House Subaddress' locator style in 10.3. I love it, but I'm running into an issue with "Hwy" vs "Highway". However, the 'US Address - Single House' style doesn't have a problem with this. My issue is that when I search for an address like "256 N Coast Hwy 101", the subaddress locator is not returning any results. The address layer has "Coast Highway 101" as the road name. If I search for "256 N Coast Highway 101", I get the proper results. It's breaking out "Coast Highway 101" correctly as the 'StreetName'. I noticed that the Single House locator will also return the correct results for "256 N Coast Hwy 101", but it breaks down "Coast Highway" as 'PreType' and "101" as 'StreetName'. I've opened up the xml files for each locator and they appear to have the same parameters. How can I get the Subaddress locator to treat "Coast Hwy 101" the way the Single House locator does? It would be great if I didn't have to use an alias table. Any thoughts or ideas would be greatly appreciated. Thanks! Kevin

‎01-09-2015

I have 10.3 DESKTOP (like the title of this topic says) installed and I'm having a lot of issues. Things I've noticed so far (off the top of my head): Editing Issues Copy and Pasting of features requires you to clear the selected features (the ones that have been copied) before you are able to paste them. Certain data paths will randomly say I can't edit them. If I close desktop and reopen the map, they'll work again. My custom Default Locators have disappeared in my maps. These appeared in my maps after installation, but today they are gone in every map, even after restarting. It won't identify my tax parcels. I have no idea why. An error symbol appears at the bottom of the identify window. I've never seen this before. Running on a 64-bit machine with WIN7. And don't get me started about ArcGIS Pro...haha.

‎06-30-2014

The solution I found came from a comment on that idea entry: "If you enable time on the layer before publishing, it will apply the UTC offset to yoru local time." I did this and it fixed the issue I was having with dates in AGOL.

‎06-02-2014

Contacted ESRI support about this and it turns out the issue was that the feature class was registered as versioned. I created a non-versioned copy in the same location and the tools worked great. I've now got a gameplan to make this happen. I hope this helps someone in the future. -Kevin EDIT: It's a bug that has been resolved in 10.2.1 - NIM073706 NIM073706: Running the Add Attachments geoprocessing tool returns the green warning message, "Cannot add file 'C:\student\seattletrips.jpg' to feature with OID = 1" when adding attachments to a target dataset that is registered as versioned. Version found: 10.1 The documented workarounds for the bug are - Workaround1: Run the tool on a file geodatabase then copy/paste back into sde. Workaround2: Make a copy of the feature class in sde and run the tool on the copy without registering it as versioned. Please keep in mind there are negative implications to unregistering a feature class as versioned. To minimize these, I would recommend taking a full, verified backup and compressing to a state 0 before unregistering the feature class as versioned and adding attachments. Below is a link to the resource center documentation which discusses unregistering the data as versioned. It mentions steps needed to carry out to prevent data loss when you unregister data as versioned.

‎05-27-2014

Hi there, I'm running into some problems when using the Attachments tools. We're assigning traffic signs of a certain MUTCD code a single image of what that sign looks like (e.g. all stop signs will have the same attachment, which is a picture of a stop sign). I'm testing out the Generate Attachment Match Table and Add Attachments tools, but can't seem to get the attachments to actually get to signs. Here are the details: I have a folder with the jpg image of the stop sign on my desktop. The name of the image is R1-1, which is the MUTCD code for stop signs. I have map open with only the sign feature class. Feature class is stored on SDE. I open up the Generate Attachment Match Table tool. Input Dataset is my feature class, Input Folder is the path to the folder I describe above, Output Match Table has been pointed to a file geodatabase on my desktop, and the key field is MUTCD. Store Relative Path is checked. I run the tool and the match table has the correct number of features for stop signs, with the features' OBID in the MatchID field and all records are pointed to the R1-1.jpg with the Filename field. I now open the Add Attachments tool. Input Dataset is my feature class, Input Join Field is OBJECTID, Match Table is the match table in my file geodatabase, Match Join Field is MatchID, and Match Path Field is Filename. Working Folder is pointing to the folder where R1-1.jpg is. When I run the tool, I'm seeing a message in the Results tab for each ObjectID in the match table that says something like, "Cannot add file 'C:\Users\khighland\Desktop\Test\R1-1.jpg' to feature with OID = 1571" But I don't understand why it's not allowing me to add the files. Does anyone have a clue why this is happening? Am I not allowed to assign a single attachment to multiple features, with the assumption it will copy the attachment x amount of times for however many features match this MUTCD? Using 10.1 SP1 with an Advanced license on a WIN7 PC with local admin rights. Any info/advice would be greatly appreciated. Kevin

‎02-06-2014

Steve - Were you using a wireless connection when it failed? I get the same message I'm connected to my City's public wireless network. It doesn't allow connections to our servers (where our basemaps are) for security reasons. Maybe this could be your issue? Changing your basemap should not break the story map. I hope this helps. Kevin

‎02-06-2014

Hi Mark, I've been noticing the same behavior with saving edits to the story map. We had a user who was trying to save and it would give him that same message (changes not saved, try again). What seemed to fix our issue was making the person who was editing it an administrator. He was previously had only publisher permissions, but since granting his AGOL account admin rights we haven't had a single problem with this. I hope this helps. Kevin

‎01-13-2014

I finally got it to work. When I changed the title field to use the full name of the field, everything seemed to sync up and work. Thanks for your help! Kevin

‎01-10-2014

Yes, all three of them work.

‎01-10-2014

Hi Robert, First of all - thank you so much for all your help over the years. You are an invaluable asset to the GIS community. I'm having an issue with the enhanced search widget. Every time I switch <fields all=" from "true" to "false", I get an error when I search on that layer that says [RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail=""] It works fine when I change it back to <fields all="true">. I want to use "false" because I would like to use the results in the data grid. Attached is my eSearchWidget.xml. My layer has a join on it, but I am using the correct field names. What am I missing? Thanks, Kevin EDIT: viewer version: 3.6, widget version 3.6.1.

‎10-04-2013

This might help others using MSSQL 2008. (Our problems revolved around very slow snapping, measure tool and any queries) The SQL Spatial types have impaired our performance greatly. When running the same problematic features as SDEBinary, in the same Dataset, our performance issues are gone. Is this a fix for all using MSSQL 2008? I can't say that for sure, but it definitely has made a big difference on our data. If you are running a similar setup. Simply copy and paste a feature into the same Dataset, and change the keyword to SDEBinary. If you don't see SDEBinary, you may be setup where the Binary option is your default. You could check DBTune to see the default "GEOMETRY_STORAGE", ours is set to "GEOMETRY". Good luck. We were having very poor performance since upgrading from 10.0 to 10.1 and this was the solution. An easy way to see your geometry storage type is to check the auto shape and length fields in a polygon feature class. If you are seeing "SHAPE.STArea()" and "SHAPE.STLength()" then you are using the SQL spatial type. The SDE Binary spatial type will show "Shape.area" and "Shape.length." I pulled copies of a few feature classes (duplicates, but one using SQL spatial and the other using SDE spatial) into an MXD and the difference between the two sets was staggering. Draw times with the SDE were four times faster than draw times with SQL. Snapping was not working with SQL, but worked perfectly with SDE. This is all on our publication database that is made up of handful of replicas. When we upgraded to 10.1, the default geometry storage type was change to SQL and then we recreated the entire pub database, so all feature classes were then using the SQL geometry. It only affected feature classes that were created since the upgrade. After making the changes Tesla described above and recreating the pub database, our problems disappeared! Hopefully this helps some of you.

‎09-19-2013

What works for me is selecting a random parcel and clicking "rejoin." This makes all of the radial lines on the map visible.

‎04-15-2013

bwragg- I ended up reverting back to the standard streets locator setup. supportsEmptyHouseNumber broke the results for specific locations on a street range. So "5 st name" would return the same results as "st name." What we told users who wanted to find the beginning of a street with just "st name" is to enter in the single street name twice, as if it's intersecting itself (which every segment actually is doing). For example "Encinitas Blvd & Encinitas Blvd" takes you to the beginning of the lowest range for Encinitas Blvd. This is my desired result for "Encinitas Blvd" when using supportsEmptyHouseNumber. Our users (not GIS-savvy) have seemed to grasp this "intersecting itself" concept and we no longer have the need for supportsEmptyHouseNumber. I hope this helps. Kevin

‎05-21-2012

Did not know that property existed. Seems to have done the trick. Thanks!

Online Status	Offline
Date Last Visited	‎10-30-2025 02:05 PM

My Ideas

Latest Contributions by HighKevin

Re: Any issues with ArcGIS Desktop 10.3?

Single House Subaddress - Not Recognizing "Hwy" as "Highway"

Re: Any issues with ArcGIS Desktop 10.3?

Re: Date field issue

Re: Trouble with Attachment Tools

Trouble with Attachment Tools

Re: Story Map Error - The application is not configured yet

Re: Issues with updating and saving

Re: Enhanced-Search-Widget-for-FlexViewer Part III

Re: Enhanced-Search-Widget-for-FlexViewer Part III

Re: Enhanced-Search-Widget-for-FlexViewer Part III

Re: Issue with snapping and performance speed

Re: Where are these points coming from?

Re: "US Streets" Style Locator in 10?

Re: "US Streets" Style Locator in 10?

Re: URL parameter (Feature parameter) configured i...

Re: ArcMap opening on wrong monitor

Re: Tour Map Not Saving with Links

Re: Single Choice Grid access in Field App

Linking to a Specific Point in Tour Map that is Em...

GIS Manager's Group