Latest Contributions by V_StuartFoote

David, Probably best to do it outside of ArcGIS.  If the TIFF format output of your scanner was Exif compliant, true for most newer scanners, you should be able to rotate the images by editing the Exif orientation & issuing rotate/flip--a lot of applets (including the scanner controls) to do this with. By nature this will be lossless--90, 180, 270 degrees. But, if you need additional touch-up of the scanned maps while rotating--use open source GIMP or Adobe PhotoShop.  Note that any rotation other than 90, 180, or 270 will "resample" the pixels.  The 64-bit versions of programs will allow you to handle larger TIFF images. You should be able to script the rotations. GIMP provides the Script-Fu macro language or GIMP-Python with an extension. PhotoShop has Actions macros or scripting with JavaScript or Python (w/the Photoshop.Application COM server) Of course when you bring the reoriented TIFFs into ArcMAP, to do any useful work when you georeference you will be transforming and resampling anyhow. But if you work in the same projection an AFINE transform with just 3 control points will give you good registration with simplest pixel rotation and scaling. Stuart ... View more

Adrianne, Ok, the other possibility is that you have a latency issue in capturing the result of the lmstat.bat back to the ESRILicenseUse.txt file. Functionally the WHATLG applet runs a simple FlexLM query of the license server, pipes the result to the ESRILicenseUse.txt file, and then parses that file to populate the .NET 1.1 based WHATLG GUI The lmutil.exe used needs to be a current version that is compatible with the lmgrd.exe and ARCGIS.exe FlexNet Publisher components in use on the license server. You've done that so that probably isn't the problem. Here is an example command from the lmstat.bat batch file setup with WHATLG install. lmutil lmstat -a -c @'your-license-server'  >  ESRILicenseUse.txt The greater than ">" symbol simply redirects the output of the lmutil lmstat -a command into the ESRILicenseUse.txt file. When the batch is run by WhereHaveAllTheLicensesGone.exe, the ESRILicenseUse.txt file handle is locked for redirect writing (showing as busy for any other access), and after some time elapses the .NET GUI is launched and populated by parsing the now released license use text file. Think about what happens if there is a delay and the license use text file has not been closed yet, e.g. the lmutil lmstat -a is still writing to it? The WHATLG GUI will get nothing to work with, or you'll get an error that the file is in use. I think that is what is occurring. So how to fix it? First a test. Open a cmd.exe window and change directory to where you have a copy of the lmutil.exe. Enter, and time how long it takes to complete... lmutil lmstat -a -c @'your-license-server' [INDENT]Check with your server admin as to which port the ArcGIS 10 LM is using, default would be first available in range of 27000 - 27009, or may have been set with an edit of the service.txt configuration file. http://help.arcgis.com/en/arcgisdesktop/10.0/install_guides/License_Manager_Guide/index.html#/Lock_the_ArcGIS_daemon_to_one_port/00790000000w000000/[/INDENT] now enter, and again time how long it takes to write to the screen... lmutil lmstat -a -c '2700x port used'@'your-license-server' If there are no firewalls interfering it should be a shorter delay. If so, go ahead and make the same change in the lmstat.bat file. And run WHATLG again. To explain, if there is no port prepending the -c @'your-license-server' the querry starts at 27000 and works its way up the range to 27009. Each port takes a moment for the lmgrd.exe service to respond and can take 10's of seconds total to complete the query. Specifying the port in use shortens the delay. The addition of a firewall can also impose serious delays, without open firewall ports on the server, when you send the lmutil lmstat -a query, the same 27000 - 27009 range is polled, but this time the firewall blocks the query which must timeout for each port before the next -- much longer for each and can total 100's of seconds. For just that reason I open ports 27000 - 27009 on my FlexNet license servers to clients on our network. ESRI used port 27004 for ArcGIS 9.x LM, port 27005 for ArcGIS 8.x LM. At ArcGIS 10.x LM they no longer assign a port, but allow the lmgrd.exe launch configured by the service.txt file to float to the first available port in the range 27000 -27009. Edits in the service.txt configuration can bind the port for performance and firewall control. See if making an adjustment to the lmstat.bat file fixes things. And perhaps ask your server admin about the firewall settings if any. Stuart P.S. if your laptop is coming in via a routed wireless, or worse a VPN--you'll have additional traffic routing/firewall issues ... View more

Generally I would prefer to see the Forum content topics more specifically focused, both while monitoring specific forum threads and while searching with forum tools or from external search engines. So YES - split out Python from Geoprocessing into a new forum My two cents... Stuart ... View more

