OpenStreetMap

Supaplex's diary

Recent diary entries

State of the Map Asia 2016參與記實

Posted by Supaplex on 26 November 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

這次去馬尼拉,參與 State of the Map Asia 其實是很倉促的決定,看到有 scholarship 可申請,就想說談談臺灣社群狀況,順便會會一些相關公司、社群的人。這次決定並沒有讓我失望,除了見到朋友 Wular,還碰到 Mapbox data team印度團隊的人,以及久聞大名的 Manning。

Manning Opening

Mapbox 的團隊最近在幫忙對齊臺灣的道路網路,採用新出爐的 Mapbox 衛星影像,還有 Strava GPS 軌跡。先前我只有跟 Manning 和 Mapbox data team 線上打過交道而已,見到面感謝他們的貢獻,發聲說說臺灣的狀況,能夠配合遠端鍵盤繪圖的人做些什麼事情。

這是我的演講Slide,由於時間有限,刪減不少內容。在這邊大略敘述我講了什麼,留下文字記錄。

My slide

臉書使用 OSM 資料對臺灣的影響

我談到臉書採用 OSM 資料的部分沒講太清楚,蠻多人在演講後有疑問有跑來跟我聊聊。臉書在兩個地方用 OSM 資料:用 OSM 資料訓練 AI 畫地圖;用 OSM 資料當地標資料的底圖。前者不少關心 OSM 的人都知道,也觀察到臉書的 AI 有重覆畫既有的道路網,這麼就不累敘了。

Facebook landmark page

臉書目前在日本、南韓都有用 OSM 當地標資料的底圖,而地標位置則在臉書手上,當然是使用者給他們的資料。但在去年臉書有在中國、臺灣、越南試驗把地標點底圖換成 OSM,結果在臺灣引起相當大的風波。一來是 OSM 未必在每個地方每條巷弄都畫出來,給人一種地圖很不精細粗糙的使用體驗;二來是很多人搞不清楚地標的位置由使用者建立,所以如果當初建立時輸入錯誤的訊息,那臉書拿到的資料也就錯誤了。建錯的地標連同被換掉的底圖,被怪罪到OSM,其實就不是 OSM 的問題,地標放錯位置是Facebook問題。

有一個最誇張的例子是有人興沖沖的回報他們地標位置標錯了,而且指責附近一帶的地圖上沒畫出多少巷弄,語言用詞相當的沒禮貌。當時臉書有把使用者回報導向 OSM 的 Note 系統,所以許多大大小小的抱怨湧入,有些可能是 OSM 問題,有些臉書的問題,像地標位置設錯了。這些回報包括這位沒禮貌的回報者,也就沒意識到寫出來的內容是公開的,永遠存在網路上。

Complain from Facebook user

最後臉書大概也煩了,沒人力可以處理本來他們應該處置的使用者抱怨,臺灣這邊的地標底圖改用 Here 圖資,也結束臺灣OSM社群的困擾。

需要訂定能用在臺灣的tagging標準

OSM 強調可以實作多語言地圖,照顧不同語言使用者的需求。於是我們看到除了 name 欄位填入在地社群的慣用名,其他像是 name:en、name:de、name:ja、name:fr、name:zh 表示對應的語言名稱,採用 alpha-2 code of ISO 639-1 的語言代碼後綴。

但儘管有辦法能夠實現多語言共存的狀況,仍然要先制訂標準出來。實際上在中文世界這邊,OSM 目前訂定的name:zh並不夠,不能妥善涵蓋用到繁體、簡體中文字的人,需要另行制訂繁體中文、簡體中文對應的 tag。

還有一問題是誰的中文才是中文name:zh,在中國和臺灣等用中文的地區之外,究竟要用中國的中文代表中文,還是臺灣的中文代表中文呢?誰的中文才是中文?

於是 Rex 大大依據 IETF language tag  (BCP 47) 的語言規範,制訂適用臺灣、中國、香港、澳門,以及其使用中文的地方,或者有用到中文譯名的地方。

Chinese name tag proposed

