POST
|
The number I was looking for was NIM084360 from 9/2012; perhaps it is the same thing? My access to this forum at work is horrifically slow, so I would not have looked for another bug. Hi Dana, Are you referring to NIM071576: The Feature to Point tool creates a different center point when the option to constrain the point to the inside of the polygon is enabled, but the center point is actually inside the polygon. ? If so, it shows as having been fixed in the next release. Best, Melanie S.
... View more
02-25-2013
07:13 AM
|
0
|
0
|
422
|
POST
|
This is registered as a bug for 10.0, but I am not clear on the status since I can't find the bug report. Was this fixed in 10.1 or do I have to work around this for my SDE data? http://forums.arcgis.com/threads/29346-Calculate-the-centroid-of-a-polygon-in-ArcMap-10.0?highlight=feature+point+centroid The problem is the "inside" option of feature to point does not place the centroid anywhere near the center, as it does with Calculate Geometry or with FtoP without the "inside" option selected. [ATTACH=CONFIG]22047[/ATTACH]
... View more
02-21-2013
07:46 AM
|
0
|
5
|
558
|
POST
|
This is very common and is probably related to the printing engine, transparency, and just too much information/layers for the buggy interface ArcView uses to print. (Labels also disappear sometimes on multiframe maps.) You can try fiddling with the resolution by making the output-page size bigger or by reducing the resolution of the export. You could also try exporting to a lossless format like TIFF and creating a PDF from that if you have a PDF creator like full Acrobat, but this doesn't work very often. The last resort is exporting parts of the map separately and reassembling them in Illustrator or similar tool, if you have access to one.
... View more
04-01-2011
09:04 AM
|
0
|
0
|
6667
|
POST
|
It looks like you need at least one more field as a key. MUID is a unit identifier, while chorizons are more detailed, so this is a many-to-one relationship to MUID. The likely candidate key fields are component and chorizon. I haven't done any work with the newer format soils data, but see especially pg2-35 in this document: ftp://ftp-fc.sc.egov.usda.gov/NSSC/guidebook/Using_the_SSURGO_Template.doc for an Access example.
... View more
03-30-2011
04:29 PM
|
0
|
0
|
826
|
POST
|
Can you tell me how I would vew the source code of the html popup? I can view it in the KML file and do not find anything wrong (other than the field aliases being truncated). Rob This is sounding like a little ESRI bug when generating or transforming the XML; XSL does have a replace function that could take out one letter, I suspect because you have spaces in your aliases. To look at the popup source: View Source will only show you the XML. I use Firefox with Firebug (this is a miniapp that can be added to Firefox) to view the hidden HTML. This requires navigating away to a new tab from the XML page and then back after opening it in Firefox. Right now, this isn't working for me because Firefox is not playing nice today, but it was when I was developing my XSL.
... View more
03-01-2011
08:59 AM
|
0
|
0
|
341
|
POST
|
Are you talking about the field labels that come from the aliases (FieldName) or the content (FieldValue) of one of your fields? Which HTML popup XSL are you using? If it is custom code, there could be an error in it. Do a View Source on the popups with problems to see if the XML has the contents you would expect for that record.
... View more
02-22-2011
02:52 PM
|
0
|
0
|
341
|