Design and implement a SMALL database of attractions for testing and development

[dongskyler]

If you're interested in working on this issue, please contact me. I have designed the data schema and some data in CSV files.

Is your feature request related to a problem? Please describe.

Design a small database for testing and development. For example, a limited number of National Parks or state parks in a given state.

Create a small database of 10-20 attractions, so that we can use it to develop core algorithms that can recommend road trip routes.

The area around Las Vegas is an ideal choice. There are many natural attractions within ~4 hours of driving, including Grand Canyon National Park, Death Valley National Park, Zion National Park, Bryce Canyon National Park, Horseshoe Bend, and Antelope Canyon.

Describe the solution you'd like

The database can be implemented in SQL (such as PostgreSQL or MySQL) or noSQL (such as MongoDB).

The database will be implemented with MongoDB.

Because it is difficult to pre-define the schema, given that:

• Attractions of different types may have very different attributes.
• When we scale this database up, we don't know what attributes will be included.

Therefore, a noSQL database (such as MongoDB) is an ideal choice.

The database will include at least the following info:

• Name
• Coordinates
• Type of attraction (e.g. National Park, National Monument, National Historical Park, etc)
• Hours
• Entrance fee, annual pass
• Campsite info
• In-park lodging
• Major attractions inside each park/attraction
• Popularity, measured by, e.g., number of visitors (of last available year)

[dongskyler]

This issue is too big. It needs to be broken down into smaller tasks.