About Map API

[jyeok]

According to our design and implmentation wiki, We are to use django-location-field and KaKao Map API.

But django-location-field seems to not supporting the KaKaoMap but Google Map. So if we are to use django-location-field , I think we have to change our location/search provider to Google Map.

I Think Google Map is better since our service is based on English except the name of menu and Our Sign in with SNS will support Google Login. What you guys think about it?

[ByungHeeCha]

I wonder what does google map support for google users.

[ByungHeeCha]

I think it will be easier using google map api then kakao api. However, I think google map doesn't have much information than kakao map in Korea.

[jyeok]

Although we don’t use particular feature of google maps, user will feel awkward if our service supports many google-based features (log-in with google, google calender, uploading picture via google image/drive etc..) but uses KaKao Map for only map feature. Because we are not going to use special features which kakomap api provides, I think it is matter of inconsistency.

[ByungHeeCha]

I agree with you. I think we have to find more google-based feature for our users.

[jyeok]

FYI when typing ‘우참순’ to each Map service, Google map automatically redirects to ‘우리가참순대’ but Kakao Map gives no results. Also, google map has far more data that seems useful. When we type ‘박막례청진동해장국’, google map shows 347 reviews and ‘relevant location’, while kakao map shows shows only 15 reviews with ‘daum blog review’. Maybe no need to worrying about lack of location / information using google map

[ByungHeeCha]

Hmm... well google map was better than I thought!

[tho-kn]

as we're to integrate google service in many of our services, using google map api would help our development too imo

[jyeok]

It seems cofirmed that we are going to use Google Map API instaed of KaKao Map, So I'll close this issue.