Latest Contributions by RobertStevens

‎12-19-2019

I have just today run into this same issue. I read all the correspondence and finally, by using the two spaces between "Zone" and the numeral got it to work. Thanks for the solution. But .... What a complete crock. The larger crok is this use of whitespace at all -- it is a monumental headache for anyone scripting in eg cygwin. And the smaller crock is ESRI not using something like the "name" field returned in the spatial reference. And, here we are, over two years on from the original problem and ESRI still cannot come up with something better.

‎08-09-2019

Dan All our data, except for a basemap, is local (and in the specific instance I reference above even the basemap was local -- came from Business Analyst). We have used datasets from Business Analyst (which are quite big), but because BA 2015 is not supported in acrmap post 10.4 we no longer use any BA programs. However the spatial join I refer to above as between two datasets of polygons of 600K and 20K features. Our machine is standalone. No other tasks going on except for usual system stuff and antivirus. No database connections to servers or anything of that kind. Rob

‎08-09-2019

Amen to what David said. Why is there no "have their center in". Is there a workaround? Sure. But I have a better workaround: have ESRI actually make logical design decisions, and better software.

‎08-09-2019

I have been a strident critic of ESRI's software for some time, as examination of my posts will show. In the past, I have used a MacBook Pro, running Windows10 under Parallels, and assigned 8G amd two cores to the VM. The performance was just awful, and the response of many was: "..need more resources...32G RAM minimum, prefer 64G:, "Parallels not supported"... etc. Ok. So our company has bought a dedicated PC. Graphics card is some high end NVIDIA jobbie as used by gamers; 64G RAM. 1T solid state drive; multicore AMD processor; $3000 later and .... fanfare....(no) Is performance better? Yes, it is better. But it is still slow enough to be irritating to the user. It is plain not good enough Could ESRI please explain this: I run a tool out of the standard toolbox. The same comment applies to many tools, but let's take Analysis Tools=> Overlay=>Spatial Join. There is a checkbox "Keep All Target Features (optional)". The default is on. I click it to turn if off. It takes 9+-1 seconds for the tick mark to disappear. So long, in fact, that one's first reaction is to click it again, whereupon it will be turned back on after another interminable wait. I am sorry. That is just pathetic. What can this behemoth of a software be doing that a simple graphical operation takes that long to echo??? And other fields are the same. There is always a pregnant pause after each field is entered or modified. The spinning blue circle and the "... is not responding from the OS" are my constant companions. So now, now that the stock response of "wrong computer, wrong this, wrong that.." are not applicable, tell me: Should i expect better?. That is a rhetorical question. This product reminds me of using computers in the seventies and eighties. I have not yet tried to use ArcPro on this revved up hardware. I am not optimistic.

‎06-26-2019

Jugal I now how been able to replicate my original problem (the one before this other issue about visible/invisible fields arose. I try to join the two point layers, and the join fails claiming the second dataset (part of a group layer) does not exist. If you can screen share that would be helpful.

‎06-21-2019

Yes, have had arcmap installed for years. I wouldn't call that blindingly fast either. But, aside from these ESRI products, windows is doing no other user tasks. Arcmap is a 32 bit app (still, isn't it?) and so we surely cannot gain very much performance by installing more memory, can we?

‎06-21-2019

This continues to be a problem, and I have filed a bug against it: case02346902 The join frequently works, but then will sometimes fail. Once it has failed once, it will continue to fail. But if the map is saved, arcmap exited, and the map reopened, it will start working again. It is very clear that some software structure is being corrupted, but I am unable to come up with a precise sequence of operations that will cause the failure. Frankly, I am not paid to troubleshoot ESRI products, and this kind of investigation is really time consuming. I will report back when technical support have looked into this further. UPDATE: this problem is hard to replicate. Now, six months after the original. I am encountering the same problem again. I have a new bugID 02478740 If anyone else has encountered strange behavior of spatial joins please report them here. Synopsis: spatial join of points to polygons using "within". It usually works. But it seems to start failing after one has invoked it incorrectly (say one had the criteria wrong, or was trying to join points to points using within). Thereafter it fails to perform the join correctly. There may be other circumstances that trigger the failure. It is hard to reproduce at will: I have not found a consistent way to do so.

‎06-18-2019

So I closed the map. Opened it again (new invocation of arcmap) and the join now works. I suspect that I will try it again in a few hours, and it will fail. I find this all too typical of ESRI software. I have had a suspicion for a very long while that cleanup after greoprocessing operations is not properly performed. I would be willing to bet that there are memory leaks. What is abundantly clear is that multiple invocations of the same tool can have quite different results depending upon the history of the specific arcmap invocation. A specific example of this kind of thing occurred with the arcpy tools a while back (reported by me as bug back then). One of these APIs performed a cd (change directory) without then reverting back to the original directory afterwards. The calling code was looping through a list of files, and suddenly could no longer find the next file on the list. Fine programming.

