Landscape Explorer is a React-based web application for visualizing geospatial data using interactive maps. It enables users to explore landscapes through administrative boundaries, filters, and pattern-based visualizations.

• React
• OpenLayers
• Node.js / npm
• GeoServer

Ensure the following are installed:

• Node.js (v16+ recommended)
• npm

git clone https://github.com/core-stack-org/landscape-explorer.git
cd landscape-explorer

npm install

Create a .env file in the root directory of the project where the package.json is located.

touch .env

Add the following variables to .env

REACT_APP_API_URL="https://geoserver.core-stack.org/api/v1"
REACT_APP_GOOGLE_KEY="xxx"
REACT_APP_GEOSERVER_URL="https://geoserver.core-stack.org:8443/geoserver/"

# Google Analytics
REACT_APP_GA_MEASUREMENT_ID="xxx"
REACT_APP_API_KEY="xxx"

REACT_APP_WATERBODYREJ_USERNAME="xxx"
REACT_APP_WATERBODYREJ_PASSWORD="xxx"
REACT_APP_BASEURL="https://geoserver.core-stack.org"

npm run start

The application will be available at:

http://localhost:3000

In some cases, after running npm install, the application may fail to start due to a missing react-icons/gi module.

Install the missing dependency manually:

npm install react-icons

Then restart the development server:

npm run start

We welcome contributions to Landscape Explorer. Please follow the guidelines below to ensure a smooth collaboration process.

1. Fork the Repository
   Create your own fork of the repository to start working on the codebase.

2. Clone Your Fork

   git clone https://github.com/core-stack-org/landscape-explorer.git
   cd landscape-explorer

3. Work on the development Branch Always switch to the development branch before starting your work:

   git checkout development
   

If you want to work on an existing issue:

1. Comment on the issue expressing your interest.
2. Tag any of the repository maintainers.
3. Wait until the issue is officially assigned to you.
4. After assignment, start working on the implementation.
5. Submit your changes through a Pull Request.

Ensure your branch is updated with the latest development branch.

1. Push your changes to your fork.
2. Create a Pull Request (PR) targeting the development branch.
3. Provide a clear description of:
   • What changes were made
   • Why the changes were made
   • Any related issue number (if applicable)