除了字體之外,把地區不同用詞也考量進去。比如說,在臺灣、中國各自用慣用的繁體、簡體在name:zh欄位沒什麼大問題,但在這兩個地方以外,有些地方不只簡繁體的差異,而是用詞完全不同,像是Mt. Everest,臺灣用的是聖母峰,而中國那邊採用喜马拉亚山。

也許提 Mt. Everest 對菲律賓人來說很遙遠,因此在演講時反應不強。我應該提一些菲律賓的知名地名或旅遊景點,比較讓菲律賓和外國人有點印象,像是民答那峨 (Mindanao)、薄荷島 (Bohol)。兩者在臺灣和中國分別是如下稱呼:

  • 英文 臺灣繁體中文 中国简体中文
  • Mindanao 民答那峨 棉兰老
  • Bohol 薄荷 保和

由此可見,除了繁簡體中文字問題,還有不同的慣用翻譯,影響 OSM 的在地化和體驗。

除了中文的標示問題以外,臺灣還有使用南島語系福爾摩沙語言的原住民,結合先前有關原住民地圖的討論,曾談到該使用那些語言代碼當後綴,也一併在這一次納入。

Tagging for the Formosan language of Taiwan Aborigines

對臺灣的社群來說,長期目標是希望各個使用 OSM 圖資的開發者,能夠逐步採用這套語言標示服務各地中文使用者,解決臺灣、中國等地繁、簡字體差異,還有用詞不一的問題,提供各地用戶更客製化、在地化的體驗。未來臺灣的 OSM 社群在提出這套方案之後,也將通知各個用到 OSM 資料的地圖 app 開發者,希望他們能夠採用。

與歐美主流宗教不同的宗教崇拜場所標示問題

現行在 OSM 的宗教教派標示方式,像是佛教、基督教、天主教、道教、回教的分別,對於標示臺灣的宗教和民間信仰並不精確,容易帶來誤解。臺灣很多廟宇祭拜的對象以歷史人物為主,分辦是屬於那個宗教教派其實沒意義。應當更聚焦在這間宗教崇拜場所是供奉那位神祗。

小時候我學到依廟宇名稱後面來分辨是佛教還是道教,xx宮被歸為道教廟宇,而xx寺則是佛教廟宇。有一陣子我會依據前述提到的原則來標示。但後來仔細鑽研之後發現並不精確,因為前面提到區別主要拜那位神才更精確更有意義。

Taiwan traditional religion tagging

因此Rex提出傳統信仰標注方式 (草案),希望提出一套標準來解決前面提到如何標示臺灣多元宗教教派的面貌,解決現行OSM上臺灣宗教歸類的亂像。除了前面提到應當用主祠神為主要區別,應該另立獨立的臺灣傳統宗教信仰標籤,下面有例子解釋。

臺灣漢人傳統信仰:

  • religion=folk
  • denomination=TaiwaneseFolkReligion

為了兼顧非漢人信仰,像是西拉雅族的阿立祖公廨標法:

  • religion=folk
  • denomination=SirayaFolkReligion

廟宇標法範例:

慈惠堂 (仍須依據其運作模式來判斷)

  • religion=folk
  • denomination=TaiwaneseFolkReligion
  • dedication:principal=瑤池金母
  • dedication:principal:wikidata=Q1064059

其他的標籤問題

其他還有其他問題,像是中文地址書寫習慣,在線上編輯器iD欄位設計時主要考慮英文地址書寫方式,造成中文排列問題,會在 iD 2.0 版獲得改善。

不同的廠商、組織的交流

我在演講時刻意提到 Mapbox 團隊在臺灣依據 Strava GPS 軌跡,重新對齊臺灣道路網。演講完也與他們團隊有相當密切的交流。原先只有在網路平臺交換意見,能在實體空間碰面交談,類似第一次面對面見到網友的體驗,相當新奇。

Mapbox works

我也遇到 Maps.me CEO,跟他交換不少意見。他在演講時提到 OSM 需要輕量的參與者,增加在地的商家,因此就需要能夠很簡單就能增加資訊的 App,他們的 Maps.me就是這樣一套工具,不然靠重量級的圖客觸腳永遠都碰不到所有地方。

