Jump to content

Any Ios Developers...?


Recommended Posts

Posted

bhayya...

nenu big data developer ni..I have some basic questions on ios...attending an interview and they are asking me some basic ios questions....

like how lattitutde and longitudes get loaded into Database....

can some one please help me to get these answers.....

many many thanks..!!

Posted

[url="http://stackoverflow.com/questions/1370170/database-sql-how-to-store-longitude-latitude-data"]http://stackoverflow.com/questions/1370170/database-sql-how-to-store-longitude-latitude-data[/url]

Posted

latitude / longitude data kosam normal ga third-party providers untaru like MaxMind.. konta mandi GPL license kinda open-source chestaru.. others who have more accurate and updated information charge for the same..

maverickpuli vesina link lo explain chesinattu database lo store chestaru.. normal ga ee third-party vendors deggara nundi either direct feed via API or lat/long files vastayi which can be ETLed into our required table structure..

iOS lo lat/long collect cheyadaniki naaku telisi chaala methods untayi.. one of the methods is to use CLLocationManager class and try to get the data like that and compare it with the database you have..

hope this helps!

Posted

[quote name='Pinky123' timestamp='1373414131' post='1303936393']
latitude / longitude data kosam normal ga third-party providers untaru like MaxMind.. konta mandi GPL license kinda open-source chestaru.. others who have more accurate and updated information charge for the same..

maverickpuli vesina link lo explain chesinattu database lo store chestaru.. normal ga ee third-party vendors deggara nundi either direct feed via API or lat/long files vastayi which can be ETLed into our required table structure..

