Osmap is a standard for storing map data in XML tags. Its goal is to be very simple and easy to use, compared to other data storage techniques such as GIS or OGC. The standard defines the tags and attributes of many elements, which fall into three categories: shape, line, and object. A key point to osmap is the ability to contain extra data, such as names of businesses, images, and short descriptions. Nearly every possible feature is attempted to be covered in the standard, so that any implementation does not need to create proprietary additions. For example, osmap has a long list of possible building types, and it is recommended that people use the exact spelling and spacing of the building type, such as school, postoffice, gas, etc. The idea is that any osmap data will work with any osma
Attributes | Values |
---|
rdfs:label
| |
rdfs:comment
| - Osmap is a standard for storing map data in XML tags. Its goal is to be very simple and easy to use, compared to other data storage techniques such as GIS or OGC. The standard defines the tags and attributes of many elements, which fall into three categories: shape, line, and object. A key point to osmap is the ability to contain extra data, such as names of businesses, images, and short descriptions. Nearly every possible feature is attempted to be covered in the standard, so that any implementation does not need to create proprietary additions. For example, osmap has a long list of possible building types, and it is recommended that people use the exact spelling and spacing of the building type, such as school, postoffice, gas, etc. The idea is that any osmap data will work with any osma
|
dcterms:subject
| |
abstract
| - Osmap is a standard for storing map data in XML tags. Its goal is to be very simple and easy to use, compared to other data storage techniques such as GIS or OGC. The standard defines the tags and attributes of many elements, which fall into three categories: shape, line, and object. A key point to osmap is the ability to contain extra data, such as names of businesses, images, and short descriptions. Nearly every possible feature is attempted to be covered in the standard, so that any implementation does not need to create proprietary additions. For example, osmap has a long list of possible building types, and it is recommended that people use the exact spelling and spacing of the building type, such as school, postoffice, gas, etc. The idea is that any osmap data will work with any osmap software, without any catches. Types of data that don't need to be seen could be disabled, as in layers. An example would be a Fireman needing to see all the fire hydrants on his map, but others would choose not to see them. The standard is currently on version 0.2, and is open source. Ideas to improve the standard are very welcome and can be submitted on osmap's Source Forge project page.
|