On Sat, Jan 2, 2021 at 7:59 AM Michael Saupe wrote:
> Hi Evan,
>
> thank you for the explanation. That makes sense. However, in my opinion
> ogr2ogr behavior is not really consistent in this case: The column ogc_fid
> , which is in fact the track id, is incremented on each gpx file import (
> reg
Hi,
For my mind the behavior is consistent. FID (in this case named as ogc_fid)
is a unique feature ID and tracks table contains tracks so it is natural
that FID is increasing when more tracks are added - and it must increase or
otherwise the FID is not unique. The track_points table contains poin
Like Richard, I live and hike in a region with a substantial amount
of steep, cliffy terrain, so the bunching of contour lines serves a
useful purpose - "Stay away". That said, the Swiss maps suggest a
multi-step procedure.
Assuming we have a DEM -
1. Compute the the
I am referring to ogc_fid of 'tracks' table.
Am 02.01.2021 um 15:59 schrieb Michael Saupe:
> Hi Evan,
>
> thank you for the explanation. That makes sense. However, in my opinion
> ogr2ogr behavior is not really consistent in this case: The column ogc_fid ,
> which is in fact the track id, is in
Hi Evan,
thank you for the explanation. That makes sense. However, in my opinion ogr2ogr
behavior is not really consistent in this case: The column ogc_fid , which is
in fact the track id, is incremented on each gpx file import ( regardless if
you use -update -append or not ).
Michael
Am 02.
On vendredi 1 janvier 2021 22:09:47 CET Stephen Woodbridge wrote:
> 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 gd
On Fri, 1 Jan 2021, Stephen Woodbridge wrote:
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 pr
Michael,
You have a single track in each file, so it is expected that track_fid doesn't
change and is set at 0 (as there's no attribute to uniquely identify a track)
For what you want to do (that is have distinct track_fid for each file),
you'll likely have to use an intermediate postgresql sche