[color=#ff0000]iOS lo lat/long collect cheyadaniki naaku telisi chaala methods untayi.. one of the methods is to use CLLocationManager class and try to get the data like that and compare it with the database you have..[/color]

hope this helps!
[/quote]

many thanks pinky for your help.....

This what my general observation as a iphone consumer and as a ETL developer...could you please put this in more technical terms.

Step 1: When you enable location services in your iPHone, your ios process keeps storing your GPS information every time. I dont know, how frequently it refreshes that data to update your current GPS location.

Step 2: There should be an iOS API call from my iPhone application to my iphone application (lets say Amazon).

Step 3: from your iphone application there would be WEB API call / web service program to calls many function calls...

Step 4: these function calls writes to the Database.

Could you please please put this in more technical way..? Does my assumption is correct ..??
Your help would be very much Appreciated...!!

Thanks Maveric bhayya...but I am not looking for how to query or use latitude and longitude.... more interested how data would be loaded from iphone to the Database...

Posted

[quote name='TheLeader' timestamp='1373416378' post='1303936468']

many thanks pinky for your help.....

This what my general observation as a iphone consumer and as a ETL developer...could you please put this in more technical terms.

Step 1: When you enable location services in your iPHone, your ios process keeps storing your GPS information every time. I dont know, how frequently it refreshes that data to update your current GPS location.

Step 2: There should be an iOS API call from my iPhone application to my iphone application (lets say Amazon).

Step 3: from your iphone application there would be WEB API call / web service program to calls many function calls...

Step 4: these function calls writes to the Database.

Could you please please put this in more technical way..? Does my assumption is correct ..??
Your help would be very much Appreciated...!!

Thanks Maveric bhayya...but I am not looking for how to query or use latitude and longitude.... more interested how data would be loaded from iphone to the Database...
[/quote]

naaku mari ekkuva teliyadu, kani based on what I know I will tell you my observations:

When using LBS (Location Based Services) on iPhone, you basically make use of iOS core location framework which uses either "Standard Location Services" or "Significant-Change Location Services". The latter is available on iOS4+ models.

iOS basically uses a three-step process to determine the current location in a descending order of priority(if this feature is turned on, as you mentioned above):

1. Assistd GPS
2. Free Wi-Fi around you (if wi-fi radio is turned on but not necessarily connected to a wi-fi network)
3. Cellular network

Once an app gets the location initially, the app developer can decide on how frequently the location needs to be updated. Since LBS is a power-intensive operation, it is advisable not to do so very frequently. You can also configure the accuracy and the distance to be traveled before acquiring a new location.

Once the location is locked, the core framework passes the latitude and longitude along with a timestamp on when the location was acquired to the application. So, when updating the location it is important to look at the timestamp as well to ensure a cached result is not being returned.

Once you have the location coordinates, you need to make a call to you app's Web API and pass these coordinates. Once your app's webservices have the information, it depends on how you want to use that information.

  • Upvote 1
Posted

[quote name='Pinky123' timestamp='1373417658' post='1303936502']

naaku mari ekkuva teliyadu, kani based on what I know I will tell you my observations:

When using LBS (Location Based Services) on iPhone, you basically make use of iOS core location framework which uses either "Standard Location Services" or "Significant-Change Location Services". The latter is available on iOS4+ models.

iOS basically uses a three-step process to determine the current location in a descending order of priority(if this feature is turned on, as you mentioned above):

1. Assistd GPS
2. Free Wi-Fi around you (if wi-fi radio is turned on but not necessarily connected to a wi-fi network)
3. Cellular network

Once an app gets the location initially, the app developer can decide on how frequently the location needs to be updated. Since LBS is a power-intensive operation, it is advisable not to do so very frequently. You can also configure the accuracy and the distance to be traveled before acquiring a new location.

Once the location is locked, the core framework passes the latitude and longitude along with a timestamp on when the location was acquired to the application. So, when updating the location it is important to look at the timestamp as well to ensure a cached result is not being returned.

Once you have the location coordinates, you need to make a call to you app's Web API and pass these coordinates. Once your app's webservices have the information, it depends on how you want to use that information.
[/quote]
naki subject edo interesting ga anpistondi...gps ela work ayiddo i know kani sw lo coordinates ela vastayo donno

Posted

[quote name='Pinky123' timestamp='1373417658' post='1303936502']

naaku mari ekkuva teliyadu, kani based on what I know I will tell you my observations:

When using LBS (Location Based Services) on iPhone, you basically make use of iOS core location framework which uses either "Standard Location Services" or "Significant-Change Location Services". The latter is available on iOS4+ models.

iOS basically uses a three-step process to determine the current location in a descending order of priority(if this feature is turned on, as you mentioned above):

1. Assistd GPS
2. Free Wi-Fi around you (if wi-fi radio is turned on but not necessarily connected to a wi-fi network)
3. Cellular network

Once an app gets the location initially, the app developer can decide on how frequently the location needs to be updated. Since LBS is a power-intensive operation, it is advisable not to do so very frequently. You can also configure the accuracy and the distance to be traveled before acquiring a new location.

Once the location is locked, the core framework passes the latitude and longitude along with a timestamp on when the location was acquired to the application. So, when updating the location it is important to look at the timestamp as well to ensure a cached result is not being returned.

Once you have the location coordinates, you need to make a call to you app's Web API and pass these coordinates. Once your app's webservices have the information, it depends on how you want to use that information.
[/quote]

you are awesome Pinky..!!! So knowledgeable..!!

  • Upvote 1
Posted

In your Application use CLLocationManager to let your class know when the user is moving or have a timer to check users current Lat and Long with certain accuracy (battery drainage is directly proportional to accuracy desired). When the CLLocationManager object calls the callback method/function you may choose to asynchronously send it to webserver or for the sake of minimizing network calls save all these Lat and Long to Core Data/SQLite/Plist and send them to webserver once everyday.

Posted

[quote name='Pinky123' timestamp='1373417658' post='1303936502']

naaku mari ekkuva teliyadu, kani based on what I know I will tell you my observations:

When using LBS (Location Based Services) on iPhone, you basically make use of iOS core location framework which uses either "Standard Location Services" or "Significant-Change Location Services". The latter is available on iOS4+ models.

iOS basically uses a three-step process to determine the current location in a descending order of priority(if this feature is turned on, as you mentioned above):

1. Assistd GPS
2. Free Wi-Fi around you (if wi-fi radio is turned on but not necessarily connected to a wi-fi network)
3. Cellular network

Once an app gets the location initially, the app developer can decide on how frequently the location needs to be updated. Since LBS is a power-intensive operation, it is advisable not to do so very frequently. You can also configure the accuracy and the distance to be traveled before acquiring a new location.

Once the location is locked, the core framework passes the latitude and longitude along with a timestamp on when the location was acquired to the application. So, when updating the location it is important to look at the timestamp as well to ensure a cached result is not being returned.

Once you have the location coordinates, you need to make a call to you app's Web API and pass these coordinates. Once your app's webservices have the information, it depends on how you want to use that information.
[/quote]
:3D_Smiles:

Posted

[quote name='pichuka' timestamp='1373429267' post='1303937051']
In your Application use CLLocationManager to let your class know when the user is moving or have a timer to check users current Lat and Long with certain accuracy (battery drainage is directly proportional to accuracy desired). When the CLLocationManager object calls the callback method/function you may choose to asynchronously send it to webserver or for the sake of minimizing network calls save all these Lat and Long to Core Data/SQLite/Plist and send them to webserver once everyday.
[/quote]


AWESOME...bhayya...you rock..!!

Posted

[quote name='TheLeader' timestamp='1373481906' post='1303938989']


AWESOME...bhayya... you rock..!!
[/quote]

Thanks.

Posted
:3D_Smiles_216: [img]http://www.sherv.net/cm/emoticons/birds/cute-blue-bird-crying-smiley-emoticon.gif[/img] [img]http://www.sherv.net/cm/emo/sad/crybaby.gif[/img]
×
×
  • Create New...