Today (Tuesday) 700 students from secondary schools, 7th grade through high school, attended the GIS Day Event at the Salt Lake Community College Miller Campus. These schools came from areas around the Salt Lake County and as far away as Saratoga Springs and Ogden. Other activities are taking place elsewhere in the state too including another event for school kids at the Utah County Administration building, hosted by the Utah Valley GIS Users Group and a whole week of activities at the University of Utah Geography Department.
Tomorrow (GIS Day) we are expecting 1200 3rd grade through 6th grade students. These students are from elementary schools from around the Salt Lake Valley. The schools include public and private schools. Both days, the students are able to enjoy learning about the geospatial technology through the generous bus grants from the Utah Geographic Information Council (UGIC).
The U.S. Census Bureau is conducting the Boundary and Annexation Survey (BAS) to update our records regarding changes to legal boundaries, names, and governmental status of all governmental units effective on or before January 1, 2010. This voluntary survey is an important opportunity for you to ensure that we have the correct boundary and legal name for your county, as well as for the governments within your jurisdiction. The Census Bureau will use the boundary information you provide to report data from the 2010 Census and estimates from other programs and surveys, such as the Population Estimates Program (PEP) and the American Community Survey (ACS). The 2010 BAS is especially important as it is the last opportunity for participants to update their legal boundaries prior to the completion of the 2010 Census. Accurate legal boundaries will result in more accurate data tabulation for all of the census programs and surveys.
In preparation for the upcoming 2010 BAS, the U.S. Census Bureau is conducting BAS workshops in select cities across the country. The BAS workshops will be open to interested participants and will include both digital and paper BAS training. The training will have separate sessions for digital and paper participation procedures. You may choose to attend one or both sessions. Each session will provide an overview of the BAS, an explanation of geographic relationships, and information on why correct boundaries are important for the 2010 Census, PEP and ACS.
Digital BAS training will include demonstrations on how to complete the BAS using ArcGIS or the MAF/TIGER Partnership Software (MTPS). MTPS is a PC-based software application provided by the Census Bureau for participants to digitally update the Census Bureau maps and forms. There will be hands-on digital BAS training in select cities (please see the attachment). We encourage you to bring laptops along with your boundary data, so we may clarify any questions you may have.
Paper BAS training will include a detailed review of how to read and update paper maps and the BAS forms. Participants will learn how to properly annotate legal boundary updates and feature changes on the Census Bureau maps. We request you bring your annexation information since there will be an opportunity to update your boundaries on-site.
What: BAS 1-Day Training
When: December 10, 2009 and December 11, 2009 (The same one-day training is being offered on consecutive days at this location)
Agenda: 8:30 AM – Noon Digital BAS Workshop, 1:00 PM – 4:30 PM Paper BAS Workshop
Where: Utah State Capitol Complex, Room 30 House Building (West Building)
RSVP: by December 3, 2009
If you wish to RSVP via email, please email the above information to
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
If you wish to RSVP via telephone, please contact the BAS Team at (301)-763-1099.
If you have any questions pertaining to the BAS program and the upcoming workshops, contact the BAS team via email at
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
or via telephone at (301)-763-1099. Additional information on the BAS program can be found on the BAS website: http://www.census.gov/geo/www/bas/bashome.html
AGRC and UDOT are collaborating on the maintenance of a statewide roads GIS layer from which the route features can be derived and calibrated.
The steps below describe a process of building and calibrating polylineM route features from the statewide road feature dataset maintained in Utah's State Geographic Information Database. This process can be used at anytime by UDOT staff using the road features in AGRC's editing database (UTRANS) and will also be done periodically as part of AGRC's bimonthly scheduled releases of roads related data in the SGID public-facing database (SGID93) and related shapefile and file geodatabase products on the SGID ftp site.
1. Data Preparation - Streets. Features in the street centerline feature class (based on SGID93.Transportation.Roads) must be attributes with the proper UDOT route name attribute (field=DOT_RTNAME, example value=0015P for Interstate 15) and the route part attributes (field=DOT_RTPART, example value=1 for all single part routes).
2. Data Preparation - Calibration End Points. Most routes are composed of a single, connected polyline part. However, there are a fair number of route that must be built from two or more component parts. This must be done for 3 cases: A)concurrent routes that run concurrently with other higher order routes (examples: US89 between Bountiful and Farmington, I-84 between Tremonten and Ogden); B) broken routes, where the route stops in one location and then starts up again in another location (example: SR-30 in Box Elder, Cache, and Rich counties; and C) branching or looping routes (examples: SR-190 in Big Cottonwood includes both a branch and a loop). Each route part must have two end point features stored in the UTRANS.TRANSADMIN.UDOTRoutePartEndPoints feature class that carry the route name, direction, and part number (in the LABEL field, a concatenation of RT_NAME, RT_DIR, and RT_PART) and REF_VALUE (milepost value at start and end, respectively).
3. Build Simple Calibrated Routes. The first step in route building is to build simply calibrated routes. This process, described in the post VBA: Build Simple Calibrated Routes aggregates the centerline features into a single route feature for each route part, stored in a file-geodatabase. Check the output file that is written to disc from this process for problems/issues that will include calibration end points that are not coincident with the end of the polyline route, routes that are accidently missing segments or missing DOT_RTNAME/DOT_RTPART codes, duplicate or overlapping geometries etc. Repeat this process until the outfile is empty. Exit ArcMap and recalculate the spatial index for this layer in ArcCatalog, otherwise some of the longer routes will not draw properly.
4. Merge Route Parts into a Single Route Feature. The code to do this is a function called improvedRoutePartMerge()process which is found at the bottom of the VBA: Build Simple Calibrated Routes post. This will result in the merged routes (which may be composed of several ordered parts) being added to the route feature class created in step #3 above. Start an edit session and delete all the unmerged routes (they are the ones with the _ underscore in the LABEL field) and save. You should now have 1 route feature per route (approximately 260 routes).
5. QC Simple Route Features. Rules that must be enforced include
M Coordinates must ordered with the direction of the route feature (0 must be at the start point) and must be increasing across the entire route feature. This means that correct ordering of the parts is essential and is why this is done with a script instead of with the ArcMap merge functionality.
M coordinates can be repeated where vertices are within the resolution (5 feet) of one another but more than one 0.000 m coordinate is not allowed in the Oracle environment
Other requirements here...
6. Apply Intermediate Calibration Points to Route. In an ideal world, the mileposts are the monuments for the linear referencing system and a high-precision location would be available for all mileposts in order to provide for a dense, precise mid-route calibration. Until they are all collected, a set of midpoint calibration points can be employed from the UTRANS.TRANSADMIN.UDOTRouteReferencePoints feature class. This process is described in the post ArcMap .Cal Script: Refine Route Calibration with Milepost Point where a .cal script is currently utilized (needs to be slightly expanded to work across multiple routes.
7. Build X Routes. Description needed here.
8. QC Intermediate Point Calibrated Route Features. Same rules under step 5 above need to be assessed.
9. Load Routes into SDE Feature Classes. Archive the existing route feature class before loading the new routes. To load the new routes, use the 'Delete Features' command in the ArcGIS command line interface to truncate/empty existing routes and then, in ArcCatalog, right click on the newly emptied SDE route feature class and select the 'Load' context menu option use the simple data loader to import the new routes into SDE. Do this for route feature classes in both the UDOT (UDOT.UDOTADMIN.AGRC_Routes_IPCalibrated )and SGID93 (SGID93.TRANSPORTATION.UDOTRoutes_CalibratedIP) databases. IP stands for intermediate point calibration. Shapefile and FileGDB files on the SGID ftp site should also be updated.
10. Derive and Update Interpolated Milepost Points. Until a complete, high-precision set of mileposts are available, an approximation of milepost locations can be derived using the process described in this post.VBA: Generate Milepost Locations From PolylineM Routes. The mileposts generated throgh this process currently get loaded into SGID93.Transportation.UDOTMileposts_Approx. Shapefile and FileGDB files on the SGID ftp site should also be updated.
11. Recalculate Milepost To/From Ranges on Centerline Road Features (AGRC). Use the code in this post,VBA: Transfer Milepost M Coordinates From Route To Features, to update the fields DOT_F_MP and DOT_T_MP in UTRANS.TRANSADMIN.StatewideStreets.
You have a layer of polygons, say grazing permits, that are mostly based on another layer, say state and federal land ownership. Let's say the base data layer, land ownership, gets updated due to an improved survey. Is there an easy way to make the geometry adjustment to the grazing permits.
There are a couple of options to explore within the ArcMap UI, namely:
Spatial Joins.Good approach but creates a new dataset as a result and sometimes the dataset + dataset = new dataset approach doesn't meet requirements and/or makes an unnecessary mess
Spatial Adjustment toolbar --> Attribute Transfer tool, Geometry Transfer option. Also a good approach but involves mouse clicks, is not customizable, and doesn't resolve matching between single and multipart features
Here is another option, a .CAL script to run in the ArcMap field calculator on a selected set, within an edit session.
TO USE:
open the attribute table for the target feature class (grazing in the example above), select one or more features (start with one at a time).
Right click on the SHAPE field or hit CTRL + SHIFT + F to open the field calculator.
In the field calculator, check the Advanced Option box and paste the script below in the Pre-Logic VBS Script Code text box.
Make sure that the source layer number script parameter is set, This can be found by searching for SET THIS in the code. Set the layer index number for the polygon layer with the source geometry
In the bottom box, under Shape =, type in: pOutPolygon
Notes:
If you're running this on a big selected set, the message box (shown below) will bug you. It can easily be disabled or deleted if desired. It's at the end of the script and can be disabled by sticking an apostrophe (') in front of it to comment that function out.
