For those of you that arrived in San Diego on Sunday, you were greeted by a downpour of rain that lasted into the night. However, that all cleared up today for the 36th Annual ESRI User Conference.
During this morning’s Plenary Session, Jack emphasized the “Geography Everywhere” theme and touched on the usual things like web GIS and sharing data. Really there were few surprises. However, they did have a cute little skit about all their apps, posing like individuals in a dating service to get your attention to use them. It was a different way of showing you all the choices you have when it came to apps. You can even vote for your favorite app here.
Here are a few new announcements that might be of interest:
- Vector tiles, finally!
- New Workforce/Dispatcher, Workforce/Mobile, and Navigator apps that will work with Collector
- New AppStudio for ArcGIS that will help you build your own native apps in Android, iOS, Windows, and Linux
- ArcGIS Earth, full KML file support
- New drone app
- Statistical and scientific packages like R and SciPy will be able to run directly as geoprocessing tools/scripts in ArcGIS
- ArcGIS for home use licensing will now extend to the entire ArcGIS product, not just Desktop
- Expect ArcGIS 10.4 and Pro 1.2 in Winter 2016
I would suspect that ESRI will have the Plenary Session video online sometime today. I will update this post when it becomes available for you to watch at home! -mike
4:25pm update: Click here for today’s videos.
This week ESRI has released ArcGIS Pro 1.1. Here is a list of some of the enhancements:
- A new SDK for .NET to customize and extend ArcGIS Pro
- A Range Slider that allows you to dissect and visually analyze your numeric data
- The ability to publish 3D scenes containing multipatches
- Layout enhancements, like guides and snapping and the ability to add extent indicators
- Support for working with Excel tables directly
- Date line wrapping allowing you to pan, edit, and work across the international date line
Click below to read more about the release.
This year in July will be Disneyland’s 60th anniversary. Disneyland opened on July 17, 1955 in Anaheim California and was the only theme park designed and built under the direction of Walt Disney.
Opening day was broadcast live by ABC (one of the investors and joint owner of Disneyland) and was hosted by three of Walt’s friends: Art Linkletter, Bob Commings, and Ronald Reagan. About 28,000 people visited the park. Watch the whole thing below!
Believe it or not, Disneyland was built in 7 months before opening day! Also, Tomorrowland construction was delayed and was put together in the last 2 months! Before building began, Walt Disney was insightful to place towers around the area to film time-lapse movies during the construction. Check out this video of one of the film reels. It is really cool to see what that area of Anaheim looked like before Disneyland was built.
When guests entered the park, they were given little guides that told them about all the attractions at Disneyland. Check out this 1958 guide and maps.
I like in the Tomorrowland section there is a caption that reads “The colorful Avenue of Flags marks the entrance to Tomorrowland, the world of 1987”. I don’t remember 1987 looking like that!
Note no Monorail, Matterhorn, or Submarine Voyage. Those came in the summer of 1959. Check out this insert that was placed in the guides.
If you plan on visiting Disneyland tomorrow on anniversary day … all I can say is good luck to you and stay sane!
From time to time I encounter the issue of a text field that is too small. A great example would be a street name field that was fine for a while, but now you have new street names that require more characters. Here are a few examples on how to change the field length. I will be using ArcGIS 10.2.2 and a feature class in a file geodatabase to demonstrate.
The Traditional Way
Open the feature class in ArcMap and bring up the attribute table. Below is a feature class representing schools.
Add a new text field to the table with more characters.
Right click on the new field name in the table and select the field calculator option to calc the new field to the old one.
And finally right click on the old field name and delete it. Here is mine.
What I don’t like about this method is that I could not reuse the field “NAME” and had to create “NAME2”. Also I liked the original order, and now my field is at the end of the table. Sure, I could do it again by adding back the field name “NAME” and recalcing again, but my field is still at the end. Yes you can reorder fields for display in ArcMap, but it does not do anything to the real order of the fields in the geodatabase … and that bugs me! So on to the second option.
The Feature Class to Feature Class Tool
A better way of doing this is by using the Feature Class to Feature Class tool. The tool allows you to change the field mapping, thus allowing you to change the field length and keep the field name and position if you want. You can find the tool by doing a tool search. Open the tool and load in your input feature class.
You have to specify a new output feature class. Also note the fields that are listed in the field map section. Right click on the field you want to change the length of and select Properties.
Change the Length property and click OK. Then click OK on the tool. A new feature class is created with the larger field. Just to verify, you can use ArcCatalog to view the field information.
Field mapping with the tool allows you to shuffle around the fields, rename them, or remove ones you do not want as well. The down side? A new feature class has to be created, which might be an issue if you have millions of records and limited space, however you probably don’t so it works out fine.
After the tool is done, you can delete your old feature class and rename the new one to whatever you want.
So now that leaves the last option … a python script that will do this.
The Python Script
# Change a text field length # Import arcpy module import arcpy # Overwrite exising output arcpy.env.overwriteOutput = True # Setup feature class and field info infc = "c:/temp/fieldtest/data.gdb/schools" outloc = "c:/temp/fieldtest/data.gdb" outfc = "schools2" fieldname = "NAME" fieldlen = 50 # Setup field mappings skipfields = ["OBJECTID", "FID", "Shape"] fms = arcpy.FieldMappings() fields = arcpy.ListFields(infc) for field in fields: if field.name in skipfields: pass else: fm = arcpy.FieldMap() fm.addInputField(infc, field.name) if field.name == fieldname: newfield = fm.outputField newfield.length = fieldlen fm.outputField = newfield fms.addFieldMap(fm) # Copy feature class with new field mappings arcpy.FeatureClassToFeatureClass_conversion(infc, outloc, outfc, field_mapping=fms) # All done! print "Done!"
So let’s step through this. The arcpy module is imported and we set our overwrite output to True so we can rerun this script and overwrite our output feature class.
Next are some variables that you can modify. The input feature class “infc”, the output location “outloc”, the output feature class name “outfc”, the text field “fieldname” that we want to change the length of, and the new field length “fieldlen”.
Next, we setup field mappings, but we only want the non-system type fields. Fields like OBJECTID, FID, and Shape are maintained by ArcGIS, so we don’t want to mess with them. A list of fields we want to avoid, “skipfields”, is set, a blank field mappings “fms” is set, and we collect all the fields in the input feature class and store them in “fields”.
Next, we loop through all the fields and check if each one is a field we should skip. If so, we do nothing “pass”. If not, we setup a blank field map “fm”, add all the field information to it (field type, length, etc.) from the field in the input feature class, then check if the field is the one we need to change. If so, we make a new field variable “newfield” set to the current field map, change the length property of the “newfield” to the value we set in “fieldlen”, then reset the current field map to our “newfield” setting. We then add the field map to the field mappings “fms”. Think of the field mappings as the list of fields and their properties, while a field map is the properties of one field.
Once the loop is done building the field mappings “fms”, it is used in arcpy.FeatureClassToFeatureClass_conversion to create our new feature class “outfc”.
Give the script a try and see if it works for you. One thing you could do with the script at the end is to rename or delete the old input feature class and then rename the new output feature class to the old name. Just a thought! -mike