Free street software for linux

Geo::StreetAddress::US is a Perl extension for parsing US street addresses.

SYNOPSIS

use Geo::StreetAddress::US;

my $hashref = Geo::StreetAddress::US->parse_location(
"1005 Gravenstein Hwy N, Sebastopol CA 95472" );

my $hashref = Geo::StreetAddress::US->parse_location(
"Hollywood & Vine, Los Angeles, CA" );

my $hashref = Geo::StreetAddress::US->parse_address(
"1600 Pennsylvania Ave, Washington, DC" );

my $hashref = Geo::StreetAddress::US->parse_intersection(
"Mission Street at Valencia Street, San Francisco, CA" );

my $normal = Geo::StreetAddress::US->normalize_address( %spec );
# the parse_* methods call this automatically...

Geo::StreetAddress::US is a regex-based street address and street intersection parser for the United States. Its basic goal is to be as forgiving as possible when parsing user-provided address strings.

Geo::StreetAddress::US knows about directional prefixes and suffixes, fractional building numbers, building units, grid-based addresses (such as those used in parts of Utah), 5 and 9 digit ZIP codes, and all of the official USPS abbreviations for street types and state names.

WebService::StreetMapLink::Google is a WebService::StreetMapLink subclass for Google Maps.

SYNOPSIS

use WebService::StreetMapLink;

my $map =
WebService::StreetMapLink->new
( country => usa,
address => 100 Some Street,
city => Testville,
state => MN,
postal_code => 12345,
);

my $uri = $map->uri;

This subclass generates links to Google Maps.

PostScript::MailLabels are modules for creating PostScript files of mailing address labels.
Flexible enough to tackle other printing tasks, basically anything requiring a set fields be printed on a regular grid. Also creates PostScript(tm) code for calibrating and testing mailing label printing.
The module has three distinct output modes. In my experience, printing mailing labels is a matter of tweaking parameters to get them all to fit properly on the page. This module is designed with this in mind.
The first output is the calibration sheet. This is a pair of annotated axes, either in inches or centimeters, centered on the page and covering the whole page in X and Y directions. The intent is for you to output this page first, and simply read off the relevant page dimensions directly.
The second output is the label test. This output is a series of boxes drawn on the page, meant to outline the edges of all the mailing labels. Take this sheet and line it up with a sheet of labels to see if they actually match perfectly. If not, tweak the parameters until they do. Note that sometimes you will get a message at the bottom of the sheet saying ``Bottom gap too large, last row cannot be printed.
This means that the printable area of your printer is too small to utilize the last row of labels. I have this problem. But I handle it for you. Note also the arrows on the test sheet. As you hold the test sheet over a sheet of labels, hold it up to the light and slide the test sheet so that the boxes match the edges of the labels. If you slide in the arrow direction, that is a positive adjustment.
The other direction is negative. If the edges of some boxes come out dashed, that means that the non-printing border cuts off the end of the label, so I will adjust the printing area appropriately. Dont try to line up the dashed lines with label edges - it wont work. Just line up the solid lines.
The third output is the labels themselves. By default, I have set up a US-centric address definition :
firstname, lastname, street address, city, state, zipcode
But with version 2.0, you can now create your own definition. You can define new fields, and you can define how those fields land on a label. You can also control the fonts on a per-field basis. Not the size, yet - later pilgrim.
Parameters you can set :
Paper size, orientation, borders on the printable area (many printers will not print right up to the edge of the paper), where the labels live on the page and how big they are, overall x-y shift of page, whether or not to print PostNET barcode, font, fontsize, units (english or metric), which Avery(tm) product code to use, and where the first label starts.
This last needs explanation. If you have a partially used sheet of labels, you might want to use it up. So you count the missing labels, starting at the upper left, and counting across, and then down. For example, if I have 3 columns of labels, label five is the second label in the second row.
If you have an Avery(tm) product that I havent defined, send me the specs and Ill add it.
Also, if there is another brand of labels that you use, send me the relevant data and Ill add that as well. I suspect that there must be some other vendor in Europe, but I dont know who that would be.
When setting up the addresses, I check to see if they will fit on the label. If not, I try to shorten them semi-intelligently until they fit. This part could use quite a bit more work, if done right it probably merits a module all its own.
Briefly, for the name line, I start trimming the ends off the first name, and leave the last name alone.
For the street, I look for things like Road or Avenue and nuke those first, then I trim the street name from the right.
Enhancements:
- Parentheses are now escaped in the generated PostScript code.

