People at sohu say this setting is useful because the result of the query, rounded up with python's round function, takes three times longer than all the other commands combined.It's a question someone on StackOverflow asked.

The gdal/swig/python/samples/ogr_layer_algebra.py should be promoted to an official Python script

Steps:

• move it to gdal/swig/python/scripts
• create a new test script for it in autotest/pyscripts/test_ogr_layer_algebra.py
• write a documentation page in doc/source/programs/ogr_layer_algebra (and link it to the index)

We should add type aliases like type UnitVector3<N> = Unit<Matrix<N, U3, U1, Owned<N, U3, U1>>>; to simplify their uses, e.g., in SIMD code: UnitVector3::from([v1, v2, v3, v4]).

When I edit a polygon with a zoom level low and I snap this polygon to another one, it's very common the created snap point is not exactly on the line / point.
For me, it's a problem regarding I control if these polygons are not intersecting.

Description
The rendering engine hogs all available CPU cores by default. I think it would be good to allow user to limit the amount of cores Synfig uses. For example, I usually listen to various playlists on YouTube while I'm working and in some cases those CPU spikes to 100% when Synfig renders current frame is noticeable.

It would be good to have such setting in "Preferences->Render" di

Add Runnable links of the code below the example.
Use link name Run Code which links to a Online C++ complier conatining the example code.
Use Rextester as the Online C++ Compiler (If you have a better suggesstion please comment).

Follow below steps to generate the Run Code Link.

1. Go to Rextester
2. Copy or write the example

An option like $ fio cat --bounds w s e n --bounds-crs <crs> --dst-crs <crs> would allow for filtering prior to reprojection, like $ ogr2ogr -spat w s e n -spat_srs <crs>.

See Toblerity/Fiona#210 for a discussion about standardizing bounding boxes as --bounds w s e n rather than --bbox w,s,e,n.