On 1/1/2021 9:47 PM, Richard Greenwood wrote:
On Fri, Jan 1, 2021 at 2:36 PM Stephen Woodbridge
mailto:stephenwoodbridg...@gmail.com>>
wrote:
Hi all,
I'm contouring bathemetry data using gdal_contour and it works really
great. The problem I have is that when depth falls off rapidl
On Fri, Jan 1, 2021 at 2:36 PM Stephen Woodbridge <
stephenwoodbridg...@gmail.com> wrote:
> Hi all,
>
> I'm contouring bathemetry data using gdal_contour and it works really
> great. The problem I have is that when depth falls off rapidly like at
> the continental shelf or into a canyon, I get too
Hi all,
I'm contouring bathemetry data using gdal_contour and it works really
great. The problem I have is that when depth falls off rapidly like at
the continental shelf or into a canyon, I get too many contour lines
that all bunch up. If I change the contour step size to fix this, then
the
clarification: second table of my points is 'track_points'.
Also adding my 2 gpx files for reference:
*file1.gpx:*
http://www.topografix.com/GPX/1/1";>
1
1
1
2
2
Hello folks,
I am importing multiple gpx files into a postgis database. The tables 'tracks'
and 'track_points' are created / updated.
The column track_fid in in the track_points table should be a reference to the
track feature id as documented in https://gdal.org/drivers/vector/gpx.html,
howev
I'm trying to create a geopdf using gdal_translate. However, the basic
styling options provided by GDAL don't work. viz:
- PEN: dash patterns for Linestrings don't work
- LABEL: angle (a:) option for Points doesn't work, when {angle} needs to be
read from feature
properties (ex: a:{rotation}). Man
