Hello,

I've updated the beta versions of all my software to add improved GPX
1.0 support.  I added several private elements (route color, leg name,
leg description, and leg url) to the GPX files produced by my programs
so that my users could save their data as GPX without losing any info.
I added a File Info dialog similar to Dave's, which also allows the
advanced user to specify an XSLT stylesheet for the GPX file.  I added
a "Publish to Web" feature which allows you to upload your GPX files
to your favorite FTP server.  An example of the output can be found at:
http://home.attbi.com/~topografix/mystic_basin_trail.gpx

For more info, see http://home.attbi.com/~topografix/

The new software is at:
http://www.easygps.com/beta.asp
http://www.topografix.com/beta.asp
http://www.expertgps.com/beta.asp

--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

ping.

c.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

I have posted an announcement of Version 2.0 of Wissenbach Map on
the map_authors group

http://groups.yahoo.com/group/map_authors

in the hope that people will begin to use the format.

I am also now distributing a local-version CD of the Wissenbach Map
program in the Boise area to try to get a few other trails websites
out there, and I've added my web site to the search list on

http://www.travelbygps.com

I hope to see other announcements of programs with support for our
new format out there soon! (In fact, I'm counting on it, as I won't
be supporting my own program with any particular diligence!)

Dave

It would be a cruel world without cordless screwdrivers, ATM
machines, and wysiwyg HTML editors.  What do you use to edit your
XML?  Please dont' tell me "notebook"!
, Doug

--- In gpsxml@y..., "gps_maps" <gps_maps@y...> wrote:
> It would be a cruel world without cordless screwdrivers, ATM
> machines, and wysiwyg HTML editors.  What do you use to edit your
> XML?  Please dont' tell me "notebook"!
> , Doug

I rarely, if ever, edit .gpx files directly. But when I do, I use
wordpad to edit raw text. (I also ride a bicycle to work, every day,
rain or shine, cold or hot.)

You might visit

http://www.xslt.com

for a listing of stylesheet editors to transform xml documents. (I
even saw a stylesheet debugger there, visual XSTL). I tend to be
adverse to expensive new tools, although I do own a cordless
screwdriver!

Doub inquires:

> It would be a cruel world without cordless screwdrivers, ATM
> machines, and wysiwyg HTML editors.  What do you use to edit your
> XML?  Please dont' tell me "notebook"!

Well....I have been known to use notebook for quick on-the-fly changes to
small XML-encoded config files.  Usually use JPadPro or sometimes XMLSpy
otherwise.

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

I am starting a group about GPS (Global Positioning System) in Europe.

Everybody is invited to join

  http://groups.yahoo.com/group/gps-europe/

to join, just send ANY email to:

gps-europe-subscribe@yahoogroups.com

Hello.

I've started an implementation of a program using GPX 1.0.  I intend to
make it freely available.  Though I'm not a an XML jock, I have a few
questions and I hope you can help me capture the intent of GPX.

1) <time> is specified as "conforming to ISO 8601" but that allows a
    plethora of potential encodings.  Is a conforming GPX reader expected
    to handle any of them?  Could I get a clarification on the precise
    allowable members of this field?   Bonus points for providing suitable
    strftime (as in ISO/IEC 9899:1999) specifiers to make it completely
    unambiguous.

2) By my reading, the example file is illegal.

	
http://groups.yahoo.com/group/gpsxml/files/Sample%20XML%20Files/Kevin%20Read%20U\
ntitled.gpx

   This file, among other deviations, contains "lat" and "lon" instead
   of "latitude" and "longitude".   Are abbreviations for the tag names
   really allowed?

3) Does the <url> tag include protocol?   ("http://www.mountwashington.org")

4) Are there guidelines for <sym>?  Tables for Magellan and Garmin would
    be helpful.

5) There is a reference a the elements in <gpx> that links to "Private
    elements" but there is no such tag on the page.   Is additional
    information on this available?


Additionally, this isn't strictly an GPX question, but I suspect this
group has experience on this subject.  Is there a table of "real
world" field sizes for the various makers of GPSRs available?  For
example, I've learned that Magellan supports 8 character waypoints
and 30 character descriptions in Magellan protocol but the NMEA
limits are 6 and 20.  (I've also learned that at least one well known
commercial program crashes when it gets waypoints from my 330 that have
descriptions longer than 20 bytes, so I suspect this is not exactly a
route well travelled.)  Similarly, are there published "best practices"
for adapting "portable" data for the various receivers?  "Truncate this
field from the right, preserving any trailing numeric data", etc.

Thanx for any help you can offer.

RJL

Hello,

Thursday, April 04, 2002, 10:21:48 PM, Robert wrote:

RL> I've started an implementation of a program using GPX 1.0.  I intend to
RL> make it freely available.  Though I'm not a an XML jock, I have a few
RL> questions and I hope you can help me capture the intent of GPX.

Keep us posted on your progress, Robert, and let us know if you run
into other areas of GPX that aren't sufficiently clear.

In general, GPX was designed with these goals in mind:
  - Easy to parse (only ONE way to represent things)
  - Easy for humans to read

RL> 1) <time> is specified as "conforming to ISO 8601" but that allows a
RL>    plethora of potential encodings.  Is a conforming GPX reader expected
RL>    to handle any of them?  Could I get a clarification on the precise
RL>    allowable members of this field?   Bonus points for providing suitable
RL>    strftime (as in ISO/IEC 9899:1999) specifiers to make it completely
RL>    unambiguous.

From http://www.topografix.com/gpx_manual.asp#time
<time>2002-02-10T21:01:29.250Z</time>

Creation/modification timestamp for element. Date and time in are in Univeral
Coordinated Time (UTC), not local time! Conforms to ISO 8601 specification for
date/time representation. Fractional seconds are allowed for millisecond timing
in tracklogs.

By "Conforms to ISO 8601...", we intended that the time format we
chose would be in a standard format, but we didn't intend that all
ISO 8601 representations would be valid in GPX.  GPX 1.0 is more strict,
and only allows two representations: ("Easy to Parse")

1. <time>2002-02-10T21:01:29.250Z</time>   (fractional seconds)

2. <time>2002-02-10T21:01:29Z</time>       (no fractional seconds)

RL> 2) By my reading, the example file is illegal.

RL>        
http://groups.yahoo.com/group/gpsxml/files/Sample%20XML%20Files/Kevin%20Read%20U\
ntitled.gpx

RL>   This file, among other deviations, contains "lat" and "lon" instead
RL>   of "latitude" and "longitude".   Are abbreviations for the tag names
RL>   really allowed?

lat and lon are the correct tag names.  "latitude" and "longitude"
aren't allowed.  The guiding rule was "choose a tag name that's long
enough to be understandable, but balance that against a desire for
small file sizes".

I've corrected the manual to remove references to "latitude" and
"longitude".  Please excuse my earlier error.

RL> 3) Does the <url> tag include protocol?   ("http://www.mountwashington.org")

Yes.

RL> 4) Are there guidelines for <sym>?  Tables for Magellan and Garmin would
RL>    be helpful.

http://www.topografix.com/gpx_manual.asp#sym
<sym>Scenic Area</sym>
Text of GPS symbol name. For interchange with other programs, use the exact
spelling of the symbol on the GPS, if known.

For any GPS that lists the symbol name in English, use the exact English
text.  Some GPS units (MLR, for example) don't give names, so it
becomes a guessing game.  Even Garmin has trouble keeping the names
straight - they've switched names on several GPS models, and their
MapSource software doesn't always use the same names.

EasyGPS includes the names for many brands of GPS.  You're welcome to
use those for reference.  As mentioned above, nobody does a perfect
job with the names, but in places where two programs share the same
name for a symbol, GPX will do the right thing.

You should never use the internal ID for the name.  <sym>1906</sym>
means nothing.  See "Easy to Read".

RL> 5) There is a reference a the elements in <gpx> that links to "Private
RL>    elements" but there is no such tag on the page.   Is additional
RL>    information on this available?

You can put any tags you want at the end of any element in GPX.  You
need to provide your own schema for these tags.  You can look at the
topografix or wissenbach private data for examples:

TopoGrafix "Active Point" element at top level:
<?xml version="1.0"?>
<gpx
  version="1.0"
  creator="ExpertGPS 1.1b1 - http://www.topografix.com"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns="http://www.topografix.com/GPX/1/0"
  xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1"
  xsi:schemaLocation="http://www.topografix.com/GPX/1/0
http://www.topografix.com/GPX/1/0/gpx.xsd
http://www.topografix.com/GPX/Private/TopoGrafix/0/1
http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
<time>2002-02-26T21:50:02Z</time>
<bounds minlat="42.392077" minlon="-71.110768" maxlat="42.406111"
maxlon="-71.075170"/>
...
<topografix:active_point lat="42.402496" lon="-71.088814"/>
</gpx>

Wissenbach "Layer" element in Wpt:
<wpt lat="43.772503" lon="-116.092756"><name>INSPIR</name>
...
<sym>Scenic Area</sym>
<wissenbach:layer>plan_log</wissenbach:layer>
</wpt>

RL> Additionally, this isn't strictly an GPX question, but I suspect this
RL> group has experience on this subject.  Is there a table of "real
RL> world" field sizes for the various makers of GPSRs available?  For
RL> example, I've learned that Magellan supports 8 character waypoints
RL> and 30 character descriptions in Magellan protocol but the NMEA
RL> limits are 6 and 20.  (I've also learned that at least one well known
RL> commercial program crashes when it gets waypoints from my 330 that have
RL> descriptions longer than 20 bytes, so I suspect this is not exactly a
RL> route well travelled.)  Similarly, are there published "best practices"
RL> for adapting "portable" data for the various receivers?  "Truncate this
RL> field from the right, preserving any trailing numeric data", etc.

It's more complicated than just data length, since each GPS model has
it's own list of acceptable characters.  Converting "@MyCar" (Magellan
Meridian) to "MYCAR " (Garmin 38) is a difficult task.  My own method
is:
1. Remove all illegal characters.
2. Truncate to maximum length.

GPX doesn't impose any restrictions on data length or contents, so "My
very 1st waypoint with ASCII JunK!$#@$$$" is a valid waypoint name.
It's up to your program to impose any restrictions before sending to
a GPS.

Hope this helps!
--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

Hello, Dan.

Thanx for the reply.


> Keep us posted on your progress, Robert, and let us know if you run

I'm largely successfuly parsing the inputs.  I haven't started on the
output side yet.   It was interesting that I started laying out my
data structures before learning about GPX and had to make very few
changes to accomodate it.   I'll probably use it as my primary storage
format.

> In general, GPX was designed with these goals in mind:
>  - Easy to parse (only ONE way to represent things)
>  - Easy for humans to read

I'm appreciate both goals.

To go to your first point, could you distinguish why some of the
example fields are encoded as CDATA while others have the tag data
directly in the bodies?

The falls creek example contains:
  <sym>Dot</sym>
  <type><![CDATA[Intersection]]></type>
yet the spec doesn't distinguish those two tags in any way that I see
that allows the different content styles.   Perhaps this is one of
those things that's obvious to XML jocks in which case, please just
point me politly to an authoritative paper.

>  GPX 1.0 is more strict, and only allows two representations: ("Easy
  to Parse")

Do I need to file some kind of formal erratum to get the official
spec clarified, or are message like this enough?   Is there any kind
of revision scheme in place since we've just made an incompatible
change to "1.0" or is slipstreaming it accepted practice here?   (I
don't mind - I'm just trying to understand the guidelines.)

> 1. <time>2002-02-10T21:01:29.250Z</time>   (fractional seconds)
>
> 2. <time>2002-02-10T21:01:29Z</time>       (no fractional seconds)

This, for example, should be spelled out in the spec, becuase I could
(and did!) fill that with an ISO 8601-compliant string that was
against the intent.   Spell it out very plainly.  Are leading zeros
required or optional?  Is 12-hour format with AM/PM ever acceptable,
etc.  (Don't answer the questions; fix the spec. :-)

Similary, clarifying the meaning of the "T" and "Z" in your example
would be helpful.   To this moment, I don't know what they are.



> lat and lon are the correct tag names.  "latitude" and "longitude"
> aren't allowed.  The guiding rule was "choose a tag name that's long

OK, good.

> I've corrected the manual to remove references to "latitude" and
> "longitude".  Please excuse my earlier error.

I've been involved in specifications more complex than this one.  I
understand. :-)


> RL> 4) Are there guidelines for <sym>?  Tables for Magellan and


> becomes a guessing game.  Even Garmin has trouble keeping the names
> straight - they've switched names on several GPS models, and their
> MapSource software doesn't always use the same names.

That's indeed the rub.   I was looking for tables from industry
leaders to help guide and normalize any output I may generate - after
all, avoiding yet MORE divergence in this area would be a Good Thing.

Magellan makes things even ickier by using different icon identifier
to token mappings in different models and even different f/w versions.

