Chris Holmes wrote:
As a side note, I think the Chris Holmes has included JSON as an
output format for Geoserver.
Yeah, I've been meaning to blog about it and make it available for
download, as a plug in to GeoServer. But got swamped last month.
I drew inspiration from Sean's stuff, but wasn't sure how to handle
geometry types other than points. I was going to call mine 'Simple
Features for JSON', in line with Simple Features for SQL, which defined
Well Known Text for representing geographic features. It was easiest
for me to do the same - I just used a .toWKT() function to make my
geometry.
But I'm in no way tied to doing things that way, I just wanted to start
a conversation and hopefully work towards standardization.
At first pass jdil.org feels a bit more heavyweight than I was going
for, doing all the namespaces. And it seems to really just focus on
doing the namespaces. I'd prefer to get general consensus on
namespacing json from a standards organization, I've seen a few others
talk about it and do it slightly different ways.
If there's consensus on that it'd be easy to just write GML output as
JSON, with namespaces and all.
But past that I'd really like to figure out some consensus on how to
encode lines, polygons, and collections of geometries in to JSON. Maybe
that just involves me asking Sean to add some more examples on how he
wants to do that in GeoJSON, as I have no strong preference, just want
to standardize on something.
Chris
Chris,
Other geometries? I'd simply extend the coordinate array, like
GeoRSS-Simple. Count me as one who isn't interested in namespaces. All I
want is a fairly flat data structure, not a mapping of XML.
Cheers,
Sean
--
Sean Gillies
http://zcologia.com/news
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
