I propose to release the beginning of a large repository of geographic data made available on a high-level through perl objects. Currently the data I have organized and modularized is local to the United States. The data is ZCTA (Census Zip Code Tabulation Area, essentialy Zip Codes), States, Counties, Places (Cities and others), Airports (including baloonports and others), and Airport Runways. I intend to include other parts of the world as time permits.
The intent of this data is for general purpose geographic comparison - not graphical mapping!
Since youve bothered to make this point explicitly, perhaps the namespace could also say so.
IOW - what (related) namespace would carry the maps/mapping that youre not doing ?
Geo::Mapping ? Geo::Maps ? Geo::Data::Mapping ?
Theres already a Geo::GPS::Data, Do you have a suitable/corresponding 2LD that would work ?
theres already a Geo::PostalCode - you might contact TJMATHER and inquire whether
Geo::PostalCode::CensusData is fitting - if not, Geo::ZipCode::CensusData.
CensusData is probably too specific, but Data needs somesort of qualifier, a 2LD, or a prefix.
Naming the (not yet existing ?) namespaces that could share your environment is playing nice,
youre inviting them to join your game. For instance, what if someone were trying to add
modules to support Route-Planning, Navigation ?
Hold that thought - IMO the Geo:: namespace is already a mess; it contains both Geometry and Geography stuff,
and multiple Geo::Weather*, and Geo::Stormtracker
all of which (in retrospect) could have been Geo::Weather::
obviously this is just carping, but it begs the question :
Is there sufficient justification for someone to write an Acme::Module::Rename ?
collect advice on good Module-names
collect techniques to support migration
ie: perl -pi.bak tricks, and simple script to use them.
old-name-closer.pl
rewrites the existing package to new one. writes the last version of the old-namespace module, which wraps the new namespace one.
maybe this is just POD of best practices..
I imagine theres quite a bit out there - perhaps its worth collecting ?
If anyone responds to this point, a new subject is probably warranted :-O
Every data type has
I want to hear people either cry or laugh hysterically before I actually show some code (I need to pod and do some organizing on it too). So, anyone find this intriguing?
Also, are these namespaces ok?
Aran
.
