I too have run into this problem in the past, though I believe, if you are
to use gdal_contour you have access to the underlying DEM/TIN/LAS, and if
you have that it's much easier just converting it directly to polygons
(using the technique Jamie posted, or similar ones). It could be a
gdal_contour
On jeudi 19 octobre 2017 23:56:29 CEST Tamas Szekeres wrote:
> It looks like DOWNLOAD_SCHEMA=NO would do the trick, but if I use this in a
> VRT file this way it crashes GDAL.
Just fixed the crash (related to the HTTP driver and GDAL_OF_SHARED open flag)
You can also prefix the URL with /vsicurl_
It looks like DOWNLOAD_SCHEMA=NO would do the trick, but if I use this in a
VRT file this way it crashes GDAL.
http://cstest.coordinatesolutions.com/geoserver/wfs?VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=ogi:okcounties&SRSNAME=EPSG:900913
NO
E
On Thu, Oct 19, 2017 at 2:04 PM, Even Rouault
wrote:
> On jeudi 19 octobre 2017 13:38:38 CEST James Klassen wrote:
> > Has anyone looked at reading curved geometries from an Esri rest service
> > queried with "returnTrueCurves=true"?
> >
> > My end goal is to import the data into PostGIS. We were
On jeudi 19 octobre 2017 22:55:50 CEST Tamas Szekeres wrote:
> Hi all,
>
> It looks like whenever we have a dataset (shapefile,db table,etc...) which
> has a
> column with such names like "description", "name", "location" GeoServer
> maps it to the elements in the gml namespace (in a 1.1 request),
Hi all,
It looks like whenever we have a dataset (shapefile,db table,etc...) which
has a
column with such names like "description", "name", "location" GeoServer
maps it to the elements in the gml namespace (in a 1.1 request),
therefore DescribeFeatureType doesn't contain these attributes.
For exa
echo 2 49 | /build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
-t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0
+ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on
OGRCT: PROJ >= 4.8.0 features enabled
OGRCT: Using locale-safe proj version
OGRCT: Sourc
On jeudi 19 octobre 2017 13:19:52 CEST Chris Marsh wrote:
> Hi,
>
> I build GDAL by specifying --with-static-proj4 on the configure command
> line. This does not seem to have resolved the problem.
>
> echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
>
> > -t_srs EPSG:32632
Hi,
I build GDAL by specifying --with-static-proj4 on the configure command
line. This does not seem to have resolved the problem.
echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
> -t_srs EPSG:32632
> -11818.9526229417 5451106.95020125 0
Cheers
Chris
On 18 October 2017 a
On jeudi 19 octobre 2017 13:38:38 CEST James Klassen wrote:
> Has anyone looked at reading curved geometries from an Esri rest service
> queried with "returnTrueCurves=true"?
>
> My end goal is to import the data into PostGIS. We were successful using
> ogr2ogr to translate the curved features fro
Has anyone looked at reading curved geometries from an Esri rest service
queried with "returnTrueCurves=true"?
My end goal is to import the data into PostGIS. We were successful using
ogr2ogr to translate the curved features from a geodatabase download in the
past, but that download is being repla
>From a user perspective, this can be done pretty easily using gdal_calc.py
& gdal_polygonize.py. I've used this technique in the past several times.
This doesn't help with gdal_contour of course, but is a viable way of doing
the same thing. Maybe worth considering as a new python tool.
Using a ra
Hi Gregers,
Thanks for your reply.
The question was not "how to" yet, but "shall I" ;o)
I think I did something similar to the "ends matching" in a python
script that creates those polygons (in a particular context that also
requires tiling).
What I'd like to know, is if there is a reason why i
On jeudi 19 octobre 2017 14:11:45 CEST Vincent Mora wrote:
> Hi all,
>
> I know this is old stuff (references below), but making polygons instead
> of lines would be a great option for gdal_contour IMO.
>
> It could be also another program included in gdal/app (if it is already,
> I can't find it
Hi Vincent,
> I know this is old stuff (references below), but making polygons instead
> of lines would be a great option for gdal_contour IMO.
>
> It could be also another program included in gdal/app (if it is already,
> I can't find it).
>
> What do you think, shall I add that ? If yes, first o
Hi all,
I know this is old stuff (references below), but making polygons instead
of lines would be a great option for gdal_contour IMO.
It could be also another program included in gdal/app (if it is already,
I can't find it).
What do you think, shall I add that ? If yes, first or second option
16 matches
Mail list logo