[BaseCamp] Waypoint Properties Box cells for city, state, street etc...

Jerry White jerrywhite518 at gmail.com
Thu May 23 06:58:07 PDT 2019


Thanks for the update.

On Wed, May 22, 2019 at 6:33 PM saddle sore <ironbutter at gmail.com> wrote:

> Jerry
>
> You asked specifically about my solution for populating BC properties box
> cells, so I'll report in.  At this point I have found that Extra POI Editor
> (EPE) over on POI Factory seems to accomplish what I want.  It has its
> limits, but what doesn't?  At least it will populate the cells that I want
> to populate in a BC waypoint properties box.  Quite easy to learn.
> Frustrating to have to move spreadsheet columns around to fit their order,
> but so far it works.  So that's what I am going with for this particular
> project I am working on.
>
> Note -- EPE is no longer supported by anyone and you have to dig around a
> bit to find a download.  The wikispaces site is closed.  A bit of install
> info at http://www.poi-factory.com/node/38068  and some options as to
> which version with and without installers
> http://camerabob.dyndns.org:5190/TurboCCC/
>
> Oh, and to answer my very first question.....  it was a GPSVisualizer
> thing.  GPSVisualizer is an easy-peasy way to convert files from xls to gpx
> just as long as you want just a few of those waypoint property box cells
> populated.  I'll continue to use it, but that decision will be on a case by
> case basis.  When wanting more cells populated, I think EPE is my go-to
> solution now.
>
> Thanks,  Joe Y
> western PA
>
>
>
> .
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-7723657975247211959_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Mon, May 20, 2019 at 9:30 AM Jerry White <jerrywhite518 at gmail.com>
> wrote:
>
>> Let us know how you eventually solve it.
>>
>> Have you noticed in the second example that the latitude in the cmt
>> (comment?) and desc fields is far off the actual latitude of the waypoint?
>>
>> On Mon, May 20, 2019 at 5:26 AM saddle sore <ironbutter at gmail.com> wrote:
>>
>>> Stephen, Jerry
>>>
>>> Thanks for the replies.  I have been out all weekend, away from a
>>> computer (ah, so nice to be 'unplugged').
>>>
>>> I started looking into the reverse engineering of a database per
>>> Stephen's idea.  For an exported BC gpx file which contains things like
>>> city, state, street, the internal metadata is much different from one that
>>> does not contain the info.  For example, here is what it looks like if I
>>> export a file that has known street, city, state info in the BC properties
>>> box.
>>>
>>>    <wpt lat="45.552476970478892" lon="-122.9097049869597">
>>>
>>>     <time>2019-04-02T20:52:38Z</time>
>>>
>>>     <name>'Hondo' Hydrant Tribute</name>
>>>
>>>     <sym>Contact, Dog</sym>
>>>
>>>     <type>user</type>
>>>
>>>     <extensions>
>>>
>>>       <gpxx:WaypointExtension>
>>>
>>>         <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
>>>
>>>         <gpxx:Address>
>>>
>>>           <gpxx:StreetAddress>4499 NW 229th Ave
>>> <https://maps.google.com/?q=4499+NW+229th+Ave&entry=gmail&source=g>
>>> .</gpxx:StreetAddress>
>>>
>>>           <gpxx:City>Hillsboro</gpxx:City>
>>>
>>>           <gpxx:State>OR</gpxx:State>
>>>
>>>         </gpxx:Address>
>>>
>>>       </gpxx:WaypointExtension>
>>>
>>>       <wptx1:WaypointExtension>
>>>
>>>         <wptx1:DisplayMode>SymbolAndName</wptx1:DisplayMode>
>>>
>>>         <wptx1:Address>
>>>
>>>           <wptx1:StreetAddress>4499 NW 229th Ave
>>> <https://maps.google.com/?q=4499+NW+229th%0D%0AAve&entry=gmail&source=g>
>>> .</wptx1:StreetAddress>
>>>
>>>           <wptx1:City>Hillsboro</wptx1:City>
>>>
>>>           <wptx1:State>OR</wptx1:State>
>>>
>>>         </wptx1:Address>
>>>
>>>       </wptx1:WaypointExtension>
>>>
>>>       <ctx:CreationTimeExtension>
>>>
>>>         <ctx:CreationTime>2019-04-02T20:52:38Z</ctx:CreationTime>
>>>
>>>       </ctx:CreationTimeExtension>
>>>
>>>     </extensions>
>>>   </wpt>
>>>
>>> But one waypoint from a file which I converted from Excel to GPX using
>>> GPSVisualizer (and then exported it back out of BC so I could view the
>>> metadata) looks like this
>>>
>>>   <wpt lat="37.530850041657686" lon="-85.735950004309416">
>>>
>>>     <time>2018-12-04T22:02:41Z</time>
>>>
>>>     <name>Abraham Lincoln Birthplace NHP</name>
>>>
>>>     <cmt>N37° 31.851' W85° 44.157'</cmt>
>>>
>>>     <desc>N37° 31.851' W85° 44.157'</desc>
>>>
>>>     <sym>Flag, Green</sym>
>>>
>>>     <type>user</type>
>>>
>>>     <extensions>
>>>
>>>       <gpxx:WaypointExtension>
>>>
>>>         <gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
>>>
>>>       </gpxx:WaypointExtension>
>>>
>>>       <wptx1:WaypointExtension>
>>>
>>>         <wptx1:DisplayMode>SymbolAndName</wptx1:DisplayMode>
>>>
>>>       </wptx1:WaypointExtension>
>>>
>>>       <ctx:CreationTimeExtension>
>>>
>>>         <ctx:CreationTime>2018-12-04T22:02:41Z</ctx:CreationTime>
>>>
>>>       </ctx:CreationTimeExtension>
>>>
>>>     </extensions>
>>>
>>>   </wpt>
>>>
>>> If it is up to me to alter or actually write code so that example 2
>>> becomes as detailed as example 1, well,  my code writing days ended decades
>>> ago -- about the time that the IBM punch card went the way of the Dodo
>>> Bird.  So, Jerry, I will look into GPSBabel (I have used it before but
>>> didn't feel it was as user friendly as GPSVisualizer) to see what it does
>>> with a file.  And, I am tracking down the person that created the file I
>>> have which contained example 1 above.  So thank you for your time and
>>> advice.  I appreciate the help and direction.
>>>
>>> Joe Y
>>> western PA
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
>>> www.avg.com
>>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> <#m_-7723657975247211959_m_-583403336609704373_m_5726881043662333888_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> On Fri, May 17, 2019 at 11:16 AM Jerry White <jerrywhite518 at gmail.com>
>>> wrote:
>>>
>>>> Looks like gpsbabel can read CSV and write GPX. Good luck!
>>>> https://www.gpsbabel.org/index.html
>>>>
>>>>
>>>> On Fri, May 17, 2019 at 7:52 AM Stephen! <ldrider at imagesdesavions.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> >How do I get Street, City, State and maybe other cells to populate
>>>>> when
>>>>> >I import the gpx file into BaseCamp?
>>>>>
>>>>> Not at my routing laptop right now but when working with CSV & GPX
>>>>> conversions, I always find it easier to work backwards, so-to-speak...
>>>>>
>>>>> Start in Basecamp with a waypoint that HAS all the info you want,
>>>>> export that waypoint as a GPX.  Open the GPX in a text editor and see
>>>>> exactly what Basecamp uses as a label for each data field you want to
>>>>> use...  Now you know exactly what to put at the top of each column in your
>>>>> CSV before converting it to a GPX.
>>>>>
>>>>>
>>>>> --
>>>>> There is no need to tailgate me when I am doing 50 in a 35...  and
>>>>> those flashing lights on top of your car look ridiculous.
>>>>>
>>>>> To make _ANY_ changes, including unsubscribing from this list, click
>>>>> ----->http://micapeak.com/mailman/listinfo/basecamp
>>>>>
>>>>>


More information about the Basecamp mailing list