Use natural language names

[mattyschell]

The feature class names requested in the capture rules sometimes differ from what is delivered. And in both cases the names inconsistently follow natural language.

For example, retaining wall is two words. A person searching for info on retaining walls will type retaining wall into a search. However the feature class name delivered is smushed into RETAININGWALL.

Column names and subtypes should also consistently follow natural language.

capture rules	delivered	natural language
MISC STRUCT POLY	MISC_STRUCTURE_POLY	miscellaneous structure polygon
OPEN SPACE	OPEN_SPACE_NO_PARK	open space not park
PAVEMENT EDGE CARTO	PAVEMENTEDGE_CARTO	pavement edge cartographic
RETAINING WALL	RETAININGWALL	retaining wall
SIDWALK CENTERLINE	SIDEWALK_LINE	sidewalk centerline
UNDER CONSTRUCTION	UNDER_CONSTRUCTION_UNKNOWN	under construction unknown

Updating names to match natural language may be ill-advised if it breaks linkages to prior releases and names.

[mattyschell]

see related issue #43 for the NYC Open data name cacophony