GPX Format Status

9.4k · August 8, 2002

For those who are anxiously awaiting the new GPX format, I wanted to give you a head's up and an example file of the GPX format with the extended Groundspeak:cache namespace.

You can find the example here. I don't plan on changing the elements that exist now, but may expand the elements to add travel bugs.

To use the file, save it to your desktop with the GPX extension. You can open it up into EasyGPS and ExpertGPS. If you have older versions and it errors, you will need to download the latest version from the Geocaching web site (for EasyGPS). It is located in the "links" area of the site.

The file size gets large quickly, so I will more than likely trim down the number of logs returned. Setting your Pocket Query to Zipfile significantly reduces the size, however.

Jeremy

Jeremy Irish

Groundspeak - The Language of Location

1.7k · August 8, 2002

I like it. That has everything I need, in a format I can use. Thanks for all your great work on this.

Can we assume that the xmlns:Groundspeak element will be changing to refer to the actual schema when it's finalized?

5.3k · August 8, 2002

quote:
Originally posted by Jeremy Irish:
For those who are anxiously awaiting the new GPX format, I wanted to give you a head's up and an example file of the GPX format with the extended Groundspeak:cache namespace.

I haven't picked through every byte, but glancing through it, I'm rather aroused. I threw gpsbabel at it and it just worked. Flipping through the file, it looks like all the data I'd want is there (logs, hints, etc.) in a way that'll be way easier for me to parse and presumably less work for your server to create.

I'm diggin' it. Thanx!

August 8, 2002

Originally posted by robertlipe:

it looks like all the data I'd want is there (logs, hints, etc.)

Where exactly is the logs/hint data etc. I opened it in easygps and only got symbol/desc/waypoint/comment/type/lat/long/elev/dist to active point/bearing.

Am I missing something here. I even downloaded the newer version of easy gps just to be sure (ver 1.1.9)

Goldkey

August 8, 2002

I like it.

Can you add the difficulty and cache size fields (or are they there and I missed them?)

Marty

9.4k · August 8, 2002

quote:
Originally posted by Marty Fouts:
I like it.

Can you add the difficulty and cache size fields (or are they there and I missed them?)

Marty

Good eye. I just added terrain/difficulty (which I apparently missed on the first go). I'll add the container size as well.

Goldkey - You're right. Currently all you can see differenly from before is that the waypoint symbol is now a Geocache (or "Geocache Found"). The GPX format has been extended with extra data ExpertGPS and EasyGPS do not support, but there has been a growing interest in creating client applications that do use it.

Jeremy Irish

Groundspeak - The Language of Location

August 9, 2002

I can't stand it....it's Sooooooo awsome I think I'm going to explode!!!!!

Rob

Mobile Cache Command

August 9, 2002

I can't stand it....it's Sooooooo awsome I think I'm going to explode!!!!!

Rob

Mobile Cache Command

August 9, 2002

I got so excited seeing this, I got up on my desk at work, dancing and singing, and now they think I am a loon and threw me in jail. Any help please??

Bear

I thought I was a little off, then I looked at my GPS and discovered I accurate to 12 ft.

Geocachers don't NEED to ask for directions!

1k · August 9, 2002

quote:
Originally posted by Bear & Ting:
I got so excited seeing this, I got up on my desk at work, dancing and singing, and now they think I am a loon and threw me in jail. Any help please??

I've heard there's a lot of cache people have been leaving around in strange places, enough to mkake your bail perhaps...

I wasn't paying much attention to the GPX, but after looking, like it too!

Warning: Objects in GPS may be closer than they appear!

1k · August 9, 2002

quote:
Originally posted by Bear & Ting:
I got so excited seeing this, I got up on my desk at work, dancing and singing, and now they think I am a loon and threw me in jail. Any help please??

I've heard there's a lot of cache people have been leaving around in strange places, enough to mkake your bail perhaps...

I wasn't paying much attention to the GPX, but after looking, like it too!