Chris, Stuart, This is what Revo says is left over from Apframwork. Which boxes do I check? Check at the CLSID box... {5881A257...  from there down and delete. Stuart ... View more

Chris, As I said, I don't work too much in the HEC tools, but I think at v5 they merged it all onto one GeoHMS toolbar. Also, your problem definitely could be your OS at XPsp2, any reason no install of sp3? Link to download here: [INDENT]http://www.microsoft.com/downloads/en/details.aspx?FamilyId=5B33B5A8-5E76-401F-BE08-1E1555D4F3D4&displaylang=en[/INDENT] Stuart ... View more

Use these credentials provided by ESRI in setting up your connection from FileZilla: http://forums.arcgis.com/threads/8274-ArcHydro-in-ArcGIS-10?p=35289#post35289     ftp.esri.com     login: RiverHydraulics     password: river.1114 Stuart ... View more

Chris, What OS flavor--WinXP, Vista or Win7, 32 or 64bit? Also, use the add/remove program app or a utility, i.e. CCleaner, to identify which version of the water resource utilities you've loaded. In doing the updates. I've found it most effective to remove all Water Resources App components and start the install fresh. So AppFramework, ArcHydro9, HECGeoHMS and HECGeoRAS should all come off. Use CCleaner or Revo Uninstaller.  Also, delete the program folders \ESRI\WaterUtils and \HEC to be sure your starting fresh.  Of course protect any project folders if you've put them in those directories. Use an ftp tool rather than your web browser to review the directories at the Water Resources ftp site, I prefer FileZilla ( http://filezilla-project.org ). It makes navigating, file review and downloads much easier. Unfortunately it gets a little confusing because the ReadmeMMDDYYYY.doc is sometimes a little behind and while the table of latest releases is pretty current the dated release notes are not annotated with the specific build numbers they refer to. So, looking at the support site, as of today -- 20101118: ApFramework9 v3.1.0.93 was built on 20100914 and is the version currently bundled with installers for ArcHydroTools9, HEC GeoHMS and HEC GeoRAS. HEC GeoHMS for 9.3-9.3.1 v4.2.93.51 was built on 20101008 HEC GeoRAS for 9.3.1 v4.3.1.21 was just built on 20101116 -- is listed on the ftp site as .20 (rather its folder has not been renamed) In addition to the ApFramework9 v3.1.0.93, the v4.2.93.51 GeoHMS install loads ArcHydroTools for 9.3.1  v1.4.0.253 built on 20101008 The development release of HEC GeoHMS for 9.3.1, v5.0.0.69 was built on 20101111.  It will install the same v3.1.0.93 of AppFramework9, but it installs  ArcHydroTools9 for 9.3.1 v1.4.0.255 built on 20101015. The water resource ftp site does not have the ArcHydroTools9 v 1.4.0.255 posted, just .253. To get you current with latest patches and updates uninstall all, and load the v5.0.0.69 build of HEC GeoHMS with its bundled ApFramework and ArcHydroTools9. Run that against the demo project and see if the error clears. You can reload HEC GeoRAS v4.3.1.21 when convenient. Stuart ... View more

Chris, Good to know that you've made some progress.  But as to your HECGeoHMS9 error: System.Runtime.InteropServices.COMException (0x8004005): Error HRESULT E_Fail has been returned from a call to a COM component. at ESRI.ArcGIS.Geoprocessing.GeoProcessorClass.GetEnvironmentValue(String environmentName) at HECGeoHMS9.GenerateProject.UpdateAHD(String rasterLocation, String vectorLocation, String ahProjName) Were you working with an old HMS project geodatabase or did you run preprocessing from scratch and setup a new HMS Project? It looks to me like it could be in the AppFramework, but I just don't do enough work in the Water Resources extensions to be much help. If you're up for it you might try the 9.3.1 specific v5.0 release of GeoHMS from the ftp site to see if that clears the error (but you'd also need to bring up the GeoRAS version as well). For more assistance from anyone on the forum, you'll need to post back OS and specific release versions (you said you're on ArcGIS 9.3.1 SP2 build 4000); post the build dates and version for ArcHydro, GeoHMS and GeoRAS. Stuart ... View more

Adrianne, Sounds like a permissions problem when running the script. Does your user account have ownership, or at least modify permission for the ESRILicenseUse.txt file? Stuart ... View more

Guangli, You are correct.  My apologies, as I did not actually throw together a RAS project to verify the Inundation Mapping --> Floodplain Delineation using TINs was working.  And while my 3D Analyst extension is activated, my "Delineation using TINs" menu also remains grayed out. In fact the program Help file and v 4.2.93 user manual still shows the old Floodplain Delineation --> GRID Intersection.  Which thinking about it is what I understand the active Floodplain Delineation using Raster should do--e.g. difference the TINs into a GRID (raster) of depth with a polygonal boundary--the resulting d and b prefixed layers. So guess it could be a pending feature--not yet activated, or documented--to delineate the floodplain and depth out as TIN data. Guess we'll have to wait for the development team to finish things up. Stuart ... View more