Class::Phrasebook is a Perl module that implements the Phrasebook pattern.

SYNOPSIS

use Class::Phrasebook;
my $pb = new Class::Phrasebook($log, "test.xml");
$pb->load("NL"); # using Dutch as the language
$phrase = $pb->get("ADDRESS",
{ street => "Chaim Levanon",
number => 88,
city => "Tel Aviv" } );

This class implements the Phrasebook pattern. It lets us create dictionaries of phrases. Each phrase can be accessed by a unique key. Each phrase may have placeholders. Group of phrases are kept in a dictionary. The first dictionary is the default one - which means that it will always be read. One of the dictionaries might be used to override the default one. The phrases are kept in an XML document.

Excalibur: Morganas Revenge (EMR) is a unique scenario based upon the Aleph One (Marathon) engine. It is a first-person action adventure game, featuring an epic and in-depth story line. As a Federation Marine resting after your last mission, you start aboard the exploration class Starship Kronos where you learn that your real mission has yet to begin. You are re-acquainted with the AI Merlin, who introduces you to Kronos time traveling technology, and reveals your new mission: to save mankind from the clutches of Morgana and her minions. Through untamed raptor-infested jungles, castle arenas, and war-torn streets of the future, you will wield weapons from all time periods - including the Sword of Power, Excalibur - in an effort to thwart the diabolical plot that unfolds. The EMR adventure, spread across 42 solo levels, weaves a tale of truth and honor, knighthood and bravery, and darkness and treachery. EMR also delivers 27 adrenaline pumped network levels. EMR immerses you in an amazing new world, creating an addictive, fun and unique gaming experience.

For those that played EMR under the old Marathon Infinity engine, EMR 3.0 brings exciting new maps, new high resolution textures and landscapes, a completely new set of weapons, new monsters and friends, new scenery, new 16-bit sounds, original music, and a carefully woven original story line that transcends time. Using the Aleph One engine, EMR now sports loads of new special features using Aleph Ones MML and Lua scripting languages. Please note that the AlephOne engine is old technology improved. Architecture is still simulated 3D, so there are no ramps, bridges, and balconies, nor horizontal doors. The sprites in EMR are made up of 2D images posed in different views, not 3D models. Do not expect the latest state-of-the-art graphics engine, but you can expect an intriguing storyline, creative map architectures, engaging graphics, original spellbinding music, and mood-setting sound effects.

Whats New in This Release:

• Levels with fog and mist
  
• Persistent effects such as poison, earthquakes, fire storm spell, and timed grenades
  
• Original MP3 music
  
• 12 unique weapons, including a new Dragon Flamer and T9000 Railgun
  
• New spells for your wand, including fire storm, teleportation, and raise the
  dead
  
• Beautifully rendered OpenGL textures and landscapes
  
• New graphics for Morgana, the Trex, raven, and Jurassic bug
  
• A huge variety of new hi-res scenery items
  
• New holodeck programs, including driving a Flintstone mobile through Bedrock!
  
• Blood Gulch style net map with 8 simulated net players and a huge battlefield
  
• A basketball court netmap where grenades in a basket win points for your team
  
• A beautiful new future level that lets you drive a Hoverbike!
  
• A total of 5 brand new solo maps and 4 new net maps
  
• Lots of updated maps with new areas, new tasks, new features, and new secrets
  
• New powerups, such as apples, bananas, health kits, emergency kits, and finally
  a use for all those magic scrolls!
  
• And much, much, more...
  

LMarbles is an Atomix clone with a slight change in concept. Instead of assembling molecules you create figures out of marbles. Nevertheless, the basic game play is the same: If a marble starts to move it will not stop until it hits a wall or another marble.

To make it more interesting there are obstacles like one-way streets, crumbling walls and portals.

As Marbles is meant as a puzzle game you play against a move limit and not a time limit. This way you have as much time as you need to think.

XML::Rules is a Perl module that can parse XML & process tags by rules starting from leaves.

SYNOPSIS

use XML::Rules;

$xml = < < *END*
< doc >
< person >
< fname >...< /fname >
< lname >...< /lname >
< email >...< /email >
< address >
< street >...< /street >
< city >...< /city >
< country >...< /country >
< bogus >...< /bogus >
< /address >
< phones >
< phone type="home" >123-456-7890< /phone >
< phone type="office" >663-486-7890< /phone >
< phone type="fax" >663-486-7000< /phone >
< /phones >
< /person >
< person >
< fname >...< /fname >
< lname >...< /lname >
< email >...< /email >
< address >
< street >...< /street >
< city >...< /city >
< country >...< /country >
< bogus >...< /bogus >
< /address >
< phones >
< phone type="office" >663-486-7891< /phone >
< /phones >
< /person >
< /doc >
*END*

@rules = (
_default = > sub {$_[0] = > $_[1]- >{_content}},
# by default Im only interested in the content of the tag, not the attributes
bogus = > undef,
# lets ignore this tag and all inner ones as well
address = > sub {address = > "$_[1]- >{street}, $_[1]- >{city} ($_[1]- >{country})"},
# merge the address into a single string
phone = > sub {$_[1]- >{type} = > $_[1]- >{content}},
# lets use the "type" attribute as the key and the content as the value
phones = > sub {delete $_[1]- >{_content}; %{$_[1]}},
# remove the text content and pass along the type = > content from the child nodes
person = > sub { # lets print the values, all the data is readily available in the attributes
print "$_[1]- >{lname}, $_[1]- >{fname} < $_[1]- >{email} >n";
print "Home phone: $_[1]- >{home}n" if $_[1]- >{home};
print "Office phone: $_[1]- >{office}n" if $_[1]- >{office};
print "Fax: $_[1]- >{fax}n" if $_[1]- >{fax};
print "$_[1]- >{address}nn";
return; # the < person > tag is processed, no need to remember what it contained
},
);
$parser = XML::Rules- >new(rules = > @rules);
$parser- >parse( $xml);

The United States Postal Service (USPS) has on its web site an HTML form at http://www.usps.com/zip4/ for standardizing an address. Given a firm, urbanization, street address, city, state, and zip, it will put the address into standard form (provided the address is in their database) and display a page with the resulting address.
Scrape::USPS::ZipLookup Perl Module provides a programmatic interface to this service, so you can write a program to process your entire personal address book without having to manually type them all in to the form.
Because the USPS could change or remove this functionality at any time, be prepared for the possibility that this code may fail to function. In fact, as of this version, there is no error checking in place, so if they do change things, this code will most likely fail in a noisy way. If you discover that the service has changed, please email the author your findings.
If an error occurs in trying to standardize the address, then no array will be returned. Otherwise, a four-element array will be returned.
To see debugging output, call $zlu->verbose(1).
SYNOPSIS
#!/usr/bin/perl
use Scrape::USPS::ZipLookup::Address;
use Scrape::USPS::ZipLookup;
my $addr = Scrape::USPS::ZipLookup::Address->new(
Focus Research, Inc., # Firm
, # Urbanization
8080 Beckett Center Drive Suite 203, # Delivery Address
West Chester, # City
OH, # State
45069-5001 # ZIP Code
);
my $zlu = Scrape::USPS::ZipLookup->new();
my @matches = $zlu->std_addr($addr);
if (@matches) {
printf "n%d matches:n", scalar(@matches);
foreach my $match (@matches) {
print "-" x 39, "n";
print $match->to_string;
print "n";
}
print "-" x 39, "n";
}
else {
print "No matches!n";
}
exit 0;
Enhancements:
- Adapt to yet another round of changes to the USPS Zip Lookup web site, courtesy of Eric Parker.
- Copyright date updates.