Display troubles between lines in a geojson and Google streets base map

[nathalie_H]

Hi everyone!

In a form using a geojson for a select_one_from_file with a map appearance, 2 lines materializing walls to check are placed behind the bulding drawing in Google Streets base map and therefore, not visible.

They appear again when I zoom out, but it's a too small scale to work.
When I've changed the base map, switching to Google Satellite and the lines were correctly displayed .
With OSM base map, I can see the lines but because the building drawing doesn't appear exactly in the same location than with Google.

• Here are the screenshots:
  • With Google Streets base map at a large scale:
    *
    
  • With Google Streets base map at a small scale:
    
    
  • With Google Satellite:
    
    
• a simplified version of the form:
  podarcis_liolepis_pr_pb_affichage.xlsx (638.2 KB)
• and the external file (I added a point between geo and json to upload the file because geojson are not authorized extensions):
  podlio_transects_murets.geo.json (5.0 KB)

Have you ever had a similar problem?

Nathalie

[LN]

@dbemke @wkobus does this sound familiar to you? I wonder whether it could be related to or maybe the same issue as https://github.com/getodk/collect/issues/5488

[Grzesiek2010]

Hi @nathalie_H,

It turns out this is an issue with the Google Maps Android SDK. They claim it should be fixed in April. Unfortunately, we can't resolve it on our end, and the only temporary workaround would be to disable building displays.

I'd prefer to leave it as is and wait for the fix, as long as it's not a blocker for you. Is it? Alternatively, you could switch to Google Maps Terrain, which is quite similar to the Streets view.

[nathalie_H]

Hi @Grzesiek2010,
It's absolutely not a blocker for us.
Including buildings in our monitorings is not the most common situation.
I told my colleague to switch to the satellite view, wich is, for me, better for the field work.
Thank you to have checked the problem!

[Grzesiek2010]

Thanks @nathalie_H, for clarifying. We'll wait for the fix in the maps SDK in this case.