Releases: simonw/geojson-to-sqlite
Releases · simonw/geojson-to-sqlite
1.1.1
- Fixed a bug where a
_tmp
column remained after importing a geometry with no additional properties. #30
- Added
--version
option to show the current installed version of the tool. #32
1.1
- Command can now accept more than one GeoJSON file. The contents of all of the files will be inserted into the same table. #21
- Using the
--spatial-index
option against the same database twice no longer triggers an error.
- Now depends on sqlite-utils 3.23 on higher, taking advantage of the SpatiaLite utilities in that library. Thanks, Chris Amico. #28
1.0.1
- Fixed bug where
--spatialite
option failed with an error if the GeoJSON features being loaded consisted of just a geometry with no properties. #30
1.0
- New
--properties
option for writing GeoJSON properties to a JSON column called properties
- or use --properties=props
to write to a column called props
. Thanks, Chris Amico. #25
0.3.1
- Fixed bug where the
id
column did not come first in the table schema. #20
0.3
- New
--nl
option for consuming newline-delimited GeoJSON - thanks, Chris Amico! #13
- New
--spatial-index
option which creates the table using SpatiaLite and adds a spatial index for the geometry column. #17
0.2
If the GeoJSON features have an "id"
property it will now be used as the primary key, unless you specify another primary key using --pk=property
or you disable primary keys entirely (hence using a SQLite rowid
) with --pk=''
. Thanks, Chris Amico. #11
0.1.1
Fixed table creation bug with --spatialite
option, #6
0.1
First non-alpha release. All documented features are now implemented.