Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Masterijn

#16
I find that when we pause our walks for few longer moment to sit on a bench, the measured track length is getting a lot lengthier than the actual one (+10%). I guess this is because gps noise is recorded as well. I suppose by using a good noise canceling method, the 2 will be close together. My wish would be that this method would be more advanced. I know there are parameters by which to tune the recording like time and distance. But a stronger method, would also take different parameters or could be self learning. I know Oziexplorer works internally by taking angle, velocity changes etc into acount. For the user, only one "smoothing factor" parameter could be enough. Which even could be chosen with some preview/feedback when saving the current track and then controlling the post processing of raw data.
In short:
More advanced realtime smoothing for track display
Recording of gps raw data and controllable advanced smoothing with feedback when saving the track.
#17
Troubles & Questions / Off track warning
August 03, 2014, 20:37:40
When walking along a route I found that Locus incorrectly warns about being off track. I guess Locus computes how one is off track by calculating the distance to the active waypoint. But on many routes, with long straight lines this waypoint can be quite far away. I would like it better if the distance to the active route section (the line to the active waypoint, from the previous) would be taken. In the case of going off track, I would like locus to talk (tts) me to the closest point on that section instead of to the active waypoint. I find it important that I can take the right roads, even if the wrong road is also close to the active waypoint. By measuring the distance to the active section, the max off track distance can be tighter, and the distances from tts will be smaller and more usefull. Now I get false messages like route is 100 m on 0 o clock. I would like correct messages like: route is 20 meters 10 o clock.  This is good info on which to decide wether to take another road in real life or wether its a false message coming from gps inaccuracy.
#18
Other features / Re: Vector map speed
July 17, 2014, 08:48:29
You mean nearby pois are shown first? That would be nice! (Galileo is missing that feature, but one can filter by screenarea)
The offer of giving optimalisations a thought was in general. Vector maps are very specific, and beyond my knowledge :).
#19
Other features / Re: Vector map speed
July 13, 2014, 23:33:09
Is there an easy way to get the complete poiname list as a txt file or something. I've become interested in how my algorithm with fuzzy searching would stand out on such a huge list. I guess it won't be fast enough, but I'm wondering... You beeing the solo developer, this can be a good thing in respect to efficiƫncy. You'll probably need 2 extra developpers before the development will become faster, because of the overhead and learning curve of teammembers. You should turn it around, I think you are proving with Locus how powerfull a single dedicated developer can be.

As a developer i've always been somewhat of a speed optimizer, if you would like my view on optimizing a subsystem I would gladly give it a serious thought.
#20
Other features / Vector map speed
July 13, 2014, 22:10:20
You're absolutely right, functionality is more important. B.t.w. I cannot run as fast to get a bothersome delay, however for me it was suprising, because I'm already pleased with the vectormaps implementation in Locus. Beeing a developer myself, I created a huge list searching alogorithm last year. It was of a fuzzy searching kind. The best matching strings are shown first. It was implemented in a way that it doesn't need process the whole list to make that "decision". The first items are popping out fast followed by the less matching ones. The searching is quite robust against little typing errors. Years before I did some searching in a 300k list, this was restrictive searching, which can be done faster. On a normal computer this could be done in ms (need to checkit). The poi's are in the 1M but I expect it can be done within 1/10 of a sec in android phone if indexes are beeing used. Keep up the good work!
#21
Other features / Vector map speed
July 12, 2014, 16:14:18
Today I found a new version of Galileo on my iPad 3. I never came to to use this app in the field. It's incredibly limited in functionality. That said, here comes the point: in respect of render speed of vector maps it just much faster than what I used to on my Note 3. Uch locus uch... I know Locus depends on opensource renderer of vector maps, but I guess this still has a lot of room for improvement. In Galileo it's so fast that it even hard to see individual tiles are beeing rendered. But I guess the difference isn't explained by hardware vs software rendering. Another speed difference is in the drawing of tracks, this Is also much faster in Galileo. They also have an instant search and display of offline pois.
B.t.w. this is not an attack on Locus, but one sometimes needs some reference to set a feasible target.
#22
Thanks for the reply I will dive into it.
#23
Is there a way to know wich objects kan be adressed in rules? For instance in the latest o.s.m. maps of Viewranger I can see invidual houses being drawn at a high zoomlevel. In the vectormaps of Locus these are always drawn as larger blocks of multiple houses. So is this because of the rules are missing  or is the vectormapsdata less detailed?
#24
Did a check, after pairing with the simple phone android can use this connection to go on the internet.
#25
Once I put a laptop on the internet via bluetooth and a very simple phone. So it should be possible.
#26
Via bluethooth modem (to anothervsmartphone) ? Or is dat broken as well?
#27
While my searched continued I also came across Cachelab, but I only took a small glance. Now I took a better look, and indeed they've done a neat job!
Unfortunately it takes a lot of time to implement a multicache, but when it's done at home it takes only a little time in the field. Some basic integration with mapping software (google map url) or some preloading from geocaching.com would be nice. Also I don't understand why they use a strange coordinate output. I know a : is easier to type for input but in the output one could still use a degree symbol, better for copy and pasting!

edit
Locus addon solver seams like a more ideal solution. Cachelab supports sharing, which would be great in a local user community.
#28
Add-ons & Co-apps / Re: Locus Addon Solver
May 25, 2014, 11:00:33
Having worked with this app, I realy like it a lot. I think it's a very elegant solution with a lot of automaticity but also enough ways to do things by hand. I think that the part of stacked functions can theoraticaly be limiting. Can be overcome by creating intermediate variables, but a more versatile expression evaluation could be more powerfull.   
#29
Add-ons & Co-apps / Re: Locus Addon Solver
May 24, 2014, 23:17:25
Seem promising!
#30
GeoTiff is just a tiff-file with some extra info so for 90% normal tiff documentation can be used. The geo stuff are an extension, but follow the tiff way of doing stuff. I can send you my Delphi implementation, but I think the record stuff is handled different in Java. But as an example it couldn't be more easy. the class converts Tiff data to Png data via a png encoder. It shows getting the image size, reading the pixel data and a bit more. I think it was an evenings work.