geo-extension-nonWGS84 - Revision history

Artoria2e5: /* Harmonization with Geo URI and h-geo */

2021-02-17T04:18:55Z

Harmonization with Geo URI and h-geo

← Older revision		Revision as of 04:18, 17 February 2021
Line 144:		Line 144:
	As ''geo'' has always been supposed to match vCard's geo thing (currently RFC 5870), I believe we should change the "reference frame" class name to simply "p-crs". The semantics are pretty well-defined there.		As ''geo'' has always been supposed to match vCard's geo thing (currently RFC 5870), I believe we should change the "reference frame" class name to simply "p-crs". The semantics are pretty well-defined there.

	As for the class-less format, I propose just referring to RFC 5870 parsing. Stick a geo: prefix to the front and parse it.		As for the class-less format, I propose just referring to RFC 5870 parsing. Stick a geo: prefix to the front and parse it. --[[User:Artoria2e5\|Artoria2e5]] ([[User talk:Artoria2e5\|talk]]) 04:18, 17 February 2021 (UTC)

	==Related pages==		==Related pages==

Artoria2e5: /* Harmonization with Geo URI and h-geo */ add comment

2021-02-17T04:18:40Z

Harmonization with Geo URI and h-geo: add comment

← Older revision		Revision as of 04:18, 17 February 2021
Line 143:		Line 143:
	===Harmonization with Geo URI and h-geo ===		===Harmonization with Geo URI and h-geo ===
	As ''geo'' has always been supposed to match vCard's geo thing (currently RFC 5870), I believe we should change the "reference frame" class name to simply "p-crs". The semantics are pretty well-defined there.		As ''geo'' has always been supposed to match vCard's geo thing (currently RFC 5870), I believe we should change the "reference frame" class name to simply "p-crs". The semantics are pretty well-defined there.

			As for the class-less format, I propose just referring to RFC 5870 parsing. Stick a geo: prefix to the front and parse it.

	==Related pages==		==Related pages==

Artoria2e5 at 04:17, 17 February 2021

2021-02-17T04:17:44Z

← Older revision		Revision as of 04:17, 17 February 2021
Line 3:		Line 3:
	Further to proposals for [[luna]] and [[mars]] equivalents to [[geo]], the following is a "straw-man" proposal, to incorporate those ideas (and likewise for other bodies) into geo, and to make Geo available for other terrestrial schema than WGS84, in order that further debate may take place. Please feel free to critique it harshly but fairly!		Further to proposals for [[luna]] and [[mars]] equivalents to [[geo]], the following is a "straw-man" proposal, to incorporate those ideas (and likewise for other bodies) into geo, and to make Geo available for other terrestrial schema than WGS84, in order that further debate may take place. Please feel free to critique it harshly but fairly!

			__TOC__
	==Author==		==Author==
	[[User:AndyMabbett\|Andy Mabbett]]		[[User:AndyMabbett\|Andy Mabbett]]
Line 139:		Line 140:

	As suggested already it is important to define a reference frame. The term ''coordinate-frame'' (or ''coord-frame'') might also avoid ambiguities that exist for the word ''reference''. In astronomical applications it is necessary to provide both a frame (e.g. FK5) and an equinox/epoch (e.g. 2000.0). Astronomical coordinate frames that are widely supported are: ICRS, FK5, FK4, ECL, GAL, SGAL.		As suggested already it is important to define a reference frame. The term ''coordinate-frame'' (or ''coord-frame'') might also avoid ambiguities that exist for the word ''reference''. In astronomical applications it is necessary to provide both a frame (e.g. FK5) and an equinox/epoch (e.g. 2000.0). Astronomical coordinate frames that are widely supported are: ICRS, FK5, FK4, ECL, GAL, SGAL.

			===Harmonization with Geo URI and h-geo ===
			As ''geo'' has always been supposed to match vCard's geo thing (currently RFC 5870), I believe we should change the "reference frame" class name to simply "p-crs". The semantics are pretty well-defined there.

	==Related pages==		==Related pages==

Alf: Fixed link to JPL's horizons

2011-04-28T09:48:32Z

Fixed link to JPL's horizons

← Older revision		Revision as of 09:48, 28 April 2011
Line 55:		Line 55:
	</blockquote>		</blockquote>

	You can also check the description in JPL Horizons document, which uses planetographic longitude rather than planetocentric longitude, and gives much more longitude ranges used for different planets and moons, at http://ssd.jpl.nasa.gov/horizons_doc.~~html#sitecoord~~		You can also check the description in JPL Horizons document, which uses planetographic longitude rather than planetocentric longitude, and gives much more longitude ranges used for different planets and moons, at http://ssd.jpl.nasa.gov/?horizons_doc.

	==Comments==		==Comments==

