POST
|
If the points are joining the polygons, each point will be assigned the ID/attributes of the polygon it intersects. If polygons are joined to the points, there is only one record for each polygon - and thus only the first point it intersects to record. If that is not a fix, maybe the intersect tool will work. The output will be a point layer, but should contain the polygon ID that intersected each point.
... View more
10-11-2011
08:45 AM
|
0
|
0
|
216
|
POST
|
This reflects the nature of the data. Can't recall the exact explanation, but using floating point numbers is what this shows. Your solution to set the number of decimal points is the answer. The values are accurate, but displayed based on the width of the field.
... View more
09-29-2011
08:01 AM
|
0
|
0
|
203
|
POST
|
Not sure if it gives you any clues, but I was able to change a properly aligned legend to one with points offset by changing the label font size. Mine shifted in the opposite direction, the point markers were then higher than the label text. Did you do any resizing of text or markers after the legend was created? If this is not a lead, I don't have any other ideas.
... View more
09-19-2011
09:53 AM
|
0
|
0
|
521
|
POST
|
If the attributes are of the same width (that is, all have 4 numbers), use the LEFT function. If not, you may need to query and TRIM the appropriate number of characters as needed.
... View more
09-14-2011
07:04 AM
|
0
|
0
|
165
|
POST
|
Quick google search turns up: http://gislounge.com/arc-macro-language-aml/ This site has links to good resources. Some with tutorial style info: http://gis.washington.edu/phurvitz/arc_lms/week9.html http://www.fsl.orst.edu/helpdesk/gis/aml.pdf Ah, I miss using AML...
... View more
08-24-2011
12:11 PM
|
0
|
0
|
492
|
POST
|
Any luck with this yet? We have thorough SOPs that you could maybe look at for ideas. However, you are right that the content would need to be replaced in its entirety. Some questions to ask before you get too far: 1) Must the manual describe dummy-proof steps and settings, or more general terms? Is it to be used as a step by step guide for new techs? 2) Should the manual avoid command/tool specifics in order to remain relevant with software changes? That is, are conceptual steps or detailed tool settings more important for this document? 3) Is project history or context relevant to the document? A user who needs to know the big picture will call for more information that is not part of processing steps. Other things are sure to be included, such as layers, field definitions, and the like.
... View more
08-22-2011
11:15 AM
|
0
|
0
|
209
|
POST
|
I'm not a python script writer, but maybe there is a way to assign the RGB symbology using the attributes in an automated way?
... View more
08-18-2011
08:43 AM
|
0
|
0
|
451
|
POST
|
I think kimo has the right idea - points along the roads, 2*r apart, which can then be buffered. It might require simplification of the road network to create, but the resulting circles could be used overlaying the original complex road network. Using a linear event theme, this would be a fairly straightforward process. Have you thought about using a hexagon grid? This could be generated from an arbitrary starting point.
... View more
08-16-2011
08:48 AM
|
0
|
0
|
212
|
POST
|
In the layer properties, you can st the symbology to be "unique values, many fields." Each combination of the fields you choose (up to 3) can be assigned a different symbol.
... View more
08-16-2011
08:13 AM
|
0
|
0
|
451
|
POST
|
I remember seeing something like this with text labels - it had to do with the string being center or left justified. Do your representations have different justification or offsets? The default symbols (the ones lined up correctly) should have no offsets...
... View more
08-16-2011
08:10 AM
|
0
|
0
|
521
|
POST
|
Is there any chance that the values -1 to -0.4 and 0.7+ only lie within the area you have masked?
... View more
08-11-2011
12:27 PM
|
0
|
0
|
186
|
POST
|
Have you tinkered with gradient fill for your narrow polygons? Not sure if it will work consistently with a data defined 'from' and 'to', but it might be worth a look.
... View more
08-11-2011
11:56 AM
|
0
|
0
|
927
|
POST
|
Are your grid rectangles defined by a centroid? Also, is it possible to use the grid layer as a feature class for your purpose?
... View more
08-11-2011
11:53 AM
|
0
|
0
|
163
|
POST
|
I haven't geoprocessed that many features since v9, but right away would lean toward using raster. You might be looking at overnight runs to let the machine churn through the large number of records. A factor to consider is how precise your data must be. Consider the number of raster cells you will need versus the number of polygons you'll process. If you need 10 million grid cells, but only half a million polygons, the latter might work better. Are your slope values from a 30m DEM? Your grid cells should not be less than 10m. If from LIDAR with cm accuracy, this would give you vastly different needs. Raster processing would be simple, really. Assign values 1-6 for Input A. Add this (using the raster calculator) to values for Input B (values in multiples of 10) so that the possible output values are unique. Every combination of A and B has a unique sum in the output.
... View more
08-05-2011
08:51 AM
|
0
|
0
|
410
|
POST
|
You might try buffering the line to an polygon of apt width. Different values can be different polygons with their own symbols.
... View more
08-05-2011
08:22 AM
|
0
|
0
|
927
|
Title | Kudos | Posted |
---|---|---|
1 | 03-07-2018 01:39 PM | |
1 | 06-16-2011 08:44 AM |
Online Status |
Offline
|
Date Last Visited |
09-28-2023
11:24 AM
|