Map Chart Maps

Available Maps

The available maps in Davisor Chart include:

Thumbnail	namespace	Description	Object IDs	Coordinate System
	World_2000 World_2000_FIPS	Countries and separate regions of the World in 2000. Contains also continents.	'World_2000' namespace contains 2-letter ISO codes for countries, 3-letter ISO codes for countries, and continents: AFRICA, ASIA, EUROPE, NORTH_AMERICA, OCEANIA, and SOUTH_AMERICA. 'World_2000_FIPS' namespace contains FIPS 10-4 codes for countries, and continents as above.	Latitudes and longitudes in degrees so that northern latitudes are negative.
	Europe_2000	Countries and the main administration boundaries in the Europe in 2000. European parts of Russia and Turkey included. Projected using Albers equal-area conic projection with origin in 45N 10E and standard parallels in 40N and 56N.	2-letter ISO codes for countries, and Special codes for administrative regions	Projected coordinates
	USA_2001	Counties and states in the United States in 2001. Alaska, Hawaii, Puerto Rico, and Virgin Islands are scaled and transformed nearby. The main continent is projected using Lambert conformal conic projection with origin in 23N 96W and standard parallels in 20N and 60N.	FIPS 6-4 codes for counties (and county equivalents), FIPS 5-2 numeric codes for states, FIPS 5-2 alpha codes for states, and special id 'lakes' for the U.S. water areas.	Projected coordinates
	USA_2001_flat USA_2001_rough	Counties and states in the USA and outer regions in 2001. The 'rough' version contains less edges and is thus faster to draw and consumes less memory.	FIPS 6-4 codes for counties (and county equivalents), FIPS 5-2 numeric codes for states, and FIPS 5-2 alpha codes for states.	Polar latitudes and longitudes in degrees.

New Maps

If the base set of maps described above doesn't meet your needs, or You have Your own map data, please contact to Davisor Sales for feasible priced map data conversion.

Importing Own Maps

It is possible to use own maps in Davisor Chart. See the requirements below and convert your data to the proper format. NOTE: Map coordinates may be anything, the maps are always scaled, which happens by keeping aspect ratio, so that they will fit into the given image width and/or height. If image width and height are not given, then the map coordinates are used like they were pixels.

Requirements:

• A property file named namespace_shapes.properties containing id=SVG_path pairs.
• The SVG_path describes a shape identified by id. The path must be defined using SVG 1.1 path syntax.
  
  
• An additional property file named namespace.properties may be given
• That additional property file may contain the following properties:
  • id.name - Displayable name for the area. Can be used e.g. like valueFormat="{.name}". Also available for annotations.
  • id.shape - list of comma (,) separated shape ids defined in the namespace_shapes.properties file.
  • id.shapeRef - list of comma (,) separated shape id references defined in the same file.
  • id.labelx - x-coordinate for optimal label positioning (in the map coordinates)
  • id.labely - y-coordinate for optimal label positioning (in the map coordinates)
  • id.hotspotx - x-coordinate for the additional shape (e.g. used to mark the capital city)
  • id.hotspoty - y-coordinate of the additional shape
  • id.anything_else - additional value, which can be used in valueFormat or annotations
  
  
• Both property files must be in CLASSPATH so that they can be found. Those property files are loaded as ResourceBundles so they can be in subfolders (use dots when giving namespace then).

Disclaimer

Disclaimer of Warranty: The map data may be inaccurate or incomplete, and is subject to change. Davisor Ltd. does not warrant the accuracy or completeness of this map product and therefore disclaims all liability for its fitness of use.