‎06-18-2019

Dan I changed the name of the group and replaced blanks with underscores. No joy. Then I changed the name of the layer similarly. Still no joy. Being an old Unix jockey, I am always suspicious of using white space in anything that might be or become a data object. You seem of like mind. I know this join has worked for me within the last week. There is no obvious reason it would now fail except pure passage of time. There seems to be some environmental factor (I use the word loosely, not in the ESRI sense) which is causing this sometimes to fail. But nothing I can so far reproduce. Dan, if you don't watch out, answering my posts to this community will wear you out. Ty. I am convinced this is a bug, and I have now reported it as a new case #02346902.

‎06-18-2019

I am running spatial join tool, joining points to points : I wish to determine for each point in the target dataset the nearest feature in the join dataset, and to record that distance. Both the join and the target dataset have the same (projected) coordinate system. They are both visible on the map. Attachment#1 shows my table of contents. The target dataset is nswdb_2019q2_project. The join dataset is Chic Grocery Stores 2015. The tool fails: see Attachment#2 Why does it fail? I have noticed this kind of failure before, intermittently, when the join dataset is in a group layer (as it is here). When I move the Chic Grocery Stores 2015 layer outside the group layer, the join works. I have edited this posting to use the terminology used by the tool. )2019-06-18 15:57 EST). There was no change to the substance of the problem.

‎06-18-2019

Amen to your last two sentences.

‎06-18-2019

Dan, I have frequently found your posts most useful, and I thank you for them. This is a pretty small potatoes issue, certainly, but I really think you are being an apologist for a second best ESRI design decision. If I have fields invisible in the original dataset, it is more likely that not that I wish them to rmain invisible in some new dataset created from it by the operation described.

‎06-15-2019

Dan Yes, but the reason to hide fields is to make the user experience better yet keep the possibility of resurrecting some or all of those fields. For example, Business Analyst datasets have several hundred fields. It is tiresome to have to scroll left to right to find those of interest, yet at some future data I might see the need to visit a handful of those fields. There are many workarounds, yes, but this seems like a poor default behavior.

‎06-15-2019

I have a point dataset, with many of the fields invisible. I create a selection on that point dataset, and use selection=>create layer from selected features. That works, but now all the fields which had been invisible now become visible. Why? That doesn't seem logical. I didn't want them to display in the old dataset, and it is unlikely that I want them to display in the new subset. Not a big deal, but more pointing and clicking. I seem to do much pointing and clicking with arcmap. Too much.

‎06-15-2019

I have a layer created with the Multiple Ring Buffer tool in the Analysis Tools=>Overlay toolbox. The field, chosen by the tool, that has the radii of the distance rings is called, unsurprisingly, distance. Now I make a many-to-one spatial join of a point dataset (the target) to this buffer dataset (the join), the aim being to find how many points lie in each buffer and to extract other statistics from the point dataset as a function of distance. The result of this operation is a new layer, and it seems correct in all aspects bar one: the distance field has been set to zero. This would seem to be a bug. Some spatial joins give one the option to record a distance, but there was no such option for this join. Th fact that the numbers are all zero anyway shows that nothing useful is being recorded. It is just wiping out data which I need for the next step in my analysis. Obviously, the fix is simple. Take the multiple buffer output and rename distance as something else. That works and no new field named distance is created, thus confirming the fact that no useful data was being saved.

Online Status	Offline
Date Last Visited	‎06-09-2026 07:17 PM

My Ideas

Latest Contributions by RobertStevens

Re: Issues with ArcPy SpatialReference Class

Re: ArcMap Performance. Round2

Re: Spatially joining polygons centroid within

ArcMap Performance. Round2

Re: Spatial Join Cannot Open Joined Dataset in Group Layer. Why Not?

Re: ArcPro: Some Performance (or lack therof) Stats

Re: Spatial Join Cannot Open Joined Dataset in Group Layer. Why Not?

Re: Spatial Join Cannot Open Joined Dataset in Group Layer. Why Not?

Re: Spatial Join Cannot Open Joined Dataset in Group Layer. Why Not?

Spatial Join Cannot Open Joined Dataset in Group Layer. Why Not?

Re: Invisible Fields Become Visible After Create New Layer From Selection

Re: Invisible Fields Become Visible After Create New Layer From Selection

Re: Invisible Fields Become Visible After Create New Layer From Selection

Invisible Fields Become Visible After Create New Layer From Selection

Spatial Join Sets distance Field to Zero

Transform from NAD_1983_HARN to WGS_1984

Shape_Length and Shape_Area of Geographic Coordina...

Re: Conda. How can it be so slow?

Conda. How can it be so slow?

Activation of Conda Environments