> EasyGPS includes the names for many brands of GPS.  You're welcome
to
> use those for reference.  As mentioned above, nobody does a perfect
> job with the names, but in places where two programs share the same
> name for a symbol, GPX will do the right thing.

I can't spot such a list at http://www.easygps.com/manual.asp.
Can you please provide a more precise reference?


> RL> 5) There is a reference a the elements in <gpx> that links to
"Private
> RL>    elements" but there is no such tag on the page.   Is
additional
> RL>    information on this available?
>
> You can put any tags you want at the end of any element in GPX.  You
> need to provide your own schema for these tags.  You can look at the
> topografix or wissenbach private data for examples:

Interesting.   This would be good text to put in the dangling internal
href link to:
http://www.topografix.com/gpx_manual.asp#gpx_private

> RL> route well travelled.)  Similarly, are there published "best
practices"
> RL> for adapting "portable" data for the various receivers?
"Truncate this

> It's more complicated than just data length, since each GPS model
> has it's own list of acceptable characters.

Oh, there's a form of joy I wasn't even expecting.   Thanx for the
tip.

> Converting "@MyCar" (Magellan
> Meridian) to "MYCAR " (Garmin 38) is a difficult task.  My own
method
> is:
> 1. Remove all illegal characters.
> 2. Truncate to maximum length.

So you don't try to get clever with making "@mycarisa78pinto" from
"@mycarisa71mustang" into seperate names, just letting them collide
after you apply the heuristics above?

If it's a problem you haven't seen fit to solve, then I'll feel a lot
better about not worrying about it. :-)


> GPX doesn't impose any restrictions on data length or contents, so
"My
> very 1st waypoint with ASCII JunK!$#@$$$" is a valid waypoint name.
> It's up to your program to impose any restrictions before sending to
> a GPS.

I agree that "cleansing" the data at the edges is most appropriate.  I
was just looking for guidance on the mechanics of that cleansing since
I figured this crowd had dealt with those issues.

> Hope this helps!

Indeed it does.   Thanx very much!
robertlipe@...

--- In gpsxml@y..., Robert Lipe <robertlipe@y...> wrote:
> Hello.
>
> I've started an implementation of a program using GPX 1.0.  I
intend to
> make it freely available. >
> 2) By my reading, the example file is illegal.

...

>
>  http://groups.yahoo.com/group/gpsxml/files/Sample%20XML%
20Files/Kevin%20Read%20Untitled.gpx
>
>
The required version attribute tells the story here.

<gpx version="0.2" ...

The released version is 1.0. That sample probably may not have been
validated against the version 0.2 schema. There is a different
schema for each version of the format. The schemaLocation should
select a schema to match the version.

Protect your application against schema changes by ignoring unknown
elements. Protect other applications from yours by validating test
files from your application against the schema.

Regarding symbols.

Tough question. I've put the ones I use for the Garmin eTrex on my
web page

http://www.cableone.net/cdwissenbach/map.html

>
> RJL

--- In gpsxml@y..., "davewissenbach" <davewissenbach@y...> wrote:
> --- In gpsxml@y..., Robert Lipe <robertlipe@y...> wrote:

> > 2) By my reading, the example file is illegal.
>
> ...
>
> >  http://groups.yahoo.com/group/gpsxml/files/Sample%20XML%
> 20Files/Kevin%20Read%20Untitled.gpx
> >
> >
> The required version attribute tells the story here.
>
> <gpx version="0.2" ...
>
> The released version is 1.0. That sample probably may not have been

Aaaah.   I'd missed that detail.   Perhaps the samples in the 'files'
section of the yahoo group should be updated or at least more clearly
marked as being for a prototype version.

> validated against the version 0.2 schema. There is a different
> schema for each version of the format. The schemaLocation should
> select a schema to match the version.

Forgive my XML virginity here, but I don't know what a 'schema' is.
Just reading it, it appears somewhat like what we dinosaurs would call
a 'grammar'.  In 50 words are less, can anyone offer an explanation of
what a schema is and why we'd care? (References to books or URLs or
whatever are fine; I'm not expecting a free education here. :-)


> Tough question. I've put the ones I use for the Garmin eTrex on my
> web page
>
> http://www.cableone.net/cdwissenbach/map.html

Thanx for the reference.   There is a substantial overlap betweeen
this table and the five (grrrrr.) magellan tables.   There are some
gratituous differences, but since this would  ultimately fall into a
case insensitive table match anyway, I think I can handle this pretty
easily with just some slightly redundant table entries.   Besides, at
the end of the day if an icon gets an inexact translation, it's not a
traumatic event.

This disucssion will help me honor the adage of:

"Be liberal in what you accept and conservative in what you
generate..."

Thanx!
RJL

Thor,

I have recently started using JAXB for another (unrelated) project.
I've been very impressed so far.  There are a few little glitches,
but no show-stoppers.  I'd like to see the GPX schema have a
companion DTD for now...  there seem to still be a bunch of tools
that only support DTDs.

I'll take a closer look at the schema when I get a chance - maybe it
would be an easy conversion to a DTD.

-Helen


--- In gpsxml@y..., "ithork" <ithork@y...> wrote:
> Hi,
>
> I was looking at delveloping a Java program that supports GPX
> format.  I'm still learning about XML in general, but from what
I've
> read, JAXB looked like a good API for this.  Until, though, I
noticed
> that you guys were not using a DTD for this (JAXB v1.0 only
supports
> DTD right now).  Can anyone suggest an alternative Java API, or has
> anyone written a DTD for GPX?
>
> Thanks!
> Thor

--- In gpsxml@y..., "robertlipe" <robertlipe@y...> wrote:
> >
> > The released version is 1.0. That sample probably may not have
been
>
> Aaaah.   I'd missed that detail.   Perhaps the samples in
the 'files'
> section of the yahoo group should be updated or at least more
clearly
> marked as being for a prototype version.
>

I've posted newer samples for GPX1.0 in the Files section.

> Forgive my XML virginity here, but I don't know what a 'schema' is.
> Just reading it, it appears somewhat like what we dinosaurs would
call
> a 'grammar'.  In 50 words are less, can anyone offer an
explanation of
> what a schema is and why we'd care? (References to books or URLs or
> whatever are fine; I'm not expecting a free education here. :-)
>

An XML Schema is an XML document which defines the grammar for
an XML application such as GPS eXchange.

See the standard with supporting documentation at

http://www.w3.org/XML/Schema

I've bought two XML books so far:

XML In a Nutshell, O'REILLY, ISBN: 0-596-00058-8

and

Professional XML Schemas, WROX, ISBN: 1-861005-47-4

