Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[Anita Graser]

On Wed, Sep 21, 2016 at 8:05 PM, Matthias Kuhn  wrote:

> I agree that we shouldn't ship broken things like this.
>
> Just a sidenote, I'm always very careful when reading "from a user
> perspective" as an argument in a discussion.
> I'm still looking for "the user" and the person who knows "the users
> perspective" and couldn't find those two yet ;)
>

​Let's translate it to "humans on gis.se/twitter/user mailing list" ;-)

Best wishes,
Anita

​





>
> All the best
> Matthias
>
> On 09/21/2016 07:38 PM, Anita Graser wrote:
> > Mathieu Pellerin wrote
> >> Unless we have a feature parity with the current openstreetmap tool
> >> (offered through vector -> openstreetmap), please do not drop it.
> >
> > From a user and software quality perspective, I think that we should not
> > ship a severely broken plugin as core plugin while the working Quick OSM
> > plugin has to be installed separately. (Even if one is lacking a specific
> > feature over the other.)
> >
> > Make the broken OSM importer optional.
> >
> > Best wishes,
> > Anita
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://osgeo-org.1560.x6.
> nabble.com/Deprecation-of-the-Vector-OpenStreetMap-Importer-
> tp5286805p5287154.html
> > Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[Matthias Kuhn]

I agree that we shouldn't ship broken things like this.

Just a sidenote, I'm always very careful when reading "from a user
perspective" as an argument in a discussion.
I'm still looking for "the user" and the person who knows "the users
perspective" and couldn't find those two yet ;)

All the best
Matthias

On 09/21/2016 07:38 PM, Anita Graser wrote:
> Mathieu Pellerin wrote
>> Unless we have a feature parity with the current openstreetmap tool
>> (offered through vector -> openstreetmap), please do not drop it.
> 
> From a user and software quality perspective, I think that we should not
> ship a severely broken plugin as core plugin while the working Quick OSM
> plugin has to be installed separately. (Even if one is lacking a specific
> feature over the other.) 
> 
> Make the broken OSM importer optional.
> 
> Best wishes,
> Anita
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://osgeo-org.1560.x6.nabble.com/Deprecation-of-the-Vector-OpenStreetMap-Importer-tp5286805p5287154.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[Anita Graser]

Mathieu Pellerin wrote
> Unless we have a feature parity with the current openstreetmap tool
> (offered through vector -> openstreetmap), please do not drop it.

From a user and software quality perspective, I think that we should not
ship a severely broken plugin as core plugin while the working Quick OSM
plugin has to be installed separately. (Even if one is lacking a specific
feature over the other.) 

Make the broken OSM importer optional.

Best wishes,
Anita





--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Deprecation-of-the-Vector-OpenStreetMap-Importer-tp5286805p5287154.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[PieterB]

Mathieu Pellerin wrote
> Unless we have a feature parity with the current openstreetmap tool
> (offered through vector -> openstreetmap), please do not drop it. 
> 
> 
> I agree with Mathieu.  Perhaps it is possible to keep the first step of
> the download and redirect it to add it as a vector layer?
> 
> One
> useful feature that isn't available through OGR (or QuickOSM last time I
> trieD) is the exporting of individual tags as fields (versus only creating
> a few fields and an "other_tags" field).
> 
> On Tue, Sep 20, 2016 at 1:17 PM, Andre Joost 

> andre+joost@

> 
> wrote:
> 
>>
>> Dear all,
>>
>> This topic pops up regularly on the mailing lists, but nothing happened
>> lately.
>> The OS import tool is still not able to load features with node numbers
>> exceeding the 32bit-unsigned limit, see http://wiki.openstreetmap.org/
>> wiki/64-bit_Identifiers . As a consequence, features get lost, or lines
>> and polygons don't get imported at all, as soon as recently added nodes
>> are
>> involved. This makes the importer quite useless.
>>
>> Following the discussion here at http://osgeo-org.1560.x6.
>> nabble.com/Suggestion-Remove-Vector-Openstreetmap-tool-
>> from-QGIS-2-12-td5226614.html and on GIS SE http://gis.stackexchange.com/
>> questions/211000/is-there-a-qgis-tool-that-handles-osm-64-
>> bit-identifiers-correctly I suggest to drop the 3-part importer from the
>> Vector menu.  Add vector layer and the QuickOSM plugin can import OSM
>> data
>> without the 32-bit limitation.
>>
>> It would be good to drop the item in the upcoming QGIS 2.18.
>>
>> Alternatively, somebody would have to change the data type for osm_id in
>> the spatialite export (part 2 of the 3-part-importer) from integer to
>> long
>> integer or text.
>>
>> Greetings,
>> Ande Joost
>>
>> ___
>> Qgis-developer mailing list
>> 

