[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#779942: marked as done (ITP: osmium-contrib -- Various programs showing what you can do with the Osmium library)



Your message dated Wed, 24 Jun 2015 09:48:32 +0200
with message-id <558A60D0.6060607@xs4all.nl>
and subject line No longer intent to package
has caused the Debian Bug report #779942,
regarding ITP: osmium-contrib -- Various programs showing what you can do with the Osmium library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
779942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779942
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Bas Couwenberg <sebastic@xs4all.nl>

* Package name    : osmium-contrib
  Version         : 0.0~20150306-0c4f263
  Upstream Author : Osmium Developers <dev@openstreetmap.org>
* URL             : http://osmcode.org/osmium-contrib/
* License         : public-domain
  Programming Lang: C++
  Description     : Various programs showing what you can do with the Osmium library

Osmium Contrib contains various programs showing what you can do with the
Osmium library.

The osmium-contrib repository collects little programs that use the Osmium
library in various ways. These programs can be useful in their own right, but
they also provide nice examples for developers who want to learn about the
features of the Osmium library.

Currently the following programs are available:

 * amenity_list  - Print list of amenities in OSM file
 * export_to_wkt - Write out node, way, and area geometries as WKT
 * mapolution    - Show evolution of OSM map
 * node_density  - Create image showing OSM node density
 * pub_names     - Extract names of pubs from OSM file
 * road_length   - Calculate length of highways from an OSM file

The Osmium library has extensive support for all types of OSM entities: nodes,
ways, relations, and changesets. It allows reading from and writing to OSM
files in XML and PBF formats, including change files and full history files.
Osmium can store OSM data in memory and on disk in various formats and using
various indexes. Its easy to use handler interface allows you to quickly write
data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS
and GeoJSON geometries for easy conversion into many GIS formats and it can
assemble multipolygons from ways and relations.



This package is part of the new Osmium family superseding the existing osmium
source package. The new Osmium family consists of libosmium, node-osmium,
pyosmium, osmium-tool, osmium-contrib & osmcoastline.

The packages for the Osmium family will be maintained in the Debian GIS team.

--- End Message ---
--- Begin Message ---
After discussion on the debian-gis list [1] with the upstream developer
we decides to abandon further packaging of osmium-contrib & node-osmium.
The relevant bits from the discussion are quoted below.

There is partial packaging available in git [2][3], which I'll leave
there in case we change our mind in the future.

[1] https://lists.debian.org/debian-gis/2015/06/msg00102.html
[2] http://anonscm.debian.org/cgit/pkg-grass/osmium-contrib.git
[3] http://anonscm.debian.org/cgit/pkg-grass/node-osmium.git

On 06/24/2015 09:34 AM, Jochen Topf wrote:
> On Tue, Jun 23, 2015 at 11:57:47PM +0200, Sebastiaan Couwenberg wrote:
>> On 03/16/2015 08:08 PM, Jochen Topf wrote:
>>> On Mo, Mär 16, 2015 at 07:25:25 +0100, Sebastiaan Couwenberg wrote:
>>>> Do you still doubt the usefulness of packaging osmium-contrib?
>>>
>>> It is a bit of a grab bag of programs. Some of them might be useful on their
>>> own but mostly they are examples for libosmium use, not much use as they are
>>> but good as a starting point for somebodys own development efforts. Maybe I
>>> should put the stuff thats not usable on its own into the libosmium examples
>>> directory and only leave the stuff thats usable on its own.
>>>
>>>> I've not continued with this package because of that, besides getting
>>>> the required libosmium ready first.
>>>
>>> Lets leave osmium-contrib alone for the time being and concentrate on the
>>> other packages. Once they have settled, I'll have a look again.
>>
>> With the acceptance of libosmium [1] into the archive, I've also
>> uploaded the first revisions for osmium-tool [2], osmcoastline [3] &
>> pyosmium [4]. These will hit the NEW queue soon.
>>
>> Should we still skip further packaging of osmium-contrib?
> 
> Yes. I don't really see the point of packaging this. This is really example code
> intended for people to change and build upon, not something that non-developers
> will install. And after I have seen how much hassle the Debian packaging is, I
> am even less inclined to go through that.
> 
>> And what about node-osmium?
> 
> Currently not really in a state I want to support. And most people will use the
> simpler 'npm install' anyway. No package needed.

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

--- End Message ---

Reply to: