beelsebob / openstreetpad Goto Github PK

Description:
Text placement currently overlaps heavily

Steps to reproduce:

1. Find an area with two ways with text on them that cross over at the centre.

Expected results:
Positioning for the labels is chosen such that they do not overlap.

Actual results:
Text overlaps at the crossing point.

OpenStreetPad should support the concept of pseudo tags on objects, including :tagged to indicate if an object has tags.

Description:
Text on ways can look ugly due to poor letter positioning choices.

Steps to reproduce:
Find a way with a kink in it and a name drawn on it.

Expected results:
The text flows nicely round the corner.

Actual results:
The text collides a lot at the corner, or spaces out, depending on which way the corner bends.

OSP's MapCSS implementation does not support @import as of yet – it should!

Description:
OpenStreetPad does not currently support putting shields on ways.

Steps to reproduce:

1. add the attribute shield-text: blah; to an way.

Expected results:
Shields appear along the way.

Actual results:
No rendering change.

Description:
OpenStreetPad currently reloads data from the API every time it is launched, it should be able to cache the data locally for faster access, and to stop putting strain on the OSM servers.

Description:
OpenStreetPad does not currently support MapCSS eval expressions

Steps to reproduce:

1. Add an attribute with the value eval("1");

Expected results:
The expression is evaluated

Actual results:
Failure to use the MapCSS stylesheet correctly

Description:
OpenStreetPad currently has no reasonable way to deal with natural=coastline ways that delimit landmass.

Steps to reproduce:

1. scroll to an area with coast line in it.

Expected results:
The sea and land are correctly rendered.

Actual results:
There is no way to tell sea and land apart.

Description:
text-offset has no affect on labels with text-position: line; specified.

Steps to reproduce:
Add text-position: line; text-offset: 10 to a way type.

Expected results:
Text follows a way 10p below the existing way.

Actual results:
Text is still rendered with its baseline on the way.

Steps to reproduce:

1. Start loading the map.
2. scroll quickly away, before tiles have loaded, scroll again.

Expected results:
The new tiles immediately start loading

Actual results:
All tiles you've scrolled over are loaded.

I am new to github, can someone walk me through exactly how to install this application on my iPhone? Will it work on a device as old as the iPhone 3?

Sorry if this is not the proper venue to ask these questions, but this was the only method I came across to make contact.

Thanks in advance!

-Grant

Description:
When data arrives certain tiles sometimes fail to rerender.

Steps to reproduce:
Unknown, please help debug this!

Hi, how can i add annotation with coordinate on OSPMapView?

Description:
OpenStreetPad can crash when loading tiles in the CFStream handler.

Steps to reproduce:

1. Pan around the map a bit.

Expected results:
No crashes

Actual results:
At random, a crash in the stream handler.

Description:
OpenStreetPad is currently constrained to within one meta tile.

Steps to reproduce:

1. Start open street pad.
2. scroll to the side until you find a white area.

Expected results:
No white area.

Actual results:
White beyond the edge of one meta tile.

Why not add CoreParse as a Git submodule for easier installation? It's rather complicated to get the project up & built, and you have to dig around to understand that CoreParse should go in a folder called CoreParse (exactly), etc.

OpenStreetPad should support the exit; declaration in MapCSS.

Description:
Text on way can be positioned very poorly at the moment, it should rely on a few more heuristics to decide where's a good plane:

1. Don't place it anywhere where the way curves too much.
2. Try to avoid crossing other ways of the same type.

Description:
Some text labels appear with lettering at an angle.

Steps to reproduce:

1. Browse around an area with many text labels on points and text labels on ways.

Expected Results:
All text labels on points are horizontal.

Actual Results:
Some text labels are rendered with lettering angled.

Description:
The styler currently ignores all zoom conditions in MapCSS, it shouldn't!

support for multipolygons.

variants:

http://wiki.openstreetmap.org/wiki/Relation:multipolygon

can also be acheived with changing internal representation:

http://en.wikipedia.org/wiki/Well-known_text
http://geojson.org/geojson-spec.html
https://github.com/kothic/kothic-js/wiki/Tiles-format

Thanks, this is really great job, can you write some tutor
how did you create TestData.pbf file.
Thanks.

Add support zooming the map with a two finger pinch.

Rendering is not fast enough to work live, so we need to take a copy of the rendered tiles, and scale the images during the zoom, then rerender on stop.

Add support to the API for writing out osm files.

Description:
OpenStreetPad currently only supports pulling data directly out of the OSM API, it should support more sources, e.g. .osm files or shape files.

Description:
Text on ways can sometimes render from right to left, it should always render from left to right.

Steps To Reproduce:

1. Find a way which curves around in a C shape, and contains a steep angle where text would normally be rendered.
2. Make sure that on said way, the text ends up rendered somewhere where it must be reversed on the way.

Expected results:
Text facing from left to right.

Actual results:
Text facing from right to left and upside down.

Hey I came to visit the OpenStreetPad github page and was surprised to see a map of Monaco in the description so I was wondering How come you decided to put this map ? I'm from Monaco by the way...
Cheers.

Description:
Open zoom ranges in MapCSS do not work, they cause the parser to baulk.

Steps to reproduce:

1. put this in the MapCSS file:
   way|16-
   {
   text: tag("name");
   }
2. try to make OpenStreetPad read it.

Expected result:
names appear on all ways over zoom 16.

Actual result:
Failure to parse the MapCSS file.

Description:
OSP currently starts up showing the centre of Elgin, it should use CoreLocation to grab your current location, or remember where you were last looking at.

Description:
OpenStreetPad should be able to deal with layer identifiers to apply more than one style to the same object.

Steps to reproduce:
Add ::someLayerName to the end of a MapCSS selector.

Expected Results:
OSP accepts this selector and renders the way in more than one way based on the number of layer identifiers provided.

Actual results:
A MapCSS parse error.

Description:
Tiles render only a 1/8th border of objects around them, they need to use the bounding boxes of styled objects instead to guarantee that all objects that should be visible, are.

Description:
text-offset has no affect on labels with text-position: line; specified.

Steps to reproduce:
Add text-position: line; text-offset: 10 to a way type.

Expected results:
Text follows a way 10p below the existing way.

Actual results:
Text is still rendered with its baseline on the way.

Description:
Russian names of roads are not showed. The problem is only with objects, which have value "line" for key "text-position" in tags. There is a message ": Helvetica-Light: FT_Load_Glyph failed: error 6" in console

Steps to reproduce:

1. replace TestData.pbf with that one: http://dl.dropbox.com/u/45754014/TestData.pbf
2. replace 71st string in OSPMapView with: [self setMapArea:OSPMapAreaMake(OSPCoordinate2DProjectLocation(CLLocationCoordinate2DMake(55.74234, 37.61374)), 17.0)];
3. build and run OpenStreetPad

Expected result:
All roads' names displayed correctly

Actual result:
Roads' names are not displayed (but buildings' names are) and console message ": Helvetica-Light: FT_Load_Glyph failed: error 6" is showed