CeranWrap

We are so used to seeing the geographic map color coded per election results. Did you ever wonder how those colored blue could win when there seems to be so much more red? This is because the geographic map does not accurately depict the real numbers being used. Our elections are not based on the size of the state, nor the population. Elections are won based on the number of Electoral Votes that exist for that State.    Take Montana as an example. It is a large state and is colored red. Compare that with Washington which is blue. Using the map above, a person would see more red than blue, giving the impression that Montana means more than Washington. However, Washington carries twelve (12) Electoral Votes while Montana only carries three (3). This is why we are starting to see Electoral based maps, like the one above. The geometry is altered to fit the Electoral Vote sizes appropriately. Click the links below to view some interactive Electoral based maps.  Don't forget

First, run a query to identify the feature class "PhysicalName" or UID from GDB_ITEMS. Note: The physical name appears as DBNAME.SCHEMA.FCNAME. Use one of the two for the WHERE clause in the other queries. First Query USE [DBName] SELECT ITEMS.ObjectID ,ITEMS.UUID ,ITEMTYPES.Name as ItemType ,ITEMS.[PhysicalName] ,ITEMS.[Definition] FROM [sde].[GDB_ITEMS] as ITEMS INNER JOIN [sde].[GDB_ITEMTYPES] ITEMTYPES ON [ITEMS].[ Type ] = [ITEMTYPES].[UUID] WHERE [PhysicalName] like '%FC Name%' In the results, click the XML link under the Definition field. You should see something similar to the XML below. Notice the highlighted line of code. This is the "Remarks" field. The node "IsNullable" is set as "false". I want the Remarks field to allow NULL values and would like to update it from "false" to "true". Note: The base and delta tables should be updated as well. XML Definition View <DEFeatu

Esri Professional Services just released an updated version of mxdperfstat. A great tool to help you optimize GIS services. Per their documentation the key features include: Performance report for each scale Performance report for each layer including diagnostic statistics Optimization recommendations This update includes the tools that support Esri version 10.4. Updated Mxdperfstat Link

This one is helpful if you have many MXDs located within a folder that need a layer replaced. For those who create Map Books, this could come handy. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 # Name: Replace layers in MXD TOC # Purpose: This script is meant to be added to an ArcGIS Toolbox. # It will copy all MXDs within the specified directory to a folder on your desktop. # Then it will scan each MXD in that desktop folder, looking for a layer name, per user input, # and replace with an existing layer file, per user input. # Author: Nicole Ceranek # Date

I have several enterprise level geodatabases (GDB) to manage. Instead of setting up maintenance scripts for each project GDB, I decided to write one script to manage them all. (Get the movie reference?) This script requires two directories to be setup 1) OwnerFileDir and 2) AdminFileDir. The first will store several SDE owner connection files; one per database. Owner is usually "dbo" or "sde". The second will store several Esri object owner connection files; one per database. The Esri object owner is the user that owns each object's schema e.g. < DatabaseName >.< Schema >.< PolygonFeatureClassName >. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86