Re: [gdal-dev] Why are fields required in osmconf.ini file?

georges wrote > Thank you for the quick reply Even! > > So this required predefined set of fields is a necessary step for any .osm > file conversion with ogr2ogr.exe? > Not only conversion from .osm to .shp? > But also to .pbf, geojson etc. ? Only exception and highly recommended if you want to

[gdal-dev] Converting MULTILINESTRING to LINESTRING

Hi! Sorry if it's not the appropriated place to ask this, but is there a way to convert MULTILINESTRING to LINESTRING? For example: = ogr2ogr -f "SQLite" -gt 65536 -dsco SPATIALITE=YES database.sqlite shape.shp ERROR 1: Cannot insert feature with geometry of type MULTILINESTRING in column

Re: [gdal-dev] Why are fields required in osmconf.ini file?

Le jeudi 17 novembre 2016 22:20:02, Djordje Spasic a écrit : > Hello, > > When converting an .osm file to .shp files with ogr2ogr.exe, one needs to > define a list of required fields (keys) in gdal-data\osmconf.ini file, for > each geometry type (points, lines, multipolygons,

Re: [gdal-dev] Index Tiling Questions for WMTS, Bing, Google/TMS

Le jeudi 17 novembre 2016 21:53:47, esacree a écrit : > A few questions based on the GDAL examples for Google, Bing/VirtualEarth > and WMTS tile servers. > > 1. Google Maps has the tile/image origin in the upper left corner. TMS > has the tile image origin in the lower left corner. Where

Re: [gdal-dev] Recommended lib Curl version for GDAL 2.1.2 and WMTS

Le jeudi 17 novembre 2016 21:37:52, esacree a écrit : > Which version of libCurl is recommended for use with GDAL 2.1.2 and the > GDAL_WMTS driver? None in particular. Should hopefully work will all of them issued in the last 5 years. > > We have been using libCurl version 7.45 dated

[gdal-dev] Index Tiling Questions for WMTS, Bing, Google/TMS

A few questions based on the GDAL examples for Google, Bing/VirtualEarth and WMTS tile servers. 1. Google Maps has the tile/image origin in the upper left corner. TMS has the tile image origin in the lower left corner. Where should the tile/image origin be for Google maps when using the

[gdal-dev] Recommended lib Curl version for GDAL 2.1.2 and WMTS

Which version of libCurl is recommended for use with GDAL 2.1.2 and the GDAL_WMTS driver? We have been using libCurl version 7.45 dated 7-Oct-2016. The newest version is 7.51 dated 2-Nov-2016. 7.51 contains a very long list of fixes. The upgrade could be time consuming to rebuild everything.

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Hi, a) If you look at this code here [1] from the raster driver, there are two function, FIND_GEOG_CRS and FIND_PROJ_CRS, that uses the WKT string to find matches with inside SRS. That runs independently from Authority code and returns a list of possible matches SRIDs. The driver takes the

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Hi, Probably SDO_COORD_REF_SYS is what to use nowadays even I guess that it points to MDSYS tables. Looks like something has changed with Oracle 10.2 and I believe that it is very hard to use so old Oracle version without paying much extra.

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Le jeudi 17 novembre 2016 14:19:10, Ivan Lucena a écrit : > Hi Even, > > Did you try your change? Yes > > There has been a lot of changes in both sides over the years that are not > reflected on the OCI driver code. > > That hard coded SRID conversion should be deleted since EPSG is fully >

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Hi Even, Did you try your change? There has been a lot of changes in both sides over the years that are not reflected on the OCI driver code. That hard coded SRID conversion should be deleted since EPSG is fully supported now. He georaster driver uses some PLSQL functions to try to match WKT

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Le jeudi 17 novembre 2016 12:49:09, Michael Smith a écrit : > Yes even the current version needs the layer creation option for dim. I > would be +1 for this change (never really understood why it was this way). > I think we are probably one of the biggest users of the oracle driver and > I think

Re: [gdal-dev] Ogr2ogr -dim and Oracle

For the srid, I would say keep that as an srs doesn't always map cleanly to an srid. Sent from my iPhone > On Nov 17, 2016, at 5:54 AM, Rahkonen Jukka (MML) > wrote: > > Hi, > > I would also check how ogr2ogr options –a_srs and –t_srs behave or if the

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Hi, I would also check how ogr2ogr options –a_srs and –t_srs behave or if the OCI driver option –lco SRID is still needed. -Jukka- Lähettäjä: Michael Smith [mailto:michael.smith.e...@gmail.com] Lähetetty: 17. marraskuuta 2016 13:49 Vastaanottaja: Rahkonen Jukka (MML)

Re: [gdal-dev] Ogr2ogr -dim and Oracle

Yes even the current version needs the layer creation option for dim. I would be +1 for this change (never really understood why it was this way). I think we are probably one of the biggest users of the oracle driver and I think this would be a good improvement. Sent from my iPhone > On Nov

Re: [gdal-dev] Ogr2ogr -dim and Oracle

On jeudi 17 novembre 2016 08:06:24 CET Rahkonen Jukka (MML) wrote: > Hi, > > I noticed that Even was editing the ogr2ogr help about the -dim parameter > and remembered that I think that it does not have an effect on the OCI > driver. For forcing a new Oracle table into 2D you must use the OCI

[gdal-dev] Ogr2ogr -dim and Oracle

Hi, I noticed that Even was editing the ogr2ogr help about the -dim parameter and remembered that I think that it does not have an effect on the OCI driver. For forcing a new Oracle table into 2D you must use the OCI drivers own layer creation option "DIM" instead