Free zip codes by city software for linux

OpenCity is a 3D city simulator game.

Once upon the time, I was travelling over the Internet, and I found a city simulator under linux called FreeReign at SourceForge. But it isnt maintained any more. I decided to push the game up so I had a look at the FreeReign sources.

However, its codes were not obvious to me, and in addition the game design didnt fit my programming style. Finally, I decided to write my own free 3D city simulator, based on the original ideas of the FreeReign project. Few months later, OpenCity was born.

OpenCity is a city simulator game project written in standard C++ with OpenGL and SDL from scratch. It is not intended to be a clone of any famous city simulator from Max*s. So, if you are looking to download a free SimCity 4 like, please forget OpenCity. I work on it at my spare time, I really meant it "my spare time" !

OpenCity is also a OpenGL game programming tutorial. In the resources section, you can find the micro simulators algorithm, design document, UML diagram and information about other issues.

Quiet Console Town project is a console RPG city simulator.

Console RPGs have you visiting towns all the time, but Quiet Console Town puts you in the place of the mayor of a budding new city. Build shops, attract adventurers, hope villains overlook you: all the aspects of a console RPG town are yours.

Welcome to your everyday ordinary quiet console town. By the looks of your deceased friend there, youll probably want to stay a night at the Inn. Yes, those puncture wounds and missing organs certainly seem fatal, but all he needs is a good nights sleep and then (somehow) hell be good as new. In the meantime, might I direct you to our armor shop?

A bit of plate inbetween you and the monster might help you stay healthy! I see your thief seems anxious - theres some shady characters near the magic shop she might want to meet up with. Finally, once youre all done, perhaps you could look into the matter of our haunted mine...?

Quiet Console Town is a turn-based console RPG city simulator. You, as mayor, build the kind of RPG town youve always wanted heroes to visit. Buildings range from the simple Inn to the intricate dungeons beneath your mighty Citadel.

People can be as good as the most pious do-gooder, or evil as the most black-hearted villain. Make your city a bulwark against the forces of darkness, or a haven to shady characters round the world!

Splendid City Team Sports Scheduler, and Sports Scheduling Software System is useful for people who organize team sports or game events. It can manage sports schedules of any size and complexity. Simply fill in the requested information into the wizard like interface, and Splendid City automates the season, tournament, league, match, round-robin and practice schedules.

A great first step and time saving tool for anyone who frequently does organizational sports scheduling. Splendid City can schedule sports with any user specified combination of dates and times. Create professional double or single elimination tournaments brackets, round-robin league schedules, swiss round tournaments, cross divisional or practice schedules for any sport that requires pairings.

It features options that include the ability to set team and field constraints, game lengths; configurative time management utilities to help you organize events the way you would like; object constraint sharing; automatic schedule generation and re-generation; configurative project web site creation, tournament brackets; publishing via FTP, export to HTML, CSV, iCalendar, XML; import from CSV; standings support with tie-breaker formulas; contact management; import teams, fields, officials, players and player rosters from other users projects ; constraint and conflict checking and resolution.

Users can freely exchange all data associated with projects with other users who have a free copy of Splendid City Lite installed regardless of platform. The application comes with an integrated e-mail client that can aid with the exchange of object files among organization members. There is also a simple FTP client for direct uploading to web domains from within the schedule view frame.

The scheduler gives you complete control over all aspects of the schedule, and creates solutions effortlessly and elegantly in accordance with the user data entered. It can be custom-tailored, and with repeated use via a plugin interface, can be made to automatically accomplish users unique scheduling needs.

The user experience is interactive and straight forward. The application comes fully documented with a built in searchable help system to provide answers to implementation questions.

Geo:Coder:US 1.00 offers a full-feature facility for geocoding US addresses, that is, estimating the latitude and longitude of any street address or intersection in the United States, using the TIGER/Line data set from the US Census Bureau. Geo:Coder:US uses Geo:TigerLine to parse this data, and DB_File to store a highly compressed distillation of it, and Geo:StreetAddress:US to parse addresses into normalized components suitable for looking up in its database.

You can find a live demo of this code at http://geocoder.us/. The demo.cgi script is included in eg/ directory distributed with this module, along with a whole bunch of other goodies. See Geo:Coder:US:Import for how to build your own Geo:Coder:US database.

Consider using a web service to access this geocoder over the Internet, rather than going to all the trouble of building a database yourself. See eg/soap-client.pl, eg/xmlrpc-client.pl, and eg/rest-client.pl for different examples of working clients for the rpc.geocoder.us geocoder web service.

Major Features:

