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

IndianaMap #693

Merged
merged 3 commits into from Aug 17, 2019
Merged

IndianaMap #693

merged 3 commits into from Aug 17, 2019

Conversation

1ec5
Copy link
Member

@1ec5 1ec5 commented Aug 16, 2019

Added the three WMSes for IndianaMap orthoimagery. Note that the 2018 geometry covers more counties than the WMS currently provides; these additional counties will be added to the 2018 MapServer sometime this year.

Fixes #686.

@1ec5 1ec5 added the imagery label Aug 16, 2019
@1ec5 1ec5 self-assigned this Aug 16, 2019
@1ec5
Copy link
Member Author

1ec5 commented Aug 16, 2019

Added to JOSM.

@1ec5 1ec5 merged commit 73bf893 into gh-pages Aug 17, 2019
@1ec5 1ec5 deleted the 1ec5-indianamap-686 branch August 17, 2019 04:38
@grischard grischard mentioned this pull request Aug 18, 2019
@grischard grischard restored the 1ec5-indianamap-686 branch August 18, 2019 07:58
@grischard
Copy link
Collaborator

Hi Minh,

On one hand, it looks like I'm the one to blame for not having CI tools that caught that you were trying to add a Multipolygon, which isn't supported. I thought check.py was supposed to catch this.

On the other hand, you didn't wait for feedback, you merged quickly and on a weekend, and used a Multipolygon while the documentation says to use a Polygon.

Can you please fix your PR to use a Polygon geometry instead of Multipolygon? And I'll try to see why check.py didn't catch this.

@1ec5
Copy link
Member Author

1ec5 commented Aug 18, 2019

Sorry for jumping the gun. Would it be possible to use a feature collection instead? Unfortunately, all three layers have discontiguous coverage areas. If not, I can try to draw a very thin line connecting the polygons.

@1ec5
Copy link
Member Author

1ec5 commented Aug 18, 2019

Looks like the validation script only checks whether the type can be compared to the string Polygon, not whether it’s equal to that string:

try:
source['geometry']['type'] == "Polygon"
except (TypeError, KeyError):
raise ValidationError("{} should have a valid geometry or be global".format(filename))

@1ec5
Copy link
Member Author

1ec5 commented Aug 18, 2019

#697 fixes the bug in the validation script.

@grischard
Copy link
Collaborator

The usual, admittedly unfamiliar, for-historical-reasons way to do it is to have a simple polygon with more than one ring. Look at the France geojsons with Corsica for example.

@grischard
Copy link
Collaborator

grischard commented Aug 18, 2019

Did you see #694 too?

You should play the lottery 😄

@1ec5 1ec5 mentioned this pull request Aug 18, 2019
@bhousel bhousel deleted the 1ec5-indianamap-686 branch August 18, 2019 13:19
1ec5 added a commit that referenced this pull request Aug 19, 2019
This image was included in 73bf893 (#693) but reverted in 6bad4d4 (#696), and the merge in 73f4739 (#698) failed to restore it along with the JSON files.
IdealChain pushed a commit to IdealChain/editor-layer-index that referenced this pull request Sep 28, 2019
This image was included in 73bf893 (osmlab#693) but reverted in 6bad4d4 (osmlab#696), and the merge in 73f4739 (osmlab#698) failed to restore it along with the JSON files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IndianaMap
2 participants