Latest Contributions by BrianOevermann

Matt, Aren't all of the responses to this thread the "feedback"?  To be sure, it isn't a nice, tidy list but all of the requests are there.  At the very least, I see the common thread of "all of the widgets Robert produced for the Flex Viewer" with some additions. ... View more

Robert, 1. enhanced search 2. identify 3. basemap fader/switcher 4. draw/measure 5. related records 6. street view Like others, I would be consuming REST services directly from my own server and not via AGOL webmap/Portal.  For the basemap switcher I need it to recognize my cached map services that are in our State Plane projection. The AGOL basemap switcher doesn't seem to recognize my published basemap services as basemaps.  But maybe I am missing something simple regarding that. ... View more

Dan, The formula syntax to use depends on your source data.  See this blog post and the user comments for more info: http://mappingcenter.esri.com/index.cfm?fa=ask.answers&q=533‌ I don't recall if the contour layer in the LGIM has fields set up for coding index contours, but if not, create fields of short integer type based upon the index intervals you want to use.  Then use the formula in the link above to select those contours that fit that interval, then code the index field with a value of "1" to indicate the particular contour line is an index contour. Otherwise the field has a value of "0". For example, I have fields set up in our 2 ft. contour layer for 50 ft. and 100 ft. index contours.  If I want to show 50 ft. index contours, I copy/paste the contour layer and write a definition query where Index50 = 1 (Index50 is my field name), then symbolize it as an index contour and label that layer only. ... View more

Kathleen, I would subscribe to an "add to the model only" method and not delete anything--at least until you become familiar with the various applications and what fields they are using.  Your concern is valid and you don't want to paint yourself into a corner unnecessarily! You can hide fields by unchecking them in the layer properties within ArcMap.  That may or may not have consequences with the apps you want to use, however. ... View more

Josh, Looking at your attached graphic, that toolbar is the "standard" geocoding toolbar included in ArcMap.  Right-click on a blank area of the toolbar/menu and you can turn on/off various toolbars, including 'Geocoding'.  You can also access the same list via the Customize-->Toolbars menu. That said, your original issue is that nothing is found when you type in an address.  The toolbar defaults to the World Geocode Service (ArcGIS Online).  Is it possible that this address is not captured by the data that locator is built from?  I ignore that locator and instead use the locators built against our data.  You can drop down the left-most list in the toolbar and select "<Manage Address Locators...>" and select your own locator(s) to choose from. After another look at your graphic it appears that you are pointing it to a different locator than the default, so maybe what I wrote above is info you are well-informed about.  When was the last time that locator got rebuilt?  If the address shown in the graphic is a new addition to your streets data, a match may not be found until you rebuild the locator's indexes.  Also, is the locator set up to need a city/state/zipcode? That may be another reason for no results being found.  As for the Windows sound, I've never come across that.  If the locator doesn't find a match it simply indicates that in a tooltip--at least in my experience. I don't have the Address Management add-in installed.  Since you mentioned that you do have it installed, maybe there is some conflict between the add-in and the "regular" geocoding toolbar (i.e. either a bug or by design). ... View more

Emily, Your unit (and dir) fields are still not truly null--you have just eliminated the spaces.  If they are truly null they will look like the attached screenshot.  There are multiple ways you can accomplish this, but if there is only a space (or a "blank") I have found that I need to add some actual characters (i.e. asdf), commit them, then select that new value and hit delete on the keyboard.  This is via the attributes window when editing.  Hopefully I have described it well enough for you to get the idea. That said, when I did actually null your unit field, I was still unable to get the locator to properly find a match.  I didn't exhaust all of the possible reasons/causes because I simply don't have time to do that level of troubleshooting for you.  I still think it has something to do with how your data is formatted but I am unsure exactly what that might be.  Your data does not have all of the same fields as mine, but when you set up the locator and specify the fields to be used it should be using only those fields for matching (from what I understand about the process). You are the first person that seems to have this issue with the locator, or at least the first person to raise the question.  Maybe others have simply abandoned it without saying anything.  Regardless, I can tell you that my locator finds single family addresses as well as those with units.  My users wouldn't be happy with me otherwise! You can see it actually working via our current 'placeholder' (until I can build more focused viewers) public viewer on our website at: http://products.issaquahwa.gov/GISviewer/index.html Sample addresses are: 130 e sunset way = our main City Hall, but equivalent to a single-family address without a unit 360 nw dogwood st unit r201 = address with unit. For matching purposes you can even leave off the 'unit' and only type the 'r201' Full disclosure: the viewer is actually running a composite locator made up of: single house with unit, US Address (streets), and single-field input, in that order. If you type in a proper address it should locate it to the site address point using the single house with unit locator. Also note that capitalization is not necessary. You might try digging up Brad's (from esri) version of a unit-based locator and see if you have better luck.  You mentioned in a previous post that the "regular" SingleHouse locator worked.  That is to be expected because the way that locator is built ignores information regarding units--it knows nothing about them.  So I would expect that the locator would work well with addresses without units as well as those with units. But for those with units, the locator is only matching the base address. ... View more