我跟他說有些用戶有很有創意的使用 Maps.me 的方法:除了加店名,還用 $ 符號的數量表示該店家的價位區間,$$$$ 表示貴,而 $ 是便宜。不得不說選餐廳時這價位區間是重要資訊,但到底在 OSM 要怎麼標示。他提到未來改版會加入增加道路名稱的功能,讓 Maps.me 廣大的使用群眾,貢獻最在地也最基本的資訊,那就是用戶活動地區的道路名稱,聽他說我覺得這很重要。

Eugene talk from Mapbox

期待下次在尼泊爾舉行的大會

尼伯爾的Nama博士說他被念煩了,一直被人詢問,或是被邀請談論尼泊爾地震的急難繪圖經驗,該來辦個活動完整記錄這事情,免得過個幾年記憶模糊,細節沒記下來。另外就是很多當時的要角沒辦法輕易出國談那次經驗。下一年 2017 年,State of the Map Asia 大會,有極高可能在尼泊爾舉行,大家可以來參加會議,然後去登喜馬拉雅山。

Nama talk

儘管只有2個小時的飛機,大多數台灣人不大會往南飛,而是選擇往前往文化上比較熟悉的日本。要不是這次主辦單位的邀請,我也不會來臺灣南方的鄰國菲律賓。除了會議上與其他參與者的交流,也當地風土民情有深刻體驗。很感謝主辦單位的安排,很高興能到菲律賓分享臺灣經驗。

Location: Xavierville III, Loyola Heights, Quezon City, District III, Quezon City, Metro Manila, 1108, 菲律賓

My Talk about Taiwan Related Localizated Tagging Scheme Proposed and the Experience of State of the Map Asia

Posted by Supaplex on 22 November 2016 in English (English)

It is rush decision for me to decide to go to Manila for attending State of the Map Asia. I saw there is a scholarship I could apply, so I want to talk about the situation of Taiwan community, and meet some OpenStreetMap-related company. I'm very glad I travel to the Philippine, meet some old friend like Wular, and meet the Mapbox data team in India.

Also I meet the famous Manning from the Philippine community. Mapbox team recently are relining Taiwan road network, using the new arrived Mapbox satellite image, and Strava GPS trace. I met these guys only online, finally I have a change to talk with them face-to-face, and thank them of their hard work. We discussed what is the situation in Taiwan, what we local community can do to help them.

Manning Opening

Here is my talk slide. Due to the limit time, I decrease the size of my slide and skip some event. In the following post here, I'll describe what I told during my presentation, and keep a written record.

My slide

What did Facebook effect Taiwan when using OSM data

I didn't describe well about the Facebook part, there are some people discuss of what Facebook actually do after my talk. I didn't make it about the two things Facebook do: 1 training AI to map; 2 using OSM-based map on landmark page.

Facebook landmark page

I think who is familiar with OSM and knows about OSM-related issue will learn about the first one. They knows about Facebook AI made a mistake which draw the road network again in the Egypt case, I will not write about it here due to the limit article here.

Facebook use OSM as base map on landmark page both in Japan and South Korea. The landmark data is on the hand of Facebook, and mostly are Facebook users submitted. The switch made a big wind in Taiwan. One reason is not every alley in the effect area is mapped, some people saw the not well mapped map feel it is not a good one. The other reason is most people don't know that the location of landmark is user-submitted. If one person mark the wrong location, then the data on Face will be wrong. One see the wrong landmark information and the not so detailed basemap. OSM is blamed for the wrong doing, but it's not the issue of OSM. The wrong location of landmark is an issue of Facebook.

The most exaggerated example is someone report his landmark location is wrong, and also blame the alley around his store is missed. And his usage of language is not very polite. When the user submitted response by the note report system direct from Facebook, small and serious complain rush in. Some are OSM problems, and some are Facebook problems, like the landmark location is wrong. There response including the one not so polite, did not know the response is public available, will be on the internet permanently.

Complain from Facebook user

Finally Facebook was annoyed, didn't have enough manpower to handle the complains they should handle. The basemap of Taiwan landmark pages switch to Here map, and terminate the issue for OpenStreetMap Taiwan community.

The multi-language proposed from a Chinese language user from Taiwanese

It is said that OSM could make multi-language map possible, handling the different needs of different language users need. Despite the name field for common name used by the local, we see the name filed of name:en, name:de, name:ja, name:fr, name:zh for different corresponding language name, using the alpha-2 code of ISO 639-1 name code suffix.

