Hi,
As I wrote, I got a motivation for my first mail because I have seen that
people are quite often using GeoJSON for delivering geospatial data as data, to
be saved on disk and used like shapefiles, GML etc. As a result you get stuff
like this:
http://demo.opengeo.org/geoserver/wfs?service=
Hi Even, Jukka,
While the OGC service architecture is heavily dependent on schemas, OGR
type schemas are not *generally* useful for GeoJSON. Consider the following
abbreviated feature collection:
"features": [
{"properties": {"a": 0, "b": "lol"}, ...},
{"properties": {"c": "2014-11-21",
Even Rouault
> Le vendredi 21 novembre 2014 15:35:43, Rahkonen Jukka (Tike) a écrit :
> > Hi,
> >
> > I have no use for this feature myself but by reading various mailing
> > lists and forums I have learned that many people consider it is always
> > a good idea to read data for example from WFS s
Hi
The normal reason to select GeoJSON for geoweb applications is that JSON
is parsed directly by the web browser, i.e. you get JavaScript objects
directly digestable by your JavaScript code. This may be also
considerable faster than parsing XML.
Bandwidth is more or less irrelevant in compari
Le vendredi 21 novembre 2014 15:35:43, Rahkonen Jukka (Tike) a écrit :
> Hi,
>
> I have no use for this feature myself but by reading various mailing lists
> and forums I have learned that many people consider it is always a good
> idea to read data for example from WFS services as GeoJSON instead
Hi,
I have no use for this feature myself but by reading various mailing lists and
forums I have learned that many people consider it is always a good idea to
read data for example from WFS services as GeoJSON instead of GML. I can easily
imagine that there will be troubles with guess-by-data m
Jukka,
Data type guessing implemented in the OGR GeoJSON driver is quite natural
hopefully.
A whole scan of the GeoJSON file is made and the following rules are applied :
- if an attribute has integer-only content --> Integer
- if an attribute has an array of integer-only content --> IntegerList
Hi,
I wonder if GDAL could have some simple and relatively user friendly way for
defining a schema for GeoJSON data. The GeoJSON driver seems to guess the
data types of attributes with some undocumented way but users could have
better knowledge about the desired schema.
I know I can control the d
