Warning:
This wiki has been archived and is now read-only.

BP Mapping to the Requirements

From Spatial Data on the Web Working Group

Jump to: navigation, search

The table below provides a mapping between the Spatial Data on the Web Requirements and the best practices defined by the the Spatial Data on the Web Best Practices.

Spatial Data on the Web Requirements	Spatial Data on the Web Best Practices	Data on the Web Best Practices
Avoid coordinate transformations	Best Practice 3: Choose the coordinate reference system to suit your user's applications	Best Practice 15: Reuse vocabularies, preferably standardized ones
Bounding box and centroid	Best Practice 8: Provide geometries on the Web in a usable way
Compatibility with existing practices	Best Practice 1: Include spatial metadata in dataset metadata Best Practice 14: Publish links between spatial things and related resources	Best Practice 15: Reuse vocabularies, preferably standardized ones
Compressibility		Best Practice 17: Provide bulk download Best Practice 18: Provide Subsets for Large Datasets
Coordinate precision	Best Practice 5: Describe the positional accuracy of spatial data Best Practice 3: Choose the coordinate reference system to suit your user's applications	[Best Practice 6: Provide data quality information Best Practice 6]: Provide data quality information
Crawlability	Best Practice 4: Make your spatial data indexable by search engines Best Practice 11: Expose spatial data through 'convenience APIs'	Best Practice 1: Provide metadata Best Practice 2: Provide descriptive metadata Best Practice 3: Provide structural metadata Best Practice 23: Make data available through an API
CRS definition	Best Practice 3: Choose the coordinate reference system to suit your user's applications Best Practice 9: Describe relative positioning
Determinable CRS	Best Practice 17: State how coordinate values are encoded Best Practice 1: Include spatial metadata in dataset metadata Best Practice 3: Choose the coordinate reference system to suit your user's applications	Best Practice 15: Reuse vocabularies, preferably standardized ones
Discoverability	Best Practice 4: Make your spatial data indexable by search engines Best Practice 11: Expose spatial data through 'convenience APIs' Best Practice 14: Publish links between spatial things and related resources	Best Practice 1: Provide metadata Best Practice 2: Provide descriptive metadata Best Practice 3: Provide structural metadata Best Practice 23: Make data available through an API
Encoding for vector geometry	Best Practice 10: Encoding spatial data Best Practice 17: State how coordinate values are encoded	Best Practice 12: Use machine-readable standardized data formats
Independence on reference systems	Best Practice 9: Describe relative positioning Best Practice 17: State how coordinate values are encoded Best Practice 1: Include spatial metadata in dataset metadata Best Practice 14: Publish links between spatial things and related resources	Best Practice 13: Use locale-neutral data representations
https://www.w3.org/TR/sdw-ucr/#Linkability Linkability	Best Practice 7: Use globally unique persistent HTTP URIs for spatial things Best Practice 14: Publish links between spatial things and related resources	Best Practice 9: Use persistent URIs as identifiers of datasets Best Practice 10: Use persistent URIs as identifiers within datasets Best Practice 11: Assign URIs to dataset versions and series
Linking geometry to CRS	Best Practice 9: Describe relative positioning Best Practice 14: Publish links between spatial things and related resources
Machine to machine	Best Practice 1: Include spatial metadata in dataset metadata Best Practice 11: Expose spatial data through 'convenience APIs' Practice 7: Use globally unique persistent HTTP URIs for spatial things	Best Practice 1: Provide metadata Best Practice 2: Provide descriptive metadata Best Practice 3: Provide structural metadata Best Practice 23: Make data available through an API
Multilingual support		Best Practice 1: Provide metadata Best Practice 2: Provide descriptive metadata
Multiple CRSs	Best Practice 3: Choose the coordinate reference system to suit your user's applications Best Practice 17: State how coordinate values are encoded
Provenance		Best Practice 5: Provide data provenance information
Spatial metadata	Best Practice 1: Include spatial metadata in dataset metadata Best Practice 17: State how coordinate values are encoded Best Practice 9: Describe relative positioning Best Practice 8: Provide geometries on the Web in a usable way Best Practice 4: Make your spatial data indexable by search engines	Best Practice 1: Provide metadata Best Practice 2: Provide descriptive metadata
Spatial relationships	Best Practice 9: Describe relative positioning Best Practice 8: Provide geometries on the Web in a usable way
Spatial operators	Best Practice 9: Describe relative positioning Best Practice 8: Provide geometries on the Web in a usable way
Spatial vagueness	Best Practice 9: Describe relative positioning Best Practice 14: Publish links between spatial things and related resources
Streamable data	Best Practice 6: Describe properties that change over time	Best Practice 20: Provide real-time access Best Practice 21: Provide data up to date Best Practice 11: Assign URIs to dataset versions and series
Subject equality		Best Practice 14: Provide data in multiple formats Best Practice 19: Use content negotiation for serving data available in multiple formats
Support for 3D	Best Practice 10: Encoding spatial data Best Practice 8: Provide geometries on the Web in a usable way	Best Practice 16: Choose the right formalization level
Support for tiling	Best Practice 10: Encoding spatial data Best Practice 8: Provide geometries on the Web in a usable way
Time dependencies in CRS definitions	Best Practice 17: State how coordinate values are encoded Best Practice 3: Choose the coordinate reference system to suit your user's applications	Best Practice 35: Cite the Original Publication
Validation

Retrieved from "https://www.w3.org/2015/spatial/wiki/index.php?title=BP_Mapping_to_the_Requirements&oldid=3851"

BP Mapping to the Requirements

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Navigation

extra links

Tools