Latest Contributions by DarrenWiens2

Please post your python script and the entire error message, which should indicate which line caused the error. ... View more

As a followup to Chris and Dan's ideas, here is how to set the scale range for your layers: ... View more

You need more information than what you've provided so far. For example, were the original points collected according to the Greek_GCS? What projection, if any? What are the units for 117N and 140E (degrees, metres, etc.)? Depending on some of these answers, you may be able to just add a certain amount of degrees to each coordinate, or it may be a very convoluted formula. ... View more

I know the original projection of the map with which they recorded locations, and also the coordinates of their origin point. If I understand correctly, you can create a custom coordinate system using the original projection as a starting point, and change the false easting and northing parameters to account for the offset. Once you've got the points entered and defined by your custom projection, you can Project the points to whatever standard coordinate reference system you'd like. ... View more

Now that I see this again, a more compact alternative may be (only lightly tested): def StreetSuffix(FacilityAddress):    replace_dict = {     'ST':['STREET','STREET,','STR.','STR,','ST.','ST,'],     'WY':['WAY','WAY,','WY.','WY,']   }   list = FacilityAddress.split()    for item in range(len(list)):     for key, value in replace_dict.iteritems():       if list[item] in value:         list[item] = key   return " ".join(list)     ... View more

There is Find and Replace in Table options. ... View more

This is a common enough issue that there is a Knowledge Base Article devoted to it, here. Basically, try saving as TIFF as an alternative to meeting ESRI GRID requirements, or upgrade to 10.2.1+ to overcome feature count limitations, although 1800 features should be manageable. ... View more

Layer Properties -> Display Tab ... View more

Does it help if you Remove Join? ... View more

Can you explain what you mean by "information model"? Try running Check Geometry to see if there are any issues with your road centerline feature class. ... View more

Do you mean, how to build a label expression​, or something different? ... View more

Update - I did get it to line up by a trial and error process of customizing a projection file, but would still like to solve the georeferencing issue. I can't help with your georeferencing issue, or the fact the engineering firm was no help, but it does sound like they are using a custom coordinate system. There must be someone at the firm who knows how to translate the coordinates into a standard CRS. Whether or not the CAD operator knows it, the software is obviously using a CRS. I've run into this relatively often with custom local UTM zones from CAD, which have either a false easting or northing, and with some prodding the engineers should be able to tell you. The secret term that seems to twig the engineers' memory is "ground coordinates" (which they use) vs. "grid coordinates" (which are the standard UTM coordinates). ... View more

If you're staying completely within vector methods (no raster), cell size shouldn't be a factor. Calculating areas through field calculator is the "true" area. Cell size is a factor with raster operations that report area based on the count of square pixels (e.g. if the area of one pixel is 100m^2 and the tool reports in units of cell size, if it tells you '5', that means 500m^2, not 5m^2). As for units issues, confirm that all of your layers are in the linear units you think they are, in Layer properties, Source tab. ... View more

I see you've got your answer, however I think you can benefit from an 'elif' between the Benzene comparisons. Without 'elif', a value of 80 will get a red label (>79) followed by a green label (>0). With 'elif', a value of 80 will get a red label, then skip the >0 comparison: def FindLabel ( [NAME], [Acetone], [Benzene], [1_3_Butadi]  ):    message = ''    if int( [Benzene] ) > 79:        message = message + "<bol>" "<clr red = '255'>"+"Benzene:" + [Benzene] + "</clr>" + "</bol>"+ "\n"        message = message + "\n"     elif int( [Benzene] ) > 0:       message = message + "<bol>" "<clr green = '255'>"+"Benzene:" + [Benzene] + "</clr>" + "</bol>"+ "\n"       message = message + "\n"    if int( [Acetone] ) > 0:        message = message + "<bol>" "<clr green = '255'>"+"Acetone:" + [Acetone] + "</clr>" + "</bol>" + "\n"        message = message + "\n"      if int( [1_3_Butadi]  ) > 0:        message = message + "<bol>" "<clr green = '255'>"+"1,3-Butadiene:" + [1_3_Butadi]  + "</clr>" + "</bol>"+ "\n"        message = message + "\n"    return message ... View more

You likely have basic licensing. Intersect should work - just be aware that it will only return the areas that are covered by both a sub-basin and a land use polygon. It can be an issue if, for example, one of the sub-basins is only covered 50% by land use, and then the summed percents will not add to 100%, but as long as you know what you're getting into, it's not a problem. ... View more