Tantek: Reverted edits by Niuhaibiao (Talk) to last version by Fdrake

2010-01-14T23:08:42Z

Reverted edits by Niuhaibiao (Talk) to last version by Fdrake

← Older revision		Revision as of 23:08, 14 January 2010
Line 77:		Line 77:
	(reproduced from e-mail to [[User:AndyMabbett\|Andy Mabbett]], by kind permission)		(reproduced from e-mail to [[User:AndyMabbett\|Andy Mabbett]], by kind permission)

	*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on ~~[http://www.skldintl.com~~ solar ~~garden light]~~system bodies is interesting.		*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on solar system bodies is interesting.
	*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).		*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).
	*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.		*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.

Niuhaibiao: /* Brent A. Archinal */

2010-01-14T06:22:35Z

Brent A. Archinal

← Older revision		Revision as of 06:22, 14 January 2010
Line 77:		Line 77:
	(reproduced from e-mail to [[User:AndyMabbett\|Andy Mabbett]], by kind permission)		(reproduced from e-mail to [[User:AndyMabbett\|Andy Mabbett]], by kind permission)

	*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on solar system bodies is interesting.		*I appreciate the information you've provided and certainly the general idea of using "microformats" to indicate geographical location of points on [http://www.skldintl.com solar garden light]system bodies is interesting.
	*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).		*As to any comments on the general idea or any specific implementation, I think my colleague, Trent Hare, has already addressed any primary concerns or questions (above).
	*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.		*The main issue seems to be that both the body, and the specific definition (technically a "reference frame") in question need to be specified, e.g. 1) Earth, ITRF2005, 2) Moon, ULCN 2005, 3) Mars, "IAU2000" or similar. Note that these frames are actually realizations of various "reference systems" 1) ITRS, 2) mean Earth/polar axis system, 3) IAU2000 Mars body fixed, respectively), but the system is apparent once the frame has been identified.

Fdrake: fix typo: wither -> with

2009-08-20T17:40:23Z

fix typo: wither -> with

← Older revision		Revision as of 17:40, 20 August 2009
Line 25:		Line 25:

	===Notes===		===Notes===
	# A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e.g. "Earth", "Mars", "Moon", "Venus", etc.) ~~wither~~ "Earth" being assumed if none is specified.		# A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e.g. "Earth", "Mars", "Moon", "Venus", etc.) with "Earth" being assumed if none is specified.
	# A list of acceptable values for 'reference frame' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present (geo for Earth uses the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] by default. This extension would also allow for other terrestrial schema, of which there are many, such as OSGB36).		# A list of acceptable values for 'reference frame' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present (geo for Earth uses the datum of [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84] by default. This extension would also allow for other terrestrial schema, of which there are many, such as OSGB36).
	# As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be separated by a semi-colon and latitude MUST be first:<code><nowiki><span class=geo">37.386013;-122.082932</span></nowiki></code>		# As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be separated by a semi-colon and latitude MUST be first:<code><nowiki><span class=geo">37.386013;-122.082932</span></nowiki></code>

RichardFlapper: /* multiple representations of the same location */

2008-05-21T21:51:47Z

multiple representations of the same location