Warning: Objects in GPS may be closer than they appear!

1.3k · August 9, 2002

I feel like one of those people in a large group who jump up and down, cheer, clap, pump my fist, etc. and then turn to the guy next to me and ask "what is it we are so happy about?".

For the benefit of we cachers who know zip about writing code and applications, can someone explain what all this will mean to us. Does it mean that our pocket query downloads will be in a different format that some current apps will not open?

I know that EasyGPS is fine with the new format but Geobuddy will not. I use it to save in Streets & Trips format.

Thanks, Olar

August 9, 2002

Okay - I know that I griped before (in another thread), but I take it all back! This is great.

I have a small two small suggestions:

1) The tag really has two peices of information in it: the name and the owner. They are connected by the English word "by". To get just the name of the cache, I'd have to reg-exp this apart... Since the owner info is already present, can just have the name of the cache. Then it is up to the presentation software to decided if it wants to add "by" and the owner when showing it. (And it can do the right thing in other languages!)

2) Seems the tag seems to be a duplicate of the tag. Seems redundant. Surely it shouldn't be the title from the document at the .... That could easily change out from under the file.

- Mark

August 9, 2002

quote:
The GPX format has been extended with extra data ExpertGPS and EasyGPS do not support, but there has been a growing interest in creating client applications that do use it.

Jeremy Irish

Groundspeak - The Language of Location

By the excitement generated here, I am assuming that there must be some applications available that can use this data. If so, how do I get a copy?

Thanks

August 9, 2002

quote:
Originally posted by GoldKey:

quote:
The GPX format has been extended with extra data ExpertGPS and EasyGPS do not support, but there has been a growing interest in creating client applications that do use it.

Jeremy Irish

Groundspeak - The Language of Location

By the excitement generated here, I am assuming that there must be some applications available that can use this data. If so, how do I get a copy?

Thanks

Robert Lipe is developing a program called GPS Babel that translates between various formats (an open source geobuddy that's more complete.) It currently is in beta and only available for Unix systems, but you can track its development at http://gpsbabel.sourceforge.net/

I'm working on a program for windows that allows you to treat one of these files as a database so you can pick and chose entries for download and display on a palm, but that's a long way off because it's a spare time project.

1.7k · August 9, 2002

quote:
Originally posted by John, Mark & Kyle:
1) The tag really has two peices of information in it: the name and the owner. They are connected by the English word "by". To get just the name of the cache, I'd have to reg-exp this apart... Since the owner info is already present, can just have the name of the cache.

If a change is to be made, I think it should be made to the Groundspeak:name tag, and leave the GPX desc tag alone. The reason for this suggestion is that the owner info is not actually available to GPX-only applications; it's only available to applications that understand the custom Groundspeak extensions.

August 9, 2002

I'd like just a plain old tab delimited file, even with my limited skills, I could work with that.

9.4k · August 9, 2002

I made some modifications...

The GPX format has now split the name of the cache from the placer. The placer can sometimes be different from the account username, so although they do match on some, others will be different.

I also added addional information in GPX for the description field. I added the type of cache and the difficulty/terrain settings. I added a space to fix a formatting snafu as well.

In addition, I restricted the number of logs to 5 for each cache. It ended up reducing the size dramatically, so I expect to leave it that way.

Jeremy Irish

Groundspeak - The Language of Location

9.4k · August 9, 2002

quote:
Originally posted by Warm Fuzzies - Fuzzy:

Can we assume that the xmlns:Groundspeak element will be changing to refer to the actual schema when it's finalized?

Yes. I'll have an xsd available for it, I suspect. Which means I'll probably have to add redundant information like lat/lon so if the namespace is used alone, the Groundspeak format can be decoded and used.

I'm still in the middle of XML boot camp, so I'm trying to sort all this stuff out.

Jeremy Irish

Groundspeak - The Language of Location

5.3k · August 9, 2002

quote:
Originally posted by Marty Fouts:

