Which data type is best suited for mapping city roads?

Which data type is best suited for mapping city roads?

• A. Raster
• B. Both equally good
• C. Vector
• D. None

Answer: (C)

Representing city roads relies on precise geometry and clear connectivity. Vector data stores features as lines with exact coordinates and explicit topology, so road segments can connect at intersections, form networks, and carry attributes like names, speeds, and restrictions. This makes routing, network analysis, and editing accurate and efficient. Raster represents the world as a grid of cells. Roads would appear as pixel blocks, which can blur narrow lines, break connectivity, and require very high resolution to maintain accuracy. While rasters work well for continuous surfaces like elevation or land cover, they’re less suitable for the discrete, interconnected nature of road networks. So the best choice is vector, because it preserves the necessary geometry and topology for mapping and analyzing city roads.

Representing city roads relies on precise geometry and clear connectivity. Vector data stores features as lines with exact coordinates and explicit topology, so road segments can connect at intersections, form networks, and carry attributes like names, speeds, and restrictions. This makes routing, network analysis, and editing accurate and efficient.

Raster represents the world as a grid of cells. Roads would appear as pixel blocks, which can blur narrow lines, break connectivity, and require very high resolution to maintain accuracy. While rasters work well for continuous surfaces like elevation or land cover, they’re less suitable for the discrete, interconnected nature of road networks.

So the best choice is vector, because it preserves the necessary geometry and topology for mapping and analyzing city roads.