Tag Info

New answers tagged

1

I would make sure that there are no duplicate polylines lying underneath the 6 polylines that you can see and that you haven't accidentally inserted any other objects into the table. A good way to do this is to do a boundary select on one of the buffers that is returning the wrong count and browse the results. Then select each record in turn in the browser ...


3

If you have the purple polygon selected when you perform the clip it will only output the selected polygon.Deselect all the features you plan on clipping and try the clip again. That should clip everything to the larger polygon.


0

You can solve the geodesic intersection problem using the ellipsoidal gnomonic projection. The method is described in §8 of my paper, Algorithms for geodesics, and code to implement the solution using GeographicLib is available here


1

It is apparent that you are using a 9/9.3 example that clipped rasters. Here's a markup to show you the difference: # Import system modules # import sys, string, os, arcgisscripting #9/9.3 geoprocessor, use arcpy instead import arcpy, os, sys, string from arcpy import env #from arcpy.sa import * # don't need this, you're not doing any Spatial Analyst ...


0

Takes effing forever, but QGis's dissolve tool does work. I'm not sure why it takes so damn long, but you can dissolve everything in your layer via the "--Dissolve all--" option. Adding a spatial index or something might help I dunno but this option takes forever running inside of qgis before: after (10 minutes later on a very fast mac): And to ...


2

Using the tools in ArcGIS, if I understand your question correctly: You can use 'Tabulate Intersection' to calculate the % of area overlap between your two polygon layers (using FID as your zone field) and join the output to the appropriate polygon layer. Then use spatial join to join the attributes from one layer to the other. You can then delete any ...


1

Problem "solved". I just deleted the Select Layer By Attribute (9) and re-replaced it with a new Select Layer By Attribute process. When I revalidated and ran the model, the intersect worked, and everything looks like it's supposed to. Maybe I don't get some fundamental thing about ModelBuilder, but it looks like the order you place tools on the whiteboard ...


1

So you've confirmed that the select layer by attribute is definitely selecting your polylines. Well here is a list of potential problems: Your polyline and erase layers are different coordinate systems The erase layer has a selection on it so it never clips the area you expect? The erase layer must be a polyline or polygon layer (i.e. higher geometry ...


0

I don't know for sure, but I think something like this might solve your problem (this wont work on multilines, but you could stdump them or squish them) : SELECT ID, COUNT(*) AS theCOunt FROM ( SELECT id, ST_Intersection(A.geom, B.geom) AS geom FROM ( SELECT xx.id, xx.id2, st_makeline(xx.l_start, ...


1

Right click on Active_ESA, select Add to Display and rerun entire model



Top 50 recent answers are included