Contour Plott export and general data questions
Posted: Sat Jun 04, 2005 9:18 am
David,
don't know if you recall, but i am working with GPS/Sonar data to make contour plot for lake bottoms. you helped me with my app last fall and now all is working well and i am ready to go to the next step in the project.
right now i can open the gps/sonar units output file convert to lat,lon,depth and make a plot in dplot jr. i want to add two features: join together two data sets from two different recording sessions and exporting the plot into a format that can be downloaded into the gps/sonar unit. the first is easy, the second i'm not sure of yet.
so here goes:
for the joining of data feature i can simply add the new data onto the end of the old data and plot the whole thing. simple and easy. but, if the data set gets too large then time complexity may bite me in the butt. how big of a file can i realistically plot? i have been testing with files of less than 50k and of course it plots faster than i can blink. but what if i start getting 256 Mb? or more, even 10 times more? 256 Mb in one session is the current working limit of the gps/sonar unit i am using.
now i am also thinking that there may be a lot of "repeated" data in subsequent sessions in the same area. so i am thinking about some kind of optimizing of the data set. i'll try to explain: the gps data has a resolution of DD MM.mmm so 1/1000 of a minute or about 1.5 meters. so if you think about a cartesian plane with a major division of .001 min then your location could be anywhere on that plane. if you happen to be on an intersection then your position is reported exacly, if you happen to be inside of a square then your position is reported to be the nearest corner to your true location. thus i could record the same coordinates for two actual position that are really nearly 3 meters apart. so i am trying to decide how to sort out that margin of error and what data to keep, toss, average or ??? what are your thoughts on this? if the time complexity is a non-issue then i could just leave it all in there and let the plotting function "average" it all into the contours. any input appreciated.
also recall that this is just for fishing, so a modest amount of "let it slide" is certainly OK.
on the exporting idea: i would like to be able to take the contoours and convert them back into a series of gps coordinates that could then be loaded into the gps unit for reference on the boat. can i get that type of data out of dplot in some way? i realize that i would have to limit the number of points used, but that is something that i can work out.
thanks for any help,
cheers
jerry
PS: if your interested i can send you the app to check out.
don't know if you recall, but i am working with GPS/Sonar data to make contour plot for lake bottoms. you helped me with my app last fall and now all is working well and i am ready to go to the next step in the project.
right now i can open the gps/sonar units output file convert to lat,lon,depth and make a plot in dplot jr. i want to add two features: join together two data sets from two different recording sessions and exporting the plot into a format that can be downloaded into the gps/sonar unit. the first is easy, the second i'm not sure of yet.
so here goes:
for the joining of data feature i can simply add the new data onto the end of the old data and plot the whole thing. simple and easy. but, if the data set gets too large then time complexity may bite me in the butt. how big of a file can i realistically plot? i have been testing with files of less than 50k and of course it plots faster than i can blink. but what if i start getting 256 Mb? or more, even 10 times more? 256 Mb in one session is the current working limit of the gps/sonar unit i am using.
now i am also thinking that there may be a lot of "repeated" data in subsequent sessions in the same area. so i am thinking about some kind of optimizing of the data set. i'll try to explain: the gps data has a resolution of DD MM.mmm so 1/1000 of a minute or about 1.5 meters. so if you think about a cartesian plane with a major division of .001 min then your location could be anywhere on that plane. if you happen to be on an intersection then your position is reported exacly, if you happen to be inside of a square then your position is reported to be the nearest corner to your true location. thus i could record the same coordinates for two actual position that are really nearly 3 meters apart. so i am trying to decide how to sort out that margin of error and what data to keep, toss, average or ??? what are your thoughts on this? if the time complexity is a non-issue then i could just leave it all in there and let the plotting function "average" it all into the contours. any input appreciated.
also recall that this is just for fishing, so a modest amount of "let it slide" is certainly OK.
on the exporting idea: i would like to be able to take the contoours and convert them back into a series of gps coordinates that could then be loaded into the gps unit for reference on the boat. can i get that type of data out of dplot in some way? i realize that i would have to limit the number of points used, but that is something that i can work out.
thanks for any help,
cheers
jerry
PS: if your interested i can send you the app to check out.