Robert Lipe is developing a program called GPS Babel that translates between various formats (an open source geobuddy that's more complete.) It currently is in beta and only available for Unix systems, but you can track its development at http://gpsbabel.sourceforge.net/

Please don't perpetuate that. It works fine on any OS with a POSIX environment, including Darwin/OS-X and Windows with Cygwin load. Since I'm a UNIX guy, I tested the UNIXen within reach.

That said, gpsbabel really won't get anything out of these GPX files that it couldn't get from the (much smaller) geocaching.loc files. It's other projects that honk on the whole description that will come into play with the GPX data.

August 9, 2002

quote:
Originally posted by Jeremy Irish:
Which means I'll probably have to add redundant information like lat/lon so if the namespace is used alone, the Groundspeak format can be decoded and used.

Eeek, don't do that! Redundant info in a transfer format is the bane of all programmers (which one do you believe if they are different?)! It is fine if your XML namespace is only logical when used in conjunction with a particular document type or types. Consider that your namespace is an augmentation of another set of XML nodes - no one would ever use it alone.

If you anticipate the use of the Groundspeak namespace without GPX, then define a "minimal" doc schema (seperate from the namespace) that is what the Groundspeak namespace needs. Then anyone wanting to use the Groundspeak namespace elsewhere has a documented list of what they need to provide in thier "hosting" XML document type.

Okay, sorry, now I've polluted this forum with massive XML geek talk. Jeremy, I'd be happy to talk about this this off-line, or happier to talk about it to a seperate publc forum, if you'd like.

- Mark (SW architecture kinda guy) from TeamOzone

August 9, 2002

quote:
Originally posted by Jeremy Irish:
Which means I'll probably have to add redundant information like lat/lon so if the namespace is used alone, the Groundspeak format can be decoded and used.

Eeek, don't do that! Redundant info in a transfer format is the bane of all programmers (which one do you believe if they are different?)! It is fine if your XML namespace is only logical when used in conjunction with a particular document type or types. Consider that your namespace is an augmentation of another set of XML nodes - no one would ever use it alone.

If you anticipate the use of the Groundspeak namespace without GPX, then define a "minimal" doc schema (seperate from the namespace) that is what the Groundspeak namespace needs. Then anyone wanting to use the Groundspeak namespace elsewhere has a documented list of what they need to provide in thier "hosting" XML document type.

Okay, sorry, now I've polluted this forum with massive XML geek talk. Jeremy, I'd be happy to talk about this this off-line, or happier to talk about it to a seperate publc forum, if you'd like.

- Mark (SW architecture kinda guy) from TeamOzone

August 9, 2002

quote:
Originally posted by John, Mark & Kyle:

quote:
Originally posted by Jeremy Irish:
Which means I'll probably have to add redundant information like lat/lon so if the namespace is used alone, the Groundspeak format can be decoded and used.

Eeek, don't do that! Redundant info in a transfer format is the bane of all programmers (which one do you believe if they are different?)! It is fine if your XML namespace is only logical when used in conjunction with a particular document type or types. Consider that your namespace is an augmentation of another set of XML nodes - no one would ever use it alone.

If you anticipate the use of the Groundspeak namespace without GPX, then define a "minimal" doc schema (seperate from the namespace) that is what the Groundspeak namespace needs. Then anyone wanting to use the Groundspeak namespace elsewhere has a documented list of what they need to provide in thier "hosting" XML document type.

Okay, sorry, now I've polluted this forum with massive XML geek talk. Jeremy, I'd be happy to talk about this this off-line, or happier to talk about it to a seperate publc forum, if you'd like.

- Mark (SW architecture kinda guy) from TeamOzone

Seperate forum...yes, off-line?? NONONONONO .... I learn alot by reading, esp examples.

Bear

I thought I was a little off, then I looked at my GPS and discovered I accurate to 12 ft.

Geocachers don't NEED to ask for directions!

August 9, 2002

quote:
Originally posted by John, Mark & Kyle:

quote:
Originally posted by Jeremy Irish:
Which means I'll probably have to add redundant information like lat/lon so if the namespace is used alone, the Groundspeak format can be decoded and used.

Eeek, don't do that! Redundant info in a transfer format is the bane of all programmers (which one do you believe if they are different?)! It is fine if your XML namespace is only logical when used in conjunction with a particular document type or types. Consider that your namespace is an augmentation of another set of XML nodes - no one would ever use it alone.

If you anticipate the use of the Groundspeak namespace without GPX, then define a "minimal" doc schema (seperate from the namespace) that is what the Groundspeak namespace needs. Then anyone wanting to use the Groundspeak namespace elsewhere has a documented list of what they need to provide in thier "hosting" XML document type.

Okay, sorry, now I've polluted this forum with massive XML geek talk. Jeremy, I'd be happy to talk about this this off-line, or happier to talk about it to a seperate publc forum, if you'd like.

- Mark (SW architecture kinda guy) from TeamOzone

Seperate forum...yes, off-line?? NONONONONO .... I learn alot by reading, esp examples.

Bear

I thought I was a little off, then I looked at my GPS and discovered I accurate to 12 ft.

Geocachers don't NEED to ask for directions!

August 9, 2002

quote:
Originally posted by robertlipe:

quote:
Originally posted by Marty Fouts:

Robert Lipe is developing a program called GPS Babel that translates between various formats (an open source geobuddy that's more complete.) It currently is in beta and only available for Unix systems, but you can track its development at http://gpsbabel.sourceforge.net/

Please don't perpetuate that. It works fine on any OS with a POSIX environment, including Darwin/OS-X and Windows with Cygwin load. Since I'm a UNIX guy, I tested the UNIXen within reach.

That said, gpsbabel really won't get anything out of these GPX files that it couldn't get from the (much smaller) geocaching.loc files. It's other projects that honk on the whole description that will come into play with the GPX data.

My apologies.

August 10, 2002

quote:
Eeek, don't do that! Redundant info in a transfer format is the bane of all programmers (which one do you believe if they are different?)! It is fine if your XML namespace is only logical when used in conjunction with a particular document type or types. Consider that your namespace is an augmentation of another set of XML nodes - no one would ever use it alone.

I concure! I would hope that the original GPX data schema would be used to its maximum potential BEFORE augmenting with extensions. The reason for this is to ensure that as much useful data can be used by ANY gpx application!

Rob

Mobile Cache Command

1.1k · August 10, 2002

quote:
Originally posted by mrcpu:
I concur! I would hope that the original GPX data schema would be used to its maximum potential BEFORE augmenting with extensions.

Porn and video games have driven hardware and bandwidth improvements over the last 10 years. You need a "killer app" to drive the GPX standard. Why not Geocaching?

Dan has done a great job with augmenting LOC to the GPX standard. I believe anything else should be in a namespace. If you want to drive change in GPX, sign up for his discussion forum. It's on his GPX page.

Jeremy Irish

Groundspeak - The Language of Location

August 10, 2002

quote:
Originally posted by Jeremy (Admin):

quote:
Originally posted by mrcpu:
I concur! I would hope that the original GPX data schema would be used to its maximum potential BEFORE augmenting with extensions.

Porn and video games have driven hardware and bandwidth improvements over the last 10 years. You need a "killer app" to drive the GPX standard. Why not Geocaching?

Dan has done a great job with augmenting LOC to the GPX standard. I believe anything else should be in a namespace. If you want to drive change in GPX, sign up for his discussion forum. It's on his http://www.topografix.com/gpx.

Jeremy Irish

Groundspeak - The Language of Location

I think there are two issues here that should be discussed on the GPX forum, and I've posted a note there to start that discussion. Anyone who's not already involved in the forum but is interested can go to http://groups.yahoo.com/group/gpsxml/?yguid=45141692 and join the discussion if they have a Yahoo groups account.

The two questions that I think are more general are:

1) Should extensions be in separate namespaces? I think this is a nobrainer and the answer is yes, but I think it's worth making a formal part of the spec, so I opened the topic.

more interestingly, though, I asked

2) should fields from the base GPX be duplicated in an extension?

As a data purists, I think the answer should be no, but I don't know enough about XML to know whether Jeremy's thoughts about needing to duplicate are correct, either.

Oh, as to the killer ap. I hope I'm writing it.

August 10, 2002

quote:
Originally posted by Jeremy (Admin):

quote:
Originally posted by mrcpu:
I concur! I would hope that the original GPX data schema would be used to its maximum potential BEFORE augmenting with extensions.

Porn and video games have driven hardware and bandwidth improvements over the last 10 years. You need a "killer app" to drive the GPX standard. Why not Geocaching?

Dan has done a great job with augmenting LOC to the GPX standard. I believe anything else should be in a namespace. If you want to drive change in GPX, sign up for his discussion forum. It's on his http://www.topografix.com/gpx.

Jeremy Irish

Groundspeak - The Language of Location

I think there are two issues here that should be discussed on the GPX forum, and I've posted a note there to start that discussion. Anyone who's not already involved in the forum but is interested can go to http://groups.yahoo.com/group/gpsxml/?yguid=45141692 and join the discussion if they have a Yahoo groups account.

The two questions that I think are more general are:

1) Should extensions be in separate namespaces? I think this is a nobrainer and the answer is yes, but I think it's worth making a formal part of the spec, so I opened the topic.

more interestingly, though, I asked