Although there is a possibility for multi-language name tagging on OSM, the scheme standard should be discussed first. In the current OSM tagging scheme, the use of name:zh for Chinese language is not enough, not covering the people using Traditional and Simplified Chinese. There should be tagging scheme for Traditional Chinese and Simplified Chinese correspondingly.

And there is a big problems, for the area using Chinese like China and Taiwan, which one Chinese is Chinese, could use the name:zh field, the Chinese used in Taiwan, or the Chinese used in China? Which one Chinese is Chinese?

So the OpenStreetMap Taiwan community member Rex draw up the language name tag according to IETF language tag (BCP 47). The draft including the area using Chinese, like Taiwan, China, Hong Kong, and Macau.

Chinese name tag proposed

For Taiwan and China, using Traditional and Simplified Chinese separately, using the corresponded Chinese in name:zh field is not a problem. But for area outside these Chinese using area, the Chinese name of some place are totally different, not just the different of Traditional and Simplified Chinese characters. For example Mt. Everest, the name in Taiwan Chinese is 聖母峰(Shengmu Feng, literally means Holy Mother Peak), the name in China Chinese is 珠穆朗玛峰(Chomolungma).

It seems that Mr. Everest is far away for the Filipinos, the response was not strong during my talk. I should use the well known Filipino names or tourist attraction, like Mindanao or Bohol. These two places name in Taiwan and China Chinese:

  • English Taiwan Traditional Chinese China Simplified Chinese
  • Mindanao 民答那峨 棉兰老
  • Bohol 薄荷 保和

This shows that despite the different character set of Taiwan and China, there is also different in customs translating terms, will effect the OSM localization and user experience.

Despite the Chinese name scheme, the draft will also deal with the name scheme of Formosa Language used Taiwan Aboriginal, which belongs to Austronesian language family. When OSM spreed in Taiwan, there was discussion about the Taiwan Aboriginal language prefix, also including in the draft.

Tagging for the Formosan language of Taiwan Aborigines

In the long term for the OpenStreetMap Taiwan community, we wish the developer using OSM data could progressively adapt the name scheme dealing with the different Chinese use case. And finally it could fix the different Chinese character and terms issues. Bringing more customized and localized user experience for different users. When the OpenStreetMap Taiwan community finalize the draft into a standard scheme, we might notify map app developer who use OSM data, wish them adapt for the scheme.

The tagging of place of worship is totally different from Europe and America mainstream religion

For the religion tag use now, there are different tag use for Buddhism, Christian, Cathedral, Taoism, and Muslim. But the religion tags do not represent Taiwan religion and folklore religion very well. The standard makes confusing. There are very temple in Taiwan are mainly focus on historical figures, so distinguish they belong to different religion do not make sense at all. It should focus more on which deity the place is worshiped.

When I was young I learned that using the last word of a temple to distinguish the temple is a Buddhism or Taoism place, the xx 宮 is a Taoism temple, and the xx寺 is a Buddhism temple. I used this standard to tag temple for awhile. But studying the religious issue in Taiwan, I found out that is not very precisely. It is more accurate and making sense to distinguish by the main deity in the place of worship worshiped.

Taiwan traditional religion tagging

So Rex proposed the draft for the traditional Taiwan forklore religion scheme. By proposing a new draft standard for the face of multivariate Taiwan religion and denomination, we could fix the issue we talk about, and fix the different and disorder standard use currently in OSM. Despite we should distinguish by the main deity in the temple, we should independently draft a new Taiwan traditional folklore religion tag. We have an example to explain below:

Traditional Han people religion:

  • religion=folk
  • denomination=TaiwaneseFolkReligion

For non-Han people religion, like Siraya people Aritt's Kuwa:

  • religion=folk
  • denomination=SirayaFolkReligion

The temple tagging example:

Tzihua Temple (should be tag according to the operating mode of the temple) * religion=folk * denomination=TaiwaneseFolkReligion * dedication:principal=瑤池金母 * dedication:principal:wikidata=Q1064059

Another tagging problem

There are another problem like the iD interface for address field, will be fix when the release of iD 2.0. When the iD was release, the address field is in English address mode, not suitable for Chinese address.

