[OSM-talk] OSM data, how can we contribute to keep it to a reasonable size?
Imre Samu
pella.samu at gmail.com
Thu Jan 18 14:48:45 UTC 2018
>What can I as a map editor do to keep these data files to a reasonable
size without compromising data quality?
According to the "Lean thinking" (
https://en.wikipedia.org/wiki/Lean_thinking ) we should focus on
" eliminating waste"
Waste is:
* Any polygon or tagging errors ( because we can't use this information,
and need lot of space or processing resources ) or any from this:
https://wiki.openstreetmap.org/wiki/Error_categories ; etc
* or any mapping errors ( bad street names ; routing problems: waste for
users )
* or any not "UpToDate" data/information ( old phone numbers - it is
useless, so it is waste )
some examples:
http://area.jochentopf.com/stats/
- Errors: Intersections
- Errors: Duplicate nodes
- Errors: Duplicate segments (* ~160.000*)
- Errors: Open rings ( ~9.000)
- Errors: Inner rings with same tags as outer rings
- Errors: Wrong role ( *~ 700.000 *)
some key problems: ( unused/bad keys is a waste )
- https://taginfo.openstreetmap.org/reports/characters_in_keys#problem
( Keys with possibly problematic characters )
- https://taginfo.openstreetmap.org/reports/characters_in_keys#space
( Keys with whitespace )
- or my favorite:
--- https://taginfo.openstreetmap.org/keys/latitude#values
--- https://taginfo.openstreetmap.org/keys/LAT#values
And we have lot of low quality imports we should fix.
>What can I as a map editor
imho:
Any quality assurance work helps a lot:
https://wiki.openstreetmap.org/wiki/Quality_assurance
so fixing data problems in your area helps "eliminating waste" and less
waste is good for data size
Imre
2018-01-18 6:14 GMT+01:00 Oleksiy Muzalyev <oleksiy.muzalyev at bluewin.ch>:
> Good morning,
>
> I started to experiment with the OSM data [1] on a local computer, and I
> begin to realize how big these data files are. It takes quite a while to
> load into the local database just the data for one country.
>
> What can I as a map editor do to keep these data files to a reasonable
> size without compromising data quality? I mean in the sense, - take care
> of the pennies and the pounds will take care of themselves?
>
> I could think of the following three approaches so far:
>
> - using as short an URL as possible, website=http://somewebsite.com
> instead of website=http://www.somewebsite.com , three characters less; [2]
>
> - correct phone number ISO format, phone=+12 345 678 90 12 instead of
> phone=+12 (345) 678 90 12 , two characters less; [3]
>
> - deleting unnecessary nodes from a way (Shift-Y in JOSM) with consequent
> verification of its geometry;
>
> What else, if anything, could be done?
>
> [1] https://wiki.openstreetmap.org/wiki/Downloading_data
> [2] https://wiki.openstreetmap.org/wiki/Key:website
> [3] https://wiki.openstreetmap.org/wiki/Key:phone
>
> With best regards,
> Oleksiy
> osm: Alex-7
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20180118/b06000ab/attachment.html>
More information about the talk
mailing list