Latest Contributions by BrianOevermann

Josh, It seems that many of us are tackling ADA compliance for these facilities.  I, too, have started with the curb ramps fc and made modifications. For the sidewalks, we are going to be marking problem locations--a point feature--since the entire sidewalk segment may not be out of compliance.  I will likely "back fill" the ADACOMPLY field in the sidewalk feature for a general view of compliance/non-compliance later. I am just diving into the LGIM, so there may be better ideas out there. And given that your last reply was in January, my comments may be moot for your situation. Scott, could you consider adding an ADACOMPLY field to the curb ramp feature class as well? It is a field I will be adding (using the field from the sidewalk fc as the model) to that feature class and it would be nice for future versions to have it included already.  In a perfect world they all are compliant, but until we find the ones that aren't compliant and subsequently fix them... Brian ... View more

Chris, If you had ArcGIS 10.0 installed and then upgraded to 10.1, GDBT will work.  If your situation is like mine, where IT just replaced your machine and a fresh 10.1 install is in place (no previous 10.0 install), you are out of luck.  The install checks the registry for some 10.0 entries apparently.  Seems like it could be an easy fix for ESRI to do, if they just took a few minutes to work on it.  Or better yet, make it part of core. I believe there is an ArcGIS idea about that.  You might wish to promote it. ... View more

Marc, I wonder if your experience is due to the fact that these are SDE locators. I have no idea--maybe an ESRI employee will lurk by and have some knowledge to impart regarding that. When I upgraded Server from 9.x to 10.0, I completely rebuilt my locators because of the new underlying structure.  And when I upgraded to 10.1 I again completely rebuilt my locators. So, all of the info and experience I have shared is based on locators created using 10.1.  The underlying data those locators reference is in SDE. The "republish after rebuild" is a complete pain.  My plan is to script a nightly process that takes care of this and other Server-related maintenance headaches but I haven't had a moment to do that.  Fortunately, we aren't adding streets and site addresses by the boatload right now so it is reasonable to keep up. ... View more

Marc, So, a little background... When I created my locators (including the composite), I saved them in a folder called 'Locators' (original, I know) on the map server. As an aside, I also have a folder there that has all of the .mxd projects that create all of my map services.  The data is on SDE or in a file gdb library area, all registered with the server. Just like you, I have published each of the individual locators separately, then I publish the composite locator which gets copied to the map server. On the map server, my composite locator is sitting here: \arcgisserver\directories\arcgissystem\arcgisinput\geocode_services\<my_composite_locator_name>.GeocodeServer Inside that folder, like all map services, I have an 'extracted' folder that contains an 'esriinfo' folder. There are folders for each of the locator services in the 'geocode_services' folder with the same structure as above.  In the composite locator folder, however, there is an additional folder called 'v101' that contains the .loc and .loc.xml files. These two files make up the actual locator.  These files exist in my 'Locators' folder mentioned above for the rest of my locators.  I don't believe it is simply because I happen to have them in a folder already on the server itself that they are not copied into the same structure as the composite locator.  I think they could easily be anywhere on the network as long as the folder is registered with the server. So with all of that said, are the .loc and .loc.xml files getting saved to a 'v101' folder for your other locators or are you simply seeing the individual folders that are normally present?  I am assuming that you have registered your locator folder location, otherwise you would see the obvious warning message that the locators will be copied to the server (like you see with the composite). ... View more

Sandra, If you are using the version that Brad has posted, the "B" in 123B Main St would need to be part of the house number field. [Correct me if I am wrong about that, Brad] For the version I posted, here is a bit of context... Our City is part of a regional alliance that happens to have a long-standing address layer schema standard for use in certain regional applications.  The schema has its shortcomings and many cities maintain their address layers with fields that meet their individual needs but can still be exported to that regional schema for data sharing. We have some legacy addressing that includes fractional halves (i.e. 123 1/2 Main St) as well as your example of 123B Main St.  While the "B" is really a unit indicator, these legacy addresses have used the 123B format for so long that we simply treat them as fractionals.  But we are a reasonably small city and the number of these is small.  All newer addressing adheres to the 123 Main St Unit B format. The regional schema mentioned above is a numeric field, so that prevents me from concatenating the fractional half or letter into the house number.  Thus, my version of the locator includes a fractional field as well as the unit field. For those legacy addresses, the "B" goes into the fractional field and not the unit field. In the locator, a space is required between the 123 and the "B".  Otherwise the 123B will be searched against the house number only instead of the house number and fractional fields. All of that said, if you standardize your "A" and "B" units as 123A and 123B, you are likely better off either making them a part of the house number or using the fractional field rather than the unit field.  You really need to proceed based on how you expect users to enter the address for matching, and there is no right answer. Maybe others have some additional ideas.  Apologies for the length but I wanted to provide some context regarding why my version is built the way it is.  Admittedly, my primary intent was to create something that worked for us.  The fact that others might be able to utilize it was simply a bonus. I do hope that ESRI begins to provide these locators in the "base code". ... View more

That sounds a lot like what happens when you do not embed your fonts within the pdf document.  In the export dialog there is a tab that allows you to embed fonts, rasterize graphics, etc.  You may need to play around with various settings. ... View more

Thank you, Dasa. It turns out that I had the right location, and even the right line of code after all.  I just failed to wrap it in the <esri:exportOptions>... </esri:exportOptions> wrapper.  Doh!  I guess I wrongly assumed that I didn't need to wrap it since it was only one parameter. JStanton's idea for a pick list of dpi values (or just an input box for entering a value) is something that could be useful in certain situations, though I don't have an immediate need (nor time) to look into it.  If it is an easy "add", I would love to see it.  If it is more complex (and I suspect it may be), this could be a great, "quick enhancement" to the next version of the print widget.  I would also make a pitch to have a dpi (or dpi pick list) added to the config file for the "non-developers" out there.  Just a thought. Thanks again for the quick solution, Dasa. @Rhett:  Maybe all of the rain is short-circuiting our code here in Washington! Ha! ... View more

Bjorn, I, too, have users screaming for better print resolution. I have attached a sample that illustrates what I believe Rhett is also experiencing. I have attempted to add the dpi setting from exportOptions to the widget but have been unsuccessful so far.  I have a feeling that I am inserting the dpi setting in the wrong place within the ExportWebMapForm.mxml Could you point Rhett, I, and probably many others in the right direction? ... View more

Derek, Thank you for the pointer.  I am using direct connections to SDE so needed to use the 'Create Database Connection' instead.  But your response got me on the right track. ... View more

Derek, Your assumptions accurately describe the situation.  Can you point me to a help document that describes how one creates a .sde connection file to a specific version of a feature class?  The 'Add Database Connection' is straightforward but appears to not have the granularity to reach "inside" a geodatabase to specify a particular version.  I am obviously missing something that is likely very simple. Thanks for your help. ... View more

Prectaylor, Are you using the style that Brad has posted or the one I have posted?  Are you on 10.1 or an earlier version? And the way I read your post, the only issue is with the 'NE' directional?  Extremely odd... Maybe Brad (or others) have some insight.  I can successfully use all directionals--in 10.0 as well as 10.1. There isn't an extra space in your prefix data field for the 'NE' by chance?  (i.e.  ' NE' instead of 'NE' ) Brian ... View more

Bjorn, Perfect!  I thought it would be something simple.  This seems like it would be a good topic for the web help documents.  Maybe a short how-to for all of the common layout elements that are added to layouts? ... View more