Re: General Comments
Yup. Dummy me. Brought the file into NotePad++ It understands the xml syntax. Much easier to pick through. Thx for the reply. Not going to experiment with it anyway. Like the way it works now. And you guys keep up the good work. Kevin On Sunday, March 8, 2020 at 5:21:12 PM UTC-4, Harry van der Wolf wrote: > > > > Op zo 8 mrt. 2020 om 21:57 schreef Kevin McLaughlin >: > >> >> Saw the comments about "Cant find routing.xml" >> Spent about an >> hour last night looking at the internal >> >> > It is not the routing.xml itself. That is an xml file INSIDE the apk (an > apk is actually a specially structured hierarchical) zip file. > If the user in the other topic meant that, he was right. I added 2 xml > files to that post, and he mentioned he had copied those and cound not find > them. > Maybe a big misunderstanding. > In that those internal zip folders are more files, like the > "/net/osmand/router/routing.xml" or the > "/net/osmand/osm/rendering_types.xml" or the > "/net/osmand/render/default.render.xml". And many more. Some of them are > unpacked to the Android file system to /Android/data/net.osmand(.dev | > .plus)/files in the several subfolders. And some remain in the apk like the > routing.xml. > > You can copy the routing.xml into that routing folder inside > "/Android/data/net.osmand(.dev | .plus)/files" and modify it, or make > derivaties of it and copy those under different names into that folder. > Some other internal folders can be treated the same way. > > >> >> Never found the routing.xml >> >> Like mentioned above. > > >> Just as an experiment I grabbed the "routing.xml" from the >> install of apk. Using WinRar to look at the contents of the apk. >> Found the routing.xml. Put it in the routing directory >> and played with the *heuristicCoefficient .* >> From the apk, the car route value is 1.5. >> Changed it to 1.0. >> >> No this is not correct. That 1.5 value is an "outcommented" value. If you > altered that one it is still outcommented and will simply not work, like > you described further in your mail. > > Don't look at the top. Look at the header for the several . > Below the default: > minSpeed="20.0" defaultSpeed="45.0" maxSpeed="130.0" leftTurn="5" > rightTurn="5" roundaboutTurn="5" onewayAware="true"> > > Below my modified from mycar15 > restrictionsAware="true" minSpeed="20.0" defaultSpeed="45.0" > maxSpeed="130.0" leftTurn="5" rightTurn="5" roundaboutTurn="5" > heuristicCoefficient="1.5"> > > Note the heuristic coefficient at the end and also the altered name "mycar > 1.5". Otherwise OsmAnd doesn't know which profile to use. > > > Harry > > -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/abef58b0-0b0b-4e0f-89ec-6c6aee70ebd1%40googlegroups.com.
Re: General Comments
Op zo 8 mrt. 2020 om 21:57 schreef Kevin McLaughlin : > > Saw the comments about "Cant find routing.xml" > Spent about an > hour last night looking at the internal > > It is not the routing.xml itself. That is an xml file INSIDE the apk (an apk is actually a specially structured hierarchical) zip file. If the user in the other topic meant that, he was right. I added 2 xml files to that post, and he mentioned he had copied those and cound not find them. Maybe a big misunderstanding. In that those internal zip folders are more files, like the "/net/osmand/router/routing.xml" or the "/net/osmand/osm/rendering_types.xml" or the "/net/osmand/render/default.render.xml". And many more. Some of them are unpacked to the Android file system to /Android/data/net.osmand(.dev | .plus)/files in the several subfolders. And some remain in the apk like the routing.xml. You can copy the routing.xml into that routing folder inside "/Android/data/net.osmand(.dev | .plus)/files" and modify it, or make derivaties of it and copy those under different names into that folder. Some other internal folders can be treated the same way. > > Never found the routing.xml > > Like mentioned above. > Just as an experiment I grabbed the "routing.xml" from the > install of apk. Using WinRar to look at the contents of the apk. > Found the routing.xml. Put it in the routing directory > and played with the *heuristicCoefficient .* > From the apk, the car route value is 1.5. > Changed it to 1.0. > > No this is not correct. That 1.5 value is an "outcommented" value. If you altered that one it is still outcommented and will simply not work, like you described further in your mail. Don't look at the top. Look at the header for the several Below my modified from mycar15 Note the heuristic coefficient at the end and also the altered name "mycar 1.5". Otherwise OsmAnd doesn't know which profile to use. Harry -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPpvK0%3D71NMK3qtKZ_QrPNQu_SqeZESh3Mk08LrtRJv1t1Q%40mail.gmail.com.
General Comments
Long time user of Osmand. Been quite a while since I commented. I used to keep several versions on my phone. Using.. net.osmand net.osmand.dev net.osmand.plus However the 3.6.3 has been such a remarkable cleanup of the menus for the different profiles, I'm dumping everything I used to play around with. Great job with the new interface to the the profiles. Cleaner! Elegant! Orthogonal! Not sure what the best word is. I run Osmand on a $59 phone from 4 years ago. And it works great. About the routing. Yes sometimes a little slower than some of the other commercial ones, but I played with all of them a lot over the past 4 years and I "feel" osmand tends to give more logical results. Like not routing through a big city instead of taking the bypass around the city. While it's cool to see a 500 mile route. In reality I don't drive than way. I pick a spot down the road to get going. Maybe a 100 miles. The points further down the road I pick in my head while driving. Long distance plans just never seem to work out for me. Saw the comments about "Cant find routing.xml" Spent about an hour last night looking at the internal net.osmand/files/routing net.osmand.dev/files/routing net.osmand.plus/files/routing and the external net.osmand/files/routing net.osmand.dev/files/routing net.osmand.plus/files/routing on versions 3.4.8, version 3.5.5, and version 3.6.3 And I used the file search menu of Fx file explorer. So the guy that can't find it. I think he's right. Never found the routing.xml Which is fine with me as I have no desire to optimize something that has been optimized by people with a lot more knowledge of what's going on "under the hood". Just as an experiment I grabbed the "routing.xml" from the install of apk. Using WinRar to look at the contents of the apk. Found the routing.xml. Put it in the routing directory and played with the *heuristicCoefficient .* >From the apk, the car route value is 1.5. Changed it to 1.0. Was not able to observe any difference on the calculation time of a 50 mile route. But I have no idea if the app is even reading the routing.xml from the directory I put it in so not much point to the experiment. I personally don't think I should be screwing with that value. Much simpler to "guide" a route with "avoid road" and "intermediate points" I can then jump to another application and get the same route. Which by the way. The "Cruiser" app by "devemux86" is really quite remarkable. Simple, lightweight. Routes from point A to point B using car, bicycle, or foot. Can learn the entire menu system is about 10 minutes. If Osmand is the "swiss army knife" then "Cruiser" is the "dagger" or "switch blade". Osmand and Cruiser are the two navigation apps I keep on my phone. If I had and mission to Mars, needed a navigation system that my life depended on, it would probably be "Cruiser" So to both camps. Keep up the great work. The offline maps are great. And both Apps are great!. Kevin -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/ee648ee1-ae56-4a26-ae80-288d98c87035%40googlegroups.com.
Preferred types of roads: no options selectable
There's an option called "Preferred roads", in German "Bevorzugen von..": navigation profile > routing parameter But the only two options there are called - Autobahnen bevorzugen (prefer motor ways) - unbefestigte Straßen bevorzugen (prefer unpaved roads) The first option is not changeable, even if you set "Keine Autobahnen" (no motor ways) in roads to avoid. Could someone explain this to me, please? Why is one type of road listed there, and why can't I change it? Did I do something wrong or did I misinterpret something? -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/6130343b-342f-484b-a02f-319dd2b25c9c%40googlegroups.com.
Re: How can I find all results for keyword/value "internet_access = wlan" and "internet_acccess:fee = no"?
There are two ways how we can create a poi for wlan, and - unfortunately - two different ways how we can access it with search: (1) internet_access=wlan is the "main" atrribute example: https://www.openstreetmap.org/node/7048846981 internet_access=wlan internet_access:fee=no name=EDEKA free-wifi operator=EDEKA (2) internet_access=wlan is NOT "main" attribute, but in this example amenity= cafe is the "main" attribute (and/or shop=bakery). internet_access=wlan is only a "additional" attribute, which is handled quite different in search !!! https://www.openstreetmap.org/node/4450210786 amenity=cafe shop=bakery internet_access=wlan internet_access:fee=no name=Die Kaiserin highchair=yes opening_hours=Mo-Sa 06:00-20:00, Su,PH 07:30-20:00 outdoor_seating=yes website=https://bahnhof.kaisers-backstube.de/ wheelchair=yes - The way, Harry described, refers ONLY to case (1). Wlan created like case (2) will NOT be found ! To find case (2) pois follow this instructions: - Create a custom seach which contains ALL categories in ALL category groups, which might be relevant. In the example above , add at least whole groupe "Food". To get also shops with wlan add whole group "Store", to get also Hotels with wlan add whole group "Tourism" and so on. Of course you can only add the single categories, but it is easier (and it works) if you add complete groups. I - personally added ALL groups, so I will get really ALL pois with wlan. - After having added one or more groups: + in the blue bar at bottom, press SHOW + press the symbol for settings in the top bar Now you see a long list with options with check boxes. + scoll down to "Internet access type" and open (expand) it + ckeck "wifi" + press APPLY FILTERS in blue bar at bottom OR SAVE FILTER on top bar (three dots menu) That's all. Quite easy, isn't it Ok. --- If you want to FIND BOTH (1) AND (2), you need to search for BOTH seperately. I did not find a way to solve that with ONE Search. If anybody has an idea, it is very wellcome. Have fun with testing! Peter -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/3302434a-c252-47ab-a649-4ad2c4914b83%40googlegroups.com.
Re: Vehicle parameter: weight and hight need more options
Thanks again for your kind help! I will try your two modified routing profiles during the week and if you're interested, I will report back their behaviour and performance next weekend. I looked into the discussions that you gave links to, about the heuristic and brouter, but I'm afraid I did not understand half of it. I am not a real programmer, and I am missing many of the background theories there. So I can not predict which one of your files is the best for me, I will have to stick to try to find out . ;) -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/223b686b-650a-4626-9ac5-ee44288aa7f6%40googlegroups.com.
Re: Vehicle parameter: weight and hight need more options
I created a pull request ( https://github.com/osmandapp/OsmAnd-resources/pull/613). The 12t and 30t have been added. Now you have to wait untill a new release is published on the Play store to have it by default in the app. Op zo 8 mrt. 2020 om 12:16 schreef Harry van der Wolf : > Sorry. I made a very stupid mistake. > I set the 12t as 12r, and did not add the correct weight. > Please use attached one. > > Please also find a truckmod12.xml which uses a slightly elevated hc=1.2. > Try for yourself :) > > Harry > > > Op zo 8 mrt. 2020 om 12:08 schreef Harry van der Wolf : > >> >> >> Op zo 8 mrt. 2020 om 11:46 schreef We Ka : >> >>> >>> Talking about a vehicle's length: this should also become an optional >>> parameter for routing in a future version, because there are also >>> limitations in length on many crossings and corners. These limitations do >>> not only apply to trucks, but also to vans and cars pulling trailers. So I >>> thing that this is of common interest as well. >>> >>> >> Sorry. Forgot to answer this. Please file this as a feature request at >> https://github.com/osmandapp/Osmand/issues >> >> Harry >> > -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPpv%2BUTM072m0XXmxUhfrS2Cn7HpBfc%3DJC5pHr3khYpi9%2Bg%40mail.gmail.com.
Re: Osmand routing calculation is very slow for long distance for many years
Op zo 8 mrt. 2020 om 14:57 schreef 'ra' via OsmAnd : > what I do not understand: I would expect the 1,5 to give the fastest route > also, due to smaller rates of choice. but although the differences are > close to non-existence that is not the case. > That is not necessarily true. When using a higher hc, the "search for alternatives" (my terminology) is stopped earlier. It does not follow all roads (paths according the mathemathical wording) until it finds another that, when adding it to the route, leads to an even faster route in total, where in this case faster=shorter => shortest path. Please read this (very high overview) article in wikipedia: https://en.wikipedia.org/wiki/A*_search_algorithm Use in Google for example the search term "shortest path A* algorithm" and look for the images and videos, which to some are more explanatory than reading a page of text. > when I drive by car I am mostly not in a hurry and would like to be lead > to small unknown roads that even shorten my way - so I mostly choose gas > saving (in fact, that is what I love osmand the most for!). one problem > here still remains: the time calculations become completely wrong the > moment I switch for gas saving. they are more than 50% to high (while > without they are pretty much exact). a trip which takes about 3hours20 may > be displayed with 5hours10. that shure helps not starting too late - but > arriving way too early doesn't help either ;-) how can I change that > without getting into even bigger problems? thank you! > > I did read your questions/remarks/issues related to this earlier. When looking at the routing.xml it is "just" a different setting of the parameters. Therefore I think it is a bug in the calculation: the route may be correct, but OsmAnd does something strange with the route time calculation. Harry -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPptK2YvuqYtMVO0KzYoJex7WyUk8fT1TX2UXUZumH3ewAQ%40mail.gmail.com.
Re: Osmand routing calculation is very slow for long distance for many years
dear harry, I followed your kind advice but am afraid to need more. I installed all smoothly and tested now with a few destinations of about 100 and 200 km distance. you are right: the only difference really is the time taken: with the standard profile you say to have HC1,0 it takes more time to calculate. which is most annoying when in need of a fast recalculation because of a deviation. I remember well sitting on the roadside for minutes after minutes sometimes (in former times) waiting for osmand to help me find my way (great when it's dark and raining!). that is over after I switched for your 1,2 or 1,5. what I do not understand: I would expect the 1,5 to give the fastest route also, due to smaller rates of choice. but although the differences are close to non-existence that is not the case. when I drive by car I am mostly not in a hurry and would like to be lead to small unknown roads that even shorten my way - so I mostly choose gas saving (in fact, that is what I love osmand the most for!). one problem here still remains: the time calculations become completely wrong the moment I switch for gas saving. they are more than 50% to high (while without they are pretty much exact). a trip which takes about 3hours20 may be displayed with 5hours10. that shure helps not starting too late - but arriving way too early doesn't help either ;-) how can I change that without getting into even bigger problems? thank you! Am Freitag, 6. März 2020 15:25:39 UTC+1 schrieb Harry van der Wolf: > > > > Op vr 6 mrt. 2020 om 15:16 schreef Episteme PROMENEUR < > episteme...@gmail.com >: > >> >> About long distance itinerary computing,for bike trekking what value for >> hc ? >> >> How to assign this value ? >> >> The heuristic coefficient is always 1.4 for bike trekking, unless you > make your own profile. > (So there the hc is not 1.0, like for car navigation. For pedestrian it is > 1.2) > I therefore do not know if it is interesting to play with this for cycling. > > See the blog post describing new features: https://osmand.net/blog > > You can easily play with the profiles. The original routing.xml can be > found on and downloaded from: > https://github.com/osmandapp/OsmAnd-resources/blob/master/routing/routing.xml > > Copy attached mycar15.xml to Android/data/net.osmand(.plus)/files/routing. > Same for mycar12.xml > > Make sure that they are saved as .xml. Some file managers save xml files > as .xml.txt > Simply open the xml in a text editor and you see that it is only a > subset for car navigation (but this can be done the same way for other like > the mentioned bike trekking). > The only changes are the name of the derived profile and the heuristic > coefficient which are added in the header of the routing profile. > You can also easily modify that yourself to play with other values. > > Open OsmAnd > - Settings -> Scroll down and create new profile > - Select Profile car > - Give it a name (mycar 1.5?) > - Select color and icons and save. > > You are now still in your freshly created profile. > - Got to navigation settings (2nd option) > - Select Navigation type (1op one) > - Now scroll down and select the mycar15 navigation type > - Go back until your are out of the profile and you can now use it. > - Adapt it further to your liking. > > > Attached also a mycar12.xml. I use this one in big towns. > -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/9cbde803-5880-40c2-b795-a401d07e0eed%40googlegroups.com.
Re: Vehicle parameter: weight and hight need more options
Sorry. I made a very stupid mistake. I set the 12t as 12r, and did not add the correct weight. Please use attached one. Please also find a truckmod12.xml which uses a slightly elevated hc=1.2. Try for yourself :) Harry Op zo 8 mrt. 2020 om 12:08 schreef Harry van der Wolf : > > > Op zo 8 mrt. 2020 om 11:46 schreef We Ka : > >> >> Talking about a vehicle's length: this should also become an optional >> parameter for routing in a future version, because there are also >> limitations in length on many crossings and corners. These limitations do >> not only apply to trucks, but also to vans and cars pulling trailers. So I >> thing that this is of common interest as well. >> >> > Sorry. Forgot to answer this. Please file this as a feature request at > https://github.com/osmandapp/Osmand/issues > > Harry > -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPps5RjJGZKRYZ1R55psVufw3fitvo5__RYrfwAJ5KGyZbA%40mail.gmail.com.
Re: Vehicle parameter: weight and hight need more options
Op zo 8 mrt. 2020 om 11:46 schreef We Ka : > > Talking about a vehicle's length: this should also become an optional > parameter for routing in a future version, because there are also > limitations in length on many crossings and corners. These limitations do > not only apply to trucks, but also to vans and cars pulling trailers. So I > thing that this is of common interest as well. > > Sorry. Forgot to answer this. Please file this as a feature request at https://github.com/osmandapp/Osmand/issues Harry -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPptSsqWS72RdNaXk0vNrxVohNQ7qvh6e4qAdgnG0ZqoCWw%40mail.gmail.com.
Re: Vehicle parameter: weight and hight need more options
Op zo 8 mrt. 2020 om 11:46 schreef We Ka : > > Note that the attached truck_mod.xml still has the default heuristic >> coefficient (heuristicCoefficient="1.0") >> > > I don't know what this means, what (dis)advantage it will bring and if I > should change it to any thing else. If you could tell me in one or two > sentences, I'd be thankful. > > Sorry, but I can't explain this in 2 sentences. a heuristic coefficient =1 it theoretically (!) the best but by far the slowest (and used by OsmAnd by default). "Real world" values are somewhere between 1.2 < hc < 1.6. In the real world a value between 1.3 and 1.5 is optimal (I think). See the posts in this thread: https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/osmand/EeVN_6i1UaI/QmCpwSk2CwAJ If you only want the specifics, start with my post of 5 March and ending with my post on 6 March with the 2 xml files attached. And do not only read my posts but also those of Arndt (creator of Brouter) and of Florian. These contain really important info. Harry -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAGARPptc201OXfa%2BjGRnPjWP5WxJs_iSHHV186rn%2B9avqBF3mw%40mail.gmail.com.
Re: Vehicle parameter: weight and hight need more options
Thank you very much! This will certainly ease my work a lot by shortening the routes. :) > Please let me know what it should be and I will do a pull request. Adding the 12t is simple, but are there more (legal) weight limits? Theoretically, any limitation of maximum allowed weight is possible on a road. It depends on the static of bridges, the ground beneath the pavement, and on the tightness of turnings and corners of a road, because a truck's maximum weight and length are mostly related to each other. (Not always, but most of the times.) And last, but not least, it depends on what kind of traffic the local residents want in their streets. ;) But the most common limitations are: 3,5t, 5t, 7,5t, 12t, 20t. The limitation to 12t max weight is a very important one, because it is the category of trucks that is most often used for delivery of heavy and large goods to private addresses and companies in local areas and within towns. Talking about a vehicle's length: this should also become an optional parameter for routing in a future version, because there are also limitations in length on many crossings and corners. These limitations do not only apply to trucks, but also to vans and cars pulling trailers. So I thing that this is of common interest as well. Note that the attached truck_mod.xml still has the default heuristic > coefficient (heuristicCoefficient="1.0") > I don't know what this means, what (dis)advantage it will bring and if I should change it to any thing else. If you could tell me in one or two sentences, I'd be thankful. -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/79a94b26-e5af-4533-bc38-59ad9846921f%40googlegroups.com.