Emily, I will answer your latest question and then comment on the testing I have done with your data... Re: batch geocoding with a table that contains the unit in a separate column from the address - To my knowledge the entire address to be matched must be in a single column.  I don't batch geocode often, but I seem to recall only being able to specify one field/column that contains the address to be matched.  Someone please correct me if I am misinformed! Re: testing [apologies for the length] So... I added your data to a new ArcMap project, then added your locator built with the style file I uploaded to the forum to ArcMap via the Geocoding toolbar.  I used your AddressTable table to inform me of sample addresses and typed an address containing a unit as well as an address without a unit and got the same results you indicated--those addresses without units were not found. I closed ArcMap and then created a brand new locator against your address point data.  My thought was maybe the upload got corrupted somehow and using the locator style that is on my system (that I successfully create locators with) could confirm that possibility.  After loading the new locator into ArcMap in the same way described above, my results were still the same. I next took a closer look at your data.  Within the unit field, if an address does not have a unit associated with it, the field is populated with a 'space'.  In the unique values list within the 'select by attributes' dialog it looks like: ' ' .  A space as a value is not the same as a NULL value, and I suspect that might be the reason for the failed address match.  In an attempt to confirm that, I edited your data to null the unit field.  The most that would do is change the value in the unique values list to: '' .  That also is not the same as NULL.  Typically the result of nulling the field is an entry of NULL, so I started looking at your feature class schema. For your UNIT field (and for your DIR field as well) you have the field set to NOT allow NULL values, which is why I was not able to completely NULL the field.  You likely have a sound business reason for disallowing NULL values on these fields, but general best practices are that you only disallow NULLs when you absolutely require something to be filled in that field.  For street directionals and units, you may or may not have a value.  That is why I found spaces as values--a user must put something in the field.  And while a space is not equal to NULL, it IS a valid value that satisfies the field not being NULL (and the field otherwise looks blank). All of that said, I think that if you recreate your feature class and set the DIR and UNIT fields to allow NULLs, you will find success with the address matching.  If your business rules require those fields to not have NULLs then you are likely stuck.  You may want to test it so that you can make a sound business case to change the rules accordingly. You should be able to import your fields from the existing layer and make the required changes before completing the creation of the new feature class, then use the simple data loader to load all of your features from the old to the new.  You will need to then NULL those two fields where a value does not exist.  At that point, re-create your locator--you could try rebuilding the existing one but why take the chance--and attempt your address match again. I hope this all makes sense... ... View more

Emily, That is strange, as I have no issues locating addresses that do not have a unit/suite associated.  I'll compare your data schema with mine--maybe there's a slight difference? I'll work in a test for you but likely won't have a chance until tomorrow. ... View more

Patrick, My version of the style hasn't changed, so the file available on other threads is still valid.  Regardless, it is attached for your convenience.  At this writing my organization is using 10.2. ... View more

I've had hit and miss luck with legends in my print templates.  It seems to work better if you have a core set of layers that you are making available to your users.  That said... You might try creating a legend "window" in your layout that spans the entire white space that you appear to have available for your legend.  You also should set, in the legend properties, more than just a single column for the legend.  The legend properties, by default, is a single column.  You will want to experiment with the number of columns.  I found that it worked better when I put in way more columns than I thought were feasible for the space I allocated to the legend (i.e. I thought no more than 5 or 6 columns would fit but I set it to 10 columns (just an example)).  Designating the number of columns seemed to work better when I was initially setting up the legend, and less so when I attempted to tweak the legend options later. The other big tip--and you didn't mention this so you may already have this covered--is to leverage all of the legend options available to maximize the ability of the system to generate a readable legend that fits on the map.  You should go into the Items tab in the properties and check the box for each available layer to only show the features that are in the current extent.  This will eliminate any legend patches of features that don't exist in the current view.  This is a big help with, for example, a zoning map that is zoomed in to only show a small area where only a few different zones are present.  You don't need the legend to show every zone within the City/County in that context. You should also play around with the word wrapping functionality.  You can set a maximum length for a legend entry and have it wrap to a new line.  For example, if you have a feature that is titled "Sites within project area greater than 5 acres" the word wrapping function will split that title into 2 or more lines.  Along with your column setup, this can maximize the layout of the legend. There are a few other options in the legend properties that you can tweak to get the most out of your legend.  These tips really are useful for all of your maps.  If you have set up your templates in a folder that is registered on the server instead of having your layouts copied to the server, maintenance of your templates is really easy (as well as adding additional templates later).  I suggest creating a test layout template, and within the flex viewer add a bunch of layers to your map (many more than logical) and see what the print result is.  From there expand columns, etc. until it starts looking like you want it.  With the dynamic nature of the templates you really need to play a bit to see where it might break, unless you really constrain your users with the data available. ... View more