I believe things are fine, my installation behaves the same way. It just is that you need to create your Water Surface TINs from the RAS GIS export files first. Once they exist in the map session the "Floodplain Delineation Using TINs" will activate and you'll be presented with a selection tool to choose the set to work with. Stuart ... View more

Romeyn, You were close to getting it all correct. Unfortunately your version of HEC-GeoRAS was newer than your installed HEC-GeoHMS version. The four Water Resources Applications--ApplicationFramework9, ArcHydro, HEC-GeoHMS, HEC-GeoRAS are all developed/maintained in sync meaning that you need to change all as you update any component. At the Water Resources group ftp site, ftp://RiverHydraulics:river%2E1114@ftp.esri.com,  you need to closely read the latest release notes and installation procedures (it is the ReadmeMMDDYYYY.doc document). As I said, you were close, the last build date for the ArcGIS 9.3.1 Water Resources Applications was 10/8/2010; so for ArcGIS Desktop 9.3.1 SP2 (build 4000) you can use either the v4.2.93.51 or v5.0.0.67 of GeoHMS from that build date. In addition to the latest development version of GeoHMS, the 10/8/2010 builds would install ArcHydro, v1.4.0.253, and the correct build of the ApplicationFramework9, v3.1.0.93.  You can then follow that with another  install attempt of HEC-GeoRAS v4.3.1.16 from that build date (built/posted the 15th) which will accept the installed v3.1.0.93 ApplicationFramework9. Poking around in the folders for each water application will help you to verify you've got matching build versions--look at the build dates while following along in the release notes/install procedures document. Yes its confusing, but these Water Resources development apps are on the bleeding edge and so require that you follow along with the development process as you put them to use. Stuart ... View more

Suspect you should be set for your evaluation. As with the user interface for all ArcGIS releases you need to activate a licensed extension before you can use it in ArcMap or ArcCatalog. At ArcGIS 10 extension activation is from the Customize --> Extensions drop-down menus.  Check the extension you'd like to activate for the session.  If not listed or is grayed out the extension is not authorized (licensed). Then you can add the toolbar. Again from Customize --> Toolbars select the corresponding toolbar(s) for the extension you just activated. (Note: at 9.x and earlier this selection was done from Tools --> Extensions;  and View --> Toolbars) As a caution, activation of an extension is statefull.  The ArcMap, ArcCatalog documents you create will require those extensions be present, active and authorized (licensed) to properly open/close, affects portability if you need to move the documents. Also, the ArcMap and ArcCatalog configurations retain the last run settings. Best practice is after saving a document to then deactivate extensions when closing a session.  And to reactivate the extensions as needed when opening new session and creating new documents. Good luck and post back if that was not clear enough to get you going. Stuart ... View more

Sorry,  I had to correct the 2 Oct post as the URL to the release notes (readme09172010.doc) changed with an update release on 8 Oct. So, to obtain latest release notes, from the folder listing reached via the ftp URL below download the readme<dateofrelease>.doc document. [indent]ftp://RiverHydraulics:river%2E1114@ftp.esri.com[/indent] Then please fully read the installation procedures and release notes before downloading and attempting to setup any of the components. It will save you a lot of aggravation.  Be sure you obtain the correct release for your version of ArcGIS and remove any prior version components before starting an install. Stuart ... View more

Patricia, The ESRI ftp site version of HEC GeoHMS 4.2.93 is most current and deploys version 3.1.0.93 of the ApFramework9 and 1.4.0.248 of the ArcHydro Tools. Since you'd previously updated your version of AppFramework9 with the HEC GeoRAS install, you also needed the matching versions of ArcHydro and GeoHMS from the ESRI ftp site as well--as you discovered the HEC download site version of GeoHMS is incompatible with your installed version of the application framework. It is probably best (and believe it is intended) that for a user, all the Water Resources components are maintained at the same release level by updating the entire suite when you update any one component via the ftp site. The versioned releases are all maintained for the community by the ESRI Water Resources Group on the ftp server, but it can be confusing as to which to grab. A careful read of the installation procedures and release notes will help sort it out.  Also, see if the suggestions in this thread help with cleaning up the installs. [INDENT]http://forums.arcgis.com/threads/13235-Problems-with-Hec-GeoHMS-Installation[/INDENT] Stuart ... View more