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
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 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
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 of
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
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 services as
Hi,everyone,
*I'm using gdal to open a gtiff with auxilary xml file,but the process is
crashed in CPLFree in Line 1208 @ cpl_minixml.cpp. *
*There is also another weird phenomenon , if i build my gdal dll without
dds driver, it works fine.As long as I add dds format support to my gdal
build,
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, d: wut}, ...}
Hi Simen,
Ok, here is how to implement the suggestion I gave, which was to create a
new worldfile and shift the image so that it fit the footprint vector
better.
1. Use gdal_edit.py with the -unsetgt option to remove the georeferencing
from the .tif
2. Then copy the attached .tfw file into the
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:
Hello, I am a osgeo4w user and very green in the field of geo data.
I am using gdal_grid to grid and ungridded set of points (a CSV file).
I ultimately want to use it with gdaltransform to change the projection
type and gdaltransform does not work with ungridded files from my
understanding.
The
11 matches
Mail list logo