Skip to content
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

OSMCha doesn't work #384

Closed
literannn opened this issue Aug 18, 2019 · 6 comments
Closed

OSMCha doesn't work #384

literannn opened this issue Aug 18, 2019 · 6 comments

Comments

@literannn
Copy link

OSMCha does not show changesets for about half a day. Only pink background and "Map failed" box.

@andrewharvey
Copy link

@willemarcel
Copy link
Collaborator

Thanks for reporting, @literannn and @andrewharvey ! It seems our Overpass instance stopped. We will be working on it in some hours

@willemarcel
Copy link
Collaborator

The issue is solved!

@andrewharvey
Copy link

https://s3.amazonaws.com/mapbox/real-changesets/production/73494566.json still says Access Denied for me.

@willemarcel
Copy link
Collaborator

willemarcel commented Aug 19, 2019

I think it's not an issue of OSMCha, as overpass is running out of memory when querying the changeset. The same happened on achavi: https://overpass-api.de/achavi/?changeset=73494566&relations=true

@nrenner
Copy link

nrenner commented Aug 20, 2019

These are two different things.

The achavi-like, live adiff query is only run as a fallback when the S3 json is not available.

The cached S3 json files are generated by a script from minutely augmented diffs that don't have the memory issue, see:
https://www.openstreetmap.org/user/geohacker/diary/40846
drolbr/Overpass-API#346 (comment)

After an outage, the S3 script would ideally start over after the last successful json or run separately to fill up the missing ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants