<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Re: [GeoJSON] Aligning implementations</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText44261 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Hello everyone,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>since I've been reading this thread, I've
seen nowhere that a client would make use of feature type information;
h</FONT><FONT face=Arial size=2>ence the necessity to have the toplevel
'geometry' property, or the toplevel 'default_geom' property to access the
corresponding property in the object.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV><FONT face=Arial size=2>
<DIV dir=ltr><FONT face=Arial size=2>Since I'm pretty new to this list, maybe I
missed something, but.. why does nobody take feature type information into
consideration? </FONT></FONT><FONT face=Arial size=2></DIV></DIV>
<DIV dir=ltr>I strongly believe a sufficiently advanced feature
inspecting/editing client will *require* that information. </DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>Best regards,</DIV>
<DIV dir=ltr> A.</DIV></FONT>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> geojson-bounces@lists.geojson.org on
behalf of Tim Schaub<BR><B>Sent:</B> Tue 4/10/2007 8:31 PM<BR><B>To:</B>
geojson@lists.geojson.org<BR><B>Subject:</B> Re: [GeoJSON] Aligning
implementations<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Chris Holmes wrote:<BR>>>> [multiple
geometries]<BR>>>> what do I do? <BR>>><BR>>>
{<BR>>> id:
string,<BR>>> geometry:
array,<BR>>> properties: object<BR>>>
}<BR>>><BR>><BR>> Yeah, I don't really like that so much. If
you have multiple geometries<BR>> people will probably want names for
them. Ie which one's the building<BR>> and which one's the lot.
If you just have an array you don't know which<BR>> is which.<BR><BR>I don't
like it either. But if you want geometries to have arbitrary<BR>names,
then a geometry object would look like:<BR><BR>{<BR>
type: string,<BR> data:
array,<BR> name: string<BR>}<BR><BR>and you could
iterate through all your geometry objects in the<BR>feature.geometry array to
find the name you want.<BR><BR>If you really want geometries to be keyed by
arbitrary names, then<BR>you'll have to iterate through all keys to get all
geometries anyway.<BR><BR>Again, I don't like this, but I think it is preferable
to iterating<BR>through all the keys of the properties object and testing each
value to<BR>see whether or not it is a geometry. What if I want to name my
geometry<BR>link or title? Are those forbidden names for geometry because
they are<BR>also optional
properties?<BR><BR><BR>Tim<BR>_______________________________________________<BR>geojson
mailing list<BR>geojson@lists.geojson.org<BR><A
href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</A><BR></FONT></P></DIV>
</BODY>
</HTML>