Re: [OSM-talk] Problem with JOSM imagery
On Mon, Mar 21, 2016 at 2:01 PM, Ian Dees wrote: > > > Yes, the issue is with the rate limiter on the tile service. I have > removed the rate limiter so you shouldn't run into problems now. > Thanks again Ian! That will make my work editing in the National Forests much faster (and enjoyable)! Mike ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
On Mon, Mar 21, 2016 at 7:51 PM, Mike Thompson wrote: > > > On Mon, Mar 21, 2016 at 1:34 PM, Ian Dees wrote: > >> >> I forgot that I have a rate limiter enabled that is probably tuned too >> low. I will block the IPs that are scraping and loosen the rate limiter a >> bit. >> > Thanks Ian. Might this be an issue with the actual tile service as > well[1]? This is the same type of behavior I am seeing in JOSM when > attempting to consume the USGS topo tiles. It works great for a minute or > two, and then nothing until I stop and wait. > Yes, the issue is with the rate limiter on the tile service. I have removed the rate limiter so you shouldn't run into problems now. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] JOSM plugin to import GeoJSON?
On Mon, Mar 21, 2016 at 1:53 PM, Christoph Hormann wrote: > > The general problem with SQLite based files is that they are always read > and written through the SQLite database engine which is not > particularly good for sequential write and read operations. In my experience the engine defaults to one write operation per transaction which is very slow. If you are processing a large amount of data you need to explicitly open and then later (after many writes) commit the transaction if you want reasonable performance. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] JOSM plugin to import GeoJSON?
On Monday 21 March 2016, Stefan Keller wrote: > > I'm not sure if Geopackage has significant performance improvements > > over simple Spatialite but if it hasn't then my recommendation for > > simple GIS processing is certainly to stick with shape files for > > the time being - despite all their shortcomings. > > Shapefiles, Spatialite and GeoPackage all use R-tree indexes. > I never heard about performance advantages of Shapefiles (except a > bug in a former Spatialite driver). The general problem with SQLite based files is that they are always read and written through the SQLite database engine which is not particularly good for sequential write and read operations. You can get reasonable performance from Spatialite in many cases but you never get anywhere close to shapefiles in my experience. > Can you tell me a use case? Which Spatialite SW are you using? I am not aware of any software dealing with spatialite files that does not use libspatialite/SQLite. -- Christoph Hormann http://www.imagico.de/ ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
On Mon, Mar 21, 2016 at 1:34 PM, Ian Dees wrote: > > I forgot that I have a rate limiter enabled that is probably tuned too > low. I will block the IPs that are scraping and loosen the rate limiter a > bit. > Thanks Ian. Might this be an issue with the actual tile service as well[1]? This is the same type of behavior I am seeing in JOSM when attempting to consume the USGS topo tiles. It works great for a minute or two, and then nothing until I stop and wait. Mike [1] tile.openstreetmap.us/usgs_scanned_topos ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
On Mon, Mar 21, 2016 at 5:01 PM, Mike Thompson wrote: > > > On Mon, Mar 21, 2016 at 10:02 AM, Ian Dees wrote: > >> Try browsing the map in your area with this debug slippy map (double >> click to zoom, shift-double-click to zoom out): >> http://tile.openstreetmap.us/usgs_scanned_topos/preview.html >> >> Works great for a little while (in the default area of SF), but then the > tiles apparently stop being served and all I see is white space except for > the tiles that have already been downloaded. > I forgot that I have a rate limiter enabled that is probably tuned too low. I will block the IPs that are scraping and loosen the rate limiter a bit. ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] JOSM plugin to import GeoJSON?
Hi, 2016-03-21 17:33 GMT+01:00 Frederik Ramm : > I'm not sure if Geopackage has significant performance improvements over > simple Spatialite but if it hasn't then my recommendation for simple GIS > processing is certainly to stick with shape files for the time being - > despite all their shortcomings. Shapefiles, Spatialite and GeoPackage all use R-tree indexes. I never heard about performance advantages of Shapefiles (except a bug in a former Spatialite driver). Can you tell me a use case? Which Spatialite SW are you using? What people need to realize is, that Shapefiles really have issues: 1. Attribute name length restricted to 10 chars => resulting in information loss. 2. Strings length restricted to 255 chars => resulting in information loss. 3. No Multi LineString/Multi Polygon => resulting in information loss. 4. Max. file size restricted to 2GB => resulting in splitting tables into several files. 5. Several cluttered files => makes users forget to include all. :Stefan 2016-03-21 17:33 GMT+01:00 Frederik Ramm : > Hi, > > On 03/20/2016 10:56 PM, Stefan Keller wrote: >> But Shapefile remains an oldtimer with more drawbacks than limited >> field names; see [1]. >> GeoJSON (ascii) and GeoPackages (binary) are formats which are more >> suited for the job. >> I still have hope that JOSM will be able to read those vector formats too. > > Frankly, whenever I venture into the brave new world of Spatialite, I > come back to good old shape files after a while for performance reasons. > I'm not sure if Geopackage has significant performance improvements over > simple Spatialite but if it hasn't then my recommendation for simple GIS > processing is certainly to stick with shape files for the time being - > despite all their shortcomings. > > Bye > Frederik > > -- > Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" > > ___ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
On Mon, Mar 21, 2016 at 10:02 AM, Ian Dees wrote: > Try browsing the map in your area with this debug slippy map (double click > to zoom, shift-double-click to zoom out): > http://tile.openstreetmap.us/usgs_scanned_topos/preview.html > > Works great for a little while (in the default area of SF), but then the tiles apparently stop being served and all I see is white space except for the tiles that have already been downloaded. Mike ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] JOSM plugin to import GeoJSON?
Hi, On 03/20/2016 10:56 PM, Stefan Keller wrote: > But Shapefile remains an oldtimer with more drawbacks than limited > field names; see [1]. > GeoJSON (ascii) and GeoPackages (binary) are formats which are more > suited for the job. > I still have hope that JOSM will be able to read those vector formats too. Frankly, whenever I venture into the brave new world of Spatialite, I come back to good old shape files after a while for performance reasons. I'm not sure if Geopackage has significant performance improvements over simple Spatialite but if it hasn't then my recommendation for simple GIS processing is certainly to stick with shape files for the time being - despite all their shortcomings. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
Try browsing the map in your area with this debug slippy map (double click to zoom, shift-double-click to zoom out): http://tile.openstreetmap.us/usgs_scanned_topos/preview.html I cleared out the disk cache for this layer a couple months ago to save some space so the areas you're looking at might need to be re-cached, which can take some extra time and cause the JOSM connection to time out. On Mon, Mar 21, 2016 at 2:41 PM, EthnicFood IsGreat < ethnicfoodisgr...@gmail.com> wrote: > Recently I started having a problem getting imagery to display in JOSM. > Bing and the standard OpenStreetMap layer display fine, but none of the > other layers in the default list will display. They produce the following > error: > > Error downloading tiles: > Java.net.SocketTimeoutException: > Connect timed out > > All these layers used to display. I recently switched from basic to OAuth > authentication. Could the problem be related to this? Note that I can > display the USGS topo tiles okay in my browser ( > tile.openstreetmap.us/usgs_scanned_topos). My machine is located in a > corporate office environment. > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Problem with JOSM imagery
Mark, Have you checked whether your corporate IT department is blocking the URLs/IP addresses for those tile services? Mike On Mon, Mar 21, 2016 at 8:41 AM, EthnicFood IsGreat < ethnicfoodisgr...@gmail.com> wrote: > Recently I started having a problem getting imagery to display in JOSM. > Bing and the standard OpenStreetMap layer display fine, but none of the > other layers in the default list will display. They produce the following > error: > > Error downloading tiles: > Java.net.SocketTimeoutException: > Connect timed out > > All these layers used to display. I recently switched from basic to OAuth > authentication. Could the problem be related to this? Note that I can > display the USGS topo tiles okay in my browser ( > tile.openstreetmap.us/usgs_scanned_topos). My machine is located in a > corporate office environment. > > Mark > > ___ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Problem with JOSM imagery
Recently I started having a problem getting imagery to display in JOSM. Bing and the standard OpenStreetMap layer display fine, but none of the other layers in the default list will display. They produce the following error: Error downloading tiles: Java.net.SocketTimeoutException: Connect timed out All these layers used to display. I recently switched from basic to OAuth authentication. Could the problem be related to this? Note that I can display the USGS topo tiles okay in my browser ( tile.openstreetmap.us/usgs_scanned_topos). My machine is located in a corporate office environment. Mark ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
