Latest Contributions by MikeMeeks

‎04-20-2011

If that is the case, how have my python scripts worked the past 3 years from Release 9.2 thru 9.3.1? Mike

‎04-20-2011

I'm converting all my 9.3.1 python scripts to 10.0 sp1 arcpy scripts and getting fatal crashes in IDLE when I use the r raw string when defining constants which worked fine in the 9.3.1 gp. Example: Layers = r'Road Centerline' Scales = r'2000;900' All = r'Recreate All Tiles' arcpy.ManageMapServerCacheTiles_server("server","BaseCache/RoadCache", "Layers", Layers, Scales, All.......etc) After I changed the constants to replace r with " it worked Example: Layers = "'Road Centerline'" Scales = "'2000;900'" All = "'Recreate All Tiles'" I've used r for years with python and had no problems in the past. It was a habit and am now having to change all references of r when used in an arcpy call. The r still works with python functions such as open(r'C:\GIS Scripts\RoadCacheLog.txt', 'a') Has arcpy been designed not to accept the r now? because it worked with gp! Mike

‎12-17-2010

Brad, I extracted the file into C:\Program Files\ArcGIS\Desktop10.0\Locators which is where the other locators are found. I then created the Address Locator selecting the General - Single Field. I went into ArcMap and selected the Geocoder and entered a condo address without the # sign and it still would not make a match. Maybe I did something wrong? so I have uploaded a zip file with a shapefile that contains some condo records with the # sign. I also included the General locator to have you review and ensure it is the alternate one you created. I included the AddressLocator.loc that I created. And lastly a screen shot in ArcMap where the locator can not find the address. I hope all this data will help to resolve the issue at hand. I do appreciate your effort in trying to create a custom geocoder! Thank you - Mike

‎12-15-2010

In 9.3.1 a single field Address Locator against our Property Appraiser database worked just fine. The PA uses a # symbol to designate a condo unit. In 10.0 Single Field Address Locator, it will not match with a condo unit unless the # sign is entered, regardless of the Spelling Sensitivity. In 9.3.1 it would match at 90% but would still find the match. I never thought something a core as Geocoding would break in 10.0 sp1. What a disappointment 10.0 has been!

‎12-15-2010

I'm trying without any luck to get ANY layers to show up as Operational or Base Map using Mobile Project Center. I have Cached Services that I use as BaseMaps in my .net Web applications just fine along with operational services. All these services were created with the Mobile Data operations capability checked. Using Mobile Project Center, I can't seem to get any Services to show up and when I navigate to the conf.xml file in the Cached folder, the system does not find any cache. When I manually type the folder/conf.xml combination, it accepts the layer but gives me a red ! stating Error: Not a valid conf.xml file. I called ESRI and the analyst had no clue using a screen sharing session how to use Mobile Project Center. Any help would be appreciated. I can't believe it is this hard to have the system recognize my Services & Caches!

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by MikeMeeks

Re: r' Raw String Suppress Escape not working in arcpy ArcGIS 10

r' Raw String Suppress Escape not working in arcpy ArcGIS 10

Re: Geocoding in 10.0 sp1 does not work with # character though it worked in 9.3.1!

Geocoding in 10.0 sp1 does not work with # character though it worked in 9.3.1!

Can't get any layers except ArcGISonline to appear as base maps!