vector

Is there an existing issue for this?

• I have searched the existing issues

What would you like to be added?

I would like to add DataType_UInt64.

Why is this needed?

Databases like mysql support unsigned integer numbers through keywords such as UNSIGNED.
In order to enrich the data type, we have no reason not to support it.

Anything else?

No response

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

In the event payload the return type of layer is `L.Layer? so it needs to be casted to the Layer-Type.

layer.on('pm:edit', (e) => {
  if(e.shape === 'Polygon'){
     (e.layer as Polygon).getLatLngs();
  }
});

I think following should work too: (But not tested)

layer.on('pm:edit', (e) => {
  if(e.layer instanceof L.Polygon){
     (e.layer as Polygon).getLatLngs();
  }

Is your feature request related to a problem? Please describe.
I'm always frustrated when I'm typing a new value for a parameter and I gave up on this edition, but I can't cancel it by keyboard.

Describe the solution you'd like
By pressing Esc I should be able to cancel my in-going edition on the Value column of the Parameters Panel as I'm able to when editing a layer name in the La

Currently there is no mention of the important function st_relate() in Chapter 4 or anywhere in the book.

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

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.