I mentioned Mapbox team relining Taiwan road network according to the data of Strava GPS trace and the new Mapbox Satellite image. I talked with the Mapbox team very deeply. We met first on the online platform, discussing about how to handle Taiwan road network. It was a very unique experience for me to meet the web pal on line, just like meet someone face-to-face I know online for the first time.

Mapbox works

I also had a chance to meet Maps.me CEO Eugene, and exchange view about OSM. When his talk, he mentioned OSM needs light contributor, to bring more local information like stores. So there is a need for an App that could add information very easy. I told him there was very unique way from a Maps.me user: despite adding store name, he also added $ symbol for the price range, $$$$ for very expensive, and $ for very cheap. I have to say that the price range is very important information, but how to handle in OSM database is a problem.

Eugene talk from Mapbox

Eugene said in the future release of Maps.me app, they will add a function to edit the road name. It is a very important information for the local and big crowd of Maps.me user, and they can add the basic and fundamental information. I agree with his point about the importance of adding road name.

Looking forward for the conference in Nepal

Nama said he was annoyed by everyone ask him about the Nepal earthquake experience. He kept invite to talk about the crisis mapping in Nepal earthquake, even this time of State of the Map Asia. It is time to record the experience by a conference in Nepal, otherwise it will be forgotten. Another factor is many important figures could make it very easy to talk about the experience aboard. The next year 2017, there is a high possible of State of the Map Asia hold in Nepal. Nama said he will invite everybody for the conference, and could arrange climbing Himalaya mountain.

Nama talk

Although it is just a 2 hours flight, most Taiwanese won't head south. Most Taiwanese will choose to flight North to more familiar Japan. If the conference organizer not invite me this time, I would not travel south to the neighborhood country the Philippine. Despite the experience to talk with other attendees, I also had a deep experience of the local Philippine culture. I'm very appricate of the arrangement from the organizers, and very happy to share my experience of Taiwan community.

Location: Xavierville III, Loyola Heights, Quezon City Circle, District III, Quezon City, Metro Manila, 1108, Philippines

OSMAnd+問題

Posted by Supaplex on 22 August 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

OSMAnd+ 2.4.3版,要新增node時,存檔花得時間比以前九,害我還等等一會兒才能從探察的現場離開。

新手第一筆編輯

Posted by Supaplex on 15 August 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

最近很多熱心的參與者加入開放街圖計畫,但是一開始當然沒辦法到完美的地步,需要好好看他們加了什麼上去。看日記別人談到新手狀況監控時,談到他一定會打開編輯畫面來看,很多東西從地圖rendering狀況看不出來異狀,但一打開畫面就會哇一聲。

先前我有開Achavi來比對,但只會看到新增的部分,無法評估跟既有資料的整合狀況。看來我要學那位圖客的作法,打開編輯畫面好好看加上去的原始資料狀況。也許無法每一筆都看,從第一筆看,如有問題馬上回應,才不會帶著不好的習慣一直編下去。到了那時候要修就累了。

歡迎新手訊息的難處

Posted by Supaplex on 13 August 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

在日記看到這一篇,提到荷蘭社群放棄向新用戶寄新手歡迎訊息。臺灣也有類似的新手歡迎計畫,也將面臨類似的低回應率,以及不大會有後續編輯的問題。

也許解決的方式得從OpenStreetMap網站改起,要方便一些用戶能夠一次大量寄發訊息給其他人,但這也會帶來大量spam問題。或者要把Forum、OpenStreetMap Forum整合進主網站,但這得有人力處理單一登入問題,是大工程。

圓山水神社探察

Posted by Supaplex on 30 July 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

圓山水神社一帶真的有草地!原來的蓄水池現在變草地了,水神社參拜道前的確是草地。看來愛台玩至少在水神社,不完全是map for rendering。

Location: 大直, 永安里, 竹子林, 中山區, 臺北市, 臺灣

20160620踏查-下內埔營舍遺址

Posted by Supaplex on 20 June 2016 in Chinese (Taiwan) (‪中文(台灣)‬)

晚上去臺大後門118巷,以及下內埔營舍遺址踏查。

