vector

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

We've see many people complain about Milvus 2.0 spent too many disk spaces.

One thing we can do is do compress the binlogs and check if we can get some compression ratio, If so compression should also help the load speed due to saved IOs

D

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)

I've come across a weird behavior that really baffled me initially.

This compiles with nalgebra 0.29:

let _: nalgebra::SVector<f32, 3> = nalgebra::point![1.0, 2.0].into();

It converts an OPoint<f32, 2> into an SVector<f32, 3>, using Into.

Here's the same, with debug output:

let v: nalgebra::SVector<f32, 3> = dbg!(nalgebra::point![1.0, 2.0]).into();
dbg!(v

This is a ToDo-Issue.

Following events should be added:

• while moving the hintMarker a event should be fired like move or change. For example, while drawing the rectangle, the current bounds / latlngs can be useful. see #1072
• While moveing / editing the coords of a layer, we can send a coordsmove event. Edit, Drag, Rotation, ...
• Enabledrag & disabledrag in Dragging.js

synfig v1.4.2 windows 10 21h1

There are few panels I want to move a bit to the bottom, but it seems like they're locked to a particular minimum size which was not the case in older version of synfig.
Please lower the minimum size of the those panels.

https://user-images.githubusercontent.com/50204208/126040293-93e7fa2e-2894-4e49-8fd9-bc93747a805e.mp4

This is for first-time-contributors :
Add functions which belong to a particular header file in its corresponding .md file inside the header folder.
For example
std::sort belongs to algorithm header file, so make a new file sort.md inside the algorithm directory while maintaining the CONTIBUTING gu

Context: this from @agila5: https://twitter.com/a_gilardi5/status/1487813588454678528

I have not had a chance to read the explanation and am not sure what we should say on the topic but guess it's worth a mention here. Any thoughts?

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.