Latest Contributions by SimonJackson

Interesting. After creating the surface, I will be doing some raster calculations against this layer and multiple other raster datasets.  Any issues using a terrain dataset for this? ... View more

Hi Dan Patterson‌.   Coordinate system With the query layer (4326) I set an environmental variable to output the results in a projected coordinate system. With the Enterprise GDB/File GDB, the data had already been projected into a pcs. Point to Raster Good suggestion. The 'cell size' of the point layer is 40m.   Would have been desirable to interpolate to 5-10m, but resampling might be an approach there.  I assumed (disregarding size of the dataset for now) that Nearest Neighbour would have been the optimal approach for this? And what if the orientation of the points is not exactly linear, would this not cause an issue?   Hmm. Just tried running the tool and it produced an empty output.  Will investigate. EDIT I got it to output a layer, but it does not convert all the points. Interestingly, if I apply a graduated renderer, it ends up not showing all the points (the same as what does not get created by the point to raster). The points that have not been rendered have values assigned to them and are valid geometries.  Does this provide a clue into what could be causing the issue? Below: Layer with a graduated renderer.  Layer with a simple renderer (squares). A simple result of the point to raster tool. The Point to Raster output matches the same values not rendered by the unique renderer. All those datapoints have a value behind them. Perhaps when it tries to come up with a classification scheme, a graduated renderer stops scanning a table after a certain number of records?   From an interpolation/point to raster perspective, seems like it might be hitting this same issue and not outputting the correct result? Point to Raster output full extent: This does not look correct in several areas (that match up to the areas that fail to render with the graduated renderer) ... View more

I should point out that the output is set as a parameter and can confirm that the layer is still not added to my Contens after running the tool from the dialog. ... View more

Sorry, should have had that enabled in my screenshot for consistency. However, makes no difference. ... View more

Can understand why you would assume QoE would be ordinal as sounds like something you would survey from people, but it is actually a measure calculated from download throughput. I do appreciate this is still very early stages in the data exploration, and definitely treading carefully.  Still toying between a raster vs vector based analysis.  The below animated gif might give you a better indication of the data I am working with.  Still needs a lot of work, some outliers to remove, etc, but would still be very interested to hear additional thoughts you might have. ... View more

Hey Dan - appreciate your thoughts. All three datasets are I believe interval data and not nominal or ordinal.  Let me edit this answer in a bit with some summary stats and screenshots to give you a better feel for the datasets.  This might change your answer? As for 'weighted anything' ... is it supported by fact, observation or conjecture We will be doing some statistical testing in order to come up with the weightings. ... View more

Is this in v2?  ... View more

Thanks Dan - the combine tool and your comments in the other post are very helpful. ... View more

Thanks everyone for the extra info.  It was due to Anaconda setting the PATH variable.   I actually fixed it by installing the beta v2.0 of Pro and this corrected the PATH for me. ... View more