Latest Contributions by WesKing

If using sdo_geom, is there any way to get the SHAPE.AREA and SHAPE.LEN to populate correctly?  Yes, other fields could be added to store this geometry info., but I'd rather not do that if possible. Thanks in advance, Wes ... View more

Thanks JSkinn, that worked great. Wes ... View more

Hi Mouseam, Thanks for your reply!  Keep in mind I'm not a DBA or Sys Admin so my understanding of these things is minimal. We've been looking into things further after discovering this problem and found we're pretty sure it has nothing to do with privileges.  What I said in my first posting turned out to be incorrect. Here's what we know at this point.  When creating a new table everything works as it is supposed to (text fields = VARCHAR2, etc.).  However we have some tables that show up as "SDE Table" types and some that just show up as "Table".  If we add a new text field to these tables it is NVARCHAR2.  Important to note, we do have 2 database instances but these tables are in the instance where the DBTUNE table had the setting for UNICODE_STRING FALSE and can't be modified from the other instance.  These tables say they are registered with SDE, but I believe since they aren't SDE_Table types, they are not using the DBTUNE table when changes are made (adding a field). After this info., do you have any ideas?  Do you know the difference between a "Table" and "SDE_Table"?  Could it be that the table was created outside of Arc? Our character set is WE8MSWIN1252 Thanks, Wes ... View more

Thought I'd post something else I found that worked great. When creating overviews start by defining overviews (don't just build overviews).  In the Overview Tile Parameters I changed the default value of 3 for the Overview Sampling Factor to 2 and in the Overview Image Parameters make sure the Resampling Method is Bilinear or Cubic.  This creates many more overviews, but it gave me exactly what we needed; higher quality overviews and soooo much faster when zooming to different extents. Wes ... View more

Hi, Have you seen this ESRI white paper?  It's a suggested read for your project. [URL="http://www.esri.com/library/whitepapers/pdfs/lidar-analysis-forestry-10.pdf"] Hope this helps.  It's a great paper!!! Wes ... View more

Hi Everyone, I've learned that at least one way of removing the grainy appearance at full extent is when adding rasters to the mosaic dataset, under 'Raster Pyramid Options', the smaller the value for 'Minimum Rows or Columns' the smoother the full extent appearance. The default is 1500, but only when I set it to 100 does the appearance look the same as a true mosaicked image (all tiles mosaicked into one new raster).  However, this seems to make the performance much slower. Mosaic datasets seem to be the way raster storage is headed for now with ESRI and from my reading of the different raster types it does seem to be correct.  But if I can't make our rasters look good...at all extents...and have good performance, I'm being told we won't go that direction.  I want to believe that I just don't fully understand how to accomplish building a mosaic dataset that looks decent at full extent.  This seems to basic...what am I missing? Thanks, Wes ... View more

Thank you, the processed setting does work and it works as a default so when others bring it into their document it displays as intended. I understand there may be many reasons for the coarse/grainy appearance at full extent, but can I bother you (or anyone else) to list a few of the most common reasons.  I've researched all over and can't find anything that talks about this problem.  Most of my parameters were defaults (not all) so I'm sure this has got to be something others have run into also. Thanks again! Wes ... View more

Thanks Jonathan, I was hoping for something quick and easy (already available in ModelBuilder), but I know it's rarely that easy. Thanks again for your response. Wes ... View more