I've actually been thinking of suggesting an ":abbr" suffix key to all name-accepting tags (name, name:en, name:fr, alt_name, int_name, etc.) and the values are a semicolon-separated list of abbreviations. This is backwards compatible since existing tools can still use the base name tags and ignore the :abbr tags. But for renderers and namefinder tools that need abbreviated names, then can then look into the :abbr tags and select the one which fits the space or matches a query.<br>
<br>Example:<br><br>name=Epifanio delos Santos Avenue<br>name:abbr=Epifanio delos Santos Ave.;E. delos Santos Ave.;EDSA<br><br>name=Asian Development Bank Headquarters<br>name:abbr=ADB HQ;ADB<br><br>Another advantage is that this frees the alt_name key for truly alternate names. Some people place the abbreviation/acronym into the alt_name which doesn't seem correct since the abbreviation is still the same name, just shortened, and not an alternate.<br>
<br>Example:<br><br>name=Sen. Gil J. Puyat Avenue<br>name:abbr=Sen. Gil J. Puyat Ave.;Sen. Gil Puyat Ave.;Gil Puyat Ave.;Gil Puyat<br>alt_name=Buendia Avenue<br>alt_name:abbr=Buendia Ave.;Buendia<br>old_name=Buendia Avenue<br>
old_name:abbr=Buendia Ave.;Buendia<br>
<br>I haven't thought yet of how to handle standard abbreviations (like Avenue -> Ave., Street -> St., Road -> Rd., North -> N.) so that the abbr: tags need not specify these explicitly.<br><br><br><div class="gmail_quote">
On Fri, Jul 17, 2009 at 11:10 AM, Arne Goetje <span dir="ltr"><<a href="mailto:arne@linux.org.tw">arne@linux.org.tw</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi list,<br>
<br>
in Taiwan we have the situation, that street names may be too long to be<br>
rendered on the map. In addition, we'd like to keep the map bilingual<br>
(Chinese, Romanized/English), which makes the names rendered on the map<br>
even longer. How can we give the renderer some hints how to abbreviate<br>
the street names properly in different zoom levels?<br>
<br>
Would it be possible to specify multiple alternative entries in the<br>
'name' tag and the renderer picks whatever fits onto the map?<br>
<br>
For example:<br>
A very common naming scheme for small alleys is to number them according<br>
to their location on the main road. When a lane/alley is located between<br>
house numbers 8 and 12, it would carry the number 10.<br>
The naming scheme is:<br>
* Main Road (路/街/道) -- optionally with Section (段)<br>
* Chinese: 介壽路二段<br>
* Full romanized/English name: Jieshou Road Section 2 (or: Section 2<br>
Jieshou Road)<br>
* Abbr.: Jieshou Rd. Sec. 2 (or: Sec. 2 Jieshou Rd.)<br>
* Lane (巷)<br>
* Full Chinese name: 介壽路二段325巷<br>
* Full romanized/English name: Lane 325, Jieshou Road Section 2<br>
* Chinese abbr.: 325巷 (rendered next to the associated main road on<br>
Chinese maps)<br>
* Romanized/English abbr.: Ln. 325, Jieshou Rd. Sec. 2<br>
* Further abbrevation: Ln. 325 (rendered next to the associated main road)<br>
* Alley (弄)<br>
* Full Chinese name: 介壽路二段325巷1弄<br>
* Full romanized/English name: Alley 1, Lane 325, Jieshou Road Section 2<br>
* Chinese abbr.: 325巷1弄 (or: 1弄 rendered next to the associated lane)<br>
* Romanized/English abbr.: Aly. 1, Ln. 325, Jieshou Rd. Sec. 2<br>
* Further abbrevation.: Aly. 1, Ln. 325 (or: Aly. 1 rendered next to<br>
the associated lane)<br>
* Cross-Alley (衖)<br>
* Full Chinese name: 介壽路二段325巷1弄1衖<br>
* Full romanized/English name: Alley 1-1, Lane 325, Jieshou Road Section 2<br>
* Chinese abbr.: 325巷1弄1衖 (or: 1弄1衖, or: 1衖)<br>
* Romanized/English abbr.: Aly. 1-1, Ln. 325, Jieshou Rd. Sec. 2<br>
* Further abbr.: Aly. 1-1, Ln. 325 (or: Aly. 1-1)<br>
<br>
Now: a user would search for either the full Chinese name, or the most<br>
complete romanized/English abbreviation, but not the full<br>
romanized/English name (nobody uses that one).<br>
So, the database and routing engine would need to know those entries:<br>
* Chinese: 介壽路二段325巷1弄1衖 （actually it would need the full<br>
address, which would include city and county, except for bigger cities,<br>
there the county is omitted)<br>
* Romanized/English: Aly. 1-1, Ln. 325, Jieshou Rd. Sec. 2<br>
<br>
On the map however, the lanes and alleys are usually quite short. We do<br>
prefer to render the names bilingual, i.e. Chinese name<br>
(romanized/English name) -> 介壽路二段325巷1弄1衖 (Aly. 1-1, Ln. 325,<br>
Jieshou Rd. Sec. 2), but fall back to Chinese only if the alleys are<br>
even too short for the abbreviations below (Sometimes alleys are just 20<br>
Meters long).<br>
So, it would be nice if we could tag the roads with a list of<br>
alternatives for the renderer to pick from in order to render the street<br>
name according to the zoom level.<br>
e.g.:<br>
* 介壽路二段325巷1弄1衖 (Aly. 1-1, Ln. 325, Jieshou Rd. Sec. 2)<br>
* 325巷1弄1衖 (Aly. 1-1, Ln. 325)<br>
* 1弄1衖 (Aly. 1-1)<br>
* 325巷1弄1衖<br>
* 1弄1衖<br>
* 1衖<br>
<br>
For the rendering options: just put them all in the 'name' tag,<br>
separated by ';' ?<br>
<br>
For the rendering position, I was thinking: maybe this could be done<br>
with relations?<br>
E.g.: 介壽路二段325巷1弄1衖 is a member of 介壽路二段325巷1弄, which is<br>
a member of 介壽路二段325巷, which is a member of 介壽路二段, which is a<br>
member of 八德市 (city), which is a member of 桃園縣 (county).<br>
<br>
If we would build up relations like that and also include the house<br>
numbers, would we be able to find the house if we provide the full<br>
address in one string (e.g. 桃園縣八德市介壽路二段325巷1弄1衖39號)? Or<br>
would we need to tag each house with the full address individually?<br>
<br>
How about postal codes? Also use relations for that? (E.g. a relation<br>
for postal code 33444 would include all the roads, lanes, alleys and<br>
houses)?<br>
<br>
Would Mapnik/Osmarender be able to handle such constructs?<br>
<br>
Cheers<br>
Arne<br>
<font color="#888888">--<br>
Arne Götje (高盛華) <<a href="mailto:arne@linux.org.tw">arne@linux.org.tw</a>><br>
PGP/GnuPG key: 1024D/685D1E8C<br>
Fingerprint: 2056 F6B7 DEA8 B478 311F 1C34 6E9F D06E 685D 1E8C<br>
Key available at <a href="http://wwwkeys.pgp.net" target="_blank">wwwkeys.pgp.net</a>. Encrypted e-mail preferred.<br>
<br>
<br>
</font><br>_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/dev" target="_blank">http://lists.openstreetmap.org/listinfo/dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://vaes9.codedgraphic.com">http://vaes9.codedgraphic.com</a><br>