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
IndianaMap #693
Conversation
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 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. |
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. |
Looks like the validation script only checks whether the editor-layer-index/scripts/check.py Lines 127 to 130 in e3b91ea
|
#697 fixes the bug in the validation script. |
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. |
Did you see #694 too? You should play the lottery 😄 |
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.
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.