Latest Contributions by MatthewNoteboom

‎06-11-2019

Thanks Ken, the data is all public Canadian topographic/land use data, but I'm not with that organisation anymore so don't have it on hand. That's the conclusion I came to as well as the classes had silly numbers of features, although it was mostly guesswork as the tool seemed to indicate everything worked - it would be useful if the tools logged when they hit a memory limit. I found a workaround doing some steps in python that probably worked better than my original workflow anyway.

‎06-10-2019

I have a polygon feature class of zones within a watershed, which I'm using to define zones to tabulate areas of land uses from a land use raster. But...the sum of the areas in the resulting table is very close to double the area of the feature class. Any suggestions? In the meantime I'll try working around it by either changing the polygons to raster, or the raster to polygons, but I'd like to know what on earth is happening. Edit: converting the zone polygon class to a raster seems to return sensible results...

‎01-10-2019

Another follow-up comment: With ArcGIS Desktop, I was able to handle the two smallest provinces (by feature count), then passed the database onto a colleague with ArcGIS Pro to try the Pairwise dissolve tool which seems to have a bit more capability. That sorted out 4 more provinces, but the 4 largest (by feature count) come out of Pairwise dissolve with 1 feature, but with null geometry. So any ideas for that are welcome.

‎01-10-2019

Thanks guys. From reading around (albeit older posts) I think maybe the scale of these layers hits a memory limit when using the Dissolve function. I have a layer of man-made cover for Canada that was WAY to unwieldy, so I broke it into provinces (which is how we want to handle the next part of analysis anyway), but I think there's still too many features. I think they're all single-part features to start with, I'm actually trying to make one multipart, but I think it might be too ambitious. I've attached a windows snip of the British Columbia layer, with one of the output features selected. This layer started with 496924 features, and looks to have basically just dissolved 2 blocks. With denser provinces, the output breakdown is 4+ tiles like this.

‎01-10-2019

I'm trying to dissolve a layer with a LOT of polygons to a single multipart so I can place random points throughout (but at less than 1pt/polygon). However, ArcMap seems to have decided it can't dissolve ALL of the features, just subsets. I've tried in ArcMap, and with a standalone Python script. I've tried without using a dissolve field, and with a dissolve field that has the same value for every feature. Multi-part is on. I can't see anything blocking it from completing the process.

‎06-18-2018

thanks Dan. I got there more or less. I was seeing it as a more simple structure like other visually similar database types I've worked with. Since longitude/latitude were fields in the attribute table, I was thinking those actually represented the geometry, but I now understand they're just data fields like all the others.

‎06-18-2018

This is driving me nuts. I'm trying to add one point to a shapefile with 10 points and about 12 fields - I want to give it a name, and type in coordinates calculated elsewhere. Arcmap seems to have a problem with this although it doesn't say so, it just doesn't ever display the point that has perfectly sensible coordinates.

‎02-01-2017

Update, in case anyone has the same question: I at least partly worked this out: use the "Define Mosaic Dataset NoData" tool. Now I just need to work out the best compromise method for non-zero values in the overlap.

‎02-01-2017

I have lovely, untouched Landsat 8 images from USGS that I would like to merge/mosaic. However, I can't find a function to somehow ignore the zero-value wedges. I also processed a stack of files so that they don't have the zeroes but when I add those to a mosaic dataset, Arc seems to lose its s*&^ and jumbles up the values in the output bands (and for many, just puts in the maximum value, not the value from the input).

‎06-12-2016

I have a vector layer which I converted to a raster. I want to see the raster with the same colours. Why is this hard?

‎05-13-2016

I'm just now having similar frustrations with Spatial Analyst on V10.3 on a Windows 10 PC. Haven't previously had any regular crashes with ArcMap; I've been working through a certificate course in GIS. Currently finding most processing works, but sometimes can't that far: when using extract by Attributes, I got a crash if I tried to save the expression (unless I did that before selecting the input raster). And now I get a crash as soon as I load the Raster Calculator. RasterEngine.dll appears to be in a sensible location.

‎04-08-2016

The drivers are up to date. Not sure it's not 64-bit windows being picky about 32-bit and 64-bit applications... Edit: Not sure it's that particularly, but it IS a windows display setting with some recent versions.

‎04-08-2016

Not QUITE latest of Arc I think. It's a one-year student licence while I'm studying a certificate course and I'm not sure I can update. I'm on 10.3.0.4322. The video driver's been updated since the new year I think, so it should be good. With ArcCatalog it's always like that, but ArcMap is only triggered to jump occasionally.

‎04-08-2016

On my PC ArcCatalog has a bug where it doesn't display at full resolution (the software itself, not data views). ArcMap sometimes does the same thing. I've attached at image of part of two windows: ArcMap functioning properly (at 1920x1080) with ArcCatalog alongside at whatever subsampled resolution it has adopted. I am using a Dell laptop with Windows 10, with an AMD Radeon R7 M270 graphics card. I think the drivers are up to date. I think this issue also occurred with Windows 8.1 but it's been a few months since updating.

‎04-03-2016

Thanks, found another similar post (don't know why it took so long to even find this post): How to Remove Decimal Points From Measured Grid Units It's buried way more deeply that it should be...and I still think 6 decimals is a pretty silly default.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by MatthewNoteboom

Re: How to force Dissolve to put ALL features together?

Tabulate Area results greater than area of input zones

Re: How to force Dissolve to put ALL features together?

Re: How to force Dissolve to put ALL features together?

How to force Dissolve to put ALL features together?

Re: How do i add a point to a shapefile so that it has (not null) geometry?

How do i add a point to a shapefile so that it has (not null) geometry?

Re: Mosaic Landsat 8 without black bands

Mosaic Landsat 8 without black bands

i want to use my vector colours in a raster!!!

Re: 10.1 - Instant crash on any (all?) spatial analyst tools.

Re: arccatalog doesn't display at screen resolution

Re: arccatalog doesn't display at screen resolution

arccatalog doesn't display at screen resolution

Re: change number of decimals on graticule

Re: change number of decimals on graticule