GIS Data Analysis for Road Naming
Budget: $30 – $250 USD
I am overseeing an urban road-naming initiative and need a GIS specialist to handle the data side of the project. The core of the job is to collect, clean, and analyse three data streams—geographical layers, current demographic information, and traffic-flow figures—so our team can assign practical, culturally appropriate street names backed by solid evidence rather than guesswork.
Here is what I expect:
• Source and aggregate up-to-date geographical, demographic, and traffic datasets for the target city (government portals, open spatial repositories, or your licensed sources).
• Integrate those datasets into a single geodatabase, resolving any projection or schema clashes along the way.
• Run spatial analyses that highlight naming conflicts, service-area gaps, and high-priority corridors.
• Produce clear map outputs (ArcGIS Pro, QGIS, or equivalent) plus an explanatory memo summarising findings, methodology, and recommended next steps.
Acceptance criteria: the geodatabase must open without errors in ArcGIS Pro 3.x, all layer metadata should be filled out, maps must visually differentiate existing vs. proposed roads, and the summary memo should be concise yet traceable to the data.
If you are comfortable juggling shapefiles, CSVs, traffic sensor feeds, and census tables—and you write documentation that non-GIS colleagues can follow—I’m ready to get started.
Here is what I expect:
• Source and aggregate up-to-date geographical, demographic, and traffic datasets for the target city (government portals, open spatial repositories, or your licensed sources).
• Integrate those datasets into a single geodatabase, resolving any projection or schema clashes along the way.
• Run spatial analyses that highlight naming conflicts, service-area gaps, and high-priority corridors.
• Produce clear map outputs (ArcGIS Pro, QGIS, or equivalent) plus an explanatory memo summarising findings, methodology, and recommended next steps.
Acceptance criteria: the geodatabase must open without errors in ArcGIS Pro 3.x, all layer metadata should be filled out, maps must visually differentiate existing vs. proposed roads, and the summary memo should be concise yet traceable to the data.
If you are comfortable juggling shapefiles, CSVs, traffic sensor feeds, and census tables—and you write documentation that non-GIS colleagues can follow—I’m ready to get started.