Bookmark this page:
If you were Registered and logged in, you could reply and use other advanced thread options
I'd say that 75% of the gpx tracks of hiking trails that I encounter
will not upload to MapSource. A few will...but most will not.
Why is this happening? Is there a work-around?
Many thanks.
Am 31.08.2010 06:55, schrieb PastaClerk:
gpx-files are XML-files an I guess the ones that won't work have all the
data in one line. That's too much for MS. Just get it in a text editor
an hack itin shorter lines e.g. after each </???>. Then you habe a tag
per line and it will work.
Jo Asaret wrote:
> Am 31.08.2010 06:55, schrieb PastaClerk:
>> I'd say that 75% of the gpx tracks of hiking trails that I encounter
>> will not upload to MapSource. A few will...but most will not.
>> Why is this happening? Is there a work-around?
>> will not upload to MapSource. A few will...but most will not.
>> Why is this happening? Is there a work-around?
>
> gpx-files are XML-files an I guess the ones that won't work have all the
> data in one line. That's too much for MS. Just get it in a text editor
> an hack itin shorter lines e.g. after each </???>. Then you habe a tag
> per line and it will work.
> gpx-files are XML-files an I guess the ones that won't work have all the
> data in one line. That's too much for MS. Just get it in a text editor
> an hack itin shorter lines e.g. after each </???>. Then you habe a tag
> per line and it will work.
Your answer appears to be correct, Jo. The GPX tracks that work have
spaces following the </***> while those GPX tracks that create errors do
not have those spaces.
I'm putting in the spaces for a GPX file using Notepad and its "Find"
feature, but this is really slow going.
Might there be a utility available to do this? I've searched for one and
can't find it.
Might there be a better tool than MapSource that could handle GPX files
with no line spacing?
Many thanks.
On Tue, 31 Aug 2010 12:52:12 -0700, PastaClerk wrote:
> Jo Asaret wrote:
>> Am 31.08.2010 06:55, schrieb PastaClerk:
>>> I'd say that 75% of the gpx tracks of hiking trails that I encounter
>>> will not upload to MapSource. A few will...but most will not.
>>> Why is this happening? Is there a work-around?
>>> will not upload to MapSource. A few will...but most will not.
>>> Why is this happening? Is there a work-around?
>>
>> gpx-files are XML-files an I guess the ones that won't work have all the
>> data in one line. That's too much for MS. Just get it in a text editor
>> an hack itin shorter lines e.g. after each </???>. Then you habe a tag
>> per line and it will work.
>> gpx-files are XML-files an I guess the ones that won't work have all the
>> data in one line. That's too much for MS. Just get it in a text editor
>> an hack itin shorter lines e.g. after each </???>. Then you habe a tag
>> per line and it will work.
>
>
> Your answer appears to be correct, Jo. The GPX tracks that work have
> spaces following the </***> while those GPX tracks that create errors do
> not have those spaces.
>
> I'm putting in the spaces for a GPX file using Notepad and its "Find"
> feature, but this is really slow going.
>
> Might there be a utility available to do this? I've searched for one and
> can't find it.
>
> Might there be a better tool than MapSource that could handle GPX files
> with no line spacing?
>
> Many thanks.
>
> Your answer appears to be correct, Jo. The GPX tracks that work have
> spaces following the </***> while those GPX tracks that create errors do
> not have those spaces.
>
> I'm putting in the spaces for a GPX file using Notepad and its "Find"
> feature, but this is really slow going.
>
> Might there be a utility available to do this? I've searched for one and
> can't find it.
>
> Might there be a better tool than MapSource that could handle GPX files
> with no line spacing?
>
> Many thanks.
Does your editor not have a replace function?
If not get one of the more advanced free downloads. I use NoteTab Light,
which also has a paid version.
You might have to use regular expressions to do the above, so I guess
you really do have to find another besides NotePad.
--
Gene E. Bloch (Stumbling Bloch)
Am 31.08.2010 21:52, schrieb PastaClerk:
> Jo Asaret wrote:
>> Am 31.08.2010 06:55, schrieb PastaClerk:
> Your answer appears to be correct, Jo. The GPX tracks that work have
> spaces following the </***> while those GPX tracks that create errors do
> not have those spaces.
> I'm putting in the spaces for a GPX file using Notepad and its "Find"
> feature, but this is really slow going.
> spaces following the </***> while those GPX tracks that create errors do
> not have those spaces.
> I'm putting in the spaces for a GPX file using Notepad and its "Find"
> feature, but this is really slow going.
It's not a matter of spaces but of the total line length. I had
gpx-files with 100MB of size, all in one single line that wouldn't
import in MS. Adding newlines (not spaces!) after each '>' cured the
problem.
> will not upload to MapSource. A few will...but most will not.
> Why is this happening? Is there a work-around?