ESRI UC - Day 1

View from my room
So imagine my complete and utter surprise when I walked into the SDCC, where I thought I was going to know no-one except my SRK colleagues that I had yet to meet, and the first person I see is a fellow AU presenter Gordon Luckett of Arrow Geomatics! It is truly bizarre that in a sea of over 13,000 people, that I just happened to walk in that particular entrance, and Gord happened to be standing right there... All I can muster is bizarre!!!! I was great to catch up with Gord, and I'm sure we'll cross paths this week.

Anywho... As I mentioned previously, today was the Plenary Sessions to kick off the conference. Jack Dangermond discussed his GIS Vision for the coming year, and years, followed by various technical demonstrations. Highlights of the sessions included:
  • ArcGIS innovations including new features of the upcoming 10.1
  • ArcGIS Online improvements
  • 64 bit support
  • Improved LiDAR support
  • Geodatabase administration tools
I managed to track down my SRK colleagues and finally meet some of the people I have had communications with over the last 11 months.

Keynote speakers included:
  • Timothy T. Schilling and Michele Adesir-Schilling discussing the Green Living Project, which enabled Rwandan coffee farmers to produce a better quality coffee bean to supply the international specialty coffee market.
  • Jacqueline McGlade, director of the European Environement Agency, discussed the 'one degree' change in temperature, and how it will impact the earth.
Well, I need to figure out my sessions for tomorrow, so until next time, take care.

Warren

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