Re: [OSM-dev] Current planet file is broken (was: osmosis cutting planet)
On Fri, Apr 24, 2009 at 12:00 AM, Frederik Ramm wrote: > Frederik Ramm wrote: > This is due to a bug in the planet dump script which I have fixed (review > before use, please). d'oh :-) cheers, matt ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] SVN and individual tag/branch trees
On Fri, Apr 24, 2009 at 01:45:40AM +0200, Frederik Ramm wrote: > Is there a way I can tell SVN to "check out everything *except* tags and > branches"? Ideally in a way that SVN remembers, so that when I > absent-mindedly type "svn update" I'll not get the whole bunch again? I’ve read about sparse directory support in Subversion before[1], but have not used it. It looks like it should help, but won’t get you a repository excluding tags and branches in one foul swoop. [1]: http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html Simon -- A complex system that works is invariably found to have evolved from a simple system that works.—John Gall signature.asc Description: Digital signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] SVN and individual tag/branch trees
Hi, I normally keep the whole SVN tree checked out on all computers I use regularly. But with projects gradually introducing their own branches/trunk/tag structure, this means that I am amassing a lot of stuff. For example, the Osmosis trunk has roughly 1600 files, but if you simply check out the whole SVN then you have 8100 Osmosis files due to various tags and branches; same, to a lesser degree, elsewhere. Is there a way I can tell SVN to "check out everything *except* tags and branches"? Ideally in a way that SVN remembers, so that when I absent-mindedly type "svn update" I'll not get the whole bunch again? Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Current planet file is broken
Again, Frederik Ramm wrote: > And that's what it is; the whole "relation" section of the > planet-090421.osm.bz2 planet file is broken, it has types where it > should have ids and vice versa: Those of you who have downloaded the broken planet file might be able to fix it: 1. unzip planet file to planet.osm 2. verify it has 124128254400 bytes 3. download and unzip http://www.remote.org/frederik/tmp/fixplanet.gz 4. dd if=fixplanet of=planet.osm.osm conv=notrunc bs=1048576 seek=118294 This replaces the broken "relations" section by one with swapped types and ids. I haven't yet fully processed the resulting planet so I cannot promise it will be perfect afterwards but maybe it is worth a try ;-) Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Current planet file is broken (was: osmosis cutting planet)
Hi, Frederik Ramm wrote: > From the source it seems that somewhere in the relation section we have > something like > > And that's what it is; the whole "relation" section of the planet-090421.osm.bz2 planet file is broken, it has types where it should have ids and vice versa: This is due to a bug in the planet dump script which I have fixed (review before use, please). Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] osm_schema_latest.sql
Try: http://gweb.bretth.com/apidb06-postgresql-latest.sql or http://gweb.bretth.com/apidb06-mysql-latest.sql PostgreSQL is preferred at this point because it is used by the production database and is better tested at my end. Joachim Zobel wrote: > Hi. > > Do you already have a > > http://gweb.bretth.com/osm_schema_latest.sql > > for the 0.6 API database. The above is still MySQL and looks outdated. > > Thanks, > Joachim > > > > ___ > dev mailing list > dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/dev > ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] osmosis - smallint again
Apologies, when I made the 0.5 change I assumed it was going to be fixed as part of the migration for 0.6 so left the 0.6 schema as smallint. I've updated the script in svn to use int for the sequence_id column on both way_nodes and relation_members tables. Florian Lohoff wrote: > Hi, > i tried to import a current planet 090421 to a postgres with the 0.6 simple > schema (no linestring, no bbox) and it failed again because of the smallint > thing we have discussed in the past - there are ways with more nodes than > smallint ... Osmosis svn 0.30.3 altering the table now ... > ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] osm_schema_latest.sql
Hi. Do you already have a http://gweb.bretth.com/osm_schema_latest.sql for the 0.6 API database. The above is still MySQL and looks outdated. Thanks, Joachim ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] osmosis cutting planet
Hi, Florian Lohoff wrote: > java.lang.NumberFormatException: For input string: "Way" From the source it seems that somewhere in the relation section we have something like I'd love to investigate but the planet download from heanet.ie has been going on for 6 hours now and slowed to a trickle; wget claims it is going to be another 9 hours. Might also be congestion on my end, don't know. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] London Hack Weekend - 30th 31st May
Hi Devs, Announcing an upcoming Hack Weekend for the final weekend (not a bank holiday) in May. Full details are on the wiki. Venue is the CloudMade offices in central London. http://wiki.openstreetmap.org/wiki/London_Hack_Weekend It's great to see all the suggestions and interest that the 0.6 API has thrown up, and there's a few outstanding other things we can work on. In any case, I'm sure there will be beer and pizzas. So put the dates in your diary, and all devs are welcome - especially anyone who's keen to dive in but wants some help / guidance / advice! Cheers, Andy ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] Commit message not empty
2009/4/23 ce-test, qualified testing bv - Gert Gremmen : > In JOSM however, we can ease the user in maintaining > a self updating drop down box, and a number > of standard comments with . behind it > to stimulate completing. > > Updating highways .. (user fills-in :) > > Updating highways = cycleways near Moskou I've had some ideas along similar lines, though I see more automation being used. Like Frederik, I think that comments are important - important enough for us to strongly encourage mappers to use them and appreciate their value. So I figure we should try to devise a repeatable, automatable style of default commit message which would be proposed to users prior to upload (in JOSM - Potlatch could silently use it if desired) with an encouragement to adapt or replace it with something better. Possible formats: Small|Medium|Large update within x km radius of Update of x nodes, y ways, z relations within n km of Adding town or city names for better orientation makes it a lot better, and would be feasible without external lookups in any cases where the downloaded data set contained any place nodes of significance. What do people think? My intent here is that the automatic "guessed" message would be as close as feasible to the kind of informative message you'd like the user to learn to use. (I'll duck any "patches welcome" answer right away by disclaiming all Java skills, but hopefully somebody else will value the idea enough to try coding it). Cheers, Dermot -- -- Iren sind menschlich ___ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [OSM-dev] osmosis - smallint again
Hi, Florian Lohoff wrote: > i tried to import a current planet 090421 to a postgres with the 0.6 simple > schema (no linestring, no bbox) and it failed again because of the smallint > thing we have discussed in the past - there are ways with more nodes than > smallint ... Osmosis svn 0.30.3 altering the table now ... The API does not allow the creation or modification of such ways any longer. All it needs is a one-time effort to split up the existing long ways and the problem is gone for good. Bye Frederik ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] osmosis cutting planet
Strange. "Way" is indeed not a number. Any way to identify the offending XML-element? Marcus On Thu, 23 Apr 2009 14:36:51 +0200, Florian Lohoff wrote: > Hi, > i tried cutting germany from the 090421 planet on planet.openstreetmap.org > with > svn osmosis (0.30.3) and it failed somewhere at the end: > SEVERE: Thread for task 1-read-xml-0.6 failed > java.lang.NumberFormatException: For input string: "Way" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Long.parseLong(Long.java:403) > at java.lang.Long.parseLong(Long.java:461) > at > org.openstreetmap.osmosis.core.xml.v0_6.impl.RelationMemberElementProcessor.begin(RelationMemberElementProcessor.java:52) > at ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] osmosis - smallint again
Hi, i tried to import a current planet 090421 to a postgres with the 0.6 simple schema (no linestring, no bbox) and it failed again because of the smallint thing we have discussed in the past - there are ways with more nodes than smallint ... Osmosis svn 0.30.3 altering the table now ... f...@tiles-two:~/initialimport$ osmosis --read-xml-0.6 file=planet-090421.osm.gz --write-pgsql database=osm user=flo password=flo Apr 22, 2009 9:05:13 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version 0.30.3 Apr 22, 2009 9:05:14 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Preparing pipeline. Apr 22, 2009 9:05:14 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Launching pipeline execution. Apr 22, 2009 9:05:14 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Pipeline executing, waiting for completion. Apr 23, 2009 7:42:03 AM org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion SEVERE: Thread for task 1-read-xml-0.6 failed org.openstreetmap.osmosis.core.OsmosisRuntimeException: Unable to bulk insert way nodes into the database. at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.flushWayNodes(PostgreSqlWriter.java:638) at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.addWayNodes(PostgreSqlWriter.java:570) at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.flushWays(PostgreSqlWriter.java:504) at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.process(PostgreSqlWriter.java:943) at org.openstreetmap.osmosis.core.container.v0_6.WayContainer.process(WayContainer.java:60) at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.process(PostgreSqlWriter.java:907) at org.openstreetmap.osmosis.core.xml.v0_6.impl.WayElementProcessor.end(WayElementProcessor.java:105) at org.openstreetmap.osmosis.core.xml.v0_6.impl.OsmHandler.endElement(OsmHandler.java:108) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.openstreetmap.osmosis.core.xml.v0_6.XmlReader.run(XmlReader.java:108) at java.lang.Thread.run(Thread.java:636) Caused by: org.postgresql.util.PSQLException: ERROR: smallint out of range at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1592) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1327) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:192) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:350) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:304) at org.openstreetmap.osmosis.core.pgsql.v0_6.PostgreSqlWriter.flushWayNodes(PostgreSqlWriter.java:636) ... 21 more Apr 23, 2009 7:42:03 AM org.openstreetmap.osmosis.core.Osmosis main SEVERE: Execution aborted. org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks failed. at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146) at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:85) at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:30) -- Florian Lohoff f...@rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin signature.asc Description: Digital signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] Commit message not empty
I see a clear parallel to software commenting ;<( Anyone understands and appreciated the comments when they are there, but no programmer ever is enough "on-focus" to spoil time in commenting I have some experience in software analysis for medical equipment, and software quality is clearly correlated to the amount of comments In JOSM however, we can ease the user in maintaining a self updating drop down box, and a number of standard comments with . behind it to stimulate completing. Updating highways .. (user fills-in :) Updating highways = cycleways near Moskou But it isn't easy, as I find myself mixing updates, adding all kind of stuff, and fix some tags, add a traffic light and do some cycle routing (relation) in one and the same session What to comment in such diversity ? Maintenance in Moskou ??? Gert Gremmen - Openstreetmap.nl (alias: cetest) Before printing, think about the environment. -Oorspronkelijk bericht- Van: josm-dev-boun...@openstreetmap.org [mailto:josm-dev-boun...@openstreetmap.org] Namens Frederik Ramm Verzonden: Thursday, April 23, 2009 11:40 AM Aan: Rolf Bode-Meyer CC: josm-dev Onderwerp: Re: [josm-dev] Commit message not empty Hi, Rolf Bode-Meyer wrote: > That's exactly what I think can be a problem for users. > Users should have an idea of what type of comment is expected and > connected to this what it will be used for, where it will appear. Let them learn by doing. Let them write "bicycle ride" or "afternoon in the rain" on their first commits. They will sooner or later find out what this is about. And forcing them to enter *something* will make them think; will make them bring up the question the next time they have a beer with fellow mappers. Allowing them to simply hit enter will make them ignore the topic and forget about it. The "leave empty if unsure" makes it easy for users to ignore the concept and I don't want to make this easy for them. Bye Frederik ___ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[OSM-dev] osmosis cutting planet
Hi, i tried cutting germany from the 090421 planet on planet.openstreetmap.org with svn osmosis (0.30.3) and it failed somewhere at the end: f...@tiles-one:~/import$ ../osmosis/osmosis-0.30.3/bin/osmosis --read-xml-0.6 file=planet-090421.osm.gz --bp file=germany2pts.txt --write-xml-0.6 file=g ermany-090421.osm.bz2 Apr 22, 2009 8:39:56 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version 0.30.3 Apr 22, 2009 8:39:56 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Preparing pipeline. Apr 22, 2009 8:39:56 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Launching pipeline execution. Apr 22, 2009 8:39:56 PM org.openstreetmap.osmosis.core.Osmosis run INFO: Pipeline executing, waiting for completion. Apr 23, 2009 6:24:20 AM org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion SEVERE: Thread for task 1-read-xml-0.6 failed java.lang.NumberFormatException: For input string: "Way" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Long.parseLong(Long.java:403) at java.lang.Long.parseLong(Long.java:461) at org.openstreetmap.osmosis.core.xml.v0_6.impl.RelationMemberElementProcessor.begin(RelationMemberElementProcessor.java:52) at org.openstreetmap.osmosis.core.xml.v0_6.impl.OsmHandler.startElement(OsmHandler.java:91) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at org.openstreetmap.osmosis.core.xml.v0_6.XmlReader.run(XmlReader.java:108) at java.lang.Thread.run(Thread.java:619) Apr 23, 2009 6:24:20 AM org.openstreetmap.osmosis.core.Osmosis main SEVERE: Execution aborted. org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks failed. at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146) at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:85) at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:30) -- Florian Lohoff f...@rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin signature.asc Description: Digital signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Full History Files
Andy Allan wrote: > On Thu, Apr 23, 2009 at 2:04 AM, Brett Henderson wrote: > > >> * Create a new tool that dumps into a full history osm format. It would >> differ from existing planet files by having multiple versions of each >> entity (rather than just the latest) and each would have the visible >> flag set. >> > > A full history dump with all the changeset info would be nice, IMHO. > In the same way that most people eventually "graduate" from using > planet files to using diffs, it's a straightforward concept to get > your head around (everything in one file) so probably lowers the > barrier to entry. > From which they could then graduate to history files ;-) I'll take a look. It should be fairly straightforward to get to a single snapshot file in several steps. I'm not sure when I'll get time to do it though. 1. Combine the daily files I already have into a larger dataset. 2. Re-sort by entity type, then id, then version (uses temporary disk space to perform persistent low-memory merge sort). 3. Process the large history file into an osm file with history and the visible flag set as appropriate. Step 2 is time and disk consuming because a merge sort of large data sets requires a lot of temporary disk space. Of course the other option is to modify the existing planet dumper to do it instead, the downside being that it requires hitting the database heavily instead of working offline. Osmosis is unlikely to ever directly support an OSM file with multiple versions of a single entity. It requires the addition of the visible flag which makes no sense for most processing. I'd rather keep that concept out of the osmosis pipeline because that's what the change streams are supposed to achieve. I'd just write a custom task for step 3 above which receives a standard change stream and writes it in the special osm history format. Brett ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Full History Files
On Thu, Apr 23, 2009 at 2:04 AM, Brett Henderson wrote: > * Create a new tool that dumps into a full history osm format. It would > differ from existing planet files by having multiple versions of each > entity (rather than just the latest) and each would have the visible > flag set. A full history dump with all the changeset info would be nice, IMHO. In the same way that most people eventually "graduate" from using planet files to using diffs, it's a straightforward concept to get your head around (everything in one file) so probably lowers the barrier to entry. Cheers, Andy ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Changeset Revert Tool
On Wed, Apr 22, 2009 at 7:43 AM, Frederik Ramm wrote: > Something like > > * user tells application "please revert changeset" > * application redirects user to API > * API tells user "please authenticate for application X" > * user enters credentials > * API redirects user back to application, with magic token > * application makes API requests using magic token > > I don't know how far existing technologies can be used to achieve this; > I believe OpenAuth only goes so far as to tell the application "yes, > that guy really is user abc123 at my site", it doesn't do the second bit. OAuth does the second bit too. :-) we can certainly limit the scope of the OAuth token to a particular changeset, or to particular API calls, allowing users pretty fine-grained control over what 3rd party apps are allowed to do on their behalf. cheers, matt ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] "Expect error 417" is back
Frederik Ramm wrote: > Tom Hughes wrote: >> Could you explain what you're talking about exactly? If you're talking >> about the api then no, it isn't running apache. It's running lighttpd >> as it has done for the last couple of years. > > "The PHP curl library [...] uses a special HTTP 1.1: 100 (Continue) > Status on POST requests, that have a certain size. Some webservers (like > lighttpd) do not support this behaviour and return HTTP error codes (417 > in case of lighttpd)." Well nothing has changed in terms of what web server we are running, so it's not clear to me why this would have "come back". Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] "Expect error 417" is back
Hi,
Tom Hughes wrote:
> Could you explain what you're talking about exactly? If you're talking
> about the api then no, it isn't running apache. It's running lighttpd as
> it has done for the last couple of years.
"The PHP curl library [...] uses a special HTTP 1.1: 100 (Continue)
Status on POST requests, that have a certain size. Some webservers (like
lighttpd) do not support this behaviour and return HTTP error codes (417
in case of lighttpd)."
Experts disagree on whose fault it is (curl's or lighttpd's).
The problem can be fixed by patching lighthttpd (problem is reportedly
fixed for 1.5 in SVN), or by patching curl, or by manually setting the
header to nothing from PHP like this:
curl_setopt($curl_handle, CURLOPT_HTTPHEADER, array('Expect:'));
Bye
Frederik
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] "Expect error 417" is back
Till Harbaum / Lists wrote: > osm2go stopped working with "error 417" in all transactions. This likely > means that curl is having the problem with http expect again. > > Did you switch back from apache to that old broken server? Could you explain what you're talking about exactly? If you're talking about the api then no, it isn't running apache. It's running lighttpd as it has done for the last couple of years. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
