Latest Contributions by RonnieRichards

Is it even possible to detect a if a layer is a query layer using ArcPy? ... View more

Yes the fix is we have to change our APT values to # which is very silly when the source data matches USPS standards. The locator supports the unit_type column and it is mapped to our column but clearly does not work. Changing to a # only provides a 98.0 score because the unit_type does not match, huh?? Something is wrong here and improving the scoring is not documented anywhere. This is what #BUG-000093854 refers to. Give it a try with your source data. W were not happy with the results and we have wasted months of time trying to get it to work well. ... View more

Hello Gabi, Unfortunately no we have reverted back to the 9.x locator style for units because the 10.x locators are still not documented well or work very well for that matter. We expect an address locator with units to match at 100% and this is not the case in the current versions and locator style.  There are bugs in the new styles. Below are all of my ArcGIS Ideas, enhancements and bugs which you might consider reviewing and voting for if you agree. Several releases and years later we are still waiting and now looking at 3rd party solutions because when we call support they call this a "Customization" yet no complete documentation exists and we are using the out of the box locator style. Fully document the Customizing Locator process and update Locator documentation https://c.na9.visual.force.com/apex/ideaView?id=087E00000005AR4IAM Standardize Addresses Tool mixed case results and other inconsistencies https://c.na9.visual.force.com/apex/ideaView?id=087E00000004GOqIAM #NIM070066   The Standardize Addresses tool does not return the same address standardization using ArcGIS Version 10 address locators as compared to version 9.3.1 address locators. Update File based locator's reference feature class https://c.na9.visual.force.com/apex/ideaView?id=087E00000004EhvIAE Locator style for Apartment / Units in core product https://c.na9.visual.force.com/apex/ideaView?id=08730000000by67AAA #NIM081240   [Enhancement] Please add support for building/unit/apartment numbers in the standard locator styles. #BUG-000093854   When using the US Address-Single House Subaddress locator style with the Find tool, the match score is improved if using '#' as the unit indicator instead of 'APT' even if the original input data uses 'APT'. #NIM059962   Cannot create an address locator with a multipoint shape file. The result is a Background Processing Error or ArcGIS Application Error. schemaLockingEnabled for Geocode services https://c.na9.visual.force.com/apex/ideaView?id=087E0000000CxTRIA0 ... View more

Yes I am surprised they work thru mxd import but not Layer files or add Data? I agree with above if they are going away why supported them at all with mxd import? Raster Catalogs do have a place how else do you do a time-series enabled raster publication? ... View more

Have you tried AGO-Assistant? What you are looking for might already exist... ... View more

Agreed. Same thing happen to us from 10.2.2 -> 10.3.0 upgrade didn't report it to support because it is near impossible to reinstall 10.2.2 and reproduce. ... View more

This idea is only 3 years old please provide the options to set all locator properties AT TIME OF CREATION. Having users expect to know or compare all properties to existing locators (especially in Geocode services) is not reliable or a sustainable solution.  For example in 10.x the Dual Ranges locator does not support intersection searches and requires changing the properties of the locator AFTER IT IS CREATED.  In 9.x the option for intersections was a default so the new tools need to have these options exposed to become maintabale at an enterprise level.  ... View more

Jeff, We also still have this issue in 10.3.1 but we are still using the 10.2.2 compact cache format and we hoping it was fixed but does not seem to be the case. It appears instead of fixing the problem with the compact cache, a new cache format was created in 10.3. Are you using the new 10.3.1 cache format? ... View more

When publishing services to ArcGIS Server using arcpy it does not provide the ability to set service parameters. Please expose all service parameters so they can be automated for service deployment. This should include the basic things like "overWriting" a service as well as enabled or disabling capabilities and parameters.  Provide arcpy classes, modules or methods to allow a complete arcpy publication solution and similar workflow to the Desktop publication workflow. We should not have to resort to xml or file based hacks to publish services in the same manner as Desktop. Support will not provide examples on modifying the SDDraft and the documentation does not even mention this limitation or ability so a solution needs be provided.  ... View more

I agree or at least support RDBMS calculated columns since SDE edit sessions currently do not support these field datatypes. ... View more

Matt, This is great thanks for letting us know. We applied this to our environment and it seems to working for us. Amazing how cool caching is when it actually works and none of the silly work-a-rounds have to be initiated. Is ArcGIS the only software package that we all clap when it works? Whew finally that is fixed now we wait for the 10.3.1 release Sure wish I heard this news from ESRI because we are on the bug watch list. That system needs to improve since we reported this issue last summer around the same time David reported it AND we should not have to report an issue to be aware of it. This information should be readily available and subscriptions to interested parties. ... View more