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.


Messages - Andrew Heard

Pages: 1 2 3 [4] 5
46
Troubles & Questions / Re: no voice during navigation simulation
« on: October 31, 2016, 09:57:09 »
What does it do? When you have disabled GPS, then there is logically no detected movement. If you then start navigation, movement is based on your movement on map center cross anyway still no speed. And this settings say, that when GPS is off, speed of your map center movement will be define value. And because almost everything in navigation is around your speed, Locus needs it to compute voice TTS announcements.
The following users thanked this post: Andrew Heard

47
Versions / Re: [APP] - version 3.19.x (12. 10. 2016+)
« on: October 22, 2016, 09:07:00 »
Guys, I'm glad you find new interface for BRouter useful. I was worried that this solution will be hardly to understand and also Petr with Michal was little "angry" for what I again did, anyway for now I've found it as best what I can do. So enjoy it, it won't be worst :)

@Bango903: hard to help, please read here, mainly part about creating logs. With such vauge description, there is nothing I may do.

@Joachim Buhl: we are talking here about manually clicked route where these via-points are on places where you clicked? This will be changed in next version next week.
The following users thanked this post: Andrew Heard

48
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: October 13, 2016, 06:43:08 »
Hi guys, version is out ...
this was looongest time between two major versions ever, I think. Hope list of news will have something interesting for everyone.
Thanks also for a valuable feedback, just please criticize (constructively), but don't take example from joeloc above and crtiticize at least few days before planned release. Better as soon as you discover any problem.
Thanks!

EDIT: ah! and thanks @gynta for neverending updates of first post with published versions. I almost always forget to update it :).
The following users thanked this post: Andrew Heard

49
Dear Locus map creators and users!

I want to tell you, that I've created several Digital Terrain Models (DTMs), which are based on precise Opendata LiDAR-elevation data of the country's Geographical Institutes. Right now these are:
The improvements in accuracy, quality and fine details of my model's elevations compared to those of the popular SRTM-datasets are enormous. Especially in mountainous terrain.

You can use these new DTMs to create improved, more accurate contour lines in maps. Or you can copy the files for the area of your interest into the correct folder of Locus to improve dynamic elavation values and the shading of the maps in these areas.

The latest versions of Openandromaps in these countries are already based on my DTMs and people say the improvement of contour lines' (and dynamic elevation as well as hill shading) quality in the new maps are excellent.

Have a look at some map comparisons: Map using SRTM-DTM >>> Map using Laser-DTM: http://goo.gl/DM2YxD

There's also a thread regarding the implementation of these DTMs into Openandromaps (in German):
http://www.openandromaps.org/oam-forums/topic/neues-genaueres-hoehenmodell-fuer-oesterreich
The following users thanked this post: Andrew Heard

50
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: September 10, 2016, 18:28:42 »
Hi.  Just looked at this for the first time, and skimmed the wiki.  (My head is spinning.)

In the Locus UI, may I suggest: "Wet conditions".  That means, in a general sense, things are wet right now.  "Is wet" implies knowledge of the route, but you haven't been there specifically yet.

For the explanatory text, maybe "Avoid route that may be difficult in wet weather."  (In North American English, the term "road" doesn't include trails, which are part of this.)

(In spite of my user name, I'm a native English speaker; Spanish is just a hobby to support travel.)
The following users thanked this post: Andrew Heard

51
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: September 05, 2016, 08:19:10 »
[...]

Wet surface
"Try to avoid muddy or slippery roads"

Not clear for me.
This Roads are muddy or slippery only if it's raining??

or this roads always are muddy or slippery because that's his normal ground conditions (bog path, road through marshland, moore land,...)? 

The iswet flag means there is possiblility of being muddy or slippery for  ways that can be - according to OSM surface data -  vulnerable to that.
Iswet could be named as well as "Prefer_roads_that_do_not_get_muddy_or_slippery_if_water_is_applied_on_them". But iswet is shorter. For being muddy as normal condition, there is OSM tag surface=mud.

In trekking bike and bike travelling context, most people would take unpaved soil track shortcut, if it is supposed to be dry, but (not too big ) tertiary road detour instead, if there are/can be muddy ponds on it.

It is generally recommended not to consider things useless until they are understood. Until integrated to Locus, people familiar to BRouter used to got quickly, what iswet flag is good for, as it is an old thing already.
The following users thanked this post: Andrew Heard

52
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: August 12, 2016, 16:04:18 »
What about - perhaps a crazy idea - general expandable list of "slots" for the Locus Routing

It would have
Slot Name ( like Fast Tollfree - car would be seen from the icon )
Mode, projected to the slot icon ( car, moped, bike, foot, canoe ). For BRouter may be extracted from Profile code
User routing service ( Mapquest, OSRM, GraphHopper, BRouter )
Optional legend - extracted or typed
Dynamic routing  options ( possible ?? ) like
     already available options for existing services ( car/bike/foot, fast/short for OSRM etc,)
     for Mapquest also toll, unpaved ...,
     For Brouter the used profile + extracted list of defined parameters.( or just predefined fixed list )
The following users thanked this post: Andrew Heard

53
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: August 12, 2016, 14:31:51 »
- I read about no single problem till now, that car-fast, car-slow ... etc. cause problems to anybody.

I can help you remember :-)

http://forum.locusmap.eu/index.php?topic=5066.msg42633#msg42633

Quote
So this system as is, is usable and logical for users.

The system, as it is used, is not logical. In my mapping I mapped "moped" -> "car slow". A moped is not a car, so this is not logical, it's just a workaround. When zossebart maps 5 biking-profiles on the 5 transport modes and has a hard time to remember what "car slow" actually is, then there's also a usability problem.


Quote
What comes now is a complication - "profiles". You care about "average users". I care currently more about less then average users. They don't care about profiles. I expect, they will use all settings as is, no need to modify it.

I do not agree. The complication is the fact that there are two "namespaces" with a mapping between them. If there's only one namespace, whether you call it a mode or a profile is just wording. A user seeing a combobox with items like "car" "moped" "roadbike" "velomobil" "bike" "hike" will be less confused than a user that has to learn that a moped is a slow car.

Quote
- anyway good point is with extra parameters. As I think about it, agree they should be shared and agree they needs to be visible easily directly during creating navigation definition (start/stop).

Think about consistency. As poutnik pointed out, it's quite arbitrary where you put the "cut" between having distinct profiles or controlling behavior via parameters (and in current beta there are far too many profiles, because most differnces would be better implemented by parameters).

There's no good reason to treat these two ways of configuring the router on different levels of visibility/reachability. So if I convinced you to put the parameters directly on the Navigation Screen, I will also convice you to put the profile name there. Then you have a layout problem because of the extra space that needs, and convice yourself that you need to remove the transport mode buttons :-)
The following users thanked this post: Andrew Heard

54
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 22, 2016, 12:52:49 »
Quote
I would keep scenario themes as the baseline, with bunch of check-in options to tweak them,
like Elevate theme for OpenAndroMaps ( Hiking / Cycling / City, each with lot of options )
exactly +1 8)
The following users thanked this post: Andrew Heard

