Skip to content

"Cruisy" as amenity feature in the 1990s #82

@lukeave

Description

@lukeave

Old data entry rule:
"IF a location has (cruisy) in the description it is handled differently. In that case the location gets a type of cruisy area BUT NOT an amenity. Only cruising areas listed at the end of a city should have the AMENITY of cruising area."

We need to think about whether the rule still applies to later guides. In prior years, the "type" variable could have many values per entry as a single entry could be both a bar and a restaurant. It was also subjective to whoever did the data transcription. The types become uniquely defined categories in the later guides themselves, making the type column in the data a "single select" field instead of a "multiple select" field. In other words, an entry cannot be listed under "Bars" and "Cruisy Areas" at the same time.

If the location has "(cruisy)" in the description, it becomes a methodological decision whether we should consider this information an amenity feature. Although often in parenthesis, it does not show up in the guide's "Key to Code" like other features considered amenities.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions