On Friday, 17 March 2017 15:13:02 UTC+1, Max1234Ita wrote: > > > > when did you do the modifications? >
On 29 February 2017: https://www.openstreetmap.org/changeset/46410912 > OSM maps (those on www.openstreetmap.org site) are updated almost > immediately after you commit your changesets; OsmAnd ones (the "Standard" > version), instead, are once per month (almost), and I also know of other > sites which update their OSM tiles only 1-2 times per year; so it's > possible a OsmAnd DB freeze has occurred after you submitted only part of > your changes. > My modifications were both to Heggerankweg and Ribesstraat, in one changeset: Before: from the crossing with Kamperfoelieweg you could enter Ribesstraat, and then head north into Heggerankweg. After: driving direction in Heggerankweg and Ribesstraat were flipped, so you can now drive south on Heggerankweg onto Ribesstraat, and then head east. If it were merely a matter of waiting for the changes to appear I wouldn't be worried. However, it now seems that only half the changeset was applied. > You have now 3 possible solutions: > > - Grab a .pbf data file for your region and try compiling the desired > map yourself wit OsmAndMapCreator; (alternatively, you can look around for > another user who has done it and shared the result); > > - Subscribe to OsmandLive service (paid), which provides fresh maps > several times per day; > > > - Wait until next Standard map update for OsmAnd occurs, and check if > all of your changes are present; > > In all the three cases above, I expect all data to be correctly shown; if > not, just check for some mapping error... > 1088 I'm already a OsmanLive subscriber, and there the data is also wrong (but that's in beta, so I didn't want to nag about that). Furthermore, there has already been a standard map rotation for OsmAnd, and that didn't provide any solution. I've downloaded Netherlands.pbf and extracted a part of the file around the offending area. However, I couldn't properly convert it with OsmAndMapCreator; it complained loudly about SQL exceptions like these: SEVERE: Could not save in db (entity NODE 568296316) java.sql.SQLException: UNIQUE constraint failed: node.id The entire log, with PBF and OBF files can be downloaded from https://stack.stuvel.eu/s/ltQd438Su8rilZD if you're interested. Cheers, Sybren -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
