Python/ArcPy for ArcGIS Pro 1.3 is now installed in
So your IDE needs to be pointed at that environment to pick up the link to arcpy.
In Visual Studio open the Python Environments window, click "+ Custom..." and select "Configure".
Give the new environment a name e.g. Python 64-bit 3.5 ArcPy and ...
I did not per se figure it out becuase i don't really understand what is going on here but I was trying different things until it worked. I am not sure whether it is suppose to work or whether this crudity can even be called a workaround but here it goes:
Keep both "ESRI.ArcGIS.AddIns.targets" and "ESRI.ArcGIS.AddIns.11.targets" in the "C:\Program Files (...
I had some difficulty integrating ArcPy with ArcGIS Pro and VS Code. Here's how to get things working on Windows 10 and ArcGIS Pro 2.5.0
It is confusing at first as it depends where you have come from. You may be familiar with Python, but not ArcGIS 10.x or Pro. Or you may have Visual Studio experience but not VS Code. So this might be helpful for some.
ArcObjects .Net SDK for ArcGIS 10.2.x requires Visual Studio 2010 or 2012. Visual Studio 2015 isn't supported for 10.2.x
See ArcObjects SDK 10.2.x system requirements - Scroll to bottom of page for info on ArcObjects SDK for the Microsoft .NET Framework.
ArcObjects for 10.3.x requires VS 2012 or VS 2013
ArcObjects for 10.4.x requires VS 2013 or VS ...
Here's just the nuts-and-bolts from some working code:
// in main()...
GDALAllRegister(); // register all drivers
// open your raster - format doesn't matter as all the drivers are registered
GDALDataset* SourceRasterDS = (GDALDataset*) GDALOpen(Raster,GA_ReadOnly);
double GeoTransform; ...
The important difference is the way interop information is stored; either in your assembly, or in an external PIA. Because ArcGIS already provides PIA's, you should always set 'Embed Interop Types' to false for ArcGIS solutions.
The following paragraphs are taken from http://resources.arcgis.com/en/help/arcobjects-net/conceptualhelp/index.html#//...
In order to debug ArcMap 10.3 Add-in with VS2013 in .Net 4.5. I had to attach VS2013 to ArcMap.exe process. This is kinda annoying but it is the only way I got it to work for now. I'm still confused on why this is happening.
How to attach process
In VS2013, go to menu "DEBUG" -> "Attach to Process"
Select "ArcMap.exe" and click on "Attach" ...
You need to iterate the datasets to get his containing feature classes. Like this:
While Not pSdeDSName Is Nothing
Dim pEnumDataset = pSdeDSName.Subsets
Dim pSubset = pEnumDataset.Next()
While Not pSubset Is Nothing
If pSubset.Type = ESRI.ArcGIS.Geodatabase.esriDatasetType.esriDTFeatureClass Then
I put as an answer the steps I've followed.
You have to follow my notes described in this post, BUT you will have to make some changes.
When you open the Visual Studio solution with the devenv command, DON'T DO THE BUILD, wait a bit.
Go to qgis_core properties and add Version.lib
Now do the build and go out for a drink as this takes a long time.
First, I check that Microsoft.VisualStudio.Shell.9.0 was in the GAC, It was not there... :( then I proceed as Juho Vainio in Geonet suggest : Visual Studio Command Prompt --> Run as Administrator --> gacutil /i Microsoft.VisualStudio.Shell.9.0.dll, but it failed because I was not giving the full pat of the dll, so I search for it in the Visual Studio 2008 ...
Using scipy and numpy:
import numpy as np
from scipy.spatial import Delaunay
points = np.random.rand(4, 3)
tri = Delaunay(points)
See the documentation here.
Here's an additional answer since I just went through this process with ArcGIS 10.3 and Visual Studio 2015. I'll just paste the reply I posted at https://geonet.esri.com/message/579779#579779. There are several steps, but none of them are too difficult.
First, to get the SDK installed, you need to add a few registry keys so that ArcGIS thinks that you have ...
It seem you have written an ArcEngine application. So, you must install ArcEngine Runtime on any machine you need to run your application.
ArcEngine Runtime is the minimum. You can either install ArcEngine SDK or even ArcGIS Desktop to run you application.
The Arc Application (Engine or Desktop), must match the version of sdk that you have built your ...
Yes, things can seem a bit complicated.
However, I can confirm that developing add-ins works with ArcGIS 10.3 and Visual Studio 2013. I haven't tried 2015, but I don't expect it to work, because it came out after ArcGIS 10.3.
Some people are having issues debugging in Visual Studio 2013, but for me it eventually worked.
The ArcObjects SDK for the ...
return @"SELECT ST_AsGeoJSON(ST_Transform(geom, 32633))
WHERE ST_Distance(ST_Transform(geom, 32633),
ST_SetSRID(ST_Point(536251.378984788,5211860.67521085), 32633)) < 100";
(This is called Verbatim string literal)
The fist problem is it's not an add-in.
public class PanDown : ICommand
public class PanDown : ESRI.ArcGIS.Desktop.AddIns.Tool
public class PanDown : ESRI.ArcGIS.Desktop.AddIns.Button
Have a good read of this and start again from scratch, ensuring that you select an add-in type for your project when you start in Visual Studio. There are a ...
You can download the spatialite binary from http://www.gaia-gis.it/gaia-sins/windows-bin-amd64/
You can download the .net assemblies from http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki, or just use NuGet after reading which bits you need.
Open the connection, enable extension loading, and then load the SpatiaLite extension using ...
Here is how I resolve this issue and it works pretty much every time it comes up.
Right click on project -> Debug -> Start new instance (this will prevent it from building first)
If above doesn't work then:
Use Select some project as Startup then click Start in the toolbar.
If that doesn't work this works every time:
The easiest way to loop through layers in ArcMap is to use IEnumLayer. You get a reference to that from IMap.Layers.
Then check the type and cast each raster layer returned by the enumerator to IRasterLayer.
The problem was somehow the target CPU of the project had changed. If you go to project properties and then compile there are 2 places where the target platform is set. On the first line there is a dropdown for "Platform". This was correctly set to x86. But 4 rows down there is another drop down for "Target CPU". This was set to x64 somehow. Once I changed ...
You can debug plugin in Visual Studio 2015.
Create project file for VS2015 and add break points in code.
Start QGIS dont load plugin.
Go to Debug -> Attach To Process (Ctrl + Alt + P). Find the qgis process and attach to it.
Break point is hit and you can debug
I figure some people might don't want to install 2013 along side 2015, this is another simpler workaround that worked for me..
ValidateAddinXmlTask is not that important if you know your XML is good. The easiest thing to do is comment it out in your targets file.
While the SDK is required to create new projects (the templates that appear when you choose File>New Project), it should be possible to compile existing projects without the ArcObjects SDK.
Also, I've heard:
1) you don't really need Visual Studio to compile - you can use MSBuild, which is now part of the .NET framework installation.
2) you can compile ...
I see that it is not supported yet for VS 2017
VS2017 is supported. The latest release dropped support for VS2015, albeit you can still use the NuGet packages from nuget.org in VS2015 (all the installer does is add some starter-templates and creates a local nuget repository).
The issue you're hitting is you're targeting a very old version of .NET. You need ...
I solved that problem just creating an environment variable called ECCODES_DEFINITION_PATH. You have to find the path to "definition" folder. In my PC, That path is
But in some PCs the path could be
Setting the coordinates for Center doesn't mean displacing the polygon to those coordinates. A centroid doesn't represent the polygon itself, it is just a point. Center.PutCoords(-1, -1); means just setting (-1, -1) coordinates for a point which has the same coordinates as the polygon's centroid.
Use that way:
private void ExtendPolygon(ref IFeature ...
The correct solution turned out to be that Move shifts by a relative number of units. It is necessary to immediately transfer to the parameters by how much to shift (do not set relative to the center)
For example pTrans.Move(0, 0.2);
private void ExtendPolygon(ref IFeature pPolygonFt)
IPoint Center = ...