Latest Contributions by DavidTriggs

The ability to import colour ramps is critical and a serious tool missing from Pro. There are so many options to work with but they are difficult to implment at the moment. One important consideration ESRI should give to this tool is every colour scheme the user imports to a style is one that ESRI doesn't have to create. ... View more

Sorry for the delay, but am still waiting for the package to compress so I check the template settings. The photo was dragged across from the project pane as a raster dataset, so I presume it will be a UNC path ... View more

Ok, solved. The toolboxes were the problem. It seems to be saving at the moment, but I put our 41Gb aerial photo in as the base map and it is now copying the 41gb file from one place on the network to another. Why? The template has a link to where the data is stored; why wouldn't it just load it? I can't see the need to copy anything. ... View more

Thanks Joanne, there are no layers at all, I am trying to create an empty template with all my usual data connection and folders. Since Pro does not appear to have a nicely set up catalog of connection files which we can set up once, creating a project template appears to be the only way to set up your data connections. Once I had set up my data connections and tried to save them, it fails. The actual MyMap5.aprx file has saved, but saving it as a template fails. I have since tried adding a Map and adding our aerial photo to it and saving the template again, but it still gives me a general function failure. The Consolidate Project failed rather spectacularly Start Time: Fri Jan 09 06:53:04 2015 ERROR 001659: Consolidating toolbox O:\GIS\Toolboxes\XTools Pro.tbx((null)) ERROR 000989: Python syntax error: within script tool XToolsPro_CalculateLengthBatch_(O:\GIS\Scripts\CalcLengthBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_CalculateAreaBatch_(O:\GIS\Scripts\CalcAreaBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_AddXYZBatch_(O:\GIS\Scripts\AddXYZBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_AddLatLongBatch_(O:\GIS\Scripts\AddLatLongBatch.py) ERROR 001659: Consolidating toolbox O:\GIS\Toolboxes\Minara Tools.tbx((null)) ERROR 000989: Python syntax error: within script tool UpdateTenements2_(G:\My Documents\UpdateMonthlyTenements.py) ERROR 000989: Python syntax error: within script tool Digability_(G:\My Documents\DigabilityScript.py) ERROR 000989: Python syntax error: within script tool BuildPyramids_(G:\My Documents\BuildPyramidsAndProjectTIFFS.py) ERROR 000989: Python syntax error: within script tool ReplaceTenements_(G:\ImportTenements.py) ERROR 000989: Python syntax error: within script tool UpdateClearing_(G:\My Documents\Script1.py) ERROR 000989: Python syntax error: within script tool ClippingTopoData_(G:\My Documents\ClipBecsTopo.py) ERROR 000989: Python syntax error: within script tool GenSetoutPts_(G:\GenerateSetoutCoordinates.py) WARNING 001683: Found Python 2 to 3 errors: Line 32:     print("Processing " + bName) ->     print(("Processing " + bName)) WARNING 001683: Found Python 2 to 3 errors: Line 45:         if field.name <> ShpFldName: ->         if field.name != ShpFldName: ERROR 000989: Python syntax error: within script tool GenSetoutPts_(G:\GenerateSetoutCoordinates.py) ERROR 000989: Python syntax error: within script tool ClippingTopoData_(G:\My Documents\ClipBecsTopo.py) ERROR 000989: Python syntax error: within script tool UpdateClearing_(G:\My Documents\Script1.py) ERROR 000989: Python syntax error: within script tool ReplaceTenements_(G:\ImportTenements.py) ERROR 000989: Python syntax error: within script tool BuildPyramids_(G:\My Documents\BuildPyramidsAndProjectTIFFS.py) ERROR 000989: Python syntax error: within script tool Digability_(G:\My Documents\DigabilityScript.py) ERROR 000989: Python syntax error: within script tool UpdateTenements2_(G:\My Documents\UpdateMonthlyTenements.py) ERROR 001659: Consolidating toolbox O:\GIS\Toolboxes\Minara Tools.tbx((null)) ERROR 000989: Python syntax error: within script tool XToolsPro_AddLatLongBatch_(O:\GIS\Scripts\AddLatLongBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_AddXYZBatch_(O:\GIS\Scripts\AddXYZBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_CalculateAreaBatch_(O:\GIS\Scripts\CalcAreaBatch.py) ERROR 000989: Python syntax error: within script tool XToolsPro_CalculateLengthBatch_(O:\GIS\Scripts\CalcLengthBatch.py) ERROR 001659: Consolidating toolbox O:\GIS\Toolboxes\XTools Pro.tbx((null)) Failed to execute (ConsolidateProject). Failed at Fri Jan 09 06:53:56 2015 (Elapsed Time: 51.52 seconds) Regards David ... View more

Hi John, It depends on how you do it, the Project View or the Project Pane. It seems to fail in the Project View, but if you swithch to Pane which looks just like ArcCatalog, you can rename there and it appears that the project properties are retained. ... View more

Why do we even have ArcScene? I can't think of another program that needs one program to edit in 2D and a separate one to edit in 3D. As far as snapping goes the snapping in ArcScene is very badly done, you can barley tell if the point has snapped or not. The Production Mapping Extension is not available in 3D Analyst for some bizarre reason, but its implementation in Arc9.3 was the first really useful 3D editing tool that ESRI had supplied is long suffering user base. Z Snapping in ArcMap should be standard. If the point has a Z vertice, grab the value, if it doesn't, don't. That, in one sentance, pretty sums up what is required. It can't be that difficult. ... View more

Since I wrote this this mornng I was able to get the 32 bit version up and running. I have played around with the API but am confused as to how to extract and write a point. From the C# samples, you get the geometry and write it to a PointShapeBuffer, however if I try this in VB.net, I get an error saying that the GetGeometry function returns a ShapeBuffer. PointShapeBuffer pointGeometry = row.GetGeometry(); point = pointGeometry.point; It will offer a solution of CType(row.GetGeometry(), PointShapeBuffer) which then fails. My question is, pardon the thread drift, is how do I get from row.GetGeometry returning a ShapeBuffer to a PointShapeBuffer and then to a point which is what I am trying to extract. There does not appear to be a connection between these three sets of information. Thanks David ... View more

Hi Lance, I am trying to run the API in VB.net and have the same problem locating the DLL. I am also using the 64 bit version. I have copied the 3 DLL's to the Debug directory and checked that C++ redist is uptodate. I then tried the 32-bit version and it comes back with the following errors. It seems to be obsessed with the geodatabase.cpp source file. I can't get this to work in either 32 bit or 64 bit. Chers David Locating source for 'f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp'. Checksum: MD5 {b4 4d cd c9 dd f8 f3 7b 31 b9 5 e3 d9 33 3f b3} The file 'f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp' does not exist. Looking in script documents for 'f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp'... Looking in the projects for 'f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp'. The file was not found in a project. Looking in directory 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\vc7\atlmfc'... Looking in directory 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\vc7\crt'... The debug source files settings for the active solution indicate that the debugger will not ask the user to find the file: f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp. The debugger could not locate the source file 'f:\filegdb_api\src\esri.filegdbapi\geodatabase.cpp'. ... View more

Hi Guys, I was wondering if there had been any development on the VB.Net version of the File Geodatabase API? Thanks David ... View more

Thanks Lance, thats is good news, is there a rough release date? ... View more