遍尋不著下內埔營舍遺址在那,不過在工地東側的停車場有看到幾棵被包起來的大樹。大概是以前的營地範圍,簡單弄一弄變成社區停車場。猜測下內埔營舍剩下的門柱應該在那一帶,工地東側的入口附近。

和平國小工地不只有國小,還有臺北籃球館。隨著少子化的狀況,和平國小是否開闢變數很大,說不定變運動設施用地了。

118巷有一些標示英文名稱的店家,順道探查看中文名稱。

Location: 古亭, 頂東里, 嘉禾新村, 中正區, 臺北市, 臺灣

承天禪寺

Posted by Supaplex on 6 September 2015 in Chinese (Taiwan) (‪中文(台灣)‬)

坐805到永寧,走到山上承天禪寺,走其中一條賞螢步道,下來是走清溪步道,延石壁寮溪旁步道下來。在南天母廣場坐F606公車下山。

香客大樓該怎麼標示呢?

Posted by Supaplex on 23 August 2015 in Chinese (Taiwan) (‪中文(台灣)‬)

常有大型的廟宇附設提供住宿的香客大樓,來讓進香團住宿。但轉換到,記得在臺北的OSM Meetup曾討論過這一個問題,當時我說香客大樓是共宿方式,類似青年旅舍,提議比照tourism=hostel來標示。

香客大樓

你覺得該如何標示呢?是否贊同我的說法?

Location: 竹林路, 菁湖里, 粉寮, 林口區, 新北市, 24445, 臺灣

恐怖的中和POI密度

Posted by Supaplex on 23 August 2015 in Chinese (Taiwan) (‪中文(台灣)‬)

2015中和POI

OSM Wiki連結

必須說感謝twister88564!讚嘆twister88564!連地址也標注上去了。

Location: 南勢角, 景新里, 中和區, 新北市, 臺灣

3D建築範例-印度蘇丹Mysore Palace皇宮

Posted by Supaplex on 23 August 2015 in Chinese (Taiwan) (‪中文(台灣)‬)

在OSM日記看到Chetan_Gowda寫的SImply 3D Buildings一文,用Mysore Palace當作範例示範單純用標籤描述3D建築樣式,用F4Map地圖展示的樣子 OSM 物件,可以打開地圖資料看是怎麼標示的)。

F4地圖 漂亮的3D建築(Flickr連結)

開放街圖 開放街圖上的資料(Flckr連結)

開放街圖詳細資料 開放街圖上詳細的資料,可以看到3D地圖的塔樓部分怎麼繪製出來的。(Flickr連結)

building part標籤 Flickr連結

OSM Buildings 在其他3D地圖的樣子-OSM Buildings(Flickr連結)

想到臺灣的總統府,塔樓的部分需要重新繪製,用building:part=yes單獨繪出塔樓的部分。

OSM Buildings總統府 Flickr連結

Location: Vani Vilas, Mysuru, Mysuru taluk, Mysuru district, Karnataka, 570001, 印度

2015北大特區的大進擊

Posted by Supaplex on 23 August 2015 in Chinese (Taiwan) (‪中文(台灣)‬)

jiazheng新增北大特區興趣點,並且用相片記錄他的踏查過程,全部都能在Flickr上看到。而且還有門牌號碼、郵遞區號(3+2),太厲害了!

北大特區POI (OSM Wiki連結)

Location: 北大特區, 南園里, 樹林區, 新北市, 臺灣

近期工作項目(20140318)

Posted by Supaplex on 18 March 2014 in Chinese (Taiwan) (‪中文(台灣)‬)

公車

  • 9003
  • 202
  • 298

線上計畫

  • 基隆改善計畫
  • 基隆公車整理
  • 原住民地名標注
  • OSM Vs 其他地圖
  • 建構需要完成任務清單

大活動

  • 規畫維基百科+開放街圖活動
  • 原住民部落-溪洲部落

20131021-GPS軌跡

Posted by Supaplex on 21 October 2013 in Chinese (Taiwan) (‪中文(台灣)‬)
  • 綠5:碧潭-耕莘醫院,記載站名
  • 909:民族路-市立體育場,記載站名
Location: 新店區, 中興里, 檳榔坑, 新店區, 新北市, 231, 臺灣