55
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 22, 2016, 12:46:12 »
Thank you for comments about names of themes. I'll discuss it with team - "Hike & Bike" / "Ski" could be ideal solution. BUT you gave me another idea - "General" theme. What about to remove City theme and create something between City and Hike & Bike. Menion gonna kill me but I like this idea.

IMHO, I would keep scenario themes as the baseline, with bunch of check-in options to tweak them,
like Elevate theme for OpenAndroMaps ( Hiking / Cycling / City, each with lot of options )
The following users thanked this post: Andrew Heard

56
Navigation & Guidance / Re: Automatic Display activation
« on: May 26, 2016, 13:01:30 »
Hello Christian,

main key parameter for guidance that influence "when" Locus switch to next trackpoint is "Set next trackpoint" (in Guidance settings).

About rotation ... good observation. Locus filtered values from "before" screen turned off. I've fixed it now. Result is quite visible jump in rotation right after you turn screen on, but positive is, that you see it almost immediately. So "fixed", thanks.
The following users thanked this post: Andrew Heard

57
Discussion/New features / Re: Locus - offline addresses
« on: May 20, 2016, 13:07:57 »
Hello Petr
We talk about "house number sorting" in march 2016. do you remember?
I think alphabetical sorting arrays will be work. Let's try
Currently we have a wild mixed list.


done
The following users thanked this post: Andrew Heard

58
@ Andrew.
I tested your tracks  (from tracks.zip). Long and short navigation works perfect on TAB4 or THL4000.
@Poutnikl. I know = before generated by Locus.

NEW EDIT: Both tracks are inclusive navigation hints !  (Also notice my used equipment for details)

Succesful Navigation start on the Samsung TAB4. Locus V3.17  (The most used tab for on desk "virtual" tests)
Sucessful Navigation start on the THL4000. Locus V3.17            (The mobile unit in use)

Unseccesfull Navigation start on the  the Samsung Tab Pro: Locus V 3.16.1 (needs push on nearest point)
After updating:
Unsuccesful Navigation start  on the Samsung Tab Pro: Locus V 3.17  (needs push on nearest point)
Unsuccesfull Navigation start on old Android phone: V 3.15.3.  (needs push on nearest point).

Extra EDIT:
Same testcircuit by .tcx file and exact the same report as above.
2 x succesfull  and 2x need a push on nearest point to start.
Attached: the tcx file.
The following users thanked this post: Andrew Heard

59
Discussion/New features / Re: Locus - offline addresses
« on: May 18, 2016, 21:56:57 »
@Andrew Heard
My description were quite simplified. There are more values that influence if road / street has record in DB. Num of segments (number of OSM Way with the same name), the distance from the city (if any exist around), houses along the road...

The handling of long roads is not ideal and the address database does not expect that there could be long roads outside the towns. The generator process them but there are some weakness.
More over is complicated to recognize if Osm Way  is part of street inside any town if it is only some named road outside.  For example almost every forest track in Germany has defined the name. For example https://www.openstreetmap.org/way/37641016

And the question is how handle such way? Is it street? Should we use this road in address search? This is probably the question for every body..

However you can send me some mistakes and I'll check them.
The following users thanked this post: Andrew Heard

60
Versions / Re: [APP] - version 3.17.x (16. 5. 2016+)
« on: May 18, 2016, 14:51:26 »
@Andrew: hmm I'm almost sure that my small change should have no influence on this. I may disable it, as it's just one line of code, but it really should work without a problem.

Do you have exact steps I may follow to get exactly same problem?

I'm trying to play with it little bit, but GPS is always turned of correctly in Locus, hmm :/.

EDIT: maybe I've found some weird combination, so next version probably during weekend, thanks
The following users thanked this post: Andrew Heard

Pages: 1 2 3 [4] 5