> Qgis-developer@.osgeo

>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> 
> ___
> Qgis-developer mailing list

> Qgis-developer@.osgeo

> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer





--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Deprecation-of-the-Vector-OpenStreetMap-Importer-tp5286805p5286982.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[Etienne Trimaille]

2016-09-20 9:55 GMT+02:00 Mathieu Pellerin :

> One useful feature that isn't available through OGR (or QuickOSM last time
> I trieD) is the exporting of individual tags as fields (versus only
> creating a few fields and an "other_tags" field).
>

FYI, QuickOSM is not creating the "other_tags". There is a special parser
in the plugin to create individual fields.


>
> On Tue, Sep 20, 2016 at 1:17 PM, Andre Joost 
> wrote:
>
>>
>> Dear all,
>>
>> This topic pops up regularly on the mailing lists, but nothing happened
>> lately.
>> The OS import tool is still not able to load features with node numbers
>> exceeding the 32bit-unsigned limit, see http://wiki.openstreetmap.org/
>> wiki/64-bit_Identifiers . As a consequence, features get lost, or lines
>> and polygons don't get imported at all, as soon as recently added nodes are
>> involved. This makes the importer quite useless.
>>
>> Following the discussion here at http://osgeo-org.1560.x6.nabbl
>> e.com/Suggestion-Remove-Vector-Openstreetmap-tool-from-QGIS-
>> 2-12-td5226614.html and on GIS SE http://gis.stackexchange.com/q
>> uestions/211000/is-there-a-qgis-tool-that-handles-osm-64-bit
>> -identifiers-correctly I suggest to drop the 3-part importer from the
>> Vector menu.  Add vector layer and the QuickOSM plugin can import OSM data
>> without the 32-bit limitation.
>>
>> It would be good to drop the item in the upcoming QGIS 2.18.
>>
>> Alternatively, somebody would have to change the data type for osm_id in
>> the spatialite export (part 2 of the 3-part-importer) from integer to long
>> integer or text.
>>
>> Greetings,
>> Ande Joost
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Deprecation of the Vector - OpenStreetMap - Importer

[Mathieu Pellerin]

Unless we have a feature parity with the current openstreetmap tool
(offered through vector -> openstreetmap), please do not drop it. One
useful feature that isn't available through OGR (or QuickOSM last time I
trieD) is the exporting of individual tags as fields (versus only creating
a few fields and an "other_tags" field).

On Tue, Sep 20, 2016 at 1:17 PM, Andre Joost 
wrote:

>
> Dear all,
>
> This topic pops up regularly on the mailing lists, but nothing happened
> lately.
> The OS import tool is still not able to load features with node numbers
> exceeding the 32bit-unsigned limit, see http://wiki.openstreetmap.org/
> wiki/64-bit_Identifiers . As a consequence, features get lost, or lines
> and polygons don't get imported at all, as soon as recently added nodes are
> involved. This makes the importer quite useless.
>
> Following the discussion here at http://osgeo-org.1560.x6.
> nabble.com/Suggestion-Remove-Vector-Openstreetmap-tool-
> from-QGIS-2-12-td5226614.html and on GIS SE http://gis.stackexchange.com/
> questions/211000/is-there-a-qgis-tool-that-handles-osm-64-
> bit-identifiers-correctly I suggest to drop the 3-part importer from the
> Vector menu.  Add vector layer and the QuickOSM plugin can import OSM data
> without the 32-bit limitation.
>
> It would be good to drop the item in the upcoming QGIS 2.18.
>
> Alternatively, somebody would have to change the data type for osm_id in
> the spatialite export (part 2 of the 3-part-importer) from integer to long
> integer or text.
>
> Greetings,
> Ande Joost
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer