I’m back… Again…

Well, it has certainly been a while...

Between work, family, and extracurricular commitments, as well as trying to complete the final course for my GIS degree, let's just say there aren't many hours (minutes) left in the day. But, that's no excuse, and I'm going to try hard to maintain at least a bi-weekly post.

So it's been a few months now at my new position with SRK Consulting and it's been going really well. I've learned a great deal about the mining industry, and there is much more to learn, and all-in-all this has been an exciting time.

The mining industry uses many different, niche, applications for very specific tasks, and I'm looking forward to learning more about these applications. In my new role I'm working closer with the Arc* family of products and having spent a good portion of my career on the Autodesk side of things, it's nice to dive a little deeper into the Arc products. Specifically, I've been working with the ArcSDE geodatabases to better understand how these products are being implemented and configured within a spatial database environment. I want to continue to improve the interoperability between various tools, and understanding more about how SDE is configured will help this.

As I have done previously on this blog, I'm going to discuss technical topics related to the various technologies I'm using.

Today's tidbit:

3demI recently needed to combine multiple DEMs into a single DEM. The Arc* products do have tools to create a merged image or grid of this DEM data, but I simply wanted a single DEM file created from multiple DEM files. A quick Google search identified a tool called 3DEM. This free tool provides a lot of functionality in addition to what I needed it for including 3D terrain visualization and the ability to create flyby animation's. The program consumes DEM data in a variety of formats including: the standard USGS formats (DEM, SDTS), LAS files, XYZ, and others.

Unfortunately, this tool is no longer in development, but the author has give the site Free Geography Tools permission to host the last version of the program.

Check out this post for details, and click here to download the program.

Until next time…
Take care,

Warren M

Comments

Post a Comment

Popular posts from this blog

ArcGIS: Packaging error - General function failure

Image
Whoa... 2 posts within 2 months...  I'm on a roll baby...   :-) In today's episode I want to document what I've discovered with the following lovely error when attempting to create a Map Package: I've had this very insightful (hint:sarcasm) message box pop-up a number of times when trying to create a Map Package.  After much copying/pasting, renaming, re-connecting data sources I finally figured out what the problem was in this particular instance. This particular map had some DWG files connected to the map, and some of these DWG names contained a special character "#", and also contained extra 'dots' in the name to delimit a date.  For example: Name#-2013.04.09.dwg In my testing and trials, removing the '#' symbol did not resolve the issue, and it wasn't until I removed the extra 'dots' in the name that I was finally able to successfully generate the package.  Further testing revealed that the '#' symbol
Read more

More ArcGIS Woes with 'Special' Characters...

Image
It's no secret that I've griped and complained about many of ArcGIS's quirks that seem stuck or rooted in the 80's ...  One would think I wouldn't be surprised anymore when I come across such silly issues... But I am. The latest 'undocumented feature' I've discovered is that the Field Calculator will fail if there is forward slash ( '\' ) in the Layer name. ArcGIS 11 can't come soon enough.
Read more

ArcGIS Collector: Update Error Code 1006

Image
Alright, this is the second time this happened to me, and I neglected to document it the first time, so I had to search again to find the answer, so I will document it here, and now. Here goes... If you happen to come across ArcGIS Collector throwing an error when updating a feature, and the error states something along the lines of: Invalid untrusted Html content detected in field: Have no fear, there is a simple fix.  Well, that is, it's a simple fix if this is 'local' map, not accessible to the general public.  That's only because ESRI doesn't actually 'recommend' this fix. So what is 'this fix' I speak of? A little more background... If you have any fields that contain HTML content, there is a chance that Collector could see that as malicious content, and it will block it.  You can see a list of allowable HTML tags in Collector a this link . In my instance, I am running some database triggers to populate and update a URL field, where
Read more