News:

Plan-G has over 1700 followers on FACEBOOK! Click HERE and add your support

Main Menu

User waypoint csv files & database

Started by gert57, January 24, 2014, 10:47:29 AM

Previous topic - Next topic

gert57

Hi Tim,
I made a complete new install of Plan-G v3.07. Befoere that all old files were cleared away in the program folder and in the document folder.
Program strarts up ok and functions well.
But considering user waypoints some strange things happen:
1. I used the virgin database instealled when installing plan-G I wanted to edit an OZx user waypoint, adding some info. BUT I could not click ok, the button was grayed out and unclickable. With this waypoint I observed something strange. In the field magvar the number was shaded red, and it showed a rather large positive value, I believe 347.
2. After that I tried to import some csv files. All controlled in CSVed if the syntax etc and comma separation was ok. The files impoted allright, user waypoints showed up on the map. BUT all these user waypoints had the same strange behaviour as the user waypoint in 1.
The log file showed no faults. So I tried importing vfr waypoints in France. These showed up ok, AND COULD BE EDITED!!
Maybe this has to do something with the magvar field. records with a poitive magvar coulld be edited, records with a neg magvar couldnt.
I did an test. A single record was exported and the large positive number was edited to a corresponding negative number in CSVed, eg 348 changed to -12.
Afterwards record imported, shows up allright but cant be edited AND THE NEG NUMBER CHANGED TO 348 AND DISPLAYED RED in the editing screen.
I hope this info can help you solving this problem.
Thank you for all your effort in creating and maintainig this very usefull piece of software.

Gert

tim arnot

That's interesting; +347 should be equivalent to -13 degrees, and it ought to be handled accordingly (I don't remember off the top of my head whether that equates to east or west). I'll look into why it isn't. Thx.

Tim. @TimArnot

gert57

Hi Tim, I installed the new version of plan-g.
The issue is now fixed.
Thank you!
Greetings,
Gert

tim arnot


Tim. @TimArnot