Just for grins, I coded up a simple example of YAML for tabular
geospatial data.
Seems like this might be another direction to go in. YAML has solved a
lot of the tricky little issues you get into when serializing data to a
text format.
The one thing they don't have AFAICS is a way of encoding "out-of-band"
attributes on data elements. This would make it ugly to provide
metadata items like a fid or particularly a SRID. But there may be
simple conventions which would work around this.
I was pleased to see that YAML allows you to express element datatypes
inline (which makes a nice way of supporting WKT and WKB in the same schema)
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
# YAML example for tabular geospatial data
--- !!cities
- !!city
# Notice the use of a wkt datatype. wkb could be supported as well
geometry: !!wkt POINT( 1008983.125 455516.906 0.0 )
fcode: AR08750000
name: Tofino
pop2000: 1540
- !!city
geometry: !!wkt POINT( 1024338.125 1028831.0 0.0 )
fcode: AR08750000
name: Victoria
pop2000: 350000
- !!city
# Large geometries can be handled over multiple lines
geometry: !!wkt |
POLYGON ((
1168880.5 375965.906 0,
1036351 441199.656 0,
1008983.125 455516.906 0,
595521.313 933632.438 0,
592512 980219 0,
563199.813 1643181.25 0,
1190712.5 1540146.375 0,
1790964.875 637044.375 0,
1798382 584774.375 0,
1789736.125 559290.188 0,
1691089.875 500872.719 0,
1180498 376722 0,
1168880.5 375965.906 0
))
fcode: AR08750000
name: Vancouver
pop2000: 2000000
...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
