This page is for discussing the contents of Wiki Community/April 2010 Wiki Meeting and providing additional input.
Discussion
Please Edit in any Discussion here, provide Comments below.
Zip codes on Addresses:
-
Zip Code to Town is a difficult/impractical automation task as there is no direct mapping from zip code to town or vice versa. I learned a lot on the subject when I spent a lot of time on the Zip Codes page and its corresponding Zip Codes/Talk - as well as information on Webster and Fairport which are notorious for their zip code issues. The Rochester zip codes cover parts or all of several towns. There are a number of area towns with NO ZIP CODE, such as Brighton, Gates, Chili and Perinton.
All of these problems caused me to start using the technique of the two argument Address Macro. The macro allows you to put the actual geocoding address in the first argument and the display data in the second argument. By leaving out the geocoding town and placing it wiki linked after the macro (post-fixed), we get a more useful output. I understand that some folks want zip codes for GPS needs, so I am now including them in the post-fixed data.
For example, the
original page for the Perinton Town Hall contained the address of Fairport, which is a small Village within the Town of Perinton.
Jack mentioned that zip codes should be included on addresses for GPS programming purposes. Dawn suggested an automation to translate zip code->town name for display, perhaps adding the appropriate wiki link as well.
I changed it to the new Perinton Town Hall which provides the correct town (wiki linked), the address with mapping, and the GPS-sers Zip code.
[[Address("1350 Turk Hill Road, Fairport, NY 14450","1350 Turk Hill Rd")]], ["Perinton"], NY 14450 | |
1350 Turk Hill Rd ![]() |
The Zip Codes page has some good resource links for those wanting to understand the problem a little better.
Quick comments:
-
On
Buffalo Wiki I implemented a
RAW Data page that has it's security settings to allow non-logged in users to add comments on the page. In fact, Jack used the capability himself. I would suggest that instead of
Jack suggested a mechanism where comments/feedback could be left by non-logged-in users, perhaps to report out-of-date information or suggest additional features. Handling this inform ation will require some thought.
Comments:
Note: You must be logged in to add comments
on the non-logged in page, it could contain something like
'''Comments:Note: You must be logged in to add comments or provide data via our ["RAW Data"] page.'''
Comments
Meeting Minutes Feedback
Note: You must be logged in to add comments