-
Notifications
You must be signed in to change notification settings - Fork 121
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
Add test for maritime_boundary #1484
Conversation
self.load_fixtures([ | ||
'https://www.openstreetmap.org/relation/148838', | ||
'https://www.openstreetmap.org/relation/1428125', | ||
'file://integration-test/fixtures/buffered_land/' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By hosting the shapefile in a buffered_land
directory FixtureTest will set that as the database table name on import.
The way that the shapefile fixtures work at the moment is different from how the OSM URL fixtures work (although it would be better to load them explicitly). Moving the buffered land shapefile into the fixtures directory means it gets loaded automatically.
5db16cb
to
36ad71b
Compare
Following 36ad71b, we now have two test failures (rather than the errors we had before). I think these failures represent the actual regressions we have in the code for dealing with maritime boundaries, so in that sense the tests are "working". The code is the next thing we need to fix. |
…ously was set up. Tightened up the filter for maritime `buffered_land` polygons, so it's perhaps a little more obvious where they come from.
After c0768c9, test failures just say |
Circle is happy now! @zerebubuth, can you give a formal review, please? |
# TODO: either set up new buckets, or deprecate these things. | ||
#- ./scripts/update-integration-test-coordinates.sh | ||
#- pip install awscli | ||
#- aws s3 sync ~/.cache/vector-datasource/ s3://mapzen-tiles-assets/integration-test-fixtures/ --size-only --exclude="*" --include="*.geojson" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one exists now:
In retrospect we should probably call the bucket tilezen-assets
instead...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's a big deal to rename it. It's just a matter of updating the getting started instructions and configuration for the shapefile import/prepare processes right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I'm cool with leaving the decision about the cache bucket to a later issue. It would be nice to set it up, but I don't think it's critical.
Update data migrationsUpdate docs