/* Data Copyright OpenStreetMap Contributors, Some Rights Reserved.
CC-BY-SA 2.0. */
This content needs to be in the file. Feel free to suggest
alternative ways to format or present it but I don't think straight
removal is possible.
This breaks one of our tools that uses the php json_decode
On 26 February 2010 23:17, Brian Quinion
openstreet...@brian.quinion.co.uk wrote:
This content needs to be in the file. Feel free to suggest
alternative ways to format or present it but I don't think straight
removal is possible.
Encode it as part of the JOSN?
I'm uncertain why the json
Hi,
Brian Quinion wrote:
This content needs to be in the file. Feel free to suggest
alternative ways to format or present it but I don't think straight
removal is possible.
I doubt that it needs to be in the file; the OSM API hands out OSM
data without such comments and has worked quite
Brian Quinion schrieb:
/* Data Copyright OpenStreetMap Contributors, Some Rights Reserved.
CC-BY-SA 2.0. */
This content needs to be in the file. Feel free to suggest
alternative ways to format or present it but I don't think straight
removal is possible.
This breaks one of our tools
This content needs to be in the file. Feel free to suggest
alternative ways to format or present it but I don't think straight
removal is possible.
I doubt that it needs to be in the file; the OSM API hands out OSM data
without such comments and has worked quite well for a few years now!
Because we already developed a tool that bases on the json response and now
it's broken. Why do you offer the json response type if you don't deliver
json? this is neither javascript (it's lacking an assignment operator) nor
json, so even the Mime-Type it's delivered with is not correct.
Just
Brian,
Just at the moment I'm at a loss to know why I spend my free (unpaid)
time developing a tool when a small mistake gets me a load of abuse.
Don't be too upset. I believe Peter would have simply fixed it himself
but felt it more appropriate to raise the issue on the list first. I
have
Don't be too upset. I believe Peter would have simply fixed it himself but
felt it more appropriate to raise the issue on the list first. I have now
commented out the offending bit in the code in SVN (but of course it needs
to be deployed on the site to come into force).
Peter, since you
On 26 February 2010 23:57, Brian Quinion
openstreet...@brian.quinion.co.uk wrote:
Just at the moment I'm at a loss to know why I spend my free (unpaid)
time developing a tool when a small mistake gets me a load of abuse.
Sorry if my last message sounded harsh, however JSON is quite useful,
for
Hi,
Brian Quinion wrote:
Above seems like the 0.6 API is isn't compliant with CC-By-SA?
Depends on how strict you read things. I have seen a number of E-Mails
on the lists where people quoted a full OSM object without giving either
attribution or license. It's ok for me. If someone goes to
Frederik Ramm schrieb:
Brian,
Just at the moment I'm at a loss to know why I spend my free (unpaid)
time developing a tool when a small mistake gets me a load of abuse.
Sorry I didn't want to bug you, I just encountered that the tool did not
work any more and wanted to talk here about why
I miss a license notice in every map tile ;)
Am 26.02.10 15:48, schrieb Peter Körner:
Frederik Ramm schrieb:
Brian,
Just at the moment I'm at a loss to know why I spend my free (unpaid)
time developing a tool when a small mistake gets me a load of abuse.
Sorry I didn't
Hi
Nominatim now adds a comment to the json outout, like
/* Data Copyright OpenStreetMap Contributors, Some Rights Reserved.
CC-BY-SA 2.0. */
[{place_id:551851,osm_type:node,osm_id:240111242,boundingbox:[51.0165061950684,...
This breaks one of our tools that uses the php json_decode function,
13 matches
Mail list logo
