-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not displaying changes #21
Comments
Thanks for the report, I will take a look. |
Cheers if you need more info let me know. |
And here is another one. Area: Example of a way in that changeset: |
I triggered the tiler manually for those two changesets. Please check if it includes your changes properly. There is a bug for changesets which are uploaded in many chunks - the tiler runs only once for each changeset so if you open a changeset and then upload some data then it won't be included anymore. It will be fixed in the next major version in a few weeks probably, sorry for the long wait... |
Thanks Pawel. That makes sense. No problem with the wait just glad it will be sorted before it goes live. |
That'll be the day when (or - if!) this gets live ;-) Anyway, when you have a minute, please verify if those two changesets look OK to you. I guess so far no one (except me) has really looked too closely at what is shown, so you are the first in-depth tester :-) |
Sorry I forgot to say they seem fine now. I wasn't concerned for those appearing staright away just that the process to get them fixed longer term is addressed. I'll happily do more testing I have another bug for the map that I will investigate more and post a report. When or if....the ultimate OSM problem. Things move so slowly here. It is sad that many people just give up because of this.Personally I wanted to do stuff with the new carto-CSS map render (adding much needed new elements to the render, fixing errors, etc) ) but it is only useful (as I have no need for a tile server myself) if it actually gets on the homepage but again that can be months or years away and then more bureaucracy will come into play. . Anyway rant over keep up the good work. |
John, I understand what you mean. However, in case of OWL/New History Tab the problem is actually me, or rather my lack of time. This project is very complex and it is currently in a state that is not satisfactory for me. I already got "offers" from OSM.org admins to roll it out to the main page - so there most definitely is hardware and the will to deploy it. It's just that I'm not comfortable with the code - it needs more simplification and testing. So in this case if anyone is to blame for the slow going, it's me :-) |
Aha ok I thought it was still part of the funding drive.to got the hardware up to date.I read a couple of projects are dependant on this. I'll see what i can do with more testing. |
Hi Pawel,
Sometimes areas that I edit don't seems to appear in the history.
My most recent example is here:
http://owl.apis.dev.openstreetmap.org/?lat=52.92522&lon=-1.43012&zoom=16&layers=M
I did a big-ish update (800+ nodes) to the park area - added all the wood areas, footpaths, etc, in this changeset:
http://www.openstreetmap.org/browse/changeset/16393726
But they do not appear, the changeset does not appear at all. Other updates I did after this appear and previous ones.
Maybe they will at some point it has been about 20 hours since I did the changeset but I am concerned that they will not appear at all.
Do you have any ideas?
Is the size (amount of edits,etc) of the changeset dependant on how quick it appears on the map?
Maybe it is area size/bounding box? Maybe that takes longer to process. shrug
I do have a habit of downloading a set area in JOSM (via remote control on the website) and editing outside that area when I see something else that needs fixing. That is why the bounding box of the changeset is large for this - and larger than the initial area I downloaded. Not sure if that has anything to do with it but I thought I would give you more information.
Cheers,
John
The text was updated successfully, but these errors were encountered: