govgis_nov2023-slim-spatial

This MCP server deploys a Dockerized stack that combines PostGIS and pgvector to host and query the govgis_nov2023-slim-spatial data. The stack is orchestrated via docker-compose and can be started from the repository root. Once started, the postgres service is initialized with the govgis_nov2023 dataset and pgAdmin provides a web interface for database management. Use the provided environment variables to configure database credentials and admin access. Interaction with the MCP server primarily occurs through the PostgreSQL database layer (PostGIS + pgvector) and any exposed endpoints defined by the surrounding application. The repository notes a data-loading process via the postgres-init service, which ingests the govgis_nov2023-slim-spatial dataset into PostGIS, enabling spatial queries and high-dimensional vector similarity searches through pgvector.

Prerequisites:\n- Docker and Docker Compose installed on your system.\n- Git installed.\n\nSteps:\n1. Clone the repository:\n git clone https://github.com/joshuasundance-swca/govgis_nov2023-slim-spatial-server.git\n2. Navigate to the project directory:\n cd govgis_nov2023-slim-spatial-server\n3. Create and configure environment variables. A typical .env-like approach is to set: POSTGRES_PASSWORD, POSTGRES_USER, and your pgAdmin credentials.\n4. Start the MCP server stack:\n docker compose up -d\n5. Verify services:\n docker compose ps\n6. Access pgAdmin (as configured): http://localhost:80 or as defined in your environment. If you modified ports, adjust accordingly.\n\nNotes:\n- The docker-compose.yml defines services such as postgres, postgres-init, and pgadmin.\n- Ensure Docker has enough resources (CPU/RAM) for PostGIS and pgvector workloads.

Tips and considerations:\n- The postgres-init service loads the govgis_nov2023 dataset into the database during initialization. Ensure the dataset download is placed in the expected path per docker-compose configuration.\n- Customize environment variables in the .env file or via the environment section in the MCP config to secure credentials.\n- For production use, consider restricting network access to pgAdmin and the PostgreSQL instance and enable proper backup strategies.\n- If you need to modify the data source, you can adjust load_data.py as mentioned in the README.\n- If you encounter issues with Docker Compose v2 syntax, ensure you are using the appropriate version (the project uses the docker compose CLI, not docker-compose v1).