Difference between revisions of "Talk:RFC-001"
From GeoJSON
AllanDoyle (Talk | contribs) |
AllanDoyle (Talk | contribs) |
||
Line 8: | Line 8: | ||
[[User:Mpd|Mpd]] | [[User:Mpd|Mpd]] | ||
− | == [User:AllanDoyle] Response == | + | == [[User:AllanDoyle|AllanDoyle]] Response == |
# Shoot. I thought SRS was in vogue and CRS is out. Great. Let's go with crs. I have no preference with linestring, etc. | # Shoot. I thought SRS was in vogue and CRS is out. Great. Let's go with crs. I have no preference with linestring, etc. | ||
# PROJ vs EPSG. PROJ is what coders will see. They may never look at EPSG. Few people will use anything other than PROJ. | # PROJ vs EPSG. PROJ is what coders will see. They may never look at EPSG. Few people will use anything other than PROJ. |
Revision as of 04:51, 11 April 2007
Mpd Comments and Questions
- I'd prefer "crs" to "srs", the latter being out step with, for example, EPSG and OGC terminology. Ditto for "LineString" and "Line", and perhaps (although less so) "Envelope" and "Box"
- Why reference PROJ.4's EPSG tables and not the EPSG tables themselves? Do I sense a coordinate order holy war type thing going on?
- What about Multi[Point|LineString|Polygon] and GeometryCollection?
- What about Polygons with multiple rings? An earlier proposal handled this.
- How does a client determine whether the, for example, six ordinates in a Line/LineString are two x,y,z-s or three x,y-s?
- You suggested an "Authors" section, for CC reasons. Care to add one?
AllanDoyle Response
- Shoot. I thought SRS was in vogue and CRS is out. Great. Let's go with crs. I have no preference with linestring, etc.
- PROJ vs EPSG. PROJ is what coders will see. They may never look at EPSG. Few people will use anything other than PROJ.
- Multi Schmulti, I always say. :)
- Rings Schmings... toss 'em in.
- This is JSON, not GML, so we should (a) use commas and (b) use proper arrays and arrays of arrays.
- Drat. OK. Authors coming right up.