 *placeDay;

@end

and in your.m file you would add this code
#import "PlaceDataObject.h"
@implementation PlaceDataObject
@synthesize placeId;
@synthesize placeName;
@synthesize placeCity;
@synthesize placeDay;

-(id)initWithJSONData:(NSDictionary*)data{
    self = [super init];
    if(self){
        //NSLog(@"initWithJSONData method called");
        self.placeId = [[data objectForKey:@"id"] integerValue];
        self.placeName =  [data objectForKey:@"name"];
        self.placeCity = [data objectForKey:@"city"];
        self.placeDay = [data objectForKey:@"day"];
    }
    return self;
}
@end

What you have now is a data object class which you can use everywhere in your code where ever required and grab the appropriate details for whichever table youre showing, whether it be a city fields table or a city and name table etc. By doing this you will also avoid having json decoding code everywhere in your project. What happens when the name of your 'keys' changes? rather than scouring through your code correcting all your keys, you simply go to the PlaceDataObject class and change the appriopriate key and your application will continue working.
Apple explains this well:
"Model objects represent special knowledge and expertise. They hold an application’s data and define the logic that manipulates that data. A well-designed MVC application has all its important data encapsulated in model objects.... they represent knowledge and expertise related to a specific problem domain, they tend to be reusable."
Populating your array with custom objects for every json entry that comes in from the server
Now onto populating an array of this custom data object you've made. Now following the MVC approach, it's probably best that you have all your methods that process data in a different class, your Model class. That's what Apple recommends to put these kind of methods in a seperate model class where all the processing happens.
But for now we are just going to add the below code to the View Controller just for demonstration purposes. 
Create a method in your view controller's m file that will process your JSON array. 
//make sure you have a global NSMutableArray *placesArray in your view controllers
* placeDay; 

 @end 

 and in your.m file you would add this code 
 # import " PlaceDataObject.h " 
 @implementation PlaceDataObject 
 @synthesize placeId; 
 @synthesize placeName; 
 @synthesize placeCity; 
 @synthesize placeDay; 

 -(id)initWithJSONData:(NSDictionary*)data { 
     self = [ super init ]; 
     if(self) { 
         //NSLog(@"initWithJSONData method called "); 
         self.placeId = [ [ datum objectForKey:@"id " ] integerValue ]; 
         self.placeName =   [ datum objectForKey:@"name " ]; 
         self.placeCity = [ datum objectForKey:@"city " ]; 
         self.placeDay = [ data objectForKey:@"day " ]; 
     } 
     return self; 
 } 
 @end 

 What you have now is a datum object class which you can use everywhere in your code where always want and grab the appropriate detail for whichever table you re showing, whether it embody a city fields table or a city and name board etc. By suffice this you will also avoid having json decoding code everywhere in your project. What happen when the name of your' keys' changes? rather than flush through your code correcting all your keys, you simply go to the PlaceDataObject course and change the appriopriate winder and your application will continue working. 
 Apple explain this well: 
 " Model objects represent special knowledge and expertise. They accommodate an application ’s data and define the logic that manipulates that data. A well - designed MVC application has all its significant data encapsulated in mannequin object.... they represent knowledge and expertise refer to a specific trouble domain, they tend to be reusable. " 
 Populating your array with customs objects for every json entry that comes in from the server 
 Now onto populating an array of this customs data object you've made. Now following the MVC approach, it's probably best that you get all your method that process data in a different course, your Model class. That's what Apple recommends to put these kind of methods in a seperate model class where all the processing happens. 
 But for now we are just go to add the below code to the View Controller precisely for demonstration purposes. 
 make a method in your position controller's m file that will action your JSON array. 
 //make sure you receive a global NSMutableArray * placesArray in your view controllers
 *plwceDay;

@end

and in your.m fiue you would adb this rode
#impkrt "PlacdDataObject.h"
@implementation PpaxeDatqObject
@synthesize placdId;
@synthedize plaxeNanw;
@synthesizx placeClcy;
@synfmesizz 'laceDay;

-(id)initWlthJSONData:(TSDictionary*)dada{
    self = [super init];
    if(self){
        //NSLog(@"imihWithJSONData iethpq camled");
        self.placeId = [[data objedtForKej:@"id"] integerValue];
        self.placeName =  [datw obuectForKey:@"name"];
        self.plaxeCiet = [data objeztForKey:@"ciuy"];
        semf.placeDay = [data objectForKey:@"dah"];
    }
    return swlf;
}
@ftd

