Re: [sqlite] geopoly data input options

2018-10-21 Thread Noel Frankinet
Spatialite does to Sqlite what Postgis does to Postgres. Same concepts. Noël On Sat, 20 Oct 2018 at 22:49, Jonathan Moules wrote: > More specifically, in the "Simple Features for SQL" specification: > > http://www.opengeospatial.org/standards/sfs > > and if you have access (or gobs of money),

Re: [sqlite] geopoly data input options

2018-10-20 Thread Jonathan Moules
More specifically, in the "Simple Features for SQL" specification: http://www.opengeospatial.org/standards/sfs and if you have access (or gobs of money), there's the ISO spec (I'm guessing it's the same) - https://webstore.ansi.org/RecordDetail.aspx?sku=ISO+19125-1%3A2004 I'd also suggest

Re: [sqlite] geopoly data input options

2018-10-19 Thread Noel Frankinet
There a WKB and WKT (text) representation). You can probably find everything : http://www.opengeospatial.org Spatialite is also a good source . On Fri, 19 Oct 2018 at 22:47, Richard Hipp wrote: > On 10/19/18, Thomas Kurz wrote: > >> Beginning with the next release, polygons will always be

Re: [sqlite] geopoly data input options

2018-10-19 Thread Richard Hipp
On 10/19/18, Thomas Kurz wrote: >> Beginning with the next release, polygons will always be stored in the >> binary format. > > Is the SQLite binary encoding identical to the Well-Known-Binary geometry > format? That might have happened, except the WKB format was not known to me... Where can I

Re: [sqlite] geopoly data input options

2018-10-19 Thread Graham Hardman
Thanks very much for your prompt reply. I had seen that I could use the geopoly_blob function to copy a json-formatted entry into a new record without getting an error from sqlite, however I was disconcerted when seeing that a select _shape from newtab (using example from documentation)

Re: [sqlite] geopoly data input options

2018-10-19 Thread Thomas Kurz
mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Thomas Kurz >Sent: Friday, 19 October, 2018 09:17 >To: SQLite mailing list >Subject: Re: [sqlite] geopoly data input options >> Beginning with the next release, polygons will always be stored in >the >> binary format. >I

Re: [sqlite] geopoly data input options

2018-10-19 Thread Keith Medcalf
nglists.sqlite.org] On Behalf Of Thomas Kurz >Sent: Friday, 19 October, 2018 09:17 >To: SQLite mailing list >Subject: Re: [sqlite] geopoly data input options > >> Beginning with the next release, polygons will always be stored in >the >> binary format. > >Is the SQLit

Re: [sqlite] geopoly data input options

2018-10-19 Thread Thomas Kurz
> Beginning with the next release, polygons will always be stored in the > binary format. Is the SQLite binary encoding identical to the Well-Known-Binary geometry format? ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] geopoly data input options

2018-10-19 Thread Richard Hipp
On 10/19/18, Graham Hardman wrote: > > My question now is : must I always format my list of vertices as text ( > in json format ) as shown in the documentation. No. Polygons can be either in the GeoJSON format as text, or in a binary format

[sqlite] geopoly data input options

2018-10-19 Thread Graham Hardman
Hi, this is my first post to this group so firstly: thanks for the oportunity to be here. I have long been in awe of sqlite's power and thankful of its open source nature. I see great possibilities for me to use the shape matching functions of the geopoly module to extend an autocad vba