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

Examples of problematic geometries #1

Open
jakepruitt opened this issue Oct 4, 2015 · 4 comments
Open

Examples of problematic geometries #1

jakepruitt opened this issue Oct 4, 2015 · 4 comments

Comments

@jakepruitt
Copy link

Beginning a running list of problematic geometries from other mapnik and earcut-related projects. Going to be adding to this list as I see more tickets appears.

Please add any other problematic edge cases you are aware of, if you have time, @rclark, @springmeyer @flippmoke @GretaCB

@wilhelmberg
Copy link

us_states.shp works for me:

@GretaCB
Copy link

GretaCB commented Oct 5, 2015

@BergWerkGIS Interesting. This is super odd. I tried re-uploading and navigated my map to the same z/x/y where your map ^^ displays the data, and I get partial tiling:

http://api.mapbox.com/v4/carolbhansen.us-states-test/page.html?access_token=pk.eyJ1IjoiY2Fyb2xiaGFuc2VuIiwiYSI6Iko1a0xjODgifQ.h7f9foFVduSgzGrh06hKUw#5/43.660/-95.208

Looks like us_states.zip is different than us_states.shp.

@wilhelmberg
Copy link

ahhh, I used
https://github.com/mapbox/mapnik-test-data/tree/master/data/shp/us_states

Looks like us_states.zip is different than us_states.shp.

Yes you are right, zip just contains DC:

image

But it is there, even in your upload:
http://api.mapbox.com/v4/carolbhansen.us-states-test/page.html?access_token=pk.eyJ1IjoiY2Fyb2xiaGFuc2VuIiwiYSI6Iko1a0xjODgifQ.h7f9foFVduSgzGrh06hKUw#7/38.895/-77.014
It's not easy to spot, because the zoom level is limited to 7.

Maybe the automatic zoom level detection has to be given another thought?
Where does this happen, mapnik-omnivore?

I uploaded us_states.zip via Mapbox Studio and made it available up to 16:
https://api.mapbox.com/v4/lr1k.2b97dd4d/page.html?access_token=pk.eyJ1IjoibHIxayIsImEiOiJ0ZDVoZ2FVIn0.VvDeZC2BzGINcCxObpfesw#12/38.8877/-77.0275

@mapsam
Copy link
Collaborator

mapsam commented Feb 4, 2016

Found one today where we had a GeoJSON file with a leading byte character that failed in mapnik tests. This PR removed the character, but might be worth keeping the old file for failed tests?

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