"Jalan XXXXX" road name again?

[doraemon]

I can't see anything wrong with "Ahmad, J". Saves display space and less taxing on processor power to do search for older units.

The bigger problem is the inconsistency in then naming, using abbreviations or full name. I will use MSM maps for example. Eg. Try searching for Public Bank branches. Search for PBB and you will see a whole list, but many branches are missing. Why? Because they are listed as Public Bank.

I have faced this problem again and again.

Thats what I mention in my post.... This time we are not only review the road naming convention, but the standards of naming POI we are going to review and obey as well.

TTS I think you will have to record your voice for the word "Jalan" to read as "Jalan" in garmin. It should not be a problem if you record the "Jln" or ", J" to read as "Jalan". Else the nuvi has to install a dictionary of so many language to be able to read out different language preference?

Can anyone confirm this... I just do some guessing here.

[moeyhc]

The GPS only matches the keyword to its data base. So whatever key word use it has to go thru' the "successive approximation" search method to find your key word. Naming them any format does not slow it down either. As long as partial name search is supported I don't see any problem. I do have concern when the full name/address is used and cannot be fully display on some GPS unit. There is a limitation in character length a GPS can display at a given time. If the address is too long you'll not see the most important road designator eg. Jalan Very Important Road Name 73/1G . If you can't see '73/1G' It is a problem...isn't it?... just my 5 sens.

[jans_wkh]

Can anyone try searching for 'Park' in other nuvi unit to see if the bug is only limited to GMXT only? I think we have to be careful here when we say the partial address search is working, as based on the partial address search that I have brought up here, there seems to be some ambiguous result output from the search. If I did not select the results output but just by glancing at the results, I wouldn't know its for Fair Park, Cerok instead of Park, Cerok.

[musangking]

My opinion is that if it is a proper name, it should be in full. For instance Teluk Intan but if it is Jalan Intan, then Intan, J is fine because it is easier to find Teluk Intan by keying in Teluk than to find it sifting through numerous Intans. For those uninitiated, it may be difficult to know what abbreviation is used for Teluk as it is a proper name. Same for Simpang Renggam, Bukit Jalil etc. GPS is not only used by enthusiasts but also as a tool for those who are less tech savvy (aka wives ) and searches will be difficult if they don't know what to key in.

[ss173b]

GPS is getting very common now a days and people who buy these days, expect to work out from the box. They face difficulties when they start to perform the search and get "No search found" error.

Cheers, Kelvin.

[9w2man]

I prefer Jalan Masjid India instead of Masjid India, J coz the first one is official format appeared in every road in Malaysia.....so people will no "congfius" lah

[OngTY]

Option 2 work fine for me as well.

[antyong (retired)]

Our maps handle partial search now. You can search for a word in the middle of the address, etc.

The way we name our roads, using the "xxxxx, J" format was done at the beginning of time when address searches had to be done from the beginning.

This is the time to review this practice and decide whether we want to retain the current format or revert to conventional naming. Please vote.

Hi antyong, doesn't mean to pour cold water or something, but just giving my 2 cents. When I read about the partial search, I did a quick check with the symbian GMXT version and this is what I have found out.

In the 1st picture, the result 'Park, Cerok' is actually referring to 'Fair Park, Cerok' in 2nd picture. 'Whereas in POI partial search, the full road name shows. The partial address search would be good, if not for the ambiguous 'partial' results shown for viewer selection. I am not sure if bug exists for nuvi or other GMXT platforms.

About the road name convention, it would be good to have the normal format provided it would not cluster the display during navigation and those device with TTS function would definitely benefit from this naming format. What Doraemon proposed for abbreviation is quite valid, but I won't know how Lrg, Psn or Jln would sound in TTS. Anyone with TTS capability would care to comment?

p.s Thanks for all the hardwork to the contributors and mappers for MSM1.03

We may not be familiar with it or like it but this is apparently how Garmin address search work. You search for a word, Garmin gives you a list of options which contain your word and then asks you to refine your search further. Therefore technically, our partial search behaves the same as Garmin NT maps and we cannot do anything more than that. The future re-inclusion of road name POIs will give our members an alternative choice of searching.

[antyong (retired)]

It is a valid point that putting "Jalan" in front makes less free space for name display. In order to find out how significant is this disadvantage, we need to do 2 things:
1. Find out the max road name display of each model (another project for our volunteer testers )
2. Find out the number of roads with name exceeding the max display

[liewss80]

Since Partial Name Search is currently supported, I would vote for full road name, such as Jalan Puchong, rather than Puchong, J which carries a big question mark to New Users.

In the prev map, I support "Puchong, J" format because its faster to search. Users dont have to type "Jalan" every time. But now, user can still type "Puchong" only to search for "Jalan Puchong" (partial name search), so, no point to use the "J" abbreviation anymore. Better use a Standard one which could be understd and acceptable by public......