https://stackoverflow.com/questions/65791074/failed-to-query-the-value-of-property-packagename-manifest-file-does-not-exis

I’ve uploaded my code to github. Can’t get the app to build, so I can’t generate a signed apk. (However the app can run however). Above is the github issue I created. If I can get it to work, I will release a signed apk.

How does the app decide what is left and what is right?

It doesn’t. The only functional purpose of the left and right buttons is to remember the previous housenumber you entered on that side of the road so that you can increment it.

For example, if I entered “24” on the left side, pressing the left button again will show “24” as a hint in the textbox. You can then increment up to “25” by pressing the plus button (and pressing it again to go to “26”). That works like streetcomplete.

Housenumbers are placed on the map underneath the crosshair. You position the crosshair to where the house actually is, then add the address. (This is why alternative background imageries to the default osm-carto is useful, so that you can see where the houses are even if they aren’t drawn in OSM).

I have a few suggestions on the interface: * When pressing < or >, does the keypad come up on fullscreen immediately? If yes, I’d suggest to have only a minimal interface with +/- buttons first (it looks like this is the case in your first screenshot)

It comes up as fullscreen immediately, however, my solution to that is to implement onFling and long press actions for those buttons.

• Long press will automatically add a housenumber to the map that is a set increment higher/lower than your previous housenumber. For example, if your increment is 2, and your previous housenumber is “24”, long pressing will automatically add “26” with the same housenumber.
• Swipe action does this same thing, however it also adds the previous Building levels. This is in case the address you want to add has the same building levels as the previous address.
• The increment & streetname can be set in the Keypad. This is useful because you can check the increment and change the streetname when you change streets, and then use the longpress or swipe features for all the other housenumbers on the street.

@westnordost

Hello, I have been developing my own android app to try and be extremely efficient for adding housenubers. You can read more about it on my diary entry about the software

Here are some screenshots:

P.S. Can you think about any names I could give to this app?

Yes, you are correct, the diary entry didn’t go over merged addresses with buildings. The shortcut is probably different for you, but you can find the tool by going to top menu bar and then: “Data” –> Merge Address Points

You can pretty easily do this in JOSM though. Simply select all the housesnumbers and buildings on a street using free-select, then press Ctrl-Shift-J to merge all the ADDRESS nodes with buildings.

I described this in more detail in my first diary entry

I went to the Vespucci page you described, and there is a multi-line comment explaining exactly how it works. Again, it seems much more complicated than what I need it to be. Vespucci’s algorithm uses data that already exists in OSM, yet my app won’t download any OSM data just yet.

So the output is a .osm file which effectively just contains markers? For example, if I add numbers for three houses in the app, I’ll have to add those numbers to the houses again in JOSM?

Effectively, yes. The correct OSM terminology is nodes, so it is a file that effectively contains multiple housenumber nodes. However, since they are positioned correctly unlike Keypad-Mapper 3, all that needs to be done in JOSM is download the surrounding OSM data and upload. (The validator will find any errors relating to the housenumbers you mapped).

@nickjohnston

You can click on the textbox to open up the keyboard. This is a feature of all basic textboxes in android.

The address prediction logic in Vespucci works reasonably well. Have you looked at that?

As for Vespucci’s prediction logic, I don’t know how it works, but here is how mine works:

If the housenumber is an integer, I simply increment that integer. If it isn’t, I strip the housenumber of all of the non-integer characters, then increment the resulting integer.

This works, for example, to increment “26a” to “27”, but it won’t work for something like “19-100” to “19-101”.

So far, I don’t think that is the most important thing.

You mention you want to add direct upload to OpenStreetMap. What happens with the data now? Also, I’m unclear if this is just adding markers, or actually changing OSM data directly. (Sorry if I’ve missed something.)

It is saved as a “.osm” file on your phone which you can send to your computer and open in JOSM. This is how Keypad-Mapper 3 works as well.

It would be great if the app could also support splitting buildings (like Terracer, and also splitting on arbitrary points, and at half way along one not necessarily straight edge).

This app currently doesn’t work with OSM data, I don’t see much reason for it to right now. Maybe when uploading data to OSM it would be a good idea to check for duplicates, but right now you when you open the osm file in JOSM , JOSM will take care of that.

JOSM also takes care of Terracing, so what reason is there to have this feature in the app?

For imagery, can you use Editor Layer Index?

I’ll look into it since it probably lists all the imageries that can be used to edit OSM data.

Good work

To everyone commenting that we should use the #newbie tag, I think this is a bad idea.

Currently, “review_requested=yes” already exists: simply check the “I want my changeset to be reviewed” button before uploading.

The newbie tag will create two standards of checking for users who want help, which will make it even more confusing. Let’s not do that, I think it is more important to tell users who are more accustomed to OSM to look for changesets tagged with “review_requested=yes” using a software such as osmCHA.

Furthermore, to identify new users, this tag is unnecessary, as like mentioned before, there are many ways of already doing this that don’t require any extra effort. The “#newbie” tag would be a worse way of finding new users because most users won’t use the tag (as most new users have not read this diary entry).

If you are a newbie (welcome!), please add the hashtag #newbie when making changes and explicitly state in your comments that you are a newbie so that other mappers can guide you.

I feel like this is unnecessary. Tools like OSMcha (OSM changeset analyser) allow you to see edits made by new users. You can then contact them if you feel that they could benefit from some tips, help, affirmation etc.

I’m confused? What is the problem with tagging the entrance with “addr:housenumber=134;150” (as you currently do)?

Then any geocoding software will simply display this:

134-150, XX street, XX city, UK

Okay fine.

Oh well, it seems that we can’t use the imagery for the exact reason @nickjohnston stated. Here is a response from NLS when asked about the imagery:

I wish I could give you better news on the 1940s OS maps of south-east England. Unfortunately, you’re right, they were scanned by a third-party commercial company who have placed commercial re-use restrictions on this layer – there are further details under our Copyright Exceptions list at https://maps.nls.uk/copyright.html#exceptions. These restrictions will last for another couple of years – until the end of 2022 – which I know might seem a long way off, but hopefully will pass quickly. Then we’ll be happily able to share them with the OSM community, along with the rest of England and Wales National Grid 1940s-1960s mapping, that will be of interest too.

Seems like 2023 is the year when we get imagery of buildings and housenumbers all over Britain.

For now, however, I don’t know how to delete this diary entry.

Also, you have zero edits. What do you want this info for?

Do you want a way to do this automatically? In JOSM or iD, you can simply move around an entrance, and if the shape of the building changes then the entrance is snapped to the building.

@CoyKoi

Filters seem useful. Infact, it seems even more useful for a guide on creating public transport routes in JOSM, as that requires selecting roads. Often boundary ways are overlayed on top of roads, making the roads impossible to select. This should be really useful for that.

Thanks

For anyone who sees this, I have now removed the “source=Bing” tags from the tagging section, as people have suggested that this is unnecessary. On top of this, pressing CTRL+h easily shows the changesets affecting that building. Going to the first changeset shows the source.

Yes, however why do you not like Java?

What is the point of getting such devices if the only feature is that it records tracks slightly more accurately?

When navigating on a phone, for example, that extreme accuracy doesn’t really matter if the GPS during navigation is going to be inaccurate anyway. I don’t think a road being off by a few metres makes that much of a difference.

I’m sure there might be some use cases for really accurately adjusted features, but I just don’t see buying a device for it, especially when your phone has so many more features, such as taking notes, adding housenumbers (keypad mapper, streetcomplete) etc.

Also, about “adjusting imagery to GPS traces”, I never understood why the community considers that to be so important. I don’t know how accurate the GPS is, I don’t know if the GPS was taken when walking, cycling or driving (Which would effect the position). I just align the imagery to the already existing roads, in most cases, because the GPS tracks tell me nothing. Often on major roads there are 10 tracks whose width is larger than the actual road, and so it provides little purpose at all.

What is the problem with Java?