Latest Contributions by BlakeTerhune

I just tried the same thing in a File Geodatabase and it worked. Maybe try leaving that optional "Join" field in Remove Join blank. However, I was not using GlobalID as a key field. Is there something else you could use to test with just to see if you can get a model that works? ... View more

If you're using a table in SDE (instead of a feature class), are you creating a table view instead of a feature layer? Also, make sure you're referencing the correct table view for the remove. ArcGIS Help 10.1 - Remove Join (Data Management) Could you also try rewriting just a simple add join, remove join based on the Esri help example to see if you're doing it right. Once you get something working, start adding in the rest of your code and see where it breaks. Maybe post a sample here so we can review it. ... View more

I don't think you can combine a definition query and visible scale range with Python like that. You could use that definition query but it would never change the visible scale range in the MXD on its own. I recommend you try using layer files. When you create a layer file, it will save the visible scale range you set (as well as definition queries, symbology, labels, etc). So instead of adding the feature class from a geodatabase, just add it from the layer file and it will already have all that stuff set up. If you want your visible scale range to change, you'd have to save over the layer file with the new visible scale range set. Your other option would be to run a Python script that checks for a vscale field in all (or certain) layers in the map and sets the visible scale range; it would have nothing to do with a definition query. ... View more

Is this a duplicate of your other thread? Changing of python code If so, please delete one to avoid confusion. ... View more

One of the first things you should know about Python is that indentation matters. The code you posted has some strange indentation and I'm not confident I'm interpreting it correctly. Do you have a link to the original Python file or can you just upload it here? ... View more

I tried clearing the display cache in ArcMap. Rebooting the server is not an option at this moment. To troubleshoot, I created a new test map service with the same aerial and created a (small) new cache for it. The only difference is that I created the cache in the new location right away (no moving). The new test map service cache displays fine in ArcMap. ... View more

I think you're on the right track. If you've got discrete categories like that with only a few categories, a choropleth map is probably your best bet. If you already have those impact descriptions attributed in your data, you can symbolize using categories and pick the field. If you've got a range of impact values and want to group them into those impact categories, symbolize by quantity and classify the categories however you see fit (just be careful not to lie with statistics). ... View more

I haven't tried using table join with a selection, but my guess would be that you need to create your table view from the selection instead of creating a selection from the table view. To make it easier, you could just use a where clause when creating the table view; then do the join. Also, the way you call the joined table in CopyFeatures might be wrong. Try this instead: arcpy.CopyFeatures_management(ALK_Flurstueck_Merge1, "zwErgebnis_" + i, "", "0", "0", "0") EDIT: Maybe try this and see what it does. I got rid of the fields you had listed in the join so it will bring back everything from Meka; not sure if that's what you want. I also got rid of the optional parameters on copy features. Did you intend to use the spatial grid parameters? # Import arcpy module import arcpy arcpy.env.workspace = r"R:\Karto\Bierer2014\FFH_MEKA\data.gdb" # Local variables: ALK_Flurstueck_Merge1 = r"R:\Daten\geo_daten\Basisgeometrien\Basisgeometrien_2014_03_21.gdb\data\ALK_Flurstueck_Merge1" Meka = r"R:\Karto\Bierer2014\FFH_MEKA\Meka.mdb\Meka" Count_Lines = arcpy.GetCount_management(Meka) print Count_Lines for i in range(0, 18000, 100):     print i     y = i + 99     print y     z = i     where_clause = "[ID] < {} AND [ID] > {}".format(y, z)     MekaLyr = arcpy.MakeTableView_management(Meka, where_clause)     # Process: Feld verbinden     arcpy.JoinField_management(ALK_Flurstueck_Merge1, "FLSKZ", MekaLyr, "FLRSTKZ")     # Process: Features kopieren     zwErgebnis = "zwErgebnis_{}".format(i)     arcpy.CopyFeatures_management(ALK_Flurstueck_Merge1, zwErgebnis) ... View more

I don't have a solution right away, but maybe you can find something helpful from this blog post? Split into equal length features | ArcPy Café Looks like you need ArcGIS 10.3 for the segmentAlongLine method of a geometry object. ... View more

Good suggestions. It looks like all of the config files and stuff are there in the folder that was copied. I tried stopping and starting the service but the issue remains. ArcCatalog Preview doesn't show anything either. The view in ArcGIS.com Map also works. ... View more

