http://schema.org/GeoShape
http://schema.org/box
http://schema.org/polygon

See discussion at geojson/geojson-ld#28

Original text: "See http://geowanking.org/pipermail/geowanking_geowanking.org/2012-June/026179.html
Schema.org's design came via rNews from GeoRSS, and there from GML. It needs a fresh look."

This is now a meta bug for improvements to schema.org's geo(spatial) vocabulary:

Geospatial 'core' terms:

• http://schema.org/latitude http://schema.org/longitude http://schema.org/elevation on http://schema.org/GeoCoordinates are vague; they don't mention e.g. wgs-84. GeoCoordinates improvements: allow address, mention wgs84 #802
• http://schema.org/elevation has no units or base; contrast e.g. W3C basic geo which we defined (eventually) as "The WGS84 altitude of a SpatialThing (decimal meters above the local reference ellipsoid)."
• http://schema.org/box has the wrong text (copy/paste error), definition is identical to http://schema.org/polygon. Needs a definition. VOCAB: schema.org/box has the description for "polygon" #8
• Suggest to also allow http://schema.org/geo on Organization (however it is on Place and therefore applicable on any LocalBusiness already)
• GeoShape and GeoCoordinates should allow a postalCode for rough positioning.
• a GeoCircle would improve upon existing simple 'circle' property of GeoShape, as publishers could define radius and (various approaches to) centre without pushing it all into textual micro-syntax.

Related schema.org vocabulary for locally oriented info:

• Physical Web e.g. via beacons such as https://github.com/google/physical-web - what kind of richer schemas are needed to support these use cases?
• Accessibility of Places - schema.org expects to do some work to support scenarios such as 'is there a wheelchair ramp?', see Accessibility of places #254
• Opening Hours markup needs improving - schema.org has two ways to represent openingHours - need unified documentation and cornercase tweak #245