EOTopo 2018 Beta

We are using OSM for the residential street road network (we have been using this as the Streets & Paths on existing mapping interfaces) and are using our own updated ported versions of previous EOTopo roads data (which is a mix of GeoScience and ExplorOz User Treks and Treks data) for the rural data network. The road data conflation process was the hardest part of this release as OSM and all road map data providers have little or no rural data that is reliable so our process was to bring these together - it took me the best part of 18 months to conceive and convert the networks. Hopefully we have the best of both worlds but we have full access to all the data so can update and change independently of OSM on any level - plus we have an in-place upgrade mechanism that means we can easily update the road network each year to facilitate updates to the streets data. However 2018 uses data from all over the place to produce a best of breed topology - for instance last week I spent 2 days converting a data set from the ABS which is called the 2016 Mesh Boundaries and this produced our built up areas system which was used to not only identify built up residential roads (to make them appear smaller at larger scales) but forms an opacity based grey overlay on the map to identify what is effectively a built up area. This sort of data has been added to all layers and levels so it is not at all correct to say OSM is the base map because it is not it forms part of the overall combination of data sources.

No there is no way to distinguish private property from open roads as this would not be topographic, nor would it be possible to maintain. We have identified a number of roads on the map that are private but it is not possible for any map provider to maintain this. We can mark them if we are advised but the other problem them becomes who tells us if the status changes. We have identified all areas of Native Title as a data layer again from the ABS but this does not provide any level of permit requirement or access controls. The other element is that in an emergency situation it does not really matter if it is private or not - if it is there is should be on the map - but as mentioned if we know we can mark it. If a land owner has a sign or gate that is your best guide - failing that it is not really possible to fully identify but just because it is on a map does not mean you can use it freely.
David

Jon,

Not 100% sure however the web browser positioning function does not generally get a position from the gps more often it uses cell tower triangulation or ip lookup for web based map queries. An app that interfaces directly to the gps will be giving the right position and trust me there is no calibration issue of that magnitude within the map data.

David

Ah not sure Stephen I just double checked your user trek and the whole area and every road is there in exactly the place represented in your user route file. Including the crossing and all roads you travelled. I may be additionally showing the old road as i believe it is still there just not being used, but if not I can simply remove it however the right roads are there 100% as represented in your user trek. You may need to look away from the user trek page as the purple line may be covering the roads. From the user trek index (only) you can turn on/off the user trek overlay to confirm.

I just checked that exact crossing and there appears to be a mismatch between my workstation and the online map. I will need to investigate but off for a few days break will get back to you next week. Was there a specific other example you can point me at. I am confused why that road appears different but may have not republished one part of the database. This is what the beta concept was for so thanks for the alert.

Hi David

Enjoy your time off and make sure you leave your phone home.....lol

I did send you a couple more examples of wrong roads in the area via private email. With the new roads in the Nhulunbuy area and the main Central Arnhem Highway that we travelled are the main roads. All new detours no longer give access to the old original road and in most cases, large wind rows and trees have been dragged over the old roads so people can not use them and to let's them revegetate and in a few years will be back to natural bush.



Cheers



Stephen

Thanks Stephen,

Funny I missed this followup as it would have helped me in the questions I just emailed you about the older roads around the newer crossings. Would you be so kind to just confirm via the email I just sent as it has all the updated screen shots for the roads in question. Thanks again for your feedback I am fairly convinced this area is much more accurate however I just need to work out what roads to remove now.

David

Hi David

I have replied and included a couple of photos of the new roads and bridge crossings.

If they do not come through, please let me know.


Cheers


Stephen

Thanks John - I will have to work out why that road is different - we are turning stuff on/off at differing levels however it would appear that there is something funny with that road as it should be enabled on zoom 11 - I will check this out as it will be effecting all areas with this road type (which could be many). It is difficult as the roads network is build from 4 different databases all with differing fields and field codes so in one db the highway = track and in another the class = Track, all good fun (not) and many hours of pouring over data definitions.

David