Latest Contributions by KevinHighland

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 ... View more

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 ... View more

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 ... View more

Yes, all three of them work. ... View more

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. ... View more

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. ... View more

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

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 ... View more

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

These aren't out of the box in 10. If you have a "full address" field for your address layer that spells out the information for units and apartment blocks (ex: 335 Santa Fe Dr A), you can create a 'General - Single Field' locator around this field and it should work fine. ... View more

Make sure that the "SHAPE" field is turned on on your line feature class! ... View more

The popups only identify the top-most layer that is being displayed. So even though your symbology for the boundaries (feature layers) may be hollow or transparent, these features are blocking your popups from identifying the dynamic layers. That's why they don't work when your feature layers are turned on. One way I've worked around this is to use the rsheitlin Identify Widget. You set which layers to identify and it will return all the results it encounters, not just the top-most. You can download it here: http://www.arcgis.com/home/item.html?id=39cf66d58c234279ba728c50461a1a89 ... View more

Robert, Thanks again for all of your help! This is perfect. ... View more