|
|
Post by donsarlak on Dec 5, 2015 21:16:23 GMT 5.5
HI,
After converting OSM to Navitel nm3 format through GPSmapedit, some of the POIs do not show up in search results even though they are visible in the map itself. Is it an error in converting or anything to do with attributes in those POIs? (map data was downloaded from garmin.openstreetmap.nl)
|
|
|
|
Post by ajith on Dec 6, 2015 6:16:49 GMT 5.5
HI, After converting OSM to Navitel nm3 format through GPSmapedit, some of the POIs do not show up in search results even though they are visible in the map itself. Is it an error in converting or anything to do with attributes in those POIs? (map data was downloaded from garmin.openstreetmap.nl) Since you say some of the POIs, they definitely have some marking errors as computer algorithms have no double standards on any data. I have found this scenario on my Garmin also and I am on the halfway to find the reason. If you could kindly tell me 2,3 such places, I can easily come to a conclusion that where the problem is. |
|
|
|
Post by sadeepa on Dec 6, 2015 7:46:38 GMT 5.5
HI, After converting OSM to Navitel nm3 format through GPSmapedit, some of the POIs do not show up in search results even though they are visible in the map itself. Is it an error in converting or anything to do with attributes in those POIs? (map data was downloaded from garmin.openstreetmap.nl) Since you say some of the POIs, they definitely have some marking errors as computer algorithms have no double standards on any data. I have found this scenario on my Garmin also and I am on the halfway to find the reason. If you could kindly tell me 2,3 such places, I can easily come to a conclusion that where the problem is. By the way do you see this on nm3 maps I have published too? If so please let us know such features. |
|
|
|
Post by donsarlak on Dec 6, 2015 10:26:11 GMT 5.5
Since you say some of the POIs, they definitely have some marking errors as computer algorithms have no double standards on any data. I have found this scenario on my Garmin also and I am on the halfway to find the reason. If you could kindly tell me 2,3 such places, I can easily come to a conclusion that where the problem is. By the way do you see this on nm3 maps I have published too? If so please let us know such features. I checked with sadeepa's map & it shows the same search results without a problem. One thing I noticed is, for an example, on sadeepa's map, Sakura restaurant in Rheinland place shows with a proper restaurant icon and on mine it shows with a fast food icon, plus the pop-up does not show when you touch on that icon. This is the same for other POIs, mainly restaurants, which do not show up in search results in my map (ex. Sapid, Sizzle, Flower lounge, Green cabin, Kami maki). Maybe something happens when converting them to nm3 from img.   |
|
|
|
Post by sadeepa on Dec 6, 2015 15:49:24 GMT 5.5
By the way do you see this on nm3 maps I have published too? If so please let us know such features. I checked with sadeepa's map & it shows the same search results without a problem. One thing I noticed is, for an example, on sadeepa's map, Sakura restaurant in Rheinland place shows with a proper restaurant icon and on mine it shows with a fast food icon, plus the pop-up does not show when you touch on that icon. This is the same for other POIs, mainly restaurants, which do not show up in search results in my map (ex. Sapid, Sizzle, Flower lounge, Green cabin, Kami maki). Maybe something happens when converting them to nm3 from img. When you are converting did you change the type set from Garmin to Navitel in GPSMapedit ? If not try changing it (File - > Map Properties -> Header -> Type Set). I think when we convert between typesets they may not 100% correctly match. I will try to look at the problems you have reported. |
|
|
|
Post by sadeepa on Dec 7, 2015 13:05:25 GMT 5.5
HI, After converting OSM to Navitel nm3 format through GPSmapedit, some of the POIs do not show up in search results even though they are visible in the map itself. Is it an error in converting or anything to do with attributes in those POIs? (map data was downloaded from garmin.openstreetmap.nl) Try these two maps and let me know 1. NM2 maps updated 01st Dec 2015 ('anura' has confirmed that it worked on his CE device but do not know search results as in your case) 2. SL_151102_CE.nm3 (November map indexed on a CE device and tested with Navitel V.9.1.0.491 on WinCE 6.0 (128K RAM) device. Search works for the POIs you have listed.) |
|
|
|
Post by donsarlak on Dec 7, 2015 16:31:35 GMT 5.5
HI, After converting OSM to Navitel nm3 format through GPSmapedit, some of the POIs do not show up in search results even though they are visible in the map itself. Is it an error in converting or anything to do with attributes in those POIs? (map data was downloaded from garmin.openstreetmap.nl) Try these two maps and let me know 1. NM2 maps updated 01st Dec 2015 ('anura' has confirmed that it worked on his CE device but do not know search results as in your case) 2. SL_151102_CE.nm3 (November map indexed on a CE device and tested with Navitel V.9.1.0.491 on WinCE 6.0 (128K RAM) device. Search works for the POIs you have listed.) Both map files worked fine on wince6  . Search results didn't have any faults  . I wonder my map source garmin.openstreetmap.nl is at fault for ending up with wrong POI types. May I know from where you get yours? |
|
|
|
Post by Thilina on Dec 7, 2015 20:34:44 GMT 5.5
|
|
|
|
Post by donsarlak on Dec 7, 2015 21:45:55 GMT 5.5
Thanks for the link. But are these file extensions support by GPSmapedit? |
|
|
|
Post by sadeepa on Dec 7, 2015 22:50:58 GMT 5.5
Thanks for the link. But are these file extensions support by GPSmapedit? Download OSM file from above link and then use "osm2mp32" to convert it to MP format.Thilina has posted link to it in this forum. Then the procedure is same as you've already done (as we discussed on PM). Do not worry I will publish NM2 files for WinCE users monthly. |
|
|
|
Post by ajith on Dec 16, 2015 12:06:57 GMT 5.5
මම දැකල තියනව සමහර තැන්වල පදික මාරුව "Street Crossing" විදිහට නම් කරල තියනව. ඒක හරිද? මම නම් හිතන්නෙ "Pedestrian Crossing" තමයි හරි.
|
|
|
|
Post by sadeepa on Dec 17, 2015 8:10:42 GMT 5.5
මම දැකල තියනව සමහර තැන්වල පදික මාරුව "Street Crossing" විදිහට නම් කරල තියනව. ඒක හරිද? මම නම් හිතන්නෙ "Pedestrian Crossing" තමයි හරි. These are just two presets on ID2 editor. When you just look the words I seems "Pedestrian Crossing " is more appropriate. But I think we need to dig bit deeper. If you look at at the descriptions for "Street Crossing" and "Pedestrian Crossing" on ID2 it shows same description and leads to same wiki page. Therefore wee need to look at the differences in tags they add to road data. So when you look at the tag it adds to highway is equal too. It differs in other details (1)Street Crossing highway=crossing
crossing=uncontrolled crossing_ref=zebra (2)Pedestrian Crossing highway=crossing
crossing=zebra When you look at above two tag sets, (1) is more accurate, descriptive and complies with usage description for "Crossing" in OSM wiki (http://wiki.openstreetmap.org/wiki/Key:crossing). So if someone uses JOSM or other editor and set tags as No (1) case, ID2 will show it as "Street Crossing". ID2 shows "Pedestrian Crossing" only for the above mentioned (2) tag set. For ex: at a place where you have red/green man symbol lights we have to use highway=crossing crossing=traffic_signals Then again ID2 will show it as "Street Crossing". If you look at all these cases in "Potlatch" editor all above cases are shown as "pedestrian crossings" (There is no Street crossing preset in Potlatch ?). Finally my opinion is "use correct tags (key,value pairs) for what you want to mark". These tags (key,values) are the things which will be used by navigation app or any other app not preset names of different editors.
So if I happen to use ID2, I would start with any of above crossing presets and edit default tags (key, values) as appropriate. |
|
|
|
Post by Thilina on Dec 17, 2015 8:31:02 GMT 5.5
I usually use option 1 but without crossing=uncontrolled, because it very rare traffic signal for pedestrians in sri lanka |
|
|
|
Post by sadeepa on Dec 17, 2015 8:58:12 GMT 5.5
I usually use option 1 but without crossing=uncontrolled, because it very rare traffic signal for pedestrians in sri lanka Thats true. I think we can assume "crossing=uncontrolled" as the defaults value, but adding it means no harm. Now a days where ever traffic lights are there they seems to fix lights for pedestrians too. So its not that rare in and around cities |
|
|
|
Post by Thilina on Dec 17, 2015 9:06:25 GMT 5.5
I usually use option 1 but without crossing=uncontrolled, because it very rare traffic signal for pedestrians in sri lanka Thats true. I think we can assume "crossing=uncontrolled" as the defaults value, but adding it means no harm. Now a days where ever traffic lights are there they seems to fix lights for pedestrians too. So its not that rare in and around cities mmm if so i need to update my preset in JOSM . when i was working in bambalapitiya i notice that non of those buttons in traffic signals for pedestrian are working. (bambalapitiya, wellawatta and dehiwala area ) i though same as for rest of palaces  . |
|
. Search results didn't have any faults 
. I wonder my map source garmin.openstreetmap.nl is at fault for ending up with wrong POI types. May I know from where you get yours?
.