Emily, I can confirm that the style I've uploaded--that contains a field for the fractional portion of the address--works at 10.2.  I would expect that the style that Brad from esri has uploaded also works, but I cannot confirm that since I don't use that style. Were you having trouble getting either to work? You should be able to find the links/files in earlier thread messages and even in one or two other threads if you haven't already downloaded either of them. ... View more

Jonah, If I recall correctly, the help outlines a couple of different methods related to using your own templates.  One is via publishing an Export Web Map gp print task.  The other is discussed under the umbrella of "advanced printing".  Are you talking about the Export Web Map gp task when you say "...published...a geoprocessing service"?  If so, you either save your mxd templates in a folder or let ArcGIS Server copy them onto the server (recommend the former) per the instructions in help.  The config file entries for the Flex viewer are really minimal, regardless if you use the Application Builder or the source code. I suspect you were following the help related to the "advanced printing", as the result is something that you then need to program your own front end to use effectively. Just my opinion. I effectively serve up letter-sized to E-sized templates to my users with the Export Web Map print task, with excellent results just by following the instructions in help carefully. ... View more

Alejandra, I think I may be at the end of any suggestions I am able to make regarding this.  I have no experience with WMS services, so I don't know if there are any tricks with getting those to work with editing and the Flex viewer. Typically, backward compatibility of datasets can be an issue. But I don't know if an ArcGIS 10-based WMS service is incompatible with ArcGIS 9.3 even though your user is consuming the data as a service and not directly. Your comment that you can sometimes see the service but not consistently sounds like a connectivity issue of some sort with the server. Unless someone else here in the forums has something to offer, your best bet may be to start a support incident with ESRI. I'm sorry I cannot offer anything more... ... View more

Alejandra, You mention a WMS service.  Are you referring to the fact that when publishing your service you checked the "WMS" box in the Capabilities list or are you using 'WMS' as a generic term for the service? If you are publishing and sharing the service as WMS I will be of no further help, as I have never needed to publish my services in that way.  Hopefully someone else on the forums can respond or perhaps this warrants a support call to ESRI. If you are using WMS generically, in the Capabilities list for services that have editing capabilities I check the "Feature Access" capability.  This enables the geometry to be served up via the FeatureServer service that shows up in your services list. As for the data layers being edited... I use data layers from my SDE data store, versioned for editing with the option to move edits directly to base (the checkbox in the dialog that pops up when you register a layer as versioned).  I am using direct connections to the SDE database.  I create a child version that will be used for the editing in my flex viewer in ArcMap.  Then in ArcToolbox I use the "Create Database Connection" tool to create a connection to my SDE database **that connects to the version that I am using for editing**.  That tool allows you to specify a particular version.  I save that connection in a place where my Server can access it. I then start a new ArcMap project and connect to my SDE database and add my layer(s) that I am editing within that version.  You may need to start editing and ensure that the layer templates are set up.  I typically add a feature of every type that will be edited just to test but also to verify that the editing app is "seeing" everything.  I delete these features later before actual use.  I then publish the map as a service with Feature Access checked (as described above). After the service is published, I configure the edit widget as well as the main flex viewer config file so that my layers show up.  I typically create a separate version of my viewer specifically for editing a particular layer or set of layers.  I like to have my users in the habit of consciously editing or consuming data but not blurring the two use cases together.  After all, if they are the stewards of the data, I want them to be successful and not inadvertently introducing errors into the data.  End users that edit data don't always think about the big picture of their actions like those of us that "do GIS" do. That means their regular, departmental viewer has the layers that they edit but doesn't have the editing function added.  If they need to add or change anything with that layer they must load the editor, which I tend to strip down to the necessities for editing and not everyday use. But your specific needs will dictate how you structure everything. If your map services are public, share the link and we can take a look.  Maybe something will pop out that hasn't been obvious in our dialog. ... View more

Alejandra, Have you published your map service as a feature service?  The editing widget uses the FeatureServer rather than the MapServer service.  Perhaps you did not check that particular box when publishing your map service? The other thing to look into is whether you have properly set up your data for editing.  Is this an SDE data layer or a layer in a file geodatabase? ... View more