So I just finished getting this all set up. I checked the Javascript viewer and the cached map service works fine. I tried adding the service to ArcMap and nothing shows up. The layer is in the table of contents but there is nothing in the map data view. Any ideas? ... View more

Haha! Well, you did post in the Python section so I thought I would go for it. It's not as complicated as it looks. Create Near table Add two new fields for in and near key fields Join the original feature classes to field calc the in and near key field values Export final near table ... View more

I haven't used Wing, but it looks like the Auto-Completion and Source Assistant is what you need. In some cases you may need add to the Python Path in Wing's Project Properties, accessed from the Project menu. ... View more

I've done something similar and the Near table worked for me. When I was doing this, I also found it frustrating that the Near table would only show the ObjectID of the features, requiring additional joins to actually see what features the OIDs were for. I created this Python script that will create a Near table with a key field of your choice in the output. I haven't tested it much but maybe you can get some use out of it. import arcpy import os try:     # Set local variables     sourceGDB = r"C:\temp\mytempsource.gdb"     outputGDB = r"C:\temp\mytempoutput.gdb"     ## IN and NEAR features can be the same     in_fc = "FeatureClassIn_Name"     in_fc_keyfield_name = "KeyField_Name"     in_fc_keyfield_type = "Long"     in_fc_path = os.path.join(sourceGDB, in_fc)     near_fc = "FeatureClassNear_Name"     near_fc_keyfield_name = "KeyField_Name"     near_fc_keyfield_type = "Long"     near_fc_path = os.path.join(sourceGDB, near_fc)     search_radius = "25 Feet"     # Create near table and make as TableView     neartable_inmem = os.path.join("in_memory", "neartable_inmem")     arcpy.GenerateNearTable_analysis(         in_fc_path,  ## in_features         near_fc_path,  ## near_features         neartable_inmem,  ## out_table         search_radius,  ## search_radius         "NO_LOCATION",  ## location         "NO_ANGLE",  ## angle         "ALL",  ## closest         "0",  ## closest_count         "PLANAR"  ## method     )     arcpy.MakeTableView_management(neartable_inmem, "neartable_view")     print "Near table view created"     # Add new IN and NEAR key fields to near table     in_kf = "IN_{}".format(in_fc_keyfield_name)     arcpy.AddField_management(         "neartable_view",  ## in_table         in_kf,  ## field_name         in_fc_keyfield_type,  ## field_type     )     near_kf = "NEAR_{}".format(near_fc_keyfield_name)     arcpy.AddField_management(         "neartable_view",  ## in_table         near_kf,  ## field_name         near_fc_keyfield_type,  ## field_type     )     print "Key fields added"     # Join and calc IN key field     arcpy.AddJoin_management(         "neartable_view",  ## in_layer_or_view         "IN_FID",  ## in_field         in_fc_path,  ## join_table         "OBJECTID",  ## join_field         "KEEP_COMMON"  ## join_type     )     arcpy.CalculateField_management(         "neartable_view",  ## in_table         in_kf,  ## field         "!{}!".format(in_fc_keyfield_name),  ## expression         "PYTHON_9.3"  ## expression_type     )     arcpy.RemoveJoin_management("neartable_view")     print "{} field populated".format(in_kf)     # Join and calc NEAR key field     arcpy.AddJoin_management(         "neartable_view",  ## in_layer_or_view         "NEAR_FID",  ## in_field         near_fc_path,  ## join_table         "OBJECTID",  ## join_field         "KEEP_COMMON"  ## join_type     )     arcpy.CalculateField_management(         "neartable_view",  ## in_table         near_kf,  ## field         "!{}!".format(near_fc_keyfield_name),  ## expression         "PYTHON_9.3"  ## expression_type     )     arcpy.RemoveJoin_management("neartable_view")     print "{} field populated".format(near_kf)     # Export final near table     kf_near_table = "{}_NEAR".format(in_fc.replace('.', '_'))  ## Replace any dot with underscore and add _NEAR suffix     kf_near_table_path = os.path.join(outputGDB, kf_near_table)     arcpy.CopyRows_management(         "neartable_view",  ## in_rows         kf_near_table_path  ## out_table     )     print "Final near table output at {}".format(kf_near_table_path) except Exception as err:     print err     ## If there was an ArcPy error, write all of the messages returned by the last tool     if arcpy.GetMessages(2):         print arcpy.GetMessages() finally:     # Cleanup     arcpy.Delete_management("in_memory")     arcpy.ClearWorkspaceCache_management() ... View more