← Older revision		Revision as of 21:51, 21 May 2008
Line 105:		Line 105:

	--[[User:DavidCary\|DavidCary]] 17:06, 5 Apr 2007 (PDT)		--[[User:DavidCary\|DavidCary]] 17:06, 5 Apr 2007 (PDT)

			* Why not use the same approach as used in GML? Use the [http://en.wikipedia.org/wiki/Geography_Markup_Language#Coordinate_Reference_System srsName] attribute when referring to a Coordinate Reference System (CRS) (or Datum). This way a coordinate can be recalculated to whatever CRS.

			--[[User:RichardFlapper\|Richard Flapper]] 23:46, 21 May 2008 (MET)

	===Other===		===Other===
	I'm no expert on these matters, and am not sure if this is the right place for such comments, but these are are a few ideas/issues that came to mind after reading this page:		I'm no expert on these matters, and am not sure if this is the right place for such comments, but these are are a few ideas/issues that came to mind after reading this page:

RichardFlapper: /* thare */

2008-05-21T21:43:56Z

thare

← Older revision		Revision as of 21:43, 21 May 2008
Line 66:		Line 66:
	*** Perhaps "reference frame" would be a less confusing term than "schema"? --[[User:DavidCary\|DavidCary]] 17:06, 5 Apr 2007 (PDT)		*** Perhaps "reference frame" would be a less confusing term than "schema"? --[[User:DavidCary\|DavidCary]] 17:06, 5 Apr 2007 (PDT)
	**** The HTML class attribute is a space seperated list, so 'class="reference frame"' is semantically equivalent to 'class="frame reference"' or 'class="reference" class="frame"' (though the latter is not syntactically valid). This could clash with, say, a theoretical microformat for footnotes, endnotes and references. Hyphenating ('class="reference-frame"') may be an improvement. [[User:TobyInk\|TobyInk]] 12:29, 6 Jun 2007 (PDT)		**** The HTML class attribute is a space seperated list, so 'class="reference frame"' is semantically equivalent to 'class="frame reference"' or 'class="reference" class="frame"' (though the latter is not syntactically valid). This could clash with, say, a theoretical microformat for footnotes, endnotes and references. Hyphenating ('class="reference-frame"') may be an improvement. [[User:TobyInk\|TobyInk]] 12:29, 6 Jun 2007 (PDT)
			***** Often a reference system like WGS84 is referred to as [http://en.wikipedia.org/wiki/Datum datum] [[User:RichardFlapper\|Richard Flapper]] 23:28 21 May 2008 (MET)
	*I would suggest just using "''Moon''". For other spellings for planetary bodies I would look toward the IAU/IAG documentation (an international working group) [http://astrogeology.usgs.gov/Projects/WGCCRE/ IAU/IAG Working Group (WG) on Cartographic Coordinates and Rotational Elements]		*I would suggest just using "''Moon''". For other spellings for planetary bodies I would look toward the IAU/IAG documentation (an international working group) [http://astrogeology.usgs.gov/Projects/WGCCRE/ IAU/IAG Working Group (WG) on Cartographic Coordinates and Rotational Elements]
	*Since this is a simple case, I tried to stay away from this issue but just can't. What does Earth really mean? There a many definitions for the size of Earth that need to be resolved when using lat/lon coordinates. Is the size of the Earth defined by the WGS84 or NAD27 definition? For Mars, is it the definition used in 1991 or redefined in 2000? This has previously been solved in web GIS applications by using an "EPSG" code. For planetary bodies we are attempting to define a similar coded standard which currently is called the IAU2000 code or namespace. Thus for Mars the code might be IAU2000:49900.		*Since this is a simple case, I tried to stay away from this issue but just can't. What does Earth really mean? There a many definitions for the size of Earth that need to be resolved when using lat/lon coordinates. Is the size of the Earth defined by the WGS84 or NAD27 definition? For Mars, is it the definition used in 1991 or redefined in 2000? This has previously been solved in web GIS applications by using an "EPSG" code. For planetary bodies we are attempting to define a similar coded standard which currently is called the IAU2000 code or namespace. Thus for Mars the code might be IAU2000:49900.

StuartLowe: /* Comments */ Suggestion to include astronomical reference frames

2008-03-05T22:26:46Z

Comments: Suggestion to include astronomical reference frames

← Older revision		Revision as of 22:26, 5 March 2008
Line 124:		Line 124:

	--[[User:Inkwina\|Inkwina]] 01:54, 30 Nov 2007 (PST)		--[[User:Inkwina\|Inkwina]] 01:54, 30 Nov 2007 (PST)

			===Astronomical Coordinates===
			Comments from [[User:StuartLowe\|Stuart]]

			Rather than limit the format to the surfaces of planets and moons, would it be possible to include astronomical coordinates for objects in celestial coordinate frames? This would be very useful for tagging astronomical objects (e.g. M41 or NGC 7027).

			If you do not want to break the existing ''geo'' tag might I suggest the more generic term ''coord''?

			As suggested already it is important to define a reference frame. The term ''coordinate-frame'' (or ''coord-frame'') might also avoid ambiguities that exist for the word ''reference''. In astronomical applications it is necessary to provide both a frame (e.g. FK5) and an equinox/epoch (e.g. 2000.0). Astronomical coordinate frames that are widely supported are: ICRS, FK5, FK4, ECL, GAL, SGAL.

	==Related pages==		==Related pages==