>
> Thanx!
> RJL

I am finish my app for doing some GPSR management and I
would like to use the GPX format for saving all files. But I would
like to include some application specific info (like window
positions, preferences, etc.) in the <gpx>.

I couldn't file a spcification for private data in the GPX dev man.
Where should it go? Or, is there no allowance for private data?

Karl

--- In gpsxml@y..., "ThreadHead1" <threadhead@m...> wrote:
> I am finish my app for doing some GPSR management and I
> would like to use the GPX format for saving all files. But I would
> like to include some application specific info (like window
> positions, preferences, etc.) in the <gpx>.
>
> I couldn't file a spcification for private data in the GPX dev
man.
> Where should it go? Or, is there no allowance for private data?
>
> Karl

There is a provision for private data. But shouldn't window
positions and preferences go in the registry? (If this is a windows
program).

Look at the Schema, url below:

http://www.topografix.com/GPX/1/0/gpx.xsd

Private data must be qualified in your namespace and can be
inserted into the document anywhere you see

<xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" />

If you think that the rest of us might also eventually use this
information then we should talk about creating a new version of the
schema which allows this.

To validate that your application's output (and you should)conforms
to the schema, you'll need your own auxiliary schema. You can see
examples of how this is done in my samples at

http://www.cableone.net/cdwissenbach

<gpx
   xmlns="http://www.topografix.com/GPX/1/0"
   version="1.0" creator="Wissenbach Map 1.7"
   xmlns:wissenbach="http://www.cableone.net/cdwissenbach"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://www.topografix.com/GPX/1/0
http://www.topografix.com/GPX/1/0/gpx.xsd
http://www.cableone.net/cdwissenbach
http://www.cableone.net/cdwissenbach/wissenbach.xsd">


The private schema is

http://www.cableone.net/cdwissenbach/

where I insert a <wissenbach:layer> tag to assign trails, routes and
waypoints to a permanent layer or to a working layer. ExpertGPS uses
the same technique to assign a color to tracks and routes. Notice
the additional namespace declaration and the additional pair of URLs
in the schemaLocation attribute to match the additional namespace to
the schema for the private data.

You should be able to validate a sample document without complaint
from the Zerces, or other schema-aware, validating parser.

On Saturday, April 13, 2002, at 03:05  PM, davewissenbach wrote:
> There is a provision for private data. But shouldn't window
> positions and preferences go in the registry? (If this is a windows
> program).

It's a Macintosh program, but since each individual file can have it's
own window location/size, then it is more appropriate to be in the file.
Plus some other things may be more appropriately stored in the GPX file,
like columns widths, selected/hidden items, etc.

> Look at the Schema, url below:
>
> http://www.topografix.com/GPX/1/0/gpx.xsd

Ahh, haven't see this before. Will look it over now.

> Private data must be qualified in your namespace and can be
> inserted into the document anywhere you see
>
> <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" />
> If you think that the rest of us might also eventually use this
> information then we should talk about creating a new version of the
> schema which allows this.

I don't know. But I would say that if you are going to store window
positions, then in the GPX file would be the more appropriate place.
However, I must add that remembering window positions may be more of a
'Mac thing' than PC, so I am not sure it is something everyone would
like to see. Plus, I certainly can't see that it would apply to every
GPS type of application.

> To validate that your application's output (and you should)conforms
> to the schema, you'll need your own auxiliary schema. You can see
> examples of how this is done in my samples at
>
> http://www.cableone.net/cdwissenbach
>
> <gpx
>   xmlns="http://www.topografix.com/GPX/1/0"
>   version="1.0" creator="Wissenbach Map 1.7"
>   xmlns:wissenbach="http://www.cableone.net/cdwissenbach"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://www.topografix.com/GPX/1/0
> http://www.topografix.com/GPX/1/0/gpx.xsd
> http://www.cableone.net/cdwissenbach
> http://www.cableone.net/cdwissenbach/wissenbach.xsd">
>
>
> The private schema is
>
> http://www.cableone.net/cdwissenbach/
>
> where I insert a <wissenbach:layer> tag to assign trails, routes and
> waypoints to a permanent layer or to a working layer. ExpertGPS uses
> the same technique to assign a color to tracks and routes. Notice
> the additional namespace declaration and the additional pair of URLs
> in the schemaLocation attribute to match the additional namespace to
> the schema for the private data.
>
> You should be able to validate a sample document without complaint
> from the Zerces, or other schema-aware, validating parser.

Ok, I see now. Just what I was looking for.

Do you have URLs for for the validating parsers?


Thanks for the help!
Karl

make your own tags. this is standard xml practice. only systems concerned
with those tags will use them.

however, may i suggest that if i am to share an xml file with you, i do not
want to share your screen size settings.

this should be stored in an application specific file. xml is about data -
not applications.

my 2 cents.

c.

