Paul Norman | 25 May 23:45 2015
Picon

[OSM-dev] Seeking users of osm2pgsql floating-point node storage

osm2pgsql has an option to use floating points for lat/lon storage 
instead of fixed points. To remove unused code, I am planning on 
removing it, but wanted to check if anyone is using it.

To use it, #define FIXED_POINT had to be changed in several source 
files, so this is not something that would be accidentally used. If you 
don't know, you're not using it.

If you are using it, please comment on 
https://github.com/openstreetmap/osm2pgsql/pull/357.

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Harry Wood | 21 May 19:00 2015
Picon

[OSM-dev] nominatim 'boundingbox' field. Recently changed?

I had a bit of code which was using the boundingbox field of the nominatim response

I'd swear something seemed to change a couple of weeks ago. It now returns a zero sized boundingbox, where
previously it returned something more useful. e.g. for any "suburb" match:
http://open.mapquestapi.com/nominatim/v1/search.php?format=json&q=Herne+Hill,+London

My code's pointed at mapquest, but I see the same problem on osm's instance.
http://nominatim.openstreetmap.org/search?format=json&q=Herne+Hill,+London

Still getting a sensible bounding box for cities and for ways and various other things, but these suburbs
used to be working. Anyone else noticed this change? I guess I'll work around it ...unless it's an easy one
for nominatim folks to fix somehow.

Harry

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Michael Larsen | 17 May 17:44 2015
Picon

[OSM-dev] Changeset without bbox

Hi,

I recently observed a changeset which does not have a bbox (the 'min_lat', 
'max_lat' etc. tags).   The changeset re-orderes members of a relation, so it 
is not a typical changeset and maybe this is the expected behavior since no 
nodes are directly involved?

The changeset is here:
https://www.openstreetmap.org/api/0.6/changeset/31217983

The web-map-view from the URL below also does not show the bbox nor does it 
zoom to the area for the changeset. This indicates to me that the bbox was 
expected by the web-map-view backend...?

https://www.openstreetmap.org/changeset/31217983

/MichaelVL

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Matthijs Melissen | 13 May 18:53 2015
Picon

[OSM-dev] Release openstreetmap-carto v2.30.0

Dear all,

Today, v2.30.0 of the openstreetmap-carto stylesheet has been rolled
out to the openstreetmap.org servers.

This version includes the following changes:
* New wetland rendering, including differentiation based on the wetland key.
* Added rendering for amenity=bicycle_parking.
* Added icons for historic=monument, amenity=court_house,
amenity=bench, amenity=waste_basket, man_made=hunting_stand,
shop=alcohol, shop=electronics, shop=furniture, shop=gift,
shop=jewelry/jewellery, shop=mobile_phone, shop=optician, shop=shoes,
shop=diy, shop=hardware, and shop=bicycle.
* Changed icon for shop=clothes, historic=archaeological_site,
highway=bus_stop, tourism=caravan_site, tourism=motel, power=generator
with generator:source=wind, and man_made=lighthouse.
* Added rendering for landuse=greenhouse_horticulture (rendered as
landuse=farmland).
* Changed rendering for man_made=cutline
* Added name labels to tourism=viewpoint, amenity=post_office,
natural=tree, amenity=bicycle_rental,  man_made=mast,
amenity=recycling, amenity=drinking_water, man_made=water_tower,
tourism=picnic_site, leisure=picnic_table, and leisure=slipway,
amenity=car_sharing (operator label) and amenity=atm (operator label).
* Added name labels to natural=cliff and man_made=embankment.
* Better water halos.
* Various bug fixes.

For a full list of commits, see
https://github.com/gravitystorm/openstreetmap-carto/compare/v2.29.0...v2.30.0 .
(Continue reading)

Walter Nordmann | 7 May 11:58 2015
Picon
Picon

[OSM-dev] get node data from flatfile

Hi,

at the moment i'm using osm2pgsql with slim-mode + flatfile for my imports
and diff-updates and everything is running fine.

But now i need to create pbf-exports of my database and i would like to
access the node-data of the flatfile, because planet_osm_nodes is empty
(whicht is ok).

Is there any way to access those nodes by osm_id? I tried to write a litte
program starting with node-persistent-cache-reader.c but i did not manage
it. Many nodes are missing.

At the end i would like to write my own pg/plsql-Function get_node(osm_id)
which gives me the geometry of that node (reading the flatfile of course).

Regards
walter

-----
[url=http://osm.wno-edv-service.de/residentials] Missing Residentials Map 1.17[/url]
[url=http://osm.wno-edv-service.de/plz] Postcode Map 2.0.2[/url]
--
View this message in context: http://gis.19327.n5.nabble.com/get-node-data-from-flatfile-tp5843642.html
Sent from the Developer Discussion mailing list archive at Nabble.com.

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
(Continue reading)

Rob Nickerson | 6 May 23:45 2015
Picon

[OSM-dev] Learn Rails

Code academy have added Ruby on Rails, which is what OpenStreetMap uses for the website.

Learn via their online interactive learning.

http://www.codecademy.com/learn/learn-rails

You never know, you could be contributing to OpenStreetMap code soon after :)

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Paul Norman | 30 Apr 22:41 2015
Picon

[OSM-dev] Osm2pgsql 0.87.3 release

Osm2pgsql 0.87.3 has been released. This development release primarily fixes
bugs, but some of the bug fixes make other features usable.

Included is a bug fix for the lockfree queue implementation. Anyone using
versions 0.87.0 to 0.87.3-dev, parallel processing, Boost 1.53 or newer, and
not using --without-lockfree should immediately upgrade or stop using 
parallel
processing. No data corruption issues have been observed, but the lockfree
implementation may have been buggy on all systems.

There have been various fixes with moving hand-written C structures to C++
standard library equivalents and other code cleanups. The main user-facing
changes are

- The multi-backend should now be functional, with an example which creates
   separate tables for bus nodes, highways, and buildings

- --without-lockfree is no longer needed on OS X, BSD and some Linux
   distributions and architectures. This should simplify downstream build
   scripts for multi-architecture builds and improve speed on any OS that
   required the option before.

- nodecachereader should now work with node IDs > 2^31. This is a separate
   utility program, and obviously isn’t used much

- Nominatim-related performance improvements

- Many autoconf macros have been updated. This should ease configuration on
   non-standard systems.

This may be the last tagged release that does not require C++11. We have no
current PRs which will require C++11, but would be willing to accept them.

A full list of commits is at 
https://github.com/openstreetmap/osm2pgsql/compare/0.87.2...0.87.3

As always, bugs can be raised at 
https://github.com/openstreetmap/osm2pgsql/issues.
I’m particularly interested if package maintainers have concerns. If 
osm2pgsql
isn’t packaged for your OS and you want to do so and have questions 
about the
osm2pgsql side, please ask them too.

Many thanks to those who have contributed code to this and previous 
releases.

(diary entry version at 
http://www.openstreetmap.org/user/pnorman/diary/34887)

Paul Norman
On behalf of the osm2pgsql maintainers

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
andrew byrd | 29 Apr 01:35 2015
Picon

[OSM-dev] Simpler binary OSM formats

Hello OSM developers,
 
Over the last few years I have worked on several pieces of software that consume and produce the PBF format. I have always appreciated the advantages of PBF over XML for our use cases, but over time it became apparent to me that PBF is significantly more complex than would be necessary to meet its objectives of speed and compactness.
 
Based on my observations about the effectiveness of various techniques used in PBF and other formats, I devised an alternative OSM representation that is consistently about 8% smaller than PBF but substantially simpler to encode and decode. This work is presented in an article at http://conveyal.com/blog/2015/04/27/osm-formats/. I welcome any comments you may have on this article or on the potential for a shift to simpler binary OSM formats.
 
Regards,
Andrew Byrd
_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Peter Barth | 27 Apr 22:42 2015
Picon

[OSM-dev] GSoC - Accepted students have been announced

Hi all,

the list of accepted projects is out and OpenStreetMap will
mentor 8 student projects during Google Summer of Code 2015. You
can have a look at the full list at the google melange site¹.

Additionally, you can have a look at our wiki page here, for the
accepted OSM projects and project details². As the community
bonding period³ starts now, the students have time to get to know
their mentors, read documentation and get up to speed to begin
working on their projects. Official coding begins on 25 May, and
I hope we'll have 8 motivated students who will do a great
project. So you may expect first documentations of progress after
25 May.

We hope that students whose applications were unsuccessful will
nevertheless stay in touch with OpenStreetMap. Contributors are
always welcome, and we have a wealth of interesting projects
available ;)

Happy GSoC,
Peda

[1] https://www.google-melange.com/gsoc/projects/list/google/gsoc2015
[2] https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/AcceptedProjects
[3] http://googlesummerofcode.blogspot.de/2007/04/so-what-is-this-community-bonding-all.html

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Ramneek Paul Singh | 23 Apr 20:20 2015
Picon

[OSM-dev] Diagrams

Can i get the site from where i could get the the exact Structure charts , ER diagram of open street map ?
--
Ramneek Paul Singh
http://ramneekpaulsingh.wordpress.com
" Failure is the opportunity to begin again more intelligently "
_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
Paul Norman | 22 Apr 01:17 2015
Picon

[OSM-dev] rsync and osm2pgsql flat nodes

osm2pgsql flat nodes is a binary file with the position of all nodes, in 
a representation which is very efficient for full planet dumps, needing 
only 8 bytes * max node ID, instead of the 40-60 bytes * number of nodes 
that alternative representations would need. For the planet where the 
number of nodes is about 81% of the max node ID, this takes much less 
space.

One significant downside for production environments is that this data 
is not in the database and does not have the replication and redundancy 
of in-DB nodes. This is a problem but should not be insurmountable. 
Rather than needing to keep the flat nodes and database synchronized 
with your replication method, the flat nodes needs to be no older than 
the state file which also should be saved.

Has anyone used rsync to keep a copy of the flat nodes file up to date 
on another standby machine which can then step in in case the first one 
fails? My initial thought was to have another cron script that runs 
async to the updates which rsyncs the flat nodes and then the state 
file, in that order. I have no idea how the performance is, but most of 
the flat nodes file should not have changed.

_______________________________________________
dev mailing list
dev <at> openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Gmane