1. Geo:Coder:US->geocode( $string )
   • Given a string containing a street address or intersection, return a list of specifiers including latitude and longitude for all matching entities in the database. To keep from churning over the entire database, the given address string must contain either a city and state, or a ZIP code (or both), or geocode() will return undef.
   • geocode() will attempt to normalize directional prefixes and suffixes, street types, and state abbreviations, as well as substitute TIGER/Line's idea of the "primary street name", if an alternate street name was provided instead.
   • If geocode() can parse the address, but not find a match in the database, it will return a hashref containing the parsed and normalized address or intersection, but without the "lat" and "long" keys specifying the location. If geocode() cannot even parse the address, it will return undef. Be sure to check for the existence of "lat" and "long" keys in the hashes returned from geocode() before attempting to use the values! This serves to distinguish between addresses that cannot be found versus addresses that are completely unparseable.
   • geocode() attempts to be as forgiving as possible when geocoding an address. If you say "Mission Ave" and all it knows about is "Mission St", then "Mission St" is what you'll get back. If you leave off directional identifiers, geocode() will return address geocoded in all the variants it can find, i.e. both "N Main St" and "S Main St".
   • Don't be surprised if geocoding an intersection returns more than one lat/long pair for a single intersection. If one of the streets curves greatly or doglegs even slightly, this will be the likely outcome.
   • geocode() is probably the method you want to use. See more in the following section on the structure of the returned address and intersection specifiers.
2. Geo:Coder:US->geocode_address( $string )
   • Works exactly like geocode(), but only parses addresses.
3. Geo:Coder:US->geocode_intersection( $string )
   • Works exactly like geocode(), but only parses intersections.
4. Geo:Coder:US->filter_ranges( $spec, @candidates )
   • Filters a list of address specifiers (presumably from the database) against a query specifier, filtering by prefix, type, suffix, or primary name if possible. Returns a list of matching specifiers. filter_ranges() will ignore a filtering step if it would result in no specifiers being returned. You probably won't need to use this.
5. Geo:Coder:US->find_ranges( $address_spec )
   • Given a normalized address specifier, return all the address ranges in the database that appear to cover that address. find_ranges() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_ranges() to find the closest match possible in preference to returning nothing. You probably want to use lookup_ranges() instead, which will call find_ranges() for you.
6. Geo:Coder:US->lookup_ranges( $address_spec, @ranges )
   • Given an address specifier and (optionally) some address ranges from the database, interpolate the street address into the street segment referred to by the address range, and return a latitude and longitude for the given address within each of the given ranges. If @ranges is not given, lookup_ranges() calls find_ranges() with the given address specifier, and uses those returned. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.
7. Geo:Coder:US->find_segments( $intersection_spec )
   • Given a normalized intersection specifier, find all of the street segments in the database matching the two given streets in the given locale or ZIP code. find_segments() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_segments() to find the closest match possible in preference to returning nothing. You probably want to use lookup_intersection() instead, which will call find_segments() for you.
8. Geo:Coder:US->lookup_intersection( $intersection_spec )
   • Given an intersection specifier, return all of the intersections in the database between the two streets specified, plus a latitude and longitude for each intersection. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.

Requirements: Perl

Lincity project is an city simulation game for SVGALib/X/Win32/etc.

You are required to build and maintain a city. You must feed, house, provide jobs and goods for your residents.

You can build a sustainable economy with the help of renewable energy and recycling, or you can go for broke and build rockets to escape from a pollution ridden and resource starved planet, its up to you.

Due to the finite resources available in any one place, this is not a game that you can leave for long periods of time.

Missile Command project is a game in which you have to save your city from nuclear doom.

Missile Command is a clone of the Atari save-your-city-from-impending-nuclear-doom game.

OpenGuides is a wiki-like package for maintaining a collaborative city guide. It is written in Perl and runs as a CGI program, and uses either the MySQL, PostgreSQL, or SQLite database.
OpenGuides offers features over a "normal" wiki such as metadata management and a "find nearby things" function. The look and feel is highly customizable thanks to use of the Template Toolkit.
Enhancements:
- This is mostly a bugfix release, improving character set handling in the database, correcting some latitude/longitude issues, and other miscellaneous bits.
- Also added is the ability to ping external services when updates are made.

RIG is a program I wrote to replace a particularly poor closed-source unattributed public-domain implementation for MS-DOS. Essentially it gathers random selections of first and last names, location data, and street names, to assemble a fake name and address, complete with geographically consistant ZIP code, area code, state, and city name.
My implementation of fake is GPL, however its database belongs to whoever wrote the original implementation, or if that person remains unknown then I suppose it lies in the public domain. If you feel uncomfortable with this then please provide a new database. It shouldnt be too hard to create a new one.
Install should be pretty easy, just type "make install". If your system dosent
have /dev/urandom and youd like to use /dev/random instead, do
make install CFLAGS=-DDEVRANDOM
Enhancements:
- Fix compilation on some platforms. Thanks to many people for noticing these problems.
- Fix problems with the -m and -f options. Thanks to Casey Carter noticing this problem, and to the Debian developers (notably Norbert Veber and Aaron Lehmann ) for proposing a fix.
- Add an entry for Coward, SC.
- Make Biloxi area and ZIP codes match the same physical spot. Thanks to Chris Lawrence for noticing this.