I have drawn a map with some coordinate(longitude and latitude). What are good points that a map should have eg labels, legend, etc. Edit: The map if for the purpose of locating different objects and showing their interconnections through landmark ,color etc. The map should provide clue about itself.
closed as primarily opinion-based by PolyGeo♦ Jan 5 '16 at 23:15
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
The standard elements that I teach my students are:
- Neat Line
- North Arrow
- Scale Bar (If you use Scale Text instead, make sure to include the size of the original document)
- Date of Production
Neat line depends strongly on the usage of the map. Many of these elements can be combined together with the legend or into a title block. Some people really like scale text, but I have found that documents get resized so much now that often your scale text can become inaccurate quickly. So, I always include the size of the original document if I have scale text; but still prefer to use scale bars. The idea of each of these elements is to prevent the viewer from having to make assumptions about the map and data used for the map.
Here are some additional elements to consider:
The cartographer needs to be mindful of the end user when constructing the map layout (e.g. is the map clear and easy to understand and not too busy with text, is the size of the map appropriate for it use?).
Do the elements within the map (data frames, legend, map header, additional text areas...etc) balance each other.
Avoid having too many features and or labels on the map.
Include date/time and reference text.
The map should have all the basic elements as 'ASMapper' answer has described.
A overview map may be useful.
A north arrow, a scale bar, some kind of legend/key...
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
Besides all the great stuff artwork21 and ASPMapper said, I think there is one good general advice I can give, and artwork21 touched it in his first point.
Have a talk with the customer\end user to make sure you understand what he needs.
It works both ways - sometimes he asks for something he doesn't really need (or worse: it is something that only ruin his real needs) and then you, as an expert, can point him to a better solution. On the other side, sometimes during a talk you can reveal other needs he has (and you can fulfill) or things you weren't aware of, by yourself (such as the existence of standards for mapping of the area of expertise - such as High volt cables in red only, Interstates in yellow-and-black and such).
I'm a kid and I believe that a map has to have four essential things:
- north arrow
- scale bar ( this is optional)