On Thu, Mar 19, 2015 at 5:03 PM, Even Rouault
wrote:
> Selon Ari Jolma :
>
> > 19.03.2015, 05:55, Even Rouault kirjoitti:
> > > Hi,
> > >
> > > The build of Ruby bindings is broken in trunk. See
> > > http://trac.osgeo.org/gdal/ticket/5880
> > >
> > > The situation is that, in years, nobody has r
Selon Ari Jolma :
> 19.03.2015, 05:55, Even Rouault kirjoitti:
> > Hi,
> >
> > The build of Ruby bindings is broken in trunk. See
> > http://trac.osgeo.org/gdal/ticket/5880
> >
> > The situation is that, in years, nobody has really maintained them, so it
> isn't
> > even sure that they work at run
19.03.2015, 05:55, Even Rouault kirjoitti:
Hi,
The build of Ruby bindings is broken in trunk. See
http://trac.osgeo.org/gdal/ticket/5880
The situation is that, in years, nobody has really maintained them, so it isn't
even sure that they work at runtime once compilation issues are fixed. So we
m
Hi
I checked PostGIS and it implements all M related stuff in a component
called lwgeom, the other functions are called from geos. I think that
it might be better to work, first, on fully compatibility with PostGIS
and then start to see other drivers because of the time it takes to
get familiar wit
Hi,
The build of Ruby bindings is broken in trunk. See
http://trac.osgeo.org/gdal/ticket/5880
The situation is that, in years, nobody has really maintained them, so it isn't
even sure that they work at runtime once compilation issues are fixed. So we
might just have to wipe them out, or remove th
Hi,
I am testing new Boolean data type in OpenJUMP which is saved as Logical when
data are exported into shapefiles. Kosmo GIS supports Logical already and
Geotools and gvSIG as well. I said Logical is well defined but that is not
totally true. Some implementations seem to use space to mean not
Selon Jukka Rahkonen :
> Hi,
>
> Is there some special reason why the shapefile driver does not support
> Logical (Boolean) data type for attributes? It seems that the "L" data type
> is there in dBase III format
> https://ulisse.elettra.trieste.it/services/doc/dbase/DBFstruct.htm#C1.4 and
> even
Hi,
Is there some special reason why the shapefile driver does not support
Logical (Boolean) data type for attributes? It seems that the "L" data type
is there in dBase III format
https://ulisse.elettra.trieste.it/services/doc/dbase/DBFstruct.htm#C1.4 and
even well defined Value: "? Y y N n T t F
Hi,
I am a masters student from IIIT Hyderabad and currently in my final year
of study and working in the Lab for Spatial Informatics here.
I was a part of GSOC 2014 and worked on the project *'Schematization Plugin
for QGIS'* last year [1][2].
I am interested in the project *'Integration of cpp
My objective is to create a hillshaded color-relief image of a DEM using
commandline/programmatic means only, so the process >can be automated
and combined within an existing GMT/GDAL workflow.
If your workflow includes GMT that you have a reach panoply of methods to
do shade illuminati
With 1000 tables, the disparity is 300ms for the join on geometry_columns and
30ms for the straight system table query.
Still, not something that should be noticeable (really) in the context of a
batch query. I guess actually it would be twice as big, since the OGR query
runs twice (once for ge
OK, yeah, even w/o populating my database with 1000 tables, I can see the
timing difference between joining with geometry_columns, and just hitting
system tables directly
-- joined with geometry columns (14ms)
SELECT
c.relname, n.nspname, c.relkind,
g.f_geometry_column, g.type, g.coord_dimens
Yes, that’s what ‘f’ is.
It could just be that on a database with N-hundred tables the query would be
slow regardless. Something I’ll do a quick test of.
I’m writing up a few variants to go into those slots for different versions.
P
--
http://postgis.net
http://cleverelephant.ca
On March
On Wed, Mar 18, 2015 at 09:58:20AM -0700, Paul Ramsey wrote:
> There’s also a couple new relation types, ‘m’ for materialized
> views and ‘f’ for… gah! I don’t know.
I think 'f' is for foreign data tables.
It's surprising that joining a view on catalogue tables considerably
slows down. Shouldn'
On March 18, 2015 at 9:53:58 AM, Even Rouault (even.roua...@spatialys.com)
wrote:
>
> It certainly is. I think the performance issue appeared with PostGIS 2.0 when
> geometry_columns has become a view.
>
> > Probably either the query should just use the
> > system tables alone, and take adv
Hi Paul,
> We noticed that in databases with lots of tables, OGR throws some pretty
> crazy SQL at the database, and things get slow and the source of the problem
> seems to be here:
>
>
http://trac.osgeo.org/gdal/browser/trunk/gdal/ogr/ogrsf_frmts/pg/ogrpgdatasource.cpp#L851
>
> Which in addition
Gareth,
Frank implemented a method to merge a hillshade and color-mapped image
in GDAL/python (called hsv_merge.py). This code could be changed to meet
your needs. Otherwise you might be able to stretch the hillshade using the
scale parameter in gdal_translate prior to using hsv_merge.py.
https
We noticed that in databases with lots of tables, OGR throws some pretty crazy
SQL at the database, and things get slow and the source of the problem seems to
be here:
http://trac.osgeo.org/gdal/browser/trunk/gdal/ogr/ogrsf_frmts/pg/ogrpgdatasource.cpp#L851
Which in addition to being a big quer
Hi - firstly, apologies if the gdal-dev mailing is not the appropriate
mailing list, please advise a more suitable place to post if so.
My objective is to create a hillshaded color-relief image of a DEM using
commandline/programmatic means only, so the process can be automated and
combined withi
Hi again,
the issue is fixed now. It turned out that there was some hidden and
"suboptimal" work around in older source code which caused the newer PROJ4
version 1.11 to crash. Removing that solved the problem.
Regards
Niels
Von:niels.vonfestenberg-packisch@rohde-schwarz.com
An:
Oracle definitely supports M.
Mike
Michael Smith
US Army Corps
Remote Sensing GIS/Center
michael.sm...@usace.army.mil
On 3/17/15, 11:20 PM, "Even Rouault" wrote:
>Selon Daniel Morissette :
>
>> FWIW I think support for M would be a very welcome addition. An
>> immediate use I'd see fo
21 matches
Mail list logo