2) should fields from the base GPX be duplicated in an extension?

As a data purists, I think the answer should be no, but I don't know enough about XML to know whether Jeremy's thoughts about needing to duplicate are correct, either.

Oh, as to the killer ap. I hope I'm writing it.

August 11, 2002

quote:
Originally posted by Jeremy (Admin):
Porn and video games have driven hardware and bandwidth improvements over the last 10 years. You need a "killer app" to drive the GPX standard. Why not Geocaching?

Dan has done a great job with augmenting LOC to the GPX standard. I believe anything else should be in a namespace. If you want to drive change in GPX, sign up for his discussion forum. It's on his http://www.topografix.com/gpx.

OT:

With regards to your porn comment, check this out:

http://artists.mp3s.com/artist_song/954/954828.html

You might also enjoy some of their other work too:

http://artists.mp3s.com/artists/37/three_dead_trolls_in_a_bag.html

Anyways, back on topic... the main thing I noticed was that the description field wasn't being used for the description. For example, when I opened the sample in easygps the description was very short. I haven't looked at it since, so I'm wondering if that was a charlen issue or something else.

Anyways, it's still totaly awsome!

Cheers,

Rob

Mobile Cache Command

August 12, 2002

I'd like to offer a service that converts these GPX files into, say, a Plucker database. Would Groundspeak Inc have any kind of problem with this? I'd hate to sink a bunch of work into a project that would have to be shut down.

August 12, 2002

quote:
Originally posted by blscearce:
I'd like to offer a service that converts these GPX files into, say, a Plucker database.

As a Plucker user, I'd certainly make use of such a service.

Spiders taste like chicken.

August 14, 2002

Finaly...Data thats not locked up in a locked down format:)-

Thanks Jeremy, this is exactly what a lot of us have been waiting and wailing for.

You put out the data, the apps will come....

Finaly..

-tom

----------------------------

TeamWSMF@wsmf.org

August 14, 2002

Finaly...Data thats not locked up in a locked down format-

Thanks Jeremy, this is exactly what a lot of us have been waiting and wailing for.

You put out the data, the apps will come....

Finaly..

-tom

----------------------------

TeamWSMF@wsmf.org

August 15, 2002

quote:
Originally posted by blscearce:
I'd like to offer a service that converts these GPX files into, say, a Plucker database. Would Groundspeak Inc have any kind of problem with this? I'd hate to sink a bunch of work into a project that would have to be shut down.

