This will have three options, ‘create_zip_db’, ‘read_zip_db’ and ‘verbose’. The ‘doc’ attribute gives a brief description of each option. The ‘short’ attribute specifies any aliases that can be used for each option. The is ‘ro’ , means that the option value is immutable.<\/p>\n\n\n
\noption create_zip_db => (\n is => 'ro',\n short => 'new_zipdb|new_zip',\n doc => q\/Create a new NYC Zip, Borough, District, Town JSON file.\/,\n);\n\noption read_zip_db => (\n is => 'ro',\n short => 'read_db',\n doc => q\/Read the NYC Zip file database.\/,\n);\n\noption verbose => ( is => 'ro', doc => 'Print details' );\n<\/pre><\/div>\n\n\nThere are three Moo attributes. Some time in the future I can put these into a separate Moo <\/a>module.<\/p>\n\n\n\nhas db_dir => (\n is => 'rw',\n isa => Path,\n coerce => 1,\n default => sub { "$Bin\/..\/db" }\n);\n\nhas zip_db_json_file => (\n is => 'lazy',\n isa => Path,\n builder => sub {\n $_[0]->db_dir->child("zip_db.json");\n }\n);\n\nhas zip_hash => (\n is => 'lazy',\n isa =>\n sub { die "'zips_hash' must be a HASH" unless ( ref( $_[0] ) eq 'HASH' ) }\n ,\n builder => sub {\n deserialize_file $_[0]->zip_db_json_file;\n }\n);\n<\/pre><\/div>\n\n\nThe first attribute ‘db_dir’ specifies the future location of the JSON file. It uses Types::Path Tiny <\/a> to enforce this directory path as a Path::Tiny <\/a>object. The ‘zip_db_json_file’ is also a Types::Path::Tiny Path.<\/p>\nThe ‘zip_hash’ is the data structure what will store the NYC Zip code, borough, district, town information. The ‘isa’ for this attribute will ensure that it is a Perl hash. The ‘deserialize_file’ function comes from the CPAN module, File::Serialize<\/a> , which is very useful for dumping out Perl data structures to a JSON file, or in this case slurping in a JSON file to a Perl data structure. It also handles formats other than JSON.<\/p>\nNote that the ‘zip_hash’ attribute is ‘lazy’. I’m not saying that zip codes are particularly adverse to work. This is just Moo’s way of saying, “please don’t make me do anything until I really have to”. That way, resources are not nu-necessarily used creating a structure that isn’t being called for. <\/p>\n\n\n
\n# Main\nsub run {\n my ($self) = @_;\n $self->create_new_zipdb_file if $self->create_zip_db;\n $self->read_and_dump_the_db if $self->read_zip_db;\n say "All Done!" if $self->verbose;\n}\nmain->new_with_options()->run;\n<\/pre><\/div>\n\n\nMooX::Options<\/a> has it’s own particular style for creating a “Main” function that you won’t usually see in standard Perl scripts. It may be borrowed from brian d foy’s “Modulino”<\/a> concept. Anyway, the script is invoked by: <\/p>\n\n\n\nmain->new_with_options()->run;<\/pre>\n\n\n\nThe main ‘run’ function will call the methods as specified by the command line options.<\/p>\n
To run this script from the command line.<\/p>\n\n\n
\n# To get help\n\u03bb perl bin\\create_zipdb.pl -h\nUSAGE: create_zipdb.pl [-h] [long options ...]\n\n --create_zip_db Create a new NYC Zip, Borough, District, Town JSON\n file.\n --read_zip_db Read the NYC Zip file database.\n --verbose Print details\n\n --usage show a short help message\n -h show a compact help message\n --help show a long help message\n --man show the manual\n\n# Create a JSON file database\n\u03bb perl bin\\create_zipdb.pl --create_zip_db --v\n\n# Read the database and dump to the terminal\n\u03bb perl bin\\create_zipdb.pl --read_zip_db\n<\/pre><\/div>\n\n\nMost of the actual work of reading in the hard coded data structure and creating\/reading the JSON database file is done here:<\/p>\n\n\n
\nsub create_new_zipdb_file {\n my $self = shift;\n my $zip_boro_dist = $self->get_raw_zip_data();\n serialize_file $self->zip_db_json_file => $zip_boro_dist;\n say "Created a new " . $self->zip_db_json_file if $self->verbose;\n}\n\nsub get_raw_zip_data {\n my $self = shift;\n my %zips_to_city = %{ _get_zips_to_city() };\n my %bdz = %{ _get_borough_district_zips() };\n my %zip_boro_dist;\n for my $borough ( sort keys %bdz ) {\n my %district = %{ $bdz{$borough} };\n for my $district_name ( sort keys %district ) {\n my @district_zips = @{ $district{$district_name} };\n for my $zip ( sort @district_zips ) {\n my ( $city, $county ) = split \/,\/, $zips_to_city{$zip};\n $county =\n $borough eq 'Brooklyn' ? 'Kings'\n : $borough eq 'Bronx' ? 'Bronx'\n : 'New York'\n unless $county;\n\n $zip_boro_dist{$zip} = {\n borough => $borough,\n district => $district_name,\n city => $city,\n county => $county,\n };\n }\n }\n }\n return \\%zip_boro_dist;\n}\n\nsub read_and_dump_the_db {\n my $self = shift;\n my $location_rec = $self->zip_hash;\n dump $location_rec;\n}\n<\/pre><\/div>\n\n\nMethod ‘get_raw_zip_data’ grabs the two hard coded data structures and merges them. It makes a few little adjustments. It is called by ‘create_new_zipdb_file which uses the ‘serialize_file’ function from File::Serialize<\/a> to dump the the Perl data structure in JSON format to the output JSON file.<\/p>\nMethod ‘read_and_dump_the_db’ just reads this JSON file into the ‘zip_hash’ and dumps the contents to the console.<\/p>\n\n\n
\n "10022" : {\n "borough" : "Manhattan",\n "city" : "New York",\n "county" : "New York",\n "district" : "Gramercy Park and Murray Hill"\n },\n "10023" : {\n "borough" : "Manhattan",\n "city" : "New York",\n "county" : "New York",\n "district" : "Upper West Side"\n },\n ...\n "10314" : {\n "borough" : "Staten Island",\n "city" : "Staten Island",\n "county" : "Richmond",\n "district" : "Mid-Island"\n },\n "10451" : {\n "borough" : "Bronx",\n "city" : "Bronx",\n "county" : "Bronx",\n "district" : "High Bridge and Morrisania"\n },\n ...\n "11426" : {\n "borough" : "Queens",\n "city" : "Bellerose",\n "county" : "Queens",\n "district" : "Southeast Queens"\n },\n "11427" : {\n "borough" : "Queens",\n "city" : "Queens Village",\n "county" : "Queens",\n "district" : "Southeast Queens"\n },\n "11428" : {\n "borough" : "Queens",\n "city" : "Queens Village",\n "county" : "Queens",\n "district" : "Southeast Queens"\n },\n<\/pre><\/div>\n\n\nThe complete script can be found here create_zipdb.pl<\/strong><\/a><\/p>\n\n\n\n\n\n\n\n\n