New answers tagged

1

The following is a 4-step approach with standard QGIS functions which might get what you want. Here's the TLDR: Buffer the fences Split the buffers along all boundaries Extract the overlap areas Remove the parts of the river that fall within the overlaps Here's a more detailed explanation: 1. Buffering the fences "Vector --> Geoprocessing Tools --> ...


0

AFAIK WPS only supports XML as the request format, the formats you are seeing in the DescribeProcess document are for the encoding of the geometry element. So your request should look something like: <?xml version="1.0" encoding="UTF-8"?><wps:Execute version="1.0.0" service="WPS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://...


0

I think your for loop is incorrect. Since texasPipeline.graphics is an array, you would use forEach instead of for ... in. You can get even fancier by using array.map to turn them into an array of graphics in one line. Here's a JSFiddle illustrating that. Hope this helps! https://jsfiddle.net/gavinr/rbcagx93/


1

What I would try: Densify river lines. Draw perpendicular lines on vertices. Split perpendicular lines by riverlines. Classify perpendicular lines left / right with sidebuffer. Analyse linecrossings perpendicular lines with fencelines. Join results to vertices. Check where left and / or right did not cross fencelines. I would use FME Desktop (build ...


0

One possibility is to do a polygon buffer around each toxic site point: Main Toolbar > Vector > Geoprocessing Tools > Buffer(s) This will provide radial areas of interest around the sites, geometries which can then be used too... ...find any address points contained therein: Main Toolbar > Vector > Research Tools > Select By Location All of this ...


2

Right now the closest you can get is to set the End Cap Style to square and the Stroking Density to 1. Inside corners get a single point, but outside corners get two points, meaning it's probably not quite what you want. However, the Bufferer was updated for FME2017 and now includes parameters that would allow you to do keep angles intact. If you're OK with ...


0

You're gonna need to use WPS, Take a look at this. It has all your answers.


4

As commented by @Kirk Kuykendall, it appears your buffer is being saved into a Shapefile. Shapefiles do not support true arcs/curves, so saves the features with multiple segments. Shapefiles do not support true parametric curves, including circular arcs, ellipses, and B├ęzier curves, so these shapes are stored as straight segments. True curves are ...


2

I haven't looked at this in a long while, but as far as I know it hasn't changed. ArcGIS draws the buffers at a fixed graphical resolution, so they appear smooth when viewed at that zoom level but if you zoom in you see the straight lines as you observe. If you zoom in the layer to buffer and then run the buffer tool you should see that these straight ...


3

It's not the most efficient way to do this. Instead of creating buffers and looking for intersections, you can do this with scipy.spatial library. First get all of your points (accidents) as numpy array. From csv file it will be: from scipy import loadtxt data = loadtxt("/path/to/file.csv", delimiter=",") Then you can use the most efficient way to find ...


3

What you want is: SELECT ST_Buffer(geometry_column, 0) FROM scheme.table Where geometry_column is the column within your table (scheme.table) that contains your geometry. You current result of: ---------------------- 010300000000000000000 (1 row) Looks correct, that is the well known binary version of the geometry, or how PostgreSQL sees it. For ...


0

You can check the link geospatialearth site link. You need to allow Adobe flash in your browser. Firefox is recommended. As a programmer, to create a buffer of a point you can use geographiclib javascript along with js2shapefile. You will be able to create numerous equi-angled points at a fixed distance x around every point of the csv file using ...


0

Paraphrasing a comment by @SaultDon: If the buffers use ARCS/CURVES instead of regular linestrings, then be aware that the openfilegdb and esri filegdb api driver both don't support curves in geometries unfortunately. See QGIS 2.8.1 OpenFileGDB compatibility with ESRI FileGDB?



Top 50 recent answers are included