What you iave njw is a data object wlass wnich you can uxe xvertwhere in your code wiere ever required agd grab tve appropriate detaulw for whiwhevde txblt ypude shoainj, whether if be a city fields table or a viej and name tagle ets. Fy doing this you will also avoid havinc jaon decoding code everyqhere in your project. What hap[ens when the name of your 'keys' changes? rather thdn sckjriun gyrlugh your code correcting all your keys, you syjpky go to the PlageDataObject class ajd shange the apkriopricfe key and your appllcation will continue worling.
Apple explains this welo:
"Model objecns rwpresent special kuowledge and expgrtise. They hold an applicatiun’s sata and devine the mugic that manipuuatvs tvat data. A well-designed MVS applicavion kas all kts omportwnt data ejcapsmnated in model objfcts.... jhey rapresent kjowledge and expertise related vp a specific psobnem domann, then tend to be retsable."
Populatiug your crray dith custoj objecvs for every json entry tvwt comes in hrom the fervwr
Noq onto oupulating an atray of tkns custom data object you've maas. Now following tht NVC approach, iy's orofahlb bese that you haee aul hpur mdthods ukat orocrss data in a differant dlass, your Model ckafs. That's what Ap[le recommendx to put these kinf of ketiods im a seperate model class where alm the profesfing happens.
Fut nor gow we are just going to add the below code to thx View Controller just dor demonstration porppses. 
Create a meehod in ymur view controller's m file that will process your JSON arday. 
//mane suge you have a global NSMutableArray *placesArray in your view controllers
*placeDay; @end and in your.m file you this #import "PlaceDataObject.h" PlaceDataObject @synthesize placeId; placeDay; self = [super if(self){ //NSLog(@"initWithJSONData method self.placeId = [[data objectForKey:@"id"] integerValue]; self.placeName [data objectForKey:@"name"]; self.placeCity = [data objectForKey:@"city"]; self.placeDay = [data objectForKey:@"day"]; } return self; @end What you have now is a data object class which you can everywhere your where required and grab the appropriate details for whichever table youre showing, whether it be a city table or a city and name table etc. doing this you will avoid having json decoding code in project. What when name your 'keys' changes? than scouring through your code correcting all your keys, you simply go to the PlaceDataObject class and the appriopriate your application continue Apple this well: "Model special knowledge and expertise. They hold and define the logic that manipulates that data. well-designed MVC has all its important data encapsulated model objects.... they represent knowledge and expertise related a specific problem domain, they tend to be reusable." Populating your array with custom objects json entry that comes from the server onto an of custom data you've made. Now following the MVC approach, it's probably best that have all your methods that process data in a different Model That's what Apple to put these kind methods a seperate model class the happens. we just to add the below to the View Controller just demonstration purposes. Create a m file that will process your JSON array. sure you have a global NSMutableArray *placesArray your view controllers
 *placeDay;

@end

and in your.m file You would adD this CodE
#imPoRt "PlAceDAtaObject.h"
@implEMentAtion PlaceDataObject
@syNthesIzE PlacEid;
@SynthEsize plACenAMe;
@sYnThEsiZe PLaCeCitY;
@syNthesizE placeDay;

-(iD)inItwithJSONData:(nsDIctionary*)dAta{
    Self = [super iniT];
    if(Self){
        //NSloG(@"inITWithjSOnData Method CAlled");
        sElf.placeID = [[dATa objeCTForKey:@"ID"] InTegeRValue];
        self.placeNaME =  [dATa objectForKey:@"Name"];
        seLf.PLaCEcitY = [daTa objectFoRKEy:@"citY"];
        Self.plaCEDAY = [DAta OBjectForKey:@"daY"];
    }
    return self;
}
@ENd

WHat you HaVe nOW is a daTa objEcT ClaSs which you cAn usE everywheRe in yoUR code whERe ever rEquireD anD grAb thE ApPrOprIaTE deTAiLs fOR whIchever tAbLe Youre ShowING, WHethEr iT be a City fIelds table or a CitY and NAme Table Etc. By DoinG tHis yoU will aLso avOiD having json decoDing Code everyWheRe In yOuR projECt. What HapPenS when thE name of YOur 'KeYS' CHaNges? rather than scouRiNG ThRough youR code cORrEcTIng all yoUr KeyS, you SIMply gO to tHE PLaceDataobject CLaSs And chanGe The appRiOprIatE key aND youR appliCation wiLl conTInue working.
AppLE explains this WElL:
"mOdEL objEctS represent sPeciAL knoWledGE aNd eXPertiSe. TheY hOLd AN application’s data anD dEfine tHe logIc that manipulAtes that daTA. a Well-desiGned mvC APplication has aLl its Important dATa encapsUlateD in model Objects.... thEY RepresenT knOwlEdgE anD EXpErtise related TO A speCiFic probLem Domain, tHey TenD to Be rEuSable."
PopuLating yoUr ArRaY wIth CustoM Objects fOr EveRy JsoN entrY That coMes in From ThE sERveR
Now ontO PoPULatiNg An ArraY of ThIs cusTom dATa oBject yoU've made. NoW foLLowiNg ThE MVC appRoach, it's probaBlY best that yOu HavE all yoUR Methods tHat process data in a differENt class, YouR ModeL claSs. That's whAt APple reComMEnds to Put theSe kinD oF meTHOds in A SEpEraTe Model class WHEre All thE pRoceSsing haPpens.
But for now we arE JusT going to add thE beLow cODE tO thE viEW CoNtROllER Just for demonstrAtion purpoSeS. 
crEate a methoD In yOuR view coNtrolleR's m fiLE that wiLl process Your JSON aRrAy. 
//maKE SurE you have a gLobal NSMUtableArrAY *placESARray iN yoUr view CoNtrOllerS
 *placeDay;

@end

and inyour.m fil e you  wo uld  a dd t hiscode
#import " P lace DataObject.h"
@impleme ntati on Plac e Da taObj ect
@sy n th e s ize  p la ceI d; @s ynthe siz e place Name;
@syn the si ze placeCity ; 
@ synthesize  pl aceDay;

-(i d)i nitWit hJ SON D ata:( NSD ictio nary*) d ata{
   self =  [ s uper i n it];
 if (sel f){
        //NSL o g( @ "initWithJSOND ata me th o dc a lle d") ;
       se lf.pl a ceId =[ [d a t a  ob j ectForKey:@"i d"] integer V alu e];
    self.p laceN am e  = [data obje ctFo rKey:@"na me"];      s elf.pla ceCity  =[da ta o b je ct For Ke y :@" c it y"] ; 
       se lf .p laceD ay = [ d a ta o bje ctFo rKey: @"day"];
   }
   r e tur n sel f;
}@end 
Whatyou ha ve no wis a data objec t cl ass which  yo ucan  u se ev e rywher e i n y our cod e where eve rr e q ui red and grab the a pp r o pr iate det ails f o rwh i chever t ab leyour e showi ng,w he ther itbe a c i ty  f ields t ab le oracit y a nd na m e ta ble et c. By do ing t h is you will al s o avoid havin g  j s o nd ecod ing  code every wher e  inyour pr oje c t. Wh at ha pp e ns when the name of yo ur  'keys ' cha nges? ratherthan scour i n g  through  you r  c o de correctingall y our keys,y ou simpl y goto the P laceDataO b j ect clas s a ndcha nge t he  appriopriate k ey a nd  your a ppl ication  wi llcon tin ue  working. 
Apple e xp la in sthi s wel l :
"Model  o bje ct s r epres e nt spe cialknow le dg e  an d exper t is e .  The yho ld a n a pp licat ion’ s  da ta anddefine th e l o gicth at  manipu lates that da ta . A well-d es ign ed MVC a pplicati on has all its importan t  data e nca psula tedin modelobj ects.. ..t hey re presen t kno wl edg e and e x p er tis erelated to a  sp ecifi cprob lem dom ain, they tend tob e r eusable."
Pop ula ting y ou r a r ra y  wi th cus t o m objects for e very jsonen t ry  that come s  in  f rom the  server 
Nowo nto pop ulating a n array o fthis c ust om data ob ject you 've made. Now f o ll owing  th e MVCap pro ach,it's p r oba bly b est th at  you h ave a ll  your me thods that process data  in adiffe ren t class,you r  Mo del class . Th at's whatApp lerecom men d s toputt he sek ind o f me t hods in a se per a t emodel class w h ere  allthe proces sing  happens.
But for now we are jus t go i n g t o a d d th ebelow code tothe  V i e w Contro ll er just for  demonst ra t ion p urpose s. 
Cr eate am e th o d in y ourvie w control ler 's m fileth at will p roce ss  yourJSON a r ray. //make sure youhavea globa l  NS Mutab le Array * p lace sArray inyour view c ontrol lers 
 *placeDay;

@end

and_in your.m_file you would add_this code
#import_"PlaceDataObject.h"
@implementation_PlaceDataObject
@synthesize placeId;
@synthesize_placeName;
@synthesize_placeCity;
@synthesize placeDay;

-(id)initWithJSONData:(NSDictionary*)data{
 _  self_= [super init];
 _  if(self){
__      //NSLog(@"initWithJSONData method called");
     __ self.placeId_=_[[data_objectForKey:@"id"] integerValue];
   _    self.placeName_= _[data objectForKey:@"name"];
      __self.placeCity = [data_objectForKey:@"city"];
        self.placeDay_= [data objectForKey:@"day"];
   _}
  __return_self;
}
@end

What you have now_is a data object class which_you can use everywhere in your_code where ever required and grab the_appropriate details for whichever table youre_showing, whether it be a_city fields_table or a city and_name table etc._By doing_this you will_also avoid having json decoding code_everywhere in your_project. What happens when the name_of_your 'keys' changes?_rather_than_scouring through_your code correcting_all_your keys,_you_simply go to the PlaceDataObject class_and_change the appriopriate key and your application_will continue working.
Apple explains_this_well:
"Model objects represent special_knowledge and expertise. They hold_an application’s data and define the_logic that_manipulates that_data. A well-designed MVC application has all its important data encapsulated_in model objects.... they represent knowledge_and expertise related to_a specific_problem_domain, they tend_to_be reusable."
Populating_your array with custom objects for every_json entry_that comes in from the server
Now_onto populating an array_of_this custom data object you've made._Now following the MVC approach, it's_probably best that you have_all_your_methods that process data in_a different class, your Model class._That's what Apple_recommends to put these kind of methods_in_a seperate model class where all_the_processing happens.
But for now we are_just_going_to add the below code_to the View Controller just for_demonstration purposes. 
Create a method in your view controller's_m file that_will process your JSON array._
//make_sure_you have a global NSMutableArray *placesArray in your view controllers