-
Notifications
You must be signed in to change notification settings - Fork 23
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
some geometry is not redenderer #1
Comments
Does the code handle exceptions ? Any way to look at them ? I guess ST_Intersection or even ST_MakeValid may be throwing an exception |
No exceptions, all request to SQL look valid (valid geojson). At zoom level 2 there are problems with tiles (2, 1, 1) and (2, 0, 1). In both tiles there are geometry rendered (so some geometry is returned from the sql api for that tile) I've updated and pushed the tile_sql tool you used in the previous prototype. The sql for that tiles is: |
Ah, I see ST_SnapToGrid is involved. That function would still turn collapsed polygon into EMPTY elmements. Try taking ST_SnapToGrid out ? |
BTW, I don't really see the missing geometries from the custom renderer example. But I do see what looks like a completely missing tile on the east of Canada. |
yep, you are right, is east not west, sorry. But if you play a little bit with whatever tool you use for debugging web apps (firebug, chrome developer tools...) you can see that there are no missing tiles, all tiles render geometry. |
Would be useful to be able to overlay the correct and bogus layers to see exactly what's missing. Does vecnik repo replace cartodb_tile_render one or integrates it ? |
""" new one using some code from cartodb_tile_render. |
I was thinking: could it be your client-side clipping introducing the problem ? I'm pretty sure I've seen missing geometries also before the SQL part was changed. I know it's not easy to "clip" vectors not intersecting the clipper range (all covered and all within hole cases) -- If you have a way to disable clipping it should be easy to tell. About doing: my TODO list is growing exponentially, worth discussing some before going into implement things. I shall point out that I'd give precedence to implement an OpenLayers layertype if I had to touch JS for VECNIK, that way it'd have layer management for free :) |
dont worry @strk it is better to solve it myself :) (there is no client side clipping btw) |
openlayers FTW !! |
I just had another thought: can it be a winding issue ? Ie: something that would be fixed by a call to ST_ForceRHR. |
I've got an addendum to this issue; one of my Vecnik-ModestMaps implementations has also gotten selective about which tiles it renders. There's a few missing at each zoom level, and it seems to be the same error pattern on Chrome, FF and Safari. Was there an easy resolution on this? |
Some geometry is not renderer in some tiles, for example the west canada
http://vizzuality.github.com/VECNIK/examples/custom_renderer.html#2/0.0/62.4
The text was updated successfully, but these errors were encountered: