[GeoJSON] Aligning implementations
ad at ionicsoft.com
Wed Apr 11 00:32:54 PDT 2007
since I've been reading this thread, I've seen nowhere that a client would make use of feature type information; hence the necessity to have the toplevel 'geometry' property, or the toplevel 'default_geom' property to access the corresponding property in the object.
Since I'm pretty new to this list, maybe I missed something, but.. why does nobody take feature type information into consideration?
I strongly believe a sufficiently advanced feature inspecting/editing client will *require* that information.
From: geojson-bounces at lists.geojson.org on behalf of Tim Schaub
Sent: Tue 4/10/2007 8:31 PM
To: geojson at lists.geojson.org
Subject: Re: [GeoJSON] Aligning implementations
Chris Holmes wrote:
>>> [multiple geometries]
>>> what do I do?
>> id: string,
>> geometry: array,
>> properties: object
> Yeah, I don't really like that so much. If you have multiple geometries
> people will probably want names for them. Ie which one's the building
> and which one's the lot. If you just have an array you don't know which
> is which.
I don't like it either. But if you want geometries to have arbitrary
names, then a geometry object would look like:
and you could iterate through all your geometry objects in the
feature.geometry array to find the name you want.
If you really want geometries to be keyed by arbitrary names, then
you'll have to iterate through all keys to get all geometries anyway.
Again, I don't like this, but I think it is preferable to iterating
through all the keys of the properties object and testing each value to
see whether or not it is a geometry. What if I want to name my geometry
link or title? Are those forbidden names for geometry because they are
also optional properties?
geojson mailing list
geojson at lists.geojson.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geojson