When you say a "Plucker database", what does that mean? GPX (or any XML format/layout) is pretty much already a "database". I haven't bothered with Plucker, but I have seen it mentioned here and there.

EDIT: Nevermind... I hit the Plucker homepage and checked it out myself. The main problem I have with that is that no matter what final "format" you put data into, it's "wrong" for me. I want my final output to look just so and include just so much data, as each person does. And the only way we'll each be able to have that is for the "raw" data to be available for use by each person's stylesheet. Then you can boil it down to an ebook, or retain Jeremy's original look and feel, or (my choice) print 4 text-only cache pages per page.

> Martin (Magellan 330)

Don't have time to program and record your shows while geocaching? Get a TiVo!

[This message was edited by martinp13 on August 15, 2002 at 11:31 AM.]

August 15, 2002

quote:
Originally posted by martinp13:
The main problem I have with that is that no matter what final "format" you put data into, it's "wrong" for me. I want my final output to look just so and include just so much data, as each person does. And the only way we'll each be able to have that is for the "raw" data to be available for use by each person's stylesheet. Then you can boil it down to an ebook, or retain Jeremy's original look and feel, or (my choice) print 4 text-only cache pages per page.

> Martin (Magellan 330)

I think you'll like my GPX display program, if I ever get it finished. [;-)]

5.3k · August 15, 2002

quote:
Originally posted by martinp13:
GPX (or any XML format/layout) is pretty much already a "database". [ munch ] The main problem I have with that is that no matter what final "format" you put data into, it's "wrong" for me. I want my final output to look just so and include just so much data, as each person does. And the only way we'll each be able to have that is for the "raw" data to be available for use by each person's stylesheet. Then you can boil it down to an ebook, or retain Jeremy's original look and feel, or (my choice) print 4 text-only cache pages per page.

GPX is that format. It provides the data with logical (not textual) markup so you can easily see which of the words in that stream are the hider's name, which are the coords, which are the hint, and so on. GPX is the delivery vehicle for that "raw" data that allows you (well, at least any tool or programer that can cope with XML) to boil it to any of the formats you cite or more.

8.9k · August 16, 2002

The standard question I've been waiting for...

Is there a way to get XML into a standarad database program like Access? I'm running Access 2000 at work and Access XP at home, but I couldn't find any references to importing the information into tables, etc. Web searches on Google didn't help much, and neither did Microsoft.com.

Help. I'm trying to see the benefits here.

Markwell

Chicago Geocaching

1.7k · August 16, 2002

quote:
Originally posted by Markwell:
Is there a way to get XML into a standarad database program like Access?

You can import XML data into Access xp. I've just tried it do it with a .loc file, and it was marginally successful. It might have been more successful if I'd had a copy of the XML Schema for the .loc format.

Worst case, you can use some other program like GPSBabel or GeoBuddy to convert the data to CSV data that you can then import into just about anything.

August 16, 2002

quote:
Originally posted by martinp13:

The main problem I have with that is that no matter what final "format" you put data into, it's "wrong" for me. I want my final output to look just so and include just so much data, as each person does.

Of course. I'm planning to build some flexibility into the formatting and presentation (I've had some kudos for the stuff I'm creating now at Palmable Geocaching, so something like that will continue to be offered). But I don't think I'll come up with something that satisfies everybody. If there's too much flexibility, the specification for "how I want it to look" ends up being essentially the XML parser, and you're forcing the user to be a programmer.

August 17, 2002

Some of you are missing the point behind GPX. There would be no need to use plucker or even the pathetique site. You would have all the data already IN the gpx file... logs, description, terrain rating etc etc.

GPX format means that you can either create a stylesheet to display the data in your web browser as you see fit and then print it to take with you, or you create a palm application that does this and upload the data to it, or you can import the data into your favorite mapping software.

Using the GPX format to feed plucker or a program that goes to pathetique would be just sort of stupid.

Rob

Mobile Cache Command

August 17, 2002