20131019 GPS軌跡-坪林

Posted by Supaplex on 21 October 2013 in Chinese (Taiwan) (‪中文(台灣)‬)

這天前去坪林快閃半日遊

總共記下軌跡如下:

  1. 綠12:新店轉運站-坪林站,包括公車站牌位置、名稱
  2. 坪林街道、新北市新巴士F722金瓜寮線來回
  3. 坪林老街、觀音台步道、水柳腳步道入口、保坪宮、水楖腳步道另一入口
  4. 923:坪林站-捷運新店站,包括公車站牌位置、名稱

下次去坪林,可以去南山寺、漁光國小一線,或者在坐F722去金瓜寮溪沿線走走。走老街旁的水柳腳步道,看看以前日本人運兵的保甲路。

Location: 觀音台, 坪林里, 苦嶺腳, 坪林區, 新北市, 232, 臺灣

臺灣巷弄的tagging

Posted by Supaplex on 19 May 2013 in Chinese (Taiwan) (‪中文(台灣)‬)

前幾天跟Irvin談臺灣的巷弄要怎麼tag,討論出來後,由Irvin整理後寫在Taiwan tagging

這邊有範例,拿道路畫得最詳細的臺南地區,來看圖片吧 Tainan Alley

用行動裝置加沿途的POI

Posted by Supaplex on 6 March 2013 in Chinese (Taiwan) (‪中文(台灣)‬)

今天晚上與Shangkuanlc約一起吃晚餐,在龍安街與興安街交叉口的青島餃子店吃餃子。吃完後來map附近一帶的地理特徵。餃子店不遠處是台北大學的合江街校區,被合江街分成東、西兩塊,其中東校區與台大用教育部大樓的土地交換,解決長期教育部佔用台大校地的問題。兩塊校地上的建築挺舊的,由於科系關係,這邊都是講台教室型的教學大樓。

我與Shangkuanlc看到有老婦人帶狗進校園,一眼附近社區民眾的樣子,就逕自進入校園。由於合江街校地位處市區,晚上不少學分班還有在職進修課程正在上課。校區裡建築看起來很舊,遮天的樹蔭顯示這些樹也有一定年紀。Shangkuanlc拿著平板用Go Map!!圈出合江街校區出來,竟然先前還沒有人畫這裡。我們來這裡,某種程度也算是為學校巡視未來的校地XDD。西校區中間是停車位,在西側的門旁邊有蔣公銅像。

逛完台北大學,沿著合江街,記錄附近的商家。從校門出來就有好多影印店,當然餐廳也不少。我與上官分別用手機以及平板記錄商家資訊。最令人吃驚的是,台北大學旁邊有北科大的宿舍。猜想是以前台北大學的,現在都遷至三峽,留在台北的宿舍沒急著拆,就給臨近的北科大拿來用。

合江街校區北邊的影印店

用Android手機的OSMAnd,加POI的速度沒那麼快,軟體主要是拿來導航為主,加POI功能藏很裡面,花點時間熟悉才會知道。相反的Shangkuanlc平板中的Go Map!!軟體,則是專為編輯功能而設計的軟體,邊探察邊編輯,操作界面直覺易上手,很不錯,值得推薦。

之後我與Shangkuanlc會好好寫使用教學,預計最快在中和四號公園的Mapping Party就會用到了。

Location: 大稻埕, 延平里, 延平, 大同區, 臺北市, 臺灣

今日成就-臺北捷運雙軌化

Posted by Supaplex on 5 December 2012 in Chinese (Taiwan) (‪中文(台灣)‬)

*淡水至關渡

*動物園至忠孝復興

*北門、西門、中正紀念堂、古亭麻花隧道

Location: 西門町, 萬壽里, 龍山, 萬華區, 臺北市, 臺灣

NTU Mapping Party

Posted by Supaplex on 19 November 2012 in Chinese (Taiwan) (‪中文(台灣)‬)

2012-11-18主辦NTU Mapping Party

成果如下:

我依空照圖畫的建築物 空照圖

上官的翻譯計畫 翻譯

Location: 古亭, 頂東里, 嘉禾新村, 中正區, 臺北市, 臺灣
Older Entries | Newer Entries