At 15:45 13/04/2002 -0700, you wrote:
>On Saturday, April 13, 2002, at 03:05  PM, davewissenbach wrote:
> > There is a provision for private data. But shouldn't window
> > positions and preferences go in the registry? (If this is a windows
> > program).
>
>It's a Macintosh program, but since each individual file can have it's
>own window location/size, then it is more appropriate to be in the file.
>Plus some other things may be more appropriately stored in the GPX file,
>like columns widths, selected/hidden items, etc.
>
> > Look at the Schema, url below:
> >
> >
>
<http://www.topografix.com/GPX/1/0/gpx.xsd>http://www.topografix.com/GPX/1/0/gpx\
.xsd
>
>Ahh, haven't see this before. Will look it over now.
>
> > Private data must be qualified in your namespace and can be
> > inserted into the document anywhere you see
> >
> > <xsd:any namespace="##other" minOccurs="0" maxOccurs="unbounded" />
> > If you think that the rest of us might also eventually use this
> > information then we should talk about creating a new version of the
> > schema which allows this.
>
>I don't know. But I would say that if you are going to store window
>positions, then in the GPX file would be the more appropriate place.
>However, I must add that remembering window positions may be more of a
>'Mac thing' than PC, so I am not sure it is something everyone would
>like to see. Plus, I certainly can't see that it would apply to every
>GPS type of application.
>
> > To validate that your application's output (and you should)conforms
> > to the schema, you'll need your own auxiliary schema. You can see
> > examples of how this is done in my samples at
> >
> > <http://www.cableone.net/cdwissenbach>http://www.cableone.net/cdwissenbach
> >
> > <gpx
> >
> xmlns="<http://www.topografix.com/GPX/1/0>http://www.topografix.com/GPX/1/0"
> >   version="1.0" creator="Wissenbach Map 1.7"
> >
>
xmlns:wissenbach="<http://www.cableone.net/cdwissenbach>http://www.cableone.net/\
cdwissenbach"
> >
>
xmlns:xsi="<http://www.w3.org/2001/XMLSchema-instance>http://www.w3.org/2001/XML\
Schema-instance"
> >
>
xsi:schemaLocation="<http://www.topografix.com/GPX/1/0>http://www.topografix.com\
/GPX/1/0
> > http://www.topografix.com/GPX/1/0/gpx.xsd
> > <http://www.cableone.net/cdwissenbach>http://www.cableone.net/cdwissenbach
> > http://www.cableone.net/cdwissenbach/wissenbach.xsd">
> >
> >
> > The private schema is
> >
> >
> <http://www.cableone.net/cdwissenbach/>http://www.cableone.net/cdwissenbach/
> >
> > where I insert a <wissenbach:layer> tag to assign trails, routes and
> > waypoints to a permanent layer or to a working layer. ExpertGPS uses
> > the same technique to assign a color to tracks and routes. Notice
> > the additional namespace declaration and the additional pair of URLs
> > in the schemaLocation attribute to match the additional namespace to
> > the schema for the private data.
> >
> > You should be able to validate a sample document without complaint
> > from the Zerces, or other schema-aware, validating parser.
>
>Ok, I see now. Just what I was looking for.
>
>Do you have URLs for for the validating parsers?
>
>
>Thanks for the help!
>Karl
>
>
>Yahoo! Groups Sponsor
>ADVERTISEMENT
><http://rd.yahoo.com/M=194081.1994012.3473453.1261774/D=egroupweb/S=1706030390:\
HM/A=1036972/R=0/*http://www.ediets.com/start.cfm?code=3466>dba704f.jpg
>dba7104.jpg
>
>To unsubscribe from this group, send an email to:
>gpsxml-unsubscribe@yahoogroups.com
>
>
>
>Your use of Yahoo! Groups is subject to the
><http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.

Thanks to TopoGrafix for starting this GPS data standard!
I was going to change the data file format in USAPhotoMaps to include
more data, and the GPX standard looks like a great idea.

Doug Cox

Hello,

Monday, April 22, 2002, 9:49:27 PM, Doug wrote:

l> Thanks to TopoGrafix for starting this GPS data standard!
l> I was going to change the data file format in USAPhotoMaps to include
l> more data, and the GPX standard looks like a great idea.

   It's great to have you on board, Doug!  Let us know how your
   progress goes, and tell us if there's anything unclear about the
   standard or the documentation.

--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

Hello,

   I've added some more examples of using GPX for publishing trail
   descriptions.

   This mountain biking site uses Active Server Pages to transform the
   GPX data on the server side, and deliver HTML to the web browser.
   It uses XSL to present several views of the GPX data.
   http://www.topografix.com/team/trails.asp

   One page filters the GPX data to just the waypoints, and then uses
   an HTML form to send the data to Kevin Read's GPX to Ozi Explorer
   converter.  Hopefully others will create some web-based converters
   for other data formats.


   My GPX trails page shows what you can do without using fancy
   scripting on the server side.  I used ExpertGPS to upload GPX data
   directly to my free website.
   http://home.attbi.com/~topografix/


--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

--- In gpsxml@y..., Dan Foster <egroups@t...> wrote:
> Hello,
>
>   I've added some more examples of using GPX for publishing trail
>   descriptions.
>
...
>
>
>   My GPX trails page shows what you can do without using fancy
>   scripting on the server side.  I used ExpertGPS to upload GPX
data
>   directly to my free website.
>   http://home.attbi.com/~topografix/
>

I really like bicycling, so I appreciate the team Topografix bicycle
trails pages. I never go anywhere without my GPS.

The really neat thing about the simple website is the usage of the
map index page to index to the other trails pages! I'm going to copy
this concept to create an index page for my own website.

The kayak trip is really neat. I know avid fishermen who are using
their GPS receivers to mark fishing holes, and to gauge their
progress on the river to watch out for the big rapids, and to make
sure that they don't float too fast, wasting the day, or too slow,
endangering themselves caught out after dark.

I may ask a couple of friends from work for text format output from
their cereal box GPS programs to try to develop a few more
stylesheets, time permitting.

You should cross-post the two sample trails URLs to the map_authors
yahoo group as well!

All the examples I've seen lack richness.  I'm talking
about layout. Dan and Dave's examples read vertically,
from top to bottom using font and indention to set
apart content. What are the possibilities?  Can you
specifiy a background; include a picture, right margin
justified; use buttons, ... ?
I like the idea of using a standard file format, but
I'm not convinced that I should be using GPX showcase
file descriptions.  Currently, my plans are to link to
a GPX file from the description page as I have done at
www.travelbygps.com/guides/borrego/borrego.htm
Is this a good approach or am I still not "getting
it"?
, Doug




--- Dan Foster <egroups@...> wrote:
> Hello,
>
>   I've added some more examples of using GPX for
> publishing trail
>   descriptions.
>
>   This mountain biking site uses Active Server Pages
> to transform the
>   GPX data on the server side, and deliver HTML to
> the web browser.
>   It uses XSL to present several views of the GPX
> data.
>   http://www.topografix.com/team/trails.asp
>
>   One page filters the GPX data to just the
> waypoints, and then uses
>   an HTML form to send the data to Kevin Read's GPX
> to Ozi Explorer
>   converter.  Hopefully others will create some
> web-based converters
>   for other data formats.
>
>
>   My GPX trails page shows what you can do without
> using fancy
>   scripting on the server side.  I used ExpertGPS to
> upload GPX data
>   directly to my free website.
>   http://home.attbi.com/~topografix/
>
>
> --
> Dan Foster
> TopoGrafix - GPS Software, Waypoints, and Maps
> http://www.topografix.com -
> mailto:egroups@...
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> gpsxml-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>



__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

--- In gpsxml@y..., Dan Foster <egroups@t...> wrote:
>   It's great to have you on board, Doug!  Let us know how your
>   progress goes, and tell us if there's anything unclear about the
>   standard or the documentation.
>
> --
> Dan Foster
> TopoGrafix - GPS Software, Waypoints, and Maps
> http://www.topografix.com - mailto:egroups@t...

The GPX standard covers all the waypoint data Magellan GPS
can send to a PC, but newer Garmins can send and receive
more data. I have an old Garmin Map12 (that only sends and
receives the basic data that a Magellan sends and receives),
so I don't really know if newer Garmins lose waypoint data
if you download it to a PC and then upload only the basic
waypoint data back. But if Garmins do lose data when it's
truncated in a GPX waypoint file and then sent back, then I
think the standard should be expanded. I realize this is a
judgment call, since even if some data was lost, it doesn't
look too necessary. Here's the Garmin waypoint data
structure for the newest Garmins:

     typedef
struct                      /*                                 size */
         {
         byte            dtyp;           /* data packet type (0x01 for
D109)1    */
         byte            wpt_class;      /*
class                           1    */
         byte            dspl_color;     /* display & color (see
below)     1    */
         byte            attr;           /* attributes (0x70 for
D109)      1    */
         Symbol_Type     smbl;           /* waypoint
symbol                 2    */
         byte            subclass[18];   /*
subclass                        18   */
         Semicircle_Type posn;           /* 32 bit
semicircle               8    */
         float           alt;            /* altitude in
meters              4    */
         float           dpth;           /* depth in
meters                 4    */
         float           dist;           /* proximity distance in
meters    4    */
         char            state[2];       /*
state                           2    */
         char            cc[2];          /* country
code                    2    */
         longword        ete;            /* outbound link ete in
seconds    4    */
     /*  char            ident[];           variable length
string          1-51 */
     /*  char            comment[];         waypoint user
comment           1-51 */
     /*  char            facility[];        facility
name                   1-31 */
     /*  char            city[];            city
name                       1-25 */
     /*  char            addr[];            address
number                  1-51 */
     /*  char            cross_road[];      intersecting road
label         1-51 */
         } D109_Wpt_Type;

All fields are defined the same as D108 except as noted below.

dtyp - Data packet type, must be 0x01 for D109.

dsp_color - The 'dspl_color' member contains three fields; bits 0-4
specify
the color, bits 5-6 specify the waypoint display attribute and bit 7
is unused
and must be 0. Color values are as specified for D108 except that the
default
value is 0x1f. Display attribute values are as specified for D108.

attr - Attribute. Must be 0x70 for D109.

ete - Estimated time en route in seconds to next waypoint. Default
value is
0xffffffff.

This group-posting software does an automatic wordwrap at
the end of the 58th character on a line, so everyone
writing a message here should write it in Notepad (or
whatever), and do a hard carriage return (press Enter)
before a word crosses that 58th character on a line (like
I'm doing).

Doug Cox

Hello,

Wednesday, April 24, 2002, 8:11:03 AM, Doug wrote:

DA> All the examples I've seen lack richness.  I'm talking
DA> about layout. Dan and Dave's examples read vertically,
DA> from top to bottom using font and indention to set
DA> apart content. What are the possibilities?  Can you
DA> specifiy a background; include a picture, right margin
DA> justified; use buttons, ... ?
DA> I like the idea of using a standard file format, but
DA> I'm not convinced that I should be using GPX showcase
DA> file descriptions.  Currently, my plans are to link to
DA> a GPX file from the description page as I have done at
DA> www.travelbygps.com/guides/borrego/borrego.htm
DA> Is this a good approach or am I still not "getting
DA> it"?

  The possibilities are endless...  Assuming you can figure out the
  XSL statements to use!

  Here's a general strategy for converting your HTML layout to GPX/XSL:

  Your website has a look.  On each page, the text changes, but
  certain things (background picture, fonts, margin sizes) remain the
  same.  Let's call the changing text "content", and the common style a
  "template".  The content for each page will live in a GPX file, and
  the common template will be an XSL file.  The XSL will display your
  HTML page, and insert pieces of GPX data as content.  (Think of the
  Mail Merge command in Microsoft Word...)

  The first thing to do is to strip away all the content and create a
  template with placeholders for the content.  For example, on the page
  you offered, "Anza-Borrego State Park" becomes [file-name], and
  "Most folks envision the desert as a wasteland..." becomes
  [file-description].  Do this for all the changing content on your
  page.

  Now look at the list of placeholders, and try to match them up with
  GPX tags:
  [file-name] = <gpx:name>
  [file-description] = <gpx:desc>
  [file-photo] = !!! doesn't exist in GPX !!!
  ...

  Notice that there's no way to specify a photo for the GPX file.
  If you can't include the picture information in the GPX file, you won't
  be able to use it as content on your page.  (This is different from
  including the same picture on every page - that's part of your
  template!)  You have three choices:
  1. Remove [file-photo] from your template.
  2. Create your own private GPX tag for [file-photo], and edit your
  GPX files by hand.
  3. Suggest to this group that we include a [file-photo] tag in the
  next version of GPX.

  Let's assume you chose option #1 for all placeholders that didn't
  match up with GPX tags.  You now have a list of GPX tags to insert in
  your XSL template.  Don't replace any yet.  XSL can be really
  difficult to debug when you make a mistake, so let's add the tags one
  at a time.

  First, start with an XSL document that only displays your stripped
  down template.  Here's mine:

saved as test.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
   xmlns:gpx="http://www.topografix.com/GPX/1/0">
<xsl:template match="gpx:gpx">

<html>
<head>
<title>[file-title]</title>
</head>
<body>
<h2>[file-title]</h2>
<p>
[file-description]
</p>
</body>
</html>

</xsl:template>
</xsl:stylesheet>

Now let's replace the [file-title] placeholder with the <gpx:name>
tag:

saved as test.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
   xmlns:gpx="http://www.topografix.com/GPX/1/0">
<xsl:template match="gpx:gpx">

<html>
<head>
<title><xsl:apply-templates select="gpx:name"/></title>
</head>
<body>
<h2><xsl:apply-templates select="gpx:name"/></h2>
<p>
[file-description]
</p>
</body>
</html>

</xsl:template>

<xsl:template match="gpx:name">
<xsl:value-of select="."/>
</xsl:template>

</xsl:stylesheet>

As you can see, I replaced all [file-title] placeholders with:
<xsl:apply-templates select="gpx:name"/>

and I added a new template:
<xsl:template match="gpx:name">
<xsl:value-of select="."/>
</xsl:template>

Keep doing that with all your placeholders, and you'll end up with
your finished XSL transform document to use with all your GPX files.

Here's the stripped-down sample GPX data I was using:
saved as borrego3.xml:
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="test.xsl"?>
<gpx
  version="1.0"
  creator="ExpertGPS 1.1.1 - http://www.topografix.com"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns="http://www.topografix.com/GPX/1/0"
  xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1"
  xsi:schemaLocation="http://www.topografix.com/GPX/1/0
http://www.topografix.com/GPX/1/0/gpx.xsd
http://www.topografix.com/GPX/Private/TopoGrafix/0/1
http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
<name><![CDATA[Anza-Borrego State Park]]></name>
<desc><![CDATA[Most folks envision the desert as a wasteland completely void of
hospitable scenery and lacking in varied topography, but the quintessential
picture of the Borrego Desert is a California Palm Oasis with the costal
mountain range as backdrop. These palm oases are the object of a popular
activity, called "oasis bagging." You drive for miles on jeep trails up arroyos
and washes, get out and hike up canyons, then walk around to find the perfect
location to photograph these desert rarities. Download this GPS Map to help you
locate many of the Palm Oases and other points fo interest in the Borrego
Dessert.
The Anza-Borrego State Park is located two hours east of San Diego. RVs pulling
off-road vehicles are a common site along the routes between the desert and the
population centers of southern California. Accommodations for RV camping are as
plentiful and varied as the 4-wheel drive trails on which to ride. Likewise,
other lodging facilities include budget motels, bed-and-breakfasts, and even a
five-star hotel.
]]></desc>
</gpx>

This is just a basic example to get you started with XSL.  I didn't
attempt to describe what any of those XSL statements meant, because at
first, you won't care, and later, you'll use other people's examples
or Google or a book to figure things out.

XSL is tough stuff.  I'm still struggling to learn it, and I suspect
others are as well.  I'd be happy to host some sample XSL files on my
website if others want to contribute some tutorial snippets.  If
you have specific XSL questions, post them here, and someone may have
already figured out the answer.

Q. how do I turn <url> into a hyperlink?
A.
<xsl:template match="gpx:url">
<p>Related website:
  <xsl:text disable-output-escaping="yes"><a href="</xsl:text>
  <xsl:value-of select="."/>
  <xsl:text disable-output-escaping="yes">"
target="_blank"></xsl:text>
  <xsl:value-of select="../gpx:urlname"/>
  <xsl:text disable-output-escaping="yes"></a> </xsl:text>
</p>
</xsl:template>

Good luck!

--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

Hello,

Wednesday, April 24, 2002, 10:08:44 AM, Doug wrote:

l> The GPX standard covers all the waypoint data Magellan GPS
l> can send to a PC, but newer Garmins can send and receive
l> more data. I have an old Garmin Map12 (that only sends and
l> receives the basic data that a Magellan sends and receives),
l> so I don't really know if newer Garmins lose waypoint data
l> if you download it to a PC and then upload only the basic
l> waypoint data back. But if Garmins do lose data when it's
l> truncated in a GPX waypoint file and then sent back, then I
l> think the standard should be expanded. I realize this is a
l> judgment call, since even if some data was lost, it doesn't
l> look too necessary.

Most of those data fields are used for specifying routes that contain
waypoints from aviation databases built into the GPS.  (Jeppesen data,
for example)  I've never seen a file format that included those data
elements.

I supply a custom version of EasyGPS to an aviation flight-planning
service.  We don't include any of the Garmin aviation fields in our
file exchange.

There are certainly some elements of the Garmin private data that
could be included in GPX.  <depth>120</depth> makes sense for
exchanging data between fish-finders.  <subclass>???</subclass>
doesn't make much sense outside of the Garmin world, though.
That's why you have the ability to define private data tags in GPX.


To answer your question about whether Garmins lose data, they don't.
What happens is that if you send the GPX-stripped version of an aviation
routepoint back to the GPS, it will create a user waypoint rather than
using the matching airport in the Jeppesen database.  So you end up
with one extra waypoint in memory.  Not a big issue for most people,
and pilots expect this when using 3rd party software.

--
Dan Foster
TopoGrafix - GPS Software, Waypoints, and Maps
http://www.topografix.com - mailto:egroups@...

--- In gpsxml@y..., Dan Foster <egroups@t...> wrote:
> Hello,
>
> Most of those data fields are used for specifying routes that
contain
> waypoints from aviation databases built into the GPS.  (Jeppesen
data,
> for example)  I've never seen a file format that included those data
> elements.
>
> I supply a custom version of EasyGPS to an aviation flight-planning
> service.  We don't include any of the Garmin aviation fields in our
> file exchange.
>
> There are certainly some elements of the Garmin private data that
> could be included in GPX.  <depth>120</depth> makes sense for
> exchanging data between fish-finders.  <subclass>???</subclass>
> doesn't make much sense outside of the Garmin world, though.
> That's why you have the ability to define private data tags in GPX.
>
>
> To answer your question about whether Garmins lose data, they don't.
> What happens is that if you send the GPX-stripped version of an
aviation
> routepoint back to the GPS, it will create a user waypoint rather
than
> using the matching airport in the Jeppesen database.  So you end up
> with one extra waypoint in memory.  Not a big issue for most people,
> and pilots expect this when using 3rd party software.
>
> --
> Dan Foster
> TopoGrafix - GPS Software, Waypoints, and Maps
> http://www.topografix.com - mailto:egroups@t...

Thanks a lot for the quick reply! That all sounds good to me!

Doug Cox

Wow.  Thanks for the detailed reply, Dan. This will
take some indigesting.
, Doug



   --- Dan Foster <egroups@...> wrote:
> Hello,
>
> Wednesday, April 24, 2002, 8:11:03 AM, Doug wrote:
>
> DA> All the examples I've seen lack richness.  I'm
> talking
> DA> about layout. Dan and Dave's examples read
> vertically,
> DA> from top to bottom using font and indention to
> set
> DA> apart content. What are the possibilities?  Can
> you
> DA> specifiy a background; include a picture, right
> margin
> DA> justified; use buttons, ... ?
> DA> I like the idea of using a standard file format,
> but
> DA> I'm not convinced that I should be using GPX
> showcase
> DA> file descriptions.  Currently, my plans are to
> link to
> DA> a GPX file from the description page as I have
> done at
> DA> www.travelbygps.com/guides/borrego/borrego.htm
> DA> Is this a good approach or am I still not
> "getting
> DA> it"?
>
>  The possibilities are endless...  Assuming you can
> figure out the
>  XSL statements to use!
>
>  Here's a general strategy for converting your HTML
> layout to GPX/XSL:
>
>  Your website has a look.  On each page, the text
> changes, but
>  certain things (background picture, fonts, margin
> sizes) remain the
>  same.  Let's call the changing text "content", and
> the common style a
>  "template".  The content for each page will live in
> a GPX file, and
>  the common template will be an XSL file.  The XSL
> will display your
>  HTML page, and insert pieces of GPX data as
> content.  (Think of the
>  Mail Merge command in Microsoft Word...)
>
>  The first thing to do is to strip away all the
> content and create a
>  template with placeholders for the content.  For
> example, on the page
>  you offered, "Anza-Borrego State Park" becomes
> [file-name], and
>  "Most folks envision the desert as a wasteland..."
> becomes
>  [file-description].  Do this for all the changing
> content on your
>  page.
>
>  Now look at the list of placeholders, and try to
> match them up with
>  GPX tags:
>  [file-name] = <gpx:name>
>  [file-description] = <gpx:desc>
>  [file-photo] = !!! doesn't exist in GPX !!!
>  ...
>
>  Notice that there's no way to specify a photo for
> the GPX file.
>  If you can't include the picture information in the
> GPX file, you won't
>  be able to use it as content on your page.  (This
> is different from
>  including the same picture on every page - that's
> part of your
>  template!)  You have three choices:
>  1. Remove [file-photo] from your template.
>  2. Create your own private GPX tag for
> [file-photo], and edit your
>  GPX files by hand.
>  3. Suggest to this group that we include a
> [file-photo] tag in the
>  next version of GPX.
>
>  Let's assume you chose option #1 for all
> placeholders that didn't
>  match up with GPX tags.  You now have a list of GPX
> tags to insert in
>  your XSL template.  Don't replace any yet.  XSL can
> be really
>  difficult to debug when you make a mistake, so
> let's add the tags one
>  at a time.
>
>  First, start with an XSL document that only
> displays your stripped
>  down template.  Here's mine:
>
> saved as test.xsl:
> <?xml version="1.0"?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>   xmlns:gpx="http://www.topografix.com/GPX/1/0">
> <xsl:template match="gpx:gpx">
>
> <html>
> <head>
> <title>[file-title]</title>
> </head>
> <body>
> <h2>[file-title]</h2>
> <p>
> [file-description]
> </p>
> </body>
> </html>
>
> </xsl:template>
> </xsl:stylesheet>
>
> Now let's replace the [file-title] placeholder with
> the <gpx:name>
> tag:
>
> saved as test.xsl:
> <?xml version="1.0"?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>   xmlns:gpx="http://www.topografix.com/GPX/1/0">
> <xsl:template match="gpx:gpx">
>
> <html>
> <head>
> <title><xsl:apply-templates
> select="gpx:name"/></title>
> </head>
> <body>
> <h2><xsl:apply-templates select="gpx:name"/></h2>
> <p>
> [file-description]
> </p>
> </body>
> </html>
>
> </xsl:template>
>
> <xsl:template match="gpx:name">
> <xsl:value-of select="."/>
> </xsl:template>
>
> </xsl:stylesheet>
>
> As you can see, I replaced all [file-title]
> placeholders with:
> <xsl:apply-templates select="gpx:name"/>
>
> and I added a new template:
> <xsl:template match="gpx:name">
> <xsl:value-of select="."/>
> </xsl:template>
>
> Keep doing that with all your placeholders, and
> you'll end up with
> your finished XSL transform document to use with all
> your GPX files.
>
> Here's the stripped-down sample GPX data I was
> using:
> saved as borrego3.xml:
> <?xml version="1.0" encoding="ISO-8859-1"
> standalone="yes"?>
> <?xml-stylesheet type="text/xsl" href="test.xsl"?>
> <gpx
>  version="1.0"
>  creator="ExpertGPS 1.1.1 -
> http://www.topografix.com"
>
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xmlns="http://www.topografix.com/GPX/1/0"
>
>
xmlns:topografix="http://www.topografix.com/GPX/Private/TopoGrafix/0/1"
>
>
xsi:schemaLocation="http://www.topografix.com/GPX/1/0
> http://www.topografix.com/GPX/1/0/gpx.xsd
> http://www.topografix.com/GPX/Private/TopoGrafix/0/1
>
http://www.topografix.com/GPX/Private/TopoGrafix/0/1/topografix.xsd">
> <name><![CDATA[Anza-Borrego State Park]]></name>
> <desc><![CDATA[Most folks envision the desert as a
> wasteland completely void of hospitable scenery and
> lacking in varied topography, but the quintessential
> picture of the Borrego Desert is a California Palm
> Oasis with the costal mountain range as backdrop.
> These palm oases are the object of a popular
> activity, called "oasis bagging." You drive for
> miles on jeep trails up arroyos and washes, get out
> and hike up canyons, then walk around to find the
> perfect location to photograph these desert
> rarities. Download this GPS Map to help you locate
> many of the Palm Oases and other points fo interest
> in
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

--- In gpsxml@y..., "davewissenbach" <davewissenbach@y...> wrote:
> --- In gpsxml@y..., "gps_maps" <gps_maps@y...> wrote:
> > It would be a cruel world without cordless screwdrivers, ATM
> > machines, and wysiwyg HTML editors.  What do you use to edit your
> > XML?  Please dont' tell me "notebook"!
> > , Doug
>
> I rarely, if ever, edit .gpx files directly. But when I do, I use
> wordpad to edit raw text. (I also ride a bicycle to work, every
day,
> rain or shine, cold or hot.)
>
> You might visit
>
> http://www.xslt.com
>
> for a listing of stylesheet editors to transform xml documents. (I
> even saw a stylesheet debugger there, visual XSTL). I tend to be
> adverse to expensive new tools, although I do own a cordless
> screwdriver!

Since I *love* expensve new tools, I do have XMLSpy (www.xmlspy.com),
and use it a good deal.  However, I do walk to work, which gives you
the idea that I use notepad or vi at least half the time for XML
editing.

Here are my thoughts on XMLSpy:

1.) It has very nice tools that can help you understand new schemas,
such as a schema documentation generator and a handy feature
called "Generate Sample XML".

2.) You get all the convenience of clicking on a button to check for
well-formedness (is it legal XML?) and for validation (does it adhere
to the schema?)

3.) It has many, many other features that you may never need to use.
For example, it has a whole setup whereby you can define a "form" for
editing a particular type of XML (say GPSXML...) and then an end-user
can edit that XML via your form and the XMLSpy "Document Editor."

4.) The XMLSpy Suite (includes everything, including the form and
document editing described above) runs $400.  The XMLSpy IDE only
runs $200 - this is the license that I bought.  That being said,
unless you are designing schemas or working with new schemas often, I
think that XMLSpy is overkill for just editing xml files.

Whew... posting this had made me think that I should consider finding
a tool "lighter" than XMLSpy, but "heftier" than notepad.  OK, I have
a team member working on editing some XML files today, I will have
her try Xeena (http://www.alphaworks.ibm.com/tech/xeena) and report
back!

Cheers,
Helen