What's New
This page tracks notable new capabilities as they're added to Velocity. Each entry links back to the change that introduced it.
| Reference | Feature | Description |
|---|---|---|
| #130 | PostgreSQL geography-aware spatial indexing | Spatial indexes on a PostgreSQL geometry column can now also index that column's geography representation, so distance and buffer calculations expressed in real-world units or compared against a Geography value, can use an index instead of scanning the whole table. Enable it with the new IndexGeographyCast connection setting. |
| #131 | Streaming imports for large CSV files | ImportData can now read a CSV file in chunks and send each one as it is read, instead of parsing the whole file into memory first. Pass streamImport: true to enable it; the chunk size is the existing ImportBatchSize connection setting. Peak memory stays flat no matter how large the file is. See Streaming Large Files. |
| #132 | GeoJSON import | ImportGeoJSON loads a GeoJSON file into a table, appending rows the way a CSV import does. Every object GeoJSON allows at the top level is accepted, a FeatureCollection imports one row per feature, and a bare Feature or a bare geometry of any type imports one. Each part of a Feature is mapped separately with GeoJSONImportConfig: the geometry, the top-level id member, which needs its own mapping because it is not one of the properties, and the properties themselves, including nested ones addressed by a dotted path such as contact_info.manager. A path that does not resolve imports as null, so features that omit optional details need no special handling. Supports the same streamImport flag as ImportData. See Importing GeoJSON. |
| #133 | SpatialDWithin — indexed "within a distance" queries |
New spatial function that tests whether two locations are within a given real-world distance of each other, returning true or false directly rather than requiring a separate distance calculation and comparison. On PostgreSQL this can use a spatial index, making it significantly faster than computing an exact distance for every row. PostgreSQL only, see Geospatial Support for the portable alternative. |
| #134 | GeometrySrid — configurable spatial reference for Geometry columns |
The spatial reference system used for Geometry columns is now a connection setting in its own right rather than a fixed value, so planar data can be stored under a known projection such as Web Mercator instead of always being written as "no coordinate system". It is applied everywhere the fixed value used to be, column creation, parameter and literal binding, and bulk imports, and defaults to 0, or to 1 on DB2, Oracle and Teradata, whose spatial catalogues reserve that identifier for data with no coordinate system. The existing DefaultSrid setting, which only ever applied to Geography, is renamed GeographySrid to match. See Geospatial Support. |
See Also
- Indexing - Creating and managing indexes, including spatial indexes
- Geospatial Support - Working with geometry and geography data