Latest Contributions by MalcolmNunn

Very simple fix! Thanks Jake. ... View more

This problem is continuing to rear it's head. I created a new blank MXD, set up new data frames, added a new basemap fresh. Initially service layer credits were displaying correctly, then somewhere along the way of copying in layers and elements into the new map layout, they disappeared and stopped working. Getting very frustrating when attribution is part of the licensing for using the basemap imagery, yet the software isn't even displaying it on the imagery itself. ... View more

I'm not sure about what happens if I use MXD doctor after creating a new map document with a working dynamic link to service layer credits. Dragging over layers doesn't fix it (service layer credits will be blank in the old MXD). I have noticed that the problem is specific to data frames existing in the old MXDs. If I create a new data frame within the document and add a basemap to that, service layer credits will display correctly. I have a lot of old templates and maps that need to be updated - would prefer not to have to create a new data frame in every one, copy over features, resize and set extent, and re-do the legend! ... View more

Hi Anna That's correct Anna. I am working with ArcGIS Desktop Basic 10.1 (SP1). If I begin with a new map document, I can get service layer credits to display correctly. These MXDs are ones that existed previously that I am updating, however as far as I can tell they are also the same version. Using MXD Doctor to copy everything out into a new MXD results in the same problem carrying over though - I still can't get the service layer credits to display! ... View more

Noone else come across this problem? Making it difficult to correctly reference the ESRI layers as attribution requires. ... View more

Hi Matthew Thanks for the response, it does clarify this a little bit. I think my confusion actually lay in whether object properties could be directly accessed without creating a Describe object. For example, accessing the raster bandCount property from the raster object directly without creating a Describe object. After a little experimentation I find that this is indeed possible - my problem was that in the method I used of listing datasets then looping through the list, the iterable item was actually unicode and needs to be converted into the correct object first, ie: import arcpy arcpy.env.workspace = r"C:\Users\uqmnunn\Documents\Borneo\spatial_data\DataInventoryTool_test" datasets = arcpy.ListDatasets("*", "Raster") for d in datasets:     print("Raster dataset found: %s" % str(d))     print("Band count:%d" % d.bandCount) Will return an AttributeError to say that 'unicode' object has no attribute 'bandCount'. However, converting d to a raster object first makes it possible to access raster object properties directly without a Describe object:      d = arcpy.Raster(d) So thank you for the explanation of Describe, and now I have clarified my other misunderstanding about accessing object properties without Describe! Cheers Mal ... View more

This post was from a few weeks ago but since it is something I've just been trying to deal with, thought I'd attempt to give an explanation. My understanding of this is that while FAC determines what gets classified as a stream, stream segmentation (and thus the generation of drainage points and catchments) is essentially a function of the branching of that network. You might set a relatively large FAC threshold so that only major rivers are defined - but if that major river network has segments that are quite dendritic in a short stretch, you end up with a drainage point at every convergence, and many catchments that are very small compared to the drainage area used to initially define a stream. The flip side of this is that if the generated drainage network has no feeder streams or convergences for a long stretch, there will be no stream segmentation along it, no drainage points midway, and Arc Hydro will delineate you one main, large catchment - instead of nice equal area divisions of your watersheds! EDIT: I did this example before I re-read the post and realised that you said you were getting surprisingly few catchments large catchments, not many small ones. Will leave it for illustration of the segmentation and catchment delienation process however. For example, in the image attached I used a large FAC threshold to define streams (24 000 cells at 93 x 93 m, so ~ 207 km 2 . Segmentation is performed at each convergence and a drainage point generated (red dots). Segments one and two converge first, then the third happens to converge a short way downstream. The result is catchments of reasonably appropriate size upstream of segments 1, 2 & 3 before they converge. However, just upstream of where 1 & 2 converge with 3 is a tiny catchment < 1 km 2 - which is an area far far below the sort of drainage area used to define the streams initially. [ATTACH=CONFIG]33316[/ATTACH] Hope this helps - note I could be wrong about how it works but this seems to make sense in the context of results I've had. To avoid or control this, I guess you would need to manually select or set drainage points rather than Arc Hydro delineate automatically on all drainage points. If you wanted to break up your large catchment into smaller ones, then I'd suggest setting more drainage/delineation points along the stretch of stream that needs to be broken up. As Mark said above - this is where setting batch points or using other tools comes in handy, rather than using the automatically generated catchments/drainage points as your final delineation. Cheers Mal ... View more

Assuming that the data you wish to mask by the India shapefile are features, use Clip in the Analysis toolbox to clip the input features to the India shapefile. If you have interpolated points to create a raster, then you can use Extract By Mask in Spatial Analyst to perform a similar operation. Cheers Malcolm ... View more

Having said that - it could be that the FAC input grid must be specified as an input parameter and loaded as a layer in the current MXD for the tool dialogue to be able to automatically populate Number of Cells from Area SqKm. Depending on how many times you have to run your model with different inputs, I would suggest the simplest thing to do would have a list set up of your desired areas (eg Excel spreadsheet) and their corresponding Number of Cells, and just enter the values manually. (assuming your input raster CELLSIZE is in meters): NUMBER OF CELLS = (AREA SQKM * 1 000 000) / (CELLSIZE^2) Then for your model, have input parameters for Number of Cells and Area SqKm, make sure that Area SqKm is set to blank (assuming the same issue I previously mentioned) and specify the number of cells according to your conversion sheet. Cheers Mal ... View more