|
POST
|
To the left in your image... did you click on Borrow/Return ?
... View more
05-27-2020
02:16 PM
|
0
|
3
|
2192
|
|
POST
|
Multipatch to Raster—Conversion toolbox | Documentation you may be stuck ... The output raster stores the Z values of the input multipatch features at each cell center location. To determine the Z value for each cell, a vertical line is extended from the cell center location to intersect the input multipatch features. The maximum Z value from the points of intersection is assigned to the output raster.
... View more
05-27-2020
01:26 PM
|
2
|
0
|
2592
|
|
POST
|
Maria Manz post again, if you get acceptable results and show what parameters you used for the inputs. It is important that you masked/removed the land from the analysis... you don't want to set off alarm bells about onshore shark sitings
... View more
05-27-2020
11:30 AM
|
1
|
2
|
8597
|
|
POST
|
Not directly, it will select the points that are within county A, what you can do is select by location those that are identified as being in count A then do a select by attributes, but don't clear the selection Select features using attributes—ArcGIS Pro | Documentation then do the select by attributes those that are NOT in couty A. (presume you have a column that does that) You now have the errors
... View more
05-27-2020
11:15 AM
|
1
|
0
|
1676
|
|
POST
|
Select features by location—ArcGIS Pro | Documentation your points in your county... or they aren't
... View more
05-27-2020
08:20 AM
|
0
|
0
|
1676
|
|
POST
|
Have you seen the existing documentation within the Metadata link? View and edit metadata—ArcGIS Pro | Documentation
... View more
05-27-2020
07:46 AM
|
0
|
2
|
1286
|
|
POST
|
On a quick note... you might want to remove the mako shark sightings in the pacific ocean and particularly those on land! These are going to have a big impact on the results you have obtained. You will need to eliminate the landmass completely with nodata values. These are skewing your results
... View more
05-27-2020
07:29 AM
|
1
|
4
|
8597
|
|
POST
|
a = [1, 11, 111, 1111]
s = "E000186"
e = 0
["{}{:>04}{}".format(s, i, e) for i in a]
Out[14]: ['E00018600010', 'E00018600110', 'E00018601110', 'E00018611110'] The key is the '0' padding in the middle variable, represented by 'a' above. s is the start, e is the end values
... View more
05-27-2020
07:18 AM
|
1
|
0
|
1231
|
|
POST
|
I have no more ideas, except to revisit the georeferencing. Sorry, the differences are too big to be something simple
... View more
05-27-2020
06:30 AM
|
0
|
0
|
3009
|
|
POST
|
What are the actual values of a location and for what location? 2 km is a big difference. 200m would suggest a datum difference, What other coordinate systems are used in your area? I have run out of ideas... what does your associate say?
... View more
05-27-2020
01:23 AM
|
0
|
0
|
3009
|
|
POST
|
Near will give you the distance from the line. Unless you replicated all the street nuances (aka curves) and intersections, your streets generated from your observations may or may not be a good representation of existing conditions. Perhaps you can share a typical sample of the existing network and your point locations before you spend a lot of time generating output.
... View more
05-26-2020
08:21 PM
|
0
|
0
|
2788
|
|
POST
|
You might want to look at these as well... it will save you connecting the points if you are only interested in "how close" the data are representing the actual locations. Generate Near Table—Help | Documentation Near—Help | Documentation Spatial Join—Help | Documentation
... View more
05-26-2020
07:59 PM
|
0
|
0
|
2788
|
|
POST
|
Points To Line—Data Management toolbox | Documentation But I suspect if you are looking at comparisons, then you may want to compare offsets of the observations versus the existing? Clarification might help.
... View more
05-26-2020
05:12 PM
|
0
|
0
|
2788
|
|
POST
|
Maria Manz Use None if no item or special value will be used and each feature will be counted once. cell size .... 0.1688... method ... planar I think that your coordinates are in decimal degrees? Right? if so is your study area huge? like 42 degrees high and/or wide? (1/250 of the width or height is the default cell size in the units of the data) Why don't you want to specify a search radius? was this agreed upon? or is this an R default that you are emulating? Think about this. Do you see clusters in the points? In what sort of radius are the clusters? method... use geodesic and revisit your cell size choice, especially if your points are clustered into groupings smaller than your cell size It is hard to make any other recommendations without the "end goal" being known, especially if this goes beyond a pretty map and you need to make inferences about the population patterns. So, you can get a map, it will represent 'density per unit area' but the details still depend on the choices made. If you have a license for An overview of the Spatial Statistics toolbox—ArcGIS Pro | Documentation there are other tools there for mapping and examining patterns (ellipse pattern) and clusters or An overview of the Geostatistical Analyst toolbox—Help | Documentation if you are looking at a predictive surface. So many decisions eh ?
... View more
05-26-2020
05:01 PM
|
1
|
6
|
8597
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 13 hours ago | |
| 1 | 13 hours ago | |
| 2 | 13 hours ago | |
| 1 | 03-19-2026 04:57 PM | |
| 1 | 05-06-2026 01:39 PM |