Latest Contributions by ChrisDonohue__GISP

Some ideas: I suspect you need to do some data cleanup.  For example, the MyEurope table shows some Nulls in the CNTRY_NAME field.  Therefore you will have to decide what to do with those records, as they lack the information needed to do the Join.  If they are needed, populate the CNTRY_NAME field for them as appropriate.  If they are not needed, I would export a copy of your data by selecting all the CNTRY_NAME IS NOT NULL and then proceed with that  exported file to do the Join.  Take some time to go through your data and see if it makes sense. After you do the Join, save the joined dataset off as a new feature class.  This will make the the feature class with the information permanent.  Make this layer time-enabled. This can help avoid an wierdness that can crop up due to an active join. Chris Donohue, GISP ... View more

I managed to get it to work, but am now puzzled as to why you are getting the invalid characters error.  Can you recheck the paths and file names to ensure that their are no restricted characters being used?  Keep in mind that in the raster-processing world there are severe restrictions on what can be used for filenames, so that may be what is tripping things up. Check to see that all the folders in the path and all file names that have short letter names, numbers, and underscores only.  Also, if numbers are used, make sure they are not the first character in the file name, as this will cause some crashes.  Chris Donohue, GISP ... View more

In regards to the shapefile issue, I did notice this morning when I set up a quick Iterate Rasters that if the result from the Raster to Polygon is sent to a geodatabase it continually tried to add the .shp to the output unless one sent the output to a Feature Dataset within the geodatabase. So in other words if the output is sent to the base-level of the geodatabase, .shp will be added by default (even though this is not correct).  So I'd start by creating a Feature Dataset within your geodatabase and send the output to that. As to the invalid characters error, at least at first glance I don't see why that is triggering. Chris Donohue, GISP ... View more

Assuming you are using ArcGIS Desktop, what I suspect has happened so far is that you copied the layer in the Table of Contents, which appears to have created a new layer but actually just creates another link back to the same single dataset.  So at this point you have two choices - either use a Query to modify what is being displayed for each layer shown, or make an actual permanent copy of the data and edit that. If you want to go the query route, right-click on the layer, Properties, then Definition Query tab.  Then in the area below define a query to affect the data displayed.  Given the example you stated, it probably would be something like YEAR = 2014, As for the create a new permanent layer route, go to the feature class in the Table of Contents, right-click, Data, Export Data Exporting features—Help | ArcGIS for Desktop  Chris Donohue, GISP ... View more

I'd start by looking at how your data is stored, as at least by the error message there appears to be some strange things potentially going on. 1.  Iterate Rasters is typically done by iterating rasters in a folder.  One solution may be to copy your rasters to a folder and then run the iterate against that folder. Summary Iterates over rasters in a Workspace or a Raster Catalog. Iterate Rasters—Help | ArcGIS for Desktop  2.  At least from the path shown in the error message, it almost appears that you have a shapefile stored in a geodatabase.  That's not possible.  Check to see if actually have shapefiles or instead have feature classes in a geodatabase.  If feature classes are being accessed, the filename will not end with .shp. 3.  The geodatabase SLR Results.gdb appears to have a space in the name.  If there is a space, try renaming it with and underscore _ .  It's not well known, but many processes in GIS bomb out if there is a space in anywhere in the path, including the filenames and geodatabase names. Chris Donohue, GISP ... View more

If you are using ArcMap, you can manually change the zoom level of the Extent Indicator to get started, then set it to an automatic mode .  Here's what you do: 1.  Look at the Table of Contents for the Extent Indicator Data Frame.  It is usually defaulted to "New Data Frame" but may also have been renamed. 2.  Right-click on the Extent Data Frame name in the Table of Contents and choose "Activate" 3.  You can now use the zoom tools to zoom in or use the Map Scale pulldown (or manually type in the map scale) 4.  To make this more automatic, one can also go to the Data Frame tab and set the Extent to Fixed Scale or one of the other options. Note - if Data Drive Pages are being employed, there are some other options (though that's another major discussion in itself). Chris Donohue, GISP ... View more

I have not used the LGIM, but know from working with the Stormwater folks in updating our Floodplain and Floodway that the Floodway is based on a single flood scenario, so I doubt in LGIM that any codes in the Floodway field translate to "Fair Weather" or "Wet Weather" or any varying weather condition. If I had to venture a guess, I suspect that the Floodway field exists in LGIM to help designate a Floodway polygon from the other types of flood polygons, while still allowing flexibility to show all the other data.  For example, in our FEMA data Floodway is a subtype found in "AE" flood polygons. In other words, only some "AE" polygons are Floodway, but all Floodway polygons are "AE" designation. A "Regulatory Floodway" means the channel of a river or other watercourse and the adjacent land areas that must be reserved in order to discharge the base flood without cumulatively increasing the water surface elevation more than a designated height. Communities must regulate development in these floodways to ensure that there are no increases in upstream flood elevations. For streams and other watercourses where FEMA has provided Base Flood Elevations (BFEs), but no floodway has been designated, the community must review floodplain development on a case-by-case basis to ensure that increases in water surface elevations do not occur, or identify the need to adopt a floodway if adequate information is available. Floodway | FEMA.gov  Chris Donohue, GISP ... View more

jborgion : If I can ask, what are the aspects of addressing that need to make it "defendable in court"?  Is that particular to 911 Response issues?  Or are there other legal responsibilities/liabilities that come with addressing? Chris Donohue, GISP ... View more

If you have access to an Advanced ArcGIS license, there is a handy geoprocessing tool that will accomplish what you need. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Tabulate Intersection (Analysis) Note that you will want to fill out the Class Fields (optional) and Sum Fields (optional) settings. If you don't have access to an Advanced license, it could get a bit more involved depending upon your data.  One could run an Intersect (Analysis), then in Excel do a Pivot Table.  The tricky part will be if you end up with multiple polygons of the same ID in the same Fishnet, as the multiple polygon with the same ID will be be listed separately and not aggregated. Chris Donohue, GISP ... View more

Joe: Just curious - for situations where there are multiple entrances to a facility, do you supplement the official address point(s) with additional "access" points so the routing goes to the closest entrance?  Or is there a better way to handle this situation? Chris Donohue, GISP ... View more

Interesting. As for the address change suggestion by the vendor, I suspect their may be a minor amount of pushback from the affected parties.....  Chris Donohue, GISP ... View more

So just to confirm, the goal is a polygon that represents 80% of the merged area?  Were there any other parameters concerning how/where the 80% can be? Chris Donohue, GISP ... View more

One method: 1. Convert your raster to a vector feature class.  ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Raster to Polygon 2. Start an Edit Session on the new vector layer from step 1. 3. Select by Location all polygons from the vector layer made from raster that Intersect the source layer feature of the polygons in your other layer. ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Using Select by Location. 4.  Switch Selection to come up with the polygons that don't cover a polygon in the other layer. 5.  Delete those selected. 6.  Save edits, then close the edit session. Chris Donohue, GISP ... View more

In ArcMap, one way to check on the license level you have: Chris Donohue, GISP ... View more