Are you adding the data in through add xy data? Also some characters are not accepted in a field, making it null. Perhaps some formatting of the xls is messing it up, copy and paste the values only into a new xls or csv. Ensure that wgs84 is your projection when adding data also (if it is wgs84 later longs).
To remove gaps and overlaps you should use the Topology tool. The Topology tool helps validate your data based on different rules you choose appropriate.
One of the many rules available in that tool is: (features) "Must not Overlap".
The tool has an "Error Fix" button that let you zoom to the error (in your case, an overlap) and let you choose what to do - ...
Using the Union tool is the answer. But, you will need to do a bit more work after you run the tool. All the overlapping and non overlapping polygon WILL show up in the attribute table. You will need to detect which are the overlaps an which are not by simply looking at the FID (some will have a -1 and some will carry over the FID from the overlapping ...
The previous answers are not complete/correct. There are two options for creating spatial functionality in a PDF. The first is the open standard Geospatial PDF. Users do not require the any proprietary plug-in to read geospatial PDFs created following the PDF 1.7 specification, which was published as ISO 32000-1 standard. Geospatial PDF's can be create ...
As you say in an answer that you have included within your question this appears to be Bug NIM084228:
Summarizing attribute tables return incorrect results with null values.
Esri have therefore acknowledged that this bug exists in ArcMap. ArcMap uses an architecture that is 20-25 years old, and which was superseded by ArcGIS Pro a number of years ago.
If I understand correctly, you are trying to remove overlap between polygons. I would suggest looking at the ERASE and CLIP tools. If you are talking about slivers (gaps) between polygons, you can use the align to edge tool on the editor toolbar, as well as the snap tool. If you can provide screenshots of your workflow and examples of your issue I may be ...
This does not sound like a use case for the ArcGIS Spatial Analyst or a TIN data format.
If you know the area of a particular polygon, and that is easy to calculate for a shapefile, or is automatically calculated for a geodatabase feature class, then all you need do to get the volume that you are after is to multiply that area by the height you want to ...
I think it's the if [UNIT] <> " " that cause problem. By testing for " " you are looking for a space you should try with "" (empty string) or IS NULL depending on your field type (text or numeric, if it's a text field you may want to check that the "empty" cells are consistant).
I think @PolyGeo is correct if you have ArcPro then Contingent Values is the way to go. But if you don't then domains and sub-types would work if when you create your feature on the map you use the template. If you then went back into the attribute table then yes you see the list of all values rather than a subset.
So to explain I created a text Domain ...
I believe you may need to reset the gamma using the Image Analysis window. If you read this thread (https://community.esri.com/thread/3285) and scroll down to the reply from allisamcmasters and follow their instructions this might make your image appear when you click 'zoom to layer'. It certainly worked for me with a similar problem.
This can be achieved using formatted labels and wingding fonts. An example is shown below:
This assumes you have a field called circle and that this numeric field holds numbers 1 to 3, it could potentially hold 0 to 9 if you wished. Then you have another numeric field called v and this is the value that precedes the v.
The Label expression would be:
Or maybe this Python Function will be useful to some.
'''Converts Radians (East = 0 then counter-clockwise)
to Geographic Degrees (North = 0 then clockwise).'''
theta = math.degrees(theta)
theta = theta - 90.0
if theta < 0:
theta = theta + 360.0
theta = -1*(theta *...
I had a workaround to do this with a few conditions. it works and keeps the angle as you want between 0 and 180, transfering Geographic angles (Azimuth in this line of code) to your Arithmetric angle:
if(450-Azimuth<180, 450-Azimuth, if(450-Azimuth>360, 450-Azimuth-360, 450-Azimuth-180))
Make a seed2d file in microstaion where you define your projection and unit. In Arcgis desktop while using Export to CAD, Use the seed file in optional box. That will solve your problem. Same work for Dwg too.
Symmetrical Difference (Analysis)
Features or portions of features in the input and update features that do not overlap will be written to the output feature class.
Usage - The input and update feature class or feature layer must be of the same geometry type. Attribute values from the input feature classes will be copied to the output feature class.
If you have a Spatial Analyst Licence, you can use the Extract Values to Points tool which:
Extracts the cell values of a raster based on a set of point features
and records the values in the attribute table of an output feature
If your 5000 xy coordinates are not a Feature Layer, you can follow these steps to convert a table (e.g. a csv or ...
You do not specify which ArcGIS Desktop application you are using so I will assume ArcGIS Pro. In any event the workflow is probably the same in ArcMap for this part of the software.
You could try to do the following for each species:
Use the Select (Analysis) tool to create two feature classes for one species from each survey. I'll call them SurvA_sp1 ...
This is most likely due to numerical rounding and precision. As currently implemented in TauDEM, the aread8 results are held in a "float" variable in C++ which has about 7 decimal digits of precision (line 152 in https://github.com/dtarb/TauDEM/blob/Develop/src/aread8.cpp). Specifically, if the number 1 is added to 26648268 numerical effects will result in ...
If you follow exact steps from ESRI, it works and will produce something like that:
I don't like that they are disconnected. Perhaps create sub-catchments from stream network and assume that divides between them ARE ridges:
Note smaller flow accumulation threshold you'll use to derive streams will result in more detailed ridges network.
Consider erasing ...
What you are describing sounds like the use case for contingent values:
Contingent values, sometimes referred to as contingent attribute
values, are a data design feature that allow you to make values in one
field dependent on values in another field. Attribute domains allow
you to restrict the valid entries on a field to a set list or range of
To export GPX files as CSV from Garmin Basecamp, select the waypoints you want to export and then:
Save as Type csv and select where to save the file
You can find more information on Garmin's info page here.
Alternatively, ArcMap can directly import gpx files using the GPX to Feature tool. Documentation on the tool is ...
Python is really handy for the casual user but its scope is limited, ArcObjects offers a much bigger scope for modification and can need external software. As we've seen in the comments there are some things that even ArcObjects can't do.
The limited scope of python is one of its strong points, not having to search through thousands of interfaces, classes, ...
This happened to me with 10.6.1.
Sometimes the window moves so that you can see a very small portion of it on the edge of your active monitor. Look closely at the edge of your screen to see if there is just the border of the window there. If so you may be able to grab it (even enough just to resize it a bit) and then drag the window into your main screen.
One other solution is to create/insert two legend element, one for each of your column (each containing only the layer you want depending on the column and each with the correct option to display all or only visible classes)
The downside are you spend twice the time fine tuning the legend and the alignement between the two are not always easy to get right......
I have the same issue with DDP and I get around it by having the the first two items in the legend, "Preserved Lands" and "Conservation Easements" for you, be what will always appear on every page. Then have the third item be what will only sometime show. Then on the second item check the "Place items in new column" and make sure it is unchecked from other ...
My initial approach was to use the Data Management Tools --> Raster
--> Raster Processing --> Clip function with a shapefile of the lower 48 as the Output Extent.
From that description it sounds like you have a single shapefile with 48 polygons representing the lower 48 states. The tool has likely used all polygons so it's clipping out a ...
Alright: I've figured this out. It has to do with the settings.
I was exporting my map with high resolution settings
Resolution: 300 dpi
JPEG Quality: 100
This led to the output PDF being exported without the WMS layer (imagery). However, with the settings set to:
Resolution: 300 dpi
JPEG Quality: 85
Everything exports properly and ...
I could be way off here as I cannot offer the complete answer but wouldn't the tool be failing at the select data point because you have just imported the accounts from an excel spreadsheet, there has been no feature geometry created yet to assign XY coordinates to?
Your coordinates look like they could be in WGS 1984 - Pseudo Mercator (Web Mercator, EPSG 3857. Web maps often use Web Mercator, so it is a likely candidate), or World Mercator (EPSG 3395). In both cases, your example point would fall near the UAE - Oman border. Check to see if one of these fit your data correctly.
Some tools like projfinder and epsg.io ...
This answer is still the case. Radio buttons are not an option. Use Boolean for a check-box. This will allow for two choices (checked vs unchecked).
Another option is to use String and add a filter for a drop-down list.
How do you do this using ArcGIS Desktop?
You use it as an external data source, you can query at any point location to get the underlying data (the clay layer is queryable), but you can't directly access the full data though the WMS.
I put full data here, because as can be seen in the GetCapabilites response for the clay service:
You can't*. A WMS serves rendered map images not data.
You can use data.isric.org to download the actual data instead.
* You can save a georeferenced raster of the WMS map image, but you're still only getting the rendered map, not the actual data.
Depending on the output that you are after here, there are two approaches that you can take. The first is to aggregate to a different resolution representing the size of your cell groups. Aggregation will take a group of cells, apply a statistic and then return the value of the statistic to the new resolution.
The second approach would be to keep the same ...
You can't preserve the input, unless you convert the raster to polygons - try spex::polygonize (see @mdsumner comment).
This is an effective solution for what I was trying to achieve.
## load library
## convert raster to polygon
r1.p <- polygonize(r_toconvert)
## change projection to desired projection
r1.pj <- st_transform(r1.p, crs=...
If you are still having this issue, at the bottom of the "Display XY Data" window there is a check box that has the label "Warn me if the resulting layer will have restricted functionality." If you uncheck this box and then click OK, the error message will not appear.
you need to parse the path.
Please insert Parse Path in your model through Insert > Models Only Tools > Parse Path, then choose the parse type = NAME. Connect "Value" tool to "Raster to Polygon" as precondition.
For the output, you can write it as %Value%
See attached picture.
I've been able to use your code snippet, along with another snippet to create a sequence of numbers:
counter = 1
rows = arcpy.UpdateCursor("Cities","","","NAME; SortFld", "NAME")
for row in rows:
row.SortFld = counter
counter = counter + 1
I found this in another discussion:
Sort Column and Sequentially Number Separate ...
Since you are not concerned with which of the B geoms overlap the target A geom, you might try a different approach:
1) Calculate the area of each feature in A -> OrigArea
2) Get the difference of A and B (using B as the overlay) -> Difference
3) Calculate the area of each feature in Difference output -> NewArea
4) Compute Delta = OrigArea-NewArea
Use a "butt" style of line cap. This creates a flat end that stops exactly at the end of the line (as compared to "square" which extends the symbol past the geographic end of the line).
Add a marker symbol layer. Make the marker symbol a single black circle, the same width as the line, placed at the endpoint of the line.
Note: apparently this method works ...
You are initializing the label with a white space, then for each s you add a new line and the s value. After the 1st s, the label is therefore white space + newline + s1
You could add the new line after the s value:
label = " "
For Each value in s
label= label & value & vbNewLine
Note that you way want to initialize with an empty char (""...
If I understand your problem right, you should use page definition on the other data frames.
layer properties >> page query >> select the relevant attribute according which you want the layer to appear
The only way to add a layer using Python/arcpy to ArcMap is using the arcpy.mapping.AddLayer function. This function works with mapping layers.
No matter what you do in the ArcGIS for Python API, you'll never get back an arcpy mapping layer object. Meaning: you cannot simply do a search using the Python API, and pass that reference through to arcpy.mapping....
Turns out it is quite an easy task in ArcObject. Type cast the feature to network feature and you are done. Below is the code for reference.
# get current ArcMap application pointer
pApp = NewObj(esriFramework.AppRef, esriFramework.IApplication)
# get selected features from ArcMap
pFeatSel = CType(pApp.Document, esriArcMapUI.IMxDocument).FocusMap....
My solution is:
1) Use 'Find Identical' (from Data Management Tools -> General);
2) Join the result of p.1 with your original table by system ObjectID field;
3) In Model Builder: 'Insert -> Iterators -> For' and set 'From Value' and 'To Value' the min and max values from the 'FEAT_SEQ' field of your table (after p.2);
4) Use 'Select Layer By Attribute' ...