Author: lonvia
[Added to the original trac issue at 7.45pm, Thursday, 23rd August 2012]

This is a data problem. There is no street named 'Gegui g.' in the area. Nominatim needs a street with the exactly same name as the name you used in the addr:street tag.

Side node: please don't abbreviate street names (speaking of the 'g.' in 'Gegui g.' here). It is much easier for a machine to abbreviate a complete name than guess what an abbreviation means.

Author: geriBatai
[Added to the original trac issue at 12.23pm, Thursday, 30th August 2012]

Replying to [comment:1 lonvia]:

Side node: please don't abbreviate street names (speaking of the 'g.' in 'Gegui g.' here). It is much easier for a machine to abbreviate a complete name than guess what an abbreviation means.

I'm not sure about this. I use "g." because most of the time addresses are not found without it. As example - "13, Virsilu" finds only street object, yet "13, virsilu g." finds the house number. Data problem also?

Author: lonvia
[Added to the original trac issue at 7.38am, Friday, 31st August 2012]

Replying to [comment:2 geriBatai]:

I'm not sure about this. I use "g." because most of the time addresses are not found without it. As example - "13, Virsilu" finds only street object, yet "13, virsilu g." finds the house number. Data problem also?

Yes, in this case Nominatim is tripped by the fact that there is a street named 'Virsilu' as well. If you rename http://www.openstreetmap.org/browse/way/80515568 to 'Viril g.' it will work fine.

Technical explanation: Nominatim looks for the street first and then for house numbers on the street. In this case, it is happy to find an exact match to your query 'Virsilu' and stops right there. It then cannot find the house number because it is attached to the other way named 'Viril g.'.

Anyhow, this has nothing to do with you using abbreviations or not. If you name that street 'Viril g.', it is rather difficult to find out that this is supposed to mean 'Viril gatv' (at least that is what Google tells me) because you first have to figure out which language that name is in etc. It is much easier, when the name is not abbreviated in OSM. Then all we need is a list of common abbreviations for each language. Of course, you still need to let us know what all these abbreviations mean in Lithuanian.

Author: geriBatai
[Added to the original trac issue at 1.18pm, Friday, 31st August 2012]

Replying to [comment:3 lonvia]:

Replying to [comment:2 geriBatai]:

I'm not sure about this. I use "g." because most of the time addresses are not found without it. As example - "13, Virsilu" finds only street object, yet "13, virsilu g." finds the house number. Data problem also?

Yes, in this case Nominatim is tripped by the fact that there is a street named 'Virsilu' as well. If you rename http://www.openstreetmap.org/browse/way/80515568 to 'Viril g.' it will work fine.

Technical explanation: Nominatim looks for the street first and then for house numbers on the street. In this case, it is happy to find an exact match to your query 'Virsilu' and stops right there. It then cannot find the house number because it is attached to the other way named 'Viril g.'.

Anyhow, this has nothing to do with you using abbreviations or not. If you name that street 'Viril g.', it is rather difficult to find out that this is supposed to mean 'Viril gatv' (at least that is what Google tells me) because you first have to figure out which language that name is in etc. It is much easier, when the name is not abbreviated in OSM. Then all we need is a list of common abbreviations for each language. Of course, you still need to let us know what all these abbreviations mean in Lithuanian.

What I would like to know is what to do with all the street data in Lithuania. Almost all of the streets have 'g.' (shorthand for gatv - street) attached