Hi all,
I recommend that JSON item names match the names of methods of the GDAL
API. If not precisely, then at least in a consistent and predictable way.
Introducing new names increases the amount of needed documentation and
generally sows confusion.
For example, Rasterio's rio-info command (you
Hello,
On 30/03/15 10:20, Even Rouault wrote:
Homme's comments :
>
>> Yes, it would be nice to have support (or the possibility of support)
>> for the
>> information concerning the larger gdal data model. This kind of
high level
>> declarative API is really useful in covering a lot common us
Hi Jukka,
On 30/03/15 09:46, Jukka Rahkonen wrote:
Homme Zwaagstra geodata.soton.ac.uk> writes:
>
>>
>>
>>
>> P.S. on the proposal below, perhaps things could be 'standardised'
>> even more by
>> including the cornerCoordinates in both wgs84 and native coordinate
>> systems
>>
Hi,
(giving my feedback on all comments)
>
> 1: Is there any particular reason to implement XML? Every language has a
> good JSON parser these days, as you note in the RFC XML is more complex to
> implement, and it's not like strict schemas or streaming (usual reasons for
> XML) are going to be
Homme Zwaagstra geodata.soton.ac.uk> writes:
>
>
>
> P.S. on the proposal below, perhaps things could be 'standardised'
> even more by
> including the cornerCoordinates in both wgs84 and native coordinate
> systems
> (much like gdalinfo does at the moment). In this way
P.S. on the proposal below, perhaps things could be 'standardised' even
more by
including the cornerCoordinates in both wgs84 and native coordinate systems
(much like gdalinfo does at the moment). In this way you can be
guaranteed of
getting geojson output in its default coordinate system.
Hi,
On 29/03/15 23:58, Robert Coup wrote:
Hi,
>
> Good work, thanks for taking this on!
Yes, this will be very useful!
2: In terms of the proposed gdalinfo JSON...
>
> b) personally I'd prefer to be slightly more verbose in attribute
naming. eg. block -> blockSize, colorInterp -> colorInt
Robert Coup koordinates.com> writes:
>
>
> Hi,
> Good work, thanks for taking this on!
>
> 1: Is there any particular reason to implement XML? Every language has a
good JSON parser these days, as you note in the RFC XML is more complex to
implement, and it's not like strict schemas or streamin
Hi,
Good work, thanks for taking this on!
1: Is there any particular reason to implement XML? Every language has a
good JSON parser these days, as you note in the RFC XML is more complex to
implement, and it's not like strict schemas or streaming (usual reasons for
XML) are going to be in place.
Hi,
I am planning to implement json output for gdalinfo and ogrinfo. I have added
the proposed json format for gdalinfo. I would like to get feedback.
http://trac.osgeo.org/gdal/wiki/rfc44_gdalinfoxml
Regards,
Faza Mahamood
___
10 matches
Mail list logo
