Skip to content

Commit ef7b79c

Browse files
committed
Start spanish translation: full copy of guide and front page.
1 parent 57b991a commit ef7b79c

15 files changed

+2051
-0
lines changed

_config.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,14 @@ translations:
1818
feedbackspan: "Was this chapter helpful?"
1919
feedback: "Let us know and help us improve the guides!"
2020
proceed: "proceed to next chapter"
21+
es:
22+
tagline: "Aprende OpenStreetMap Paso a Paso"
23+
contribute: "Ayuda a mejorar las guías"
24+
trainingspan: "Are you a workshop organizer?"
25+
training: "Check out training material for this guide (in English)"
26+
feedbackspan: "Was this chapter helpful?"
27+
feedback: "Let us know and help us improve the guides!"
28+
proceed: "proceed to next chapter"
2129
fr:
2230
tagline: "Learn OpenStreetMap Step by Step"
2331
contribute: "Help improve our guides"

_posts/es/0100-01-01-contribute.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
layout: contribute
3+
permalink: /es/contribute/
4+
lang: es
5+
title: Contribute
6+
contributetitle: "Help improve our guides"
7+
startwith: "Ready to get started?"
8+
startA: "Send us feedback"
9+
startB: "Create a translation"
10+
startC: "Improve Language"
11+
startD: "Fork and improve site"
12+
nosearch: true
13+
---
14+
This guide is created and maintained by the [OpenStreetMap](http://www.openstreetmap.org/) and [Humanitarian OpenStreetMap](http://hotosm.org/) community. You can help us improve this guide by simply sending your feedback or by contributing directly to it via [Github](http://github.com/hotosm/learnosm).

_posts/es/0100-01-01-index.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
layout: front
3+
permalink: /es/
4+
lang: es
5+
fronttitle: "OpenStreetMap is a free street level map of the world, created by an ever growing community of mappers."
6+
frontintro: "Anyone can edit OpenStreetMap. Here you can learn how Learn OSM provides easy to understand, step-by-step guides for you to get started with contributing to OpenStreetMap and using OpenStreetMap and using OpenStreetMap data. If you are interested in running an OpenStreetMap workshop, check out the LearnOSM trainer resources."
7+
ourguides: "Our Guides"
8+
searchtext: "What are you looking for?"
9+
begspan: "New to OpenStreetMap?"
10+
beg: "beginner's guide"
11+
interspan: "More guides (currently in English)"
12+
inter: "Intermediate, advanced, QGIS..."
13+
advspan: "Organizing a workshop?"
14+
adv: "See our trainer material"
15+
faq: "Common Questions"
16+
faqA: "What is OpenStreetMap?"
17+
faqB: "Who created LearnOSM?"
18+
faqC: "How can I get started mapping?"
19+
faqD: "Where can I find additional help?"
20+
nosearch: true
21+
---

_posts/es/0100-01-01-status.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
layout: default
3+
permalink: /es/status/
4+
lang: es
5+
title: Translation Status
6+
nosearch: true
7+
---
8+
9+
## Translation Status - All Languages
10+
11+
- [Spanish]({{site.baseurl}}/es/status/)
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
layout: doc
3+
title: All Chapters
4+
permalink: /es/beginner/all-chapters/
5+
lang: es
6+
category: beginner
7+
nosearch: true
8+
---
9+
{% for post in site.categories.[page.category]%}
10+
{% if post.lang == page.lang %}{% unless post.hidden %}
11+
{{post.content | markdownify}}
12+
{% endunless %}{% endif %}
13+
{% endfor %}
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
layout: doc
3+
title: Further Reading
4+
permalink: /es/beginner/moving-forward/
5+
lang: es
6+
category: beginner
7+
---
8+
9+
Further Reading
10+
===============
11+
12+
If you have made it this far, congratulations! You should have a good
13+
understanding now of how to make maps with OpenStreetMap. What else can
14+
you do with OSM? How can you learn more? How can you stay connected to
15+
the community of mappers?
16+
17+
OpenStreetMap Tools
18+
-------------------
19+
20+
In this guide we have learned the building blocks of OSM, and the tools
21+
you need to contribute to the map. But because the data on OSM is open,
22+
it has encouraged many more projects and tools that allow you to do more
23+
with the OpenStreetMap map.
24+
25+
MapOSMatic
26+
----------
27+
28+
One such project is called MapOSMatic, which you can access through your
29+
internet browser at [maposmatic.org](http://www.maposmatic.org/). This
30+
is a simple tool for printing a map of any area you choose. It will
31+
automatically create the map, along with a grid over the map, and an
32+
index of locations that are included in the area.
33+
34+
Learn More
35+
----------
36+
37+
There is a lot of information about OpenStreetMap available at
38+
[wiki.openstreetmap.org](http://wiki.openstreetmap.org/). Here you can
39+
find information about other projects that are related to OpenStreetMap,
40+
and documents and tutorials that can help you learn more about OSM.
41+
42+
Mailing List
43+
------------
44+
45+
The best way to get connected to the OpenStreetMap user community is to
46+
join your local mailing list. Many people sign up, using their email
47+
accounts to the OSM mailing list. Once you are on the list, you can send
48+
an email to the group if you have a question or want to talk about
49+
OpenStreetMap.
50+
51+
- To sign up for your country's mailing list, open your internet
52+
browser and go to
53+
[lists.openstreetmap.org](http://lists.openstreetmap.org/).
54+
55+
- Scroll down the page to find the list associated with your country.
56+
The country lists are named "Talk-lg", where lg represents the
57+
country of that list. For example, "Talk-id" is the list for
58+
Indonesia.
59+
- Click on the list you want to join.
60+
- Enter the following information in the boxes on this page:
61+
62+
- your email address
63+
- your first name
64+
- a new password
65+
- repeat the password
66+
67+
- When you are finished, click Subscribe.
68+
- Now you need to open your email, just as you did when you signed up
69+
for OpenStreetMap in chapter 2. There will be a confirmation email
70+
in your inbox from the mailing list.
71+
- Click on the confirmation link, which looks like this:
72+
73+
- You should now be a member of the mailing list.
74+
- Now when you want to send a message to the list, you can send it to
75+
76+
replacing "id" with the country for your list. You will also receive
77+
emails when other members send a message to the list.
78+
79+
Summary
80+
-------
81+
82+
These are some of the ways that you can use and stay connected with the
83+
OpenStreetMap community and learn more. We hope you'll continue
84+
exploring and learning more about OSM, and contribute to the project.
85+
Happy Mapping!
Lines changed: 192 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,192 @@
1+
---
2+
layout: doc
3+
title: Using Aerial Imagery
4+
permalink: /es/beginner/aerial-imagery/
5+
lang: es
6+
category: beginner
7+
---
8+
9+
Using Aerial Imagery
10+
====================
11+
12+
Tracing over imagery is both an easy and powerful way to contribute to
13+
OSM. Especially when resolution is high and skies are clear, digitizing
14+
from satellite imagery can provide the skeleton of OSM maps. This is
15+
useful because it makes ground-truthing, or gathering attribute data,
16+
easier for people in the field.
17+
18+
Nonetheless, tracing from imagery requires some precautions so that
19+
objects are not placed in the wrong location. There are two important
20+
aspects that must be considered when tracing from imagery:
21+
22+
1. Resolution: The resolution refers to the detail of imagery or the
23+
number of pixels from which the image is comprised. A pixel is the
24+
smallest unit of an image. The smaller the area of the pixel the
25+
better the resolution. With smaller pixels you are able to
26+
distinguish between between objects on earth better, as evidenced by
27+
the figure below. On the left is an image with low resolution, and
28+
less pixels per image. It is hard to distinguish the puzzle piece
29+
because a majority of the image is considered part of the puzzle
30+
piece. On the other hand, the image on the right with high
31+
resolution has smaller pixel units and therefore enables the puzzle
32+
piece to be much
33+
more distinguishable. In OSM, you are most likely to be able to use
34+
imagery is high resolution. Satellite civil imagery offers
35+
resolution under “1 meter”, which means each pixel of the imagery
36+
represents a one meter squared. That is pretty good!
37+
38+
![puzzle][]
39+
40+
2. Georeference: The georeference is a term for how the imagery was
41+
set, or essentially how close the imagery’s pixels represent the
42+
actual locations on the ground. This a relatively complex process,
43+
and the greater the terrain variation and relief, the harder the
44+
georeferencing. Satellites are hundreds of kilometers from the
45+
surface of the earth and when they take flat pictures to represent
46+
the curved earth there is bound to be some distortion and offset.
47+
The existence of offsets is shown slightly when you move between two
48+
images covering the same area, e.g. when you zoom in and the former
49+
displayed layer replaces another one with better resolution. Can you
50+
see shifts in the objects displayed in the imagery?
51+
52+
To get an idea of why the offset occurs image taking a picture of a
53+
statue and printing it. Now try to deform and stretch it so that it
54+
mimics the shape of the statue. This is what occurs when georeferencing
55+
imagery.
56+
57+
Fortunately, satellites are progressively being built with greater
58+
imagery precision and therefore extremely accurate resolution (the unit
59+
is often in centimeters). On the other hand, the georeferences of
60+
satellites is still off, for which the unit remains over a meter. A 5-10
61+
m georeference is considered good.
62+
63+
When you are trying to accurately map an area based on satellite
64+
imagery, keep in mind that high resolution imagery is not the only
65+
aspect that permits good location. Almost all objects in the image are
66+
offset from the ground location.
67+
68+
There are ways that you can minimize the imprecision of the imagery
69+
offset. You will be exposed to two main scenarios and methods for
70+
overcoming imagery offset:
71+
72+
1. you want to trace over imagery in an area that has already been
73+
mapped in OSM
74+
75+
2. you want to trace over an imagery in an area where there is no
76+
existing data in OSM
77+
78+
Offsets with existing data in OSM
79+
---------------------------------
80+
81+
Sometimes after downloading OSM data, adding the imagery, and zooming
82+
into the best resolution, you realize that the existing OSM data,
83+
especially roads, does not correctly overlay the imagery objects.
84+
85+
![existing data][]
86+
87+
Many OSM beginners believe that the roads have been traced incorrectly
88+
and thus move the roads to what appear to be the better location. Moving
89+
the road may be completely __WRONG__! There is a potential that the
90+
imagery is poorly aligned in comparison to the reality in the field.
91+
92+
A way to check or prove that the imagery is offset is through using GPS
93+
tracks. To do so, add __existing GPS tracks__(yours or
94+
other peoples-- more information on how to do this can be found in
95+
[Adding](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[GPS](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[Data](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[to](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[OSM](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit)[server](https://docs.google.com/a/engelsted.co/document/d/1jjlthSuc9yltWxQDKxeQD4OO9LvH_DaGwEsdlxSE6l8/edit))
96+
to the area you are tracing. Click on
97+
![download][] then tick «Raw GPS
98+
data» near the top in the «Download» window. After downloading, an
99+
additional layer «Downloaded GPX data» will appear.
100+
101+
![downloaded GPX][]
102+
103+
In this example, with the GPS tracks (in red) added you can see that the
104+
existing data (here: the roads) is positioned correctly. The imagery is
105+
actually not correctly georeferenced, and has an offset in comparison
106+
with the reality. It has to be adjusted.
107+
108+
> Do not be confused that the tracks appear like a sequence of
109+
> lines and not one solid line. Most GPS devices have a 2-5 m accuracy,
110+
> which is sufficient for roads because you do not drive or walk in the
111+
> middle of the road. Try to imagine an average GPS trace somewhere in the
112+
> middle of the existing lines.
113+
114+
To offset imagery, right-click the imagery layer or menu «Imagery», open
115+
«New offset», or use the imagery adjust button
116+
![adjust button][] in left toolbar. Then
117+
drag the imagery so that it is correctly overlaid by the tracks. Click
118+
on another tool when it is over. Note that for some projects people will
119+
save offset information to the wiki or other sources so that people
120+
working together on areas can share common values. You can also give the
121+
offset a “Bookmark name” if you need to use it again in the future. This
122+
offset is saved in a new “Imagery offset” menu available from the
123+
imagery drop-down.
124+
125+
![adjust window][]
126+
127+
![downloaded GPX][]
128+
129+
Now that the imagery is adjusted you can trace over it. While mapping
130+
you can hide layer «Downloaded GPX data» if it interferes with your
131+
work.
132+
133+
![adding to existing data][]
134+
135+
One last thing to remember: the offset might not be the same over the
136+
extent of the imagery! This is especially true in regions with a marked
137+
relief. So when the imagery seems to be offset again, repeat the whole
138+
process.
139+
140+
Offsets with no existing data in OSM
141+
------------------------------------
142+
143+
It may happen that you are the first one to OSM map an area, e.g. in
144+
remote rural areas or in developing countries. Therefore, neither
145+
existing OSM data nor GPS tracks can be downloaded.
146+
147+
![no data][]
148+
149+
How can you deal with this since you do not have any reference to
150+
control the offset of the imagery? There are two ways around this:
151+
152+
1. Go into the field: If you have the possibility to use a GPS in the
153+
area, take waypoints on significant infrastructure or objects that
154+
will are visible on the imagery and/or make tracks of the roads,
155+
then add them in JOSM.
156+
157+
2. Use existing data: If you cannot go into the field then another
158+
option is to gather other __Open Database License data (ODbl)__
159+
If you can it is best to check the imagery with another image that
160+
is correctly aligned. If you are offsetting an image based on
161+
another one, using transparency is the easiest way. To do this,
162+
simply click the gradient line and change the opacity of the layer.
163+
164+
![change opacity][]
165+
166+
Usually administration imagery has poor resolution, over ten meters of
167+
resolution, and so might be worst than the previous image.
168+
169+
If you have access to vector data, roads, lakes, rivers and buildings
170+
are your best options for determining how offset your imagery is. Try to
171+
stay away from boundary lines because those are not reliable for
172+
figuring out if imagery is misaligned.
173+
174+
Summary
175+
-------
176+
177+
Tracing imagery is a technique that makes mapping in OSM faster and more
178+
efficient. However, it must be done with precision and care. There are
179+
times when you are digitizing an area and the imagery itself may be off.
180+
Whether it be through poor resolution or poorly georeferenced imagery,
181+
there are ways you can deal with inaccurate imagery. They mainly involve
182+
referencing imagery with GPS traces and tracks.
183+
184+
[puzzle]: {{site.baseurl}}/images/offset_puzzle_en.png
185+
[existing data]: {{site.baseurl}}/images/offset_existing_data_en.png
186+
[download]: {{site.baseurl}}/images/offset_tool_download_en.png
187+
[downloaded GPX]: {{site.baseurl}}/images/offset_downloaded_gpx_en.png
188+
[adjust button]: {{site.baseurl}}/images/offset_tool_adjust_en.png
189+
[adjust window]: {{site.baseurl}}/images/offset_adjust_window_en.png
190+
[adding to existing data]: {{site.baseurl}}/images/offset_add_to_data_en.png
191+
[no data]: {{site.baseurl}}/images/offset_no_data_en.png
192+
[change opacity]: {{site.baseurl}}/images/offset_change_opacity_en.png

0 commit comments

Comments
 (0)