quote:
Originally posted by mrcpu:
Some of you are missing the point behind GPX. There would be no need to use plucker or even the pathetique site. You would have all the data already IN the gpx file... logs, description, terrain rating etc etc.

GPX format means that you can either create a stylesheet to display the data in your web browser as you see fit and then print it to take with you, or you create a palm application that does this and upload the data to it, or you can import the data into your favorite mapping software.

Using the GPX format to feed plucker or a program that goes to pathetique would be just sort of stupid.

Rob

Mobile Cache Command

Of course, my favorite mapping program doesn't understand XML, and I want to be able to extract subsets of Pocket Query response files to put on my minimum-memory PDA.

And, of course, it's nice to have the data on the PDA in a format that's a little petter compressed than an XML file.

August 18, 2002

quote:
Originally posted by mrcpu:
or you create a palm application that does this and upload the data to it

That's exactly what I'm working on. If there's already an app out there that formats GPX XML data into a nice-to-read PDA format, let me know and save me some coding. I'm happy to admit that I don't keep up with the full universe of PDA software.

I know all the info is in the XML, that's what makes it possible for me to write the software. But not everyone is a software engineer.

August 19, 2002

Originally posted by mrcpu:

GPX format means that you can either create a stylesheet to display the data in your web browser as you see fit and then print it to take with you, or you create a palm application that does this and upload the data to it, or you can import the data into your favorite mapping software.

Using the GPX format to feed plucker or a program that goes to pathetique would be just sort of stupid.

My wife says put a coordinate on it and I'll find it.

August 19, 2002

Originally posted by mrcpu:

GPX format means that you can either create a stylesheet to display the data in your web browser as you see fit and then print it to take with you, or you create a palm application that does this and upload the data to it, or you can import the data into your favorite mapping software.

Using the GPX format to feed plucker or a program that goes to pathetique would be just sort of stupid.

Some of us are not programmers, so the format that Brian is working on is very helpful to us. I have used the format from Pathetique and have found it very helpful. I'm sort of computer illiterate (sp) so all the help I can get I truly enjoy.

My wife says put a coordinate on it and I'll find it.

August 19, 2002

Originally posted by mrcpu:

GPX format means that you can either create a stylesheet to display the data in your web browser as you see fit and then print it to take with you, or you create a palm application that does this and upload the data to it, or you can import the data into your favorite mapping software.

Using the GPX format to feed plucker or a program that goes to pathetique would be just sort of stupid.

Some of us are not programmers, so the format that Brian is working on is very helpful to us. I have used the format from Pathetique and have found it very helpful. I'm sort of computer illiterate (sp) so all the help I can get I truly enjoy.

My wife says put a coordinate on it and I'll find it.

August 19, 2002

even do a quote without messing it up. That's why every little bit of help I can get sure is appreciated.

My wife says put a coordinate on it and I'll find it.

August 19, 2002

I just got a chance to read the forums (school started today and things have been a little hectic....). Anyway, this is too cool! Great work Jeremy!

Fat, drunk, and stupid is no way to go through life, son!

August 19, 2002

I just got a chance to read the forums (school started today and things have been a little hectic....). Anyway, this is too cool! Great work Jeremy!

Fat, drunk, and stupid is no way to go through life, son!

August 19, 2002

quote:
Originally posted by Marty Fouts:
Of course, my favorite mapping program doesn't understand XML, and I want to be able to extract subsets of Pocket Query response files to put on my minimum-memory PDA.

And, of course, it's nice to have the data on the PDA in a format that's a little petter compressed than an XML file.

There are a couple of options:

1st. Write a style sheet to create an HTML or csv file for what you want out of the data.

2nd. I'm sure someone pretty soon will fill the space. I've seen a couple of Geocaching apps for the palm recently that seem to have potential if GPX format is supported.

As for a subset, this should be done at the query level, but again, if you want to parse the XML then go for it!

Rob

Mobile Cache Command

GPX Format Status

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment